Re: current kernel crashes while building userland

[Robert Swindells]

Riccardo Mottola  wrote:
>On 24/10/2019 22:06, Robert Swindells wrote:
>> You maybe need some changes to the ata disk driver that went in on the
>> 23rd.
>
>bad luck. I upgraded kernel and modules, installed and it crashes during 
>userland build, so no progress at all.
>
>Still a crash in compat_90_sys_fstatvfs1() at compat_90_sys_fstatvfs1
>
>Could it be that it is actually a compatibility issue, where userland 
>calls somethingin the kernel that crashes? I wonder that it is compat_90

The recommended build process is to do the userland first then use the
new toolchain to build the kernel.

This is a clean build isn't it ? The amd64 port switched to gcc 8.3 on
the 22nd.

Re: current kernel crashes while building userland

[Riccardo Mottola]

Hi,


On 24/10/2019 22:06, Robert Swindells wrote:

You maybe need some changes to the ata disk driver that went in on the
23rd.



bad luck. I upgraded kernel and modules, installed and it crashes during 
userland build, so no progress at all.


Still a crash in compat_90_sys_fstatvfs1() at compat_90_sys_fstatvfs1


Could it be that it is actually a compatibility issue, where userland 
calls somethingin the kernel that crashes? I wonder that it is compat_90



Riccardo.

Re: current kernel crashes while building userland

[Riccardo Mottola]

Hi Manuel,

Manuel Bouyer wrote:


System panicked: trap
Backtrace from time of crash is available.
crash> bt
_KERNEL_OPT_NARCNET() at 0
?() at c68067793ea0
vpanic() at vpanic+0x161
panic() at panic+0x3c
trap() at trap+0xb55
--- trap (number 6) ---
compat_90_sys_fstatvfs1() at compat_90_sys_fstatvfs1



Is it the same for the 2 crashes ?


yes it is, only the addresses change:

_KERNEL_OPT_NARCNET() at 0
?() at b28069383ea0
vpanic() at vpanic+0x161
panic() at panic+0x3c
trap() at trap+0xb55
--- trap (number 6) ---
compat_90_sys_fstatvfs1() at compat_90_sys_fstatvfs1



maybe Robert is right and I have unlucky version of the ATA driver?


No, it looks like  something else (probably in compat_90_sys_fstatvfs1()).

When you updated your kernel, did you also update modules ?



Yes I did! I usually update them after, but in this case, with the old 
modules, the new kernel wouldn't even boot.


Riccardo

PS: in the meanwhile, I updated CVS as of yesterday, so new kernel + 
modules is coming and then a new try for userland

Re: current kernel crashes while building userland

[Christos Zoulas]

In article <29de16f3-bbd0-5d3e-46d8-0c0965b16...@libero.it>,
Riccardo Mottola   wrote:
>Hi Michael,
>
>Michael van Elst wrote:
>> You should be able to analyse the files with the crash(8) tool
>> and report the panic message and backtrace.
>
>
>System panicked: trap
>Backtrace from time of crash is available.
>crash> bt
>_KERNEL_OPT_NARCNET() at 0
>?() at c68067793ea0
>vpanic() at vpanic+0x161
>panic() at panic+0x3c
>trap() at trap+0xb55
>--- trap (number 6) ---
>compat_90_sys_fstatvfs1() at compat_90_sys_fstatvfs1
>
>
>maybe Robert is right and I have unlucky version of the ATA driver?

Is the compat code a module?

christos

Re: current kernel crashes while building userland

[Michael van Elst]

On Thu, Oct 24, 2019 at 10:42:21PM +0200, Riccardo Mottola wrote:
> Hi Michael,
> 
> Michael van Elst wrote:
> > You should be able to analyse the files with the crash(8) tool
> > and report the panic message and backtrace.
> 
> compat_90_sys_fstatvfs1() at compat_90_sys_fstatvfs1

fstatvfs() was changed recently to also report an original mount path.
The panic seems to be in the compatibility function for older binaries.


-- 
Michael van Elst
Internet: mlel...@serpens.de
"A potential Snark may lurk in every tree."

Re: current kernel crashes while building userland

[Manuel Bouyer]

On Thu, Oct 24, 2019 at 10:42:21PM +0200, Riccardo Mottola wrote:
> Hi Michael,
> 
> Michael van Elst wrote:
> > You should be able to analyse the files with the crash(8) tool
> > and report the panic message and backtrace.
> 
> 
> System panicked: trap
> Backtrace from time of crash is available.
> crash> bt
> _KERNEL_OPT_NARCNET() at 0
> ?() at c68067793ea0
> vpanic() at vpanic+0x161
> panic() at panic+0x3c
> trap() at trap+0xb55
> --- trap (number 6) ---
> compat_90_sys_fstatvfs1() at compat_90_sys_fstatvfs1
> 

Is it the same for the 2 crashes ?

> 
> maybe Robert is right and I have unlucky version of the ATA driver?

No, it looks like  something else (probably in compat_90_sys_fstatvfs1()).

When you updated your kernel, did you also update modules ?

-- 
Manuel Bouyer 
 NetBSD: 26 ans d'experience feront toujours la difference
--

Re: current kernel crashes while building userland

[Riccardo Mottola]

Hi Michael,

Michael van Elst wrote:

You should be able to analyse the files with the crash(8) tool
and report the panic message and backtrace.



System panicked: trap
Backtrace from time of crash is available.
crash> bt
_KERNEL_OPT_NARCNET() at 0
?() at c68067793ea0
vpanic() at vpanic+0x161
panic() at panic+0x3c
trap() at trap+0xb55
--- trap (number 6) ---
compat_90_sys_fstatvfs1() at compat_90_sys_fstatvfs1


maybe Robert is right and I have unlucky version of the ATA driver?

Riccardo

Re: current kernel crashes while building userland

[Michael van Elst]

riccardo.mott...@libero.it (Riccardo Mottola) writes:

>in /var/crash however I find the two gzipped files, too big to post 
>public here. Each crash has its own.

You should be able to analyse the files with the crash(8) tool
and report the panic message and backtrace.

Another possibility is to put the following into /etc/sysctl.conf

ddb.onpanic?=1
ddb.commandonenter="trace;show registers"

This should avoid the reboot and print a backtrace and register
values that you can read.

-- 
-- 
Michael van Elst
Internet: mlel...@serpens.de
"A potential Snark may lurk in every tree."

Re: current kernel crashes while building userland

[Robert Swindells]

Riccardo Mottola  wrote:
>I upgraded to 9.99.17 22nd October. I built kernel + modules, rebooted.
>on amd64
>
>Then I started a distribution build... and after some hours, the machine 
>resets.
>I restarted again (without doing an update build)... and it reboots again.
>
>I just find the machine rebooted, I can't read any message.
>
>in /var/crash however I find the two gzipped files, too big to post 
>public here. Each crash has its own.
>
>Can I send them somebody? How can I give more information?
>
>This machine is running netbsd current since a long time and has always 
>been very stable (many other issues, but never reboots during builds)

You maybe need some changes to the ata disk driver that went in on the
23rd.

Also you could look at a description of how to use gdb on crash dumps
here:

current kernel crashes while building userland

[Riccardo Mottola]

Hi,

I upgraded to 9.99.17 22nd October. I built kernel + modules, rebooted.
on amd64

Then I started a distribution build... and after some hours, the machine 
resets.

I restarted again (without doing an update build)... and it reboots again.

I just find the machine rebooted, I can't read any message.

in /var/crash however I find the two gzipped files, too big to post 
public here. Each crash has its own.


Can I send them somebody? How can I give more information?

This machine is running netbsd current since a long time and has always 
been very stable (many other issues, but never reboots during builds)



Riccardo