kernel BUG at /build/buildd/linux-2.6.32/fs/ext4/extents.c:1716 makes most programs freeze few minutes after boot

[Raphaël F.]

Hi,

I noticed two facts which can be related to this bug.

* First, few time after kernel upgrade to 2.6.32-24, I got some programs freezing and leading the computer to be unusable. I mean, there was not complete freeze: ie. mouse cursor, time and window moves still worked, but majority of running apps (firefox, chrome, transmissionBT, nautilus, etc.) were freezing and turned grey, while trying to open other apps was not possible. Even log in tty1 failed: prompt never came after login. Elsewhere, network activity was stopping immediately when the bug occurred. Concerning the CPU usage, it was not at max, about 10-30%, nothing extraordinary.
Taking a look at system-monitor (which had not frozen, as I remember) showed that status of processes which had frozen were tagged as "ininterruptible". I discover that jdb2 was also tagged "ininterruptible", I don't know why, but kernel.log showed following entry several times about 17 seconds after boot (cf. dmesg or syslog):
"JBD: barrier-based sync failed on md0-8 - disabling barriers"

* In addition, I noticed this bug appeared equally after copying huge data in my /home partition making it full at 95% (with less than 5% free space), I don't know if this is linked, because since I have deleted these files and made /home partition less loaded, the freezes did not reappear...

I have tried to use current mainline-kernel: 2.6.35-999-generic, but the behaviour was identical, so I came back to stable kernel (as you can see in log files). The only fact I noticed that resolved the problem was making free space available in my /home partition as said above. For testing, I have tried to make this partition full at 99%, but the computer is ON since 1h40 now, but nothing to report currently...

Attached files show several "cut here" statements in syslog, 8/10 concerns:
"last sysfs file: /sys/devices/pci0000:00/0000:00:06.0/0000:02:00.0/net/eth0/statistics/collisions"
The 2 other are related to:
"last sysfs file: /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq"

Hope that helps.

ps: I will attach complete syslog of the day, from kernel upgrade to resolved problem...

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: linux-image-2.6.32-24-generic 2.6.32-24.38
Regression: No
Reproducible: No
ProcVersionSignature: Ubuntu 2.6.32-24.38-generic 2.6.32.15+drm33.5
Uname: Linux 2.6.32-24-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: rflores 1626 F.... pulseaudio
 /dev/snd/controlC1: rflores 1626 F.... pulseaudio
CRDA: Error: [Errno 2] Aucun fichier ou dossier de ce type
Card0.Amixer.info:
 Card hw:0 'SB'/'HDA ATI SB at 0xfe024000 irq 16'
   Mixer name : 'Realtek ALC887'
   Components : 'HDA:10ec0887,1458a002,00100202'
   Controls : 40
   Simple ctrls : 22
Card1.Amixer.info:
 Card hw:1 'camera'/'USB camera at usb-0000:00:13.1-3, full speed'
   Mixer name : 'USB Mixer'
   Components : 'USB045e:00f7'
   Controls : 3
   Simple ctrls : 2
Card2.Amixer.info:
 Card hw:2 'HDMI'/'HDA ATI HDMI at 0xfdffc000 irq 19'
   Mixer name : 'ATI RS690/780 HDMI'
   Components : 'HDA:1002791a,00791a00,00100000'
   Controls : 4
   Simple ctrls : 1
Card2.Amixer.values:
 Simple mixer control 'IEC958',0
   Capabilities: pswitch pswitch-joined penum
   Playback channels: Mono
   Mono: Playback [off]
Date: Sun Jul 25 02:55:11 2010
Frequency: I don't know.
HibernationDevice: RESUME=UUID=ad2dc738-34d8-4f66-92f9-7b3d22702c61
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100427.1)
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. GA-MA74GM-S2H
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-24-generic root=UUID=e561f624-e8b8-4731-ba7e-be40b0c0c655 ro quiet splash
ProcEnviron:
 LANG=fr_FR.utf8
 SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.34.1
RfKill:

SourcePackage: linux
dmi.bios.date: 12/21/2009
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: FBi
dmi.board.name: GA-MA74GM-S2H
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrFBi:bd12/21/2009:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA74GM-S2H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA74GM-S2H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: GA-MA74GM-S2H
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
---
Architecture: i386
DistroRelease: Ubuntu 10.04
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100427.1)
Package: linux (not installed)
ProcEnviron:
 LANG=fr_FR.utf8
 SHELL=/bin/bash
Tags: lucid
Uname: Linux 2.6.35-999-generic i686
UnreportableReason: The running kernel is not an Ubuntu kernel
UserGroups: adm admin cdrom dialout fuse lpadmin plugdev sambashare

---
Architecture: i386
DistroRelease: Ubuntu 10.04
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100427.1)
Package: linux-image-2.6.35-999-generic 2.6.35-999.201007241005
PackageArchitecture: i386
ProcEnviron:
 LANG=fr_FR.utf8
 SHELL=/bin/bash
Tags: lucid
Uname: Linux 2.6.35-999-generic i686
UnreportableReason: This is not a genuine Ubuntu package
UserGroups: adm admin cdrom dialout fuse lpadmin plugdev sambashare

[Raphaël F. (rflores)]

Attached file show complete syslog which contains numerous "CUT HERE" statements showing the kernel bug explanation, and dmesg, and other utils.

[Jeremy Foshee (jeremyfoshee)]

Hi rflores,

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.]

[Raphaël F. (rflores)]

Hi Jeremy,

I thinks youj meant launch ubuntu-bug for getting logs with mainline kernel ? Because I already tested with mainline kernel: 2.6.35-999-generic.

I've rebooted, and I'm currently using mainline kernel, I'll see if the bug reappers, but since I've made some free space sunday, the behaviour has not been reproduced, so I don't know if thesse reports will be helpful to you. I'll upload reports with mainline kernel soon.

Thanks.

[Raphaël F. (rflores)]

Hi.

Currently running onto kernel 2.6.35-999-generic, I cannot reproduce the bug, I have updated the report using command:
"apport-collect -p linux 609643", and I removed needs-upstream-testing tag.

It seems the added report is not really verbose, I've tried with "ubuntu-bug linux" command, but it has failed because of following:
"The problem cannot be reported:

This is not a genuine Ubuntu package"

If you have suggestions for getting a proper report, I'm in wait.

I still use the kernel for getting more info if found.

Hope this will help.

[Raphaël F. (rflores)]

apport information

[Raphaël F. (rflores)]

Adding some manual reports...

[Raphaël F. (rflores)]

Adding manual reports using mainline kernel...

[Raphaël F. (rflores)]

I set the status to new since last information have been given. Hope all is here to help to debug.

[Kristopher Clark (kristopher-clark)]

I can confirm this bug on 64bit kernel 2.6.32-25-generic

[Kristopher Clark (kristopher-clark)]

I know this doesn't pin point the bug, but I did upgrade to 10.10 x64 last night and it seems this problem has been resolved, can anyone else confirm this?

[Kristopher Clark (kristopher-clark)]

changing to invalid as I am the only person who can reproduce this and it seems to have been fixed with the upgrade

[tinnycloud (tinnycloud)]

HI Ted:

I was run into this issue with 32.36 kernel. But hard to reproduce.
Did you mean the 2.6.35 kerenel fixed the problem.
Could you let me know how to reproduce it in a fast way.
Many thanks.