Kernel Oops - BUG: unable to handle kernel paging request at 3f93cd3a; EIP is at kfree+0x3d/0xe0

Bug #744777 reported by moma
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Low
Unassigned

Bug Description

The Linux kernel (on Ubuntu 11.04) crashes randomly. It may be a hardware failure because this laptop (Fujitsu Siemens AMILO Li 1718 laptop) is rather old.

lspci -v | grep -i vga
01:05.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI RC410 [Radeon Xpress 200M] (prog-if 00 [VGA controller])

Tested:
+ vmlinuz-3.2.0-20-generic-pae (standard kernel in Ubuntu 12.04)
And two upstream kernels from http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.3-rc7-precise/
+ vmlinuz-3.3.0-999-generic
+ vmlinuz-3.3.0-999-generic-pae

WORKAROUND: Use fglrx.

ProblemType: KernelOops
DistroRelease: Ubuntu 11.04
Package: linux-image-2.6.38-7-generic 2.6.38-7.39
Regression: Yes
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38
Uname: Linux 2.6.38-7-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Annotation: Your system might become unstable now and might need to be restarted.
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: moma 1141 F.... pulseaudio
 /dev/snd/pcmC0D0p: moma 1141 F...m pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'SB'/'HDA ATI SB at 0xc0500000 irq 41'
   Mixer name : 'Realtek ALC861-VD'
   Components : 'HDA:10ec0862,173410fb,00100001 HDA:10573055,173410fb,00100700'
   Controls : 12
   Simple ctrls : 8
Date: Mon Mar 28 21:42:26 2011
Failure: oops
HibernationDevice: RESUME=UUID=c227fdae-6e11-42ce-a414-8e280d80ea78
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110325)
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: FUJITSU SIEMENS AMILO Li 1718
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-7-generic root=UUID=8e274136-c7f3-44d6-8e45-28ab02c016b6 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-2.6.38-7-generic N/A
 linux-backports-modules-2.6.38-7-generic N/A
 linux-firmware 1.49
SourcePackage: linux
Title: BUG: unable to handle kernel paging request at 3f93cd3a
UpgradeStatus: No upgrade log present (probably fresh install)
WifiSyslog:
 Mar 29 08:24:27 natty32 kernel: [ 969.712033] hda-intel: azx_get_response timeout, switching to polling mode: last cmd=0x10a90000
 Mar 29 08:24:28 natty32 kernel: [ 970.716042] hda-intel: No response from codec, disabling MSI: last cmd=0x10a90000
 Mar 29 08:24:29 natty32 kernel: [ 971.720025] hda_intel: azx_get_response timeout, switching to single_cmd mode: last cmd=0x10a90000
dmi.bios.date: 11/12/07
dmi.bios.vendor: Phoenix
dmi.bios.version: V1.9
dmi.board.name: AMILO Li 1718
dmi.board.vendor: FUJITSU SIEMENS
dmi.board.version: Rev.A
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: ATI
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenix:bvrV1.9:bd11/12/07:svnFUJITSUSIEMENS:pnAMILOLi1718:pvr-1:rvnFUJITSUSIEMENS:rnAMILOLi1718:rvrRev.A:cvnATI:ct1:cvrN/A:
dmi.product.name: AMILO Li 1718
dmi.product.version: -1
dmi.sys.vendor: FUJITSU SIEMENS
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 1.95-0ubuntu1
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: moma 1602 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
CurrentDmesg: [ 52.821269] cfg80211: Found new beacon on frequency: 2472 MHz (Ch 13) on phy0
DistroRelease: Ubuntu 12.04
HibernationDevice: RESUME=UUID=9d083ac6-cff0-4b98-bc78-fb7c683af596
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20120322)
MachineType: FUJITSU SIEMENS AMILO Li 1718
Package: linux (not installed)
ProcEnviron:
 LANGUAGE=en_US:en
 TERM=xterm
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-20-generic-pae root=UUID=46d5cae2-e732-4ebc-9022-c8238b29a2dd ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.2.0-20.32-generic-pae 3.2.12
Tags: precise
Uname: Linux 3.2.0-20-generic-pae i686
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 06/14/07
dmi.bios.vendor: Phoenix
dmi.bios.version: V1.7
dmi.board.name: AMILO Li 1718
dmi.board.vendor: FUJITSU SIEMENS
dmi.board.version: Rev.A
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: ATI
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenix:bvrV1.7:bd06/14/07:svnFUJITSUSIEMENS:pnAMILOLi1718:pvr-1:rvnFUJITSUSIEMENS:rnAMILOLi1718:rvrRev.A:cvnATI:ct1:cvrN/A:
dmi.product.name: AMILO Li 1718
dmi.product.version: -1
dmi.sys.vendor: FUJITSU SIEMENS

