From: Ken Moffat <zarniwhoop@ntlworld.com>
To: Valdis.Kletnieks@vt.edu
Cc: linux-kernel@vger.kernel.org,
"Eric W. Biederman" <ebiederm@xmission.com>,
Vivek Goyal <vgoyal@in.ibm.com>, Andi Kleen <ak@suse.de>
Subject: Re: Lockup after logging out of X
Date: Tue, 8 May 2007 21:48:52 +0100 [thread overview]
Message-ID: <20070508204852.GA30610@deepthought> (raw)
In-Reply-To: <16635.1178655711@turing-police.cc.vt.edu>
On Tue, May 08, 2007 at 04:21:51PM -0400, Valdis.Kletnieks@vt.edu wrote:
> On Tue, 08 May 2007 20:51:42 BST, Ken Moffat said:
>
> > After trying git-bisect, it tells me:
> > 0dbf7028c0c1f266c9631139450a1502d3cd457e is first bad commit
> > commit 0dbf7028c0c1f266c9631139450a1502d3cd457e
> > Author: Vivek Goyal <vgoyal@in.ibm.com>
> > Date: Wed May 2 19:27:07 2007 +0200
> >
> > [PATCH] x86: __pa and __pa_symbol address space separation
[...]
>
> I saw this same exact problem on my box back at 21-rc5-mm4, but didn't
> report it here because Christoph Hellwig thinks such things are off-topic (as
> I was seeing it with the NVidia driver).
>
> http://marc.info/?l=linux-kernel&m=117579249300455&w=2
> http://www.nvnews.net/vbulletin/showthread.php?t=89444
>
> Sorry to see you hit a problem with the exact same patch with a Radeon card
> a month later.
>
OK, in view of the minimal oops output that made it to my log
(forgot to say in today's repost that it was from one of the bad
bisect builds), I'd better point out that I don't have the ati
module (fglrx or whatever it is called), this is purely using Linus'
tree.
Ken
--
das eine Mal als Tragödie, das andere Mal als Farce
next prev parent reply other threads:[~2007-05-08 20:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-08 19:51 Lockup after logging out of X Ken Moffat
2007-05-08 20:21 ` Valdis.Kletnieks
2007-05-08 20:48 ` Ken Moffat [this message]
2007-05-08 22:47 ` Michal Piotrowski
2007-05-08 23:03 ` Ken Moffat
2007-05-09 1:48 ` young dave
2007-05-08 23:01 ` Andi Kleen
2007-05-08 23:42 ` Valdis.Kletnieks
2007-05-09 0:14 ` Ken Moffat
2007-05-09 9:08 ` Andi Kleen
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=20070508204852.GA30610@deepthought \
--to=zarniwhoop@ntlworld.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=ak@suse.de \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vgoyal@in.ibm.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