From owner-freebsd-current@FreeBSD.ORG Mon Sep 29 00:15:28 2014 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6F4BE8FD for ; Mon, 29 Sep 2014 00:15:28 +0000 (UTC) Received: from srv56-45.cdn.bestreaming.com (srv56-46.cdn.bestreaming.com [204.140.16.4]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 228E8B66 for ; Mon, 29 Sep 2014 00:15:27 +0000 (UTC) Received: from mail.yourbox.net (localhost [127.0.0.1]) by srv56-45.cdn.bestreaming.com (8.14.5/8.14.5) with ESMTP id s8T0FUsv055396; Mon, 29 Sep 2014 00:15:30 GMT (envelope-from fbl@aoek.com) From: "=?UTF-8?Q?Jos=C3=A9_P=C3=A9rez_Arauz?=o" To: "Mike." , freebsd-current@freebsd.org Subject: Re: Looping during boot-up process in FreeBSD-11 current Date: Mon, 29 Sep 2014 02:15:25 +0200 Message-Id: <20140928234329.M15139@beckpeccoz.com> In-Reply-To: <201409281153050191.00909A0F@smtp.24cl.home> References: <201409281152140359.008FD377@smtp.24cl.home> <201409281153050191.00909A0F@smtp.24cl.home> X-Mailer: OpenWebMail 2.53 X-OriginatingIP: 213.37.0.220 (ame) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Sep 2014 00:15:28 -0000 Hi Mike, it looks like we are hitting the same problem. If we find a third person with the same issue we can fund a club. :) Interesting to note: 1) we both run FBSD on small netbooks which usually get equipped with crappy ^D^D^D^D^D^D^D cheap hardware. 2) yours seems to be an Intel-only box, mine is an AMD-only, so the problem is not there (I mean, it's not the graphic chip). 3) we both have an Atheros wifi, whose driver has been updated recently, maybe this is the issue? As of now I suspect the problem is not related to AHCI because if you remove it from the kernel you still end up in an enless loop in some other driver. Actually the latest device_attach loops forever. You might still get some output from previous device probes complaining, notably USB, especially if you plug something in, or AHCI --as we both report--. I would like to debug the running kernel from another machine, altought the suggestions I got so far (see thread about kernel debugging in this same mailing list) are not encouraging. I will keep you posted, in the meantime you can try and boot your pc from 271146, it works for me. BR, On Sun, 28 Sep 2014 11:53:05 -0400, Mike. wrote > I'm starting to look at FreeBSD 11-current to see what's coming soon. > I have an older notebook that I use for test environments for > purposes such as this. Unfortunately, the notebook won't boot up > from the install CD, there's a loop it cannot seem to get out of. > > Details are: > > - The install CD was made from this image: > FreeBSD-11.0-CURRENT-i386-20140918-r271779-disc1 > > - The dmesg for the notebook is at the end of this message. The > dmesg was captured with FreeBSD 10.0. In the dmesg, you can see the > following lines: > > (aprobe0:ata1:0:1:0): ATAPI_IDENTIFY. ACB: a1 00 00 00 00 40 00 00 00 > 00 00 00 > (aprobe0:ata1:0:1:0): CAM status: Command timeout > (aprobe0:ata1:0:1:0): Error 5, Retry was blocked > run_interrupt_driven_hooks: still waiting after 60 seconds for > xpt_config > (aprobe0:ata1:0:1:0): ATAPI_IDENTIFY. ACB: a1 00 00 00 00 40 00 00 00 > 00 00 00 > (aprobe0:ata1:0:1:0): CAM status: Command timeout > (aprobe0:ata1:0:1:0): Error 5, Retry was blocked > > which, while slowing down the boot process drastically, still allowed > the boot process to run to successful completion. > > - When I try to boot using the FreeBSD 11-current install CD, that > loop seems to go on ad infinitum, or at least for the 5 minutes until > I gave up. I cannot post a dmesg from that boot-up because I never > got to a prompt. However, I did take a couple of pictures of the > offending screens. They are here: > http://archive.mgm51.com/cache/fbsd-11-current-01.jpg > http://archive.mgm51.com/cache/fbsd-11-current-02.jpg > The first image shows the start of the looping, and the second shows > the continuation. > > While this notebook is used only for testing, it is important to me > in that aspect. How can I get around this looping issue? > > Please let me know if there's any additional info you need. > > Thanks. > > And now, the dmesg... > > Copyright (c) 1992-2014 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, > 1994 > The Regents of the University of California. All rights reserved. > FreeBSD is a registered trademark of The FreeBSD Foundation. > FreeBSD 10.0-RELEASE-p8 #1 r271323: Wed Sep 10 20:25:45 EDT 2014 > root@a31pf.245l.home:/usr/obj/usr/src/sys/GENERIC i386 > FreeBSD clang version 3.3 (tags/RELEASE_33/final 183502) 20130610 > CPU: Intel(R) Pentium(R) 4 Mobile CPU 1.70GHz (1698.60-MHz 686-class > CPU) > Origin = "GenuineIntel" Id = 0xf24 Family = 0xf Model = 0x2 > Stepping = 4 > Features=0x3febf9ff PGE, MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT, > TM> real memory = 1073741824 (1024 MB) avail memory = 1029230592 > (981 MB) kbd1 at kbdmux0 random: initialized > acpi0: on motherboard acpi_ec0: GPE 0x1c, ECDT> port 0x62,0x66 on acpi0 acpi0: Power Button (fixed) > acpi0: reservation of 0, a0000 (3) failed acpi0: reservation of > 100000, 3ff00000 (3) failed cpu0: on acpi0 attimer0: timer> port 0x40-0x43 irq 0 on acpi0 Timecounter "i8254" frequency > 1193182 Hz quality 0 Event timer "i8254" frequency 1193182 Hz > quality 100 atrtc0: port 0x70-0x71 irq 8 on > acpi0 Event timer "RTC" frequency 32768 Hz quality 0 Timecounter > "ACPI-safe" frequency 3579545 Hz quality 850 acpi_timer0: <24-bit > timer at 3.579545MHz> port 0x1008-0x100b on acpi0 acpi_lid0: > on acpi0 acpi_button0: on > acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: > on pcib0 agp0: on hostb0 > pcib1: at device 1.0 on pci0 > pci1: on pcib1 > vgapci0: port 0x3000-0x30ff mem > 0xe8000000-0xefffffff,0xd0100000-0xd010ffff irq 11 at device 0.0 on > pci1 > vgapci0: Boot video device > uhci0: port > 0x1800-0x181f irq 11 at device 29.0 on pci0 > usbus0 on uhci0 > uhci1: port > 0x1820-0x183f irq 11 at device 29.1 on pci0 > usbus1 on uhci1 > uhci2: port > 0x1840-0x185f irq 11 at device 29.2 on pci0 > usbus2 on uhci2 > pcib2: at device 30.0 on pci0 > pci2: on pcib2 > cbb0: mem 0x50000000-0x50000fff irq 11 > at device 0.0 on pci2 > cardbus0: on cbb0 > pccard0: <16-bit PCCard bus> on cbb0 > cbb1: mem 0x50100000-0x50100fff irq 11 > at device 0.1 on pci2 > cardbus1: on cbb1 > pccard1: <16-bit PCCard bus> on cbb1 > pci2: at device 0.2 (no driver attached) > fxp0: port 0x8000-0x803f > mem 0xd0200000-0xd0200fff irq 11 at device 8.0 on pci2 > miibus0: on fxp0 > inphy0: PHY 1 on miibus0 > inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto, > auto-flow > fxp0: Ethernet address: 00:0e:9b:2c:d3:f6 > isab0: at device 31.0 on pci0 > isa0: on isab0 > atapci0: port > 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x1860-0x186f at device 31.1 on > pci0 > ata0: at channel 0 on atapci0 > ata1: at channel 1 on atapci0 > pci0: at device 31.3 (no driver attached) > pcm0: port 0x1c00-0x1cff,0x18c0-0x18ff irq 11 > at device 31.5 on pci0 > pcm0: > pci0: at device 31.6 (no driver > attached) > acpi_tz0: on acpi0 > atkbdc0: port 0x60,0x64 irq 1 on acpi0 > atkbd0: irq 1 on atkbdc0 > kbd0 at atkbd0 > atkbd0: [GIANT-LOCKED] > psm0: irq 12 on atkbdc0 > psm0: [GIANT-LOCKED] > psm0: model Generic PS/2 mouse, device ID 0 > uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on > acpi0 > battery0: on acpi0 > acpi_acad0: on acpi0 > pmtimer0 on isa0 > orm0: at iomem > 0xc0000-0xcffff,0xd0000-0xd0fff,0xd1000-0xd1fff,0xdc000-0xdffff, > 0xe000 0-0xeffff pnpid ORM0000 on isa0 sc0: at > flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> > vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on > isa0 ppc0: parallel port not found. acpi_perf0: Control> on cpu0 p4tcc0: on cpu0 > Timecounters tick every 1.000 msec random: unblocking device. > usbus0: 12Mbps Full Speed USB v1.0 usbus1: 12Mbps Full Speed USB > v1.0 usbus2: 12Mbps Full Speed USB v1.0 ugen2.1: at usbus2 > uhub0: on usbus2 > ugen1.1: at usbus1 > uhub1: on > usbus1 > ugen0.1: at usbus0 > uhub2: on > usbus0 > uhub0: 2 ports with 2 removable, self powered > uhub1: 2 ports with 2 removable, self powered > uhub2: 2 ports with 2 removable, self powered > ath0: irq 11 at device 0.0 on cardbus1 > ath0: AR5212 mac 5.6 RF5112 phy 4.1 > ath0: 2GHz radio: 0x0000; 5GHz radio: 0x0036 > (aprobe0:ata1:0:1:0): ATAPI_IDENTIFY. ACB: a1 00 00 00 00 40 00 00 00 > 00 00 00 > (aprobe0:ata1:0:1:0): CAM status: Command timeout > (aprobe0:ata1:0:1:0): Error 5, Retry was blocked > run_interrupt_driven_hooks: still waiting after 60 seconds for > xpt_config > (aprobe0:ata1:0:1:0): ATAPI_IDENTIFY. ACB: a1 00 00 00 00 40 00 00 00 > 00 00 00 > (aprobe0:ata1:0:1:0): CAM status: Command timeout > (aprobe0:ata1:0:1:0): Error 5, Retry was blocked > ada0 at ata0 bus 0 scbus0 target 0 lun 0 > ada0: ATA-6 device > ada0: Serial Number MPC412Y4G6J1AE > ada0: 100.000MB/s transfers (UDMA5, PIO 8192bytes) > ada0: 76319MB (156301488 512 byte sectors: 16H 63S/T 16383C) > ada0: Previously was known as ad0 > cd0 at ata1 bus 0 scbus1 target 0 lun 0 > cd0: Removable CD-ROM SCSI-0 device > cd0: 33.300MB/s transfers (UDMA2, ATAPI 12bytes, PIO 65534bytes) > cd0: Attempt to query device size failed: NOT READY, Medium not > present - tray closed > Trying to mount root from ufs:/dev/ada0p2 [rw]... > wlan0: Ethernet address: 00:04:e2:b6:d4:d6 > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" -- José Pérez Arauzo