Corrupted low memory at ffff880000005df0 (5df0 phys) = e47700000000

Bug #536814 reported by Whorehay
12
This bug affects 3 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
Low
Manoj Iyer

Bug Description

The error continues to occur regardless of what I'm doing on the computer. Installing the latest updates has not fixed it, nor has rebooting the computer.

ProblemType: KernelOops
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Annotation: Your system might become unstable now and might need to be restarted.
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: NVidia [HDA NVidia], device 0: STAC92xx Analog [STAC92xx Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: george 1601 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'NVidia'/'HDA NVidia at 0xf0980000 irq 17'
   Mixer name : 'Nvidia MCP7A HDMI'
   Components : 'HDA:111d7604,102802ba,00100302 HDA:10de0007,102802ba,00100100'
   Controls : 20
   Simple ctrls : 11
Date: Wed Mar 10 08:28:44 2010
DistroRelease: Ubuntu 10.04
Failure: oops
Frequency: Once a day.
HibernationDevice: RESUME=UUID=84eb0f7a-f13d-4e2b-aa34-acebcdb8f662
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100307)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 002: ID 0c45:63e7 Microdia
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Studio 1440
NonfreeKernelModules: nvidia
Package: linux-image-2.6.32-16-generic 2.6.32-16.25
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-16-generic root=UUID=079540be-a826-4ee8-a40e-bacc4c1ced0c ro quiet
ProcVersionSignature: Ubuntu 2.6.32-16.25-generic
Regression: Yes
RelatedPackageVersions: linux-firmware 1.32
Reproducible: No
SourcePackage: linux
TestedUpstream: Yes
Title: BUG: unable to handle kernel paging request at ffff8800ad905000
Uname: Linux 2.6.32-16-generic x86_64
dmi.bios.date: 10/27/2009
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A04
dmi.board.name: 0J372M
dmi.board.vendor: Dell Inc.
dmi.board.version: A04
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A04
dmi.modalias: dmi:bvnDellInc.:bvrA04:bd10/27/2009:svnDellInc.:pnStudio1440:pvrA04:rvnDellInc.:rn0J372M:rvrA04:cvnDellInc.:ct8:cvrA04:
dmi.product.name: Studio 1440
dmi.product.version: A04
dmi.sys.vendor: Dell Inc.

Revision history for this message
Whorehay (whorehay) wrote :
Revision history for this message
Chase Douglas (chasedouglas) wrote :

Note that the OopsText.txt has only the last oops message, which is not the most relevant. Check WifiSyslog.txt for previous Oops messages.

summary: - BUG: unable to handle kernel paging request at ffff8800ad905000
+ Corrupted low memory at ffff880000005df0 (5df0 phys) = e47700000000
Revision history for this message
Chase Douglas (chasedouglas) wrote :

This looks to be a pretty serious corruption. Is it possible for you to try running without the nvidia driver loaded? If you are able to reproduce without the nvidia driver we may be able to help. Otherwise the issue likely has to do with the nvidia driver, and we can't help with that because the nvidia driver is closed source.

Thanks

