Date: Sun, 15 Sep 2013 10:32:37 -0400 From: Paul Mather <pmather@vt.edu> To: Su Kang Yin <paradyse@gmail.com> Cc: Tim Kientzle <tim@kientzle.com>, freebsd-arm <freebsd-arm@freebsd.org>, Ian Lepore <ian@freebsd.org> Subject: Re: FreeBSD 10.0-ALPHA1 r255532 bootup freeze on BBB Message-ID: <E570E3DE-60B7-4245-9C91-682FD0A8F9F8@g.mail.vt.edu> In-Reply-To: <CAHjFwoAT5BO4c0DdOYCAqsdY=f=yS%2B3-M1W%2BOH=wMmEx-FSzLw@mail.gmail.com> References: <CAHjFwoBcLfy%2BU9B=jLMWXGF7dMZfzTSwBak05V7qs-MNZy=h4w@mail.gmail.com> <1379188513.1197.35.camel@revolution.hippie.lan> <0AC11ABC-5C40-4C63-B90D-2E686562BFD2@kientzle.com> <CAHjFwoAT5BO4c0DdOYCAqsdY=f=yS%2B3-M1W%2BOH=wMmEx-FSzLw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sep 15, 2013, at 1:25 AM, Su Kang Yin wrote: > Hi, >=20 > I found that issue. >=20 > It is because I disabled this options: >=20 > #options DDB #Enable the kernel debugger > #options INVARIANTS #Enable calls of extra sanity = checking > #options INVARIANT_SUPPORT #Extra sanity checks of > internal structures, required by INVARIANTS > #options WITNESS #Enable checks to detect > deadlocks and cycles > #options WITNESS_SKIPSPIN #Don't run witness on > spinlocks for speed > #options DIAGNOSTIC >=20 > Without them rootfs does not mount (kernel does not freeze, when I > eject mmc, kernel shows "mmc0: detached") >=20 >=20 > I use default kernel config and it works fine. I can report that this also happened to me on BeagleBone Black with = those debugging options removed. The kernel would boot but would then = stop when trying to mount the root file system. Oddly enough, a kernel of the same revision (r255420) with those = debugging options removed will boot to multi-user on Raspberry Pi. Cheers, Paul. >=20 > Thanks, > Yin >=20 > On 15 September 2013 07:25, Tim Kientzle <tim@kientzle.com> wrote: >>=20 >> On Sep 14, 2013, at 12:55 PM, Ian Lepore <ian@freebsd.org> wrote: >>=20 >>> On Sun, 2013-09-15 at 01:15 +0800, Su Kang Yin wrote: >>>> Log: >>>>=20 >>>> 48.0MHz/4bit/65535-block >>>> uhub0: 1 port with 1 removable, self powered >>>> uhub1: 1 port with 1 removable, self powered >>>>=20 >>>> ^^^^^^^^^^ Stuck here.... and I didn't connect any usb device. >>>>=20 >>>> Any idea? >>>>=20 >>>=20 >>> Two thoughts... make sure you're powering the board with a 5v = adapter, >>> not through a usb connection, >>=20 >> I have lots of 5v supplies around but when I recently tried >> to run one of my BBB from a USB connection, it did hang >> a lot. The BBW worked okay, though. >>=20 >> I suspect we're missing some boot code to detect >> the power source and adjust the CPU clock accordingly. >>=20 >>> and try adding this to your kernel config: >>>=20 >>> option USB_HOST_ALIGN=3D64 >>>=20 >>> If I don't use a separate power supply I get strange usb errors (but = not >>> a hang). If I do use the power supply, I get a data abort. Usb has >>> never worked on my BBW, but I don't need it, so I've never tried = hard to >>> figure out why. >>=20 >> I've just recently started tinkering with USB on my BBB here. >> In particular, I've been able to run a urtwn USB Wifi adapter >> (Specifically: adafru.it/814). >>=20 >> I haven't tried with the BBW, though. >>=20 >> Tim >>=20 >>=20 >> _______________________________________________ >> freebsd-arm@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-arm >> To unsubscribe, send any mail to = "freebsd-arm-unsubscribe@freebsd.org" > _______________________________________________ > freebsd-arm@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" >=20
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E570E3DE-60B7-4245-9C91-682FD0A8F9F8>