Linux PARISC architecture development
 help / color / mirror / Atom feed
From: "Carlos O'Donell Jr." <carlos@baldric.uwo.ca>
To: Sorin Ghinescu <sghinesc@columbus.rr.com>
Cc: parisc-linux@lists.parisc-linux.org
Subject: [parisc-linux] 53c700 SCSI Driver Problems ~?= 712/80 and Quantum Fireball 1050MB HD problem
Date: Tue, 8 Jan 2002 17:00:22 -0500	[thread overview]
Message-ID: <20020108170022.X11181@systemhalted> (raw)
In-Reply-To: <001001c19861$55b59de0$0800a8c0@beta>; from sghinesc@columbus.rr.com on Tue, Jan 08, 2002 at 11:27:10AM -0500

> Help with the following problem would be much appreciated:
> 
> I boot parisc-linux from cd-drive and everything goes fine except the HD
> is not detected. All other hardware is correctly detected. The
> installation program recommends passing args to boot: or load
> appropriate module.
> 
> Has anyone experienced this kind of problem?
> Thanks
> Sorin
>

Can you try to get a snip of text printed by the SCSI driver?

I seem to be having some issues with the newer SCSI driver
(October merge) on my 715/50's ... I'll post my info tommorow.

In particular (0.9.3 Install with apt-get updates):

Kernel 2.4.16-pa21 (Will be updating tommorow)

- Most of the drives I put into the box refuse to spinup.
	= E.g. "spinning up....." until timeout

- Boxes with 525MB HP Quantum ProDrive HD's lockup solid in
  mke2fs while writing superblocks (always happens).

- Drives that do spinup are reported as 0MB's because the 
  sector size was invalid (4GIG Barracudas)

- Random lockups accessing the drive on 712/50's that 
  seem to have functional drives. Usually manifested as
  a solid lock at a Random time during Init scripts.
  (I know cause I ran init=/bin/sh and straced evertyhing)

Most of our cluster is running 2.4.9-pa25 <= Very Stable.

Mind you, the latest kernel runs fine on our 712/60. 
And since the problem _looks_ to be SCSI related...
that's what I'm going to try investigate.

=-= Help investigating =-=

I'm wondering if I'll need to get kgdb??
Or something other than serial?
The box _locks_ solid, no response, and I'm not quite sure
how to diagnose that.

c.

  reply	other threads:[~2002-01-08 21:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-02  3:35 [parisc-linux] 0.9.3 installer didn't set 712 bootable Nick Papadonis
2002-01-02  4:21 ` [parisc-linux] DISREGARD " Nick Papadonis
2002-01-02  4:38   ` Christian Suder
2002-01-03 15:28     ` Matthew Wilcox
2002-01-03 18:03       ` Grant Grundler
2002-01-08 16:27         ` [parisc-linux] 712/80 and Quantum Fireball 1050MB HD problem Sorin Ghinescu
2002-01-08 22:00           ` Carlos O'Donell Jr. [this message]
2002-01-09  5:37           ` Phil Anderson

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=20020108170022.X11181@systemhalted \
    --to=carlos@baldric.uwo.ca \
    --cc=parisc-linux@lists.parisc-linux.org \
    --cc=sghinesc@columbus.rr.com \
    /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