[Regression] Freezes since kernel 2.6.35-23

Bug #706532 reported by YannUbuntu
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

On Ubuntu 10.10
With kernel 2.6.35-23 and later (last tested : 2.6.35-27), I have the following problem : my session freezes few minutes after i start my computer. The mouse does not move any more, and no application runs. I noticed that when I listen some music at this moment (Rhythmbox or Minitube), the last 3 or 4 seconds continue to play in loop indefinitely after the freeze.
It can also happen just with Firefox open.

I now use the 2.6.35-22 kernel, and I don't have this bug any more.

EDIT : I had a freeze with 2.6.35-22 kernel (see below) but i cannot reproduce, whereas I can reproduce very very easily with the 2.6.35-23 and later kernels.

I did not have freeze on Ubuntu 10.04 LTS.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: linux-image-2.6.35-22-generic 2.6.35-22.35
Regression: Yes
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.35-22.35-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: yyy 1348 F.... pulseaudio
 /dev/snd/pcmC0D0p: yyy 1348 F...m pulseaudio
Card0.Amixer.info:
 Card hw:0 'SB'/'HDA ATI SB at 0xc0000000 irq 16'
   Mixer name : 'Realtek ALC262'
   Components : 'HDA:10ec0262,10338802,00100002 HDA:11c13026,1033880b,00100700'
   Controls : 12
   Simple ctrls : 9
Date: Sun Jan 23 19:59:10 2011
HibernationDevice: RESUME=UUID=def8769f-2a4a-43b5-b9d9-c27f7234ac7d
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
Lsusb:
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: NEC PC-LL550HG
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-generic root=UUID=b5dc97e5-a22e-48ef-840d-f3a2b6d0834d ro vga=773 quiet splash i8042.nomux=1
ProcEnviron:
 LANG=fr_FR.utf8
 SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.38
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
dmi.bios.date: 01/06/2007
dmi.bios.vendor: NEC
dmi.bios.version: NOTE BIOS Version /524A0402
dmi.board.name: HAL50
dmi.board.vendor: NEC
dmi.board.version: 20C2B
dmi.chassis.type: 10
dmi.chassis.vendor: NEC
dmi.modalias: dmi:bvnNEC:bvrNOTEBIOSVersion/524A0402:bd01/06/2007:svnNEC:pnPC-LL550HG:pvr:rvnNEC:rnHAL50:rvr20C2B:cvnNEC:ct10:cvr:
dmi.product.name: PC-LL550HG
dmi.sys.vendor: NEC

Revision history for this message
YannUbuntu (yannubuntu) wrote :
Revision history for this message
YannUbuntu (yannubuntu) wrote :

It seems that the freezes occur only when I do a copy/paste from disk to disk (not via USB).

Revision history for this message
YannUbuntu (yannubuntu) wrote :

I just had a new freeze with the 2.6.35-22 kernel , while I was running Thunderbird. Magic Sys Keys had no effect, I had to shutdown the computer with ON/OFF button.

summary: - [Regression] Freezes since kernel 2.6.35-23
+ [Regression] Freezes since Ubuntu 10.10
description: updated
YannUbuntu (yannubuntu)
summary: - [Regression] Freezes since Ubuntu 10.10
+ [Regression] Freezes since kernel 2.6.35-23
description: updated
YannUbuntu (yannubuntu)
description: updated
Revision history for this message
Eric Zurcher (eric-zurcher) wrote :

Could this be related to bug #719446?

Revision history for this message
YannUbuntu (yannubuntu) wrote :

Thanks Eric for the clue.
Yes it looks similar.
How can I check if I have a single-core system or not ?

(I don't know if it can help, but for information, I run Ubuntu 10.10 32 bit, and I think my processor is 64 bit)

Revision history for this message
Pawel Jasnos (pjasnos) wrote :

Yann, first of all can you test your RAM for defects?
Hold left shift key while powering on your computer to see GRUB boot menu and select memory test from there. You should run it for a few hours (probably best overnight) and see if there are any errors reported at the bottom of the screen (in which case you would need to replace your RAM as it is damaged).
 I'm asking you to do this as you said you experienced freezes even on 2.6.35-22.

Also, looking at ProcCpuinfo.txt which you attached to this bug report, your processor is indeed single core.

Revision history for this message
YannUbuntu (yannubuntu) wrote :

Thank you for your message.

Indeed the problem I had once on 2.6.35-22 (only once, since I used many times this kernel without any bug) is I believe very different from the systematic (each time I open a session) and fast (after few minutes PC use) I have with following kernels.

Nevertheless, I tried the Memtest86+ tests 3 times, and surprisingly, each time, after ~60% of the 1st pass, my computer suddenly shut off completely !!!
What could be the reason ?

Revision history for this message
Pawel Jasnos (pjasnos) wrote :

Most likely reason is that your RAM is damaged and you need to replace it.

Revision history for this message
Pawel Jasnos (pjasnos) wrote :

Some other hardware problems are also possible, but less likely.

Revision history for this message
Pawel Jasnos (pjasnos) wrote :

Yann, I'm going to mark this bug as invalid, as it's next to impossible to find a culprit of a software problem if hardware is unreliable. If you're suffering from https://bugs.launchpad.net/bugs/719446 , then it is already triaged with high priority so it will be fixed. If you're suffering from a different bug, any diagnosing efforts are going to be hampered by hardware problems.
If you manage to find and fix a cause for your computer crashing during memtest (most likely culprit is RAM), feel free to re-open this bug by marking it as 'New' again.

Changed in linux (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.