Date: Wed, 1 Jun 2011 16:18:20 +0000 From: Holger Kipp <Holger.Kipp@alogis.com> To: Jeremy Chadwick <freebsd@jdc.parodius.com> Cc: "stable@freebsd.org" <stable@freebsd.org>, "mav@freebsd.org" <mav@freebsd.org> Subject: RE: 8-STABLE won't boot with ZFSv28 Message-ID: <814C9E9472FDCC40AAC3FC95A2D67E3B0BD890BD@msx3.exchange.alogis.com> In-Reply-To: <814C9E9472FDCC40AAC3FC95A2D67E3B0BD88F48@msx3.exchange.alogis.com> References: <814C9E9472FDCC40AAC3FC95A2D67E3B0BD88C69@msx3.exchange.alogis.com> <20110601085454.GA19434@icarus.home.lan> <814C9E9472FDCC40AAC3FC95A2D67E3B0BD88DC0@msx3.exchange.alogis.com>, <20110601095610.GA20255@icarus.home.lan>, <814C9E9472FDCC40AAC3FC95A2D67E3B0BD88F48@msx3.exchange.alogis.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Dear all, got the same messages over and over again - panic took some time: unknown: WARNING - ATAPI_IDENTIFY requeued due to channel reset LBA=3D0 ata0: reinit done .. ata0: reiniting channel .. ata0: DISCONNECT requested <short delay here> ata0: p0: SATA connect time=3D0ms status=3D00000113 ata0: p1: SATA connect timeout status=3D00000000 ata0: reset tp1 mask=3D03 ostat0=3D00 ostat1=3D00 ata0: stat0=3D0x00 err=3D0x01 lsb=3D0x14 msb=3D0xeb ata0: stat1=3D0x00 err=3D0x01 lsb=3D0x14 msb=3D0xeb ata0: reset tp2 stat0=3D00 stat1=3D00 devices=3D0x30000 unknown: WARNING - ATAPI_IDENTIFY requeued due to channel reset LBA=3D0 ata0: reinit done .. ata0: reiniting channel .. ata0: DISCONNECT requested <short delay here> ata0: p0: SATA connect time=3D0ms status=3D00000113 ata0: p1: SATA connect timeout status=3D00000000 ata0: reset tp1 mask=3D03 ostat0=3D00 ostat1=3D00 ata0: stat0=3D0x00 err=3D0x01 lsb=3D0x14 msb=3D0xeb ata0: stat1=3D0x00 err=3D0x01 lsb=3D0x14 msb=3D0xeb ata0: reset tp2 stat0=3D00 stat1=3D00 devices=3D0x30000 unknown: WARNING - ATAPI_IDENTIFY requeued due to channel reset LBA=3D0 ata0: reinit done .. ata0: reiniting channel .. ata0: DISCONNECT requested <short delay here> ata0: p0: SATA connect time=3D0ms status=3D00000113 ata0: p1: SATA connect timeout status=3D00000000 ata0: reset tp1 mask=3D03 ostat0=3D00 ostat1=3D00 ata0: stat0=3D0x00 err=3D0x01 lsb=3D0x14 msb=3D0xeb ata0: stat1=3D0x00 err=3D0x01 lsb=3D0x14 msb=3D0xeb ata0: reset tp2 stat0=3D00 stat1=3D00 devices=3D0x30000 might presumably take about an hour before system will drop me to a db> prompt. Hmm - last time system was up about 1 hour... Ah no, my mistake. <wild guessing mode>Assuming we have a 512kB buffer for such messages, then at about two roundtrips per second, only issuing th= e WARNING, this would need about 1 hour. For all the detailed messages, it would reach the same amount in about 10 Minutes. Just went back to the server, and already had the db> prompt this time. Hooray.</wild guessing mode> Files can be found here: info.0: http://www.hkipp.de/dump/info.0 core.txt.0: http://www.hkipp.de/dump/core.txt.0 please let me know if this is useful :-) Best regards, Holger ________________________________________ From: owner-freebsd-stable@freebsd.org [owner-freebsd-stable@freebsd.org] o= n behalf of Holger Kipp [Holger.Kipp@alogis.com] Sent: 01 June 2011 13:36 To: Jeremy Chadwick Cc: stable@freebsd.org; mav@freebsd.org Subject: RE: 8-STABLE won't boot with ZFSv28 Dear all, just a short update on the issue: I changed SATA setting in BIOS to AHCI and can now boot without problems. Thanks very much for the hint! Interesting thing is that only the DVD-drive is directly attached using SAT= A: - System Disks are attached using 3ware-controller (mirror, twe) - ZPool devices are accessed via FibreChannel. I'll try to provide more verbose info later during the day by preparing the= current kernel and including the required debugging settings and then rebooting with AHCI disabled again - but normal work is currently kicking in again... Best regards, Holger ________________________________________ From: Jeremy Chadwick [freebsd@jdc.parodius.com] Sent: 01 June 2011 11:56 To: Holger Kipp Cc: stable@freebsd.org; mav@freebsd.org Subject: Re: 8-STABLE won't boot with ZFSv28 On Wed, Jun 01, 2011 at 09:26:05AM +0000, Holger Kipp wrote: > Jeremy Chadwick [freebsd@jdc.parodius.com] wrote on 01 June 2011 10:54 > > >On Wed, Jun 01, 2011 at 08:23:19AM +0000, Holger Kipp wrote: > >> I have a very irritating problem with 8-STABLE and ZFSv28 > >> > >> I upgraded to 8-STABLE as of yesterday (31.05.2011), > >> downloaded stable-8-zfsv28-20110521.patch.xz > >> and applied the patch using > >> > >> cd /usr/src > >> patch -E -p0 < /path/to/patchfile > >> make buildworld > >> make buildkernel KERNCONF=3Dfoo > >> make installkernel KERNCONF=3Dfoo > >> make installworld > >> mergemaster > >> > >> which all went smoothly. > >> > >> After reboot, I only got > >> unknown: WARNING - ATAPI_IDENTITFY requeued due to channel reset LBA= =3D0 > >> all the time, and then after an hour or so (wasn't on site), > >> system gave > >> Fatal trap 12: page fault while in kernel mode > >> cupid - 0; apic id =3D 00 > >> fault virtual address =3D 0x8 > >> fault code =3D supervisor read data, page not pr= esent > >> instruction pointer =3D 0x20:0xffffffff80252301 > >> stack poiner =3D 0x28:0xffffff80000a7ac0 > >> frame pointer =3D 0x28:0xffffff80000a7b00 > >> code segment =3D base 0x0, limit 0xfffff, type 0x1b > >> =3D DPL 0, pres1, long = 1, def32 0, gran 1 > >> processor eflags =3D interrupt enabled, resume, IOPL =3D 0 > >> current process =3D 0 (thread taskq)trap number = =3D 12 > >> panic: page fault > >> cpuid =3D 0 > >> Uptime: 1h0m13s > >> Cannot dump. Device not defined or unavailable. > >> Automatic reboot in 15 seconds - press a key on the console to abort > >> > >> Needless to say the system did not reboot. Had to powercycle. > >> > >> Then always got the > >> unknown: WARNING - ATAPI_IDENTITFY requeued due to channel reset LBA= =3D0 > >> error about once per second. > >> > >> Have now used a fixit-disk to change back to the old kernel: > >> FreeBSD 8.2-STABLE #12: Mon Apr 18 12:48:56 CEST 2011 > >> and rebootet. > >> Now zfs claims to be v28, current storage pool is at 15.I'd love to > >> try ZFSv28, but with the old kernel I don't think > >> this is a good idea - but with the new kernel it seems I can't > >> even boot properly. > >> Any suggestions as to how to proceed? > > > I think this is much more likely related to an ATA/ATAPI-related change > > that was committed on April 17th recently and is not related to ZFSv28. > > Please see this thread: > > > > * 2011/05/29 -- ICH9 panic/instability on recent kernel > > http://lists.freebsd.org/pipermail/freebsd-stable/2011-May/thread.htm= l#62804 > > > > Holger, can you please provide the following two things? > > > > 1) Output from "pciconf -lvcb". > > That's an easy one: > > hostb0@pci0:0:0:0: class=3D0x060000 card=3D0xd28015d9 chip=3D0x29f08= 086 rev=3D0x01 hdr=3D0x00 > vendor =3D 'Intel Corporation' > device =3D '3200 Chipset (Bearlake) Processor to I/O Controller' > class =3D bridge > subclass =3D HOST-PCI > cap 09[e0] =3D vendor (length 12) Intel cap 9 version 1 > pcib1@pci0:0:1:0: class=3D0x060400 card=3D0xd28015d9 chip=3D0x29f18= 086 rev=3D0x01 hdr=3D0x01 > vendor =3D 'Intel Corporation' > device =3D '3200 Chipset (Bearlake) PCIe Root Port 1' > class =3D bridge > subclass =3D PCI-PCI > cap 0d[88] =3D PCI Bridge card=3D0xd28015d9 > cap 01[80] =3D powerspec 3 supports D0 D3 current D0 > cap 05[90] =3D MSI supports 1 message > cap 10[a0] =3D PCI-Express 2 root port max data 128(128) link x8(x16) > ecap 0002[100] =3D VC 1 max VC0 > ecap 0005[140] =3D unknown 1 > uhci0@pci0:0:26:0: class=3D0x0c0300 card=3D0xd28015d9 chip=3D0x29378= 086 rev=3D0x02 hdr=3D0x00 > vendor =3D 'Intel Corporation' > device =3D '82801IB/IR/IH (ICH9 Family) USB Universal Host Contro= ller' > class =3D serial bus > subclass =3D USB > bar [20] =3D type I/O Port, range 32, base 0x1820, size 32, enabled > cap 13[50] =3D PCI Advanced Features: FLR TP > uhci1@pci0:0:26:1: class=3D0x0c0300 card=3D0xd28015d9 chip=3D0x29388= 086 rev=3D0x02 hdr=3D0x00 > vendor =3D 'Intel Corporation' > device =3D '82801IB/IR/IH (ICH9 Family) USB Universal Host Contro= ller' > class =3D serial bus > subclass =3D USB > bar [20] =3D type I/O Port, range 32, base 0x1840, size 32, enabled > cap 13[50] =3D PCI Advanced Features: FLR TP > uhci2@pci0:0:26:2: class=3D0x0c0300 card=3D0xd28015d9 chip=3D0x29398= 086 rev=3D0x02 hdr=3D0x00 > vendor =3D 'Intel Corporation' > device =3D '82801IB/IR/IH (ICH9 Family) USB Universal Host Contro= ller' > class =3D serial bus > subclass =3D USB > bar [20] =3D type I/O Port, range 32, base 0x1860, size 32, enabled > cap 13[50] =3D PCI Advanced Features: FLR TP > ehci0@pci0:0:26:7: class=3D0x0c0320 card=3D0xd28015d9 chip=3D0x293c8= 086 rev=3D0x02 hdr=3D0x00 > vendor =3D 'Intel Corporation' > device =3D '82801IB/IR/IH (ICH9 Family) USB2 Enhanced Host Contro= ller' > class =3D serial bus > subclass =3D USB > bar [10] =3D type Memory, range 32, base 0xd9001000, size 1024, ena= bled > cap 01[50] =3D powerspec 2 supports D0 D3 current D0 > cap 0a[58] =3D EHCI Debug Port at offset 0xa0 in map 0x14 > cap 13[98] =3D PCI Advanced Features: FLR TP > pcib4@pci0:0:28:0: class=3D0x060400 card=3D0xd28015d9 chip=3D0x29408= 086 rev=3D0x02 hdr=3D0x01 > vendor =3D 'Intel Corporation' > device =3D '82801IB/IR/IH (ICH9 Family) PCIe Root Port 1' > class =3D bridge > subclass =3D PCI-PCI > cap 10[40] =3D PCI-Express 1 root port max data 128(128) link x4(x4) > cap 05[80] =3D MSI supports 1 message > cap 0d[90] =3D PCI Bridge card=3D0xd28015d9 > cap 01[a0] =3D powerspec 2 supports D0 D3 current D0 > ecap 0002[100] =3D VC 1 max VC0 > ecap 0005[180] =3D unknown 1 > pcib5@pci0:0:28:4: class=3D0x060400 card=3D0xd28015d9 chip=3D0x29488= 086 rev=3D0x02 hdr=3D0x01 > vendor =3D 'Intel Corporation' > device =3D '82801IB/IR/IH (ICH9 Family) PCIe Root Port 5' > class =3D bridge > subclass =3D PCI-PCI > cap 10[40] =3D PCI-Express 1 root port max data 128(128) link x1(x1) > cap 05[80] =3D MSI supports 1 message > cap 0d[90] =3D PCI Bridge card=3D0xd28015d9 > cap 01[a0] =3D powerspec 2 supports D0 D3 current D0 > ecap 0002[100] =3D VC 1 max VC0 > ecap 0005[180] =3D unknown 1 > pcib6@pci0:0:28:5: class=3D0x060400 card=3D0xd28015d9 chip=3D0x294a8= 086 rev=3D0x02 hdr=3D0x01 > vendor =3D 'Intel Corporation' > device =3D '82801IB/IR/IH (ICH9 Family) PCIe Root Port 6' > class =3D bridge > subclass =3D PCI-PCI > cap 10[40] =3D PCI-Express 1 root port max data 128(128) link x1(x1) > cap 05[80] =3D MSI supports 1 message > cap 0d[90] =3D PCI Bridge card=3D0xd28015d9 > cap 01[a0] =3D powerspec 2 supports D0 D3 current D0 > ecap 0002[100] =3D VC 1 max VC0 > ecap 0005[180] =3D unknown 1 > uhci3@pci0:0:29:0: class=3D0x0c0300 card=3D0xd28015d9 chip=3D0x29348= 086 rev=3D0x02 hdr=3D0x00 > vendor =3D 'Intel Corporation' > device =3D '82801IB/IR/IH (ICH9 Family) USB Universal Host Contro= ller' > class =3D serial bus > subclass =3D USB > bar [20] =3D type I/O Port, range 32, base 0x1880, size 32, enabled > cap 13[50] =3D PCI Advanced Features: FLR TP > uhci4@pci0:0:29:1: class=3D0x0c0300 card=3D0xd28015d9 chip=3D0x29358= 086 rev=3D0x02 hdr=3D0x00 > vendor =3D 'Intel Corporation' > device =3D '82801IB/IR/IH (ICH9 Family) USB Universal Host Contro= ller' > class =3D serial bus > subclass =3D USB > bar [20] =3D type I/O Port, range 32, base 0x18a0, size 32, enabled > cap 13[50] =3D PCI Advanced Features: FLR TP > uhci5@pci0:0:29:2: class=3D0x0c0300 card=3D0xd28015d9 chip=3D0x29368= 086 rev=3D0x02 hdr=3D0x00 > vendor =3D 'Intel Corporation' > device =3D '82801IB/IR/IH (ICH9 Family) USB Universal Host Contro= ller' > class =3D serial bus > subclass =3D USB > bar [20] =3D type I/O Port, range 32, base 0x18c0, size 32, enabled > cap 13[50] =3D PCI Advanced Features: FLR TP > ehci1@pci0:0:29:7: class=3D0x0c0320 card=3D0xd28015d9 chip=3D0x293a8= 086 rev=3D0x02 hdr=3D0x00 > vendor =3D 'Intel Corporation' > device =3D '82801IB/IR/IH (ICH9 Family) USB2 Enhanced Host Contro= ller' > class =3D serial bus > subclass =3D USB > bar [10] =3D type Memory, range 32, base 0xd9001400, size 1024, ena= bled > cap 01[50] =3D powerspec 2 supports D0 D3 current D0 > cap 0a[58] =3D EHCI Debug Port at offset 0xa0 in map 0x14 > cap 13[98] =3D PCI Advanced Features: FLR TP > pcib7@pci0:0:30:0: class=3D0x060401 card=3D0xd28015d9 chip=3D0x244e8= 086 rev=3D0x92 hdr=3D0x01 > vendor =3D 'Intel Corporation' > device =3D '82801 Family (ICH2/3/4/5/6/7/8/9,63xxESB) Hub Interfa= ce to PCI Bridge' > class =3D bridge > subclass =3D PCI-PCI > cap 0d[50] =3D PCI Bridge card=3D0xd28015d9 > isab0@pci0:0:31:0: class=3D0x060100 card=3D0xd28015d9 chip=3D0x29168= 086 rev=3D0x02 hdr=3D0x00 > vendor =3D 'Intel Corporation' > device =3D '82801IR (ICH9R) LPC Interface Controller' > class =3D bridge > subclass =3D PCI-ISA > cap 09[e0] =3D vendor (length 12) Intel cap 1 version 0 > features: SATA RAID-5, 4 PCI-e x1 slots > atapci0@pci0:0:31:2: class=3D0x01018a card=3D0xd28015d9 chip=3D0x29208= 086 rev=3D0x02 hdr=3D0x00 > vendor =3D 'Intel Corporation' > device =3D '82801IB/IR/IH (ICH9 Family) 4 port Serial ATA Storage= Controller 1' > class =3D mass storage > subclass =3D ATA > bar [10] =3D type I/O Port, range 32, base 0x1f0, size 8, enabled > bar [14] =3D type I/O Port, range 32, base 0x3f4, size 1, enabled > bar [18] =3D type I/O Port, range 32, base 0x170, size 8, enabled > bar [1c] =3D type I/O Port, range 32, base 0x374, size 1, enabled > bar [20] =3D type I/O Port, range 32, base 0x1c10, size 16, enabled > bar [24] =3D type I/O Port, range 32, base 0x1c00, size 16, enabled > cap 01[70] =3D powerspec 3 supports D0 D3 current D0 > cap 13[b0] =3D PCI Advanced Features: FLR TP > none0@pci0:0:31:3: class=3D0x0c0500 card=3D0xd28015d9 chip=3D0x29308= 086 rev=3D0x02 hdr=3D0x00 > vendor =3D 'Intel Corporation' > device =3D 'Intel(R) ICH9 Family SMBus Controller working fine wi= th http://download.cnet.com/Chipset-Driver-Inte (8086)' > class =3D serial bus > subclass =3D SMBus > bar [10] =3D type Memory, range 64, base 0xd9001800, size 256, enab= led > bar [20] =3D type I/O Port, range 32, base 0x1100, size 32, enabled > atapci1@pci0:0:31:5: class=3D0x010185 card=3D0xd28015d9 chip=3D0x29268= 086 rev=3D0x02 hdr=3D0x00 > vendor =3D 'Intel Corporation' > device =3D '82801IB/IR/IH (ICH9 Family) 2 port Serial ATA Storage= Controller 2' > class =3D mass storage > subclass =3D ATA > bar [10] =3D type I/O Port, range 32, base 0x1c68, size 8, enabled > bar [14] =3D type I/O Port, range 32, base 0x1c5c, size 4, enabled > bar [18] =3D type I/O Port, range 32, base 0x1c60, size 8, enabled > bar [1c] =3D type I/O Port, range 32, base 0x1c58, size 4, enabled > bar [20] =3D type I/O Port, range 32, base 0x1c30, size 16, enabled > bar [24] =3D type I/O Port, range 32, base 0x1c20, size 16, enabled > cap 01[70] =3D powerspec 3 supports D0 D3 current D0 > cap 13[b0] =3D PCI Advanced Features: FLR TP > none1@pci0:0:31:6: class=3D0x118000 card=3D0x000015d9 chip=3D0x29328= 086 rev=3D0x02 hdr=3D0x00 > vendor =3D 'Intel Corporation' > device =3D '82801IB/IR/IH (ICH9 Family) Thermal Subsystem' > class =3D dasp > bar [10] =3D type Memory, range 64, base 0xd9000000, size 4096, ena= bled > cap 01[50] =3D powerspec 3 supports D0 D3 current D0 > pcib2@pci0:1:0:0: class=3D0x060400 card=3D0x00000000 chip=3D0x03298= 086 rev=3D0x09 hdr=3D0x01 > vendor =3D 'Intel Corporation' > device =3D 'PCI Express-to-PCI Express Bridge A (6700PXH)' > class =3D bridge > subclass =3D PCI-PCI > cap 10[44] =3D PCI-Express 1 PCI bridge max data 128(256) link x8(x8) > cap 05[5c] =3D MSI supports 1 message, 64 bit > cap 01[6c] =3D powerspec 2 supports D0 D3 current D0 > cap 07[d8] =3D PCI-X bridge > ecap 0001[100] =3D AER 1 0 fatal 1 non-fatal 0 corrected > ecap 0004[300] =3D unknown 1 > ioapic0@pci0:1:0:1: class=3D0x080020 card=3D0xd28015d9 chip=3D0x03268= 086 rev=3D0x09 hdr=3D0x00 > vendor =3D 'Intel Corporation' > device =3D '6700/6702PXH I/OxAPIC Interrupt Controller A' > class =3D base peripheral > subclass =3D interrupt controller > bar [10] =3D type Memory, range 32, base 0xd8900000, size 4096, ena= bled > cap 10[44] =3D PCI-Express 1 endpoint max data 256(256) link x8(x8) > cap 01[6c] =3D powerspec 2 supports D0 D3 current D0 > pcib3@pci0:1:0:2: class=3D0x060400 card=3D0x00000000 chip=3D0x032a8= 086 rev=3D0x09 hdr=3D0x01 > vendor =3D 'Intel Corporation' > device =3D 'PCI Express-to-PCI Express Bridge B (6700PXH)' > class =3D bridge > subclass =3D PCI-PCI > cap 10[44] =3D PCI-Express 1 PCI bridge max data 128(256) link x8(x8) > cap 05[5c] =3D MSI supports 1 message, 64 bit > cap 01[6c] =3D powerspec 2 supports D0 D3 current D0 > cap 07[d8] =3D PCI-X bridge > ecap 0001[100] =3D AER 1 0 fatal 1 non-fatal 0 corrected > ecap 0004[300] =3D unknown 1 > ioapic1@pci0:1:0:3: class=3D0x080020 card=3D0xd28015d9 chip=3D0x03278= 086 rev=3D0x09 hdr=3D0x00 > vendor =3D 'Intel Corporation' > device =3D 'I/OxAPIC Interrupt Controller B (6700PXH)' > class =3D base peripheral > subclass =3D interrupt controller > bar [10] =3D type Memory, range 32, base 0xd8901000, size 4096, ena= bled > cap 10[44] =3D PCI-Express 1 endpoint max data 256(256) link x8(x8) > cap 01[6c] =3D powerspec 2 supports D0 D3 current D0 > twe0@pci0:2:1:0: class=3D0x010400 card=3D0x100113c1 chip=3D0x10011= 3c1 rev=3D0x01 hdr=3D0x00 > vendor =3D '3ware Inc' > device =3D 'ATA-133 Storage Controller (7000/8000 series)' > class =3D mass storage > subclass =3D RAID > bar [10] =3D type I/O Port, range 32, base 0x2000, size 16, enabled > bar [14] =3D type Memory, range 32, base 0xd8800000, size 16, enabl= ed > bar [18] =3D type Memory, range 32, base 0xd8000000, size 8388608, = enabled > cap 01[40] =3D powerspec 1 supports D0 D1 D3 current D0 > isp0@pci0:5:0:0: class=3D0x0c0400 card=3D0x01371077 chip=3D0x24321= 077 rev=3D0x03 hdr=3D0x00 > vendor =3D 'QLogic Corporation' > device =3D 'Dual Channel 4G PCIe Fibre Channel Adapter (ISP2432)' > class =3D serial bus > subclass =3D Fibre Channel > bar [10] =3D type I/O Port, range 32, base 0x3000, size 256, enable= d > bar [14] =3D type Memory, range 64, base 0xd8b00000, size 16384, en= abled > cap 01[44] =3D powerspec 2 supports D0 D3 current D0 > cap 10[4c] =3D PCI-Express 1 endpoint max data 128(1024) link x4(x4) > cap 05[64] =3D MSI supports 16 messages, 64 bit enabled with 1 messag= e > cap 03[74] =3D VPD > cap 11[7c] =3D MSI-X supports 16 messages in map 0x14 > ecap 0001[100] =3D AER 1 0 fatal 1 non-fatal 0 corrected > ecap 0004[138] =3D unknown 1 > em0@pci0:13:0:0: class=3D0x020000 card=3D0x108c15d9 chip=3D0x108c8= 086 rev=3D0x03 hdr=3D0x00 > vendor =3D 'Intel Corporation' > device =3D 'Intel Corporation 82573E Gigabit Ethernet Controller = (Copper) (82573E)' > class =3D network > subclass =3D ethernet > bar [10] =3D type Memory, range 32, base 0xd8a00000, size 131072, e= nabled > bar [18] =3D type I/O Port, range 32, base 0x4000, size 32, enabled > cap 01[c8] =3D powerspec 2 supports D0 D3 current D0 > cap 05[d0] =3D MSI supports 1 message, 64 bit enabled with 1 message > cap 10[e0] =3D PCI-Express 1 endpoint max data 128(256) link x1(x1) > ecap 0001[100] =3D AER 1 0 fatal 1 non-fatal 0 corrected > ecap 0003[140] =3D Serial 1 003048ffffd21aba > em1@pci0:15:0:0: class=3D0x020000 card=3D0x109a15d9 chip=3D0x109a8= 086 rev=3D0x00 hdr=3D0x00 > vendor =3D 'Intel Corporation' > device =3D 'Intel PRO/1000 PL Network Adaptor (82573L)' > class =3D network > subclass =3D ethernet > bar [10] =3D type Memory, range 32, base 0xd8c00000, size 131072, e= nabled > bar [18] =3D type I/O Port, range 32, base 0x5000, size 32, enabled > cap 01[c8] =3D powerspec 2 supports D0 D3 current D0 > cap 05[d0] =3D MSI supports 1 message, 64 bit enabled with 1 message > cap 10[e0] =3D PCI-Express 1 endpoint max data 128(256) link x1(x1) > ecap 0001[100] =3D AER 1 0 fatal 1 non-fatal 0 corrected > ecap 0003[140] =3D Serial 1 003048ffffd21abb > vgapci0@pci0:17:4:0: class=3D0x030000 card=3D0xd28015d9 chip=3D0x515e1= 002 rev=3D0x02 hdr=3D0x00 > vendor =3D 'ATI Technologies Inc. / Advanced Micro Devices, Inc.' > device =3D 'Radeon ES1000 (Radeon ES1000)' > class =3D display > subclass =3D VGA > bar [10] =3D type Prefetchable Memory, range 32, base 0xd0000000, s= ize 134217728, enabled > bar [14] =3D type I/O Port, range 32, base 0x6000, size 256, enable= d > bar [18] =3D type Memory, range 32, base 0xd8d00000, size 65536, en= abled > cap 01[50] =3D powerspec 2 supports D0 D1 D2 D3 current D0 > > > > 2) Full output from a verbose boot (option "5" at the loader prompt). > > That's a bit more difficult... I'll check, but don't think anything is se= t up > there to get a meaningful dump or verbose boot information in electronic = form... > > > I imagine #2 isn't going to work for most users because there's no way > > to get pages and pages and pages of data from a panic'd machine without > > either serial console (which will require a 2nd machine and possibly a > > null-modem cable) or properly setting up a dedicated swap partition and > > large-enough /var filesystem, plus their kernel would need DDB support > > added to it (so they could properly do "call doadump" then "reboot"). By the way, regarding this specific explanation -- you'll need dumpdev=3D"auto" in rc.conf for this to work, plus after the panic will need to ensure that the very next kernel which boots can work reliably. I'll explain how I'd go about this -- there may be an easier way, but it's what I'd do. - Adjust your kernel config to include these options: options KDB # Enable kernel debugger support options KDB_TRACE # Print stack trace automatically= on panic options DDB # Support DDB options GDB # Support remote GDB options MSGBUF_SIZE=3D262144 # Increase kern.msgbufsize from= 64K to 256K - Make sure you have a dedicated swap partition, and /var big enough to hold a kernel panic (panic will probably be ~1-2GB in size). Or make a new filesystem for /var/crash (if so, be sure to copy over /var/crash/minfree!) - Add dumpdev=3D"auto" to /etc/rc.conf. - Add ddb_enable=3D"yes" to /etc/rc.conf. - Revert /usr/src to RELENG_8 dated April 16th or earlier. You can accomplish this using "date=3DYYYY.MM.DD.hh.mm.ss" in your csup file. See csup(1) man page for details. I imagine svn has a better way to do this, but I don't use it. - Rebuild world/kernel per instructions in /usr/src/Makefile. This will get you a kernel and system which won't panic. - Update RELENG_8 to latest source code (e.g. remove "date=3D" line you just added) using csup (or svn method). - Rebuild world/kernel per instructions in /usr/src/Makefile. This will get you a kernel and system which WILL panic, with the old (usable) kernel in /boot/kernel.old. - Boot into "bad" kernel, but at the loader menu, pick option 5 for a verbose boot. - Panic will happen and drop you to a db> prompt. There, you should do "call doadump" and then "reboot". The first will cause the kernel to dump memory to your swap partition, the 2nd will reboot. - Boot into "good" kernel by pressing option 6 at the loader menu, then at "ok" prompt enter "boot kernel.old". If that doesn't work, you might need to do something like this: unload load /boot/kernel.old/kernel load -t /boot/zfs/zpool.cache /boot/zfs/zpool.cache boot - During the startup phase, savecore(8) will detect the crash from the previous kernel and populate /var/crash with details. One of these files will be /var/crash/core.txt.0, which should contain the contents of your verbose dmesg (or most of it anyway; this is why I adjusted MSGBUF_SIZE). I sure hope this works. :-) Serial console would, as I said, be a better choice. You wouldn't need to worry about all the panic/crash/swap stuff -- a verbose boot would be all you'd need, and you'd have the output on another machine in its scrollback buffer from whatever terminal or utility you were using that connected to the serial port. > > A workaround which one user has confirmed is to enable AHCI for your > > SATA controller in your system BIOS (if such is available). ataahci.ko > > will be used (which is AHCI via ATA) and your device names probably > > won't change. Alternatively you could enable AHCI and use ahci.ko > > (ahci_load=3D"yes" in /boot/loader.conf) to get AHCI via CAM, which > > provides NCQ and other features, but your device names will change. > > My familiarity with ATAPI is limited however. > > Will try both if available and let you know the results. Understood. The former method worked for Michael, and I imagine it would work for you too if AHCI is available in your BIOS. I tend to advocate people use ahci.ko if they're using AHCI at all though, given the excellent CAM subsystem. -- Holger Kipp Diplom-Mathematiker Senior Consultant Tel. : +49 30 436 58 114 Fax. : +49 30 436 58 214 Mobil: +49 178 36 58 114 Email: holger.kipp@alogis.com alogis AG Alt-Moabit 90b D-10559 Berlin web : http://www.alogis.com ---------------------------------------------------------- alogis AG Sitz/Registergericht: Berlin/AG Charlottenburg, HRB 71484 Vorstand: Arne Friedrichs, Joern Samuelson Aufsichtsratsvorsitzender: Reinhard Mielke
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?814C9E9472FDCC40AAC3FC95A2D67E3B0BD890BD>