Date: Wed, 8 Feb 2006 23:10:57 +0100 From: Wilko Bulte <wb@freebie.xs4all.nl> To: =?iso-8859-1?Q?S=F8ren?= Schmidt <sos@deepcore.dk> Cc: stable@freebsd.org Subject: Re: Showstopper ATA bug in 6.1-PRE? Message-ID: <20060208221056.GA1299@freebie.xs4all.nl> In-Reply-To: <43EA6625.2070106@deepcore.dk> References: <20060208194603.GA689@freebie.xs4all.nl> <43EA5C50.5020804@deepcore.dk> <20060208213704.GA703@freebie.xs4all.nl> <43EA6625.2070106@deepcore.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Feb 08, 2006 at 10:44:05PM +0100, Sren Schmidt wrote.. > Wilko Bulte wrote: > >On Wed, Feb 08, 2006 at 10:02:08PM +0100, Sren Schmidt wrote.. > >>Wilko Bulte wrote: > >>>Hi Soren, > >>> > >>>I just went to 6.1-PRE on my main machine, coming from 6.0-STABLE > >>>of roughly end of december. > >>> > >>>And I hit some stuff that really worries me: > >>> > >>>- the freshly built kernel keels over with (hand transcribed): > >>> > >>>ata3: reiniting channel SATA connect ... > >>>SATA connected > >>>sata_connect_devices 0x1 <ATA_MASTER> > >>> > >>>ad6: req=0xC35ba0c8 SETFEATURES SETTRANSFERMODE semaphore timeout > >>>!! DANGER Will RObinson !! > >>> > >>>(... is where I cannot read my own handwriting, it scrolled quite fast on > >>>the screen..) > >>> > >>>Boot device is a SATA RAID1 on a Promise 2300. > >>Hmm, that should not happen. Could you try to backstep just ATA to > >>before the MFC, that is 24/1/06 and let me know if that helps please ? > > > >First impression is that the problem is gone. None of the previously > >reported errors are seen. I am running a level 0 dump from disk to disk > >to see if the box remains stable. Given that this is my primary machine > >I sure hope it will be :-) > > > >>>Another snag is that my ad10 disk on 6.0-STABLE suddenly became ad12 on > >>>6.1-PRE > >>Hmm that is because there is only 2 ports on your promise which is now > >>correctly identified, before it was errounsly found as 3 ports. > > > >Ah, OK. I would suggest a note to the Release Note writers would be a good > >thing, devices changing location after an upgrade in the -stable branch > >is unnerving ;-) > > Well, the good thing is that I can reproduce the error here, the bad > thing is that it slipped through testing on -current... > Oh, well, I'll look into it ASAP... Thank you Soren! -- Wilko Bulte wilko@FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060208221056.GA1299>