Re: Install Error

[Marco Peereboom <slash@peereboom.us>]

I need a dmesg to determine which driver you are running.

Did you read the BUGS section of the man page (not online!)?

On Jun 16, 2004, at 5:27 PM, Jane McCormack wrote:

> Hello
>
> I am new to OpenBSD, so I hope this bug report does not turn out to be
> erroneous because of fault on my part. I repeated the steps to failure 
> a total
> of 4 times, twice as a cd install the other two as a ftp install.
>
>
>
> These are the steps I followed to reproduce the error (being the 
> developers I
> assume you probably know the steps off by heart so I have removed 
> putting
> everything from the steps out and just put what keys I pressed until 
> the time
> when errors occur):
>
>  I [Enter][Enter]Y [Enter]P [Enter]UK [Enter]Y [Enter][Enter]Y [Enter] 
> p m  >
> d a  > a a  Enter  150M  Enter  /  a b  Enter  300M    Enter  > a d  
> Enter
> 500m  Enter  /tmp  > a e  Enter  1g  Enter  /var  > a g  Enter  3g  
> Enter
> /usr  > a h  Enter  Enter  Enter  /home  > p mØ       qØ       Enter   
> [/tmp]
> Enter  [/var] Enter  [/usr] Enter  [/home] Enter  [/tmp] done Charli 
> Enter
> Enterdhcp  jmc2.net  EnterEnter  Enter  Enter  Enter pAssWOrdpAssWOrd 
> (the two
> ftp ones I tried a, UK one 65 (I think) and then the main one, 1)c 
> Enter  /
> Enter bsd.rddone EnterEnter It begins installing the sets and then 
> stalls with
> this error repeated over in a loop:  sd0 (mpt0:0:0):mpt0:timeout on 
> request
> index = 0xef; seq = 0x000008d56mpt0: status 0x0000000, Mask 0x0000001,
> doorbell 0x2400000mpt: request status: on chip.  Which I went on IRC 
> to try
> and find out what it was, suspecting it was a SCSI controller problem. 
>  [
> 21:37:30 ] [ jmc2 ] sd0 (mpt0:0:0):mpt0:timeout on request index = 
> 0xef; seq =
> 0x000008d56 [ 21:37:30 ] [ jmc2 ] mpt0: status 0x0000000, Mask 
> 0x0000001,
> doorbell 0x2400000 [ 21:37:30 ] [ jmc2 ] mpt: request status: on chip. 
> [
> 21:37:36 ] [ Lucifer ] skeet shoot it [ 21:38:00 ] [ Lucifer ] 
> catapult the pc
> off, say a 20 story apartment balcony and shoot at it [ 21:38:30 ] [ 
> jmc2 ] I
> would do if I had any firearms handy [ 21:38:57 ] [ Lucifer ] well you 
> could
> shoot it with a water pistol and watch the impact damage [ 21:39:05 ] 
> [ jmc2 ]
> Openbsd has only just supporting my scsi controller, maybe still some 
> bugs in
> it [ 21:39:16 ]   Joins : dejx [ dejx@darkbOx.org ] [ 21:39:16 ] [ 
> cyberfrg ]
> probably [ 21:39:20 ] [ cyberfrg ] that's a hardware error [ 21:39:22 
> ] [ dejx
> ] :/
>
>
>
> The reason I suspect that it is a SCSI problem is because:
>
>
>
> HISTORY     The mpt driver first appeared in OpenBSD 3.5. Found at
> http://www.openbsd.org/cgi-bin/man.cgi?query=mpt&arch=i386&sektion=4
> Previously I have been unable to use OpenBSD because it didn't support 
> my
> servers SCSI controller, and this new driver is a recent addition, so 
> it seems
> the most likely culprit since the error is a hardware one
>
> My SCSI controller is: LSI Logic 53C1020 Single-Channel LVD Ultra320 
> SCSI
> controller.
>
>
>
> The system never recovers from the error and keeps repeating in a loop 
> which
> cannot be killed with ^c as shown.
>
>
>
> Sorry, I can't really enclose anymore details, I am new to this 
> system, and I
> don't think I can prise anymore info out of it since it gets stuck in 
> a loop
> that cannot be killed. Please feel free to contact me if you need 
> anymore
> details.