[9fans] mk results in rc: suicide:

[9fans] mk results in rc: suicide:

[Marco Feichtinger]

Trying to compile a kernel on a local fossil machine,
I get following errors during the build
        rc: 1844: suicide: sys: trap: fault read addr=0x965708 pc=0x0000b5d9
        mk: 8c -I../boot -FTVw ../boot/printstub.c : exit status=rc 1844: suicide: sys: trap: fault read addr=0x965708 pc=0x0000b5d9

At the same time /dev/kprint outputs 
        1844 rc: checked 20 page table entries

Every time i retried to compile, that error comes up, but on different steps during the build.
It even happens during 'mk clean'.

One time i even got
        rc 1148: suicide: sys: trap: general protection violation pc=0x0000744c
        mk: 8c -I../boot -FTVw ../port/print.c: exit status=rc 1148: suicide: sys: trap: general protection violation pc=0x0000744c

What do these error mean?

-marco


------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T68f44cf88ca61ff3-Mf907951987cf14e1b45d4b28
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

Re: [9fans] mk results in rc: suicide:

[Alexander Kapshuk]

On Thu, Jul 4, 2024 at 4:44 PM Marco Feichtinger <marco@germteig.com> wrote:
> 
> Trying to compile a kernel on a local fossil machine,
> I get following errors during the build
>         rc: 1844: suicide: sys: trap: fault read addr=0x965708 pc=0x0000b5d9
>         mk: 8c -I../boot -FTVw ../boot/printstub.c : exit status=rc 1844: suicide: sys: trap: fault read addr=0x965708 pc=0x0000b5d9
> 
> At the same time /dev/kprint outputs
>         1844 rc: checked 20 page table entries
> 
> Every time i retried to compile, that error comes up, but on different steps during the build.
> It even happens during 'mk clean'.
> 
> One time i even got
>         rc 1148: suicide: sys: trap: general protection violation pc=0x0000744c
>         mk: 8c -I../boot -FTVw ../port/print.c: exit status=rc 1148: suicide: sys: trap: general protection violation pc=0x0000744c
> 
> What do these error mean?
> 
> -marco
> 

Inspecting the process in the debugger might be insightful.
The Debugging section of https://9p.io/sys/doc/comp.pdf demonstrates
how to do it, and the error message exemplified is very similar to
what you got.

------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T68f44cf88ca61ff3-Mfb345e61d3b891c4ee4ba725
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

Re: [9fans] mk results in rc: suicide:

[wb.kloke]

[-- Attachment #1: Type: text/plain, Size: 267 bytes --]

The symptoms look like disk full error.
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T68f44cf88ca61ff3-M5f914074957df945a1b6432a
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

[-- Attachment #2: Type: text/html, Size: 761 bytes --]

Re: [9fans] mk results in rc: suicide:

[Marco Feichtinger]

Thanks for the hints.

I don't believe that this is a disk full error,
since it's a fresh install on a 16GB SATADOM.

Now following crash during mk:
       rc: 2819: suicide: sys: trap: fault read addr=0x965708 pc=0x0000b5d9
       mk: 8c -FTVw pcf.rootc.c : exit status=rc 2819: suicide: sys: trap: fault read addr=0x965708 pc=0x0000b5d9

So I tried acid.
        % acid 2819
        /proc/2819/text:386 plan 9 executable
        /sys/lib/acid/port
        /sys/lib/acid/386
        acid: src(0x0000b5d9)
        /sys/src/cmd/rc/plan9.c:476
                471                     int n;
                472
                473                     if(f<0 || f>=NFD)
                474                             return 0;
                475             Again:
                >476            if(dir[f].i==dir[f].n){ /* read */
                477                             free(dir[f].dbuf);
                478                             dir[f].dbuf = 0;
                479                             n = dirread(f, &dir[f].dbuf);
                480                             if(n>0){
                481                                     if(onlydirs){
        acid: stk()
        <stdin>:2: (error) no stack frame: './acid' file does not exist

I have no idea what that means.
Also, I don't understand acid well enough to use correctly, so i need to play more with it.

What's interesting is, when I set the window to 'noscroll', run mk, and manually 
scroll down the window, I get the kernel build without crashing.
If I scroll down too fast, it crashes.

-marco



------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T68f44cf88ca61ff3-M36a7c66c644662bf6ec85728
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

Re: [9fans] mk results in rc: suicide:

[Dave Eckhardt]

If it were my machine I would probably run a RAM tester overnight.

Dave Eckhardt

------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T68f44cf88ca61ff3-M02fac44b503b2dfc5c1be904
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

Re: [9fans] mk results in rc: suicide:

[Charles Forsyth]

[-- Attachment #1: Type: text/plain, Size: 432 bytes --]

yes, i'd suspect RAM or RAM setup

On Thu, 4 Jul 2024 at 20:55, Dave Eckhardt <davide+p9@cs.cmu.edu> wrote:

> If it were my machine I would probably run a RAM tester overnight.
> 
> Dave Eckhardt

------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T68f44cf88ca61ff3-M1d97d3b43535c1d4014c1d9f
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

[-- Attachment #2: Type: text/html, Size: 1645 bytes --]

Re: [9fans] mk results in rc: suicide:

[ibrahim via 9fans]

[-- Attachment #1: Type: text/plain, Size: 633 bytes --]

I made this experience some time ago and suspect one of your static libraries didn't get rebuild. To verify this have a look in your /386/lib folder and verify the timestamp of your libraries. If you find the culprit manually change to that library and do "mk nuke ; mk ; mk install".

I would guess you tried to add a system call to the kernel and your libc wasn't rebuild - but thats only a guess.


------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T68f44cf88ca61ff3-M87a7792e7cf56899ef10fb12
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

[-- Attachment #2: Type: text/html, Size: 1161 bytes --]

Re: [9fans] mk results in rc: suicide:

[ibrahim via 9fans]

[-- Attachment #1: Type: text/plain, Size: 581 bytes --]

To avoid such problems while rebuilding kernels + libraries + commands you can use namespaces or some tricks as in http://9p.io/wiki/plan9/compiling_kernels/index.html 

There is also divergefs for plan9 which I personally don't use but you can give it a try.

Avoid recompiling your kernel, libraries and commands directly in /sys/src.

Good luck
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T68f44cf88ca61ff3-M60506689a3962f863de10655
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

[-- Attachment #2: Type: text/html, Size: 1235 bytes --]