Bug 135590

Summary: 8021q vs. 3c59x crash
Product: [Fedora] Fedora Reporter: Jan Kratochvil <jan>
Component: kernelAssignee: Dave Jones <davej>
Status: CLOSED RAWHIDE QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: 3CC: pfrields, wtogami
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2004-10-13 20:50:20 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:

Description Jan Kratochvil 2004-10-13 17:51:34 UTC
Description of problem:

Loading 8021q crashed the kernel (panic). After reboot only harmless
warnings below produced. To be retested after the fix delivery.

Version-Release number of selected component (if applicable):
2.6.8-1.541.i686

How reproducible:
    vconfig add eth1 3
where eth1 is 3c59x handled. No packets are required for the warning
below.

Actual results:
drivers/net/3c59x.c:2991: spin_is_locked on uninitialized spinlock
074f4880.
drivers/net/3c59x.c:3012: spin_is_locked on uninitialized spinlock
074f4880.
drivers/net/3c59x.c:2991: spin_is_locked on uninitialized spinlock
074f4880.
drivers/net/3c59x.c:3012: spin_is_locked on uninitialized spinlock
074f4880.
drivers/net/3c59x.c:2991: spin_is_locked on uninitialized spinlock
074f4880.
drivers/net/3c59x.c:3012: spin_is_locked on uninitialized spinlock
074f4880.
drivers/net/3c59x.c:2991: spin_is_locked on uninitialized spinlock
074f4880.
drivers/net/3c59x.c:3012: spin_is_locked on uninitialized spinlock
074f4880.
drivers/net/3c59x.c:2991: spin_is_locked on uninitialized spinlock
074f4880.
drivers/net/3c59x.c:3012: spin_is_locked on uninitialized spinlock
074f4880.

Expected results:
no warnings.

Additional info:

Comment 1 Jan Kratochvil 2004-10-13 18:52:30 UTC
2.6.8-1.610.i686 of RawHide works fine, therefore not sure if it makes
sense to deal with this Bug.