Date: Sat, 24 Feb 2018 07:28:56 -0600 From: Adam <amvandemore@gmail.com> To: Andrea Venturoli <ml@netfence.it> Cc: FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: 11.1/amd64 hangs on boot Message-ID: <CA%2BtpaK3zK9HPaRFoyBuVwqNgYNQJDzhEvtn3NB2J6Rz6dEAn%2Bg@mail.gmail.com> In-Reply-To: <854f2a4e-1264-7c7f-60c4-7f65efa290f7@netfence.it> References: <854f2a4e-1264-7c7f-60c4-7f65efa290f7@netfence.it>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Feb 23, 2018 at 8:11 AM, Andrea Venturoli <ml@netfence.it> wrote: > Hello. > > I've had this machine for eons and it went through almost every FreeBSD > version in the last years without a hitch. > > After upgrading to 11.1, however, it will often (not always) hang on boot. > > Some extract from dmesg (I think these are the relevant parts): > > ... >> FreeBSD 11.1-RELEASE-p6 #1 r327994M: Mon Jan 15 09:50:57 CET 2018 >> root@alamar.ventu:/usr/obj/usr/src/sys/ALAMAR amd64 >> FreeBSD clang version 4.0.0 (tags/RELEASE_400/final 297347) (based on >> LLVM 4.0.0) >> ... >> ahci0: <AMD SB7x0/SB8x0/SB9x0 AHCI SATA controller> port >> 0xa000-0xa007,0x9000-0x9003,0x8000-0x8007,0x7000-0x7003,0x6000-0x600f >> mem 0xfe6ffc00-0xfe6fffff irq 22 at device 17.0 on pci0 >> ahci0: AHCI v1.10 with 6 3Gbps ports, Port Multiplier supported >> ahci0: quirks=0x22000<ATI_PMP_BUG,1MSI> >> ahcich0: <AHCI channel> at channel 0 on ahci0 >> ahcich1: <AHCI channel> at channel 1 on ahci0 >> ahcich2: <AHCI channel> at channel 2 on ahci0 >> ahcich3: <AHCI channel> at channel 3 on ahci0 >> ahcich4: <AHCI channel> at channel 4 on ahci0 >> ahcich5: <AHCI channel> at channel 5 on ahci0 >> ohci0: <AMD SB7x0/SB8x0/SB9x0 USB controller> mem 0xfe6fe000-0xfe6fefff >> irq 16 at device 18.0 on pci0 >> usbus0 on ohci0 >> usbus0: 12Mbps Full Speed USB v1.0 >> ohci1: <AMD SB7x0/SB8x0/SB9x0 USB controller> mem 0xfe6fd000-0xfe6fdfff >> irq 16 at device 18.1 on pci0 >> usbus1 on ohci1 >> usbus1: 12Mbps Full Speed USB v1.0 >> ehci0: <AMD SB7x0/SB8x0/SB9x0 USB 2.0 controller> mem >> 0xfe6ff800-0xfe6ff8ff irq 17 at device 18.2 on pci0 >> usbus2: EHCI version 1.0 >> usbus2 on ehci0 >> usbus2: 480Mbps High Speed USB v2.0 >> ohci2: <AMD SB7x0/SB8x0/SB9x0 USB controller> mem 0xfe6fc000-0xfe6fcfff >> irq 18 at device 19.0 on pci0 >> usbus3 on ohci2 >> usbus3: 12Mbps Full Speed USB v1.0 >> ohci3: <AMD SB7x0/SB8x0/SB9x0 USB controller> mem 0xfe6f7000-0xfe6f7fff >> irq 18 at device 19.1 on pci0 >> usbus4 on ohci3 >> usbus4: 12Mbps Full Speed USB v1.0 >> ehci1: <AMD SB7x0/SB8x0/SB9x0 USB 2.0 controller> mem >> 0xfe6ff400-0xfe6ff4ff irq 19 at device 19.2 on pci0 >> usbus5: EHCI version 1.0 >> usbus5 on ehci1 >> usbus5: 480Mbps High Speed USB v2.0 >> atapci0: <ATI IXP700/800 UDMA133 controller> port >> 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xff00-0xff0f at device 20.1 on pci0 >> ata1: <ATA channel> at channel 1 on atapci0 >> ... >> ahd0: <Adaptec 29320 Ultra320 SCSI adapter> port >> 0xe800-0xe8ff,0xe400-0xe4ff mem 0xfebfe000-0xfebfffff irq 20 at device 5.0 >> on pci3 >> aic7902: Ultra320 Wide Channel A, SCSI Id=7, PCI 33 or 66MHz, 512 SCBs >> ahd1: <Adaptec 29320 Ultra320 SCSI adapter> port >> 0xe000-0xe0ff,0xd800-0xd8ff mem 0xfebfc000-0xfebfdfff irq 21 at device 5.1 >> on pci3 >> aic7902: Ultra320 Wide Channel B, SCSI Id=7, PCI 33 or 66MHz, 512 SCBs >> ... >> ugen4.1: <ATI OHCI root HUB> at usbus4 >> ugen1.1: <ATI OHCI root HUB> at usbus1 >> ugen0.1: <ATI OHCI root HUB> at usbus0 >> ugen6.1: <ATI OHCI root HUB> at usbus6 >> uhub0: <ATI OHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus4 >> uhub1: <ATI OHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus1 >> uhub2: <ATI OHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus6 >> uhub3: ugen3.1: <ATI OHCI root HUB> at usbus3 >> <ATI OHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus0 >> uhub4: <ATI OHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus3 >> ugen5.1: <ATI EHCI root HUB> at usbus5 >> ugen2.1: <ATI EHCI root HUB> at usbus2 >> uhub5: <ATI EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus5 >> uhub6: <ATI EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus2 >> uhub2: 2 ports with 2 removable, self powered >> uhub0: 3 ports with 3 removable, self powered >> uhub1: 3 ports with 3 removable, self powered >> uhub3: 3 ports with 3 removable, self powered >> uhub4: 3 ports with 3 removable, self powered >> uhub5: 6 ports with 6 removable, self powered >> uhub6: 6 ports with 6 removable, self powered >> ... >> ugen5.2: <Generic Mass Storage Device> at usbus5 >> umass0 on uhub5 >> umass0: <Generic Mass Storage Device, class 0/0, rev 2.00/1.29, addr 2> >> on usbus5 >> umass0: SCSI over Bulk-Only; quirks = 0x4001 >> umass0:9:0: Attached to scbus9 >> ... >> da1 at ahd1 bus 0 scbus8 target 0 lun 0 >> da1: <HITACHI HUS103014FL3600 SA1B> Fixed Direct Access SCSI-3 device >> da1: Serial Number V5X9S3AA0051P65D0441 >> da1: 320.000MB/s transfers (160.000MHz DT, offset 80, 16bit) >> da1: Command Queueing enabled >> da1: 140205MB (287140277 512 byte sectors) >> da0 at ahd0 bus 0 scbus7 target 4 lun 0 >> da0: <IOMEGA ZIP 100 E.08> Removable Direct Access SCSI-2 device >> da0: 3.300MB/s transfers >> da0: Attempt to query device size failed: NOT READY, Medium not present >> da2 at ahd1 bus 0 scbus8 target 2 lun 0 >> da2: <HITACHI HUS103014FL3600 SA1B> Fixed Direct Access SCSI-3 device >> da2: Serial Number V5XABRAA0051P65L0026 >> da2: 320.000MB/s transfers (160.000MHz DT, offset 80, 16bit) >> da2: Command Queueing enabled >> da2: 140205MB (287140277 512 byte sectors) >> cd0 at ahcich2 bus 0 scbus2 target 0 lun 0 >> cd0: <HL-DT-ST BD-RE BH16NS40 1.03> Removable CD-ROM SCSI device >> cd0: Serial Number K9HE8TD3540 >> cd0: 150.000MB/s transfers (SATA 1.x, UDMA5, ATAPI 12bytes, PIO 8192bytes) >> cd0: Attempt to query device size failed: NOT READY, Medium not present - >> tray closed >> cd1 at ata1 bus 0 scbus6 target 0 lun 0 >> cd1: <BENQ DVD DC DW1670 103> Removable CD-ROM SCSI device >> cd1: 66.700MB/s transfers (UDMA4, ATAPI 12bytes, PIO 65534bytes) >> cd1: Attempt to query device size failed: NOT READY, Medium not present >> da3 at umass-sim0 bus 0 scbus9 target 0 lun 0 >> da3: <Generic USB SD Reader 1.00> Removable Direct Access SCSI device >> da3: Serial Number 058F312D81B >> da3: 40.000MB/s transfers >> da3: Attempt to query device size failed: NOT READY, Medium not present >> da3: quirks=0x2<NO_6_BYTE> >> Trying to mount root from ufs:/dev/mirror/gm1a [rw]... >> da4 at umass-sim0 bus 0 scbus9 target 0 lun 1 >> da4: <Generic USB CF Reader 1.01> Removable Direct Access SCSI device >> da4: Serial Number 058F312D81B >> da4: 40.000MB/s transfers >> da4: Attempt to query device size failed: NOT READY, Medium not present >> da4: quirks=0x2<NO_6_BYTE> >> da5 at umass-sim0 bus 0 scbus9 target 0 lun 2 >> da5: <Generic USB SM Reader 1.02> Removable Direct Access SCSI device >> da5: Serial Number 058F312D81B >> da5: 40.000MB/s transfers >> da5: Attempt to query device size failed: NOT READY, Medium not present >> da5: quirks=0x2<NO_6_BYTE> >> da6 at umass-sim0 bus 0 scbus9 target 0 lun 3 >> da6: <Generic USB MS Reader 1.03> Removable Direct Access SCSI device >> da6: Serial Number 058F312D81B >> da6: 40.000MB/s transfers >> da6: Attempt to query device size failed: NOT READY, Medium not present >> da6: quirks=0x2<NO_6_BYTE> >> > > The last part is the most relevant: starting from "da1:" onwards, the > order of appearance of daX and cdX is not always the same. > Often, after a few of daX and/or cdX are output, the machine hangs, the > SCSI controller light staying on: sometimes it will spontaneusly reboot > after several seconds, sometimes I'll have to press the reset button. > > There's no rules to how many times I have to try booting every morning: > some days it starts right the first time, some days I have to reboot > several times until it gets it right and goes ahead. > > While it might be an hardware problem (being the box quite old), the fact > that it started doing this after a 10.3->11.1 upgrade is suspicious. > Is there a known race-condition/LOR/whatever? Is there a way to get better > info (e.g. some option to put in the kernel config or in /boot/loader.conf)? > Should I enable DDB, INVARIANTS, WITNESS & co.? I'd like to avoid breaking > performance, but I'll do if it's the only way. > You could do a verbose boot. You can also use the switch to prevent reboot on panic. Is there anything in /var/log/messages? -- Adam
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA%2BtpaK3zK9HPaRFoyBuVwqNgYNQJDzhEvtn3NB2J6Rz6dEAn%2Bg>