FS#33567 - [linux] 3.7.4-1 panics when my dell n5050 laptop goes to suspend or hibernate
Attached to Project:
Arch Linux
Opened by Safi ud Din Khan (safiuddinkhan) - Saturday, 26 January 2013, 08:09 GMT
Last edited by Tobias Powalowski (tpowa) - Monday, 04 February 2013, 07:25 GMT
Opened by Safi ud Din Khan (safiuddinkhan) - Saturday, 26 January 2013, 08:09 GMT
Last edited by Tobias Powalowski (tpowa) - Monday, 04 February 2013, 07:25 GMT
|
Details
Description:
I am using a Dell n5050 Laptop with intel core i3 processer . although i had problem before with suspend on resuming but hibernate function worked fine . but after i upgraded to kernel 3.7.4-1 neither hibernate nor suspend works . while using suspend before my system used to go to suspend fine while resume was not always successful but now when i start suspend screen goes blank while i could still see the LEDs of power and wifi running and no key reponse nor going to ssh works . sometimes the kernel straight forwardly goes to panic and i could see the caps lock light blinking on hibernate before upgrade it used to work fine but now same symptoms . downgrading to kernel 3.6.11-1 solves the problem . on kernel 3.7.4-1 i have tested everything removing all module which i think are causing the problem or trying to do suspend and hibernate without x running but nothing works . i have also tried pm_trace but it does not show anything in dmesg 
dmesg-t.txt
(52 KiB)
lsmod.txt
(4.1 KiB)
lspci.txt
(1.6 KiB)
lsusb.txt
(0.4 KiB)
dsdt.dat
(38.6 KiB)
|
This task depends upon
echo devices > /sys/power/pm_test
echo platform > /sys/power/disk
echo disk > /sys/power/state
"debug log_buf_len=10M print_fatal_signals=1 LOGLEVEL=8 earlyprintk=vga,keep no_console_suspend acpi_sleep=nonvs"
for that i was booting with these kernel parameters
"debug ignore_loglevel log_buf_len=10M print_fatal_signals=1 LOGLEVEL=8 earlyprintk=vga,keep sched_debug panic=30 pause_on_oops=5 rootwait oops=panic" while caputring the other videos
after "PM: Entering Mem Sleep" it says ehci_hcd something and then it stops at
sda stoping disk after that computer does not response and i had to hard restart it