Re: Error from reorder_kernel

2022-11-20 Thread Aaron Miller

I agree. I think I'll get a larger disk.

Thanks for the help!

--Aaron

On 11/20/22 01:14, Stuart Henderson wrote:
I doubt there's enough free space on /usr for reorder_kernel to work. 
But the disk overall is small and there's probably not a lot that you 
can clear out. If you were to reinstall, not create /usr/src, and add 
that space to /usr instead, that would buy you a bit of time, but 
ideally you'd want a larger disk.






Re: Error from reorder_kernel

2022-11-20 Thread Stuart Henderson
I doubt there's enough free space on /usr for reorder_kernel to work. But 
the disk overall is small and there's probably not a lot that you can clear 
out. If you were to reinstall, not create /usr/src, and add that space to 
/usr instead, that would buy you a bit of time, but ideally you'd want a 
larger disk.


--
 Sent from a phone, apologies for poor formatting.

On 20 November 2022 01:47:28 Aaron Miller  wrote:


On 11/19/22 16:31, Stuart Henderson wrote:


On 2022-11-19, Aaron Miller  wrote:

Hi misc,

I ran into an issue with reorder_kernel on 7.2. It directed me to its
log file, /usr/share/relink/kernel/GENERIC/relink.log, which contains this:

 (SHA256) /bsd: OK
 LD="ld" sh makegap.sh 0x gapdummy.o
 ld -T ld.script -X --warn-common -nopie -o newbsd ${SYSTEM_HEAD}
vers.o ${OBJS}
 textdatabssdechex
 00000
 mv newbsd newbsd.gdb
 ctfstrip -S -o newbsd newbsd.gdb
 strip: there are no sections to be copied!
 rm -f bsd.gdb
 mv -f newbsd bsd
 mv: newbsd: No such file or directory
 *** Error 1 in /usr/share/relink/kernel/GENERIC (Makefile:1940 'newbsd')

I think the relevant error is the "strip: there are no sections to be
copied".

Also I saw a blue text error from the kernel (typing it rather than
copy-pasting):

  uvn_flush: obj=0xfd801ee12890, offset=0x576.  error during
pageout.

 uvn_flush: WARNING: changes to page may be lost!

What does this mean? And how do I fix it?

Most likely your filesystem is full.

Thanks! Which filesystem should I free space on?

$ df -h
Filesystem SizeUsed   Avail Capacity  Mounted on
/dev/sd1a  733M323M373M46%/
/dev/sd1k  6.2G4.9G1.0G83%/home
/dev/sd1d  1.1G436K1.1G 0%/tmp
/dev/sd1f  1.5G1.4G   73.3M95%/usr
/dev/sd1g  402M339M   42.2M89%/usr/X11R6
/dev/sd1h  3.2G2.1G1.0G67%/usr/local
/dev/sd1j  1.8G   1000M710M58%/usr/obj
/dev/sd1i  1.2G2.0K1.2G 0%/usr/src
/dev/sd1e  1.7G825M865M49%/var




Re: Error from reorder_kernel

2022-11-19 Thread Noth
Your /usr is too small, 2G is the safe size for it these days. 73.3M 
probably isn't enough for reorder_kernel to work. You might have a 
coredump somewhere in /usr/share/relink.


Cheers,

Noth

On 20/11/2022 02:47, Aaron Miller wrote:

On 11/19/22 16:31, Stuart Henderson wrote:


On 2022-11-19, Aaron Miller  wrote:

Hi misc,

I ran into an issue with reorder_kernel on 7.2. It directed me to its
log file, /usr/share/relink/kernel/GENERIC/relink.log, which 
contains this:


    (SHA256) /bsd: OK
    LD="ld" sh makegap.sh 0x gapdummy.o
    ld -T ld.script -X --warn-common -nopie -o newbsd ${SYSTEM_HEAD}
vers.o ${OBJS}
    text    data    bss    dec    hex
    0    0    0    0    0
    mv newbsd newbsd.gdb
    ctfstrip -S -o newbsd newbsd.gdb
    strip: there are no sections to be copied!
    rm -f bsd.gdb
    mv -f newbsd bsd
    mv: newbsd: No such file or directory
    *** Error 1 in /usr/share/relink/kernel/GENERIC (Makefile:1940 
'newbsd')


I think the relevant error is the "strip: there are no sections to be
copied".

Also I saw a blue text error from the kernel (typing it rather than
copy-pasting):

     uvn_flush: obj=0xfd801ee12890, offset=0x576. error during
pageout.

    uvn_flush: WARNING: changes to page may be lost!

What does this mean? And how do I fix it?

Most likely your filesystem is full.

Thanks! Which filesystem should I free space on?

$ df -h
Filesystem Size    Used   Avail Capacity  Mounted on
/dev/sd1a  733M    323M    373M    46%    /
/dev/sd1k  6.2G    4.9G    1.0G    83%    /home
/dev/sd1d  1.1G    436K    1.1G 0%    /tmp
/dev/sd1f  1.5G    1.4G   73.3M    95%    /usr
/dev/sd1g  402M    339M   42.2M    89%    /usr/X11R6
/dev/sd1h  3.2G    2.1G    1.0G    67%    /usr/local
/dev/sd1j  1.8G   1000M    710M    58%    /usr/obj
/dev/sd1i  1.2G    2.0K    1.2G 0%    /usr/src
/dev/sd1e  1.7G    825M    865M    49%    /var




