Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 118102
Summary: | (NET ACENIC)oops during bootup in ethtool | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Fred Isaman <iisaman> | ||||||
Component: | kernel | Assignee: | Jeff Garzik <jgarzik> | ||||||
Status: | CLOSED DUPLICATE | QA Contact: | Brian Brock <bbrock> | ||||||
Severity: | high | Docs Contact: | |||||||
Priority: | high | ||||||||
Version: | 2 | CC: | peterm, sahil.verma | ||||||
Target Milestone: | --- | ||||||||
Target Release: | --- | ||||||||
Hardware: | i386 | ||||||||
OS: | Linux | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2006-02-21 19:01:56 UTC | Type: | --- | ||||||
Regression: | --- | Mount Type: | --- | ||||||
Documentation: | --- | CRM: | |||||||
Verified Versions: | Category: | --- | |||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||
Embargoed: | |||||||||
Bug Depends On: | |||||||||
Bug Blocks: | 114963 | ||||||||
Attachments: |
|
Description
Fred Isaman
2004-03-11 22:25:11 UTC
Created attachment 98469 [details]
boot messages and scanpci dump
Looks like a driver bug. I guess the difference between FC2 test1 kernel and the vanilla / CITI kernels you're using is that the latter don't have SELinux compiled in, right? Does the oops happen if you don't bringup the eth interface in interactive startup but later using ifconfig? Do you get the same oops trace? Oh, silly me. It is totally obvious from your boot logs that SELinux is not enabled in vanilla / CITI kernels. If you boot FC2 test1 with selinux=0 the oops should go away. That doesn't explain the panic though. Yes, oops still happens if use interactive startup to avoid bringing up the eth interface and then later using ifconfig. Here is relevant snippet from bootup Start service network (Y)es/(N)o/(C)ontinue? [Y] Setting network parameters: [ OK ] Bringing up loopback interface: [ OK ] Start service eth1 (Y)es/(N)o/(C)ontinue? [Y] n Start service syslog (Y)es/(N)o/(C)ontinue? [Y] c Then as root `ifconfig eth1 up` causes basically same oops. Ok, at the boot menu press 'e' to edit the args and append 'selinux=0' to the 'kernel' line. Does that make the oops go away? Created attachment 98660 [details]
Boot log with oops (selinux=0)
Adding selinux=0 still has oops (with slightly different stack trace)
*** This bug has been marked as a duplicate of 119491 *** Changed to 'CLOSED' state since 'RESOLVED' has been deprecated. |