Bug 648407 – Kernel panic due to recursive lock in 3c59x driver. [rhel-4.8.z]

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 648407 - Kernel panic due to recursive lock in 3c59x driver. [rhel-4.8.z]

Summary:	Kernel panic due to recursive lock in 3c59x driver. [rhel-4.8.z]

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Enterprise Linux 4
Classification:	Red Hat
Component:	kernel (Show other bugs)
Sub Component:
Version:	4.8
Hardware:	All Linux

Priority	low Severity medium
Target Milestone:	rc
Target Release:	---
Assigned To:	Don Howard
QA Contact:	Red Hat Kernel QE team
Docs Contact:

URL:
Whiteboard:
Keywords:	ZStream

Depends On:	557380
Blocks:
	Show dependency tree / graph

Reported:	2010-11-01 04:34 EDT by RHEL Product and Program Management
Modified:	2010-12-01 17:25 EST (History)
CC List:	7 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2010-12-01 17:25:26 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHSA-2010:0936	normal	SHIPPED_LIVE	Important: kernel security and bug fix update	2010-12-06 09:19:04 EST

Groups: None (edit)

Description RHEL Product and Program Management 2010-11-01 04:34:45 EDT

This bug has been copied from bug #557380 and has been proposed
to be backported to 4.8 z-stream (EUS).

Comment 3 Don Howard 2010-11-05 14:43:29 EDT

A patch addressing this issue has been included in kernel-2.6.9-89.32.1.

Comment 5 Igor Zhang 2010-11-28 21:45:37 EST

In https://bugzilla.redhat.com/show_bug.cgi?id=557380#c19,
(In reply to comment #3)
> Vitaly,
>   What I think we can do is reserve host dell-pe650-02.rhts.bos.redhat.com. run
> the /distribution/networking/ndnc test, This will configure netdump to dump
> across the network. Than manually initiate a Alt+SysRq+C to crash the system.

On dell-pe650-02.rhts.eng.bos.redhat.com, it's not easy to trigger this
problem.
It can pass through with following messages:
...
CPU#0 is executing netdump.
< netdump activated - performing handshake with the server. >
NETDUMP START!
< handshake completed - listening for dump requests. >
2(20000)|000)/
Pid: 4584, comm:                 bash
EIP: 0060:[<c0242c8b>] CPU: 0
....

Instead of:
...
CPU#0 is executing netdump.
< netdump activated - performing handshake with the server. >
<0>Kernel panic - not syncing: drivers/net/3c59x.c:2265:
spin_lock(drivers/net/3c59x.c:dfe2b1f4) already locked by
drivers/net/3c59x.c/2419

------------[ cut here ]------------
<1>kernel BUG at kernel/panic.c:77!
<1>invalid operand: 0000 [#2]
...

Should I inject more net console pressure ? Any advices?

Thanks
Igor

Comment 8 errata-xmlrpc 2010-12-01 17:25:26 EST

An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHSA-2010-0936.html

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