Red Hat Bugzilla – Bug 1008323
Kernel 3.11.1 panic
Last modified: 2013-10-02 02:35:57 EDT
Created attachment 798131 [details]
Kernel panic screenshot.
Description of problem:
Kernel 3.11.1 from koji panic after about ten seconds of boot.
Version-Release number of selected component (if applicable):
Kernel 3.10.11 and early work normal.
Processor Intel Pentium 4.
Panic photo is attached.
thanks for the report. The following changes took place in that driver from 3.10 to 3.11:
* e47851f - (2013-08-13 15:09:06 -0700) skge: dma_sync the whole receive buffer <stephen hemminger>
* f7b7a36 - (2013-08-04 23:36:45 -0700) skge: fix build on 32 bit <Stephen Hemminger>
* 136d8f3 - (2013-08-04 18:35:01 -0700) skge: add dma_mapping check <stephen hemminger>
* 351638e - (2013-05-28 13:11:01 -0700) net: pass info struct via netdevice notifier <Jiri Pirko>
So one of these is the culprit. Two questions:
- Are you able to reproduce this 100% of the time?
- Would you be able to bisect which of the four commits (136d8f3 and e47851f are the most likely ones) introduced this issue or do you need help with that?
Thanks and regards,
I can reproduce it 100% of the time.
And I need help with build kernel without this commits.
Can you give me four kernel-3.11.1 rpm packages with disabled one of commits?
Michele, thanks for the info!
I prepare builds for testing.
Vasiliy, please test builds from here: http://ignatenkobrain.asuscomm.com:8080/kernel/ and inform us about tests.
Take this bug until find bad commit more accurately.
I checked kernels.
Panic not occur only on 351638e. On other kernel goes to panic with same backtrace.
thanks a lot for testing. So * 136d8f3 - (2013-08-04 18:35:01 -0700) skge: add dma_mapping check <stephen hemminger> is the regression commit.
Igor, do you want to take this to netdev or want me to do it?
(In reply to Michele Baldessari from comment #5)
> Hi Vasiliy,
> thanks a lot for testing. So * 136d8f3 - (2013-08-04 18:35:01 -0700) skge:
> add dma_mapping check <stephen hemminger> is the regression commit.
> Igor, do you want to take this to netdev or want me to do it?
please do tihs.
found this bug at KBZ
*********** 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 19 kernel bugs.
Fedora 19 has now been rebased to 3.11.1-200.fc19. Please test this kernel update and let us know if you issue has been resolved or if it is still present with the newer kernel.
If you experience different issues, please open a new bug report for those.
Josh, this issue present exactly in 3.11.1-200.fc19
Started discussion at maillists: https://lkml.org/lkml/2013/9/18/64
Please test: http://koji.fedoraproject.org/koji/taskinfo?taskID=5957449
Please apply as downstream patch from Mikulas.
Applied. Thank you for driving this forward.
Josh, in the future we should apply http://permalink.gmane.org/gmane.linux.network/284249 like this patch.. but I think not needed rush..
second part of patch from Mikulas http://permalink.gmane.org/gmane.linux.network/284277 but its not signed by netdevs
The original description was about the 64-bit version of kernel-3.11.1-200.
Needless to say, this applies also to the 32-bit version.
The crash occurs about 10-15 seconds after boot ends: you have the time to log in, and to start an application (browser, mailer, ....), and then you got what the picture attached to the original description shows.
Additional question : the boot menu presents the last three installed versions of the kernel, with the last one as the default. Can this buggy 3.11.1 kernel version be uninstalled while keeping the 2 others (just for the sake of getting rid of the burden of manually selecting a healthy 3.10 version at boot time) ?
This is also my case - wainting for patch working on kernel-3.10.11.
amreg, you can remove 3.11.1 kernel by command
yum remove "kernel-3.11.1*"
Josh, please apply second part of fix this bug:
Added the second patch as well. Thanks.
*** Bug 1011632 has been marked as a duplicate of this bug. ***
kernel-3.11.2-201.fc19 has been submitted as an update for Fedora 19.
I test kernel:
Net up! All good works ! Thanks.
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing kernel-3.11.2-201.fc19'
as soon as you are able to, then reboot.
Please go to the following url:
then log in and leave karma (feedback).
Bug solved in this update.
When (In reply to Vasiliy Glazov from comment #25)
> Bug solved in this update.
When this update will be released?
Rostislav, you can install and use it now from koji. But this kernel may not be in updates at all because have some other problems.
Vasiliy, if I install Fedora 19 it updates all packages, including the kernel, automatically. Then I have Fedora 19 with the 3.11.1 kernel and without any network because of the skge regression. At least it doesn't panic on my hardware configuration. Is it possible to downgrade the kernel to a previous (3.10.11 ?) version after the installation? I mean, does Fedora installer save previous (or at least original) versions or it installs the latest rpm's straight away?
When Fedora update kernel it leave three last installed kernels. So you choose previous kernel in Grub menu, load and manually update kernel to 3.11.2.
kernel-3.11.2-301.fc20 has been submitted as an update for Fedora 20.
(In reply to Vasiliy Glazov from comment #18)
> amreg, you can remove 3.11.1 kernel by command
> yum remove "kernel-3.11.1*"
Thanks for the hint. In my case, it should rather be:
> yum remove "kernel-PAE-3.11.1*"
(I don't know why, but my box uses PAE fashions of the kernel).
I hope the patch would make its way in the PAE releases as well as in the "normal (?)" releases?
Basically, just mentioning the exact "base" kernel package name in yum (i.e. kernel-PAE-3.11.1-200.fc19") should release as well dependant packages for the same version (such as headers, doc, ...)?
kernel-3.11.2-201.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
kernel-3.11.2-301.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.