Kernel panic with r1000 network card

[Pedro Côrte-Real]

I have an Asus P5B motherboard that has an integrated realtek gigabit network card:

03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. Unknown device 8168 (rev 01)

This is handled by the r1000 driver. On boot there's sometimes a kernel panic when this driver is in use. I've tried to blacklist it and confirmed that it stops happening. I made the computer reboot continuously for several hours and the panic only happens if the r1000 driver has been loaded.

This is using a Core 2 Duo so it's an SMP system. I guess something in the initialization of the card isn't SMP safe and is causing some kind of race condition.

[Kyle McMartin (kyle)]

Can you edit the grub command line and remove the "quiet" and "splash" options, and try booting? Getting a photo or a transcription of the kernel panic message is needed to debug this.
Also, you surely mean the "r8169" driver? I'm not sure what "r1000" is, but r8169 is the realtek gigabit driver in the kernel tree.

[Pedro Côrte-Real (pedrocr)]

The panic fills the whole screen so removing quiet and splash shouldn't be needed. I'll get a photo of the panic trace. The driver is called r1000, at least that's the module name. Attached is a full dmesg log of a boot that has worked. Most of them do. Probably one in 20 or 30 crashes.

[Pedro Côrte-Real (pedrocr)]

Here's the lsmod output.

[Pedro Côrte-Real (pedrocr)]

This probably happens because of network activity when setting up the driver. Because of SMP packets are probably received before the driver is fully initialized. Before dual-core processors this was probably never noticed. Does anyone care about this bug report?

[Adam Niedling (krychek)]

Please try if you get kernel panic with a later version of kernel/Ubuntu.

[Sergio Zanchetta (primes2h)]

The 18 month support period for Edgy Eft 6.10 has reached it's end of life. As a result, we are closing the linux-source-2.6.17 Edgy Eft kernel task.

[Sergio Zanchetta (primes2h)]

Hardy Heron 8.04 was recently released. It would be helpful if you could test the new release and verify if this is still an issue - http://www.ubuntu.com/getubuntu/download . You should be able to test your bug using the LiveCD. Please let us know your results. 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.

[Markus Korn (thekorn)]

Unfortunately this bug report is being closed because we received no response to the last inquiry for information. However, the Intrepid Ibex 8.10 Beta release was most recently announced - http://www.ubuntu.com/testing/intrepid/beta . If you are able to confirm this is still an issue with this most recent release please feel free to reopen this report. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New".

Thanks,
Markus