Bug 101290 - [AIO] lockup on hammer
Summary: [AIO] lockup on hammer
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: kernel   
(Show other bugs)
Version: 3.0
Hardware: x86_64 Linux
high
high
Target Milestone: ---
Assignee: Jeff Moyer
QA Contact: Brian Brock
URL:
Whiteboard:
Keywords:
: 103240 (view as bug list)
Depends On:
Blocks: 97942
TreeView+ depends on / blocked
 
Reported: 2003-07-30 17:06 UTC by Jakub Jelinek
Modified: 2007-11-30 22:06 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2003-09-03 13:02:49 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description Jakub Jelinek 2003-07-30 17:06:25 UTC
Description of problem:
It seems hammer kernels lock up when doing make check in rtkaio.
Reproduced twice on thor and once on romaine. Does not seem to lock up on other arches.
Version-Release number of selected component (if applicable):


How reproducible:
rpmbuild --rebuild ~jakub/glibc-2.3.2-66.src.rpm

Comment 1 Jakub Jelinek 2003-07-30 17:07:22 UTC
Oops, sorry.

Comment 2 Elliot Lee 2003-07-30 17:13:36 UTC
The call trace was inside __wtd_down_failed inside generic_aio_rw inside 
generic_aio_complete_write

The kernel is 2.4.21-1.1931.2.342.entsmp

Comment 4 Jim Paradis 2003-08-28 03:16:23 UTC
*** Bug 103240 has been marked as a duplicate of this bug. ***

Comment 5 John W. Lockhart 2003-08-28 03:34:38 UTC
Takes about 5 minutes to reproduce using the aiotest
in Bug 103240, which also has a full console capture.



Comment 7 Jeff Moyer 2003-09-02 13:23:07 UTC
The arguments to wtd_down_common were swapped, causing the kernel to try to lock
something that wasn't a lock.  Fix is in latest taroon.

Comment 8 Jay Turner 2003-09-03 13:02:49 UTC
Fix confirmed on Melody box in lab running 2.4.21-1.1931.2.421.ent.


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