Bug 251591 - USB and Bluetooth subsystem causing system reboots
Summary: USB and Bluetooth subsystem causing system reboots
Status: New
Alias: None
Product: Base System
Classification: Unclassified
Component: usb (show other bugs)
Version: 12.1-RELEASE
Hardware: amd64 Any
: --- Affects Some People
Assignee: freebsd-usb (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-12-05 05:05 UTC by Praveen Khurjek
Modified: 2020-12-17 22:03 UTC (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Praveen Khurjek 2020-12-05 05:05:46 UTC
System reboots while in use. 

Will post more information.
Comment 1 Hans Petter Selasky freebsd_committer 2020-12-05 11:27:46 UTC
We need some kind of panic backtrace to investigate this.
Comment 2 Praveen Khurjek 2020-12-07 07:33:43 UTC
its likely caused by hald signalling usb subsystem .

please let me know the next steps.
Comment 3 Hans Petter Selasky freebsd_committer 2020-12-07 07:53:37 UTC
Please provide a screenshot showing panic.

--HPS
Comment 4 Praveen Khurjek 2020-12-07 12:16:49 UTC
(In reply to Hans Petter Selasky from comment #3)

I disabled hald, and the problem does not seem to be.

I am using a wireless usb adapter , as the wlan card on my device is not supported yet, and ethernet is not used at time being.

ugen1.1: <AMD EHCI root HUB> at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA)
ugen0.1: <0x1022 XHCI root HUB> at usbus0, cfg=0 md=HOST spd=SUPER (5.0Gbps) pwr=SAVE (0mA)
ugen1.2: <vendor 0x0438 product 0x7900> at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (100mA)
ugen1.3: <Realtek 802.11n NIC> at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (500mA)
ugen1.5: <vendor 0x04ca product 0x3015> at usbus1, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (100mA)
ugen1.6: <Quanta VGA WebCam> at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (500mA)
ugen1.4: <vendor 0x0461 USB Optical Mouse> at usbus1, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON (98mA)


where would the logs or traces for the subsystem be stored
Comment 5 Hans Petter Selasky freebsd_committer 2020-12-07 12:35:45 UTC
Logs are stored in /var/log/

Try to build a new kernel with INVARIANTS and WITNESS and KDB enabled.

Else the kernel will just reboot automatically.

Also try to reproduce using 12-stable.

--HPS
Comment 6 Praveen Khurjek 2020-12-07 12:52:18 UTC
This is NOT a kernel panic. 

I have not explicitly enabled logging as this was a new install.

I had looked into /var/log before , is there any specific related to the usb subsystem , I was asking.
Comment 7 Praveen Khurjek 2020-12-07 12:57:28 UTC
I will use a stable build and post the findings...

at the moment , hald disabled , there are no reboots.
Comment 8 Praveen Khurjek 2020-12-07 13:00:18 UTC
for backtracing there are no kernel dumps ....
Comment 9 Praveen Khurjek 2020-12-17 22:03:13 UTC
reboots with :

uhub1: at usbus1, port1, addr 1 ( disconnected )
ugen1.2: < vendor 0x0438 product 0x7900 > at usbus 1 ( disconnected )

series of messages ...