Re: kern/44069: NetBSD-current hangs during boot under Linux kvm emulation

[Andreas Gustafsson <gson%gson.org@localhost>]

The following reply was made to PR kern/44069; it has been noted by GNATS.

From: Andreas Gustafsson <gson%gson.org@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: kern-bug-people%netbsd.org@localhost,
    gnats-admin%netbsd.org@localhost,
    netbsd-bugs%netbsd.org@localhost,
    gson%gson.org@localhost (Andreas Gustafsson)
Subject: Re: kern/44069: NetBSD-current hangs during boot under Linux kvm 
emulation
Date: Mon, 8 Nov 2010 21:31:22 +0200

 Jukka,
 
 Thanks for taking the time to analyze this issue.
 
 >  > The problem was introduced, or perhaps
 >  > exposed, by following commit by toshii:
 [...]
 >  Interestingly, the commit message tells the exact opposite story:
 >  
 >  "revision 1.79
 >   date: 2009/11/04 14:39:17;  author: toshii;  state: Exp;  lines: +3 -3
 >  
 >   Don't return an error if the _PIC method isn't found.
 >   It's an optional method and not found in kvm/qemu.
 >   ----------------------------"
 
 That's not quite the opposite story - it's consistent with the problem
 being exposed by rather than caused by toshii's commit.  For example,
 the hang could happen later in the function, in code that was never
 executed under KVM before the commit, because the function returned
 prematurely when _PIC wasn't found.
 
 >  Has NetBSD worked on KVM before? 
 
 As I said in the bug report, versions from before the commit do work,
 or at the very least they boot.  Here's a summary of the source dates
 I have tested:
 
    2009.08.23.20.57.40 ok
    2009.10.25.23.42.58 ok
    2009.10.29.14.32.18 ok
    2009.11.02.17.17.34 ok
    2009.11.04.13.29.45 ok
    2009.11.04.13.32.39 ok
    2009.11.04.14.39.17 fails
    2009.11.04.15.37.39 fails
    2009.11.04.18.11.11 fails
    2009.11.06.15.41.58 fails
    2009.11.07.19.54.17 fails
    2009.11.15.23.29.18 fails
    2009.11.23.05.01.12 fails
    2009.12.31.15.42.46 fails
    2010.04.25.22.50.11 fails
    2010.07.07.11.42.18 fails
 
 > Can you post the full dmesg?
 
 Here's the console output from the 2009.11.04.13.32.39 build booting in kvm.
 
 Loading /stand/i386/5.99.21/modules/ffs/ffs.kmod |/-\|/-\|/-\|/-\|/-\|/-\|/ 
 Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005,
     2006, 2007, 2008, 2009
     The NetBSD Foundation, Inc.  All rights reserved.
 Copyright (c) 1982, 1986, 1989, 1991, 1993
     The Regents of the University of California.  All rights reserved.
 
 NetBSD 5.99.21 (GENERIC) #0: Mon Nov  8 19:13:08  2010
        
