linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugme-daemon@bugzilla.kernel.org
To: linux-ide@vger.kernel.org
Subject: [Bug 11015] New: Delay on boot: fails to IDENTIFY ata2.01 (I/O error, err_mask=0x1)
Date: Mon, 30 Jun 2008 17:06:52 -0700 (PDT)	[thread overview]
Message-ID: <bug-11015-11633@http.bugzilla.kernel.org/> (raw)

http://bugzilla.kernel.org/show_bug.cgi?id=11015

           Summary: Delay on boot: fails to IDENTIFY ata2.01 (I/O error,
                    err_mask=0x1)
           Product: IO/Storage
           Version: 2.5
     KernelVersion: 2.6.25.6
          Platform: All
        OS/Version: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: IDE
        AssignedTo: io_ide@kernel-bugs.osdl.org
        ReportedBy: jon@kapla.se


Latest working kernel version: 2.6.24
Earliest failing kernel version: 2.6.25.4
Distribution: Arch Linux
Hardware Environment: asus a7n8x-x motherboard with nforce2 chipset

Problem Description:
The boot process is delayed (three tries, ~20 seconds) when identifying ata2
devices. The boot then continues normally. The problem occured when Arch was
switching from the 2.6.24 basekernel to 2.6.25. 

Initially reported on bugs.archlinux.org, but rejected as an upstream bug.

Relevant section of dmesg:

SCSI subsystem initialized
libata version 3.00 loaded.
pata_amd 0000:00:09.0: version 0.3.10
PCI: Setting latency timer of device 0000:00:09.0 to 64
scsi0 : pata_amd
scsi1 : pata_amd
ata1: PATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0xf000 irq 14
ata2: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0xf008 irq 15
ata1.00: ATA-6: ST3120026A, 3.06, max UDMA/100
ata1.00: 234441648 sectors, multi 16: LBA48 
ata1.01: ATA-7: Maxtor 6B300R0, BAH41B10, max UDMA/133
ata1.01: 586114704 sectors, multi 16: LBA48 
ata1: nv_mode_filter: 0x3f39f&0x3f01f->0x3f01f, BIOS=0x3f000 (0xc6c7c000)
ACPI=0x3f01f (20:15:0x1f)
ata1: nv_mode_filter: 0x7f39f&0x7f01f->0x7f01f, BIOS=0x7f000 (0xc6c7c000)
ACPI=0x7f01f (20:15:0x1f)
ata1.00: configured for UDMA/100
ata1.01: configured for UDMA/133
ata2.01: failed to IDENTIFY (I/O error, err_mask=0x1)
ata2: failed to recover some devices, retrying in 5 secs
ieee1394: Host added: ID:BUS[0-01:1023]  GUID[00023c002105b2d9]
ata2.01: failed to IDENTIFY (I/O error, err_mask=0x1)
ata2: failed to recover some devices, retrying in 5 secs
ata2.01: failed to IDENTIFY (I/O error, err_mask=0x1)
ata2: failed to recover some devices, retrying in 5 secs
ata2.00: ATAPI: SONY    CD-RW  CRX160E, 1.0e, max UDMA/33
ata2: nv_mode_filter: 0x739f&0x701f->0x701f, BIOS=0x7000 (0xc6c7c000)
ACPI=0x701f (60:600:0x13)
ata2.00: configured for UDMA/33
scsi 0:0:0:0: Direct-Access     ATA      ST3120026A       3.06 PQ: 0 ANSI: 5
scsi 0:0:1:0: Direct-Access     ATA      Maxtor 6B300R0   BAH4 PQ: 0 ANSI: 5
scsi 1:0:0:0: CD-ROM            SONY     CD-RW  CRX160E   1.0e PQ: 0 ANSI: 5

Steps to reproduce: reboot


-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

             reply	other threads:[~2008-07-01  0:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-01  0:06 bugme-daemon [this message]
2008-07-01  8:31 ` [Bug 11015] Delay on boot: fails to IDENTIFY ata2.01 (I/O error, err_mask=0x1) bugme-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-11015-11633@http.bugzilla.kernel.org/ \
    --to=bugme-daemon@bugzilla.kernel.org \
    --cc=linux-ide@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).