From: Ron Niles <Ron.Niles@falconstor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: RedHat 7.2 Stock SMP Install
Date: Wed, 22 May 2002 11:41:14 -0400 [thread overview]
Message-ID: <E79B8AB303080F4096068F046CD1D89B934EC7@exchange1.FalconStor.Net> (raw)
"Rose, Billy" <wrose@loislaw.com> wrote:
>I have an HP LPr Dual P-III 550 with 2 18G SCSI drives that locked up. No
>response at the console, ssh failed, and ping never answered.
>How can I find more info on the lockup?
When getting solid lockups like this, nmi_watchdog.txt can sometimes break
you out and give an Oops to work off of.
>Attached devices:
>Host: scsi0 Channel: 00 Id: 00 Lun: 00
> Vendor: HP Model: 18.2GB C 80-8C42 Rev:
> Type: Direct-Access ANSI SCSI revision: 02
>Host: scsi0 Channel: 00 Id: 01 Lun: 00
> Vendor: HP Model: 18.2GB C 80-8C42 Rev:
> Type: Direct-Access ANSI SCSI revision: 02
Multiple SCSI devices on the same bus often have termination problems which
can result in scsi bus lock-up or even data integrity problems. Make sure
you understand the finer points of SCSI device termination. You might want
to try running just one drive off the card and see if the system stabilizes.
>Modules Loaded ide-scsi nfsd lockd sunrpc tux autofs eepro100
usb-uhci usbcore
> ext3 jbd sym53c8xx sd_mod scsi_mod
Although it's probably not related to your lockup, I have problems with the
eepro100 drivers, most notably memory leaks. It is worth using the updated
e100 linux driver from the Intel website instead. Note that the driver name
is changed from eepro100 to e100.
next reply other threads:[~2002-05-22 15:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-22 15:41 Ron Niles [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-05-22 16:10 Rose, Billy
2002-05-22 14:38 Rose, Billy
2002-05-22 15:31 ` Doug McNaught
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=E79B8AB303080F4096068F046CD1D89B934EC7@exchange1.FalconStor.Net \
--to=ron.niles@falconstor.com \
--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
all inboxes | Powered by JetHome®