Bug 13558

Summary: Tracelog during resume
Product: Power Management Reporter: Cijoml Cijomlovic Cijomlov (cijoml)
Component: Hibernation/SuspendAssignee: ykzhao (yakui.zhao)
Status: CLOSED INSUFFICIENT_DATA    
Severity: normal CC: akpm, lenb, rjw, rui.zhang, terry1, yakui.zhao
Priority: P1    
Hardware: All   
OS: Linux   
Kernel Version: 2.6.30 Subsystem:
Regression: Yes Bisected commit-id:
Bug Depends on:    
Bug Blocks: 7216, 13070    
Attachments: dmesg-2.6.30
save/restore the irq flags in course of hibernation

Description Cijoml Cijomlovic Cijomlov 2009-06-17 11:32:10 UTC 
Hi there,

there is a new bug in 2.6.30 kernel [regression] when resuming from suspend:

------------[ cut here ]------------
WARNING: at kernel/time/timekeeping.c:98 getnstimeofday+0x21/0xcc()
Hardware name: 259IA1
Modules linked in: rfcomm l2cap parport_pc lp parport michael_mic arc4 ecb cryptomgr aead pcompress crypto_blkcipher crypto_hash crypto_algapi lib80211_crypt_tkip sbp2 ide_cd_mod ide
_core btusb bluetooth dvb_usb_dib0700 dib7000p dib7000m mt2266 tuner_xc2028 mxl5007t xc5000 s5h1411 dvb_usb_dibusb_mc dvb_usb_dibusb_common dvb_pll mt2060 lgdt3305 dib0070 dib3000mc
dibx000_common dvb_usb dvb_core snd_intel8x0 snd_intel8x0m snd_ac97_codec ac97_bus snd_pcm_oss snd_mixer_oss ipw2200 libipw ohci1394 ieee1394 snd_seq_oss snd_seq_midi_event lib80211
pcspkr 8139too snd_pcm video mii firewire_ohci firewire_core output snd_seq snd_timer snd_seq_device snd 8250_pci snd_page_alloc i2c_i801 iTCO_wdt 8250 serial_core uhci_hcd ehci_hcd
sg
Pid: 15611, comm: powerbtn.sh Not tainted 2.6.30 #1
Call Trace:
 [<c011ab6a>] ? warn_slowpath_common+0x41/0x71
 [<c011ab87>] ? warn_slowpath_common+0x5e/0x71
 [<c011aba4>] ? warn_slowpath_null+0xa/0xc
 [<c012f55e>] ? getnstimeofday+0x21/0xcc
 [<c012c5b0>] ? ktime_get_ts+0x1d/0x3f
 [<c012c5dc>] ? ktime_get+0xa/0x19
 [<c01184e6>] ? try_to_wake_up+0xe1/0xeb
 [<c01326e2>] ? tick_handle_oneshot_broadcast+0x2c/0xa9
 [<c0104573>] ? timer_interrupt+0x3f/0x48
 [<c014553e>] ? handle_IRQ_event+0x1a/0x90
 [<c014657a>] ? handle_level_irq+0x6b/0xcb
 [<c0104214>] ? handle_irq+0x38/0x44
 [<c0103edf>] ? do_IRQ+0x2b/0x63
 [<c0102ee9>] ? common_interrupt+0x29/0x30
 [<c0110000>] ? ack_apic_level+0x3d/0x93
 [<c010ea7f>] ? lapic_resume+0x166/0x16f
 [<c02a0a54>] ? __sysdev_resume+0x11/0x34
 [<c02a0ccc>] ? sysdev_resume+0x17/0x4b
 [<c013a063>] ? hibernation_snapshot+0xe6/0x1a3
 [<c013952d>] ? freeze_processes+0x7a/0x81
 [<c0139a99>] ? prepare_processes+0x5/0x18
 [<c013a1b5>] ? hibernate+0x95/0x130
 [<c0139027>] ? state_store+0x41/0xa1
 [<c0138fe6>] ? state_store+0x0/0xa1
 [<c0215792>] ? kobj_attr_store+0x18/0x1c
 [<c019f7f0>] ? sysfs_write_file+0xa4/0xd8
 [<c019f74c>] ? sysfs_write_file+0x0/0xd8
 [<c016848a>] ? vfs_write+0x73/0xa1
 [<c016854d>] ? sys_write+0x3c/0x60
 [<c0102931>] ? syscall_call+0x7/0xb
---[ end trace d7516dd88b9e957c ]---
Comment 1 Rafael J. Wysocki 2009-06-17 12:22:06 UTC 
The bug is being worked on.
Comment 2 ykzhao 2009-07-13 03:32:09 UTC 
*** Bug 13578 has been marked as a duplicate of this bug. ***
Comment 3 ykzhao 2009-07-13 05:21:53 UTC 
Hi, Cijoml
    Will you please attach the output of dmesg after the system is resumed from hibernation?
    From the log it seems that the interrupt is enabled while calling the function of sysdev_resume.
    Maybe the irq is already enabled while the system is resumed from the hibernation swap partition.
    Thanks.
Comment 4 Cijoml Cijomlovic Cijomlov 2009-07-14 05:38:27 UTC 
Created attachment 22336 [details]
dmesg-2.6.30

There is also tracelog during suspend, but it is so quick, that I can't catch it and after resume it is not in dmesg.
Comment 5 ykzhao 2009-07-21 08:11:43 UTC 
Created attachment 22424 [details]
save/restore the irq flags in course of hibernation
Comment 6 ykzhao 2009-07-21 08:12:50 UTC 
Hi, Cijoml
    Will you please try the debug patch and see whether the issue still exists in course of resume from hibernation?
    Thanks.
Comment 7 ykzhao 2009-09-11 02:48:14 UTC 
Since there is no response for more than one month, the bug will be rejected.

If the problem still exists, please try the debug patch in comment #5 and attach the output of dmesg.

Thanks.
Comment 8 Cijoml Cijomlovic Cijomlov 2009-09-11 16:31:35 UTC 
Hi there Problem is still in 2.6.30.5. I will attach dmesg log soon. Sorry for not replying for a long time!
Comment 9 Zhang Rui 2009-12-28 08:18:02 UTC 
please re-open it and attach the test result if the problem still exists in 2.6.32.