kernel failed assertions

Bug #165152 reported by Dave Love
6
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: linux-image-2.6.15-29-server

On an up-to-date dapper server system I got the following in syslog and
no other diagnostics as far as I can see:

Nov 26 01:16:16 bagpuss kernel: [50074012.610000] KERNEL: assertion (!sk->sk_forward_alloc) failed at net/core/stream.c (279)
Nov 26 01:16:16 bagpuss kernel: [50074012.610000] KERNEL: assertion (!sk->sk_forward_alloc) failed at net/ipv4/af_inet.c (148)

Revision history for this message
Julius Bloch (jbloch) wrote :

Hi,
thanks for your bugreport.
There is linux-image-2.6.15-23-server available for dapper. Does the problem/error appear again with this kernel version?
Do you see any problems running linux-image-2.6.15-29-server? Or is there just the syslog entries?

Changed in linux-source-2.6.15:
status: New → Incomplete
Revision history for this message
Dave Love (fx-gnu) wrote :

JuliusBloch <email address hidden> writes:

> Hi,
> thanks for your bugreport.
> There is linux-image-2.6.15-23-server available for dapper. Does the
> problem/error appear again with this kernel version?

I don't know. I no longer work at the place where that system was
running.

Revision history for this message
azzegai (jp-theant) wrote :

Hi Julius,
Just to confirm that the above error occurs in the linux-image-2.6.15-51-server (uname: 2.6.15-51-server). ethtool output on the NIC is:

driver: e1000
version: 7.0.33-k2
firmware-version: N/A
bus-info: 0000:05:01.0

Revision history for this message
azzegai (jp-theant) wrote :

This seems to be a bug in the e1000 kernel module, see http://marc.info/?l=linux-netdev&m=114368730330622&w=2 for more info. Looks like this bug was still present up to and including kernel version 2.6.16. Not sure if it has been fixed since, but I'm not getting these kernel warnings on another server of mine running a 2.6.21 kernel and using an e1000 NIC.

The following post suggests that a work around is to run 'ethtool -K ethX tso off': http://marc.info/?l=linux-netdev&m=114324941105614&w=2 . I haven't tried this out yet, but will report back once I've got results on this.

Revision history for this message
Launchpad Janitor (janitor) wrote : This bug is now reported against the 'linux' package

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this linux-source-2.6.15 kernel bug to the new "linux" package. We appreciate your patience and understanding as we make this transition. Also, if you would be interested in testing the upcoming Intrepid Ibex 8.10 release, it is available at http://www.ubuntu.com/testing . Please let us know your results. Thanks!

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Revision history for this message
Michele Mangili (mangilimic) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in linux:
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.