https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244692
Bug ID: 244692
Summary: gjournal TRIM support
Product: Base System
Version: 12.1-RELEASE
Hardware: Any
OS: Any
Status: New
Severity: Affects Only Me
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244692
Kubilay Kocak changed:
What|Removed |Added
CC||f...@freebsd.org
Assigne
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244693
Bug ID: 244693
Summary: gmirror configure priority does not take an effect
until reboot?
Product: Base System
Version: 12.1-RELEASE
Hardware: Any
OS:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244605
--- Comment #3 from Brian Zou ---
(In reply to Vladimir Kondratyev from comment #1)
Thanks, I installed it from ports.
--
You are receiving this mail because:
You are the assignee for the bug.
_
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233361
Ed Maste changed:
What|Removed |Added
See Also||https://bugs.freebsd.org/bu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233361
Ed Maste changed:
What|Removed |Added
Blocks|228919 |
Referenced Bugs:
https://bugs.freebs
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233094
Bug 233094 depends on bug 228919, which changed state.
Bug 228919 Summary: GCC 4.2.1 removal
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228919
What|Removed |Added
---
On Sun, 8 Mar 2020 at 17:13, Andy Farkas wrote:
>
> Is anyone actually working on the vt(4) driver? Will it ever
> become feature-parity with the old sc(4) driver?
Yes, and yes. What specific missing functionality are you affected by?
> I've noticed some weird things happening on my console rec
On Mon, Mar 09, 2020 at 10:37:52AM -0400, Ed Maste wrote:
> On Sun, 8 Mar 2020 at 17:13, Andy Farkas wrote:
> >
> > Is anyone actually working on the vt(4) driver? Will it ever
> > become feature-parity with the old sc(4) driver?
>
> Yes, and yes. What specific missing functionality are you affe
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237463
--- Comment #16 from commit-h...@freebsd.org ---
A commit references this bug:
Author: luporl
Date: Mon Mar 9 19:01:17 UTC 2020
New revision: 358814
URL: https://svnweb.freebsd.org/changeset/base/358814
Log:
[aacraid] Handle both AIF an
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237463
Leandro Lupori changed:
What|Removed |Added
Status|In Progress |Closed
Resolution|---
On 2020-03-10 01:04, Konstantin Belousov wrote:
Take a look at r334530.
"or the user really hates this feature and can't wait to turn it off"
Excellently explained by Bruce as usual:
"Revision 314641 - (view) (download) (annotate) - [select for diffs]
Modified Sat Mar 4 06:19:12 2017 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244698
Bug ID: 244698
Summary: NFSv3 lock manager unhelpful error message
Product: Base System
Version: 12.1-RELEASE
Hardware: Any
OS: Any
Status: New
Seve
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244699
Bug ID: 244699
Summary: growfs panics after [r358714, r358716]
Product: Base System
Version: CURRENT
Hardware: Any
OS: Any
Status: New
Severity: Aff
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244699
Li-Wen Hsu changed:
What|Removed |Added
Status|New |Open
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244699
--- Comment #2 from Li-Wen Hsu ---
Forgot to attach panic message:
+ /etc/rc.d/growfs onestart
Growing root partition to fill device
ada0 recovered
ada0p3 resized
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244699
--- Comment #3 from Mark Johnston ---
Might this be fixed by r358812?
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244705
Bug ID: 244705
Summary: /usr/src/sys/x86/x86/tsc.c: System Clock is 0.3% slow
since r352684
Product: Base System
Version: CURRENT
Hardware: amd64
OS:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244705
Theron Tarigo changed:
What|Removed |Added
Keywords||regression
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244699
--- Comment #4 from Chuck Silvers ---
Yes, this is the problem that is fixed by r358812.
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org ma
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244706
Bug ID: 244706
Summary: [panic] NULL dereference inside __mtx_lock_sleep()
Product: Base System
Version: 11.3-STABLE
Hardware: Any
OS: Any
Status: New
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244706
--- Comment #1 from Eugene Grosbein ---
The CPU is two-core Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz, if it matters.
--
You are receiving this mail because:
You are the assignee for the bug.
___
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244706
--- Comment #2 from Eugene Grosbein ---
Also, this system does not clear RAM between reboots, so dmesg buffer survives
panic and saved to the log after reboot:
Fatal trap 12: page fault while in kernel mode
cpuid = 1; apic id = 02
fault vi
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206484
Mark Millard changed:
What|Removed |Added
Resolution|--- |Overcome By Events
Stat
24 matches
Mail list logo
