https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233764
Xin LI changed:
What|Removed |Added
CC||delp...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244083
Xin LI changed:
What|Removed |Added
Status|New |Open
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278383
Bug ID: 278383
Summary: libsysdecode: sysdecode_syscallnames should be
sysdecode_syscallname
Product: Documentation
Version: Latest
Hardware: Any
OS:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253759
--- Comment #2 from Michael Osipov ---
As it turns out to:
$ grep -ri -e MustQuoteChars -e MUST_QUOTE_CHARS .
/KNOWNBUGS: If a full name phrase includes characters from MustQuoteChars,
sendmail
/KNOWNBUGS: will quote the entire full name
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278379
Bug ID: 278379
Summary: aibs: Unable to set device class
Product: Base System
Version: Unspecified
Hardware: Any
OS: Any
Status: New
Severity:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278043
--- Comment #5 from Mark Johnston ---
(In reply to Gleb Smirnoff from comment #4)
I was wondering the same thing. I will try to reimplement the data path using
a raw socket this afternoon.
--
You are receiving this mail because:
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278043
--- Comment #4 from Gleb Smirnoff ---
I haven't yet look deep into the problem, but my first thought about it
was the following. Why do we create a UDP socket from the kernel, while
a userland dhclient would use a raw socket? In kernel
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253759
Michael Osipov changed:
What|Removed |Added
CC||micha...@freebsd.org
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277538
--- Comment #6 from commit-h...@freebsd.org ---
A commit in branch stable/14 references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=5128c8948b4e56d20dfd623aeb030fb39c8f95b0
commit 5128c8948b4e56d20dfd623aeb030fb39c8f95b0
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278348
--- Comment #10 from Mark Johnston ---
> It is not reproduceable fast
Is it reproducible at all? I am asking if you saw it more than once.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272001
Wolfram Schneider changed:
What|Removed |Added
Status|In Progress |Closed
Resolution|---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273665
Wolfram Schneider changed:
What|Removed |Added
Assignee|b...@freebsd.org|obr...@freebsd.org
---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250332
Wolfram Schneider changed:
What|Removed |Added
Status|Open|Closed
Resolution|---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=223516
Wolfram Schneider changed:
What|Removed |Added
Status|Open|In Progress
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=223516
Wolfram Schneider changed:
What|Removed |Added
Blocks||278378
Referenced Bugs:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278378
Wolfram Schneider changed:
What|Removed |Added
Depends on||223516
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278378
Bug ID: 278378
Summary: man(1) ignores corrupt gzip'd manual pages
Product: Base System
Version: 15.0-CURRENT
Hardware: Any
OS: Any
Status: New
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278376
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|p...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278376
Bug ID: 278376
Summary: pf: support NAT64
Product: Base System
Version: 15.0-CURRENT
Hardware: Any
OS: Any
Status: New
Severity: Affects Only Me
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276763
Michael Osipov changed:
What|Removed |Added
URL|https://github.com/Bastille |
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235136
Michael Osipov changed:
What|Removed |Added
See Also||https://github.com/rspamd/r
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235136
--- Comment #5 from Michael Osipov ---
If you happen to run Postfix like me then it is broken there as well:
https://github.com/vdukhovni/postfix/blob/a6993c3a48ebc3ac6cefd9913dab4b8c23b66ab8/postfix/src/global/mail_date.c#L125-L130
--
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235136
--- Comment #4 from Michael Osipov ---
Here is the faulty value coming from:
https://github.com/freebsd/freebsd-src/blob/bed0b2146faa2e9a445d9f9196c7b46f50034631/contrib/sendmail/src/arpadate.c#L191-L198
--
You are receiving this mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235136
--- Comment #3 from Michael Osipov ---
Here is the updated spec:
https://datatracker.ietf.org/doc/html/rfc5322#section-3.3
You are right, but I think that the issue with the format isn't in cron itself
regardless of th invalid time value.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278375
Olivier Certner changed:
What|Removed |Added
Assignee|b...@freebsd.org|r...@freebsd.org
--
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278375
Bug ID: 278375
Summary: EN: High CPU usage by kernel threads related to ZFS
Product: Base System
Version: 13.3-RELEASE
Hardware: Any
OS: Any
Status: New
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260257
Marry Joy changed:
What|Removed |Added
CC||marryjoy6...@gmail.com
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278043
--- Comment #3 from Richard Wai ---
(In reply to Mark Johnston from comment #2)
After dwelling on this for a bit, I'm starting to conclude that adding a
tunable for these source checks. For bootp/nfs root systems that can then be
turned
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254289
Christos Margiolis changed:
What|Removed |Added
Resolution|--- |Overcome By Events
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278366
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|emulat...@freebsd.org
--
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278365
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|emulat...@freebsd.org
--
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278363
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|emulat...@freebsd.org
--
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278366
Bug ID: 278366
Summary: linsysfs: missing
devices/system/cpu/cpu%d/topology/core_id
Product: Base System
Version: Unspecified
Hardware: Any
OS: Any
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278365
Bug ID: 278365
Summary: Linuxulator is missing EPOLLEXCLUSIVE support
Product: Base System
Version: Unspecified
Hardware: Any
OS: Any
Status: New
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278363
Bug ID: 278363
Summary: linsysfs: /sys/class/drm and /sys/dev/char/226:*
contents don't match /dev/dri
Product: Base System
Version: Unspecified
Hardware: Any
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278340
Gleb Smirnoff changed:
What|Removed |Added
Assignee|b...@freebsd.org|gleb...@freebsd.org
--
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278361
Bug ID: 278361
Summary: adduser after password confirmation shows [: -a:
unexpected operator
Product: Base System
Version: 14.0-RELEASE
Hardware: Any
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278311
Xin LI changed:
What|Removed |Added
Assignee|b...@freebsd.org|delp...@freebsd.org
--
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278348
Mark Linimon changed:
What|Removed |Added
Keywords||crash
--
You are receiving this
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278342
Kyle Evans changed:
What|Removed |Added
Status|New |In Progress
Flags|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278342
--- Comment #2 from commit-h...@freebsd.org ---
A commit in branch main references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=bbc6e6c5ec8c7938b98a36899fa083aa7ce4724e
commit bbc6e6c5ec8c7938b98a36899fa083aa7ce4724e
Author:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278342
Kyle Evans changed:
What|Removed |Added
Assignee|b...@freebsd.org|kev...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278311
--- Comment #18 from Joel Bodenmann ---
dev.cpu.*.temperature seems to consistently report the exact same temperature
for all cores. Is that expected?
This is the first time I have an AMD build - I have been a team blue player
until now.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278311
--- Comment #17 from Joel Bodenmann ---
hedt1% sysctl dev.amdtemp
dev.amdtemp.3.ccd3: 32.6C
dev.amdtemp.3.ccd2: 30.6C
dev.amdtemp.3.ccd1: 31.6C
dev.amdtemp.3.ccd0: 32.0C
dev.amdtemp.3.core0.sensor0: 44.1C
dev.amdtemp.3.sensor_offset: 0
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278311
--- Comment #16 from Xin LI ---
(In reply to Joel Bodenmann from comment #15)
Glad to hear! Just wanted to double check -- is the driver fully functional
now? E.g. what does `sysctl dev.amdtemp` and `sysctl dev.cpu | grep temp` show
now?
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278311
--- Comment #15 from Joel Bodenmann ---
I'm getting temperature readouts now.
Whether they are accurate I can't easily check but the values appear to be
within reasonable expectations (34C idle, 91C during stress -c 48 on a water
cooled
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278311
Xin LI changed:
What|Removed |Added
Attachment #249919|0 |1
is obsolete|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278348
--- Comment #9 from mikhail.rok...@gmail.com ---
(In reply to Mark Johnston from comment #8)
Thank you for reply.
It is not reproduceable fast and I don't have enough time for thorough
continuous heavy, overloading testing (like compiling
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278348
Mark Johnston changed:
What|Removed |Added
CC||ma...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278348
--- Comment #7 from mikhail.rok...@gmail.com ---
Created attachment 249957
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=249957=edit
VirtualBox_FBSD-CUR_13_04_2024_19_30_54.png
--
You are receiving this mail because:
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278348
--- Comment #6 from mikhail.rok...@gmail.com ---
Created attachment 249956
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=249956=edit
VirtualBox_FBSD-CUR_13_04_2024_19_30_38.png
--
You are receiving this mail because:
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278348
--- Comment #5 from mikhail.rok...@gmail.com ---
Created attachment 249955
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=249955=edit
VirtualBox_FBSD-CUR_13_04_2024_19_30_23.png
--
You are receiving this mail because:
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278348
--- Comment #4 from mikhail.rok...@gmail.com ---
Created attachment 249954
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=249954=edit
VirtualBox_FBSD-CUR_13_04_2024_19_30_08.png
--
You are receiving this mail because:
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278348
--- Comment #3 from mikhail.rok...@gmail.com ---
Created attachment 249953
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=249953=edit
VirtualBox_FBSD-CUR_13_04_2024_19_29_46.png
--
You are receiving this mail because:
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278348
--- Comment #2 from mikhail.rok...@gmail.com ---
Created attachment 249952
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=249952=edit
VirtualBox_FBSD-CUR_13_04_2024_19_29_02.png
--
You are receiving this mail because:
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278348
--- Comment #1 from mikhail.rok...@gmail.com ---
Created attachment 249951
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=249951=edit
VirtualBox_FBSD-CUR_13_04_2024_19_26_12.png
--
You are receiving this mail because:
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278348
Bug ID: 278348
Summary: Sudden kernel panic Fatal double fault
Product: Base System
Version: CURRENT
Hardware: Any
OS: Any
Status: New
Severity:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277886
--- Comment #7 from Warner Losh ---
(In reply to Edward Tomasz Napierala from comment #6)
> Well of course it's not. But the worst case we're risking here is what is
> currently the only case: a boot failure.
I think it's a bad idea. It
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278347
Bug ID: 278347
Summary: pmcstat: crash on image processing
Product: Base System
Version: CURRENT
Hardware: Any
OS: Any
Status: New
Severity:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278342
--- Comment #1 from Kyle Evans ---
LGTM (will commit later this evening, ~6-8 hours, if nobody else beats me to
it)
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277886
--- Comment #6 from Edward Tomasz Napierala ---
>Personally I don't really like this idea, though, because it is not guaranteed
>to work
Well of course it's not. But the worst case we're risking here is what is
currently the only case:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277886
--- Comment #5 from Edward Tomasz Napierala ---
Can we ignore the unsupported flags but still verify the checksums?
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278342
Bug ID: 278342
Summary: daemon(8): -R doesn't restart supervised process
Product: Base System
Version: 14.0-RELEASE
Hardware: Any
OS: Any
Status: New
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271651
(intentionally left blank) changed:
What|Removed |Added
Status|Open|Closed
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278340
Bug ID: 278340
Summary: unix(4): regressed after base aba79b0f4a3f
Product: Base System
Version: 15.0-CURRENT
Hardware: Any
OS: Any
Status: New
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277717
Vladimir Druzenko changed:
What|Removed |Added
CC||v...@freebsd.org
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278311
--- Comment #13 from Joel Bodenmann ---
Thank you for the explanation. That is pretty much what I expected/understood
but I wasn't sure whether you're hinting at something I'm unaware of.
dmesg (attached)
hedt1% sysctl dev.amdtemp
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278311
Joel Bodenmann changed:
What|Removed |Added
Attachment #249916|0 |1
is obsolete|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278311
--- Comment #11 from Xin LI ---
(In reply to Joel Bodenmann from comment #10)
> could you elaborate what kind of information would show up in dmesg that
> would be considered sensitive?
Well, I'm just trying to remind you that you should
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235136
--- Comment #2 from Mike Lempriere ---
I barely even remember this one... I worked around my issue by lowering
spamassassin scores, so haven't paid it further attention.
However, looking closely now at email source headers, I am still
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278311
--- Comment #10 from Joel Bodenmann ---
You have me slightly concerned now... could you elaborate what kind of
information would show up in dmesg that would be considered sensitive? I guess
one could argue about MAC addresses if being
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278311
--- Comment #9 from Xin LI ---
(In reply to Joel Bodenmann from comment #8)
can you share the dmesg output (ideally with only sensitive information
redacted) and `sysctl dev.amdtemp` output?
--
You are receiving this mail because:
You
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278311
--- Comment #8 from Joel Bodenmann ---
After applying your latest patch I am getting corresponding entries as
dev.cpu.*.temperature. However, all of them report -0.0
Nothing shows up in dmesg.boot that would indicate anything helpful.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263234
--- Comment #5 from John Grafton ---
Merged:
https://github.com/freebsd/freebsd-src/commit/215c0a5158f17f515f365fc28a9ff0b367be8fc9
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278333
Yuri Victorovich changed:
What|Removed |Added
Assignee|b...@freebsd.org|toolch...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278333
Bug ID: 278333
Summary: clang-18 crashes on the port
audio/noise-suppression-for-voice-lv2: Assertion
failed: (result && "no existing substitution for
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278319
Mark Linimon changed:
What|Removed |Added
Keywords||crash
--
You are receiving this
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278320
Yuri Victorovich changed:
What|Removed |Added
CC||d...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278320
Bug ID: 278320
Summary: clang fails on the port science/dynare (version 5.4):
Assertion failed: (idx < size()), function operator[],
file
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278311
Xin LI changed:
What|Removed |Added
Attachment #249918|0 |1
is obsolete|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278319
Bug ID: 278319
Summary: filemon(4) panics with KASAN enabled
Product: Base System
Version: CURRENT
Hardware: Any
OS: Any
Status: New
Severity:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278311
--- Comment #6 from Joel Bodenmann ---
I see this in your patch:
> DEVICEID_AMD_HOSTB19H_M10H_ROOT
and this in /var/log/messages:
> amdtemp0: on hostb24
Not knowing anything about the internal workings of amdtemp, I'd say this looks
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278311
--- Comment #5 from Joel Bodenmann ---
Does not seem to work yet. Still not getting any temperatures (via sysctl or
sysutils/hwstat).
Looking through /var/log/messages I see:
7306 Apr 12 00:37:15 hedt1 kernel: amdtemp0:
on hostb24
7307
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278311
--- Comment #4 from Xin LI ---
Created attachment 249918
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=249918=edit
Add support for F19 M10 (0x10..0x1f)
Could you please try this patch?
--
You are receiving this mail because:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278316
--- Comment #6 from Henrich Hartzer ---
Pull request on Github: https://github.com/freebsd/freebsd-src/pull/1164
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278316
--- Comment #5 from Henrich Hartzer ---
I got it working! Patch is attached.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278316
--- Comment #4 from Henrich Hartzer ---
Created attachment 249917
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=249917=edit
Atom S1200 UART support
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278311
--- Comment #3 from Joel Bodenmann ---
Created attachment 249916
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=249916=edit
dmesg.boot
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278311
--- Comment #2 from Joel Bodenmann ---
Created attachment 249915
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=249915=edit
pciconf
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278316
--- Comment #3 from Henrich Hartzer ---
>From FreeBSD, dmesg also shows IRQ 16. But sysctl -a seems to say that IRQ 32
is in use for the uart. I've had no luck forcing it to use IRQ 16.
But... with debug.uart_force_poll = 1, it works!
So
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278311
Xin LI changed:
What|Removed |Added
CC||delp...@freebsd.org
--- Comment #1 from
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265884
Xin LI changed:
What|Removed |Added
CC||delp...@freebsd.org
--- Comment #1 from
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278316
--- Comment #2 from Henrich Hartzer ---
I tried to force IRQ 16 (FreeBSD uses 32) with device.hints, but it stays at
IRQ 32. I'm not sure if this is a problem or not.
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278316
--- Comment #1 from Henrich Hartzer ---
I just verified that this is working on a hardware level by booting Linux Mint
and testing the port.
dmesg (from Linux) said: "ttyS4 at I/O 0xf000 (irq = 16, base_baud = 115200) is
a 16550A"
--
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278316
Bug ID: 278316
Summary: Intel Atom S1200 (Centerton) serial UART not working
Product: Base System
Version: 14.0-RELEASE
Hardware: amd64
OS: Any
Status: New
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271675
--- Comment #12 from Alan Somers ---
(In reply to Rick Macklem from comment #11)
fuse_vnop_read or fuse_vnop_write might return EINTR if:
* uiomove(9) returns ERESTART or EINTR
* getblk returns NULL
* bwrite returns EINTR
* If a signal is
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271675
Rick Macklem changed:
What|Removed |Added
CC||asom...@freebsd.org
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276961
Dimitry Andric changed:
What|Removed |Added
Status|New |Open
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278311
Joel Bodenmann changed:
What|Removed |Added
Severity|Affects Only Me |Affects Some People
--
You are
401 - 500 of 61973 matches
Mail list logo
