From: Benjamin Herrenschmidt <bh40@calva.net>
To: Johnnie Peters <jpeters@phx.mcd.mot.com>,
linuxppc-dev@lists.linuxppc.org
Subject: Re: new bootloader
Date: Tue, 16 Mar 1999 20:23:14 +0100 [thread overview]
Message-ID: <19990316202314.027662@mail.mipsys.com> (raw)
In-Reply-To: <36EE719D.EF7C5C6D@phx.mcd.mot.com>
On Tue, Mar 16, 1999, Johnnie Peters <jpeters@phx.mcd.mot.com> wrote:
>I have it running. I had some troubles with 2.2.2. The SCSI system tended
>to lock up after awhile but this seems to be gone on 2.2.3. The only thing
>I have so far noticed is that when compiled with SMP enabled, the 2.2.2
>release hung during semaphore handling in the SCSI driver and in 2.2.3 it
>panics at the same place. I traced it down that far but have not had
the time
>to
>go further.
2.2.2 (from samba, I'm only getting back vger now) gave me MESH scsi
panics on boot here. (I haven't seen them for a while). the NCR 53X8XX
behaved fine but MESH panicked just after seeing my external HD. No
problem without the disk of course.
Didn't have time to try to find the problem yet neither.
--
E-Mail: <mailto:bh40@calva.net>
BenH. Web : <http://calvaweb.calvacom.fr/bh40/>
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting. ]]
next prev parent reply other threads:[~1999-03-16 19:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-16 10:24 new bootloader Cort Dougan
1999-03-16 14:58 ` Johnnie Peters
1999-03-16 19:23 ` Benjamin Herrenschmidt [this message]
1999-03-17 1:55 ` Michael Meissner
1999-03-17 8:05 ` Cort Dougan
1999-03-17 14:38 ` Gary Thomas
1999-03-23 3:27 ` Michael Meissner
1999-03-23 13:39 ` Michael Meissner
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=19990316202314.027662@mail.mipsys.com \
--to=bh40@calva.net \
--cc=jpeters@phx.mcd.mot.com \
--cc=linuxppc-dev@lists.linuxppc.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).