Bug 237016 - Booting is very long due to probing of non-existent ata3, and ata4.
Booting is very long due to probing of non-existent ata3, and ata4.
Status: CLOSED CURRENTRELEASE
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: kernel (Show other bugs)
5.0
x86_64 Linux
medium Severity medium
: ---
: ---
Assigned To: Jeff Garzik
Martin Jenner
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2007-04-18 17:38 EDT by Homayoun Shahri
Modified: 2013-07-02 22:32 EDT (History)
3 users (show)

See Also:
Fixed In Version: 5.1
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2007-09-07 16:27:34 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Homayoun Shahri 2007-04-18 17:38:33 EDT
Description of problem:
non-existent ata3, and ata4 are probed at boot time

Version-Release number of selected component (if applicable):
Linux homayoun 2.6.18-8.1.1.el5 #1 SMP Mon Feb 26 20:37:57 EST 2007 x86_64
x86_64 x86_64 GNU/Linux

How reproducible:
Always, just boot the system

Steps to Reproduce:
1.Boot
2.Observe!
3.
  
Actual results:
It takes a long time to boot, due waiting for time out on non-existent ata3, and
ata4.
The following messages are printed from dmseg:
ata3: SATA max UDMA/133 cmd 0xFE40 ctl 0xFE52 bmdma 0xFED0 irq 50
ata4: SATA max UDMA/133 cmd 0xFE60 ctl 0xFE72 bmdma 0xFED8 irq 50
scsi2 : ata_piix
ata3: port is slow to respond, this delay is known to occur on vacant SATA ports
ata3: port failed to respond (30 secs)
ata3: SRST failed (status 0xFF)
ata3: SRST failed (err_mask=0x100)
ata3: softreset failed, retrying in 5 secs
ata3: SRST failed (status 0xFF)
ata3: SRST failed (err_mask=0x100)
ata3: softreset failed, retrying in 5 secs
ata3: SRST failed (status 0xFF)
ata3: SRST failed (err_mask=0x100)
ata3: reset failed, giving up
scsi3 : ata_piix
ata4: port is slow to respond, this delay is known to occur on vacant SATA ports
ata4: port failed to respond (30 secs)
ata4: SRST failed (status 0xFF)
ata4: SRST failed (err_mask=0x100)
ata4: softreset failed, retrying in 5 secs
ata4: SRST failed (status 0xFF)
ata4: SRST failed (err_mask=0x100)
ata4: softreset failed, retrying in 5 secs
ata4: SRST failed (status 0xFF)
ata4: SRST failed (err_mask=0x100)
ata4: reset failed, giving up

Expected results:
It should be detected that ata3, and ata4 do not exist.

Additional info:
Comment 1 Homayoun Shahri 2007-04-19 12:39:24 EDT
I compiled and ran kernel 2.6.20. This version of the kernel fixes the issue
that I have mentioned above. There is still about 1 or 2 seconds of delay, but
no where near the 2 minutes it used to take with redhat's kernel 2.6.18.
Comment 2 Peter Martuccelli 2007-04-19 12:53:27 EDT
This will be fixed in the SATA update for R5.1.
Comment 3 RHEL Product and Program Management 2007-04-19 13:16:58 EDT
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release.  Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products.  This request is not yet committed for inclusion in an Update
release.
Comment 6 Thorsten Scherf 2007-06-29 10:50:17 EDT
is there already a rawhide kernel which has the fix included?
Comment 9 Homayoun Shahri 2007-11-19 19:18:22 EST
The new 2.6.18-53 (rhel 5.1) fixes this issue.


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