tcp_xmit_retransmit_queue panic in 2.6.31 in 9.10 server kernel

[Rhomboid]

This bug is mentioned in several places and was recently fixed in 10.04 (see #615548 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/615548). Links:

http://lkml.org/lkml/2010/1/5/179

http://kerneltrap.org/mailarchive/linux-kernel/2010/7/8/4591548

http://www.spinics.net/lists/stable-commits/msg07398.html

https://bugzilla.kernel.org/show_bug.cgi?id=14470#c51

I'm having to run generic kernels on 20 machines currently but have security concerns with trying to always track "current". Having to upgrade kernels and reboot far more often is painful as well.

Trying to run the stock kernel results in essentially a DoS steady state as systems are regularly oops'ing multiple times per day.

Is there any possibility of getting a new stable kernel for 9.10 with this fix included?

I couldn't actually get a dump on 9.10 because of this bug (that also has only been fixed in 10.04 and not 9.10):

https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/599601

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/321970

ProblemType: Bug
AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory
AplayDevices: Error: [Errno 2] No such file or directory
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
Date: Tue Oct 26 13:24:18 2010
DistroRelease: Ubuntu 9.10
MachineType: Supermicro X8DTT
Package: linux-image-2.6.31-22-server 2.6.31-22.67
PciMultimedia:

ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-22-server root=UUID=047fd2c1-753f-4188-8e72-c49e0a337c99 ro quiet splash
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-22.67-server
SourcePackage: linux
Uname: Linux 2.6.31-22-server x86_64
dmi.bios.date: 05/20/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 080016
dmi.board.asset.tag: 1234567890
dmi.board.name: X8DTT
dmi.board.vendor: Supermicro
dmi.board.version: 2.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 17
dmi.chassis.vendor: Supermicro
dmi.chassis.version: 1234567890
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080016:bd05/20/2010:svnSupermicro:pnX8DTT:pvr1234567890:rvnSupermicro:rnX8DTT:rvr2.0:cvnSupermicro:ct17:cvr1234567890:
dmi.product.name: X8DTT
dmi.product.version: 1234567890
dmi.sys.vendor: Supermicro

[Jeremy Foshee (jeremyfoshee)]

Hi Rhomboid,

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 667056

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

[Rhomboid (rhomboid)]

It's still a bug. The point is that I can NOT upgrade the machines to a development release, they're commercial production machines that need to be as stable as possible. I would have upgraded to 10.04 but couldn't risk it in the time frame I had before needing to lock the system down for a project. I will be able to upgrade to a newer release sometime early next year.

My "fix" currently is to run the upstream kernel so I'm already doing that. My only worry was inheriting a new bug or security issue introduced during rapid upstream kernel development.

I was hoping to see 9.10 get a fixed kernel that will get "normal" security updates.

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