Re: Suspend bug

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

The following is the text from my e-mail that i have posted yesterday
regarding the similar issue. My laptop is equipped with AMD Dual Core
processor X2. Thought it might be relevant.
-
----------------------------------------------------------------------------------------------------------------
I grabbed the following from dmesg when i tried to "suspend" the laptop.
After booting the laptop, the first suspend was successful. The error
occurs during the second "suspend". System did not crash though, i mean
it was still functional except that the PM (power manager) throws a pop
up saying that the suspend was failed.

Running FC6 (2.6.19-1.2895.fc6 #1 SMP Wed Jan 10 18:50:56 EST 2007
x86_64 x86_64 x86_64 GNU/Linux).

Any ideas?

Thanks

Srikanth

Unable to handle kernel NULL pointer dereference at 0000000000000000 RIP:
 [<ffffffff802bf6ed>] __drain_pages+0x20/0x60
PGD 196ae067 PUD 259dd067 PMD 0
Oops: 0000 [1] SMP
last sysfs file: /power/state
CPU 0
Modules linked in: snd_rtctimer tun ipw2200 autofs4 ipv6
ip_conntrack_netbios_ns ipt_LOG ipt_REJECT xt_state ip_conntrack
nfnetlink xt_tcpudp iptable_filter ip_tables x_tables cpufreq_ondemand
dm_mirror dm_multipath dm_mod video sbs i2c_ec battery asus_acpi ac
parport_pc lp parport nvidia(P)(U) pcspkr sg shpchp i2c_nforce2
snd_hda_intel snd_hda_codec ieee80211 snd_seq_dummy i2c_core snd_seq_oss
snd_seq_midi_event snd_seq snd_seq_device sdhci snd_pcm_oss
ieee80211_crypt mmc_core snd_mixer_oss snd_pcm snd_timer r1000(U) snd
k8_edac r8169 edac_mc soundcore k8temp hwmon snd_page_alloc serio_raw
ide_cd cdrom sata_nv libata sd_mod scsi_mod ext3 jbd ehci_hcd ohci_hcd
uhci_hcd
Pid: 21867, comm: pm-suspend Tainted: P      2.6.19-1.2895.fc6 #1
RIP: 0010:[<ffffffff802bf6ed>]  [<ffffffff802bf6ed>] __drain_pages+0x20/0x60
RSP: 0018:ffff810028109dc8  EFLAGS: 00010046
RAX: 0000000000000001 RBX: 0000000000000046 RCX: ffff810001000000
RDX: ffff81000000b000 RSI: ffff81000000b768 RDI: ffff81000000b500
RBP: 0000000000000000 R08: ffff810028108000 R09: 0000000000000000
R10: ffff810002044be0 R11: ffffffff802f9d55 R12: ffff81000000ba00
R13: 0000000000000000 R14: 0000000000000001 R15: 00002aaaae1eb000
FS:  00002aaaaaadbdb0(0000) GS:ffffffff8064d000(0000) knlGS:00000000f7c466c0
CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 0000000000000000 CR3: 00000000351fc000 CR4: 00000000000006e0
Process pm-suspend (pid: 21867, threadinfo ffff810028108000, task
ffff8100319ce830)
Stack:  0000000000000001 0000000000000001 0000000000000007 ffff810026db7830
 0000000000000001 ffffffff802bf73f ffffffff80577810 ffffffff80265081
 0000000000000001 0000000000000001 0000000000000000 ffffffff802a18aa
Call Trace:
 [<ffffffff802bf73f>] page_alloc_cpu_notify+0x12/0x28
 [<ffffffff80265081>] notifier_call_chain+0x20/0x32
 [<ffffffff802a18aa>] _cpu_down+0x15b/0x217
 [<ffffffff802a1ba5>] disable_nonboot_cpus+0xa9/0x14c
 [<ffffffff802a78d5>] enter_state+0x8b/0x1a1
 [<ffffffff802a7a49>] state_store+0x5e/0x79
 [<ffffffff80300cb4>] sysfs_write_file+0xcb/0xff
 [<ffffffff80216582>] vfs_write+0xce/0x174
 [<ffffffff80216fb3>] sys_write+0x45/0x6e
 [<ffffffff8025c11e>] system_call+0x7e/0x83
 [<000000324f8bfc00>]

Code: 8b 75 00 48 8d 55 10 31 c9 4c 89 e7 e8 e4 fd ff ff c7 45 00
RIP  [<ffffffff802bf6ed>] __drain_pages+0x20/0x60
 RSP <ffff810028109dc8>
CR2: 0000000000000000
 <3>BUG: sleeping function called from invalid context at kernel/rwsem.c:20
in_atomic():0, irqs_disabled():1

Call Trace:
 [<ffffffff8026999a>] show_trace+0x34/0x47
 [<ffffffff802699bf>] dump_stack+0x12/0x17
 [<ffffffff8029e5fb>] down_read+0x15/0x23
 [<ffffffff8029661a>] blocking_notifier_call_chain+0x13/0x36
 [<ffffffff80215050>] do_exit+0x1f/0x8df
 [<ffffffff80264fe6>] do_page_fault+0x7a1/0x81c
 [<ffffffff8026307d>] error_exit+0x0/0x84
 [<ffffffff802bf6ed>] __drain_pages+0x20/0x60
 [<ffffffff802bf73f>] page_alloc_cpu_notify+0x12/0x28
 [<ffffffff80265081>] notifier_call_chain+0x20/0x32
 [<ffffffff802a18aa>] _cpu_down+0x15b/0x217
 [<ffffffff802a1ba5>] disable_nonboot_cpus+0xa9/0x14c
 [<ffffffff802a78d5>] enter_state+0x8b/0x1a1
 [<ffffffff802a7a49>] state_store+0x5e/0x79
 [<ffffffff80300cb4>] sysfs_write_file+0xcb/0xff
 [<ffffffff80216582>] vfs_write+0xce/0x174
 [<ffffffff80216fb3>] sys_write+0x45/0x6e
 [<ffffffff8025c11e>] system_call+0x7e/0x83
 [<000000324f8bfc00>]

ADDRCONF(NETDEV_UP): eth1: link is not ready
r8169: eth0: link down
ADDRCONF(NETDEV_UP): eth0: link is not ready
ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
eth1: no IPv6 routers present
eth1: no IPv6 routers present


Alan wrote:
>> the wall wart and assumed all was good.  Yesterday I found the laptop in 
>> some sort of "suspended" condition with the caps lock light blinking, 
>> other lights (power, touchpad, etc.) on but the system totally 
> 
> That's a kernel panic indicator
> 
> Do you have a sequence of actions that repeats the problem and causes it
> to occur again ?
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFwguq4QCEM551HXARAqfUAJ9fjrp6FUYJA7itGBm9E37Y57kPjgCeIIuJ
rg4ud5NPRR9Q/6tmoucWxyY=
=LzP9
-----END PGP SIGNATURE-----


[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux