On 7/18/2014 1:18 PM, Alfred Perlstein wrote:
On 7/18/14, 6:28 AM, Allan Jude wrote:
On 2014-07-17 16:12, Adrian Chadd wrote:
On 17 July 2014 13:03, Alberto Mijares amijar...@gmail.com wrote:
On Thu, Jul 17, 2014 at 2:58 PM, Adrian Chadd adr...@freebsd.org
wrote:
Hi!
3) The binary packages
I'm dealing with a shit sandwich right now where the mps(4) or cam_da
reorders drives on a few thousand legacy MBR machines I have (and I
can't easily install glabel ATM), and !EARLY_AP_STARTUP seems to have
regressed. I'd like to be able to run w/o EARLY_AP_STARTUP right
quick so I can take a
I wasn't subscribed to -x11 earlier but do want to add some commentary
to this thread.
The language describing these drivers in upstream is not at all
ambiguous WRT to how bad these are and Linux distributions have
dropped them:
menuconfig DRM_LEGACY
bool "Enable legacy drivers (DANGEROUS)"
panic: mutex sched lock 0 not owned at /d0/kev/freebsd/sys/kern/sched_ule.c:2379
On Thu, Aug 31, 2017 at 7:38 AM, John Baldwin <j...@freebsd.org> wrote:
> On Wednesday, August 30, 2017 04:54:07 PM Kevin Bowling wrote:
>> I'm dealing with a shit sandwich right now where the m
32b compat is quite different than i386 arch. It makes sense to
maintain 32b compat for quite a while.
On Wed, May 30, 2018 at 3:33 AM, Thomas Mueller wrote:
>> Wow, this blew up quite a lot bigger than I anticipated. I'll try to
>> summarize the discussion a bit below and then suggest a way
from
GENERIC and consider if you can instead use 'include GENERIC-NODEBUG'
to only track local modifications.
Regards,
Kevin Bowling
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe
Hi,
I have two systems with a zpool 2x2 mirror on 7.2k RPM disks. One
system also has a flash SLOG.
The flash SLOG system took around 12 hours to complete freebsd-update
from 13.2 to 14.0-RC1. The system without the SLOG took nearly 24
hours. This was the result of ~50k patches, and ~10k
On Mon, Aug 14, 2023 at 4:45 PM Greg 'groggy' Lehey wrote:
>
> [moving to current as requested by bz@]
>
> On Monday, 14 August 2023 at 10:09:22 -0700, Kevin Bowling wrote:
> >
> > I'm able to replicate this on my I217 using iperf3. It happens
> > quickly with
On Sun, Aug 13, 2023 at 6:55 PM Greg 'groggy' Lehey wrote:
>
> I've spent the last couple of days chasing random hangs on my -CURRENT
> box. It seems to be related to the Ethernet driver (em). I've been
> trying without much success to chase it down, and I'd be grateful.
> The box is headless,
9.20230721.panic.png
>
> According to the result of bisect, kernel panic starts with following
> commit.
>
> --
> commit 95f7b36e8fac45092b9a4eea5e32732e979989f0
> Author: Kevin Bowling
> Date: Thu Jul 20 20:3
On Sat, Jul 22, 2023 at 1:21 AM Yasuhiro Kimura wrote:
>
> From: Kevin Bowling
> Subject: Re: Kernel panic after updating 14-CURRENT amd64 to
> main-n264268-ff4633d9f89
> Date: Fri, 21 Jul 2023 21:44:13 -0700
>
> > Thanks, I have reverted for now. Can you tell me whic
rt
> FreeBSD UNIX: Web: https://FreeBSD.org
> NTP: Web: https://nwtime.org
>
> e^(i*pi)+1=0
>
>
> In message
> om>
> , Kevin Bowling writes:
> > The two MFVs on head have improved/fixed stability with poudriere for
> &
The two MFVs on head have improved/fixed stability with poudriere for
me 48 core bare metal.
On Thu, Aug 10, 2023 at 6:37 AM Cy Schubert wrote:
>
> In message om>
> , Kevin Bowling writes:
> > Possibly https://github.com/openzfs/zfs/commit/2cb992a99ccadb78d97049b40bd4
Possibly
https://github.com/openzfs/zfs/commit/2cb992a99ccadb78d97049b40bd442eb4fdc549d
On Tue, Aug 8, 2023 at 10:08 AM Dag-Erling Smørgrav wrote:
>
> At some point between 42d088299c (4 May) and f0c9703301 (26 June), a
> deadlock was introduced in ZFS. It is still present as of 9c2823bae9 (4
14 matches
Mail list logo
