From: Bruno Vidal <bruno_vidal@hpfrcu03.france.hp.com>
To: Randolph Chung <randolph@tausq.org>
Cc: "parisc-linux@lists.parisc-linux.org"
<parisc-linux@lists.parisc-linux.org>
Subject: Re: [parisc-linux] new 2.4.20-pa10 kernel: boot pb.
Date: Mon, 09 Dec 2002 09:39:49 +0100 [thread overview]
Message-ID: <3DF456D5.7E000273@admin.france.hp.com> (raw)
In-Reply-To: 20021206170904.GY19331@tausq.org
[-- Attachment #1: Type: text/plain, Size: 2204 bytes --]
Hi
Still the same behavior:
sym.0.2.0: setting PCI_COMMAND_MASTER...
sym.0.2.1: setting PCI_COMMAND_MASTER...
sym.0.1.0: setting PCI_COMMAND_MASTER...
sym0: <875> rev 0x14 on pci bus 0 device 2 function 0 irq 130
sym0: No NVRAM, ID 7, Fast-20, SE, parity checking
sym0: SCSI BUS has been reset.
sym1: <875> rev 0x14 on pci bus 0 device 2 function 1 irq 131
sym1: No NVRAM, ID 7, Fast-20, SE, parity checking
sym1: SCSI BUS has been reset.
sym2: <896> rev 0x7 on pci bus 0 device 1 function 0 irq 129
sym2: No NVRAM, ID 7, Fast-40, LVD, parity checking
sym2: SCSI BUS has been reset.
sym3: <896> rev 0x7 on pci bus 0 device 1 function 1 irq 130
sym3: No NVRAM, ID 7, Fast-40, SE, parity checking
sym3: SCSI BUS has been reset.
sym3: SCSI BUS mode change from SE to SE.
sym3: SCSI BUS has been reset.
scsi0 : sym-2.1.17a
scsi1 : sym-2.1.17a
scsi2 : sym-2.1.17a
scsi3 : sym-2.1.17a
blk: queue 000000004f9f3e40, I/O limit 4095Mb (mask 0xffffffff)
Nothing more.........
I'll try with spinlock debug now.
Randolph Chung wrote:
> > nothing more, it stay here forever.......
> >
> > It is an A500 in SMP/64.
> >
> > A normal boot with 2.4.19
> > scsi1 : sym53c8xx-1.7.3c-20010512
> > scsi2 : sym53c8xx-1.7.3c-20010512
> > scsi3 : sym53c8xx-1.7.3c-20010512
> > Vendor: SEAGATE Model: ST31230N Rev: HP05
> > Type: Direct-Access ANSI SCSI revision: 02
> > Vendor: SEAGATE Model: ST318404LC Rev: HP04
>
> Bruno, can you try the sym2 driver and let us know how it goes?
>
> CONFIG_SCSI_SYM53C8XX_2=y
> CONFIG_SCSI_SYM53C8XX_DMA_ADDRESSING_MODE=0
> CONFIG_SCSI_SYM53C8XX_DEFAULT_TAGS=16
> CONFIG_SCSI_SYM53C8XX_MAX_TAGS=64
>
> there was a similar problem with the sym2 driver that was fixed
> recently.
>
> alternatively, please try turning on CONFIG_DEBUG_SPINLOCK in your
> kernel and try running the sym53c8xx driver and see if that helps
> identify the problem...
>
> randolph
> --
> Randolph Chung
> Debian GNU/Linux Developer, hppa/ia64 ports
> http://www.tausq.org/
--
Vidal Bruno, (770-4271)
SSD-HA Team, HP-UX & LINUX Support
bruno_vidal@admin.france.hp.com
[-- Attachment #2: Card for Bruno Vidal --]
[-- Type: text/x-vcard, Size: 386 bytes --]
begin:vcard
n:Bruno;VIDAL
tel;fax:01-69-82-60-14
tel;work:01-69-29-42-71
x-mozilla-html:TRUE
url:www.france.hp.com
org:Solution Center
version:2.1
email;internet:bruno_vidal@hp.com
title:Expert Logiciel Environnement Haute Disponibilité
adr;quoted-printable:;;HP France=0D=0A;Z.A de Courtaboeuf;1 Av. du Canada;91947 Les Ulis cedex;France
x-mozilla-cpt:;26208
fn:VIDAL Bruno
end:vcard
next prev parent reply other threads:[~2002-12-09 8:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-06 16:39 [parisc-linux] new 2.4.20-pa10 kernel: boot pb Bruno Vidal
2002-12-06 17:09 ` Randolph Chung
2002-12-09 8:39 ` Bruno Vidal [this message]
2002-12-10 16:54 ` Bruno Vidal
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=3DF456D5.7E000273@admin.france.hp.com \
--to=bruno_vidal@hpfrcu03.france.hp.com \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=randolph@tausq.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