public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Bolle <pebolle@tiscali.nl>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: Steven Newbury <steve@snewbury.org.uk>,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	David Airlie <airlied@linux.ie>,
	intel-gfx <intel-gfx@lists.freedesktop.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Yinghai Lu <yinghai@kernel.org>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>
Subject: Re: [Intel-gfx] agp/intel: can't ioremap flush page - no chipset flushing
Date: Tue, 11 Mar 2014 01:15:24 +0100	[thread overview]
Message-ID: <1394496924.16134.40.camel@x220> (raw)
In-Reply-To: <CAErSpo6Q0w0OAenw7Uh0bjiZucpxatkUuWzREHmEvsNKJYf-qw@mail.gmail.com>

On Mon, 2014-03-10 at 18:07 -0600, Bjorn Helgaas wrote:
> On Mon, Mar 10, 2014 at 5:45 PM, Paul Bolle <pebolle@tiscali.nl> 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?

Thanks,


Paul Bolle


  reply	other threads:[~2014-03-11  0:15 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-08 19:06 agp/intel: can't ioremap flush page - no chipset flushing Paul Bolle
2014-02-08 19:59 ` Daniel Vetter
2014-02-08 20:22   ` Paul Bolle
2014-02-09  0:02     ` Daniel Vetter
2014-02-09 13:15       ` [Intel-gfx] " Steven Newbury
2014-02-09 13:25         ` Paul Bolle
2014-02-09 13:32           ` Steven Newbury
2014-02-10 21:33           ` Bjorn Helgaas
2014-03-06 20:25             ` Paul Bolle
2014-03-06 21:38               ` Bjorn Helgaas
2014-03-07 20:33               ` Bjorn Helgaas
2014-03-07  9:48             ` Paul Bolle
2014-03-07 16:55               ` Bjorn Helgaas
2014-03-07 17:16                 ` Paul Bolle
2014-03-07 20:40                   ` Bjorn Helgaas
2014-03-07 21:03                     ` Paul Bolle
2014-03-07 22:07                       ` Bjorn Helgaas
2014-03-08 14:12                     ` Bjorn Helgaas
2014-03-08 14:44                       ` Paul Bolle
2014-03-10 18:24                         ` Bjorn Helgaas
2014-03-10 23:45                           ` Paul Bolle
2014-03-11  0:07                             ` Bjorn Helgaas
2014-03-11  0:15                               ` Paul Bolle [this message]
2014-03-11  2:07                                 ` Bjorn Helgaas
2014-03-11  9:20                                   ` Paul Bolle

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1394496924.16134.40.camel@x220 \
    --to=pebolle@tiscali.nl \
    --cc=airlied@linux.ie \
    --cc=bhelgaas@google.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=steve@snewbury.org.uk \
    --cc=yinghai@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox