From: Andrew Morton <akpm@linux-foundation.org>
To: linux-ide@vger.kernel.org
Cc: bugme-daemon@bugzilla.kernel.org, fragabr@gmail.com
Subject: Re: [Bugme-new] [Bug 11086] New: 2.6.26 (sata_nv = irq 21 problem after halting)
Date: Mon, 14 Jul 2008 12:58:21 -0700 [thread overview]
Message-ID: <20080714125821.714013e2.akpm@linux-foundation.org> (raw)
In-Reply-To: <bug-11086-10286@http.bugzilla.kernel.org/>
(switched to email. Please respond via emailed reply-to-all, not via the
bugzilla web interface).
On Mon, 14 Jul 2008 12:31:54 -0700 (PDT)
bugme-daemon@bugzilla.kernel.org wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=11086
>
> Summary: 2.6.26 (sata_nv = irq 21 problem after halting)
> Product: IO/Storage
> Version: 2.5
> KernelVersion: 2.6.26
> Platform: All
> OS/Version: Linux
> Tree: Mainline
> Status: NEW
> Severity: normal
> Priority: P1
> Component: Serial ATA
> AssignedTo: jgarzik@pobox.com
> ReportedBy: fragabr@gmail.com
>
>
> Latest working kernel version: 2.6.25
> Earliest failing kernel version: 2.6.26
> Distribution: Linux from scratch
> Hardware Environment: athlon64 x2 5600+, Asus M2N-E
> Software Environment:
> Problem Description:
>
> Something happened with ncq's sata_nv support. When I halt my
> system (Athlon64, Asus M2N-E), I get the following (I had to copy by
> hand, since the system is halted, so it's just an excerpt):
>
> IRQ 21: nobody cared (try booting with the "irqpool" option)
> Pid 0, comm: swapper not tainted 2.6.26 #2
>
> Call trace:
> ........... nv_swncq_interrupt
> ........... __report_bad_irq
> ........... note_interrupt
> ........... handle_fasteoi_irq
> ........... do_irq
> ........... ret_from_intr
>
> Handles:
>
> [<f88888888803a5b90>] (nv_swncq_interrupt+0x0/0xd0)
>
> Disabling IRQ #21
>
> This just happens after a halt.
>
> If I use irqpool, this error doesn't happen.
>
> Thanks.
>
> Steps to reproduce:
>
> Just shutdown the system (halt).
>
It's a 2.6.26 regression. It happens at halt-time, so it won't be the
usual ACPI stuff.
I think this is the second report of ata going splat in this manner at
shutdown time. Did we get the order of something wrong?
parent reply other threads:[~2008-07-14 19:58 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <bug-11086-10286@http.bugzilla.kernel.org/>]
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=20080714125821.714013e2.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=fragabr@gmail.com \
--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).