headers
George Harvey | 29 May 2010 00:45

5.1_RC2 panics during install on indy

Hi,

I thought I'd give 5.1_RC2 a try on my Indy but I haven't been able to
complete the install, I get the same panic at different points each
time I try it:

wdsc0: TAG reselect without IDENTIFY; MSG 0; sending DEVICE RESET
wdsc0: TAG reselect without IDENTIFY; MSG 0; sending DEVICE RESET
panic: MSGOUT with no nexus
Stopped in pid 0.2 (system) at  0x882dbfa4:     jr      ra
                bdslot: nop 
db> bt 
0+882dbfa4 (97ffe000,d,0,cba03d74) ra 0 sz 0
User-level: pid 0.2
db>

My Indy is a 150MHz R5000SC model with 256Mb RAM and the disk is a 4.3GB
IBM DCAS-34330. Does this look like a disk error or a kernel problem?

George
Permalink | Reply |
headers
Stephen M. Rumble | 29 May 2010 03:36
Picon

Re: 5.1_RC2 panics during install on indy

On May 28, 2010, at 3:45 PM, George Harvey wrote:

> Hi,
> 
> I thought I'd give 5.1_RC2 a try on my Indy but I haven't been able to
> complete the install, I get the same panic at different points each
> time I try it:
> 
> wdsc0: TAG reselect without IDENTIFY; MSG 0; sending DEVICE RESET
> wdsc0: TAG reselect without IDENTIFY; MSG 0; sending DEVICE RESET
> panic: MSGOUT with no nexus
> Stopped in pid 0.2 (system) at  0x882dbfa4:     jr      ra
>                bdslot: nop 
> db> bt 
> 0+882dbfa4 (97ffe000,d,0,cba03d74) ra 0 sz 0
> User-level: pid 0.2
> db>
> 
> My Indy is a 150MHz R5000SC model with 256Mb RAM and the disk is a 4.3GB
> IBM DCAS-34330. Does this look like a disk error or a kernel problem?

