https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271012
Graham Perrin changed:
What|Removed |Added
Status|New |Open
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270860
Graham Perrin changed:
What|Removed |Added
Assignee|b...@freebsd.org|grahamper...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270860
Graham Perrin changed:
What|Removed |Added
Version|unspecified |13.2-RELEASE
Assignee|bu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270805
--- Comment #23 from Mark Millard ---
(In reply to Mark Millard from comment #20)
I've submitted:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271012
against main's kernel for the failure context that
I ran into (since it does not m
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271012
Bug ID: 271012
Summary: FreeBSD kernel does not detect USB3.2 storage media on
Windows Dev Kit 2023 USB-C ports (for example?)
Product: Base System
Version: CURRENT
H
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270805
--- Comment #22 from Robert Clausecker ---
(In reply to Mark Millard from comment #21)
Unfortunately the device is colocated now and hard for me to access. It's also
busy 24/7 building ports. I'll see if I can find an opportunity to perf
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270805
--- Comment #21 from Mark Millard ---
(In reply to Robert Clausecker from comment #19)
Note:
If you get ahold of a main [so: 14] loader.efi copy that
has the 2 required commits, you could try substituting
that loader.efi content into your
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270805
--- Comment #20 from Mark Millard ---
(In reply to Robert Clausecker from comment #0)
Ultimately, using main [so: 14], I've not been able to
reproduce any "after displaying the beastie menu" crashes
based on USB storage having been connec
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271010
Bug ID: 271010
Summary: network traffic to vnet Jail fails one way
Product: Base System
Version: 13.2-RELEASE
Hardware: Any
OS: Any
Status: New
Seve
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267631
Graham Perrin changed:
What|Removed |Added
Assignee|b...@freebsd.org|f...@freebsd.org
C
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268316
Graham Perrin changed:
What|Removed |Added
Assignee|b...@freebsd.org|wirel...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270805
--- Comment #19 from Robert Clausecker ---
(In reply to Mark Millard from comment #18)
I tried various boot orders and none of them changed the result. I believe
that once the boot loader is successfully load by UEFI, the boot order cease
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270805
--- Comment #18 from Mark Millard ---
(In reply to Mark Millard from comment #17)
I set up the USB-C connection context again and am looking on
screen at the scroll back for the failure:
No "umass*" ever shows up for my failing context (U
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270805
--- Comment #17 from Mark Millard ---
(In reply to Mark Millard from comment #16)
FYI:
The 2 "backtraces" are presented in forward-time order, so
backtracing is reading each bottom-to-top.
--
You are receiving this mail because:
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270805
--- Comment #16 from Mark Millard ---
(In reply to Robert Clausecker from comment #13)
Looking again at the log for the successful boot that I was
referencing, it is not as I said (from grep for usb/uhub
references) and what varies between
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270805
--- Comment #15 from Mark Millard ---
(In reply to Robert Clausecker from comment #13)
Looking again at the log for the successful boot that I was
referencing, it is not as I said (from grep for usb/uhub
references):
Dec 31 16:00:24 CA72_
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270805
--- Comment #14 from Mark Millard ---
(In reply to Robert Clausecker from comment #11)
All my ZFS testing was with the same drive in different ports.
All my UFS testing was with the same drive in different ports.
(ZFS drive vs. UFS drive
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270805
--- Comment #13 from Robert Clausecker ---
(In reply to Mark Millard from comment #12)
Weird. I only ever tried to connect to the USB A ports. Maybe the USB A ports
are not all the same?
--
You are receiving this mail because:
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270805
--- Comment #12 from Mark Millard ---
(In reply to Robert Clausecker from comment #10)
I did not write anything about USB2, only USB3.? .
The issue is USB3.0 vs USB3.2 for the hardware in the
Windows Dev Kit 2023 (WDK23) hubs/ports and it
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270805
--- Comment #11 from Robert Clausecker ---
(In reply to Robert Clausecker from comment #10)
Previous testing, as in, before I finally set up the machine. After setting it
up, I tried attaching a variety of other USB disks that may have al
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270805
--- Comment #10 from Robert Clausecker ---
(In reply to Mark Millard from comment #9)
The thermal zones for some reason do not have registers to read the temperature
from. Hence some internal interface returns -1, which is converted into
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270805
--- Comment #9 from Mark Millard ---
Another FYI of an oddity (during a buildworld):
# sysctl -a | grep "temp.*[0-9]C$"
hw.acpi.thermal.tz31.temperature: -273.1C
hw.acpi.thermal.tz30.temperature: -273.1C
hw.acpi.thermal.tz29.temperature: -
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263908
Graham Perrin changed:
What|Removed |Added
CC||grahamper...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270805
--- Comment #8 from Mark Millard ---
Just FYI: A problem that I've noticed is:
# date
Wed Dec 31 16:50:41 PST 1969
despite /etc/rc.conf having:
ntpd_enable="YES"
ntpd_sync_on_start="YES"
and it working booting other machines.
--
You a
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270805
--- Comment #7 from Mark Millard ---
(In reply to Mark Millard from comment #6)
I found the distinction that controls failure vs.
success in booting via the USB3 ports:
USB3-C ugen0.5: at usbus0 ports:
ZFS and UFS boots fail.
USB3-A uge
25 matches
Mail list logo
