swsusp2 i oops kernela po wybudzeniu

[Łukasz Maśko]

Dnia środa, 19 lipca 2006 10:40, Łukasz Maśko napisał:
[...]
> Zaraz ponownie uśpię sprzęta na dłuższy czas i zobaczę, czy sytuacja się
> powtórzy. Może wtedy uda się chociaż OOPSa zapisać, bo nawet nie wiem co
> go spowodowało. 

No to się powtórzyło, a oto OOPS z kernela:

BUG: unable to handle kernel NULL pointer dereference at virtual address 
00000000
 printing eip:
c015b504
*pde = 00000000
Oops: 0000 [#1]
PREEMPT
Modules linked in: hidp rfcomm wacom nvidia agpgart vmnet vmmon parport_pc 
parport ipv6 irtty_sir sir_dev arc4 ieee80211_crypt_wep nls_cp852 vfat fat 
nls_iso8859_2 ntfs sd_mod ircomm_tty ircomm irda crc_ccitt evdev video 
processor ac battery cpufreq_powersave cpufreq_ondemand cpufreq_stats 
p4_clockmod speedstep_lib freq_table usb_storage scsi_mod l2cap libusual 
hci_usb bluetooth pcmcia snd_pcm_oss snd_mixer_oss ohci1394 ieee1394 
i2c_sis96x ieee80211 ieee80211_crypt snd_intel8x0m firmware_class ohci_hcd 
yenta_socket rsrc_nonstatic pcmcia_core ehci_hcd usbcore sis900 mii 
snd_intel8x0 snd_ac97_codec snd_ac97_bus snd_pcm snd_timer snd soundcore 
snd_page_alloc shpchp pci_hotplug ide_cd cdrom lzf ext3 mbcache jbd 
ide_disk sis5513 ide_core
CPU:    0
EIP:    0060:[<c015b504>]    Tainted: P      VLI
EFLAGS: 00010202   (2.6.17.1_desktop-0.5 #1)
EIP is at put_page+0x4/0x40
eax: 00000000   ebx: 00000001   ecx: f70d8880   edx: 00000000
esi: ed792380   edi: f7453e04   ebp: 00000796   esp: f7453d94
ds: 007b   es: 007b   ss: 0068
Process syslog-ng (pid: 4794, threadinfo=f7452000 task=c1981030)
Stack: c028d670 00000000 ed792380 ed792380 c028d6a3 ed792380 00000000 
00000000
       c02fabd7 ed792380 f70d8800 0000003b c0454e48 dd6a000e ed792380 
eb5cfe54
       eb5cff30 00000001 00000000 ffffffa1 00000001 0000006a 00000000 
eb5cfe00
Call Trace:
 <c028d670> skb_release_data+0x80/0xa0  <c028d6a3> kfree_skbmem+0x13/0x90
 <c02fabd7> unix_stream_recvmsg+0x207/0x450  <c0288561> 
do_sock_read+0xd1/0xe0
 <c0288705> sock_aio_read+0x95/0xa0  <c0176701> do_sync_read+0xc1/0x110
 <c0132550> autoremove_wake_function+0x0/0x60  <c0181d97> 
sys_stat64+0x37/0x40
 <c01768ef> vfs_read+0x19f/0x1b0  <c0176c11> sys_read+0x51/0x80
 <c01030ab> sysenter_past_esp+0x54/0x75
Code: 75 05 58 c3 8d 76 00 8b 42 38 89 14 24 ff d0 eb f1 0f 0b 28 01 76 7f 
32 c0 eb dd 8d b6 00 00 00 00 8d bf 00 00 00 00 8b 54 24 04 <8b> 02 f6 c4 
40 75 26 8b 42 04 85 c0 74 15 ff 4a 04 0f 94 c0 84
EIP: [<c015b504>] put_page+0x4/0x40 SS:ESP 0068:f7453d94
BUG: scheduling while atomic: syslog-ng/0x00000001/4794
 <c02ffc2c> schedule+0x51c/0x530  <c0300f45> __down+0x85/0x100
 <c01197f0> default_wake_function+0x0/0x20  <c02ff6df> __down_failed+0x7/0xc
 <c023d84b> .text.lock.vesafb_thread+0x7f/0x94  <c023db05> 
vesafb_blank+0x135/0x170
 <c023386c> fb_blank+0x4c/0x80  <c022a790> fbcon_blank+0x140/0x250
 <c011de72> __call_console_drivers+0x62/0x70  <c011df80> 
call_console_drivers+0x70/0x140
 <c011e2f9> vprintk+0x1a9/0x2a0  <c021f3ec> do_unblank_screen+0x7c/0x150
 <c021f4cf> unblank_screen+0xf/0x20  <c0116e3d> bust_spinlocks+0x2d/0x60
 <c010449c> die+0x17c/0x240  <c01173e4> do_page_fault+0x2f4/0x660
 <c01170f0> do_page_fault+0x0/0x660  <c0103c43> error_code+0x4f/0x54
 <c01f007b> as_merged_requests+0x1b/0x180  <c015b504> put_page+0x4/0x40
 <c028d670> skb_release_data+0x80/0xa0  <c028d6a3> kfree_skbmem+0x13/0x90
 <c02fabd7> unix_stream_recvmsg+0x207/0x450  <c0288561> 
do_sock_read+0xd1/0xe0
 <c0288705> sock_aio_read+0x95/0xa0  <c0176701> do_sync_read+0xc1/0x110
 <c0132550> autoremove_wake_function+0x0/0x60  <c0181d97> 
sys_stat64+0x37/0x40
 <c01768ef> vfs_read+0x19f/0x1b0  <c0176c11> sys_read+0x51/0x80
 <c01030ab> sysenter_past_esp+0x54/0x75
BUG: scheduling while atomic: syslog-ng/0x00000001/4794
 <c02ffc2c> schedule+0x51c/0x530  <c0119917> __wake_up_locked+0x27/0x30
 <c02ffda8> wait_for_completion+0x78/0xd0  <c01197f0> 
default_wake_function+0x0/0x20
 <c01197f0> default_wake_function+0x0/0x20  <c023db20> 
vesafb_blank+0x150/0x170
 <c023386c> fb_blank+0x4c/0x80  <c022a790> fbcon_blank+0x140/0x250
 <c011de72> __call_console_drivers+0x62/0x70  <c011df80> 
call_console_drivers+0x70/0x140
 <c011e2f9> vprintk+0x1a9/0x2a0  <c021f3ec> do_unblank_screen+0x7c/0x150
 <c021f4cf> unblank_screen+0xf/0x20  <c0116e3d> bust_spinlocks+0x2d/0x60
 <c010449c> die+0x17c/0x240  <c01173e4> do_page_fault+0x2f4/0x660
 <c01170f0> do_page_fault+0x0/0x660  <c0103c43> error_code+0x4f/0x54
 <c01f007b> as_merged_requests+0x1b/0x180  <c015b504> put_page+0x4/0x40
 <c028d670> skb_release_data+0x80/0xa0  <c028d6a3> kfree_skbmem+0x13/0x90
 <c02fabd7> unix_stream_recvmsg+0x207/0x450  <c0288561> 
do_sock_read+0xd1/0xe0
 <c0288705> sock_aio_read+0x95/0xa0  <c0176701> do_sync_read+0xc1/0x110
 <c0132550> autoremove_wake_function+0x0/0x60  <c0181d97> 
sys_stat64+0x37/0x40
 <c01768ef> vfs_read+0x19f/0x1b0  <c0176c11> sys_read+0x51/0x80
 <c01030ab> sysenter_past_esp+0x54/0x75

Wygląda na to, że syslog-ng nie jest w stanie przeżyć uśpienia. Czy ktoś 
może to potwierdzić/zdementować? Bardzo proszę o pomoc. Podoba mi się ta 
funkcjonalność, ale jak ma mi się za każdym razem system wywracać po 
obudzeniu, to ja serdecznie dziękuję :-/
-- 
Łukasz Maśko                                           GG:   2441498    _o)
Lukasz.Masko(at)ipipan.waw.pl                         ICQ: 146553537    /\\
Registered Linux User #61028           JID: paranoid w jabber.aster.pl   _\_V