Revision history for this message
moma (osmoma) wrote :
Revision history for this message
Herton R. Krzesinski (herton) wrote :

It seems a memory corruption issue, but may still be a bug and not hardware issue. Can you boot your kernel with slub_debug kernel parameter (add slub_debug to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub and run "sudo update-grub2", then reboot), and see if you get a different oops? If you get some other oops/warning with slub_debug then please attach here the dmesg output.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
moma (osmoma) wrote :

Hello,
I have now added slub_debug to the kernel line.

$ cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-2.6.38-7-generic root=UUID=8e274136-c7f3-44d6-8e45-28ab02c016b6 ro quiet splash slub_debug vt.handoff=7

Here are syslog and some other log files from the /var/log/ directory.
http://www.futuredesktop.org/tmp/var_log.tar.gz (also added as attachment)

I have now run the MemTest86+ (v.4.20) and it passed ok. It ran 2 passes that took over 4 hours to complete. No errors were found.

I still suspect that this laptop has a hw failure.
The crash occurs very randomly and it happens both in Ubuntu 10.10 and 11.04.

Please see also this posting on Ubuntuforums.org
http://ubuntuforums.org/showthread.php?p=10613592

Changed in linux (Ubuntu):
status: Incomplete → Triaged
Revision history for this message
moma (osmoma) wrote :

I got couple of beautiful and complete crashes this morning.
Attaching a fresh /var/log/syslog

Revision history for this message
moma (osmoma) wrote :

Attachment.
$ cat syslog | grep "BUG"

Revision history for this message
Herton R. Krzesinski (herton) wrote :

Do you still get the crashes if you disable UFW (Uncomplicated Firewall)? (sudo ufw disable)

