[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6bffcb0e0705081547t198ed83eg3f4861617216127d@mail.gmail.com>
Date: Wed, 9 May 2007 00:47:02 +0200
From: "Michal Piotrowski" <michal.k.k.piotrowski@...il.com>
To: "Ken Moffat" <zarniwhoop@...world.com>
Cc: linux-kernel@...r.kernel.org,
"Eric W. Biederman" <ebiederm@...ssion.com>,
"Vivek Goyal" <vgoyal@...ibm.com>, "Andi Kleen" <ak@...e.de>
Subject: Re: Lockup after logging out of X
Hi Ken,
On 08/05/07, Ken Moffat <zarniwhoop@...world.com> wrote:
> This is a resend, with a better title and slightly more
> clarification. Originally sent yesterday evening, but I can see no
> evidence that it got beyond my isp's mailserver. Apologies to the
> Cc's if you did get the original.
>
> Using Linus' tree pulled on Sunday afternoon UK time. Running an
> amd64 ('pure64') desktop using gdm for graphical login, on Xorg 7.2
> with a radeon 9200se. No problems until I log out of the desktop
> and go back to gdm. Before that, the text consoles seem to be
> working fine. After I go back to gdm. the display is corrupted and
> only MagicSysRQ works. Mostly, the keyboard LEDs flash, but the
> only thing that made it to the logs was this exceedingly incomplete
> oops report:
>
> May 7 21:02:54 bluesbreaker kernel: [ 46.549615] [drm] writeback
> test succeeded in 1 usecs
> May 7 21:03:24 bluesbreaker kernel: [ 61.552793] Unable to handle
> kernel paging request at ffff81003befd3e8 RIP:
> May 7 21:03:24 bluesbreaker kernel: [ 61.552798]
> [<ffffffff80271576>] fasync_helper+0x52/0xf0
> May 7 21:03:24 bluesbreaker kernel: [ 61.552805] PGD 8063 PUD
> 9063 PMD 800000003bef11e3 BAD
> May 7 21:03:24 bluesbreaker kernel: [ 61.552811] Oops: 0009 [1]
> PREEMPT
> May 7 21:04:18 bluesbreaker syslogd 1.4.1: restart.
>
> After trying git-bisect, it tells me:
> 0dbf7028c0c1f266c9631139450a1502d3cd457e is first bad commit
> commit 0dbf7028c0c1f266c9631139450a1502d3cd457e
> Author: Vivek Goyal <vgoyal@...ibm.com>
> Date: Wed May 2 19:27:07 2007 +0200
>
> [PATCH] x86: __pa and __pa_symbol address space separation
>
> Currently __pa_symbol is for use with symbols in the kernel
> address
> map and __pa is for use with pointers into the physical memory
> map.
> But the code is implemented so you can usually interchange the
> two.
>
> __pa which is much more common can be implemented much more
> cheaply
> if it is it doesn't have to worry about any other kernel address
> spaces. This is especially true with a relocatable kernel as
> __pa_symbol needs to peform an extra variable read to resolve
> the address.
>
> [snip the rest of the commit message on the resend]
> This time, I'll gzip the config in case it was a size problem for
> the list.
Please check the latest -git.
31 hours ago Linus Torvalds Revert "[PATCH] x86: __pa and
__pa_symbol address space ...
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=e3ebadd95cb621e2c7436f3d3646447ac9d5c16d
>
> Ken
> --
> das eine Mal als Tragödie, das andere Mal als Farce
>
>
Regards,
Michal
--
Michal K. K. Piotrowski
Kernel Monkeys
(http://kernel.wikidot.com/start)
-
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/
Powered by blists - more mailing lists