Bug#402091: [Pbuilder-maint] Bug#402091: pbuilder-uml: create fails when installing linux-kernel-headers

[Vagrant Cascadian]

On Fri, Dec 08, 2006 at 12:06:13PM -0800, vagrant+bugs at freegeek.org wrote:
> On Fri, Dec 08, 2006 at 10:25:35AM +0100, Mattia Dongili wrote:
> > On Thu, Dec 07, 2006 at 03:30:49PM -0800, Vagrant Cascadian wrote:
> > > i can't, for the life of me, get "pbuilder-user-mode-linux create" to
> > > work.
> > > 
> > > it gets as far as installing the bae system with rootstrap, but then
> > > when it goes to apt-get packages, it always fails on
> > > linux-kernel-headers:
> > 
> > One thing to try immediatly anyway would be to increase the mem=
> > parameter in /etc/rootstrap/rootstrap.conf
> 
> ok, will try that.

ok, well, this didn't help at all. still kernel panic'd when apt-getting
linux-kernel-headers.

what i did notice was that during the "apt-get" phase of
"pbuilder-user-mode-linux create" it doesn't respect the mem setting
from rootstrap.conf, as i set it to 96M in rootstrap.conf, which worked
during the "debootstrap" phase, but when booting into the "apt-get"
phase, it used mem=128M as a kernel commandline argument. so, i suspect
it originally used mem=128M anyways.
  
> > Otherwise can you get rootstrap alone to create a useable filesystem
> > image?
> 
> yes, calling rootstrap manually works fine- though i haven't booted to
> that image and then tried to install additional packages.

tried that, i was able to apt-get update and apt-get upgrade using my
local mirror.  when i added http://debian.oregonstate.edu/debian to
souces.list and tried an apt-get update, i got a different kernel panic:

(using: linux mem=128M ubd0=uml-image-test eth0=slirp,,slirp-fullbolt)

Kernel panic - not syncing: Kernel mode signal 7

EIP: 0073:[<402afd3e>] CPU: 0 Not tainted ESP: 007b:7fa96118 EFLAGS:
00200246
    Not tainted
    EAX: ffffffda EBX: 00000007 ECX: 40326000 EDX: 006a2efd
    ESI: 40326000 EDI: 006a2efd EBP: 7fa96148 DS: 007b ES: 007b
    0ea974fc:  [<080701b4>] show_regs+0xb4/0xb9
    0ea97528:  [<0805e6a3>] panic_exit+0x25/0x3f
    0ea9753c:  [<080806b8>] notifier_call_chain+0x1d/0x37
    0ea9755c:  [<08080742>] atomic_notifier_call_chain+0x11/0x13
    0ea97570:  [<08074a72>] panic+0x52/0xd3
    0ea97590:  [<0805e093>] relay_signal+0x30/0x69
    0ea975b0:  [<0806dd5a>] sig_handler_common_skas+0xc6/0xec
    0ea975d8:  [<0806ad32>] sig_handler+0x33/0x41
    0ea975ec:  [<b7eec420>] 0xb7eec420
    0ea978dc:  [<0805f14f>] do_op_one_page+0x3b/0x40
    0ea978f0:  [<0805f20f>] do_buffer_op+0xbb/0x12b
    0ea97930:  [<0806bc88>] setjmp_wrapper+0x34/0x3d
    0ea979e4:  [<0805f2a6>] buffer_op+0x27/0x52
    0ea97a18:  [<0805f36f>] copy_from_user_skas+0x76/0x84
    0ea97a40:  [<08092d28>] generic_file_buffered_write+0x2cd/0x559
    0ea97ad8:  [<08093319>] __generic_file_aio_write_nolock+0x365/0x3c1
    0ea97b40:  [<08093479>] __generic_file_write_nolock+0x84/0x9a
    0ea97bd8:  [<08093632>] generic_file_write+0x3e/0xa9
    0ea97c10:  [<080aa10b>] vfs_write+0xa7/0x150
    0ea97c3c:  [<080aa253>] sys_write+0x3c/0x63
    0ea97c68:  [<0805eeaf>] handle_syscall+0x87/0xa0
    0ea97cb4:  [<0806d812>] userspace+0x1fc/0x240
    0ea97cfc:  [<0805ebdb>] fork_handler+0x97/0x9f
    0ea97d1c:  [<b7eec420>] 0xb7eec420

     slirp_close: process 5148 has not exited

live well,
  vagrant