On 17 January 2016 at 17:53, George Rosamond <geo...@ceetonetechnology.com> wrote: > > > George Rosamond: >> Mike Belopuhov: >>> On 15 January 2016 at 21:54, George Rosamond >>> <geo...@ceetonetechnology.com> wrote: >>>> Mike Belopuhov: >>>>> On 15 January 2016 at 21:43, Mike Belopuhov <m...@belopuhov.com> wrote: >>>>>> On 15 January 2016 at 21:41, George Rosamond >>>>>> <geo...@ceetonetechnology.com> wrote: >>>>>>> Mike Belopuhov: >>>>>>>> Hi, >>>>>>>> >>>>>>>> Thanks for the report. Could you please do a "boot -d", "w mp_verbose >>>>>>>> 1", "continue" >>>>>>>> and then show us the ioapic dump. >>>>>>> >>>>>>> I don't have console, but this is what I have, manually typed: >>>>>>> >>>>>>> ioapic0: int1 0x92 0x0 >>>>>>> " int9 0xa090 0x0 >>>>>>> " int12 0x93 0x0 >>>>>>> " int16 0xb0b0 0x0 >>>>>>> " int17 0xe063 0x0 >>>>>>> " int18 0xb062 0x0 >>>>>>> " int19 0xa061 0x0 >>>>>>> >>>>>>> then back to the ehci_sync_hc's posted below, then: >>>>>>> >>>>>>> stopped at usb_allocmem+0x175: cmpq %rbx,0(%rax) >>>>>>> >>>>>> >>>>>> cool, could you please post ehci, ohci and uhci lines from your >>>>>> dmesg as well? >>>>>> >>>>> >>>>> And I'm been told that this might have been caused by something >>>>> else. To rule that out could you also try a newer snapshot (Jan 15). >>>>> >>>> >>>> Sorry, I should have mentioned that I did update to today's snapshot, >>>> and the problem recurred. >>>> >>>> I can still post dmesg output of ehci, ohci, uhci if you still need. >>>> >>> >>> Please do. >> >> Here is the last /var/run/dmesg.boot. >> >> http://dmesgd.nycbug.org/index.cgi?action=dmesgd&do=view&id=2883 > > Issue seems resolved with snapshot #1846 from early 20160117 >
Sure, a few snaps contained a temporary change that we need to test widely. I'll be bugging you and others to test stuff this week :-) > http://dmesgd.nycbug.org/index.cgi?action=dmesgd&do=view&id=2884 > > Thanks > > g