Changed in linux (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
moma (osmoma) wrote :

Re-hello.
I disabled and removed the ufw (and gufw) packages. It did not help. The laptop keeps crashing.
I have decided to write off and put-down this laptop for good.
Thanks for your help.

Revision history for this message
laustemil@gmail.com (laustemil) wrote :

the problem may relate to the package modemmanager

Revision history for this message
Wim Feijen (wimfeijen) wrote :

Hello,

My Fujitsu Siemens laptop also started to crash spontaneously. It is a Amilo Pi 2530 running Ubuntu 11.04 in classical view (gnome 2.32.1).

I upgraded it to kernel 2.6.38-9-generic a moment ago.

Wim

Revision history for this message
Wim Feijen (wimfeijen) wrote :

Another thing I notice, is that when my computer is running, it sometimes goes superslow. Right now, I am doing nothing and CPU usage is 100% and 50%. While no program is running except for the System Monitor.

Revision history for this message
Wim Feijen (wimfeijen) wrote :

Hello,

Stupid I only thought of it now, but I own a Fujitsu Siemens Amilo Li 1718 as well.

I only recently replaced the hard drive because of spontaneous crashes.

Now I am convinced Ubuntu 11.04 is the cause of these crashes, not a defect hard drive.

I am willing to help with investigations, what kind of information do you need?

Wim

Revision history for this message
Wim Feijen (wimfeijen) wrote :

I'll post information about the hard drive:

Model: ATA WDC WD2500BEVS-22USTO
Firmware Version: 01.01A10
Location: Port 1 of SATA Host Adapter
Write Cache: Enabled
Capacity: 250 GB (250,059,350,016 bytes)
Partitoning: Maser Boot Record

Serial Number: WD-WXE907446810
World Wide NAme: 0x50014ee200918973
Device: /dev/sda
Rotation Rate: -
Connection: ATA
SMART Status: Disk has a few bad sectors

Volumes:

Usage: Filesystem
Partition Type: Linux (0x83)
Partition Flags: Bootable
Type: Ext4 (version 1.0)
Label: -

Device: /dev/sda1
Partition Label: -
Capacity: 244 GB (243,877,806,080 bytes)
Available: -
Mount Point: Mounted at /

SMART Data
Shows one warning:
Reallocated sector count
Normalized: 194
Worst: 194
Threshold: 140
Value: 47 sectors

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
Revision history for this message
o_portista17 (o-portista17-) wrote :

This error is still present, my ubuntu just crashes all the time, and i have to hard shutdown my laptop Fujitsu Siemens Amilo 1718i.
Link to my "kern.log" : http://paste.ubuntu.com/686729/
Right now i'm using kernel 3.0.0-11-generic #17-Ubuntu SMP Sat Sep 10 13:50:55 UTC 2011 i686 i686 i386 GNU/Linux, to see if the bug stops.

Any help would be more then welcome.

Changed in linux (Ubuntu):
status: Expired → Confirmed
penalvch (penalvch)
summary: - BUG: unable to handle kernel paging request at 3f93cd3a
+ Kernel Oops - BUG: unable to handle kernel paging request at 3f93cd3a;
+ EIP is at kfree+0x3d/0xe0
Revision history for this message
penalvch (penalvch) wrote :

moma, thank you for reporting this bug and helping make Ubuntu better. 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 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 . 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.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
moma (osmoma) wrote : AcpiTables.txt

apport information

tags: added: apport-collected precise
description: updated
Revision history for this message
moma (osmoma) wrote : AlsaDevices.txt

apport information

Revision history for this message
moma (osmoma) wrote : AplayDevices.txt

apport information

Revision history for this message
moma (osmoma) wrote : ArecordDevices.txt

apport information

Revision history for this message
moma (osmoma) wrote : BootDmesg.txt

apport information

Revision history for this message
moma (osmoma) wrote : Card0.Amixer.info.txt

apport information

Revision history for this message
moma (osmoma) wrote : Card0.Amixer.values.txt

apport information

Revision history for this message
moma (osmoma) wrote : Card0.Codecs.codec.0.txt

apport information

Revision history for this message
moma (osmoma) wrote : Card0.Codecs.codec.1.txt

apport information

Revision history for this message
moma (osmoma) wrote : IwConfig.txt

apport information

Revision history for this message
moma (osmoma) wrote : Lspci.txt

apport information

Revision history for this message
moma (osmoma) wrote : Lsusb.txt

apport information

Revision history for this message
moma (osmoma) wrote : PciMultimedia.txt

apport information

Revision history for this message
moma (osmoma) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
moma (osmoma) wrote : ProcInterrupts.txt

apport information

Revision history for this message
moma (osmoma) wrote : ProcModules.txt

apport information

Revision history for this message
moma (osmoma) wrote : PulseList.txt

apport information

Revision history for this message
moma (osmoma) wrote : RelatedPackageVersions.txt

apport information

Revision history for this message
moma (osmoma) wrote : RfKill.txt

apport information

Revision history for this message
moma (osmoma) wrote : UdevDb.txt

apport information

Revision history for this message
moma (osmoma) wrote : UdevLog.txt

apport information

Revision history for this message
moma (osmoma) wrote : WifiSyslog.txt

apport information

Revision history for this message
moma (osmoma) wrote :

Re-hello,
I have tested this AMILO Li1718 laptop with Ubuntu 12.04 and two new upstream kernels.
This laptop kept crashing no matter what kernel I booted with, BUT IT WORKED VERY WELL after I installed the "fglrx" or "fbdev" video drivers.

Test 1) FAILED.
 I tested Ubuntu 12.04 with these three kernels:
 vmlinuz-3.2.0-20-generic-pae (standard kernel in Ubuntu 12.04)

 And two upstream kernels from http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.3-rc7-precise/
 vmlinuz-3.3.0-999-generic
 vmlinuz-3.3.0-999-generic-pae

 The video driver was the default "xserver-xorg-video-radeon".

 The laptop crashed (within half an hour) no matter which kernel I booted with.

 Please see listing of:
 dpkg -l | egrep "radeon"
 http://www.futuredesktop.com/amilo/dpkg.radeon

 lsmod.redeon
 http://www.futuredesktop.com/amilo/lsmod.radeon

 Xorg.0.log
 http://www.futuredesktop.com/amilo/Xorg.0.log.radeon
