From: Kevin Winchester <kjwinchester@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for June 11
Date: Wed, 11 Jun 2008 21:17:09 -0300 [thread overview]
Message-ID: <48506B05.6030507@gmail.com> (raw)
In-Reply-To: <20080611193840.08a35b14.sfr@canb.auug.org.au>
Stephen Rothwell wrote:
> Hi all,
>
> Changes since next-20080610:
>
> Dropped trees (temporary): ldp (it is unfetchable - probably something to
> do with the new Staging tree), block (it just has too many conflicts and
> breaks the powerpc build).
>
> The kbuild-current tree is now itself again.
>
> The kbuild tree fixed it build problem.
>
> The usb tree lost its hid build problem.
>
> The tip-core tree lost its conflict (since the kbuild tree effectively
> moved).
>
> The x86 tree gained two conflicts with the ftrace tree.
>
> The pci tree lost its conflict with the kbuild-current tree but gained
> one with the x86 tree and one with the driver-core tree.
>
> The hid tree lost its conflict with the driver-core tree.
>
> The nsfd tree gained a conflict with the cpus4096 tree.
>
> The powerpc tree was fixed up so that it no longer needed a commit
> reverted.
>
> The net tree lost its conflict with the net-current tree.
>
> The galak tree gained a conflict with the net tree.
>
> The wireless tree lost all its conflicts.
>
> The rr tree gained a conflict with the net-current tree.
>
> I have applied the following temporary patch for known build problems:
>
> "Fix various 8390 builds" - the net tree broke builds on various
> architectures - hopefully this patch will go into the net tree shortly.
>
> The powerpc64 allyesconfig build is broken, probably by ftrace.
> The sparc32 defconfig build is broken, probably by the kbuild tree.
>
I see a problem with this tree (and possibly with ones from previous
days - I haven't tested next in 2-3 days or so). I have no direct
rendering as reported by glxinfo, whereas with Linus' latest tree I do.
I checked my logs and I see:
PCI: Using ACPI for IRQ routing
PCI: Cannot allocate resource region 0 of device 0000:00:00.0
agpgart: Detected AGP bridge 0
agpgart: Aperture conflicts with PCI mapping.
agpgart: Aperture from AGP @ e0000000 size 128 MB
agpgart: Aperture conflicts with PCI mapping.
agpgart: No usable aperture found.
agpgart: Consider rebooting with iommu=memaper=2 to get a good aperture.
In a working kernel, all I see is:
PCI: Using ACPI for IRQ routing
agpgart: Detected AGP bridge 0
agpgart: Aperture from AGP @ e0000000 size 128 MB
Does anyone have any idea where I would start to look for the cause?
Would it be a PCI problem? An AGP problem? An x86 problem?
If necessary I can bisect, but 12-13 compile-boot cycles will take me a
few evenings worth of computer time. A targeted revert or two to try
would help.
Thanks,
--
Kevin Winchester
next prev parent reply other threads:[~2008-06-12 0:17 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-11 9:38 linux-next: Tree for June 11 Stephen Rothwell
2008-06-11 14:32 ` [BUILD-FAILURE] linux-next: Tree for June 11 - on ia64 Kamalesh Babulal
2008-06-11 14:44 ` Kamalesh Babulal
2008-06-11 14:50 ` Sam Ravnborg
2008-06-11 14:50 ` Sam Ravnborg
2008-06-11 16:46 ` Kamalesh Babulal
2008-06-11 16:58 ` Kamalesh Babulal
2008-06-11 23:10 ` Stephen Rothwell
2008-06-11 23:10 ` Stephen Rothwell
2008-06-11 23:14 ` Stephen Rothwell
2008-06-11 23:14 ` Stephen Rothwell
2008-06-11 18:55 ` linux-next: Tree for June 11 Greg KH
2008-06-12 0:05 ` ldp/staging/driver-core (Was: Re: linux-next: Tree for June 11) Stephen Rothwell
2008-06-12 0:17 ` Greg KH
2008-06-12 0:17 ` Kevin Winchester [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-06-11 9:14 linux-next: Tree for June 11 Stephen Rothwell
2010-06-11 4:17 Stephen Rothwell
2010-06-11 23:31 ` Andrew Morton
2010-06-15 9:26 ` Rusty Russell
2010-06-15 9:34 ` Andrew Morton
2010-06-23 22:53 ` Andrew Morton
2010-06-25 12:57 ` Rusty Russell
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=48506B05.6030507@gmail.com \
--to=kjwinchester@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.