System partial freeze minutes after startup.

[Andrew Read]

Running Ubuntu 10.04 Netbook Edition on a Samsung N140 with the latest kernel installed (linux-image-2.6.32-22-generic) or any of the previous kernels including the previous distribution release (Ubuntu 8.10 Netbook Remix) a partial system freeze occurs. During the freeze the cursor can still be moved but it is not possible to interact with the system, after about 1 minute the system resumes without any further issues. If any keystrokes were made or mouse clicks made they will be executed in sequence after this 1 minute freeze. This freeze usually occurs after 5 minutes of system start up, demesg reports issues with an ata device.
In one instant of this freeze on another netbook of the same model this issue occurred in the middle of a package installation, system files became corrupted and non recoverable requiring a complete re installation of Ubuntu.

Here I believe are the significant entries from dmesg:

[ 236.812621] Monitor-Mwait will be used to enter C-2 state
[ 236.812641] Marking TSC unstable due to TSC halts in idle
[ 236.815834] Switching to clocksource hpet
[ 278.816169] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[ 278.816191] ata1.00: failed command: WRITE DMA
[ 278.816221] ata1.00: cmd ca/00:08:c0:b8:0d/00:00:00:00:00/e5 tag 0 dma 4096 out
[ 278.816227] res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 278.816241] ata1.00: status: { DRDY }
[ 283.856089] ata1: link is slow to respond, please be patient (ready=0)
[ 288.840087] ata1: device not ready (errno=-16), forcing hardreset
[ 288.840111] ata1: soft resetting link
[ 289.206453] ata1.00: configured for UDMA/133
[ 289.206473] ata1.00: device reported invalid CHS sector 0
[ 289.206505] ata1: EH complete

I hope this information is of use, please let me know if there are any tests that I can perform to assist.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: linux-image (not installed)
Regression: No
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.32-22.36-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: andrew 1052 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf0440000 irq 22'
   Mixer name : 'Realtek ALC269'
   Components : 'HDA:10ec0269,144dc062,00100004'
   Controls : 13
   Simple ctrls : 8
Date: Thu Jul 1 11:33:56 2010
HibernationDevice: RESUME=UUID=d0dc2263-09ba-4b68-80f4-89ff7ca3a1f6
InstallationMedia: Ubuntu-Netbook 10.04 "Lucid Lynx" - Release i386 (20100429.4)
MachineType: SAMSUNG ELECTRONICS CO., LTD. N140
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-22-generic root=UUID=09bdbbba-ff02-4fb7-b498-d599a306bf57 ro quiet splash
ProcEnviron:
 LANG=en_GB.utf8
 SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.34
RfKill:
 0: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
dmi.bios.date: 01/10/2010
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: 05CU.M021.20100110.JIP
dmi.board.name: N140
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr05CU.M021.20100110.JIP:bd01/10/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnN140:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnN140:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
dmi.product.name: N140
dmi.product.version: Not Applicable
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

[Jeremy Foshee (jeremyfoshee)]

Hi Andrew,

If you could also please test the latest upstream kernel available 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. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Andrew Read (andrew-read)]

I have tested the Netbook with the kernel packages listed:

http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/current/linux-headers-2.6.35-999-generic_2.6.35-999.201007081234_i386.deb

http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/current/linux-headers-2.6.35-999_2.6.35-999.201007081234_all.deb

http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/current/linux-image-2.6.35-999-generic_2.6.35-999.201007081234_i386.deb

The bug is not present with this release.

[Andrew Read (andrew-read)]

This bug seems to be the same as reported:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/297058
To summarise it is a conflict with a power management feature in some BIOS systems.

I have tried the kernel from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.35-rc1-lucid/
This kernel is free from this bug.

I have tested:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.34-rc7-lucid/
This kernel is also free from the bug.

I have also tested:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.33.1-lucid/
This is effected by the freeze bug.

So it seems that from kernel versions 2.6.34 and greater we are free from this bug.

I would suggest that it is of extreme importance that this is resolved through an update as soon as possible as it can cause filesystem damage and I have also seen a partition made unrecoverable and a system rendered un-bootable after such an occurrence, it seems to effect more than just this model of netbook.

If there is anything more I can test or do please let me know.

[Andrew Read (andrew-read)]

Bug still present in linux-image-2.6.32-24-generic recently released, the dmesg output is attached.

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu development release http://cdimage.ubuntu.com/daily-live/current/ . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[penalvch (penalvch)]

Andrew Read, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command in the development release from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux <replace-with-bug-number>

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please do not test the kernel in the daily folder, but the one all the way at the bottom. 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. As well, please comment on which kernel version specifically you tested.

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', and comment as to why specifically you were unable to test it.

Please let us know your results. Thanks in advance.

[Andrew Read (andrew-read)]

kernel-unable-to-test-upstream

I no longer possess the hardware in question, however this bug is resolved with newer kernels which are incorperated into the current Long Term Support distribution making it irrelevant.