On 9/6/07, Junichi Uekawa <[EMAIL PROTECTED]> wrote: > > When running on amd64 architecture and emulating amd64 architecture: > > Looks like initrd is br0ken to me. Please give specific versions.
on i386: $ sudo apt-get install linux-image-2.6.22-2-amd64 $ cat pbuilderrc-amd64.config KERNEL_IMAGE=/boot/vmlinuz-2.6.22-2-amd64 INITRD=/boot/initrd.img-2.6.22-2-amd64 MIRRORSITE=http://ftp.cz.debian.org/debian ARCH=amd64 BASEPATH=/home/ondra/debian/base-amd64.qemu MEMORY_MEGS=64 $ sudo qemubuilder --configfile pbuilderrc-amd64.config --create [...] Freeing unused kernel memory: 296k freed Loading, please wait... Begin: Loading essential drivers... ... Done. Begin: Running /scripts/init-premount ... Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx PIIX3: IDE controller at PCI slot 0000:00:01.1 PIIX3: chipset revision 0 PIIX3: not 100% native mode: will probe irqs later ide0: BM-DMA at 0xc000-0xc007, BIOS settings: hda:pio, hdb:pio ide1: BM-DMA at 0xc008-0xc00f, BIOS settings: hdc:pio, hdd:pio ne2k-pci.c:v1.03 9/22/2003 D. Becker/P. Gortmaker hda: QEMU HARDDISK, ATA DISK drive FDC 0 is a S82078B hdb: QEMU HARDDISK, ATA DISK drive ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 hdc: QEMU CD-ROM, ATAPI CD/DVD-ROM drive ide1 at 0x170-0x177,0x376 on irq 15 ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 10 ACPI: PCI Interrupt 0000:00:03.0[A] -> Link [LNKC] -> GSI 10 (level, low) -> IRQ 10 eth0: RealTek RTL-8029 found at 0xc100, IRQ 10, 52:54:00:12:34:56. SCSI subsystem initialized hda: max request size: 512KiB hda: 6293504 sectors (3222 MB) w/256KiB Cache, CHS=6243/255/63, (U)DMA hda: cache flushes supported hda: hdb: max request size: 512KiB hdb: 2099200 sectors (1074 MB) w/256KiB Cache, CHS=2082/255/63, (U)DMA hdb: cache flushes supported hdb: unknown partition table hdc: ATAPI 4X CD-ROM drive, 512kB Cache, (U)DMA Uniform CD-ROM driver Revision: 3.20 Done. Begin: Mounting root file system... ... Begin: Running /scripts/local-top ... Done. [...] works nice. The exact same procedure on amd64 architecture (using exactly the same commands) produces the output in my bug report: [...] Freeing unused kernel memory: 296k freed SCSI subsystem initialized /bin/cat: /sys/block/sda/dev: No such file or directory Waiting 1 seconds for /sys/block/sda/dev to show up /bin/cat: /sys/block/sda/dev: No such file or directory Waiting 2 seconds for /sys/block/sda/dev to show up /bin/cat: /sys/block/sda/dev: No such file or directory Waiting 4 seconds for /sys/block/sda/dev to show up /bin/cat: /sys/block/sda/dev: No such file or directory Waiting 8 seconds for /sys/block/sda/dev to show up /bin/cat: /sys/block/sda/dev: No such file or directory Waiting 16 seconds for /sys/block/sda/dev to show up /bin/cat: /sys/block/sda/dev: No such file or directory Device /sys/block/sda/dev seems to be down. /bin/mknod: missing operand after `b' Special files require major and minor device numbers. Try `/bin/mknod --help' for more information. /bin/cat: /sys/block/sda/sda7/dev: No such file or directory Waiting 1 seconds for /sys/block/sda/sda7/dev to show up /bin/cat: /sys/block/sda/sda7/dev: No such file or directory Waiting 2 seconds for /sys/block/sda/sda7/dev to show up /bin/cat: /sys/block/sda/sda7/dev: No such file or directory Waiting 4 seconds for /sys/block/sda/sda7/dev to show up /bin/cat: /sys/block/sda/sda7/dev: No such file or directory Waiting 8 seconds for /sys/block/sda/sda7/dev to show up /bin/cat: /sys/block/sda/sda7/dev: No such file or directory Waiting 16 seconds for /sys/block/sda/sda7/dev to show up /bin/cat: /sys/block/sda/sda7/dev: No such file or directory Device /sys/block/sda/sda7/dev seems to be down. /bin/mknod: missing operand after `b' Special files require major and minor device numbers. Try `/bin/mknod --help' for more information. SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled SGI XFS Quota Management subsystem mount: you must specify the filesystem type Switching root ... /usr/lib/yaird/exec/run_init: current directory on the same filesystem as the root: Success Kernel panic - not syncing: Attempted to kill init! [...] The problem seems to be in that the kernel in qemu is for some reason not able to load the initrd module. The same kernel panic with the same output happens to me for the running kernel (2.6.16-2-amd64-k8) as well on amd64, and this kernel and initrd is definitely fine, since I am running on it. Please tell me if some other information would be useful. Ondrej -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