gson@guesthouse:/bracket/work/2009.11.04.13.32.39/obj/sys/arch/i386/compile/GENERIC
 total memory = 383 MB
 avail memory = 366 MB
 mainbus0 (root)
 cpu0 at mainbus0 apid 0: Intel 686-class, 2400MHz, id 0x623
 ioapic0 at mainbus0 apid 1
 acpi0 at mainbus0: Intel ACPICA 20090730
 pckbc1 at acpi0 (KBD, PNP0303) (kbd port): io 0x60,0x64 irq 1
 pckbc2 at acpi0 (MOU, PNP0F13) (aux port): irq 12
 FDC0 (PNP0700) at acpi0 not configured
 LPT (PNP0400) at acpi0 not configured
 COM1 (PNP0501) at acpi0 not configured
 hpet0 at acpi0 (HPET, PNP0103-0): mem 0xfed00000-0xfed003ff
 apm0 at acpi0: Power Management spec V1.2
 pckbd0 at pckbc1 (kbd slot)
 pckbc1: using irq 1 for kbd slot
 wskbd0 at pckbd0 mux 1
 pms0 at pckbc1 (aux slot)
 pckbc1: using irq 12 for aux slot
 wsmouse0 at pms0 mux 0
 pci0 at mainbus0 bus 0: configuration mode 1
 pchb0 at pci0 dev 0 function 0: vendor 0x8086 product 0x1237 (rev. 0x02)
 pcib0 at pci0 dev 1 function 0: vendor 0x8086 product 0x7000 (rev. 0x00)
 piixide0 at pci0 dev 1 function 1: Intel 82371SB IDE Interface (PIIX3) (rev. 
0x00)
 piixide0: primary channel interrupting at irq 14
 atabus0 at piixide0 channel 0
 piixide0: secondary channel interrupting at irq 15
 atabus1 at piixide0 channel 1
 piixpm0 at pci0 dev 1 function 3
 piixpm0: vendor 0x8086 product 0x7113 (rev. 0x03)
 piixpm0: 24-bit timer
 piixpm0: interrupting at irq 9
 iic0 at piixpm0: I2C bus
 vga1 at pci0 dev 2 function 0: vendor 0x1013 product 0x00b8 (rev. 0x00)
 wsdisplay0 at vga1 kbdmux 1
 drm at vga1 not configured
 re0 at pci0 dev 3 function 0: RealTek 8139C+ 10/100BaseTX (rev. 0x20)
 re0: interrupting at irq 11
 re0: Ethernet address 52:54:00:12:34:56
 rlphy0 at re0 phy 0: Realtek internal PHY
 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
 isa0 at pcib0
 lpt0 at isa0 port 0x378-0x37b irq 7
 com0 at isa0 port 0x3f8-0x3ff irq 4: ns16550a, working fifo
 com0: console
 attimer0 at isa0 port 0x40-0x43
 pcppi0 at isa0 port 0x61
 midi0 at pcppi0: PC speaker
 sysbeep0 at pcppi0
 isapnp0 at isa0 port 0x279
 npx0 at isa0 port 0xf0-0xff
 fdc0 at isa0 port 0x3f0-0x3f7 irq 6 drq 2
 attimer0: attached to pcppi0
 wd0 at atabus0 drive 0: <QEMU HARDDISK>
 wd0: 512 MB, 1040 cyl, 16 head, 63 sec, 512 bytes/sect x 1048576 sectors
 atapibus0 at atabus1: 2 targets
 cd0 at atapibus0 drive 0: <QEMU DVD-ROM, QM00003, 0.12.3> cdrom removable
 Kernelized RAIDframe activated
 pad0: outputs: 44100Hz, 16-bit, stereo
 audio0 at pad0: half duplex, playback, capture
 boot device: wd0
 root on wd0a dumps on wd0b
 root file system type: ffs
 Mon Nov  8 19:23:50 UTC 2010
 Starting root file system check:
 /dev/rwd0a: file system is clean; not checking
 swapctl: setting dump device to /dev/wd0b
 swapctl: adding /dev/wd0b as swap device at priority 0
 Starting file system checks:
 /dev/rwd0a: file system is mounted read-write on /; not checking
 Setting tty flags.
 Setting sysctl variables:
 ddb.onpanic: 1 -> 0
 Starting network.
 /etc/rc: WARNING: $hostname not set.
 IPv6 mode: host
 Configuring network interfaces:.
 Adding interface aliases:.
 Building databases: dev, utmp, utmpx, services done
 Starting syslogd.
 Mounting all filesystems...
 Clearing temporary files.
 Creating a.out runtime link editor directory cache.
 Checking quotas: done.
 swapctl: setting dump device to /dev/wd0b
 Starting virecover.
 Checking for core dump...
 savecore - - - no core dump
 Starting local daemons:.
 Updating motd.
 postfix: rebuilding /etc/mail/aliases (missing /etc/mail/aliases.db)
 newaliases: warning: valid_hostname: empty hostname
 newaliases: fatal: unable to use my own hostname
 Nov  8 19:23:54  postfix/sendmail[316]: fatal: unable to use my own hostname
 /etc/rc.d/postfix reported failure status 1
 Starting inetd.
 Starting cron.
 The following components reported failures:
     /etc/rc.d/postfix
 See /var/run/rc.log for more information.
 Mon Nov  8 19:23:54 UTC 2010
 
 NetBSD/i386 (Amnesiac) (console)
 
 login:
 
 -- 
 Andreas Gustafsson, gson%gson.org@localhost