-----------------

Test 2) SUCCESS.
I booted with Ubuntu's standard vmlinuz-3.2.0-20-generic-pae kernel.
The kernel did not matter in this test.

Then I installed the "fglrx" driver which I suppose replaces the default radeon driver in Ubuntu.

[from wikipedia.org:
Fglrx is the name of the Linux display driver used for ATI Radeon and ATI FireGL family of video
adapters and stands for "FireGL and Radeon for X".]

The Laptop runs like a dream. It does not crash anymore.
I have tested it with very heavy load and various tasks in several hours and it simply runs and runs.

 Please see listing of:
 dpkg -l | egrep "radeon|fglrx"
 http://www.futuredesktop.com/amilo/dpkg.fglrx

 lsmod
 http://www.futuredesktop.com/amilo/lsmod.fglrx

 Xorg.0.log
 http://www.futuredesktop.com/amilo/Xorg.0.log.fglrx
-------------------

Test 3) SUCCESS.
I booted with Ubuntu's standard vmlinuz-3.2.0-20-generic-pae kernel.

Then I copied /etc/X11/xorg.conf.failsafe to /etc/X11/xorg.conf and rebooted.

This xorg.conf uses "fbdev" as video driver.

And the laptop runs very well this setting. I cannot make it crash.

 Please see:
 xorg.conf
 http://www.futuredesktop.com/amilo/xorg.conf

 dpkg -l | egrep "radeon|fglrx"
 http://www.futuredesktop.com/amilo/dpkg.fbdev

 lsmod
 http://www.futuredesktop.com/amilo/lsmod.fbdev

 Xorg.0.log
 http://www.futuredesktop.com/amilo/Xorg.0.log.fbdev
-------------------

This laptop has AMD/ATI Radeon Xpress 200M graphics chipset.

$ lspci -v | grep -i vga
01:05.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI RC410 [Radeon Xpress 200M] (prog-if 00 [VGA controller])

penalvch (penalvch)
description: updated
description: updated
tags: removed: needs-upstream-testing
Revision history for this message
penalvch (penalvch) wrote :

moma, the issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at http://www.kernel.org/pub/linux/docs/lkml/reporting-bugs.html . If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance.

tags: added: maverick
tags: removed: regression-release
Changed in linux (Ubuntu):
importance: Undecided → Low
status: Incomplete → Triaged
Changed in linux:
status: New → Incomplete
penalvch (penalvch)
description: updated
Revision history for this message
penalvch (penalvch) wrote :

moma, as per http://support.ts.fujitsu.com/Download/ShowFiles.asp an update is available for your BIOS (1.90). If you update to this following https://help.ubuntu.com/community/BiosUpdate , does it change anything?

If not, could you please both specify what happened, and provide the output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful.

For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette .

Thank you for your understanding.

tags: added: bios-outdated-1.90
Changed in linux (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
moma (osmoma) wrote :

Hello,
Unfortunately I do not have the laptop anymore. I sold it.
Can anyone else test the BIOS upgrade?

Revision history for this message
penalvch (penalvch) wrote :

moma, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/744777/comments/41 regarding you no longer have the hardware. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.

no longer affects: linux
Changed in linux (Ubuntu):
status: Incomplete → 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.