FS#27852 - [linux] Kernel panic when upgrading linux from 3.0.7-1 to 3.1.7-1

Attached to Project: Arch Linux
Opened by Jan Rüegg (rggjan) - Friday, 06 January 2012, 16:37 GMT
Last edited by Tobias Powalowski (tpowa) - Sunday, 25 March 2012, 12:43 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Tobias Powalowski (tpowa)
Thomas Bächler (brain0)
Architecture i686
Severity Critical
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

When upgrading the linux kernel from 3.0.7-1 to 3.1.7-1 I get a segfault soon after rebooting. This is on a up-to-date i686 arch, using a compaq nx7000 laptop.

I also tried a clean net install. While the installer (and obviously the kernel on archlinux-2011.08.19-netinstall-i686.iso) work fine, I get a kernel panic again as soon as I restart into the newly installed system.

I tried to capture the panic with netconsole, but I get only the "normal" dmesg messages with netconsole, the panic itself is not sent over the network. Also, I don't get a kernel panic right away when booting. Xserver and gnome start just fine, but as soon as I open a console and start a pacman upgrade, the system crashes. This makes me thing it might have to do with network activity...

Reverting to the older kernel resolves the problem.

I'll be happy to provide more information when needed.
This task depends upon

Closed by  Tobias Powalowski (tpowa)
Sunday, 25 March 2012, 12:43 GMT
Reason for closing:  Fixed
Comment by Biro Balazs (scar) - Sunday, 08 January 2012, 10:54 GMT
I have the same kind of panic, only caused by TCP/IP traffic.

What kind of network card do you use?
Mine is Realtek 8139 with the 8139cp module.

Comment by Jan Rüegg (rggjan) - Friday, 13 January 2012, 15:37 GMT
Yes, exactly:

lspci | grep Realtek
02:01.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 20)

lsmod | grep 8139
8139too 17344 0
8139cp 16173 0
mii 3375 2 8139too,8139cp
Comment by Biro Balazs (scar) - Monday, 23 January 2012, 21:43 GMT
Still not fixed in 3.2, could anyone report this upstream?
Comment by Denis (tankopunk) - Tuesday, 31 January 2012, 17:23 GMT
Same kernel panic, but i have broadcom adapter

02:00.0 Ethernet controller: Broadcom Corporation NetLink BCM5787M Gigabit Ethernet PCI Express (rev 02)

Loading...