From: Dave Jones <davej@redhat.com>
To: Carlo Wood <carlo@alinoe.com>,
linux-kernel@vger.kernel.org, eric@anholt.net,
zhenyu.z.wang@intel.com
Subject: Re: [AGPGART] intel_agp: use table for device probe
Date: Sun, 17 Jun 2007 15:07:14 -0400 [thread overview]
Message-ID: <20070617190714.GA18115@redhat.com> (raw)
In-Reply-To: <20070617162235.GA5486@alinoe.com>
On Sun, Jun 17, 2007 at 06:22:35PM +0200, Carlo Wood wrote:
> > Hi Dave, I have an amd64 box for which every kernel
> > after 2.6.18 hangs during boot, so I have no dmesg :(
> >
> > I used git bisect to find out where the problem patch is,
> > and assuming bisect works (imho it jumped between versions
> > very weirdly: closing in on the last 6 revisions, it
> > jumped from 2.6.18 to 2.6.18-rc2 to 2.6.18-rc6), the problem
> > is a patch in intel-agp.c, where support for the intel 965G
> > is added (which I have).
> Dave, I have no idea why you never replied to this -- don't
> you care that kernels 2.6.19 through 2.6.21 lockup on boot? --
Sometimes things fall through the cracks..
I haven't heard any similar problems, which makes it somewhat odd.
> The patch causes my machine to lock up and/or crash
> in various ways (depending on the exact version of the kernel),
> very shortly after printing: agpgart: Detected an Intel 965G Chipset.
>
> The first kernel version that stops doing that is 2.6.22-rc5.
> I used git bisect once more to find the patch that fixes this bug:
> I am mailing this mostly because the comment doesn't seem to indicate
> that the author is aware that this patch fixes an existing regression
> (it worked fine for me with 2.6.18).
Indeed, it was unknown to me too, this should have just been
a clean-up.
> If anyone wants to know more (like what hardware I'm using), please
> show me that you're actually alive / reading my mails.
Out of curiousity, I'd like to see your lspci
(not -v or anything, just run with no args)
Dave
--
http://www.codemonkey.org.uk
next prev parent reply other threads:[~2007-06-17 19:07 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-13 8:02 DRI/AGP on AMD64 based machine Alex Bennee
2007-06-13 16:29 ` Dave Jones
2007-06-14 1:15 ` Carlo Wood
2007-06-14 1:17 ` Dave Airlie
2007-06-14 4:36 ` Carlo Wood
2007-06-14 4:40 ` Dave Airlie
2007-06-17 16:22 ` [AGPGART] intel_agp: use table for device probe Carlo Wood
2007-06-17 19:07 ` Dave Jones [this message]
2007-06-17 19:59 ` Carlo Wood
2007-06-17 20:49 ` Dave Jones
2007-06-17 21:13 ` Carlo Wood
2007-06-17 21:33 ` Dave Jones
2007-06-17 21:55 ` Carlo Wood
2007-06-17 22:19 ` Carlo Wood
2007-06-17 22:36 ` Carlo Wood
2007-06-17 22:49 ` Dave Jones
2007-06-18 0:06 ` Carlo Wood
2007-06-18 0:16 ` Dave Jones
2007-06-18 0:57 ` Dave Airlie
2007-06-18 1:56 ` Carlo Wood
2007-06-18 2:18 ` Dave Airlie
2007-06-18 17:37 ` Carlo Wood
2007-06-18 2:37 ` Wang Zhenyu
2007-06-18 17:42 ` Chuck Ebbert
2007-06-18 18:06 ` Dave Jones
2007-06-18 20:13 ` Carlo Wood
2007-06-18 19:58 ` Carlo Wood
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=20070617190714.GA18115@redhat.com \
--to=davej@redhat.com \
--cc=carlo@alinoe.com \
--cc=eric@anholt.net \
--cc=linux-kernel@vger.kernel.org \
--cc=zhenyu.z.wang@intel.com \
/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