> From: "Theo de Raadt"
> Date: Mon, 21 Nov 2022 21:55:21 -0700
>
> I agree.
Yeah. At some point I had some hope we would learn what those were
about. But I haven't seen anything show up in specs or in Linux.
ok kettenis@
> Jonathan Matthew wrote:
>
> > On a Dell R6515, acpimadt(4) prints
On Mon, Nov 21, 2022 at 04:56:07PM +0100, Martijn van Duren wrote:
> On Sun, 2022-11-20 at 19:35 -0700, Theo de Raadt wrote:
> > Steve Litt wrote:
> >
> > > Vitaliy Makkoveev said on Mon, 21 Nov 2022 03:48:21 +0300
> > >
> > > > > On 20 Nov 2022, at 18:06, Odd Martin Baanrud
> > > > > wrote:
>
delete mbuhl from Cc:.
From: YASUOKA Masahiko
Date: Sat, 19 Nov 2022 16:37:47 +0900 (JST)
> On Sat, 19 Nov 2022 14:41:18 +0900 (JST)
> YASUOKA Masahiko wrote:
>> On Wed, 12 Oct 2022 07:58:20 +0900 (JST)
>> YASUOKA Masahiko wrote:
>>> On Wed, 05 Oct 2022 13:37:35 +0900 (JST)
>>> Masato Asou
I agree.
Jonathan Matthew wrote:
> On a Dell R6515, acpimadt(4) prints this 512 times during boot:
>
> acpimadt0: unknown apic structure type 80
>
> Previous generations of machines had a few of these, and they were easy
> enough to ignore, but 512 is a bit excessive.
>
> On further
On a Dell R6515, acpimadt(4) prints this 512 times during boot:
acpimadt0: unknown apic structure type 80
Previous generations of machines had a few of these, and they were easy
enough to ignore, but 512 is a bit excessive.
On further inspection, it seems types 0x80 through 0xFF are reserved
On Mon, Nov 21, 2022 at 07:01:44PM +0100, Tobias Heider wrote:
> + if (verbose)
This block could use braces.
> + fprintf(stderr, "%s %s to %s\n",
> + (nowrite ? "would copy" : "copying"),
> + src, dst);
> +
David Gwynne wrote:
> this is ok by me, obviously.
interesting backhistory of this problem: it was critical for getting
suspend/resume working on many machines. it's the only way you knew
the clocks were all correct...
this is ok by me, obviously.
On Sun, Nov 20, 2022 at 06:18:55PM -0600, Scott Cheloha wrote:
> Hi,
>
> systat(1)'s vmstat view should not use statclock() ticks to count
> elapsed time. First, ticks are very low resolution and they aren't
> always of equal length. Second, we're counting the
On Sun, Nov 20, 2022 at 03:15:55PM -0500, George Koehler wrote:
> On Sun, 20 Nov 2022 06:55:23 -0600
> Scott Cheloha wrote:
>
> > Build completed, upgrade from resulting bsd.rd completed. I think
> > this is ready to commit.
>
> I'm happy to hear that your dual G4 macppc is running and your
On Mon, Nov 21, 2022 at 08:09:10PM +, ssnf wrote:
> > Klemens Nanni:
> > You need to be more specific, installing to a softraid volume has always
> > required manual steps, so I have no idea what you did (not) do and when.
>
> The comment in install.sub, above my diff, states that "In case
Visa Hankala writes:
> On Fri, Nov 18, 2022 at 11:03:06AM -0500, Dave Voutila wrote:
>> That fixes booting and the Surface Keyboard is usable, but I'm getting
>> spurious faults coming from retpoline out of filt_wseventdetach if I
>> detach and reattach the Surface Keyboard multiple times
> Klemens Nanni:
> You need to be more specific, installing to a softraid volume has always
> required manual steps, so I have no idea what you did (not) do and when.
The comment in install.sub, above my diff, states that "In case this is
a softraid device, make sure all underlying device nodes
On Mon, Nov 21, 2022 at 07:01:44PM +0100, Tobias Heider wrote:
> On Mon, Nov 21, 2022 at 03:09:25PM +, Klemens Nanni wrote:
> > On Mon, Nov 21, 2022 at 03:42:37PM +0100, Tobias Heider wrote:
> > > Here is a more cleaned up version of the previous diff. I moved all the
> > > firmware logic to
On Mon, Nov 21, 2022 at 03:09:25PM +, Klemens Nanni wrote:
> On Mon, Nov 21, 2022 at 03:42:37PM +0100, Tobias Heider wrote:
> > Here is a more cleaned up version of the previous diff. I moved all the
> > firmware logic to a new write_firmware() function. This should be easy
> > to extend if
On Sun, 2022-11-20 at 19:35 -0700, Theo de Raadt wrote:
> Steve Litt wrote:
>
> > Vitaliy Makkoveev said on Mon, 21 Nov 2022 03:48:21 +0300
> >
> > > > On 20 Nov 2022, at 18:06, Odd Martin Baanrud
> > > > wrote:
> > > >
> > > > Hello,
> > > >
> > > > I have a Raspberry Pi 4 with 2 USB NIC’s
On Mon, Nov 21, 2022 at 03:42:37PM +0100, Tobias Heider wrote:
> Here is a more cleaned up version of the previous diff. I moved all the
> firmware logic to a new write_firmware() function. This should be easy
> to extend if we decide to ship more firmware this way.
This seems more tidy.
>
>
> Date: Mon, 21 Nov 2022 15:42:37 +0100
> From: Tobias Heider
>
> On Sat, Nov 19, 2022 at 08:27:18PM +0100, Tobias Heider wrote:
> > On Sat, Nov 19, 2022 at 07:25:52PM +0100, Mark Kettenis wrote:
> > > > Date: Sat, 19 Nov 2022 18:44:19 +0100
> > > > From: Tobias Heider
> > > >
> > > > On Sat,
On Sat, Nov 19, 2022 at 08:27:18PM +0100, Tobias Heider wrote:
> On Sat, Nov 19, 2022 at 07:25:52PM +0100, Mark Kettenis wrote:
> > > Date: Sat, 19 Nov 2022 18:44:19 +0100
> > > From: Tobias Heider
> > >
> > > On Sat, Nov 19, 2022 at 06:33:51PM +0100, Mark Kettenis wrote:
> > > > > Date: Sat, 19
no, they don't grow anymore. apparently, the initial growth is associated with
network services(tor, i2pd and the like), which do not immediately gain full
force. using iperf also does not cause mbufs to grow
thx! you're the best ^.^
19 matches
Mail list logo