Changed in linux (Ubuntu):
status: New → Incomplete
importance: Undecided → Low
Revision history for this message
=0yP)F]|L(0YNrv (ccgjsz8xdbdyyvy-deactivatedaccount) wrote :

This problem just hit me. Ubuntu 10.04 LTS AMD64, full release. This error popped up, and now my entire kernel is corrupted. It won't even mount the root fs!

Revision history for this message
Manoj Iyer (manjo) wrote :

Can you please post BIOS details ? dmidecode information ?

Manoj Iyer (manjo)
Changed in linux (Ubuntu):
assignee: nobody → Manoj Iyer (manjo)
Revision history for this message
Manoj Iyer (manjo) wrote :

I will need the dmidecode information to see if this is happening on the same board or if this needs to be quirked by BIOS vendor. So if the originator of this bug and other who are seeing this problem will post their dmidecode information I will be able to supply a quirked kernel that you can try.

Revision history for this message
pj81381 (penjon) wrote :
Download full text (19.9 KiB)

I think Chase is right. I've had this problem on and off while trying the nvidia 195 drivers. Rolling back to the 173 driver typically has worked for me. I've seen it on Ubuntu 9.10 and Ubuntu 10.04 LTS, AMD64.

Here's my dmidecode info:

# dmidecode 2.9
SMBIOS 2.4 present.
63 structures occupying 2992 bytes.
Table at 0x000F0000.

Handle 0x0000, DMI type 208, 12 bytes
OEM-specific Type
 Header and Data:
  D0 0C 00 00 01 05 FE 00 EC 01 01 02
 Strings:
  20040101
  00000000

Handle 0x0001, DMI type 218, 47 bytes
OEM-specific Type
 Header and Data:
  DA 2F 01 00 2E 14 33 09 0E 10 00 05 80 05 80 01
  00 10 F5 10 F5 00 00 00 80 00 80 01 00 02 80 02
  80 01 00 00 A0 00 A0 01 00 FF FF 00 00 00 00
 Strings:

Handle 0x0002, DMI type 0, 24 bytes
BIOS Information
 Vendor: Dell Inc
 Version: 1.1.11
 Release Date: 08/02/2007
 Address: 0xE0000
 Runtime Size: 128 kB
 ROM Size: 512 kB
 Characteristics:
  ISA is supported
  PCI is supported
  PNP is supported
  APM is supported
  BIOS is upgradeable
  BIOS shadowing is allowed
  Boot from CD is supported
  Selectable boot is supported
  BIOS ROM is socketed
  EDD is supported
  5.25"/360 KB floppy services are supported (int 13h)
  5.25"/1.2 MB floppy services are supported (int 13h)
  3.5"/720 KB floppy services are supported (int 13h)
  3.5"/2.88 MB floppy services are supported (int 13h)
  Print screen service is supported (int 5h)
  8042 keyboard services are supported (int 9h)
  Serial services are supported (int 14h)
  Printer services are supported (int 17h)
  CGA/mono video services are supported (int 10h)
  ACPI is supported
  USB legacy is supported
  BIOS boot specification is supported
  Function key-initiated network boot is supported
  Targeted content distribution is supported
 BIOS Revision: 1.1

Handle 0x0003, DMI type 1, 27 bytes
System Information
 Manufacturer: Dell Inc
 Product Name: Dimension E521
 Version:
 Serial Number: G2L02D1
 UUID: 44454C4C-3200-104C-8030-C7C04F324431
 Wake-up Type: Power Switch
 SKU Number:
 Family:

Handle 0x0004, DMI type 188, 255 bytes
OEM-specific Type
 Header and Data:
  BC FF 04 00 4B 38 4E 50 54 44 52 41 4D 30 03 00
  00 00 00 00 2F 01 00 00 00 00 01 00 00 00 00 00
  00 00 02 00 00 00 00 00 00 00 03 00 00 00 00 00
  00 00 04 00 00 00 00 00 00 00 05 00 00 00 00 00
  00 00 06 00 00 00 00 00 00 00 07 00 00 00 01 30
  00 D0 40 00 10 0A 00 00 00 00 00 00 04 00 EF 02
  00 0C 01 00 00 00 01 01 00 00 01 02 00 00 01 03
  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
  00 00 E0 3C F8 00 E0 3C F8 00 00 00 00 00 00 00
  00 00 46 00 00 00 00 00 00 00 22 00 00 00 00 00
  00 00 13 91 16 0C 20 12 92 00 10 0C 01 00 79 80
  10 37 88 88 FF FE 15 14 15 15 15 14 14 15 15 00
  00 00 16 16 16 16 16 15 15 16 16 00 00 00 37 41
  00 00 15 14 15 14 14 15 14 15 15 16 16 16 16 17
  16 16 15 16 3A 44 00 00 22 13 11 10 00 2F 28 00
  22 13 11 10 00 2F 28 00 00 00 00 00 00 00 00
 Strings:

Handle 0x0005, DMI type 190, 255 bytes
OEM-specific Type
 Header and Data:
  BE FF 05 00 00 00 00 D0 00 00 00 00 00 00 00 30
  01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
  00 00 00 00 ...

Revision history for this message
pj81381 (penjon) wrote :

Some corrections to my previous comment. My issue might be slightly different: the computer locks up a few minutes after suspend-resume. The logs show the corrupted low memory message on resume. With 10.04, this still occurs regardless of the Nvidia driver (I had found rolling back the Nvidia driver helped a bit on 9.10).

Revision history for this message
nutznboltz (nutznboltz-deactivatedaccount) wrote :

Can you please test and report if this works?

memory_corruption_check_size=128K

in the boot options.

The default is

memory_corruption_check_size=64K

but it seems that's not enough for some systems.

Thanks

If you don't know how to set BootOptions read

https://help.ubuntu.com/community/BootOptions

Also this thread is very important to anyone looking at this bug

http://linux.derkeiler.com/Mailing-Lists/Kernel/2009-07/msg04621.html

tags: removed: regression-potential
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

Closing this bug with Won't fix as this kernel / release is no longer supported.
Please feel free to open a new bug report if you're still experiencing this on a newer release (Bionic 18.04.3 / Disco 19.04)
Thanks!

Changed in linux (Ubuntu):
status: Incomplete → Won't Fix
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.