Bug 257596 - usbd_cntrl_transfer_setup error on boot from DVD, v13
Summary: usbd_cntrl_transfer_setup error on boot from DVD, v13
Status: New
Alias: None
Product: Base System
Classification: Unclassified
Component: usb (show other bugs)
Version: 13.0-STABLE
Hardware: i386 Any
: --- Affects Only Me
Assignee: freebsd-usb (Nobody)
URL:
Keywords: regression
Depends on:
Blocks:
 
Reported: 2021-08-03 17:40 UTC by judah.levine
Modified: 2021-08-06 17:14 UTC (History)
1 user (show)

See Also:


Attachments
screenshot of error messages as requested (591.02 KB, application/pdf)
2021-08-03 18:46 UTC, judah.levine
no flags Details
boot messages for v12 and same hardware (45.21 KB, text/plain)
2021-08-06 17:12 UTC, judah.levine
no flags Details
Boot messages for v13 same hardware (13.30 KB, text/plain)
2021-08-06 17:14 UTC, judah.levine
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description judah.levine 2021-08-03 17:40:11 UTC
FreeBSD v13 distribution will not boot on Dell 2970. Error message is usbd_ctrl_transfer_setup: could not setup
adding commands to boot options:
set hw.usb.usbhid_enable=1
usbhid_load="YES"
does not help.
System works ok with FreeBSD v12
Comment 1 Hans Petter Selasky freebsd_committer 2021-08-03 17:51:04 UTC
Can you screenshot more of the text printed?
Comment 2 judah.levine 2021-08-03 18:46:16 UTC
Created attachment 226924 [details]
screenshot of error messages as requested

the message repeats many times and then the system crashes.
the jpg file was too large to send.
Comment 3 Hans Petter Selasky freebsd_committer 2021-08-04 07:37:46 UTC
Can you also screenshot the panic?
Comment 4 Hans Petter Selasky freebsd_committer 2021-08-04 07:46:51 UTC
The ENOMEM USB err message might indicate a problem that not all RAM was detected. So it might not be related to USB.
Comment 5 judah.levine 2021-08-04 13:43:14 UTC
The system is completely dead after the screen shot that I sent previously. There is no other output and the keyboard has no effect. I have to cycle the input power.
I went back to FreeBSD V12 on this system and it works fine with no problems.

The internal test for the memory is ok. I don't know if that addresses your comment.
Comment 6 Hans Petter Selasky freebsd_committer 2021-08-04 14:10:15 UTC
Do you have the possibility to connect via a serial console and capture all the boot messages?

There has been very few changes in the USB stack between 12 and 13, so I suspect something else to be the culpit.

--HPS
Comment 7 judah.levine 2021-08-06 17:12:59 UTC
Created attachment 226995 [details]
boot messages for v12 and same hardware
Comment 8 judah.levine 2021-08-06 17:14:36 UTC
Created attachment 226996 [details]
Boot messages for v13 same hardware