Bug#774036: linux-image-3.16.0-4-amd64: Untainted Kernel shows similar issue
Hi Emil, Am Samstag 07 März 2015, 14:26:17 schrieb Emil Goode: Just to clarify, suspend/resume is working but it takes more than 60 sec for suspend to complete? yes, suspend/resume is working. I did three cycles and measured the time for suspend: The first suspend took approx. 60 seconds, the second and third approx. 30 seconds. Kind regards, Rainer -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#774036: linux-image-3.16.0-4-amd64: Untainted Kernel shows similar issue
Hello Rainer,
On Sat, Mar 07, 2015 at 06:47:31PM +0100, Rainer Dorsch wrote:
Hi Emil,
Am Samstag 07 März 2015, 14:26:17 schrieb Emil Goode:
Just to clarify, suspend/resume is working but it takes more than 60 sec for
suspend to complete?
yes, suspend/resume is working. I did three cycles and measured the time for
suspend:
The first suspend took approx. 60 seconds, the second and third approx. 30
seconds.
I see, it looks like its an issue with the ATA subsystem that is stalling
the suspend process.
[ 181.992086] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[ 181.992090] ata3.00: failed command: FLUSH CACHE
[ 181.992098] ata3.00: cmd e7/00:00:00:00:00/00:00:00:00:00/a0 tag 16
res 40/00:c8:30:0e:40/84:00:09:00:00/40 Emask 0x4 (timeout)
[ 181.992100] ata3.00: status: { DRDY }
[ 181.992106] ata3: hard resetting link
[ 181.992108] ata3: nv: skipping hardreset on occupied port
[ 182.460049] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 182.476330] ata3.00: configured for UDMA/133
[ 182.476333] ata3.00: retrying FLUSH 0xe7 Emask 0x4
[ 182.476963] ata3: EH complete
[ 182.477033] ata3.00: Enabling discard_zeroes_data
[ 182.477598] sd 2:0:0:0: [sda] Stopping disk
[ 182.736087] PM: suspend of devices complete after 61889.003 msecs
Since it is a regression what you could do is use git bisect to try and locate
the commit that introduced the issue. But its time consuming and it doesn't
always work.
Other than that I think you should post a bug in the kernel bugzilla.
Best regards,
Emil
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#774036: Re: Bug#774036: linux-image-3.16.0-4-amd64: Untainted Kernel shows similar issue
Hello Rainer, On Thu, Mar 05, 2015 at 10:09:04PM +0100, Rainer Dorsch wrote: Hi Emil, sorry for the long silence, but I did not have physical access to the machine for which I reported the bug and I did not want to install new kernel from remote... I recompiled a recent kernel with PM_TRACE_RTC enabled, but still get no log data in pm-suspend.log: root@Silberkiste:~# uname -a Linux Silberkiste 4.0.0-rc2+ #1 SMP Thu Mar 5 01:01:25 CET 2015 x86_64 GNU/Linux So the issue has not been resolved in the 4.0-rc2 kernel? root@Silberkiste:~# grep PM_TRACE_RTC /boot/config-4.0.0-rc2+ CONFIG_PM_TRACE_RTC=y root@Silberkiste:~# head -4 /usr/lib/pm-utils/pm-functions #!/bin/sh # vim:noexpandtab export PM_DEBUG=true root@Silberkiste:~# cat /var/log/pm-suspend.log root@Silberkiste:~# ls -l /var/log/pm-suspend.log -rw-r--r-- 1 root root 0 Jan 3 15:52 /var/log/pm-suspend.log root@Silberkiste:~# I did 501 echo 1 /sys/power/pm_trace 502 echo mem /sys/power/state but this did not create any logs. Do you have any suggestions, what I might do wrong? Sorry, the /var/log/pm-suspend.log is used by the pm-suspend script. Try suspending with pm-suspend and post the log. Then run the following and post the dmesg output after resuming. echo 1 /sys/power/pm_trace echo mem /sys/power/state Also did you try to suspend after blacklisting the wifi modules? I can take a look at it but note that it may require more skilled upstream people to resolve this issue. Best regards, Emil Goode Thanks, Rainer On Sunday 04 January 2015 18:12:44 Emil Goode wrote: Hello Rainer, On Sat, Jan 03, 2015 at 04:23:44PM +0100, Rainer Dorsch wrote: Hi Emil, I have only remote access to the system for the next few weeks and I feel somewhat uncomfortable to experiment with my self-compiled kernels on the system or changing networking configurations. So please apologize that I may need 3-4 weeks to test that. I assume you suggest to follow http://kernel-handbook.alioth.debian.org/ch-common-tasks.html to enable PM_TRACE_RTC and rebuild the kernel, correct? Yes and you can clone this tree for testing upstream kernels. git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git Best regards, Emil Goode On Tuesday 30 December 2014 12:40:53 Emil Goode wrote: Hello Rainer, On Tue, Dec 30, 2014 at 12:15:31AM +0100, Rainer Dorsch wrote: Hi Emil, Am Montag 29 Dezember 2014, 14:02:55 schrieb Emil Goode: Hello Rainer, The below procedure would give more information: Add the following line to the top of the file /usr/lib/pm-utils/pm-functions. export PM_DEBUG=true Then suspend with: echo 1 /sys/power/pm_trace echo mem /sys/power/state HmmI do not have a pm_trace Ok, that is because PM_TRACE_RTC needs to be enabled in the kernel config. Please be aware that when using pm_trace it will mess with your machine's real-time clock. There is a similar bug report already for an older kernel, but that seems to be fixed (?) https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=638264 The iwlagn module is for intel wireless and I believe you are using broadcom. Post dmesg and the contents of /var/log/pm-suspend.log. Have you tried disabling the mac80211 module? Can you tell how I unload a module for suspend or if http://superuser.com/questions/620201/how-to-force-ubuntu-debian-mint- to-u nload-modules-at-suspend-to-disk also applies to systemd? I think you can temporarily blacklist modules as described here: https://wiki.debian.org/KernelModuleBlacklisting I would also try the latest upstream kernel, this might have been fixed. Best regards, Emil Goode -- Rainer Dorsch http://bokomoko.de/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#774036: Re: Bug#774036: linux-image-3.16.0-4-amd64: Untainted Kernel shows similar issue
Hi Emil, sorry for the long silence, but I did not have physical access to the machine for which I reported the bug and I did not want to install new kernel from remote... I recompiled a recent kernel with PM_TRACE_RTC enabled, but still get no log data in pm-suspend.log: root@Silberkiste:~# uname -a Linux Silberkiste 4.0.0-rc2+ #1 SMP Thu Mar 5 01:01:25 CET 2015 x86_64 GNU/Linux root@Silberkiste:~# grep PM_TRACE_RTC /boot/config-4.0.0-rc2+ CONFIG_PM_TRACE_RTC=y root@Silberkiste:~# head -4 /usr/lib/pm-utils/pm-functions #!/bin/sh # vim:noexpandtab export PM_DEBUG=true root@Silberkiste:~# cat /var/log/pm-suspend.log root@Silberkiste:~# ls -l /var/log/pm-suspend.log -rw-r--r-- 1 root root 0 Jan 3 15:52 /var/log/pm-suspend.log root@Silberkiste:~# I did 501 echo 1 /sys/power/pm_trace 502 echo mem /sys/power/state but this did not create any logs. Do you have any suggestions, what I might do wrong? Thanks, Rainer On Sunday 04 January 2015 18:12:44 Emil Goode wrote: Hello Rainer, On Sat, Jan 03, 2015 at 04:23:44PM +0100, Rainer Dorsch wrote: Hi Emil, I have only remote access to the system for the next few weeks and I feel somewhat uncomfortable to experiment with my self-compiled kernels on the system or changing networking configurations. So please apologize that I may need 3-4 weeks to test that. I assume you suggest to follow http://kernel-handbook.alioth.debian.org/ch-common-tasks.html to enable PM_TRACE_RTC and rebuild the kernel, correct? Yes and you can clone this tree for testing upstream kernels. git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git Best regards, Emil Goode On Tuesday 30 December 2014 12:40:53 Emil Goode wrote: Hello Rainer, On Tue, Dec 30, 2014 at 12:15:31AM +0100, Rainer Dorsch wrote: Hi Emil, Am Montag 29 Dezember 2014, 14:02:55 schrieb Emil Goode: Hello Rainer, The below procedure would give more information: Add the following line to the top of the file /usr/lib/pm-utils/pm-functions. export PM_DEBUG=true Then suspend with: echo 1 /sys/power/pm_trace echo mem /sys/power/state HmmI do not have a pm_trace Ok, that is because PM_TRACE_RTC needs to be enabled in the kernel config. Please be aware that when using pm_trace it will mess with your machine's real-time clock. There is a similar bug report already for an older kernel, but that seems to be fixed (?) https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=638264 The iwlagn module is for intel wireless and I believe you are using broadcom. Post dmesg and the contents of /var/log/pm-suspend.log. Have you tried disabling the mac80211 module? Can you tell how I unload a module for suspend or if http://superuser.com/questions/620201/how-to-force-ubuntu-debian-mint- to-u nload-modules-at-suspend-to-disk also applies to systemd? I think you can temporarily blacklist modules as described here: https://wiki.debian.org/KernelModuleBlacklisting I would also try the latest upstream kernel, this might have been fixed. Best regards, Emil Goode -- Rainer Dorsch http://bokomoko.de/
Bug#774036: Re: Bug#774036: linux-image-3.16.0-4-amd64: Untainted Kernel shows similar issue
Hello Rainer, On Sat, Jan 03, 2015 at 04:23:44PM +0100, Rainer Dorsch wrote: Hi Emil, I have only remote access to the system for the next few weeks and I feel somewhat uncomfortable to experiment with my self-compiled kernels on the system or changing networking configurations. So please apologize that I may need 3-4 weeks to test that. I assume you suggest to follow http://kernel-handbook.alioth.debian.org/ch-common-tasks.html to enable PM_TRACE_RTC and rebuild the kernel, correct? Yes and you can clone this tree for testing upstream kernels. git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git Best regards, Emil Goode On Tuesday 30 December 2014 12:40:53 Emil Goode wrote: Hello Rainer, On Tue, Dec 30, 2014 at 12:15:31AM +0100, Rainer Dorsch wrote: Hi Emil, Am Montag 29 Dezember 2014, 14:02:55 schrieb Emil Goode: Hello Rainer, The below procedure would give more information: Add the following line to the top of the file /usr/lib/pm-utils/pm-functions. export PM_DEBUG=true Then suspend with: echo 1 /sys/power/pm_trace echo mem /sys/power/state HmmI do not have a pm_trace Ok, that is because PM_TRACE_RTC needs to be enabled in the kernel config. Please be aware that when using pm_trace it will mess with your machine's real-time clock. There is a similar bug report already for an older kernel, but that seems to be fixed (?) https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=638264 The iwlagn module is for intel wireless and I believe you are using broadcom. Post dmesg and the contents of /var/log/pm-suspend.log. Have you tried disabling the mac80211 module? Can you tell how I unload a module for suspend or if http://superuser.com/questions/620201/how-to-force-ubuntu-debian-mint-to-u nload-modules-at-suspend-to-disk also applies to systemd? I think you can temporarily blacklist modules as described here: https://wiki.debian.org/KernelModuleBlacklisting I would also try the latest upstream kernel, this might have been fixed. Best regards, Emil Goode -- Rainer Dorsch http://bokomoko.de/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#774036: Re: Bug#774036: linux-image-3.16.0-4-amd64: Untainted Kernel shows similar issue
Hi Emil, I have only remote access to the system for the next few weeks and I feel somewhat uncomfortable to experiment with my self-compiled kernels on the system or changing networking configurations. So please apologize that I may need 3-4 weeks to test that. I assume you suggest to follow http://kernel-handbook.alioth.debian.org/ch-common-tasks.html to enable PM_TRACE_RTC and rebuild the kernel, correct? Kind regards, Rainer On Tuesday 30 December 2014 12:40:53 Emil Goode wrote: Hello Rainer, On Tue, Dec 30, 2014 at 12:15:31AM +0100, Rainer Dorsch wrote: Hi Emil, Am Montag 29 Dezember 2014, 14:02:55 schrieb Emil Goode: Hello Rainer, The below procedure would give more information: Add the following line to the top of the file /usr/lib/pm-utils/pm-functions. export PM_DEBUG=true Then suspend with: echo 1 /sys/power/pm_trace echo mem /sys/power/state HmmI do not have a pm_trace Ok, that is because PM_TRACE_RTC needs to be enabled in the kernel config. Please be aware that when using pm_trace it will mess with your machine's real-time clock. There is a similar bug report already for an older kernel, but that seems to be fixed (?) https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=638264 The iwlagn module is for intel wireless and I believe you are using broadcom. Post dmesg and the contents of /var/log/pm-suspend.log. Have you tried disabling the mac80211 module? Can you tell how I unload a module for suspend or if http://superuser.com/questions/620201/how-to-force-ubuntu-debian-mint-to-u nload-modules-at-suspend-to-disk also applies to systemd? I think you can temporarily blacklist modules as described here: https://wiki.debian.org/KernelModuleBlacklisting I would also try the latest upstream kernel, this might have been fixed. Best regards, Emil Goode -- Rainer Dorsch http://bokomoko.de/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#774036: Re: Bug#774036: linux-image-3.16.0-4-amd64: Untainted Kernel shows similar issue
Hello Rainer, On Tue, Dec 30, 2014 at 12:15:31AM +0100, Rainer Dorsch wrote: Hi Emil, Am Montag 29 Dezember 2014, 14:02:55 schrieb Emil Goode: Hello Rainer, The below procedure would give more information: Add the following line to the top of the file /usr/lib/pm-utils/pm-functions. export PM_DEBUG=true Then suspend with: echo 1 /sys/power/pm_trace echo mem /sys/power/state HmmI do not have a pm_trace Ok, that is because PM_TRACE_RTC needs to be enabled in the kernel config. Please be aware that when using pm_trace it will mess with your machine's real-time clock. There is a similar bug report already for an older kernel, but that seems to be fixed (?) https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=638264 The iwlagn module is for intel wireless and I believe you are using broadcom. Post dmesg and the contents of /var/log/pm-suspend.log. Have you tried disabling the mac80211 module? Can you tell how I unload a module for suspend or if http://superuser.com/questions/620201/how-to-force-ubuntu-debian-mint-to-unload-modules-at-suspend-to-disk also applies to systemd? I think you can temporarily blacklist modules as described here: https://wiki.debian.org/KernelModuleBlacklisting I would also try the latest upstream kernel, this might have been fixed. Best regards, Emil Goode -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#774036: linux-image-3.16.0-4-amd64: Untainted Kernel shows similar issue
Hello Rainer, The below procedure would give more information: Add the following line to the top of the file /usr/lib/pm-utils/pm-functions. export PM_DEBUG=true Then suspend with: echo 1 /sys/power/pm_trace echo mem /sys/power/state Post dmesg and the contents of /var/log/pm-suspend.log. Have you tried disabling the mac80211 module? Best regards, Emil Goode -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#774036: Re: Bug#774036: linux-image-3.16.0-4-amd64: Untainted Kernel shows similar issue
Hi Emil, Am Montag 29 Dezember 2014, 14:02:55 schrieb Emil Goode: Hello Rainer, The below procedure would give more information: Add the following line to the top of the file /usr/lib/pm-utils/pm-functions. export PM_DEBUG=true Then suspend with: echo 1 /sys/power/pm_trace echo mem /sys/power/state HmmI do not have a pm_trace root@Silberkiste:~# ls -l /sys/power/ insgesamt 0 -rw-r--r-- 1 root root 4096 Dez 29 23:19 disk -rw-r--r-- 1 root root 4096 Dez 30 00:04 image_size -rw-r--r-- 1 root root 4096 Dez 30 00:04 pm_async -rw-r--r-- 1 root root 4096 Dez 30 00:04 pm_freeze_timeout -rw-r--r-- 1 root root 4096 Dez 30 00:04 pm_print_times -rw-r--r-- 1 root root 4096 Dez 30 00:04 pm_test -rw-r--r-- 1 root root 4096 Dez 30 00:04 reserved_size -rw-r--r-- 1 root root 4096 Dez 29 23:19 resume -rw-r--r-- 1 root root 4096 Dez 29 23:19 state -rw-r--r-- 1 root root 4096 Dez 30 00:04 wakeup_count root@Silberkiste:~# There is a similar bug report already for an older kernel, but that seems to be fixed (?) https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=638264 Post dmesg and the contents of /var/log/pm-suspend.log. Have you tried disabling the mac80211 module? Can you tell how I unload a module for suspend or if http://superuser.com/questions/620201/how-to-force-ubuntu-debian-mint-to-unload-modules-at-suspend-to-disk also applies to systemd? Thanks, Rainer -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#774036: linux-image-3.16.0-4-amd64: Untainted Kernel shows similar issue
Package: src:linux Version: 3.16.7-ckt2-1 Followup-For: Bug #774036 Dear Ben, many thanks for the superfast response and thanks for pointing out that I was running the nvidia driver. I run now with nouveau and also purge the virtualbox stuff. Unfortunately, the behavior is exactly the same though (except that there is no blinking cursor with nouveau, when the system hangs), i.e. the resume works when I use freezer in debug mode, the system hangs when I go to the next level (devices). rd@Silberkiste:/etc/default$ cat /sys/power/pm_test [none] core processors platform devices freezer rd@Silberkiste:/etc/default$ Please let me know, if there is anything more I could provide. Thanks Rainer -- Package-specific info: ** Version: Linux version 3.16.0-4-amd64 (debian-ker...@lists.debian.org) (gcc version 4.8.3 (Debian 4.8.3-16) ) #1 SMP Debian 3.16.7-ckt2-1 (2014-12-08) ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.16.0-4-amd64 root=UUID=d47ae970-51f3-48d3-b19d-edd7413e080f ro quiet elevator=noop rootflags=noatime,discard,data=ordered,errors=remount-ro acpi_sleep=old_ordering ** Not tainted ** Kernel log: [ 33.205263] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [ 33.205265] sd 4:0:0:0: [sda] [ 33.205267] Sense Key : Aborted Command [current] [descriptor] [ 33.205270] Descriptor sense data with sense descriptors (in hex): [ 33.205272] 72 0b 47 00 00 00 00 0c 00 0a 80 00 00 00 00 00 [ 33.205282] 07 80 0b 58 [ 33.205287] sd 4:0:0:0: [sda] [ 33.205290] Add. Sense: Scsi parity error [ 33.205293] sd 4:0:0:0: [sda] CDB: [ 33.205294] Read(10): 28 00 07 80 0b e8 00 00 08 00 [ 33.205306] sd 4:0:0:0: [sda] [ 33.205308] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [ 33.205310] sd 4:0:0:0: [sda] [ 33.205312] Sense Key : Aborted Command [current] [descriptor] [ 33.205315] Descriptor sense data with sense descriptors (in hex): [ 33.205317] 72 0b 47 00 00 00 00 0c 00 0a 80 00 00 00 00 00 [ 33.205327] 07 80 0b 58 [ 33.205332] sd 4:0:0:0: [sda] [ 33.205335] Add. Sense: Scsi parity error [ 33.205338] sd 4:0:0:0: [sda] CDB: [ 33.205339] Read(10): 28 00 07 80 0b f0 00 00 08 00 [ 33.205351] sd 4:0:0:0: [sda] [ 33.205353] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [ 33.205355] sd 4:0:0:0: [sda] [ 33.205357] Sense Key : Aborted Command [current] [descriptor] [ 33.205360] Descriptor sense data with sense descriptors (in hex): [ 33.205362] 72 0b 47 00 00 00 00 0c 00 0a 80 00 00 00 00 00 [ 33.205372] 07 80 0b 58 [ 33.205377] sd 4:0:0:0: [sda] [ 33.205380] Add. Sense: Scsi parity error [ 33.205383] sd 4:0:0:0: [sda] CDB: [ 33.205385] Read(10): 28 00 07 80 0b f8 00 00 08 00 [ 33.205408] sd 4:0:0:0: [sda] [ 33.205411] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [ 33.205414] sd 4:0:0:0: [sda] [ 33.205415] Sense Key : Aborted Command [current] [descriptor] [ 33.205419] Descriptor sense data with sense descriptors (in hex): [ 33.205421] 72 0b 47 00 00 00 00 0c 00 0a 80 00 00 00 00 00 [ 33.205431] 07 80 0b 58 [ 33.205436] sd 4:0:0:0: [sda] [ 33.205438] Add. Sense: Scsi parity error [ 33.205441] sd 4:0:0:0: [sda] CDB: [ 33.205443] Read(10): 28 00 07 80 0b 38 00 00 08 00 [ 33.205456] sd 4:0:0:0: [sda] [ 33.205459] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [ 33.205461] sd 4:0:0:0: [sda] [ 33.205463] Sense Key : Aborted Command [current] [descriptor] [ 33.205466] Descriptor sense data with sense descriptors (in hex): [ 33.205468] 72 0b 47 00 00 00 00 0c 00 0a 80 00 00 00 00 00 [ 33.205478] 07 80 0b 58 [ 33.205483] sd 4:0:0:0: [sda] [ 33.205486] Add. Sense: Scsi parity error [ 33.205489] sd 4:0:0:0: [sda] CDB: [ 33.205490] Read(10): 28 00 07 80 0b 40 00 00 08 00 [ 33.205502] sd 4:0:0:0: [sda] [ 33.205504] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [ 33.205507] sd 4:0:0:0: [sda] [ 33.205509] Sense Key : Aborted Command [current] [descriptor] [ 33.205512] Descriptor sense data with sense descriptors (in hex): [ 33.205514] 72 0b 47 00 00 00 00 0c 00 0a 80 00 00 00 00 00 [ 33.205524] 07 80 0b 58 [ 33.205529] sd 4:0:0:0: [sda] [ 33.205532] Add. Sense: Scsi parity error [ 33.205535] sd 4:0:0:0: [sda] CDB: [ 33.205536] Read(10): 28 00 07 80 0b 48 00 00 08 00 [ 33.205549] sd 4:0:0:0: [sda] [ 33.205551] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [ 33.205554] sd 4:0:0:0: [sda] [ 33.20] Sense Key : Aborted Command [current] [descriptor] [ 33.205558] Descriptor sense data with sense descriptors (in hex): [ 33.205560] 72 0b 47 00 00 00 00 0c 00 0a 80 00 00 00 00 00 [ 33.205571] 07 80 0b 58 [ 33.205575] sd 4:0:0:0: [sda] [ 33.205578] Add. Sense: Scsi parity error [ 33.205581] sd 4:0:0:0: [sda] CDB: [ 33.205583] Read(10): 28 00 07 80 0b 50 00 00 08 00 [ 33.205596] sd 4:0:0:0: [sda] [
Bug#774036: linux-image-3.16.0-4-amd64: Untainted Kernel shows similar issue
Hello, On Sun, Dec 28, 2014 at 11:15:21AM +0100, Rainer Dorsch wrote: Package: src:linux Version: 3.16.7-ckt2-1 Followup-For: Bug #774036 Dear Ben, many thanks for the superfast response and thanks for pointing out that I was running the nvidia driver. I run now with nouveau and also purge the virtualbox stuff. Unfortunately, the behavior is exactly the same though (except that there is no blinking cursor with nouveau, when the system hangs), i.e. the resume works when I use freezer in debug mode, the system hangs when I go to the next level (devices). When you get a black screen does the system hang completely or is it possible to login to the system over ssh? If it's possible to login it could be useful to post the dmesg output here. Best regards, Emil Goode -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#774036: linux-image-3.16.0-4-amd64: Untainted Kernel shows similar issue
Hi Emil, Am Sonntag, 28. Dezember 2014, 15:56:28 schrieb Emil Goode: Hello, On Sun, Dec 28, 2014 at 11:15:21AM +0100, Rainer Dorsch wrote: Package: src:linux Version: 3.16.7-ckt2-1 Followup-For: Bug #774036 Dear Ben, many thanks for the superfast response and thanks for pointing out that I was running the nvidia driver. I run now with nouveau and also purge the virtualbox stuff. Unfortunately, the behavior is exactly the same though (except that there is no blinking cursor with nouveau, when the system hangs), i.e. the resume works when I use freezer in debug mode, the system hangs when I go to the next level (devices). When you get a black screen does the system hang completely or is it possible to login to the system over ssh? If it's possible to login it could be useful to post the dmesg output here. Thank you for the idea, I tried it, but the system does not respond anymore to an ssh request. It certainly works when the system is up. Kind regards, Rainer -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#774036: linux-image-3.16.0-4-amd64: Untainted Kernel shows similar issue
Hi Emil, thanks again for our response. I have additional information, the behavior is not a hang, but the system simply needs around additional 30s to really power off. I copied the dmesg output form dmesg dmesg_before; echo mem /sys/power/state; dmesg dmesg_after into http://bokomoko.de/~rd/Debian/774036/ I do not recall this behavior with the 3.2.x kernel in wheezy, but that makes it really into a very minor issue. Rainer Am Sonntag, 28. Dezember 2014, 15:56:28 schrieb Emil Goode: Hello, On Sun, Dec 28, 2014 at 11:15:21AM +0100, Rainer Dorsch wrote: Package: src:linux Version: 3.16.7-ckt2-1 Followup-For: Bug #774036 Dear Ben, many thanks for the superfast response and thanks for pointing out that I was running the nvidia driver. I run now with nouveau and also purge the virtualbox stuff. Unfortunately, the behavior is exactly the same though (except that there is no blinking cursor with nouveau, when the system hangs), i.e. the resume works when I use freezer in debug mode, the system hangs when I go to the next level (devices). When you get a black screen does the system hang completely or is it possible to login to the system over ssh? If it's possible to login it could be useful to post the dmesg output here. Best regards, Emil Goode -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
