linux-image-2.6.20-16-generic: invalid opcode: 0000 [#1]

[Christian Holtje]

Binary package hint: linux-image-2.6.20-16-generic

I just got this error. I have rebooted just to be sure (but I saved info, I'll append it in a minute).

 I had problems before with bug #135294, but this is different. I turned off swap and the system was up for a while before this problem:

invalid opcode: 0000 [#1]
SMP
Modules linked in: xt_tcpudp iptable_filter ip_tables x_tables psmouse serio_raw i2c_voodoo3 i2c_algo_bit via_agp pcspkr i2c_viapro via686a i2c_isa i2c_core parport_pc parport shpchp pci_hotplug agpgart tsdev evdev ide_cd cdrom ide_disk 8139cp generic floppy uhci_hcd usbcore 8139too mii via82cxxx ata_generic libata scsi_mod raid10 raid456 xor raid1 raid0 multipath linear md_mod thermal processor fan fbcon tileblit font bitblit softcursor vesafb capability commoncap reiserfs dm_mod
CPU: 0
EIP: 0060:[<c02b6530>] Not tainted VLI
EFLAGS: 00010202 (2.6.20-16-generic #2)
EIP is at tcp_transmit_skb+0x220/0x810
eax: 00000401 ebx: 001fffe0 ecx: 00000005 edx: 00000005
esi: e9397b60 edi: 00008020 ebp: f461b4f0 esp: cce8fe48
ds: 007b es: 007b ss: 0068
Process amavisd-new (pid: 14260, ti=cce8e000 task=e91eb050 task.ti=cce8e000)
Stack: c027a377 000003f1 00000000 00000000 cce8fe5c 00000000 d9db2eb0 cce8fedc
       00000000 d9db2ee0 00000020 00000000 00000000 00000400 cce8ff60 c0159cf1
       e9397b60 d9db2e00 00000000 80ec4c1f c02b80fd 00000020 00000000 00000000
Call Trace:
 [<c027a377>] sock_common_recvmsg+0x47/0x70
 [<c0159cf1>] generic_file_aio_read+0x101/0x250
 [<c02b80fd>] __tcp_push_pending_frames+0x11d/0x890
 [<c027ea23>] __alloc_skb+0x53/0x120
 [<c02b9727>] tcp_send_fin+0x57/0x150
 [<c02ad606>] tcp_close+0x496/0x620
 [<c027aab2>] release_sock+0x12/0xb0
 [<c02ca464>] inet_release+0x34/0x60
 [<c0278f4a>] sock_release+0x1a/0x80
 [<c027920e>] sock_close+0x1e/0x40
 [<c01776e7>] __fput+0xa7/0x190
 [<c0174a87>] filp_close+0x47/0x80
 [<c0175deb>] sys_close+0x6b/0xd0
 [<c01031f0>] sysenter_past_esp+0x69/0xa9
 [<c02e0033>] xfrm_state_find+0x323/0x570
 =======================
Code: 00 00 bb ff ff 00 00 89 f8 89 d1 c0 e9 04 d3 e3 39 df 76 02 89 d8 c0 ea 04 89 d1 d3 e8 85 c0 75 0a c7 86 a8 02 00 00 00 00 00 00 <0f> a7 c0 89 c2 c1 e2 08 c1 e8 08 09 c2 66 89 55 0e 66 c7 45 10
EIP: [<c02b6530>] tcp_transmit_skb+0x220/0x810 SS:ESP 0068:cce8fe48

[Christian Holtje (docwhat)]

Note to self: Saved as 200709111628

[Ralph Janke (txwikinger)]

Thank you for taking the time to report this bug and helping to make Ubuntu better.

Could you please check if this problem still occurs in the newest hardy kernel.

Thanks

[Launchpad Janitor (janitor)]

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 bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

[Leann Ogasawara (leannogasawara)]

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.

[Michele Mangili (mangilimic)]

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!