Csaba Toth, thank you for reporting this and helping make Ubuntu better. Maverick reached EOL on April 10, 2012. Please see this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases
We were wondering if this is still an issue in a supported release? If so, could you please provide the information following https://wiki.ubuntu.com/DebuggingKernelSuspendHibernateResume ? As well, can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ . However, note you can only test Suspend, not Hibernate, when using a LiveCD. If the issue remains, run the following command in the development release from a Terminal (Applications->Accessories->Terminal) as it will automatically gather and attach updated debug information to this report. apport-collect -p linux <BUGNUMBER> Additionally, if you could try to reproduce this with the upstream mainline kernel that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs- upstream-testing' text. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'. Please let us know your results. Thanks in advance. ** Description changed: - The following laptop HDD is used in IBM and Apple laptops also besides Fujitsu Siemens laptops. - It was placed onto a blacklist with the 2.6.24-5.8 kernels. See Launchpad Bug 175834. Then for some reason (I don't have deep enough knowledge about that) it was removed from the balcklist with 2.6.34 and upcoming kernels (http://old.nabble.com/Re%3A-ata%3A-blacklist-FUJITSU-MHW2160BH-PL-td28469895.html). I think either the blacklist removal was a bad idea, or just my laptop HDD is bad. But with the Ubuntu 10.10 I use 2.6.34 (and currently 2.6.35) kernels not so long ago. Sometimes after wake-up from suspend, the system becomes very unresponsive (no X, even no character terminal these times sometimes), but I managed to get to the console, and I saw endless messages of I/O errors (copied by hand from the latest batch later). Obviously the machine was busy handling the IRQ related to the faulty reads, and was hogged by that. I couldn't find these error messages in the kernel logs, I guess the read error made the logging impossible (I have one big partition besides the cache partition, but anyways I have only 1 HDD). + With the Ubuntu 10.10 I use 2.6.34 sometimes after wake-up from suspend, + the system becomes very unresponsive (no X, even no character terminal + these times sometimes), but I managed to get to the console, and I saw + endless messages of I/O errors (copied by hand from the latest batch + later). Obviously the machine was busy handling the IRQ related to the + faulty reads, and was hogged by that. I couldn't find these error + messages in the kernel logs, I guess the read error made the logging + impossible (I have one big partition besides the cache partition, but + anyways I have only 1 HDD). Using GSmartControl, peeking into the HDD's error logs, we can see: "Error 324 occurred at disk power-on lifetime: 16485 hours (686 days + 21 hours) - When the command that caused the error occurred, the device was active or idle. + When the command that caused the error occurred, the device was active or idle. - After command completion occurred, registers were: - ER ST SC SN CL CH DH - -- -- -- -- -- -- -- - 40 41 03 f0 70 cd 40 + After command completion occurred, registers were: + ER ST SC SN CL CH DH + -- -- -- -- -- -- -- + 40 41 03 f0 70 cd 40 - Commands leading to the command that caused the error were: - CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name - -- -- -- -- -- -- -- -- ---------------- -------------------- - 60 08 00 f0 70 cd 40 00 00:20:45.286 READ FPDMA QUEUED - ef 10 02 00 00 00 a0 00 00:20:45.285 SET FEATURES [Reserved for Serial ATA] - 27 00 00 00 00 00 e0 00 00:20:45.285 READ NATIVE MAX ADDRESS EXT - ec 00 00 00 00 00 a0 00 00:20:45.284 IDENTIFY DEVICE - ef 03 45 00 00 00 a0 00 00:20:45.284 SET FEATURES [Set transfer mode]" + Commands leading to the command that caused the error were: + CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name + -- -- -- -- -- -- -- -- ---------------- -------------------- + 60 08 00 f0 70 cd 40 00 00:20:45.286 READ FPDMA QUEUED + ef 10 02 00 00 00 a0 00 00:20:45.285 SET FEATURES [Reserved for Serial ATA] + 27 00 00 00 00 00 e0 00 00:20:45.285 READ NATIVE MAX ADDRESS EXT + ec 00 00 00 00 00 a0 00 00:20:45.284 IDENTIFY DEVICE + ef 03 45 00 00 00 a0 00 00:20:45.284 SET FEATURES [Set transfer mode]" According to some mail list talks about that HDD, NCQ is disabled on - this Fujitsu HDD anyway (independently from the blacklist). So what are - these NCQ commands then? Very bad thing. + this Fujitsu HDD anyway (independently from the blacklist). - I see 3 unrelaocatable bad sectors according to GSmartControl. So it can happen that my HDD is bad (4 years old, I haven't ever dropped my laptop, I handle it well). But I find it more than a coincidence, that the errors popped up only with the 2.6.34 and 2.6.35 kernels, where the undo of the balcklist addition happened... + I see 3 unrelaocatable bad sectors according to GSmartControl. So it can happen that my HDD is bad (4 years old, I haven't ever dropped my laptop, I handle it well). If the NCQ supposed to be disable don this HDD anyway, seeing NCQ commands are not good signs, should not happen at all. I cannot reproduce the bug deterministically. Most of the time my laptop - comes back from suspend without aproblem. But given that this can + comes back from suspend without a problem. But given that this can result in data loss, maybe serious degradation of the HDD health and it affects Mac and IBM laptop users also, some investigation would be great. Why they removed that Fjitsu HDD from that balcklist? I manually copy the essence of the terminal error messages, there are hundreds of these with timestamps (I omitted those, since I manually copied), here they come: "ata3.00 exception Emask 0x0 SAct 0x1 SErr 0x0 action0x0 ata3.00 irq_stat 0x40000008 ata3.00 failed command: READ FPDMA QUEUED ata3.00 cmd 60/08:00:f0:70:cd/00:00:0e:00:00/40 tag 0 ncq 4096 in - res 41/40:00:f0:70:cd/00:00:0e:00:00/40 Emask 0x409 (media error) <F> + res 41/40:00:f0:70:cd/00:00:0e:00:00/40 Emask 0x409 (media error) <F> ata3.00 status: { DRDY ERR } ata3.00 error: { UNC } this repeats another 5 times, then finally: end_request: I/O error, dev sda, sector 248344816" - - Let me know if I can help. I'm a software developer, I'm a power Linux - user, I don't compile my own kernels these days though (I got lazy - compared to 10 years ago). ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: linux-image-2.6.35-30-generic 2.6.35-30.59 Regression: No Reproducible: No ProcVersionSignature: Ubuntu 2.6.35-30.59-generic 2.6.35.13 Uname: Linux 2.6.35-30-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23. Architecture: i386 ArecordDevices: - **** List of CAPTURE Hardware Devices **** - card 0: Intel [HDA Intel], device 0: ALC262 Analog [ALC262 Analog] - Subdevices: 1/1 - Subdevice #0: subdevice #0 + **** List of CAPTURE Hardware Devices **** + card 0: Intel [HDA Intel], device 0: ALC262 Analog [ALC262 Analog] + Subdevices: 1/1 + Subdevice #0: subdevice #0 AudioDevicesInUse: - USER PID ACCESS COMMAND - /dev/snd/controlC0: tocsa 2069 F.... pulseaudio + USER PID ACCESS COMMAND + /dev/snd/controlC0: tocsa 2069 F.... pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: - Card hw:0 'Intel'/'HDA Intel at 0xfe420000 irq 47' - Mixer name : 'Realtek ALC262' - Components : 'HDA:10ec0262,10cf0100,00100202 HDA:11c11040,11c10001,00100200' - Controls : 27 - Simple ctrls : 16 + Card hw:0 'Intel'/'HDA Intel at 0xfe420000 irq 47' + Mixer name : 'Realtek ALC262' + Components : 'HDA:10ec0262,10cf0100,00100202 HDA:11c11040,11c10001,00100200' + Controls : 27 + Simple ctrls : 16 Date: Wed Sep 21 12:03:45 2011 Frequency: Once every few days. HibernationDevice: RESUME=UUID=73417533-5f5d-4e3c-afd9-7ff0701da9be InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release i386 (20100816.1) MachineType: FUJITSU E8410 PccardctlIdent: - Socket 0: - no product info available - Socket 1: - product info: "O2Micro", "SmartCardBus Reader", "V1.0", "" - manfid: 0xffff, 0x0001 + Socket 0: + no product info available + Socket 1: + product info: "O2Micro", "SmartCardBus Reader", "V1.0", "" + manfid: 0xffff, 0x0001 PccardctlStatus: - Socket 0: - no card - Socket 1: - 5.0V 16-bit PC Card - Subdevice 0 (function 0) [unbound] + Socket 0: + no card + Socket 1: + 5.0V 16-bit PC Card + Subdevice 0 (function 0) [unbound] ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-30-generic root=UUID=f61c3819-eddf-4882-a450-166548d6dd4c ro quiet splash ProcEnviron: - PATH=(custom, user) - LANG=en_US.utf8 - SHELL=/bin/bash + PATH=(custom, user) + LANG=en_US.utf8 + SHELL=/bin/bash RelatedPackageVersions: linux-firmware 1.38.6 RfKill: - 0: phy0: Wireless LAN - Soft blocked: no - Hard blocked: no + 0: phy0: Wireless LAN + Soft blocked: no + Hard blocked: no SourcePackage: linux dmi.bios.date: 08/18/2008 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.15 dmi.board.name: FJNB1CF dmi.board.vendor: FUJITSU dmi.chassis.type: 10 dmi.chassis.vendor: AZ35B1E708B51033 dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.15:bd08/18/2008:svnFUJITSU:pnE8410:pvr:rvnFUJITSU:rnFJNB1CF:rvr:cvnAZ35B1E708B51033:ct10:cvr: dmi.product.name: E8410 dmi.sys.vendor: FUJITSU ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/855770 Title: FUJITSU MHW2160BH PL hard read errors after wake up from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/855770/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
