Re: [Intel-gfx] agp/intel: can't ioremap flush page - no chipset flushing

[Paul Bolle]

Bjorn Helgaas schreef op ma 10-03-2014 om 20:07 [-0600]:
> On Mon, Mar 10, 2014 at 6:15 PM, Paul Bolle <pebolle@xxxxxxxxxx> wrote:
> > On Mon, 2014-03-10 at 18:07 -0600, Bjorn Helgaas wrote:
> >> On Mon, Mar 10, 2014 at 5:45 PM, Paul Bolle <pebolle@xxxxxxxxxx> wrote:
> >> > A bit of doubt is caused by two new boot time messages:
> >> >     pnp 00:00: unknown resource type 10 in _CRS
> >> >     pnp 00:00: can't evaluate _CRS: 1
> >> >
> >> > But I haven't yet tried v3.14-rc6 without your patch, so these might be
> >> > unrelated. They're unclear to me, anyway.
> >>
> >> Hmm, this is definitely concerning.  Resource type 10 is
> >> ACPI_RESOURCE_TYPE_FIXED_MEMORY32, which we do handle (unless it's
> >> length 0).  And your previous dmesg logs (at
> >> https://bugzilla.kernel.org/show_bug.cgi?id=71611) don't show anything
> >> like that.
> >>
> >> Can you attach an acpidump and the dmesg log with my patch to the bugzilla?
> >
> > It's getting rather late over here. So I'll try (quite) a few hours
> > later. But acpidump doesn't ring any bells right now. Any hints?
> 
> There's acpidump info here: https://01.org/linux-acpi/utilities .  You
> don't need to extract the binary tables or anything; just attach the
> text dump to the bugzilla.

(On Fedora it's shipped in acpica-tools. But since acpidump is a symlink
to /usr/bin/acpidump-acpica that is created at install time it won't
show up when one does "repoquery -f "*/acpidump". Add to this that "yum
list pmtools" returns an error, and one is guaranteed roughly 30 minutes
of sheer fun. Unsurprisingly, stubbornly trying "yum install pmtools"
will actually install acpica-tools.)

At least this all is written down somewhere now.)

> It would be very interesting to try v3.14-rc6 without my patch.  I
> hope it has the same "unknown resource type" messages, because I don't
> see how my patch could be related to them.  There were no recent
> PNP-related changes, so then I start to worry about some sort of
> memory corruption from an unrelated patch.  But I hope that's not the
> case.

lkml.org is returning some error page, but Markus Trippelsdorf just
reported seeing this message too. Markus is unlikely to be also trying
this patch.

I've just added you to the CC's of my reply to Markus. I won't update
the bugzilla report for now, because those messages appear unrelated to
your patch.

Thanks,


Paul Bolle

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/