Re: Panic: Page Fault in Kernel: Yesterday's CURRENT

2021-12-16 Thread Larry Rosenman
On 12/16/2021 9:03 pm, Larry Rosenman wrote: On 12/10/2021 10:43 am, Larry Rosenman wrote: 14-2021_12_07-1217 - - 1.87G 2021-12-07 12:17 14-2021_12_09-1957 NR / 121G 2021-12-09 19:57 If that's any help On 12/10/2021 10:36 am, Alexander

Re: Panic: Page Fault in Kernel: Yesterday's CURRENT

2021-12-16 Thread Larry Rosenman
On 12/10/2021 10:43 am, Larry Rosenman wrote: 14-2021_12_07-1217 - - 1.87G 2021-12-07 12:17 14-2021_12_09-1957 NR / 121G 2021-12-09 19:57 If that's any help On 12/10/2021 10:36 am, Alexander Motin wrote: Hi Larry, This looks like some

Vastly improved speeds with iwn(4)

2021-12-16 Thread Graham Perrin
In recent months, what (if anything) changed to improve things for users of iwn(4)? Intel Centrino Advanced-N 6205 [Taylor Peak] here. At home, previously I typically got less than 9 (download), now I get more than 70 Mbps. (I see last month's

Re: Any Cronyx Tau* (ce(4) or cp(4)) users ?

2021-12-16 Thread Gleb Smirnoff
On Thu, Dec 16, 2021 at 07:53:10AM -0800, Gleb Smirnoff wrote: T> P.S. If you really wish to deprecate something, I can suggest you to T> sacrifice sbni(4) :) P.P.S. The driver actually provides a historical example: a driver removed, later appeared not only used by somebody but even having a

Re: Any Cronyx Tau* (ce(4) or cp(4)) users ?

2021-12-16 Thread Gleb Smirnoff
On Thu, Dec 16, 2021 at 09:30:41AM -0700, Warner Losh wrote: W> > E> And we're doing that just because the drivers compiles ? W> > G> We are doing that because the hardware is still produced ... W> > E> ... a lot of obsolete hardware that we've removed are still produced ... W> > G> I'd be

Re: Any Cronyx Tau* (ce(4) or cp(4)) users ?

2021-12-16 Thread Warner Losh
On Thu, Dec 16, 2021 at 8:54 AM Gleb Smirnoff wrote: > Emmanuel, > > look at this communication: > > E> And we're doing that just because the drivers compiles ? > G> We are doing that because the hardware is still produced ... > E> ... a lot of obsolete hardware that we've removed are still

Re: Any Cronyx Tau* (ce(4) or cp(4)) users ?

2021-12-16 Thread Gleb Smirnoff
Emmanuel, look at this communication: E> And we're doing that just because the drivers compiles ? G> We are doing that because the hardware is still produced ... E> ... a lot of obsolete hardware that we've removed are still produced ... G> I'd be interested to see at least one example ... E>

Re: Any Cronyx Tau* (ce(4) or cp(4)) users ?

2021-12-16 Thread Emmanuel Vadot
On Thu, 16 Dec 2021 07:01:30 -0800 Gleb Smirnoff wrote: > Emmanuel, > > On Thu, Dec 16, 2021 at 10:17:33AM +0100, Emmanuel Vadot wrote: > E> > E> I'm not sure I understand the logic here. > E> > E> We're keeping drivers for museum grade hardware that no developer > have > E> > E> access to

Re: Any Cronyx Tau* (ce(4) or cp(4)) users ?

2021-12-16 Thread Gleb Smirnoff
Emmanuel, On Thu, Dec 16, 2021 at 10:17:33AM +0100, Emmanuel Vadot wrote: E> > E> I'm not sure I understand the logic here. E> > E> We're keeping drivers for museum grade hardware that no developer have E> > E> access to and likely no one uses nowadays just for an hypothetical E> > E>

Re: CURRENT: llvm13 seem to miscompile dns/bind916 (9.16.23)

2021-12-16 Thread Dimitry Andric
On 15 Dec 2021, at 18:44, FreeBSD User wrote: > > On Fri, 10 Dec 2021 19:41:07 +1030 > Daniel O'Connor via freebsd-current wrote: >>> On 25 Nov 2021, at 18:50, FreeBSD User wrote: ... > >>> Since then named is crashing with a mysterious segmentation fault (see PR >>> 259921, >>>

Re: Any Cronyx Tau* (ce(4) or cp(4)) users ?

2021-12-16 Thread Emmanuel Vadot
On Wed, 15 Dec 2021 10:11:16 -0800 Gleb Smirnoff wrote: > On Wed, Dec 15, 2021 at 05:52:02PM +0100, Emmanuel Vadot wrote: > E> > > I've noticed this /sbin/sconfig binary and after looking it's for > E> > > configuring Cronyx E1 PCI (PCI as in PCI, not PCIe). > E> > > The products pages ([1],

Re: On amd64 main-n251456-22c4ab6cb015-dirty (Dec.-7): /boot/kernel/ng_ubt.ko is getting "symbol sysctl___net_bluetooth undefined"

2021-12-16 Thread Hans Petter Selasky
On 12/15/21 23:58, Mark Millard via freebsd-current wrote: Back when I upgraded the ThreadRipper 1950X amd64 system to (line split for readability): # uname -apKU FreeBSD CA72_16Gp_ZFS 14.0-CURRENT FreeBSD 14.0-CURRENT #25 main-n251456-22c4ab6cb015-dirty: Tue Dec 7 19:38:53 PST 2021