Description of problem: Since upgrading to the 3.16 i686+PAE kernel, I've been seeing intermittent panics in IRQ handling, going through netif_receive_skb. Here are some pictures: http://i.imgur.com/X6l42WG.jpg http://i.imgur.com/2IDLwLV.jpg Version-Release number of selected component (if applicable): Fedora kernel package 3.16.3-200.fc20.i686+PAE How reproducible: Unknown. Steps to Reproduce: n/a Actual results: Kernel panics. No information about the panic is written to any logs. Expected results: System should not panic. Additional info:
Output of `lshw -sanitized`: https://gist.github.com/slingamn/f9de6d1213bc1e20f449
looks like maybe b44 is add a null frag to the end of the frag list?
Here's a different stack trace (still the same kernel): http://i.imgur.com/mHfbbTX.jpg http://i.imgur.com/e8j3avc.jpg
Here's a slightly different trace from the 3.16.6-200.fc20.i686+PAE kernel: http://i.imgur.com/8TFeTPm.jpg If it would help for debugging, I have a reasonably good (albeit unscientific) way to provoke these now.
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 20 kernel bugs. Fedora 20 has now been rebased to 3.17.2-200.fc20. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 21, and are still experiencing this issue, please change the version to Fedora 21. If you experience different issues, please open a new bug report for those.
This is still present in 3.17.2-200.fc20.i686+PAE: http://i.imgur.com/7tEAXhX.jpg
I installed the mainline 3.18 kernel from here: https://repos.fedorapeople.org/repos/thl/kernel-vanilla-mainline/ then reproduced the panic and reported it to the kernel bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=89611 Any suggestions on people to cc there?
(In reply to Shivaram Lingamneni from comment #7) > I installed the mainline 3.18 kernel from here: > > https://repos.fedorapeople.org/repos/thl/kernel-vanilla-mainline/ > > then reproduced the panic and reported it to the kernel bugzilla: > > https://bugzilla.kernel.org/show_bug.cgi?id=89611 > > Any suggestions on people to cc there? You're likely better off emailing a problem report directly to the netdev mailing list. The maintainer info for the b44 driver is below: [jwboyer@vader linux]$ ./scripts/get_maintainer.pl -f drivers/net/ethernet/broadcom/b44.c Gary Zambrano <zambrano> (supporter:BROADCOM B44 10/1...) netdev.org (open list:BROADCOM B44 10/1...) linux-kernel.org (open list)
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 20 kernel bugs. Fedora 20 has now been rebased to 3.18.7-100.fc20. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 21, and are still experiencing this issue, please change the version to Fedora 21. If you experience different issues, please open a new bug report for those.
Here are some panics against 3.18.7-200.fc21: http://i.imgur.com/5vq7wXf.jpg http://i.imgur.com/SQbwnMG.jpg
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 21 kernel bugs. Fedora 21 has now been rebased to 3.19.5-200.fc21. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 22, and are still experiencing this issue, please change the version to Fedora 22. If you experience different issues, please open a new bug report for those.
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '21'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 21 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.