On Wed, 7 Jul 2021 09:38:05 +0100
Edward Tomasz Napiera?a wrote:
> On 0705T1833, Gary Jennejohn wrote:
> > On Mon, 5 Jul 2021 15:04:48 +0100
> > Edward Tomasz Napiera__a wrote:
> >
> > > On 0701T1330, Gary Jennejohn wrote:
> > > > Gary Jennejohn wrote:
> > > > > I noticed that the valu
On 0705T1833, Gary Jennejohn wrote:
> On Mon, 5 Jul 2021 15:04:48 +0100
> Edward Tomasz Napiera__a wrote:
>
> > On 0701T1330, Gary Jennejohn wrote:
> > > Gary Jennejohn wrote:
> > > > I noticed that the value of vm.debug.divisor affects what value is
> > > > returned in uma_core.c:uma_dbg_kski
On Mon, 5 Jul 2021 15:04:48 +0100
Edward Tomasz Napiera__a wrote:
> On 0701T1330, Gary Jennejohn wrote:
> > Gary Jennejohn wrote:
> > > I noticed that the value of vm.debug.divisor affects what value is
> > > returned in uma_core.c:uma_dbg_kskip(), so I decided to try a few
> > > different val
On 0701T1330, Gary Jennejohn wrote:
> Gary Jennejohn wrote:
> > I noticed that the value of vm.debug.divisor affects what value is
> > returned in uma_core.c:uma_dbg_kskip(), so I decided to try a few
> > different values.
> >
> > The returned value is used to set skipdbg in uma_core.c:item_dtor(
Gary Jennejohn wrote:
> On Wed, 30 Jun 2021 10:35:14 -0600
> Warner Losh wrote:
>
> > On Wed, Jun 30, 2021 at 6:58 AM Gary Jennejohn wrote:
> >
> > > On Wed, 30 Jun 2021 06:02:59 +0100
> > > Graham Perrin wrote:
> > >
> > > > On 29/06/2021 10:42, Gary Jennejohn wrote:
> > > > > _
On Wed, 30 Jun 2021 10:35:14 -0600
Warner Losh wrote:
> On Wed, Jun 30, 2021 at 6:58 AM Gary Jennejohn wrote:
>
> > On Wed, 30 Jun 2021 06:02:59 +0100
> > Graham Perrin wrote:
> >
> > > On 29/06/2021 10:42, Gary Jennejohn wrote:
> > > > ___ panic is now the result of an unaligned free.
> >
On Wed, Jun 30, 2021 at 6:58 AM Gary Jennejohn wrote:
> On Wed, 30 Jun 2021 06:02:59 +0100
> Graham Perrin wrote:
>
> > On 29/06/2021 10:42, Gary Jennejohn wrote:
> > > ___ panic is now the result of an unaligned free.
> > >
> > > panic: Unaligned free of 0xf800259e2800 from zone
> > >
On Wed, 30 Jun 2021 06:02:59 +0100
Graham Perrin wrote:
> On 29/06/2021 10:42, Gary Jennejohn wrote:
> > ___ panic is now the result of an unaligned free.
> >
> > panic: Unaligned free of 0xf800259e2800 from zone
> > 0xfe00dc9d2000(da_ccb) slab 0xf800259e2fd8(3)
> >
> > I have th
On 29/06/2021 10:42, Gary Jennejohn wrote:
… panic is now the result of an unaligned free.
panic: Unaligned free of 0xf800259e2800 from zone
0xfe00dc9d2000(da_ccb) slab 0xf800259e2fd8(3)
I have the crash dump and a debug kernel in case anyone wants more info.
Can you post the
I was sort of hoping that all the recent changes made by imp@ in cam and
umass may have fixed the cause of the kernel crash.
Unfortunately not.
But there is a change - instead of a duplicate free the panic is now the
result of an unaligned free.
panic: Unaligned free of 0xf800259e2800 from z
On Sat, 12 Jun 2021 14:10:36 +0100
Edward Tomasz Napiera__a wrote:
> On 0610T1150, Gary Jennejohn wrote:
> > On Tue, 8 Jun 2021 17:54:05 +0200
> > Gary Jennejohn wrote:
> >
> > [big snip]
>
> [..]
>
> > So, I did ``git reset --hard 8dc96b74edb844bb621afeba38fe4af104b13120'',
> > which was t
On 0610T1150, Gary Jennejohn wrote:
> On Tue, 8 Jun 2021 17:54:05 +0200
> Gary Jennejohn wrote:
>
> [big snip]
[..]
> So, I did ``git reset --hard 8dc96b74edb844bb621afeba38fe4af104b13120'',
> which was the penultimate commit made by trasz to clear CCBs on the stack
> after he committed 3394d42
On Tue, 8 Jun 2021 17:54:05 +0200
Gary Jennejohn wrote:
[big snip]
> Here's the kgdb backtrace with the -O0 kernel:
>
> (kgdb) bt
> #0 0x8081d706 in doadump (textdump=0)
> at /usr/src/sys/kern/kern_shutdown.c:398
> #1 0x804ef15a in db_dump (dummy=-2138500043, dummy2=false,
On Tue, 8 Jun 2021 06:27:04 -0600
Warner Losh wrote:
> On Tue, Jun 8, 2021 at 2:47 AM Gary Jennejohn wrote:
>
[snip old stuff]
> > Here the kgdb backtrace:
> >
> > Unread portion of the kernel message buffer:
> > panic: Duplicate free of 0xf800356b9000 from zone
> > 0xfe00dcbdd800(da_cc
On Tue, Jun 8, 2021 at 8:42 AM Gary Jennejohn wrote:
> On Tue, 8 Jun 2021 06:48:19 -0600
> Warner Losh wrote:
>
> > Sorry to reply to myself... had a thought as my brain rested while making
> > tea...
> >
> > I think we may need to consider reverting (or at least not yet enabling)
> > the uma st
On Tue, 8 Jun 2021 06:48:19 -0600
Warner Losh wrote:
> Sorry to reply to myself... had a thought as my brain rested while making
> tea...
>
> I think we may need to consider reverting (or at least not yet enabling)
> the uma stuff.
>
I tested and enabled the UMA CCB stuff immediately after tra
Sorry to reply to myself... had a thought as my brain rested while making
tea...
I think we may need to consider reverting (or at least not yet enabling)
the uma stuff.
On Tue, Jun 8, 2021 at 6:27 AM Warner Losh wrote:
>
>
> On Tue, Jun 8, 2021 at 2:47 AM Gary Jennejohn
> wrote:
>
>> On Mon, 7
On Tue, Jun 8, 2021 at 2:47 AM Gary Jennejohn wrote:
> On Mon, 7 Jun 2021 16:54:11 -0400
> Mark Johnston wrote:
>
> > On Mon, Jun 07, 2021 at 11:01:09AM +0200, Gary Jennejohn wrote:
> > > I've seen this panic three times in the last two days:
> > >
> > > [first panic]
> > > Unread portion of the
On Tue, 8 Jun 2021 11:04:33 +0200
Mateusz Guzik wrote:
> Given how easy it is to reproduce perhaps you can spend a little bit
> of time narrowing it down to a specific commit. You can do it with
> git-bisect.
>
Ok, I'll give it a try.
--
Gary Jennejohn
On 6/8/21 1:34 PM, Gary Jennejohn wrote:
Fields in the ccb like periph_name, unit_number and dev_name are filled
with zeroes.
Smells like a double free, like the panic message indicates, but would
be nice to know exactly which driver is doing this, if it is "ATA" or
"UMASS", so to speak.
Ma
On Tue, 8 Jun 2021 11:20:37 +0200
Hans Petter Selasky wrote:
> On 6/8/21 11:04 AM, Mateusz Guzik wrote:
> > Apparently caused by recent changes to CAM.
> >
> > Let me know if you want more information.
>
> Maybe you can print the *ccb being freed and figure out which device
> it belongs to.
>
On 6/8/21 11:04 AM, Mateusz Guzik wrote:
Apparently caused by recent changes to CAM.
Let me know if you want more information.
Maybe you can print the *ccb being freed and figure out which device it
belongs to.
--HPS
Given how easy it is to reproduce perhaps you can spend a little bit
of time narrowing it down to a specific commit. You can do it with
git-bisect.
On 6/8/21, Gary Jennejohn wrote:
> On Mon, 7 Jun 2021 16:54:11 -0400
> Mark Johnston wrote:
>
>> On Mon, Jun 07, 2021 at 11:01:09AM +0200, Gary Jenn
On Mon, 7 Jun 2021 16:54:11 -0400
Mark Johnston wrote:
> On Mon, Jun 07, 2021 at 11:01:09AM +0200, Gary Jennejohn wrote:
> > I've seen this panic three times in the last two days:
> >
> > [first panic]
> > Unread portion of the kernel message buffer:
> >
> >
> > Fatal trap 12: page fault while
On Mon, Jun 07, 2021 at 11:01:09AM +0200, Gary Jennejohn wrote:
> I've seen this panic three times in the last two days:
>
> [first panic]
> Unread portion of the kernel message buffer:
>
>
> Fatal trap 12: page fault while in kernel mode
> cpuid = 3; apic id = 03
> fault virtual address = 0x8
I've seen this panic three times in the last two days:
[first panic]
Unread portion of the kernel message buffer:
Fatal trap 12: page fault while in kernel mode
cpuid = 3; apic id = 03
fault virtual address = 0x801118000
fault code = supervisor write data, page not present
instruc
26 matches
Mail list logo
