Lockup after logging out of X
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
Signature · 1 line
das eine Mal als Tragödie, das andere Mal als Farce
Quoted 11 lines · Ken Moffat
After trying git-bisect, it tells me:
0dbf7028c0c1f266c9631139450a1502d3cd457eis first bad commit commit0dbf7028c0c1f266c9631139450a1502d3cd457eAuthor: Vivek Goyal <[email protected]> Date: Wed May 2 19:27:07 2007 +0200[PATCH] x86:
__paand__pa_symboladdress space separationCurrently
__pa_symbolis for use with symbols in the kernel address map and__pais for use with pointers into the physical memory map. But the code is implemented so you can usually interchange the two.
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.
Quoted 9 lines · On Tue, May 08, 2007 at 04:21:51PM -0400, [email protected] wrote:
Quoted 7 lines · Ken Moffat
After trying git-bisect, it tells me:
0dbf7028c0c1f266c9631139450a1502d3cd457eis first bad commit commit0dbf7028c0c1f266c9631139450a1502d3cd457eAuthor: Vivek Goyal <[email protected]> Date: Wed May 2 19:27:07 2007 +0200[PATCH] x86:
__paand__pa_symboladdress space separation
[...]
Quoted 11 lines
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=89444Sorry 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
Signature · 1 line
das eine Mal als Tragödie, das andere Mal als Farce
Hi Ken,
Quoted 48 lines · Ken Moffat
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:
0dbf7028c0c1f266c9631139450a1502d3cd457eis first bad commit commit0dbf7028c0c1f266c9631139450a1502d3cd457eAuthor: Vivek Goyal <[email protected]> Date: Wed May 2 19:27:07 2007 +0200[PATCH] x86:
__paand__pa_symboladdress space separationCurrently
__pa_symbolis for use with symbols in the kernel
address
map and__pais for use with pointers into the physical memory
map.
But the code is implemented so you can usually interchange the
two.
__pawhich 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_symbolneeds to peform an extra variable read to resolve the address.
Quoted 3 lines
[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 ...
Quoted 6 lines
Ken
--
das eine Mal als Tragödie, das andere Mal als Farce
Regards,
Michal
Signature · 3 lines
Michal K. K. Piotrowski Kernel Monkeys (http://kernel.wikidot.com/start)
Quoted 7 lines · Michal Piotrowski
Please check the latest -git.
31 hours ago Linus Torvalds Revert "[PATCH] x86:
__paand__pa_symboladdress space ...
Thanks.
Quoted 8 lines
Regards,
MichalSignature · 3 lines
Michal K. K. Piotrowski Kernel Monkeys (http://kernel.wikidot.com/start)
Signature · 1 line
das eine Mal als Tragödie, das andere Mal als Farce
Hi,
Seems I have the same problem. Sometimes whole system is locked, sometimes keyboard is still active but others dead.
It does not happen till now since I run a silly script on background to log the kernel messages:
-----------------
#!/bin/sh
while true; do
sleep 3
dmesg >/tmp/dmesg.txt
sync
done
-----------------
My video card is radeon x600 , fglrx driver is not used.
Quoted 26 lines · Ken Moffat
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.
Quoted 3 lines
After trying git-bisect, it tells me:
0dbf7028c0c1f266c9631139450a1502d3cd457eis first bad commit commit0dbf7028c0c1f266c9631139450a1502d3cd457e
Already known, although it is still unclear what the bug actually is. Can you run with the appended patch please (from Eric Biederman) and post any backtraces the WARN_ON in there spews out?
Also do you use swiotlb?
Thanks
-Andi
include/asm-x86_64/page.h +12 -1
@@ -105,7 +105,18 @@ extern unsigned long phys_base;/* Note: __pa(&symbol_visible_to_c) should be always replaced with __pa_symbol. Otherwise you risk miscompilation. */ -#define __pa (x) ((unsigned long)(x) - PAGE_OFFSET) +#define __pa (x) \ +({ \ + unsigned long v; \ + asm("" : "=r" (v) : "0" ((unsigned long)(x))); \ + WARN_ON(v >= __START_KERNEL_map); \ + if (likely(v < __START_KERNEL_map)) \ + v -= PAGE_OFFSET; \ + else \ + v = (v - __START_KERNEL_map) + phys_base; \ + v; \ +}) +/* __pa_symbol should be used for C visible symbols. This seems to be the official gcc blessed way to do such arithmetic. */ #define __pa_symbol (x) \
include/asm-x86_64/page.h extern unsigned long phys_base; · line 116
Quoted 11 lines · Andi Kleen
Already known, although it is still unclear what the bug actually is. Can you run with the appended patch please (from Eric Biederman) and post any backtraces the
WARN_ONin there spews out?include/asm-x86_64/page.h +4
-0+if (likely (v < __START_KERNEL_map)) \ + v -=PAGE_OFFSET ; \ +else \ + v = (v - __START_KERNEL_map) + phys_base; \
ERROR: "phys_base" [net/sunrpc/sunrpc.ko] undefined!
ERROR: "phys_base" [net/sunrpc/auth_gss/rpcsec_gss_spkm3.ko] undefined!
ERROR: "phys_base" [net/sunrpc/auth_gss/auth_rpcgss.ko] undefined!
ERROR: "phys_base" [net/mac80211/mac80211.ko] undefined!
ERROR: "phys_base" [net/ieee80211/ieee80211_crypt_wep.ko] undefined!
ERROR: "phys_base" [net/ieee80211/ieee80211_crypt_tkip.ko] undefined!
ERROR: "phys_base" [fs/nfsd/nfsd.ko] undefined!
ERROR: "phys_base" [fs/nfs/nfs.ko] undefined!
ERROR: "phys_base" [fs/jbd2/jbd2.ko] undefined!
ERROR: "phys_base" [fs/ecryptfs/ecryptfs.ko] undefined!
ERROR: "phys_base" [drivers/net/ppp_mppe.ko] undefined!
ERROR: "phys_base" [drivers/char/agp/intel-agp.ko] undefined! make[1]: *** [__modpost] Error 1
Looks like a missing EXPORT_SYMBOL. Unfortunately, the definition is here:
arch/x86_64/kernel/head.S:ENTRY(phys_base)
Do I need to go the old symtabs.c route and stick the EXPORT_SYMBOL in some other .c file?
Quoted 11 lines · Andi Kleen
Already known, although it is still unclear what the bug actually is. Can you run with the appended patch please (from Eric Biederman) and post any backtraces the
WARN_ONin there spews out?Also do you use swiotlb?
Thanks
-Andi
Had to turn off modules to get it to build. It half-logged another
oops, but no backtraces, and SysRq+r does nothing. Nothing else unusual in the log.
May 9 00:47:12 bluesbreaker gconfd (ken-2833): Resolved address "xml:readonly:/etc/gnome/gconf/gconf.xml.defaults" to a read-only configuration source at position 2 May 9 00:52:59 bluesbreaker kernel: [ 275.667737] Unable to handle kernel paging request at ffff81003b4ac3e8 RIP: May 9 00:52:59 bluesbreaker kernel: [ 275.667742] [<ffffffff8027134a>] fasync_helper+0x52/0xf0 May 9 00:52:59 bluesbreaker kernel: [ 275.667749] PGD 8063 PUD 9063 PMD 800000003b4a11e3 BAD May 9 00:52:59 bluesbreaker kernel: [ 275.667754] Oops: 0009 [1] PREEMPT May 9 00:54:26 bluesbreaker syslogd 1.4.1: restart. May 9 00:54:26 bluesbreaker bootlog: Starting system log daemon...
[ OK ]
Apparently I do use swiotlb - I didn't know that, and can't see
where it gets asked in menuconfig, but I can see CONFIG_SWIOTLB=y
Let me know if there is anything else I can test (probably pm
tomorrow), otherwise I'll go back to -head.
Ken
Signature · 1 line
das eine Mal als Tragödie, das andere Mal als Farce
Quoted 8 lines · Ken Moffat
Quoted 7 lines · Andi Kleen
Already known, although it is still unclear what the bug actually is. Can you run with the appended patch please (from Eric Biederman) and post any backtraces the
WARN_ONin there spews out?Also do you use swiotlb?
Quoted 7 lines
Quoted 4 lines
Thanks
-Andi
Had to turn off modules to get it to build. It half-logged another
oops, but no backtraces, and SysRq+r does nothing. Nothing else unusual in the log.
Hmm, not good.
Quoted 14 lines
May 9 00:47:12 bluesbreaker gconfd (ken-2833): Resolved address "xml:readonly:/etc/gnome/gconf/gconf.xml.defaults" to a read-only configuration source at position 2 May 9 00:52:59 bluesbreaker kernel: [ 275.667737] Unable to handle kernel paging request at ffff81003b4ac3e8 RIP: May 9 00:52:59 bluesbreaker kernel: [ 275.667742] [<ffffffff8027134a>] fasync_helper+0x52/0xf0 May 9 00:52:59 bluesbreaker kernel: [ 275.667749] PGD 8063 PUD 9063 PMD 800000003b4a11e3 BAD May 9 00:52:59 bluesbreaker kernel: [ 275.667754] Oops: 0009 [1] PREEMPT May 9 00:54:26 bluesbreaker syslogd 1.4.1: restart. May 9 00:54:26 bluesbreaker bootlog: Starting system log daemon...
Quoted 8 lines
[ OK ]
Apparently I do use swiotlb - I didn't know that, and can't see
where it gets asked in menuconfig, but I can seeCONFIG_SWIOTLB=yLet me know if there is anything else I can test (probably pm
tomorrow), otherwise I'll go back to -head.
Yes testing head would be a good idea. It has a different bug fix from Linus that is supposed to address this too. Unfortunately it is still not known why it actually breaks; i had hoped to find that out using the debugging patch
-Andi