Date: Sat, 26 Mar 2016 15:48:09 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-arm@FreeBSD.org Subject: [Bug 208308] Adding USB flash drive to fstab kills ue0 on Raspberry Pi 2 Message-ID: <bug-208308-7@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D208308 Bug ID: 208308 Summary: Adding USB flash drive to fstab kills ue0 on Raspberry Pi 2 Product: Base System Version: 11.0-CURRENT Hardware: arm OS: Any Status: New Severity: Affects Only Me Priority: --- Component: arm Assignee: freebsd-arm@FreeBSD.org Reporter: dhorton668@hotmail.com Created attachment 168654 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D168654&action= =3Dedit dmesg output from a successful boot noting differences from hung boot. I am using FreeBSD-11.0-CURRENT-arm-armv6-RPI2-20160308-r296485.img and experiencing a problem with USB flash drives and the built-in RPi Ethernet.= In summary, as soon as I add my USB flash drive to /etc/fstab, the system will never complete the boot process and ue0 never change the link state. Once = this happens, disconnecting the flash drive from the RPi and rebooting does not help. Only if the flash drive is never added to /etc/fstab, will the syst= em boot normally.=20=20 I don't recall experiencing this problem when using FreeBSD-11.0-CURRENT-arm-armv6-RPI2-20160127-r294912.img and wonder if the = new problem may have been introduced by changes made for "Bug 199446 - arm Raspberry Pi panic without ethernet connected on boot" Here is how to reproduce it: 1) Install FreeBSD-11.0-CURRENT-arm-armv6-RPI2-20160308-r296485.img 2) Insert a USB flash drive 3) Create a UFS filesystem on da0p1 4) Add /dev/da0p1 to /etc/fstab 5) Restart the Raspberry Pi Troubleshooting steps I've taken: Erased (dd if=3D/dev/zero of=3D/dev/da0) the flash drive and set up partiti= on again) Used different brand of flash drive. Added the option 'noauto' to fstab. Used another, known good RPi2. Used another, known good power supply. Used another, known good SD card. None of the above makes a difference and still results in the hung boot. Additional troubleshooting: I swapped components (flash drive, power supply, SD card and RPi itself) wi= th a Linux-based media center. I cannot reproduce the problem on the media cent= er. Workaround: Do not add flash drive to fstab, but mount manually after booting. I am attaching the dmesg output from a successful boot when the flash drive= is not in fstab. Unfortunately I cannot include dmesg output from the hung bo= ot, but I do notice that the 'ue0: link state changed to DOWN' and 'ue0: link s= tate changed to UP' lines never appear on the screen. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-208308-7>