Bug 248834 - kobject_add failed for brport, kernel BUG at net/core/net-sysfs.c
Summary: kobject_add failed for brport, kernel BUG at net/core/net-sysfs.c
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy-targeted (Show other bugs)
(Show other bugs)
Version: rawhide
Hardware: x86_64 Linux
Target Milestone: ---
Assignee: Daniel Walsh
QA Contact: Ben Levenson
Depends On:
TreeView+ depends on / blocked
Reported: 2007-07-19 03:08 UTC by Anssi Johansson
Modified: 2007-11-30 22:12 UTC (History)
3 users (show)

Fixed In Version: 2.6.4-29.fc7
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-07-28 13:17:59 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
syslog with the kernel error messages (43.03 KB, text/plain)
2007-07-19 03:08 UTC, Anssi Johansson
no flags Details
crash log (12.78 KB, text/plain)
2007-07-26 09:16 UTC, Felix Schwarz
no flags Details

Description Anssi Johansson 2007-07-19 03:08:44 UTC
Description of problem:
Upgraded to kernel-xen-2.6.20-2925.13.fc7 (from updates-testing) and tried to
create a new Xen guest with virt-install. I got the following error message:

kernel BUG at net/core/net-sysfs.c:429!
invalid opcode: 0000 [1] SMP

The full syslog is attached, but here's the interesting part:

xen kernel: kobject_add failed for brport (-13)
xen kernel: Call Trace:
xen kernel:  [<ffffffff8031dce6>] kobject_add+0x163/0x18e
xen kernel:  [<ffffffff8823a493>] :bridge:br_add_if+0x1d2/0x2d8
xen kernel:  [<ffffffff8823ab7d>] :bridge:add_del_if+0x41/0x5e
xen kernel:  [<ffffffff8823b203>] :bridge:br_dev_ioctl+0x669/0x6a2

( with some SELinux errors, see bug 245274 comment 13 )

MySQL was running on the server when I got that error message, and it continued
running fine despite this error. However, I was no longer able to ssh into the
server. I tried rebooting the server remotely with 'shutdown -r now', but for
some unknown reason the server didn't shut down properly and I had to visit our
server room to power cycle the server. 

The previous version (2.6.20-2925.11) didn't crash like this.

This is on Dell Poweredge 2900, with two integrated NICs and a four port D-Link
DFE-580TX, which is hidden from Domain0 with

Version-Release number of selected component (if applicable):

How reproducible:
Haven't tried to reproduce the problem yet

Steps to Reproduce:
1. boot with kernel-xen-2.6.20-2925.13
2. run virt-install to create a new guest image:
[root@xen ~]# virt-install
Would you like a fully virtualized guest (yes or no)?  This will allow you to
run unmodified operating systems. no
 What is the name of your virtual machine? gw
 How much RAM should be allocated (in megabytes)? 384
 What would you like to use as the disk (path)? /var/lib/xen/images/gw
 Would you like to enable graphics support? (yes or no) no
 What is the install location?
3. Crash!
Actual results:
Kernel crash

Expected results:
New Xen virtual machine created successfully

Comment 1 Anssi Johansson 2007-07-19 03:08:44 UTC
Created attachment 159574 [details]
syslog with the kernel error messages

Comment 2 Red Hat Bugzilla 2007-07-25 01:43:15 UTC
change QA contact

Comment 3 Felix Schwarz 2007-07-26 09:13:01 UTC
I see this bug, too (using 2.6.20-2925.11.fc7xen on x86_64). I can reproduce
this issue when doing 'xm create xenguest' which worked previously and stopped
working immediately after updating to selinux-policy-2.6.4-28.fc7 and

Before the SElinux update there was an SElinux denial, immediately afterwards I
got a "invalid opcode: 0000 [1] SMP" message on all consoles. Therefore I
suspect an SElinux issue and think the component should be changed to selinux.

Comment 4 Felix Schwarz 2007-07-26 09:16:18 UTC
Created attachment 159998 [details]
crash log

Attached you find call trace messages from Linux.

Comment 5 Anssi Johansson 2007-07-28 02:30:15 UTC
selinux-policy-targeted-2.6.4-29.fc7 doesn't seem to exhibit this problem any more.

Comment 6 Eduardo Habkost 2007-07-28 02:33:44 UTC
(In reply to comment #5)
> selinux-policy-targeted-2.6.4-29.fc7 doesn't seem to exhibit this problem 
any more.

Good. Should I close this bug?

Comment 7 Felix Schwarz 2007-07-28 09:37:59 UTC
selinux-policy-targeted-2.6.4-29.fc7 fixes the problem for me too so I think
this bug can be closed.

The only thing I noticed is that the changelog entry in the -29 rpm for the
latest revision is empty.

Comment 8 Eduardo Habkost 2007-07-28 13:17:59 UTC
Closing the bug. Changing component just to keep it recorded on the right 
component on bugzilla.

Note You need to log in before you can comment on or make changes to this bug.