Date: Mon, 11 Dec 2000 01:20:04 -0700 From: "Kerry Davis" <kedavis@uswest.net> To: "Tim McMillen" <timcm@umich.edu> Cc: <freebsd-questions@FreeBSD.ORG> Subject: Re: Kernel panic on larger SCSI drives Message-ID: <1bd101c0634b$2a619870$0200000a@system>
next in thread | raw e-mail | index | archive | help
these are all SCA drives originally, although I have 80-to-68 adaptors on them. as such, these drives don't have their own termination options. the CABLE has a terminator attached. as mentioned in the original email, the installation was fine on the 2.1 gig drive on the same cable, on the same SCSI card, with the same termination. and with the 36.4 gig drive connected, even lowly DOS 6.22 was able to see it (8 gig of it, anyway), partition it and format it (2.1 gig at a time) and use it successfully after that. But all that mighty BSD seems able to do with it, is panic. could it be that whoever came up with the Qlogic SCSI card drivers needs to look at the code again? -----Original Message----- From: Tim McMillen <timcm@umich.edu> To: Kerry Davis <kedavis@uswest.net> Date: Monday, December 11, 2000 12:44 AM Subject: Re: Kernel panic on larger SCSI drives > > >Hi, I don't even have scsi hd's but people that know will say 90% of the >problems with scsi drives is with improper termination. So have you >checked, re-checked, and re-checked your scsi cable termination? Also >check how the drives are numbered on the cable, jumpered, etc, depending >on your scsi card. > >On Sun, 10 Dec 2000, Kerry Davis wrote: > >> I have successfully installed FreeBSD 4.1 on a 486-66 system with PCI >> motherboard, Qlogic 1080 Wide SCSI card, and an IBM 2.1 gig SCA (80-pin with >> adaptor to 68-pin) drive. Everything is fine, and a "customized kernel" >> compiled without any problems. >> >> But I also have a Compaq/Seagate 36.4 gig SCA (80-pin with adaptor also) > >ok I just have to stop and laugh at this. Isn't putting that drive in a >486 kinda like putting a ferrari engine in a yugo? :) > >> drive to use for main storage, that I wasn't able to have connected during >> the install/setup, or I'd get a "kernel panic." So I disconnected it while >> doing the install. Now, even when everything else is installed >> successfully, and I connect the drive in order to add it to the BSD setup, I >> get a "kernel panic" during startup. >> >> The card works for everything else. The 36.4 gig drive does fine with the >> diagnostics that are built into the SCSI card. But BSD apparently can't >> handle it, for some reason. > >Ok, you're mixing different scsi types here right? It's possible that >even thought the card is supposed to be able to handle that, that it is >not adjusting to the different scsi types correctly. > > Can you use the system with only one or the other drive in? I >mean what is the outcome of booting from a floppy with just the 36.4GB >drive attached properly. Does that work? Now what about just the other >one? If each one works separately, then you know your problem lies with >how they interact. > Running down the other list of possibilities is you have a bad >terminator, a bad cable, bad adapter, one or more bad drives (even if the >card SAYS they're ok), or a problem with your motherboard/PCI slots that >are causing strange errors. > Of course the chances that any one of these are the problem is low >(especially that the drive is bad), but it is POSSIBLE. So work to >eliminate each one. Do you have another computer to try installing the >scsi card and drives in? Do you have another cable you can try? Another >terminator, try the working adapter on the drive that is causing >problems, etc. Try changing only one thing at a time until you've tried >every possibility. That's a lot of different combinations and would be >hard to do, but you never know. Sometimes hardware is so funky that >switching the order of drives on the scsi bus would keep the problem from >surfacing. > That's all I've got for you, hopefully it was a little helpful. >Hopefully somebody with more scsi experience can help you further. > > Tim > > >> >> Right after the "Waiting 15 seconds for SCSI devices to settle," it >> apparently looks at the drive: >> >> da1 at isp0 bus 0 target 1 lun 0 >> da1: <COMPAQ blah blah> Fixed Direct Access SCSI-2 Device >> >> and then it gets this: >> >> Fatal trap 18: integer divide fault while in kernel mode >> >> Now, for one thing, I don't understand why it appears to be looking at the >> #1 drive FIRST, rather than the #0 drive. unless it's showing that just >> because of the error. >> >> Anyone have any ideas on this? If it's a problem because the drive doesn't >> have a filesystem on it yet, how am I supposed to CREATE one if it won't >> even START? I can't use the Handbook instructions, because they all assume >> that the system will START AND RUN in order to do the commands listed. >> >> >> >> To Unsubscribe: send mail to majordomo@FreeBSD.org >> with "unsubscribe freebsd-questions" in the body of the message >> > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1bd101c0634b$2a619870$0200000a>