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 <[email protected]> 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. Ken -- das eine Mal als Tragödie, das andere Mal als Farce
Attachment:
config.amd64.gz
Description: application/gunzip
- Follow-Ups:
- Re: Lockup after logging out of X
- From: Andi Kleen <[email protected]>
- Re: Lockup after logging out of X
- From: "Michal Piotrowski" <[email protected]>
- Re: Lockup after logging out of X
- From: [email protected]
- Re: Lockup after logging out of X
- Prev by Date: [2.6.22 PATCH 26/26] dm log: fix resume failed log device
- Next by Date: [GIT PATCHES] V4L/DVB updates
- Previous by thread: [2.6.22 PATCH 26/26] dm log: fix resume failed log device
- Next by thread: Re: Lockup after logging out of X
- Index(es):