From: Andrew Morton <akpm@linux-foundation.org>
To: linux-ide@vger.kernel.org
Cc: bugme-daemon@bugzilla.kernel.org, Arjan van de Ven <arjan@infradead.org>
Subject: Re: [Bugme-new] [Bug 10752] New: pata_isapnp driver causes the ata layer to go splat
Date: Mon, 19 May 2008 15:25:49 -0700 [thread overview]
Message-ID: <20080519152549.09be22b2.akpm@linux-foundation.org> (raw)
In-Reply-To: <bug-10752-10286@http.bugzilla.kernel.org/>
On Mon, 19 May 2008 14:46:08 -0700 (PDT)
bugme-daemon@bugzilla.kernel.org wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=10752
>
> Summary: pata_isapnp driver causes the ata layer to go splat
> Product: IO/Storage
> Version: 2.5
> KernelVersion: 2.6.25
> Platform: All
> OS/Version: Linux
> Tree: Mainline
> Status: NEW
> Severity: normal
> Priority: P1
> Component: Serial ATA
> AssignedTo: jgarzik@pobox.com
> ReportedBy: arjan@linux.intel.com
>
>
> This happens quite a bit based on Fedora 9 feedback, but already happened in
> 2.6.24 and possibly earlier.
>
> http://www.kerneloops.org/search.php?search=bad_io_access
>
> shows the basic backtrace:
> *bad_io_access
> ioread8
> ata_altstatus
> ata_std_dev_select
> ata_dev_select
> ata_qc_issue_prot
> ata_qc_issue
> ata_exec_internal_sg
> ata_exec_internal
> ata_dev_read_id
> ata_eh_recover
> ata_do_eh
> ata_bmdma_drive_eh
> ata_bmdma_error_handler
> ata_scsi_error
> scsi_error_handler
> kthread
> kernel_thread_helper
>
> in all cases, this happens while pata_isapnp is being loaded; so it's not
> unlikely that this driver stomps on some other driver which then goes splat
>
Unclear who maintains pata_isapnp?
next parent reply other threads:[~2008-05-19 22:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-10752-10286@http.bugzilla.kernel.org/>
2008-05-19 22:25 ` Andrew Morton [this message]
2008-05-20 1:13 ` [Bugme-new] [Bug 10752] New: pata_isapnp driver causes the ata layer to go splat Arjan van de Ven
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=20080519152549.09be22b2.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.