What prior version were you running? I made several small changes between NetBSD-4 and NetBSD-5:
    - Added fast scsi support to WD33C93B.
    - Set the appropriate (I'm pretty sure) clock divisor for the scsi chipset.
    - Started using burst dma mode, rather than dma mode.

Could be something else entirely, but if you're interested in building an install kernel I could provide a
two line patch to effectively revert the above.

Steve
(Continue reading)

Permalink | Reply |
headers
George Harvey | 29 May 2010 19:50

Re: 5.1_RC2 panics during install on indy

On Fri, 28 May 2010 18:36:50 -0700
"Stephen M. Rumble" <rumble <at> cs.stanford.edu> wrote:

> On May 28, 2010, at 3:45 PM, George Harvey wrote:

> > My Indy is a 150MHz R5000SC model with 256Mb RAM and the disk is a 4.3GB
> > IBM DCAS-34330. Does this look like a disk error or a kernel problem?
> 
> What prior version were you running? I made several small changes between NetBSD-4 and NetBSD-5:
>     - Added fast scsi support to WD33C93B.
>     - Set the appropriate (I'm pretty sure) clock divisor for the scsi chipset.
>     - Started using burst dma mode, rather than dma mode.
> 
> Could be something else entirely, but if you're interested in building an install kernel I could provide a
two line patch to effectively revert the above.

I suspect it's something specific to R5000 Indys. I moved the disk onto
another Indy, this time with a R4600, and the install went through with
no problems. I'm currently building bash from pkgsrc as a quick(ish)
functional test on the R4600 box. I run 5.0 on a R4400 Challenge S but
when I tried 5.0 on the R5000 Indy last year, I got a lot of random
hangs which I never resolved. Going back further, I did have 4.0
running successfully on the R5000.

I'm happy to build a patched kernel and give it a try.

George
Permalink | Reply |
headers
Stephen M. Rumble | 31 May 2010 20:27
Picon

Re: 5.1_RC2 panics during install on indy

On May 29, 2010, at 10:50 AM, George Harvey wrote:

> On Fri, 28 May 2010 18:36:50 -0700
> "Stephen M. Rumble" <rumble <at> cs.stanford.edu> wrote:
> 
>> On May 28, 2010, at 3:45 PM, George Harvey wrote:
> 
>>> My Indy is a 150MHz R5000SC model with 256Mb RAM and the disk is a 4.3GB
>>> IBM DCAS-34330. Does this look like a disk error or a kernel problem?
>> 
>> What prior version were you running? I made several small changes between NetBSD-4 and NetBSD-5:
>>    - Added fast scsi support to WD33C93B.
>>    - Set the appropriate (I'm pretty sure) clock divisor for the scsi chipset.
>>    - Started using burst dma mode, rather than dma mode.
>> 
>> Could be something else entirely, but if you're interested in building an install kernel I could provide
a two line patch to effectively revert the above.
> 
> I suspect it's something specific to R5000 Indys. I moved the disk onto
> another Indy, this time with a R4600, and the install went through with
> no problems. I'm currently building bash from pkgsrc as a quick(ish)
> functional test on the R4600 box. I run 5.0 on a R4400 Challenge S but
> when I tried 5.0 on the R5000 Indy last year, I got a lot of random
> hangs which I never resolved. Going back further, I did have 4.0
> running successfully on the R5000.
> 
> I'm happy to build a patched kernel and give it a try.

It's quicker for me just to tell you than to generate a patch. In src/sys/arch/sgimips/hpc/wdsc.c, if you
change the following
(Continue reading)

Permalink | Reply |
headers
George Harvey | 1 Jun 2010 10:34

Re: 5.1_RC2 panics during install on indy

On Mon, 31 May 2010 11:27:34 -0700
"Stephen M. Rumble" <rumble <at> cs.stanford.edu> wrote:

> On May 29, 2010, at 10:50 AM, George Harvey wrote:
> 
> > I'm happy to build a patched kernel and give it a try.
> 
> It's quicker for me just to tell you than to generate a patch. In src/sys/arch/sgimips/hpc/wdsc.c, if you
change the following
>     sc->sc_clkfreq = 200;
>     sc->sc_dmamode = SBIC_CTL_BURST_DMA;
> to
>     sc->sc_clkfreq = 100;
>     sc->sc_dmamode = SBIC_CTL_DMA;
> you should get about the 4.0 behaviour (no fast scsi, wrong clock, no burst dma).

Unfortunately I am away from my test machines for a week, I'll give
this a try when I get back next week.

Thanks,
George
Permalink | Reply |
headers
Michael | 2 Jun 2010 00:49
Picon

Re: 5.1_RC2 panics during install on indy


Hello,

On Jun 1, 2010, at 4:34 AM, George Harvey wrote:

> On Mon, 31 May 2010 11:27:34 -0700
> "Stephen M. Rumble" <rumble <at> cs.stanford.edu> wrote:
>
>> On May 29, 2010, at 10:50 AM, George Harvey wrote:
>>
>>> I'm happy to build a patched kernel and give it a try.
>>
>> It's quicker for me just to tell you than to generate a patch. In  
>> src/sys/arch/sgimips/hpc/wdsc.c, if you change the following
>>    sc->sc_clkfreq = 200;
>>    sc->sc_dmamode = SBIC_CTL_BURST_DMA;
>> to
>>    sc->sc_clkfreq = 100;
>>    sc->sc_dmamode = SBIC_CTL_DMA;
>> you should get about the 4.0 behaviour (no fast scsi, wrong clock,  
>> no burst dma).
>
> Unfortunately I am away from my test machines for a week, I'll give
> this a try when I get back next week.

My R5k Indy happily runs 5.99.something with two disks on the internal  
SCSI port - maybe something needs to be pulled up?

have fun
Michael
(Continue reading)

Permalink | Reply |
headers
George Harvey | 9 Jun 2010 00:05

Re: 5.1_RC2 panics during install on indy

On Mon, 31 May 2010 11:27:34 -0700
"Stephen M. Rumble" <rumble <at> cs.stanford.edu> wrote:

> It's quicker for me just to tell you than to generate a patch. In src/sys/arch/sgimips/hpc/wdsc.c, if you
change the following
>     sc->sc_clkfreq = 200;
>     sc->sc_dmamode = SBIC_CTL_BURST_DMA;
> to
>     sc->sc_clkfreq = 100;
>     sc->sc_dmamode = SBIC_CTL_DMA;
> you should get about the 4.0 behaviour (no fast scsi, wrong clock, no burst dma).

Back home now, and built a patched kernel using my R4600 box. Moved the
disk over to the R5000 box and accidently booted the GENERIC kernel
instead of the patched version. Somewhat to my surprise, that was
successful, goes multiuser and is currently compiling some test
programs. The panics I saw with the INSTALL kernel were SCSI related so
I'm going to run some disk/filesystem test programs on both the INSTALL
and GENERIC kernels to see what happens.

George
Permalink | Reply |
headers
George Harvey | 10 Jun 2010 23:15

Re: 5.1_RC2 panics during install on indy

On Tue, 8 Jun 2010 23:05:03 +0100
George Harvey <fr30 <at> dial.pipex.com> wrote:

> Back home now, and built a patched kernel using my R4600 box. Moved the
> disk over to the R5000 box and accidently booted the GENERIC kernel
> instead of the patched version. Somewhat to my surprise, that was
> successful, goes multiuser and is currently compiling some test
> programs. The panics I saw with the INSTALL kernel were SCSI related so
> I'm going to run some disk/filesystem test programs on both the INSTALL
> and GENERIC kernels to see what happens.

Well, I've now run bonnie++ on both the GENERIC and INSTALL kernels
without any panics so I think I'll have to try another complete install
just to see if my original panic is reproducable or not. In the
meantime, I tried RC2 on my R5000 Challenge S and got an entirely
different panic. I'll start a new thread for that one.

George
Permalink | Reply |

Gmane