Date: Wed, 24 Jan 2001 19:20:02 -0700 From: "Kenneth D. Merry" <ken@kdm.org> To: clefevre@citeweb.net Cc: clefevre@noos.fr, freebsd-scsi@FreeBSD.ORG Subject: Re: SCSI suspend/resume Message-ID: <20010124192001.A4335@panzer.kdm.org> In-Reply-To: <200101240400.f0O40iT09954@gits.dyndns.org>; from root@gits.dyndns.org on Wed, Jan 24, 2001 at 05:00:43AM %2B0100 References: <20010122162354.B82472@panzer.kdm.org> <200101240400.f0O40iT09954@gits.dyndns.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jan 24, 2001 at 05:00:43 +0100, Cyrille Lefevre wrote: > Kenneth D. Merry wrote: > > On Mon, Jan 22, 2001 at 06:31:46 +0100, Cyrille Lefevre wrote: > > > "Kenneth D. Merry" <ken@kdm.org> writes: > > > > On Wed, Jan 17, 2001 at 23:54:17 +0100, Cyrille Lefevre wrote: > > > > > do you want a copy of my kernel config file ? any other things ? > > > > > > > > Nah, that's okay. The only thing I'm curious about is what sort of drive > > > > this is. Can you send dmesg output for your SCSI disk? > > > > > > single-ended 2GB HP drives :) > > > [snip] > > > > These drives look normal enough, I don't know of any problems offhand with > > them. So I don't really know why your drives aren't spinning up. > > > > Here are some things to try: > > > > - boot with -v (boot -v) and see if you get any additional diagnostic > > information when you spin down a drive and then try to do I/O. > > there is something incredible, today. it seems to work! > I don't understand anything. maybe a code change since december > and now? I can't repeat the problem w/ the old kernel, I lost it. > If it appears again, I'll tell you. Wow, that's odd. Nothing significant has changed in CAM in the past month or two, so I don't know why it would start working again. > also, I've tried a SCAM drive which is recognized by the BIOS but > not by FreeBSD. the drive is a SUN UltraPack where I turn the > dip-switch to one of the "holes" between 7 and 0! the problem is > that I don't find any doc. on this box and I don't really know how > to configure it to have full access to high SCSI targets. that's > why I've tried the "hole" front to the 0. next time, I try the one > front to the 7, who knows? maybe one is better than the other... I'm not sure what'll happen if you use a drive in SCAM mode with FreeBSD... If you can figure out a way to configure it to have a normal, fixed SCSI ID, that would probably be better. > > - try the attached patch, and see if you get any diagnostic printouts. > > yes, I did both : > > (da1:sym0:0:4:0): Attempting START UNIT > da1s1: type 0xa5, start 63, end = 4192964, size 4192902 : OK > (da1:sym0:0:4:0): Attempting START UNIT > resumed from suspended mode (slept 00:00:04) Okay, so the start unit certainly is being sent. But since things work correctly now, it would figure that they're being sent. :) > > > I know, my PLEXTOR CDROM seems to be dead :( > > > > That's normal. It's just telling you there is no CD in the drive. > > even with a CD in the drive, it can't read CD anymore... the red light > is flashing. and a mount /cdrom failed on device not ready. so, it's > really dead :)) maybe one day I'll check the cables. > > diagnostic messages are as follow : > > (da1:sym0:0:4:0): Attempting START UNIT > (cd0:sym0:0:1:0): PREVENT ALLOW MEDIUM REMOVAL. CDB: 1e 0 0 0 1 0 > (cd0:sym0:0:1:0): NOT READY asc:57,0 You neglected to cut-n-paste the meaning of 0x57,0x00: "Unable to recover table-of-contents" I would suggest trying a couple more CDs before declaring it dead. Also, see if it can play an audio CD. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010124192001.A4335>