Re: Error from reorder_kernel

2022-11-19 Thread Aaron Miller

On 11/19/22 16:31, Stuart Henderson wrote:


On 2022-11-19, Aaron Miller  wrote:

Hi misc,

I ran into an issue with reorder_kernel on 7.2. It directed me to its
log file, /usr/share/relink/kernel/GENERIC/relink.log, which contains this:

    (SHA256) /bsd: OK
    LD="ld" sh makegap.sh 0x gapdummy.o
    ld -T ld.script -X --warn-common -nopie -o newbsd ${SYSTEM_HEAD}
vers.o ${OBJS}
    text    data    bss    dec    hex
    0    0    0    0    0
    mv newbsd newbsd.gdb
    ctfstrip -S -o newbsd newbsd.gdb
    strip: there are no sections to be copied!
    rm -f bsd.gdb
    mv -f newbsd bsd
    mv: newbsd: No such file or directory
    *** Error 1 in /usr/share/relink/kernel/GENERIC (Makefile:1940 'newbsd')

I think the relevant error is the "strip: there are no sections to be
copied".

Also I saw a blue text error from the kernel (typing it rather than
copy-pasting):

     uvn_flush: obj=0xfd801ee12890, offset=0x576.  error during
pageout.

    uvn_flush: WARNING: changes to page may be lost!

What does this mean? And how do I fix it?

Most likely your filesystem is full.

Thanks! Which filesystem should I free space on?

$ df -h
Filesystem Size    Used   Avail Capacity  Mounted on
/dev/sd1a  733M    323M    373M    46%    /
/dev/sd1k  6.2G    4.9G    1.0G    83%    /home
/dev/sd1d  1.1G    436K    1.1G 0%    /tmp
/dev/sd1f  1.5G    1.4G   73.3M    95%    /usr
/dev/sd1g  402M    339M   42.2M    89%    /usr/X11R6
/dev/sd1h  3.2G    2.1G    1.0G    67%    /usr/local
/dev/sd1j  1.8G   1000M    710M    58%    /usr/obj
/dev/sd1i  1.2G    2.0K    1.2G 0%    /usr/src
/dev/sd1e  1.7G    825M    865M    49%    /var



Re: Error from reorder_kernel

2022-11-19 Thread Stuart Henderson
On 2022-11-19, Aaron Miller  wrote:
> Hi misc,
>
> I ran into an issue with reorder_kernel on 7.2. It directed me to its 
> log file, /usr/share/relink/kernel/GENERIC/relink.log, which contains this:
> 
>    (SHA256) /bsd: OK
>    LD="ld" sh makegap.sh 0x gapdummy.o
>    ld -T ld.script -X --warn-common -nopie -o newbsd ${SYSTEM_HEAD} 
> vers.o ${OBJS}
>    text    data    bss    dec    hex
>    0    0    0    0    0
>    mv newbsd newbsd.gdb
>    ctfstrip -S -o newbsd newbsd.gdb
>    strip: there are no sections to be copied!
>    rm -f bsd.gdb
>    mv -f newbsd bsd
>    mv: newbsd: No such file or directory
>    *** Error 1 in /usr/share/relink/kernel/GENERIC (Makefile:1940 'newbsd')
>
> I think the relevant error is the "strip: there are no sections to be 
> copied".
>
> Also I saw a blue text error from the kernel (typing it rather than 
> copy-pasting):
>
>     uvn_flush: obj=0xfd801ee12890, offset=0x576.  error during 
> pageout.
>
>    uvn_flush: WARNING: changes to page may be lost!
>
> What does this mean? And how do I fix it?

Most likely your filesystem is full.


-- 
Please keep replies on the mailing list.



Error from reorder_kernel

2022-11-19 Thread Aaron Miller

Hi misc,

I ran into an issue with reorder_kernel on 7.2. It directed me to its 
log file, /usr/share/relink/kernel/GENERIC/relink.log, which contains this:


  (SHA256) /bsd: OK
  LD="ld" sh makegap.sh 0x gapdummy.o
  ld -T ld.script -X --warn-common -nopie -o newbsd ${SYSTEM_HEAD} 
vers.o ${OBJS}

  text    data    bss    dec    hex
  0    0    0    0    0
  mv newbsd newbsd.gdb
  ctfstrip -S -o newbsd newbsd.gdb
  strip: there are no sections to be copied!
  rm -f bsd.gdb
  mv -f newbsd bsd
  mv: newbsd: No such file or directory
  *** Error 1 in /usr/share/relink/kernel/GENERIC (Makefile:1940 'newbsd')

I think the relevant error is the "strip: there are no sections to be 
copied".


Also I saw a blue text error from the kernel (typing it rather than 
copy-pasting):


   uvn_flush: obj=0xfd801ee12890, offset=0x576.  error during 
pageout.


  uvn_flush: WARNING: changes to page may be lost!

What does this mean? And how do I fix it?

Thanks,

Aaron