linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bjorn Helgaas <bhelgaas@google.com>
To: sedat.dilek@gmail.com
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	Dave Airlie <airlied@gmail.com>,
	Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: Re: linux-next: Tree for Sept 11 (drm related: boot problems on amd64)
Date: Wed, 12 Sep 2012 13:52:47 -0600	[thread overview]
Message-ID: <CAErSpo6RbLF1KTs8sHyJCu2NX7u4BRwFp0NQCtaXSiq-bUEThg@mail.gmail.com> (raw)
In-Reply-To: <CA+icZUVSWBLrRu_vOcGurp=x-Bb1dBv1Tfdf8P8LiPNM1SuR8Q@mail.gmail.com>

On Tue, Sep 11, 2012 at 4:04 PM, Sedat Dilek <sedat.dilek@gmail.com> wrote:
> On Tue, Sep 11, 2012 at 8:29 PM, Sedat Dilek <sedat.dilek@gmail.com> wrote:
>> On Tue, Sep 11, 2012 at 8:12 PM, Sedat Dilek <sedat.dilek@gmail.com> wrote:
>>> On Tue, Sep 11, 2012 at 8:31 AM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>>>> Hi all,
>>>>
>>>> Changes since 201209010:
>>>>
>>>> New tree: ixp4xx
>>>>
>>>> The pci tree gained a build failure so I used the version from
>>>> next-20120910.
>>>>
>>>> The regulator tree lost its build failure.
>>>>
>>>> The staging tree lost its build failure.
>>>>
>>>> The akpm tree lost a few patches that turned up elsewhere.
>>>>
>>>> ----------------------------------------------------------------------------
>>>>
>>>
>>> Hi,
>>>
>>> today's and yesterday's Linux-Next is broken for me again.
>>> I tried with systemd and upstart on Ubuntu/precise, with nomodeset and
>>> rescue boot-option.
>>>
>>> With rescue boot-option I see this in my logs (Intel sandy-bridge
>>> ultrabook here):
>>>
>>> Sep 11 18:43:36 fambox kernel: [    9.654972] [drm:drm_pci_agp_init]
>>> *ERROR* Cannot initialize the agpgart module.
>>> Sep 11 18:43:36 fambox kernel: [    9.654980] DRM: Fill_in_dev failed.
>>>
>>> I have not checked any MLs... coming from hospital right now.
>>>
>>
>> More ERRORs:
>>
>> # grep -A1 "ERROR" /var/log/kern.log
>> Sep 10 17:51:29 fambox kernel: [   10.205818]
>> [drm:i915_get_bridge_dev] *ERROR* bridge device not found
>> Sep 10 17:51:29 fambox kernel: [   10.206055] i915: probe of
>> 0000:00:02.0 failed with error -5
>> --
>> Sep 10 15:53:00 fambox kernel: [   10.500387]
>> [drm:i915_get_bridge_dev] *ERROR* bridge device not found
>> Sep 10 15:53:00 fambox kernel: [   10.500602] i915: probe of
>> 0000:00:02.0 failed with error -5
>> --
>> Sep 11 20:41:01 fambox kernel: [    9.636010]
>> [drm:i915_get_bridge_dev] *ERROR* bridge device not found
>> Sep 11 20:41:01 fambox kernel: [    9.636202] i915: probe of
>> 0000:00:02.0 failed with error -5
>> --
>> Sep 11 18:42:18 fambox kernel: [   10.132229]
>> [drm:i915_get_bridge_dev] *ERROR* bridge device not found
>> Sep 11 18:42:18 fambox kernel: [   10.132433] i915: probe of
>> 0000:00:02.0 failed with error -5
>> --
>> Sep 11 18:43:36 fambox kernel: [    9.654972] [drm:drm_pci_agp_init]
>> *ERROR* Cannot initialize the agpgart module.
>> Sep 11 18:43:36 fambox kernel: [    9.654980] DRM: Fill_in_dev failed.
>> --
>> Sep 11 19:52:10 fambox kernel: [    9.545562]
>> [drm:i915_get_bridge_dev] *ERROR* bridge device not found
>> Sep 11 19:52:10 fambox kernel: [    9.545798] i915: probe of
>> 0000:00:02.0 failed with error -5
>> --
>> Sep 11 20:04:09 fambox kernel: [    9.798233]
>> [drm:i915_get_bridge_dev] *ERROR* bridge device not found
>> Sep 11 20:04:09 fambox kernel: [    9.798557] i915: probe of
>> 0000:00:02.0 failed with error -5
>>
>
> [ CC Bjorn (pci maintainer) ]
>
> I pulled in pci.git#next up to commit
> 9c33332178e6ba49fe48c468edc08ad94b53e1b1 ("Merge branch
> 'pci/gavin-window-alignment' into next") on top of next-20120911.
> This lets my machine boot, but freezes somewhere else.

We had a PCI bug in an earlier version of this patch:
http://git.kernel.org/?p=linux/kernel/git/helgaas/pci.git;a=commitdiff;h=b9443f401bb20ae6414e3e68bca0413bad28b689
that caused lspci to fail.

I suspect this also caused the issue you saw.  We've since fixed it,
but let me know if you see a PCI-related issue again.

Bjorn

  reply	other threads:[~2012-09-12 19:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-11 18:12 linux-next: Tree for Sept 11 (drm related: boot problems on amd64) Sedat Dilek
2012-09-11 18:29 ` Sedat Dilek
2012-09-11 22:04   ` Sedat Dilek
2012-09-12 19:52     ` Bjorn Helgaas [this message]
2012-09-13  3:01       ` Sedat Dilek

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=CAErSpo6RbLF1KTs8sHyJCu2NX7u4BRwFp0NQCtaXSiq-bUEThg@mail.gmail.com \
    --to=bhelgaas@google.com \
    --cc=airlied@gmail.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sedat.dilek@gmail.com \
    --cc=sfr@canb.auug.org.au \
    /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;
as well as URLs for NNTP newsgroup(s).