Re: 8-STABLE won't boot with ZFSv28
Hi all, as yesterday was a bank holiday in Germany I wasn't in the office to try the patch linked in the email. Is it consent that I should try the patch located here: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/ata/chipsets/ata-intel.c.diff?r1=1.25;r2=1.26 and report the result? Or do you need some additional discussion on this topic? I really don't know much about ata-intel chipset programming interface things, that's why I'm asking :-) Best regards, Holger on 02.06.2011 10:37, Alexander Motin wrote: Jeremy Chadwick wrote: On Thu, Jun 02, 2011 at 09:53:58AM +0300, Alexander Motin wrote: Holger Kipp wrote: got the same messages over and over again - panic took some time: unknown: WARNING - ATAPI_IDENTIFY requeued due to channel reset LBA=0 ata0: reinit done .. ata0: reiniting channel .. ata0: DISCONNECT requested short delay here ata0: p0: SATA connect time=0ms status=0113 ata0: p1: SATA connect timeout status= ata0: reset tp1 mask=03 ostat0=00 ostat1=00 ata0: stat0=0x00 err=0x01 lsb=0x14 msb=0xeb ata0: stat1=0x00 err=0x01 lsb=0x14 msb=0xeb ata0: reset tp2 stat0=00 stat1=00 devices=0x3 unknown: WARNING - ATAPI_IDENTIFY requeued due to channel reset LBA=0 ata0: reinit done .. ata0: reiniting channel .. ata0: DISCONNECT requested I see two problems here: 1. devices=0x3 means that two ATAPI devices were detected instead of one. I can reproduce it also with other Intel chipsets. It looks like a hardware bug to me. It can be workarounded by reconnecting ATAPI device to even (2 or 4) SATA port, or connecting any other device there. 2. DISCONNECT requested means that controller reported PHY status change for some device on channel, triggering infinite retry. Unluckily I have no ICH9 board, while I can't reproduce it with ICH10 or above. This patch should workaround the first problem in software: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/ata/chipsets/ata-intel.c.diff?r1=1.25;r2=1.26 Try it please and let's see if with some luck it do something about the second problem. With regards to item #1: I don't see anything in the ICH9 errata that indicates a silicon bug if the only device attached to the controller is an ATAPI device and connected to SATA port 0 (presumably), or an odd-numbered port? If this problem exists on other ICHxx and/or ESBxx chips, I sure would hope it'd be documented. I haven't tried confirming it myself, but if need be I can set up a test box with a SATA-based DVD drive hooked up to it + provide remote serial console/etc. if it'd be of any help. I don't think it would be (sounds like you have lots of hardware :-) ), but I'm willing to help in any way I can. Intel probably don't see issue there, as the same behavior can be found even on latest chipsets. But according to my ATA specs understanding and real PATA devices behavior analysis, this behavior is not correct. When ATAPI device connected to the first of two SATA ports, routed to the same legacy-/PATA-emulated ATA channel (master device), soft-reset sequence returns false-positive slave ATAPI device presence. Problem doesn't expose with ATA disk devices, or if some other device really attached to the slave port. Problem looks like it was there always, but before ATA_CAM it was not usually noticed, due to very small IDENTIFY command timeouts in ata(4). If somebody can give better explanation or propose better workaround -- welcome, as I am not very like this solution. With regards to item #2: could this be at all related to OOB (bit 15) somehow being set in PCS (SATA register offset 0x92)? I'm doubting it but I thought I'd ask. My thought process, which is probably wrong (consider it an educational discussion :-) ): The ICH9 specification states that the default value for this register is 0x, and b15=0 means SATA controller will not retry after an OOB failure, while b15=1 causes the controller to indefinitely retry after OOB failure. I imagine system BIOSes and other things can change this default value, but we don't seem to print it anywhere in ata_intel_chipinit() during a verbose boot. Looking at chipsets/ata-intel.c, it looks like we only touch PCS in ata_intel_chipinit() and ata_intel_reset(). In the former, we avoid touching bits 4 through 15, and in the latter we mask out only what we want to adjust (e.g. the SATA port per ch variable). As as I can see, ata_intel.c should not change that bit if it was set for some reason. Theoretically, OOB (Out-of-Band signaling) is the function of the same state machine which sets that PHY changes status flag. But friendly speaking, I have no idea what result can be from setting of this bit. In this legacy/PATA emulation mode there are too many things not documented to be sure in anything. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any
Re: 8-STABLE won't boot with ZFSv28
Hi. Holger Kipp wrote: as yesterday was a bank holiday in Germany I wasn't in the office to try the patch linked in the email. Is it consent that I should try the patch located here: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/ata/chipsets/ata-intel.c.diff?r1=1.25;r2=1.26 and report the result? Or do you need some additional discussion on this topic? I really don't know much about ata-intel chipset programming interface things, that's why I'm asking :-) Yes, I want you to try it and report the result. -- Alexander Motin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 8-STABLE won't boot with ZFSv28
Hi. Holger Kipp wrote: got the same messages over and over again - panic took some time: unknown: WARNING - ATAPI_IDENTIFY requeued due to channel reset LBA=0 ata0: reinit done .. ata0: reiniting channel .. ata0: DISCONNECT requested short delay here ata0: p0: SATA connect time=0ms status=0113 ata0: p1: SATA connect timeout status= ata0: reset tp1 mask=03 ostat0=00 ostat1=00 ata0: stat0=0x00 err=0x01 lsb=0x14 msb=0xeb ata0: stat1=0x00 err=0x01 lsb=0x14 msb=0xeb ata0: reset tp2 stat0=00 stat1=00 devices=0x3 unknown: WARNING - ATAPI_IDENTIFY requeued due to channel reset LBA=0 ata0: reinit done .. ata0: reiniting channel .. ata0: DISCONNECT requested I see two problems here: 1. devices=0x3 means that two ATAPI devices were detected instead of one. I can reproduce it also with other Intel chipsets. It looks like a hardware bug to me. It can be workarounded by reconnecting ATAPI device to even (2 or 4) SATA port, or connecting any other device there. 2. DISCONNECT requested means that controller reported PHY status change for some device on channel, triggering infinite retry. Unluckily I have no ICH9 board, while I can't reproduce it with ICH10 or above. This patch should workaround the first problem in software: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/ata/chipsets/ata-intel.c.diff?r1=1.25;r2=1.26 Try it please and let's see if with some luck it do something about the second problem. -- Alexander Motin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 8-STABLE won't boot with ZFSv28
On Thu, Jun 02, 2011 at 09:53:58AM +0300, Alexander Motin wrote: Hi. Holger Kipp wrote: got the same messages over and over again - panic took some time: unknown: WARNING - ATAPI_IDENTIFY requeued due to channel reset LBA=0 ata0: reinit done .. ata0: reiniting channel .. ata0: DISCONNECT requested short delay here ata0: p0: SATA connect time=0ms status=0113 ata0: p1: SATA connect timeout status= ata0: reset tp1 mask=03 ostat0=00 ostat1=00 ata0: stat0=0x00 err=0x01 lsb=0x14 msb=0xeb ata0: stat1=0x00 err=0x01 lsb=0x14 msb=0xeb ata0: reset tp2 stat0=00 stat1=00 devices=0x3 unknown: WARNING - ATAPI_IDENTIFY requeued due to channel reset LBA=0 ata0: reinit done .. ata0: reiniting channel .. ata0: DISCONNECT requested I see two problems here: 1. devices=0x3 means that two ATAPI devices were detected instead of one. I can reproduce it also with other Intel chipsets. It looks like a hardware bug to me. It can be workarounded by reconnecting ATAPI device to even (2 or 4) SATA port, or connecting any other device there. 2. DISCONNECT requested means that controller reported PHY status change for some device on channel, triggering infinite retry. Unluckily I have no ICH9 board, while I can't reproduce it with ICH10 or above. This patch should workaround the first problem in software: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/ata/chipsets/ata-intel.c.diff?r1=1.25;r2=1.26 Try it please and let's see if with some luck it do something about the second problem. With regards to item #1: I don't see anything in the ICH9 errata that indicates a silicon bug if the only device attached to the controller is an ATAPI device and connected to SATA port 0 (presumably), or an odd-numbered port? If this problem exists on other ICHxx and/or ESBxx chips, I sure would hope it'd be documented. I haven't tried confirming it myself, but if need be I can set up a test box with a SATA-based DVD drive hooked up to it + provide remote serial console/etc. if it'd be of any help. I don't think it would be (sounds like you have lots of hardware :-) ), but I'm willing to help in any way I can. With regards to item #2: could this be at all related to OOB (bit 15) somehow being set in PCS (SATA register offset 0x92)? I'm doubting it but I thought I'd ask. My thought process, which is probably wrong (consider it an educational discussion :-) ): The ICH9 specification states that the default value for this register is 0x, and b15=0 means SATA controller will not retry after an OOB failure, while b15=1 causes the controller to indefinitely retry after OOB failure. I imagine system BIOSes and other things can change this default value, but we don't seem to print it anywhere in ata_intel_chipinit() during a verbose boot. Looking at chipsets/ata-intel.c, it looks like we only touch PCS in ata_intel_chipinit() and ata_intel_reset(). In the former, we avoid touching bits 4 through 15, and in the latter we mask out only what we want to adjust (e.g. the SATA port per ch variable). Reference material is 14.1.31 of the ICH9 datasheet: http://www.intel.com/assets/pdf/datasheet/316972.pdf -- | Jeremy Chadwick j...@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 8-STABLE won't boot with ZFSv28
Jeremy Chadwick wrote: On Thu, Jun 02, 2011 at 09:53:58AM +0300, Alexander Motin wrote: Holger Kipp wrote: got the same messages over and over again - panic took some time: unknown: WARNING - ATAPI_IDENTIFY requeued due to channel reset LBA=0 ata0: reinit done .. ata0: reiniting channel .. ata0: DISCONNECT requested short delay here ata0: p0: SATA connect time=0ms status=0113 ata0: p1: SATA connect timeout status= ata0: reset tp1 mask=03 ostat0=00 ostat1=00 ata0: stat0=0x00 err=0x01 lsb=0x14 msb=0xeb ata0: stat1=0x00 err=0x01 lsb=0x14 msb=0xeb ata0: reset tp2 stat0=00 stat1=00 devices=0x3 unknown: WARNING - ATAPI_IDENTIFY requeued due to channel reset LBA=0 ata0: reinit done .. ata0: reiniting channel .. ata0: DISCONNECT requested I see two problems here: 1. devices=0x3 means that two ATAPI devices were detected instead of one. I can reproduce it also with other Intel chipsets. It looks like a hardware bug to me. It can be workarounded by reconnecting ATAPI device to even (2 or 4) SATA port, or connecting any other device there. 2. DISCONNECT requested means that controller reported PHY status change for some device on channel, triggering infinite retry. Unluckily I have no ICH9 board, while I can't reproduce it with ICH10 or above. This patch should workaround the first problem in software: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/ata/chipsets/ata-intel.c.diff?r1=1.25;r2=1.26 Try it please and let's see if with some luck it do something about the second problem. With regards to item #1: I don't see anything in the ICH9 errata that indicates a silicon bug if the only device attached to the controller is an ATAPI device and connected to SATA port 0 (presumably), or an odd-numbered port? If this problem exists on other ICHxx and/or ESBxx chips, I sure would hope it'd be documented. I haven't tried confirming it myself, but if need be I can set up a test box with a SATA-based DVD drive hooked up to it + provide remote serial console/etc. if it'd be of any help. I don't think it would be (sounds like you have lots of hardware :-) ), but I'm willing to help in any way I can. Intel probably don't see issue there, as the same behavior can be found even on latest chipsets. But according to my ATA specs understanding and real PATA devices behavior analysis, this behavior is not correct. When ATAPI device connected to the first of two SATA ports, routed to the same legacy-/PATA-emulated ATA channel (master device), soft-reset sequence returns false-positive slave ATAPI device presence. Problem doesn't expose with ATA disk devices, or if some other device really attached to the slave port. Problem looks like it was there always, but before ATA_CAM it was not usually noticed, due to very small IDENTIFY command timeouts in ata(4). If somebody can give better explanation or propose better workaround -- welcome, as I am not very like this solution. With regards to item #2: could this be at all related to OOB (bit 15) somehow being set in PCS (SATA register offset 0x92)? I'm doubting it but I thought I'd ask. My thought process, which is probably wrong (consider it an educational discussion :-) ): The ICH9 specification states that the default value for this register is 0x, and b15=0 means SATA controller will not retry after an OOB failure, while b15=1 causes the controller to indefinitely retry after OOB failure. I imagine system BIOSes and other things can change this default value, but we don't seem to print it anywhere in ata_intel_chipinit() during a verbose boot. Looking at chipsets/ata-intel.c, it looks like we only touch PCS in ata_intel_chipinit() and ata_intel_reset(). In the former, we avoid touching bits 4 through 15, and in the latter we mask out only what we want to adjust (e.g. the SATA port per ch variable). As as I can see, ata_intel.c should not change that bit if it was set for some reason. Theoretically, OOB (Out-of-Band signaling) is the function of the same state machine which sets that PHY changes status flag. But friendly speaking, I have no idea what result can be from setting of this bit. In this legacy/PATA emulation mode there are too many things not documented to be sure in anything. -- Alexander Motin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
8-STABLE won't boot with ZFSv28
Hi all, 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=foo make installkernel KERNCONF=foo make installworld mergemaster which all went smoothly. After reboot, I only got unknown: WARNING - ATAPI_IDENTITFY requeued due to channel reset LBA=0 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 = 00 fault virtual address = 0x8 fault code = supervisor read data, page not present instruction pointer= 0x20:0x80252301 stack poiner = 0x28:0xff8a7ac0 frame pointer= 0x28:0xff8a7b00 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 0 (thread taskq)trap number = 12 panic: page fault cpuid = 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=0 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? Best regards, Holger -- 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.k...@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 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 8-STABLE won't boot with ZFSv28
Hello, Holger Kipp! On Wed, Jun 01, 2011 at 08:23:19AM + holger.k...@alogis.com wrote about 8-STABLE won't boot with ZFSv28: Hi all, 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=foo make installkernel KERNCONF=foo make installworld mergemaster Looks like you forgot to update your bootcode. gpart bootcode which all went smoothly. After reboot, I only got unknown: WARNING - ATAPI_IDENTITFY requeued due to channel reset LBA=0 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 = 00 fault virtual address = 0x8 fault code = supervisor read data, page not present instruction pointer= 0x20:0x80252301 stack poiner = 0x28:0xff8a7ac0 frame pointer= 0x28:0xff8a7b00 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 0 (thread taskq)trap number = 12 panic: page fault cpuid = 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=0 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? -- Lystopad Olexandr ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 8-STABLE won't boot with ZFSv28
On Wed, Jun 01, 2011 at 08:23:19AM +, 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=foo make installkernel KERNCONF=foo make installworld mergemaster which all went smoothly. After reboot, I only got unknown: WARNING - ATAPI_IDENTITFY requeued due to channel reset LBA=0 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 = 00 fault virtual address = 0x8 fault code = supervisor read data, page not present instruction pointer= 0x20:0x80252301 stack poiner = 0x28:0xff8a7ac0 frame pointer= 0x28:0xff8a7b00 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 0 (thread taskq)trap number = 12 panic: page fault cpuid = 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=0 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.html#62804 Holger, can you please provide the following two things? 1) Output from pciconf -lvcb. 2) Full output from a verbose boot (option 5 at the loader prompt). 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). 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=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. CC'ing mav@ here. Alexander, Holger's report looks exactly like Michael's report. Possibly we should consider reverting the April 17th commit until we can figure out what's going on here. -- | Jeremy Chadwick j...@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
RE: 8-STABLE won't boot with ZFSv28
Jeremy Chadwick [free...@jdc.parodius.com] wrote on 01 June 2011 10:54 On Wed, Jun 01, 2011 at 08:23:19AM +, 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=foo make installkernel KERNCONF=foo make installworld mergemaster which all went smoothly. After reboot, I only got unknown: WARNING - ATAPI_IDENTITFY requeued due to channel reset LBA=0 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 = 00 fault virtual address = 0x8 fault code = supervisor read data, page not present instruction pointer= 0x20:0x80252301 stack poiner = 0x28:0xff8a7ac0 frame pointer= 0x28:0xff8a7b00 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 0 (thread taskq)trap number = 12 panic: page fault cpuid = 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=0 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.html#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=0x06 card=0xd28015d9 chip=0x29f08086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' device = '3200 Chipset (Bearlake) Processor to I/O Controller' class = bridge subclass = HOST-PCI cap 09[e0] = vendor (length 12) Intel cap 9 version 1 pcib1@pci0:0:1:0: class=0x060400 card=0xd28015d9 chip=0x29f18086 rev=0x01 hdr=0x01 vendor = 'Intel Corporation' device = '3200 Chipset (Bearlake) PCIe Root Port 1' class = bridge subclass = PCI-PCI cap 0d[88] = PCI Bridge card=0xd28015d9 cap 01[80] = powerspec 3 supports D0 D3 current D0 cap 05[90] = MSI supports 1 message cap 10[a0] = PCI-Express 2 root port max data 128(128) link x8(x16) ecap 0002[100] = VC 1 max VC0 ecap 0005[140] = unknown 1 uhci0@pci0:0:26:0: class=0x0c0300 card=0xd28015d9 chip=0x29378086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82801IB/IR/IH (ICH9 Family) USB Universal Host Controller' class = serial bus subclass = USB bar [20] = type I/O Port, range 32, base 0x1820, size 32, enabled cap 13[50] = PCI Advanced Features: FLR TP uhci1@pci0:0:26:1: class=0x0c0300 card=0xd28015d9 chip=0x29388086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82801IB/IR/IH (ICH9 Family) USB Universal Host Controller' class = serial bus subclass = USB bar [20] = type I/O Port, range 32, base 0x1840, size 32, enabled cap 13[50] = PCI Advanced Features: FLR TP uhci2@pci0:0:26:2: class=0x0c0300 card=0xd28015d9 chip=0x29398086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82801IB/IR/IH (ICH9 Family) USB Universal Host Controller' class = serial bus subclass = USB bar [20] = type I/O Port, range 32, base 0x1860, size 32, enabled cap 13[50] = PCI Advanced Features: FLR TP ehci0@pci0:0:26:7: class=0x0c0320 card=0xd28015d9 chip=0x293c8086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82801IB/IR/IH (ICH9 Family) USB2 Enhanced Host Controller' class = serial bus subclass = USB bar [10] = type Memory, range 32, base 0xd9001000, size 1024, enabled cap 01[50] = powerspec 2 supports D0 D3 current D0 cap 0a[58] = EHCI Debug Port at offset 0xa0 in map 0x14 cap 13[98] = PCI Advanced Features: FLR TP pcib4@pci0:0:28:0: class=0x060400 card=0xd28015d9 chip=0x29408086 rev=0x02 hdr=0x01 vendor
Re: 8-STABLE won't boot with ZFSv28
2011/6/1 Lystopad Olexandr l...@laa.zp.ua: Hello, Holger Kipp! On Wed, Jun 01, 2011 at 08:23:19AM + holger.k...@alogis.com wrote about 8-STABLE won't boot with ZFSv28: Hi all, 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=foo make installkernel KERNCONF=foo make installworld mergemaster Looks like you forgot to update your bootcode. gpart bootcode Only necessary if the pool is upgraded, which was not the case. which all went smoothly. After reboot, I only got unknown: WARNING - ATAPI_IDENTITFY requeued due to channel reset LBA=0 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 = 00 fault virtual address = 0x8 fault code = supervisor read data, page not present instruction pointer = 0x20:0x80252301 stack poiner = 0x28:0xff8a7ac0 frame pointer = 0x28:0xff8a7b00 code segment = base 0x0, limit 0xf, type 0x1b = DPL 0, pres1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 0 (thread taskq)trap number = 12 panic: page fault cpuid = 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=0 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. Don't upgrade the pool for now, you have problems to solve first. Then, you'll be able to upgrade the pool, and don't forget to also update the zfs boot code before rebooting (see UPDATING). Don't forget you won't be able to import your (upgraded) v28 pool with a 8.2-RELEASE if you have problems with 8-STABLE ! Also, you can use mfsbsd if you shoot yourself in the foot. Any suggestions as to how to proceed? -- Lystopad Olexandr ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org -- Olivier Smedts _ ASCII ribbon campaign ( ) e-mail: oliv...@gid0.org - against HTML email vCards X www: http://www.gid0.org - against proprietary attachments / \ Il y a seulement 10 sortes de gens dans le monde : ceux qui comprennent le binaire, et ceux qui ne le comprennent pas. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 8-STABLE won't boot with ZFSv28
On Wed, Jun 01, 2011 at 09:26:05AM +, Holger Kipp wrote: Jeremy Chadwick [free...@jdc.parodius.com] wrote on 01 June 2011 10:54 On Wed, Jun 01, 2011 at 08:23:19AM +, 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=foo make installkernel KERNCONF=foo make installworld mergemaster which all went smoothly. After reboot, I only got unknown: WARNING - ATAPI_IDENTITFY requeued due to channel reset LBA=0 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 = 00 fault virtual address = 0x8 fault code = supervisor read data, page not present instruction pointer= 0x20:0x80252301 stack poiner = 0x28:0xff8a7ac0 frame pointer= 0x28:0xff8a7b00 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 0 (thread taskq)trap number = 12 panic: page fault cpuid = 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=0 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.html#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=0x06 card=0xd28015d9 chip=0x29f08086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' device = '3200 Chipset (Bearlake) Processor to I/O Controller' class = bridge subclass = HOST-PCI cap 09[e0] = vendor (length 12) Intel cap 9 version 1 pcib1@pci0:0:1:0: class=0x060400 card=0xd28015d9 chip=0x29f18086 rev=0x01 hdr=0x01 vendor = 'Intel Corporation' device = '3200 Chipset (Bearlake) PCIe Root Port 1' class = bridge subclass = PCI-PCI cap 0d[88] = PCI Bridge card=0xd28015d9 cap 01[80] = powerspec 3 supports D0 D3 current D0 cap 05[90] = MSI supports 1 message cap 10[a0] = PCI-Express 2 root port max data 128(128) link x8(x16) ecap 0002[100] = VC 1 max VC0 ecap 0005[140] = unknown 1 uhci0@pci0:0:26:0: class=0x0c0300 card=0xd28015d9 chip=0x29378086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82801IB/IR/IH (ICH9 Family) USB Universal Host Controller' class = serial bus subclass = USB bar [20] = type I/O Port, range 32, base 0x1820, size 32, enabled cap 13[50] = PCI Advanced Features: FLR TP uhci1@pci0:0:26:1: class=0x0c0300 card=0xd28015d9 chip=0x29388086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82801IB/IR/IH (ICH9 Family) USB Universal Host Controller' class = serial bus subclass = USB bar [20] = type I/O Port, range 32, base 0x1840, size 32, enabled cap 13[50] = PCI Advanced Features: FLR TP uhci2@pci0:0:26:2: class=0x0c0300 card=0xd28015d9 chip=0x29398086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82801IB/IR/IH (ICH9 Family) USB Universal Host Controller' class = serial bus subclass = USB bar [20] = type I/O Port, range 32, base 0x1860, size 32, enabled cap 13[50] = PCI Advanced Features: FLR TP ehci0@pci0:0:26:7: class=0x0c0320 card=0xd28015d9 chip=0x293c8086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82801IB/IR/IH (ICH9 Family) USB2 Enhanced Host Controller' class = serial bus subclass = USB bar [10] = type Memory, range 32, base 0xd9001000, size 1024, enabled cap 01[50] = powerspec 2 supports D0 D3 current D0 cap 0a[58] = EHCI
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 SATA: - 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 [free...@jdc.parodius.com] Sent: 01 June 2011 11:56 To: Holger Kipp Cc: sta...@freebsd.org; m...@freebsd.org Subject: Re: 8-STABLE won't boot with ZFSv28 On Wed, Jun 01, 2011 at 09:26:05AM +, Holger Kipp wrote: Jeremy Chadwick [free...@jdc.parodius.com] wrote on 01 June 2011 10:54 On Wed, Jun 01, 2011 at 08:23:19AM +, 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=foo make installkernel KERNCONF=foo make installworld mergemaster which all went smoothly. After reboot, I only got unknown: WARNING - ATAPI_IDENTITFY requeued due to channel reset LBA=0 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 = 00 fault virtual address = 0x8 fault code = supervisor read data, page not present instruction pointer= 0x20:0x80252301 stack poiner = 0x28:0xff8a7ac0 frame pointer= 0x28:0xff8a7b00 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 0 (thread taskq)trap number = 12 panic: page fault cpuid = 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=0 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.html#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=0x06 card=0xd28015d9 chip=0x29f08086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' device = '3200 Chipset (Bearlake) Processor to I/O Controller' class = bridge subclass = HOST-PCI cap 09[e0] = vendor (length 12) Intel cap 9 version 1 pcib1@pci0:0:1:0: class=0x060400 card=0xd28015d9 chip=0x29f18086 rev=0x01 hdr=0x01 vendor = 'Intel Corporation' device = '3200 Chipset (Bearlake) PCIe Root Port 1' class = bridge subclass = PCI-PCI cap 0d[88] = PCI Bridge card=0xd28015d9 cap 01[80] = powerspec 3 supports D0 D3 current D0 cap 05[90] = MSI supports 1 message cap 10[a0] = PCI-Express 2 root port max data 128(128) link x8(x16) ecap 0002[100] = VC 1 max VC0 ecap 0005[140] = unknown 1 uhci0@pci0:0:26:0: class=0x0c0300 card=0xd28015d9 chip=0x29378086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82801IB/IR/IH (ICH9 Family) USB Universal Host Controller' class = serial bus subclass = USB bar [20] = type I/O Port, range 32, base 0x1820, size 32, enabled cap 13[50] = PCI Advanced Features: FLR TP uhci1@pci0:0:26:1: class=0x0c0300 card=0xd28015d9 chip=0x29388086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82801IB/IR/IH (ICH9 Family) USB Universal Host Controller' class = serial bus subclass = USB bar [20] = type I/O Port, range 32, base 0x1840, size 32, enabled cap 13[50] = PCI Advanced
RE: 8-STABLE won't boot with ZFSv28
Dear all, got the same messages over and over again - panic took some time: unknown: WARNING - ATAPI_IDENTIFY requeued due to channel reset LBA=0 ata0: reinit done .. ata0: reiniting channel .. ata0: DISCONNECT requested short delay here ata0: p0: SATA connect time=0ms status=0113 ata0: p1: SATA connect timeout status= ata0: reset tp1 mask=03 ostat0=00 ostat1=00 ata0: stat0=0x00 err=0x01 lsb=0x14 msb=0xeb ata0: stat1=0x00 err=0x01 lsb=0x14 msb=0xeb ata0: reset tp2 stat0=00 stat1=00 devices=0x3 unknown: WARNING - ATAPI_IDENTIFY requeued due to channel reset LBA=0 ata0: reinit done .. ata0: reiniting channel .. ata0: DISCONNECT requested short delay here ata0: p0: SATA connect time=0ms status=0113 ata0: p1: SATA connect timeout status= ata0: reset tp1 mask=03 ostat0=00 ostat1=00 ata0: stat0=0x00 err=0x01 lsb=0x14 msb=0xeb ata0: stat1=0x00 err=0x01 lsb=0x14 msb=0xeb ata0: reset tp2 stat0=00 stat1=00 devices=0x3 unknown: WARNING - ATAPI_IDENTIFY requeued due to channel reset LBA=0 ata0: reinit done .. ata0: reiniting channel .. ata0: DISCONNECT requested short delay here ata0: p0: SATA connect time=0ms status=0113 ata0: p1: SATA connect timeout status= ata0: reset tp1 mask=03 ostat0=00 ostat1=00 ata0: stat0=0x00 err=0x01 lsb=0x14 msb=0xeb ata0: stat1=0x00 err=0x01 lsb=0x14 msb=0xeb ata0: reset tp2 stat0=00 stat1=00 devices=0x3 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 modeAssuming we have a 512kB buffer for such messages, then at about two roundtrips per second, only issuing the 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-sta...@freebsd.org [owner-freebsd-sta...@freebsd.org] on behalf of Holger Kipp [holger.k...@alogis.com] Sent: 01 June 2011 13:36 To: Jeremy Chadwick Cc: sta...@freebsd.org; m...@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 SATA: - 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 [free...@jdc.parodius.com] Sent: 01 June 2011 11:56 To: Holger Kipp Cc: sta...@freebsd.org; m...@freebsd.org Subject: Re: 8-STABLE won't boot with ZFSv28 On Wed, Jun 01, 2011 at 09:26:05AM +, Holger Kipp wrote: Jeremy Chadwick [free...@jdc.parodius.com] wrote on 01 June 2011 10:54 On Wed, Jun 01, 2011 at 08:23:19AM +, 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=foo make installkernel KERNCONF=foo make installworld mergemaster which all went smoothly. After reboot, I only got unknown: WARNING - ATAPI_IDENTITFY requeued due to channel reset LBA=0 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 = 00 fault virtual address = 0x8 fault code = supervisor read data, page not present instruction pointer= 0x20:0x80252301 stack poiner = 0x28:0xff8a7ac0 frame pointer= 0x28:0xff8a7b00 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 0 (thread taskq)trap number = 12 panic: page fault cpuid = 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=0 error about once per second. Have now used a fixit
