Hello Martin,
same crash happens here. A USB-monitor-hub is connected to a USB3 port
(though USB3 disabled from BIOS) in a computer. Same setup than
before, dongles are in the monitor hub. I can try if this is
reproducible with a USB2 port. Will let you know tomorrow.
Here's trace with ehcidebug=4 and usbdebug=6 enabled:
ukbd0 detached
uhidev0 detached
uvm_fault(0xffffffff81d44f20, 0x24, 0, 1) -> e
kernel: page fault trap, code=0
Stopped at strlcpy+0x16: movzbl 0(%rcx),%eax
ddb{1}> strlcpy() at strlcpy+0x16
config_detach() at config_detach+0x97
config_detach() at config_detach+0x143
usb_disconnect_port() at usb_disconnect_port+0x6a
uhub_detach() at uhub_detach+0x64
config_detach() at config_detach+0x143
usb_disconnect_port() at usb_disconnect_port+0x6a
uhub_explore() at uhub_explore+0x12b
uhub_explore() at uhub_explore+0x97
usb_explore() at usb_explore+0xcf
usb_task_thread() at usb_task_thread+0xb2
end trace frame: 0x0, count: -11
--
Regards,
Ville Valkonen
On 22 March 2014 19:31, Martin Pieuchot <mpieuc...@nolizard.org> wrote:
> On 22/03/14(Sat) 02:30, Shawn K. Quinn wrote:
>> On Fri, Mar 21, 2014, at 07:34 PM, Tristan PILAT wrote:
>> > Hello,
>> >
>> > I noticed a crash with the March 20th amd64 snapshot. When I
>> > unplug my USB wireless mouse receiver, i get this;
>> >
>> > wskbd1: disconnecting from wsdisplay0
>> > wskbd1 detached
>> > ukbd0 detached
>> > uhidev0 detached
>> > uvm_faut(0xffffffff81dc6f00, 0x24, 0, 1) -> e
>> > kernel: page faut trap, code=0
>> > Stopper at strlcpy+0x16 movzbl 0(%rcx), %eax
>> > ddb1{1}>
>> >
>> > I own a thinkpad x230 and only the right side USB port is working
>> > after the upgrade, the two left side USB port are not working
>> > anymore. Find attached my dmesg.
>>
>> A similar crash happened with the March 19th snapshot here as well when
>> switching computers on my USB KVM switch. My backtrace also indicates a
>> kernel trap in strlcpy. I was about to upgrade to the March 20th
>> snapshot to see if it was still there.
>
> It is likely to be there since it's the first time I here about such
> regression and sadly there's not enough information in your bug report
> to do anything :(
>
> Could you provide a dmesg with the USB keyboard (or whatever device
> causing the problem) plugged in and a trace when the panic occurs.
>
> See http://www.openbsd.org/report.html for more information.
>
> Martin
