All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Plattner <christoph.plattner@dot.at>
To: Richard Hirst <rhirst@linuxcare.com>
Cc: Jim Buttafuoco <jim@tylerdrive.org>, parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] Trouble booting a 710 (bushmaster)
Date: Mon, 22 Jan 2001 19:05:58 +0100	[thread overview]
Message-ID: <3A6C7686.1FC5F754@dot.at> (raw)
In-Reply-To: 20010122151515.N3571@linuxcare.com

I have the same SCSI message on my 720. The problem here
is definitly only one device, the TEAC floppy on the
SCSI bus. When I disconnect it, it runs perfect.

So this message also shows problems with special devices.
I don't know, if there are incaptibilities in the devices
(under HP sometimes this drive is seen as boot device, some
times not....).

Ot there is a problem in the routine probing the devices ....

With friendly regards
	Christoph P.


Richard Hirst wrote:
> 
> On Mon, Jan 22, 2001 at 10:02:46AM -0500, Jim Buttafuoco wrote:
> >       This also fails.  attached is the boot log.
> 
> > SCSI subsystem driver Revision: 1.00
> > sim700: Couldn't get consistent shared memory
> > sim700: Configuring 53c700 (SCSI-ID 7) at f0825100, IRQ 86, options 1
> > scsi0: Revision 0x0
> > Post test1, istat 05, sstat0 00, dstat 84
> > sim700: WARNING IRQ probe failed, (returned 0)
> > scsi0: WARNING: target data areas are not dma coherent!
> > scsi0: test 1 completed ok.
> 
> Well, scsi is happier now.  The messages above are expected, and
> test 1 passing means the scsi chip can access memeory ok.
> 
> > scsi0 : LASI/Simple 53c7xx
> > scsi0: Unable to abort command for target 0
> > scsi0: Unable to send Bus Device Reset for target 0
> > scsi0: Unable to do SCSI bus reset
> > scsi0: >>>>>>>>>>>> Host reset <<<<<<<<<<<<
> > scsi0: could not halt NCR chip, stage 0
> > scsi0: Unable to abort command for target 1
> > scsi0: Unable to send Bus Device Reset for target 1
> > scsi0: Unable to do SCSI bus reset
> > scsi0: >>>>>>>>>>>> Host reset <<<<<<<<<<<<
> 
> Those messages might be caused by an unterminated scsi bus, or by
> a problem with interrupts.
> 
> The network problem still looks like interrupts from the 82596 are
> disabled somehwere and not getting to the processor.
> 
> Still seems likely to me that the kernel is not enabling some interrupts
> properly for the 710 bushmaster machines.
> 
> Anyone on the list got a similar machine working?  The h/w database
> lists quite a few people as owning one of these boxes.
> 
> My 715 now works as far as scsi and network are concerned, but (a) I
> have to disable nscd, (b) tar hangs, and (c) I have disabled parallel
> port support.  nscd and tar both seem to go in to a loop calling
> sched_yield() from libc.
> 
> Richard
> 
> ---------------------------------------------------------------------------
> To unsubscribe: send e-mail to parisc-linux-request@thepuffingroup.com with
> `unsubscribe' as the subject.

-- 
-------------------------------------------------------------------------
private:	christoph.plattner@dot.at
company:	christoph.plattner@alcatel.at

  reply	other threads:[~2001-01-22 18:02 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200101221502.f0MF2kO05633@openbsd1.buttafuoco.net>
2001-01-22 15:15 ` [parisc-linux] Trouble booting a 710 (bushmaster) Richard Hirst
2001-01-22 18:05   ` Christoph Plattner [this message]
2001-01-22 20:01     ` [parisc-linux] strace ??? - is there any ??? Christoph Plattner
2001-01-22 20:15       ` Richard Hirst
2001-01-22 21:43         ` Further (build ?): " Christoph Plattner
2001-01-22 21:46           ` Christoph Plattner
2001-01-22 22:32             ` Richard Hirst
2001-01-22 22:45           ` Richard Hirst
2001-01-22 18:13   ` [parisc-linux] Bug in palo/palo/error.c Christoph Plattner
2001-01-18 21:04 [parisc-linux] Trouble booting a 710 (bushmaster) Jim Buttafuoco
2001-01-18 22:15 ` Richard Hirst
  -- strict thread matches above, loose matches on Subject: below --
2001-01-18 18:12 Jim Buttafuoco
2001-01-18 20:34 ` Richard Hirst
2001-01-18 15:17 Jim Buttafuoco
2001-01-18 17:54 ` bame
2001-01-18 20:52 ` Richard Hirst
2001-01-22 11:10   ` Richard Hirst
2001-01-22 13:52     ` Richard Hirst

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=3A6C7686.1FC5F754@dot.at \
    --to=christoph.plattner@dot.at \
    --cc=jim@tylerdrive.org \
    --cc=parisc-linux@thepuffingroup.com \
    --cc=rhirst@linuxcare.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.