On 15 January 2016 at 21:38, Mike Belopuhov <[email protected]> wrote:
> Hi Michael,
>
> Thanks for the report.  If you still have this snapshot installed,
> could you please
> do a "boot -d", "w mp_verbose 1", "continue" and then show us the ioapic dump.
>

I'm laso been told that this might have been caused by something
else.  To rule that out could you also try a newer snapshot (Jan 15).

Thanks.

> Thanks,
> Mike
>
> On 14 January 2016 at 22:37, Michael Lesniewski
> <[email protected]> wrote:
>> Synopsis:       ehci_sync_hc: tsleep, system doesn't boot
>> Category:       kernel
>> Environment:
>>         System      : OpenBSD 5.9
>>         Details     : OpenBSD 5.9-beta (GENERIC.MP) #1825: Tue Jan 12
>> 22:14:04 MST 2016
>>
>> [email protected]:/usr/src/sys/arch/amd64/compile/GENERIC.MP
>>
>>         Architecture: OpenBSD.amd64
>>         Machine     : amd64
>> Description:
>>         Booting the latest snapshots (from the 13th and the 14th) the system
>> does not boot.
>> Last lines shown when booting are:
>> spkr0 at pcppi0
>> ehci_sync_hc: tsleep() = 35
>> ehci_sync_hc: tsleep() = 35
>> ehci_sync_hc: tsleep() = 35
>> ehci_sync_hc: tsleep() = 35
>> ehci_sync_hc: tsleep() = 35
>> ehci_sync_hc: tsleep() = 35
>> ehci_sync_hc: tsleep() = 35
>> ehci_sync_hc: tsleep() = 35
>> uhub2: device problem, disabling port
>> ehci_sync_hc: tsleep() = 35
>> ehci_sync_hc: tsleep() = 35
>> ehci_sync_hc: tsleep() = 35
>> ehci_sync_hc: tsleep() = 35
>> ehci_sync_hc: tsleep() = 35
>> ehci_sync_hc: tsleep() = 35
>> ehci_sync_hc: tsleep() = 35
>> ehci_sync_hc: tsleep() = 35
>> uhub2: device problem, disabling port
>> vscsi0 at root
>> scsibus2 at vscsi0: 256 targets
>> softraid0 at root
>> scsibus3 at softraid0: 256 targets
>>
>> The system then gets stuck, no keyboard input registers and only holding the
>> power button is an option.
>> The kernel image from the 12 (dmesg below) works fine. This happens on both
>> bsd.mp and bsd.sp
>>
>> How-To-Repeat:
>>         Boot latest kernel on this machine
>> Fix:
>>         Unknown
>>

Reply via email to