From: Matthew Wilcox <matthew@wil.cx>
To: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Cc: linux-parisc@vger.kernel.org
Subject: Re: Hacking SuperDome
Date: Sun, 8 Feb 2009 04:33:07 -0700 [thread overview]
Message-ID: <20090208113307.GE31509@parisc-linux.org> (raw)
In-Reply-To: <20090207142906.GA8553@alpha.franken.de>
On Sat, Feb 07, 2009 at 03:29:06PM +0100, Thomas Bogendoerfer wrote:
> The bigger partition produces following boot log:
[...]
> sym0: <895> rev 0x2 at pci 0000:18:00.0 irq 67
> sym0: No NVRAM, ID 7, Fast-40, LVD, parity checking
> sym0: SCSI BUS has been reset.
> scsi0 : sym-2.2.3
> scsi 0:0:0:0: ABORT operation started
> scsi 0:0:0:0: ABORT operation timed-out.
> scsi 0:0:0:0: DEVICE RESET operation started
>
> After that it hangs...
Generally, this means that interrupts are broken; sym2 didn't get an
interrupt saying the command completed.
Looking through the rest of the log, I don't see any information
pertaining to interrupt setup. I forget whether we have debug related
to interrupts, but I bet we do ...
--
Matthew Wilcox Intel Open Source Technology Centre
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
next prev parent reply other threads:[~2009-02-08 11:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-07 14:29 Hacking SuperDome Thomas Bogendoerfer
2009-02-08 4:30 ` Kyle McMartin
2009-02-08 17:05 ` Kyle McMartin
2009-02-08 23:15 ` Matthew Wilcox
2009-02-08 11:33 ` Matthew Wilcox [this message]
2009-02-11 7:23 ` Grant Grundler
2009-02-11 10:00 ` Thomas Bogendoerfer
2009-02-11 16:26 ` Matthew Wilcox
2009-02-11 17:02 ` Grant Grundler
2009-02-11 18:14 ` Kyle McMartin
2009-02-11 18:28 ` Kyle McMartin
2009-02-11 19:29 ` Grant Grundler
2009-02-12 0:36 ` Kyle McMartin
2009-02-13 20:46 ` Thomas Bogendoerfer
2009-02-15 15:33 ` Jan-Benedict Glaw
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=20090208113307.GE31509@parisc-linux.org \
--to=matthew@wil.cx \
--cc=linux-parisc@vger.kernel.org \
--cc=tsbogend@alpha.franken.de \
/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