From: Richard Hirst <rhirst@linuxcare.com>
To: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] 2.4.16-pa15 still POWERFAIL(was 2.4.16-pa12 Power failled)
Date: Wed, 5 Dec 2001 16:08:31 +0000 [thread overview]
Message-ID: <20011205160831.F7051@linuxcare.com> (raw)
In-Reply-To: <1007547737.3c0df5599e8c9@webmail.tiscalinet.be>; from joel.soete@freebel.net on Wed, Dec 05, 2001 at 11:22:17AM +0100
On Wed, Dec 05, 2001 at 11:22:17AM +0100, joel.soete@freebel.net wrote:
> Hi all,
>
> Just to report that the problem persit on my B180 (even thought that changes was
> made on sym53c8xx but I do know if its regarding this problem).
This is a bit of debug from my a500, 2.4.16-pa13
request_irq(66, 000000001037fd90, 0x0, IO-SAPIC00-L1, 000000001009bc58)
request_irq(66, 000000001037c590, 0x0, powerfail, 0000000000000000)
request_irq(129, 0000000010374ed0, 0x4000000, sym53c8xx, 000000001fe98000)
iosapic_interrupt(): irq 66 line 1 eoi fffffffffed30840, irq_num 129
POWERFAIL INTERRUPTION !
Don't claim to understand this, but it looks like "powerfail" has
requested the wrong irq?
Richard
next prev parent reply other threads:[~2001-12-05 16:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-03 18:44 [parisc-linux] Kernel 2.4.16-pa10 joel.soete
2001-12-04 3:43 ` Phil Anderson
2001-12-04 7:01 ` [parisc-linux] Kernel 2.4.16-pa10: sti console brokrn? joel.soete
2001-12-04 13:43 ` [parisc-linux] 2.4.16-pa12 Power failled (was: 2.4.16-pa10: sti console broken?) joel.soete
2001-12-05 10:22 ` [parisc-linux] 2.4.16-pa15 still POWERFAIL(was 2.4.16-pa12 Power failled) joel.soete
2001-12-05 16:08 ` Richard Hirst [this message]
2001-12-05 17:25 ` Grant Grundler
2001-12-06 13:49 ` [parisc-linux] 2.4.16-pa16 Solves POWERFAIL (was: 2.4.16-pa15 still POWERFAIL) joel.soete
2001-12-06 17:28 ` [parisc-linux] Trying C180/current CVS again nick
2001-12-07 4:28 ` Grant Grundler
2001-12-07 4:38 ` nick
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=20011205160831.F7051@linuxcare.com \
--to=rhirst@linuxcare.com \
--cc=parisc-linux@lists.parisc-linux.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.