Re: Fwd: Hurd shutdown problems

Aloha - I've updated to the latest Debian kernel package, which includes Samuel's patch. (thank you) This fixes the symbol table problem, but my VM still locks up after a failed swapoff. I do, however, get symbolic names displayed correctly from the kernel debugger at that point. Obviously,

Re: Fwd: Hurd shutdown problems

On Fri, Aug 12, 2016 at 09:07:48PM +0200, Samuel Thibault wrote: > > I'm curious: what makes it definitely wrong on a PC ? > > A PC has BIOS stuff between A and 10. Right, misread a 0 again. -- Richard Braun

Re: Fwd: Hurd shutdown problems

Richard Braun, on Fri 12 Aug 2016 21:06:48 +0200, wrote: > On Fri, Aug 12, 2016 at 07:53:08PM +0200, Samuel Thibault wrote: > > That's what I'm talking about, and that's the second part of the printfs > > above, and they are wrong: 1-100 is definitely wrong on a PC, > > and it includes the

Re: Fwd: Hurd shutdown problems

On Fri, Aug 12, 2016 at 07:53:08PM +0200, Samuel Thibault wrote: > That's what I'm talking about, and that's the second part of the printfs > above, and they are wrong: 1-100 is definitely wrong on a PC, > and it includes the debugging symbols. I'm curious: what makes it definitely wrong

Re: Fwd: Hurd shutdown problems

Richard Braun, on Fri 12 Aug 2016 19:57:10 +0200, wrote: > On Fri, Aug 12, 2016 at 05:17:26PM +0200, Samuel Thibault wrote: > > biosmem: heap: 114f000-7a00 > > > > and objdump shows: > > > > LOAD off0x1000 vaddr 0x8100 paddr 0x0100 align 2**12 > > filesz

Re: Fwd: Hurd shutdown problems

On Fri, Aug 12, 2016 at 07:57:10PM +0200, Richard Braun wrote: > On Fri, Aug 12, 2016 at 05:17:26PM +0200, Samuel Thibault wrote: > > biosmem: heap: 114f000-7a00 > > > > and objdump shows: > > > > LOAD off0x1000 vaddr 0x8100 paddr 0x0100 align 2**12 > > filesz

Re: Fwd: Hurd shutdown problems

On Fri, Aug 12, 2016 at 05:17:26PM +0200, Samuel Thibault wrote: > biosmem: heap: 114f000-7a00 > > and objdump shows: > > LOAD off0x1000 vaddr 0x8100 paddr 0x0100 align 2**12 > filesz 0x00114700 memsz 0x00114700 flags r-x > LOAD off0x00116000 vaddr

Re: Fwd: Hurd shutdown problems

Richard Braun, on Fri 12 Aug 2016 19:50:51 +0200, wrote: > On Fri, Aug 12, 2016 at 07:08:07PM +0200, Samuel Thibault wrote: > > More precisely though, adding debugging to vm_page_load: > > > > vm_page_load 1-100 1-100 > > vm_page_load 100-7a00 114f000-79c41000 > >

Re: Fwd: Hurd shutdown problems

On Fri, Aug 12, 2016 at 07:08:07PM +0200, Samuel Thibault wrote: > More precisely though, adding debugging to vm_page_load: > > vm_page_load 1-100 1-100 > vm_page_load 100-7a00 114f000-79c41000 > vm_page_load 7a00-7ffe 7a00-7ffe > > I.e. it properly skips

Re: Fwd: Hurd shutdown problems

Samuel Thibault, on Fri 12 Aug 2016 19:08:07 +0200, wrote: > What is supposed to exclude everything else? (modules, VGA BIOS, etc.) I'm tempted to apply the attached patch at least to the Debian package to brown-tape-fix the issue. What it does is: - Make biosmem_load_segment look for the

Re: Fwd: Hurd shutdown problems

Hello, Samuel Thibault, on Fri 12 Aug 2016 17:27:42 +0200, wrote: > Samuel Thibault, on Fri 12 Aug 2016 17:17:26 +0200, wrote: > > biosmem: heap: 114f000-7a00 > > > > and objdump shows: > > > > LOAD off0x1000 vaddr 0x8100 paddr 0x0100 align 2**12 > > filesz

Re: Fwd: Hurd shutdown problems

Samuel Thibault, on Fri 12 Aug 2016 17:17:26 +0200, wrote: > biosmem: heap: 114f000-7a00 > > and objdump shows: > > LOAD off0x1000 vaddr 0x8100 paddr 0x0100 align 2**12 > filesz 0x00114700 memsz 0x00114700 flags r-x > LOAD off0x00116000 vaddr 0x81115000

Re: Fwd: Hurd shutdown problems

Brent W. Baccala, on Thu 11 Aug 2016 15:29:27 -1000, wrote: > On Wed, Aug 10, 2016 at 4:33 AM, Richard Braun <[1]rbr...@sceen.net> wrote: > > On Wed, Aug 10, 2016 at 04:26:35PM +0200, Richard Braun wrote: > > the boot loader (see MULTIBOOT_FLAGS in boothdr.S), and at > > some point,

Re: Fwd: Hurd shutdown problems

On Wed, Aug 10, 2016 at 4:33 AM, Richard Braun wrote: > On Wed, Aug 10, 2016 at 04:26:35PM +0200, Richard Braun wrote: > > the boot loader (see MULTIBOOT_FLAGS in boothdr.S), and at > > some point, late during the boot process, module data are freed > > using (see

Re: Fwd: Hurd shutdown problems

On Wed, Aug 10, 2016 at 04:26:35PM +0200, Richard Braun wrote: > the boot loader (see MULTIBOOT_FLAGS in boothdr.S), and at > some point, late during the boot process, module data are freed > using (see free_bootstrap_pages in bootstrap.c). This might Using vm_page_manage(). -- Richard Braun

Re: Fwd: Hurd shutdown problems

On Mon, Aug 8, 2016 at 9:32 PM, Justus Winter wrote: > Hello, > > "Brent W. Baccala" writes: > > > I don't have to swapoff to have "symptoms". The kernel debugger normally > > shows symbolic names, i.e: > > > > Stopped at machine_idle+0xe: leave > >

Re: Fwd: Hurd shutdown problems

Hello, "Brent W. Baccala" writes: > Further progress trying to track this down: > > I don't have to shutdown the system to have problems. "swapoff /dev/hd0s5" > is enough to cause problems, once enough swap is in use. After a failed > swapoff, I have an extra 98 storeio

Fwd: Hurd shutdown problems

Further progress trying to track this down: I don't have to shutdown the system to have problems. "swapoff /dev/hd0s5" is enough to cause problems, once enough swap is in use. After a failed swapoff, I have an extra 98 storeio processes running! I don't have to swapoff to have "symptoms". The