Kernel BUG during heavy I/O on a cryptsetup-LUKS over LVM over RAID1 partition

[Stéphane Lesimple]

The ubuntu-bug tool has been executed after a reboot, because after the kernel BUG, the machine refused any SSH connection to it (connection reset by peer).

ProblemType: Bug
AplayDevices: Error: [Errno 2] No such file or directory
Architecture: i386
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/pcmC0D1p: root 1542 F...m python
                      root 2171 F.... python
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info: Error: [Errno 2] No such file or directory
Card0.Amixer.values: Error: [Errno 2] No such file or directory
Date: Tue Feb 16 10:00:59 2010
DistroRelease: Ubuntu 9.10
IwConfig: Error: [Errno 2] No such file or directory
Package: linux-image-2.6.31-19-generic-pae 2.6.31-19.56
PciMultimedia:

ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.31-19-generic-pae root=/dev/mapper/vg0-lv_all ro debug acpi_enforce_resources=lax
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-19.56-generic-pae
RelatedPackageVersions:
 linux-backports-modules-2.6.31-19-generic-pae N/A
 linux-firmware 1.25
RfKill: Error: [Errno 2] No such file or directory
SourcePackage: linux
Uname: Linux 2.6.31-19-generic-pae i686
dmi.bios.date: 07/29/2009
dmi.bios.vendor: Intel Corp.
dmi.bios.version: LF94510J.86A.0229.2009.0729.0209
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: D945GCLF2
dmi.board.vendor: Intel Corporation
dmi.board.version: AAE46416-103
dmi.chassis.type: 3
dmi.modalias: dmi:bvnIntelCorp.:bvrLF94510J.86A.0229.2009.0729.0209:bd07/29/2009:svn:pn:pvr:rvnIntelCorporation:rnD945GCLF2:rvrAAE46416-103:cvn:ct3:cvr:

[Stéphane Lesimple (speed47)]

The actual BUG is in the WifiSyslog.txt file (even if it has nothing to do with Wi-Fi : the box doesn't even have a Wi-Fi chip)

[Stéphane Lesimple (speed47)]

The NULL pointer dereference happened when copying data on the main storage partition (the box is actually a NAS) over an Ethernet (100 Mbits) connection. The storage is exported via Samba/CIFS.

[Jeremy Foshee (jeremyfoshee)]

Hi Stéphane,

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 522522

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.

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

[Stéphane Lesimple (speed47)]

As the Lucid release is now very close, I'll wait till its GA, upgrade, and try to make the kernel BUG happen again.
If it does happen, I'll test with the vanilla kernel as you suggested.

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