Timeout poll on interrupt endpoint for RPI3 with keyboard and mouse

[Emmanuel Vadot]

On Sun, 30 Sep 2018 06:09:30 -0700
bob prohaska <fbsd at www.zefox.net> wrote:

> On Sun, Sep 30, 2018 at 11:12:08AM +0200, Emmanuel Vadot wrote:
> > 
> >  Hi,
> > 
> > On Sat, 29 Sep 2018 11:52:13 -0700
> > bob prohaska <fbsd at www.zefox.net> wrote:
> > 
> > > For the first time in a few months I connected a monitor, Dell keyboard and
> > > mouse to my Pi3, presently running
> > > 12.0-ALPHA7 r338964 GENERIC arm64
> > > which have all worked well since I got the Pi3 around six months ago.
> > > 
> > > With the peripherals connected, the serial console spews
> > > Timeout poll on interrupt endpoint
> > > and does not seem to accept normal inputs, so it isn't
> > > possible to get into the debugger, boot an old kernel
> > > or otherwise try to sort out what's going on.
> > > 
> > > disconnecting the monitor had no effect.
> > > Removing the keyboard/mouse restores normal behavior. 
> > > 
> > > Anybody got a hint what might be wrong? FWIW, this OS/kernel
> > > pair were compiled and installed with neither mouse/keyboard
> > > nor monitor connected. I wouldn't expect that to matter, but...
> > > 
> > > Thanks for reading,
> > > 
> > > bob prohaska
> > 
> >  Are you talking about U-Boot or kernel itself ?
> >  I don't remember if I tested keyboard in u-boot when I updated it to
> > 2018.09 but it definitly works for me in FreeBSD. I'll try again ALPHA7
> > to be sure.
> > 
> 
> The messages appeared in u-boot and continued into loader.
> 
> The system has since been updated to 
> FreeBSD 12.0-ALPHA8 r339018 GENERIC 
> 
> Here is a sample of console output with HDMI monitor, mouse and keyboard
> connected, starting from a power-off condition:
> 
> Please press any key to reboot.
> 
> MMC:   mmc at 7e300000: 1
> Loading Environment from FAT... *** Warning - bad CRC, using default environment
> 
> Failed (-5)
> In:    serial
> Out:   vidconsole
> Err:   vidconsole
> Net:   No ethernet found.
> starting USB...
> USB0:   scanning bus 0 for devices... 9 USB Device(s) found
>        scanning usb for storage devices... 2 Storage Device(s) found
> Hit any key to stop autoboot:  2 Timeout poll on interrupt endpoint
> Timeout poll on interrupt endpoint
>  1 Timeout poll on interrupt endpoint
>  0 
> Timeout poll on interrupt endpoint
> MMC Device 0 not found
> no mmc device at slot 0
> Timeout poll on interrupt endpoint
> switch to partitions #0, OK
> mmc1 is current device
> Timeout poll on interrupt endpoint
> Scanning mmc 1:1...
> Timeout poll on interrupt endpoint
> Timeout poll on interrupt endpoint
> Timeout poll on interrupt endpoint
> Timeout poll on interrupt endpoint
> Timeout poll on interrupt endpoint
> Timeout poll on interrupt endpoint
> Timeout poll on interrupt endpoint
> Timeout poll on interrupt endpoint
> Timeout poll on interrupt endpoint
> Timeout poll on interrupt endpoint
> Timeout poll on interrupt endpoint
> Timeout poll on interrupt endpoint
> Timeout poll on interrupt endpoint
> Found EFI removable media binary efi/boot/bootaa64.efi
> libfdt fdt_check_header(): FDT_ERR_BADMAGIC
> Timeout poll on interrupt endpoint
> Timeout poll on interrupt endpoint
> Scanning disk mmc at 7e300000.blk...
> Scanning disk usb_mass_storage.lun0...
> Scanning disk usb_mass_storage.lun0...
> Found 14 disks
> 473400 bytes read in 51 ms (8.9 MiB/s)
> libfdt fdt_check_header(): FDT_ERR_BADMAGIC
> ## Starting EFI application at 00080000 ...
> Consoles: EFI console  
> FreeBSD/arm64 EFI loader, Revision 1.1
> (Thu Aug  2 21:57:02 UTC 2018 root at releng3.nyi.freebsd.org)
> 
>    Command line arguments: loader.efi
>    EFI version: 2.70
>    EFI Firmware: Das U-Boot (rev 0.00)
>    Console: efi (0)
>    Load Path: /\efi\boot\bootaa64.efi
>    Load Device: /VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b)/SD(1)/SD(0)/HD(1,0x01,0,0x81f,0x18fa8)
> Trying ESP: /VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b)/SD(1)/SD(0)/HD(1,0x01,0,0x81f,0x18fa8)
> Setting currdev to disk0p1:
> Trying: /VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b)/SD(1)/SD(0)/HD(2,0x01,0,0x197c7,0x1d92839)
> Setting currdev to disk0p2:
> Loading /boot/defaults/loader.conf
> /boot/kernel/kernel text=0x8c5f73 data=0x178df8+0x83ddd4 syms=[0x8+0x122928+0x8+0x115b27]
> /boot/entropy size=0x1000
> /boot/kernel/umodem.ko text=0x2160 text=0x13d0 data=0x102c8+0xfd48 syms=[0x8+0xf18+0x8+0xb62]
> 
> Hit [Enter] to boot immediately, or any other key for command prompt.
> 
> 
> Type '?' for a list of commands, 'help' for more detailed help.
> OK ;21;97t
> ;21;97t not found
> OK ~ Timeout poll on interrupt endpoint
> Timeout poll on interrupt endpoint
> Timeout poll on interrupt endpoint
> Timeout poll on interrupt endpoint
> Timeout poll on interrupt endpoint
> 
> ~ not found
> OK Timeout poll on interrupt endpoint
> Timeout poll on interrupt endpoint
> Timeout poll on interrupt endpoint
> Timeout poll on interrupt endpoint
> ~Timeout poll on interrupt endpoint
> Timeout poll on interrupt endpoint
> Timeout poll on interrupt endpoint
> Timeout poll on interrupt endpoint
> Timeout poll on interrupt endpoint
> Timeout poll on interrupt endpoint
> Timeout poll on interrupt endpoint
> Timeout poll on interrupt endpoint
> Timeout poll on interrupt endpoint
> Timeout poll on interrupt endpoint
> Timeout poll on interrupt endpoint
> Timeout poll on interrupt endpoint
> Timeout poll on interrupt endpoint
> Timeout poll on interrupt endpoint
> Timeout poll on interrupt endpoint
> Timeout poll on interrupt endpoint
> Timeout poll on interrupt endpoint
> Timeout poll on interrupt endpoint
> [plug pulled]
> 
> The unprintable characters are my attempts to
> use enter-tilda-control-b to start the debugger,
> which were seemingly ignored. 

 That's because there is no debugger in the loader.

> Not sure what to make of things like
> "warning, bad CRC". Far as I can remember, that's normal and harmless.

 It is, it's because you don't have any u-boot env in the mmc.

> I'm less sure about the "Failed, -5" message; I don't recall seeing
> that before, but neither did I look for it.

 It think it's related to env too.

> Thanks for reading, please let me know if there's anything I can test.
> 
> bob prohaska


-- 
Emmanuel Vadot <manu at bidouilliste.com> <manu at freebsd.org>