Date: Thu, 9 Feb 2006 09:51:47 +0100 From: Jens Trzaska <jt@barfoos.de> 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: <20060209085147.GB78035@anastasia.lan.barfoos.de> 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
Hi, * Søren Schmidt <sos@deepcore.dk> [2006-02-08 22:44]: > 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... I have seen nearly the same problem after upgrading to -stable at the weekend. I digged through the commits and went back to 2006.01.25.00.00.00 of -stable as there were many ata and gmirror commits that time. That helped to get the mirror back alive. I am willing to test patches as I'm prepared now. Feb 5 12:21:00 beast kernel: ad6: req=0xc4e487d0 SETFEATURES SET TRANSFER MODE semaphore timeout !! DANGER Will Robinson !! Feb 5 12:21:04 beast kernel: ad6: req=0xc4e487d0 SETFEATURES SET TRANSFER MODE semaphore timeout !! DANGER Will Robinson !! This is my controller: atapci1: <Promise PDC40518 SATA150 controller> port 0xdc00-0xdc7f,0xe000-0xe0ff mem 0xdf521000-0xdf521fff,0xdf500000-0xdf51ffff irq 16 at device 12.0 on pci0 ata2: <ATA channel 0> on atapci1 ata3: <ATA channel 1> on atapci1 ata4: <ATA channel 2> on atapci1 ata5: <ATA channel 3> on atapci1 jens
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060209085147.GB78035>