On Wed, Mar 10, 2021 at 08:25:00AM -0700, Warner Losh wrote:
> ...
> > Also (as yesterday), neither laptop exhibited a problem after the
> > corresponding update.
> >
>
> Yes it "works" without invariants. I'm working on a better fix that isn't
> such a huge game of whack-a-mole that defers the
On Wed, Mar 10, 2021 at 5:37 AM David Wolfskill
wrote:
> On Tue, Mar 09, 2021 at 04:04:56PM -0700, Warner Losh wrote:
> > On Tue, Mar 9, 2021 at 2:46 PM David Wolfskill
> wrote:
> > ...
> > > uma_zalloc_debug: zone "malloc-1024"umass0 on uhub2
> > > with the following non-sleepable locks held:
On Tue, Mar 09, 2021 at 04:04:56PM -0700, Warner Losh wrote:
> On Tue, Mar 9, 2021 at 2:46 PM David Wolfskill wrote:
> ...
> > uma_zalloc_debug: zone "malloc-1024"umass0 on uhub2
> > with the following non-sleepable locks held:
> > umass0: on usbus0
> > exclusive sleep mutex CAM device
On Tue, Mar 09, 2021 at 04:04:56PM -0700, Warner Losh wrote:
> ...
> > The build nmachine (still?) panics:
> > ...
> I'm willing to "poke at it" a bit, given a hint or two...
>
> OK. I know what's happening here. disk_create() posts an event and also
> expects to sleep to get memory. I can fix
On Tue, Mar 9, 2021 at 2:46 PM David Wolfskill wrote:
> On Tue, Mar 09, 2021 at 01:23:16PM -0800, David Wolfskill wrote:
> > On Tue, Mar 09, 2021 at 01:53:37PM -0700, Warner Losh wrote:
> > > ...
> > > The following reviews should fix this. It introduces a no-wait variant
> for
> > >
On Tue, Mar 09, 2021 at 01:23:16PM -0800, David Wolfskill wrote:
> On Tue, Mar 09, 2021 at 01:53:37PM -0700, Warner Losh wrote:
> > ...
> > The following reviews should fix this. It introduces a no-wait variant for
> > disk_alloc(), provides a way to free allocated, but not created, disks and
> >
On Tue, Mar 09, 2021 at 01:53:37PM -0700, Warner Losh wrote:
> ...
> The following reviews should fix this. It introduces a no-wait variant for
> disk_alloc(), provides a way to free allocated, but not created, disks and
> changes CAM to use the new routines and take some care for not leaking
On Tue, Mar 9, 2021 at 5:09 AM David Wolfskill wrote:
> Just did a source-based update from:
>
> FreeBSD 14.0-CURRENT #1205 main-n245338-221622ec0c8e: Mon Mar 8 03:49:58
> PST 2021
> r...@freebeast.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/sys/GENERIC
> amd64 145 145
>
>
On Tue, Mar 09, 2021 at 04:09:18AM -0800, David Wolfskill wrote:
> ...
> I can afford to leave it that way for a bit, in case anyone has
> suggestions for poking at it to get more information. I expect to
> be attempting the same upgrade on a couple of laptops -- after they
> finish building
Just did a source-based update from:
FreeBSD 14.0-CURRENT #1205 main-n245338-221622ec0c8e: Mon Mar 8 03:49:58 PST
2021
r...@freebeast.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/sys/GENERIC
amd64 145 145
to:
FreeBSD 14.0-CURRENT #1206 main-n245363-b3dac3913dc9: Tue Mar
10 matches
Mail list logo