From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: david2@maincube.net (David Priban)
Cc: linux-kernel@vger.kernel.org
Subject: Re: i2o & Promise SuperTrak100
Date: Tue, 27 Feb 2001 17:32:22 +0000 (GMT) [thread overview]
Message-ID: <E14Xnz8-0003rQ-00@the-village.bc.nu> (raw)
In-Reply-To: <MPBBILLJAONHMANIJOPDIEBIFMAA.david2@maincube.net> from "David Priban" at Feb 27, 2001 12:14:14 PM
> c029072a
> Call Trace:
> [<c01b33fe>] [<c01b349c>] [<c01b308f>] [<c01b4774>]
> [<c01b47a6>] [<c011b0fe>] [<c011b4bf>] [<c018969d>]
> [<c0189731>] [<c018918e>] [<c018a12d>] [<c018a19f>]
> [<c0109f6d>] [<c010a0ce>] [<c0107120>] [<c0107120>]
> [<c0108e00>] [<c0107120>] [<c0107120>] [<c0100018>]
> [<c0107143>] [<c01071a9>] [<c0105000>] [<c0100191>]
> Code:
> 0f 0b 8d 65 dc 5b 5e 5f 89 ec 5d c3 55 89 e5 83 ec 10 57 56
> Kernel panic: Aiee, killing interrupt handler !
> In interrupt handler - not syncing
Run it through ksymoops and I might be able to guess what went wrong.
In theory however i2o is a standard and all i2o works alike. In practice i2o
is a pseudo standard and nobody seems to interpret the spec the same way, the
implementations all tend to have bugs and the hardware sometimes does too.
next prev parent reply other threads:[~2001-02-27 17:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-27 17:14 i2o & Promise SuperTrak100 David Priban
2001-02-27 17:32 ` Alan Cox [this message]
2001-02-28 18:26 ` David Priban
2001-02-28 23:10 ` Andrew Morton
2001-03-01 20:40 ` David Priban
2001-02-28 20:11 ` David Priban
2001-02-28 23:38 ` Alan Cox
2001-03-03 17:14 ` David Woodhouse
2001-03-03 17:37 ` Alan Cox
2001-03-01 1:36 ` Jens Axboe
2001-04-09 13:07 Joao Paulo Martins
2001-04-10 7:22 ` Jens Axboe
2001-04-10 11:22 ` Alan Cox
2001-04-10 11:25 ` Jens Axboe
2001-04-10 11:59 ` Joao Paulo Martins
2001-04-10 15:19 ` Chris
2001-04-12 18:33 ` Andrew Chan
2001-04-12 19:30 ` Alan Cox
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=E14Xnz8-0003rQ-00@the-village.bc.nu \
--to=alan@lxorguk.ukuu.org.uk \
--cc=david2@maincube.net \
--cc=linux-kernel@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).