From owner-freebsd-stable@FreeBSD.ORG Wed Feb 16 15:21:47 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4C3DC16A4CE for ; Wed, 16 Feb 2005 15:21:47 +0000 (GMT) Received: from woozle.rinet.ru (woozle.rinet.ru [195.54.192.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6921043D39 for ; Wed, 16 Feb 2005 15:21:46 +0000 (GMT) (envelope-from marck@rinet.ru) Received: from localhost (localhost [127.0.0.1]) by woozle.rinet.ru (8.13.1/8.13.1) with ESMTP id j1GFLgoK039313; Wed, 16 Feb 2005 18:21:42 +0300 (MSK) (envelope-from marck@rinet.ru) Date: Wed, 16 Feb 2005 18:21:42 +0300 (MSK) From: Dmitry Morozovsky To: Doug Ambrisko In-Reply-To: <200502161508.j1GF8Vad069851@ambrisko.com> Message-ID: <20050216181719.T29389@woozle.rinet.ru> References: <200502161508.j1GF8Vad069851@ambrisko.com> X-NCC-RegID: ru.rinet MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: stable@FreeBSD.org Subject: Re: stable sata patch: panic at kernel boot (can't dump) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Feb 2005 15:21:47 -0000 On Wed, 16 Feb 2005, Doug Ambrisko wrote: DA> | trying to boot RELENG_4 kernel with your patches (sata_7) on our FTP I got DA> | kernel panic (page fault in kernel mode, pid 2, no dump possible). Hardware DA> | involved: DA> | DA> | root@kucha:~# grep ata /var/run/dmesg.boot DA> | atapci0: port 0xa000-0xa03f,0x9c00-0x9c03,0x9800-0x9807,0x9400-0x9403,0x9000-0x9007 mem 0xed100000-0xed11ffff irq 11 at device 8.0 on pci0 DA> | ata2: at 0x9000 on atapci0 DA> | ata3: at 0x9800 on atapci0 DA> | atapci1: port 0xb400-0xb40f,0xb000-0xb003,0xac00-0xac07,0xa800-0xa803,0xa400-0xa407 irq 10 at device 9.0 on pci0 DA> | ata4: at 0xa400 on atapci1 DA> | ata5: at 0xac00 on atapci1 DA> | atapci2: port 0xbc00-0xbc0f at device 17.1 on pci0 DA> | ata0: at 0x1f0 irq 14 on atapci2 DA> | ata1: at 0x170 irq 15 on atapci2 DA> | ad0: 238475MB [484521/16/63] at ata0-master UDMA100 DA> | ad2: 114473MB [232581/16/63] at ata1-master UDMA100 DA> | ad4: 76319MB [155061/16/63] at ata2-master UDMA66 DA> | ad6: 76319MB [155061/16/63] at ata3-master UDMA66 DA> | ad8: 57241MB [116301/16/63] at ata4-master UDMA100 DA> | DA> | Kernel paniced just after sio0/sio1, where basic RELENG_4 starts ata channel DA> | probes. No serial console at the moment, alas. DA> | DA> | Unfortunately I can't bring this machine out of service for long time; however, DA> | we can survive occasional reboots/crashes. What other info can I provide to DA> | debug this? DA> DA> I'd like some clarification. Does the system boot sometimes and other times DA> is doesn't? Once the system is up does it stay up for a while? It doesn't DA> seem like you are not using RAID. I have a couple more ata bug fixes that DA> I need to roll into another patchset. It fixes a bug in which DMA transfers DA> have not been cancelled when the controller is reset. I fixed another DA> panic situation in version 8 that happens on boot if you have a bad sector DA> at the beginning of the drive. I'd wait to version 9. I should be able DA> to get that out later today. Sorry to not being specific enough ;-) No, the system panics reliably, just after sio initializing (for me it seems ata drives probes phase). I did not use hardware RAID, I use vinum over these 5 drives. Without the patchset system stays up for months acting as ftp/cvsupd/nfsd server without any single issue. DA> Another thing that you might want to do is monitor dmesgs for any DA> ata/ad errors while the system is running. Most panics happen later DA> after the first error message. Also you could try looking at DA> /var/log/messages. Nope, there are no such errors (I would expect them for CMD-649, but luckily even that beastie works fine) Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru *** ------------------------------------------------------------------------