linux-kernel - Re: linux-next: Tree for Sept 11 (drm related: boot problems on amd64)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <CA+icZUUj1u6YwpkzXOsUVJ4p5t-qrCWVDoaFoDbAbMT2EbEwWw@mail.gmail.com>
Date:	Tue, 11 Sep 2012 20:12:13 +0200
From:	Sedat Dilek <sedat.dilek@...il.com>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
	Dave Airlie <airlied@...il.com>,
	Daniel Vetter <daniel.vetter@...ll.ch>
Subject: Re: linux-next: Tree for Sept 11 (drm related: boot problems on amd64)

On Tue, Sep 11, 2012 at 8:31 AM, Stephen Rothwell <sfr@...b.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.

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