On 2020/01/21 20:20, Patrick Welche wrote:
> On Tue, Jan 21, 2020 at 03:48:27PM +0900, Masanobu SAITOH wrote:
>> I suspect the location of your panic is after the following message
>> (because of ixgbe_allocate_msix()'s failure):
>>
>>> aprint_normal(" ETrackID %08x\n", ((uint32_t)high <<
On Tue, Jan 21, 2020 at 03:48:27PM +0900, Masanobu SAITOH wrote:
> I suspect the location of your panic is after the following message
> (because of ixgbe_allocate_msix()'s failure):
>
> > aprint_normal(" ETrackID %08x\n", ((uint32_t)high << 16) | low);
Exactly right:
ixg0 at pci8 dev 0
Hi.
On 2020/01/21 2:06, Patrick Welche wrote:
> On Mon, Jan 20, 2020 at 04:12:45PM +, Patrick Welche wrote:
>> On Mon, Jan 20, 2020 at 12:51:00PM +, Andrew Doran wrote:
>>> This also happened the last time I touched rw_downgrade(), and I backed out
>>> the change then, but both times I
> On Jan 20, 2020, at 3:44 PM, Christos Zoulas wrote:
>
> In article <20200120185023.gd28...@homeworld.netbsd.org>,
> Andrew Doran wrote:
>> Fix committed with sys/kern/kern_rwlock.c rev 1.62. I didn't see the
>> problem as I am running with LOCKDEBUG.
>>
>> Apologies for the disruption.
>
In article <20200120185023.gd28...@homeworld.netbsd.org>,
Andrew Doran wrote:
>Fix committed with sys/kern/kern_rwlock.c rev 1.62. I didn't see the
>problem as I am running with LOCKDEBUG.
>
>Apologies for the disruption.
FYI: powerpc/arm do not build anymore...
На 2020-01-20 в 18:50, Andrew Doran написа:
> Fix committed with sys/kern/kern_rwlock.c rev 1.62. I didn't see the
> problem as I am running with LOCKDEBUG.
>
> Apologies for the disruption.
All good now, thanks.
> Andrew
Hi,
Thanks for your quick fix.
It works fine for my laptop now.
On January 21, 2020 3:50:23 AM GMT+09:00, Andrew Doran wrote:
>Fix committed with sys/kern/kern_rwlock.c rev 1.62. I didn't see the
>problem as I am running with LOCKDEBUG.
>
>Apologies for the disruption.
>
>Andrew
--
Ryo
On Mon, Jan 20, 2020 at 04:12:45PM +, Patrick Welche wrote:
> On Mon, Jan 20, 2020 at 12:51:00PM +, Andrew Doran wrote:
> > This also happened the last time I touched rw_downgrade(), and I backed out
> > the change then, but both times I don't see the bug. I have some questions:
> >
> >
Fix committed with sys/kern/kern_rwlock.c rev 1.62. I didn't see the
problem as I am running with LOCKDEBUG.
Apologies for the disruption.
Andrew
On Mon, Jan 20, 2020 at 09:28:32AM -0800, Paul Goyette wrote:
> On Mon, 20 Jan 2020, Patrick Welche wrote:
>
> > On Mon, Jan 20, 2020 at 12:51:00PM +, Andrew Doran wrote:
> > > This also happened the last time I touched rw_downgrade(), and I backed
> > > out
> > > the change then, but both
On Mon, Jan 20, 2020 at 12:51:00PM +, Andrew Doran wrote:
> This also happened the last time I touched rw_downgrade(), and I backed out
> the change then, but both times I don't see the bug. I have some questions:
>
> - Are you running DIAGNOSTIC and/or LOCKDEBUG? I would be very interested
On Mon, 20 Jan 2020, Patrick Welche wrote:
On Mon, Jan 20, 2020 at 12:51:00PM +, Andrew Doran wrote:
This also happened the last time I touched rw_downgrade(), and I backed out
the change then, but both times I don't see the bug. I have some questions:
- Are you running DIAGNOSTIC and/or
Thanks. I can reproduce a hang on boot in qemu. It's hanging starting
init, waiting on "needbuf". Investigating now.
Andrew
On Mon, Jan 20, 2020 at 04:12:45PM +, Patrick Welche wrote:
> On Mon, Jan 20, 2020 at 12:51:00PM +, Andrew Doran wrote:
> > This also happened the last time I
On Mon, Jan 20, 2020 at 12:51:00PM +, Andrew Doran wrote:
> This also happened the last time I touched rw_downgrade(), and I backed out
> the change then, but both times I don't see the bug. I have some questions:
>
> - Are you running DIAGNOSTIC and/or LOCKDEBUG? I would be very interested
On Mon, Jan 20, 2020 at 12:51:00PM +, Andrew Doran wrote:
> This also happened the last time I touched rw_downgrade(), and I backed out
> the change then, but both times I don't see the bug. I have some questions:
2 amd64 boxes, let's call them a) and b)
> - Are you running DIAGNOSTIC
Hi,
Jason Thorpe writes:
>> On Jan 20, 2020, at 6:48 AM, Ryo ONODERA wrote:
>>
>> The black screen and ims(4) panic are not related to your change.
>> Older src tree with LOCKDEBUG reproduces these problem.
>
> I'll look at the ims(4) issuer.
Thank you very much.
I can test any patch.
> --
> On Jan 20, 2020, at 6:48 AM, Ryo ONODERA wrote:
>
> The black screen and ims(4) panic are not related to your change.
> Older src tree with LOCKDEBUG reproduces these problem.
I'll look at the ims(4) issuer.
-- thorpej
Ryo ONODERA writes:
> Ryo ONODERA writes:
>
>> Hi,
>>
>> Andrew Doran writes:
>>
>>> Hi,
>>>
>>> This also happened the last time I touched rw_downgrade(), and I backed out
>>> the change then, but both times I don't see the bug. I have some questions:
>>>
>>> - Are you running DIAGNOSTIC
Ryo ONODERA writes:
> Hi,
>
> Andrew Doran writes:
>
>> Hi,
>>
>> This also happened the last time I touched rw_downgrade(), and I backed out
>> the change then, but both times I don't see the bug. I have some questions:
>>
>> - Are you running DIAGNOSTIC and/or LOCKDEBUG? I would be very
On Mon, 20 Jan 2020, Andrew Doran wrote:
Hi,
This also happened the last time I touched rw_downgrade(), and I backed out
the change then, but both times I don't see the bug. I have some questions:
- Are you running DIAGNOSTIC and/or LOCKDEBUG? I would be very interested
to see what happens
On Mon, 20 Jan 2020 at 13:06, Ryo ONODERA wrote:
>
> Hi,
>
> Andrew Doran writes:
>
> > Hi,
> >
> > This also happened the last time I touched rw_downgrade(), and I backed out
> > the change then, but both times I don't see the bug. I have some questions:
> >
> > - Are you running DIAGNOSTIC
Hi,
Andrew Doran writes:
> Hi,
>
> This also happened the last time I touched rw_downgrade(), and I backed out
> the change then, but both times I don't see the bug. I have some questions:
>
> - Are you running DIAGNOSTIC and/or LOCKDEBUG? I would be very interested
> to see what happens
Hi,
This also happened the last time I touched rw_downgrade(), and I backed out
the change then, but both times I don't see the bug. I have some questions:
- Are you running DIAGNOSTIC and/or LOCKDEBUG? I would be very interested
to see what happens with a LOCKDEBUG kernel here.
- Do you
23 matches
Mail list logo
