Re: 9.0 Installing issues
Ede Wolf <[email protected]> Thu, 16 Apr 2020 08:34:18 +0200
| Newsgroups | gmane.os.netbsd.ports.i386 |
|---|---|
| Message-ID | <[email protected]> |
The outputs from the serial console. First the last lines of issue with
the 2nd CPU, using boot -v. From what is visible and comparing it with
dmesg from boot -v -1 would blame IPSec.
But I am aware that this is just, what is visible and may not represent
what is going on in the background:
[ 1.0171127] isa0 at pcib0
[ 1.0171127] lpt0 at isa0 port 0x378-0x37b irq 7
[ 1.0171127] allocated pic ioapic0 type edge pin 7 level 6 to cpu0
slot 5 idt entry 101
[ 1.0171127] com0 at isa0 port 0x3f8-0x3ff irq 4: ns16550a, working fifo
[ 1.0171127] com0: console
[ 1.0171127] allocated pic ioapic0 type edge pin 4 level 8 to cpu0
slot 6 idt entry 129
[ 1.0171127] com1 at isa0 port 0x2f8-0x2ff irq 3: ns16550a, working fifo
[ 1.0171127] allocated pic ioapic0 type edge pin 3 level 8 to cpu0
slot 7 idt entry 130
[ 1.0171127] pckbc0 at isa0 port 0x60-0x64
[ 1.0171127] attimer0 at isa0 port 0x40-0x43
[ 1.0171127] pcppi0 at isa0 port 0x61
[ 1.0171127] midi0 at pcppi0: PC speaker
[ 1.0171127] sysbeep0 at pcppi0
[ 1.0171127] isapnp0 at isa0 port 0x279
[ 1.0171127] fdc0 at isa0 port 0x3f0-0x3f7 irq 6 drq 2
[ 1.0171127] allocated pic ioapic0 type edge pin 6 level 6 to cpu0
slot 8 idt entry 102
[ 1.0171127] attimer0: attached to pcppi0
[ 1.0171127] isapnp0: no ISA Plug 'n Play devices found
[ 1.0171127] timecounter: Timecounter "clockinterrupt" frequency 100
Hz quality 0
[ 1.0171127] timecounter: Timecounter "TSC" frequency 349098640 Hz
quality -100
[ 1.3776742] scsibus0: waiting 2 seconds for devices to settle...
[ 1.4499253] fd0 at fdc0 drive 0: 1.44MB, 80 cyl, 2 head, 18 sec
[ 1.5206351] uhub0 at usb0: NetBSD (0000) UHCI root hub (0000), class
9/0, rev 1.00/1.00, addr 1
[ 1.6246165] uhub0: 2 ports with 2 removable, self powered
<freeze>
And the instant reboot after loading the kernel. To the uninformed eye
this looks like a memory problem?
booting hd0a:netbsd (howto 0x20000)
18024596+522112+845952 [889376+937492+17696]=0x1441d60
[ 1.0000000] BIOS CFG: Model-SubM-Rev: fc-01-00, 0x74<EBDA,KBDINT,RTC,IC2>
[ 1.0000000] panic: uvm_km_bootstrap: could not reserve kernel kmem
[ 1.0000000] cpu0: Begin traceback...
[ 1.0000000]
vpanic(c10434a0,fa018ef4,fa018f44,c085d551,c10434a0,fb3ab000,16800000,0,ffffffff,ffffffff)
at netbsd:vpanic+0x12d
address 0x0 is invalid
address 0x0 is invalid
[ 1.0000000]
snprintf(c10434a0,fb3ab000,16800000,0,ffffffff,ffffffff,0,11727,fa018f1c,3a016000)
at netbsd:snprintf
address 0x0 is invalid
address 0x0 is invalid
[ 1.0000000]
uvm_km_bootstrap(fb3ab000,ffc00000,2,fb3ab000,ffc00000,3a103000,fa018fb0,c0cc6a0f,f9300,0)
at netbsd:uvm_km_bootstrap+0xdb
address 0x0 is invalid
address 0x0 is invalid
[ 1.0000000] uvm_init(f9300,0,0,0,0,0,0,0,0,0) at netbsd:uvm_init+0x5c
address 0x0 is invalid
address 0x0 is invalid
[ 1.0000000] main(0,0,0,0,0,0,0,0,0,0) at netbsd:main+0x4f
[ 1.0000000] cpu0: End traceback...
[ 1.0000000] fatal breakpoint trap in supervisor mode
[ 1.0000000] trap type 1 code 0 eip 0xc0115b04 cs 0x8 eflags 0x202 cr2
0 ilevel 0x8 esp 0xfa018ed8
[ 1.0000000] curlwp 0xc127a500 pid 0 lid 1 lowest kstack 0xfa0172c0
Stopped in pid 0.1 (system) at netbsd:breakpoint+0x4: popl %ebp
db{0}>
Am 15.04.20 um 18:26 schrieb Ede Wolf:
> First of all, "boot -1" did the trick. Now of course I am wondering how
> to get my 2nd CPU back, as even after install, I do have to disable the
> second CPU.
> The next item after fd0 is the USB hub by the way, see dmesg below.
>
> As for the other machine:
>
> I do not have any amd64 USB images, just rechecked, so we can rule out
> that.
> Good news, I do have a serial port, in fact real physical two of them,
> but so far I have not been able to get anything displayed on either.
> Tried with 9600 baud, as I wanted to copy the install messages.
>
> However, this has been before boot(8), so I'll give that a try as well.
> But first I would like to have my 2nd CPU being used again.
>
> Any information I can provide to resolve this?
>
> dmesg, showing some ACPI warnings, but disabling ACPI (boot -2) did not
> help:
>
>
> [ 1.000000] Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002,
> 2003, 2004, 2005,
> [ 1.000000] 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013,
> 2014, 2015, 2016, 2017,
> [ 1.000000] 2018, 2019, 2020 The NetBSD Foundation, Inc. All
> rights reserved.
> [ 1.000000] Copyright (c) 1982, 1986, 1989, 1991, 1993
> [ 1.000000] The Regents of the University of California. All
> rights reserved.
>
> [ 1.000000] NetBSD 9.0 (GENERIC) #0: Fri Feb 14 00:06:28 UTC 2020
> [ 1.000000]
> [email protected]:/usr/src/sys/arch/i386/compile/GENERIC
> [ 1.000000] total memory = 511 MB
> [ 1.000000] avail memory = 482 MB
> [ 1.000000] timecounter: Timecounters tick every 10.000 msec
> [ 1.000000] Kernelized RAIDframe activated
> [ 1.000000] running cgd selftest aes-xts-256 aes-xts-512 done
> [ 1.000000] timecounter: Timecounter "i8254" frequency 1193182 Hz
> quality 100
> [ 1.000003] ( )
> [ 1.000003] mainbus0 (root)
> [ 1.000003] ACPI: RSDP 0x00000000000F7140 000014 (v00 GBT )
> [ 1.000003] ACPI: RSDT 0x000000001FFF3000 00002C (v01 GBT AWRDACPI
> 42302E31 AWRD 00000000)
> [ 1.000003] ACPI: FACP 0x000000001FFF3040 000074 (v01 GBT AWRDACPI
> 42302E31 AWRD 00000000)
> [ 1.000003] ACPI: DSDT 0x000000001FFF30C0 00255D (v01 GBT AWRDACPI
> 00001000 MSFT 01000007)
> [ 1.000003] ACPI: FACS 0x000000001FFF0000 000040
> [ 1.000003] ACPI: APIC 0x000000001FFF5640 00005C (v01 GBT
> 00000000 00000000)
> [ 1.000003] ACPI: 1 ACPI AML tables successfully acquired and loaded
> [ 1.000003] ACPI: BIOS is too old (20000828). Set acpi_force_load to
> use.
> [ 1.000003] ACPI Error: Could not remove SCI handler
> (20190405/evmisc-312)
> [ 1.000003] cpu0 at mainbus0
> [ 1.000003] cpu0: Intel 686-class, 349MHz, id 0x652
> [ 1.000003] cpu0: package 0, core 0, smt 0
> [ 1.000003] pci0 at mainbus0 bus 0: configuration mode 1
> [ 1.000003] pci0: This pci host supports neither MSI nor MSI-X.
> [ 1.000003] pci0: i/o space, memory space enabled, rd/line, rd/mult,
> wr/inv ok
> [ 1.000003] pchb0 at pci0 dev 0 function 0: vendor 8086 product 7190
> (rev. 0x03)
> [ 1.000003] agp0 at pchb0: aperture at 0xd8000000, size 0x4000000
> [ 1.000003] ppb0 at pci0 dev 1 function 0: vendor 8086 product 7191
> (rev. 0x03)
> [ 1.000003] pci1 at ppb0 bus 1
> [ 1.000003] pci1: This pci host supports neither MSI nor MSI-X.
> [ 1.000003] pci1: i/o space, memory space enabled
> [ 1.000003] vga0 at pci1 dev 0 function 0: vendor 1002 product 475a
> (rev. 0x3a)
> [ 1.000003] wsdisplay0 at vga0 kbdmux 1: console (80x25, vt100
> emulation)
> [ 1.000003] wsmux1: connecting to wsdisplay0
> [ 1.000003] drm at vga0 not configured
> [ 1.000003] pcib0 at pci0 dev 7 function 0: vendor 8086 product 7110
> (rev. 0x02)
> [ 1.000003] piixide0 at pci0 dev 7 function 1: Intel 82371AB IDE
> controller (PIIX4) (rev. 0x01)
> [ 1.000003] piixide0: bus-master DMA support present
> [ 1.000003] piixide0: primary channel wired to compatibility mode
> [ 1.000003] piixide0: primary channel interrupting at irq 14
> [ 1.000003] atabus0 at piixide0 channel 0
> [ 1.000003] piixide0: secondary channel wired to compatibility mode
> [ 1.000003] piixide0: secondary channel interrupting at irq 15
> [ 1.000003] atabus1 at piixide0 channel 1
> [ 1.000003] uhci0 at pci0 dev 7 function 2: vendor 8086 product 7112
> (rev. 0x01)
> [ 1.000003] uhci0: interrupting at irq 10
> [ 1.000003] usb0 at uhci0: USB revision 1.0
> [ 1.000003] piixpm0 at pci0 dev 7 function 3: vendor 8086 product
> 7113 (rev. 0x02)
> [ 1.000003] timecounter: Timecounter "piixpm0" frequency 3579545 Hz
> quality 900
> [ 1.008917] piixpm0: 24-bit timer
> [ 1.008917] piixpm0: polling
> [ 1.008917] iic0 at piixpm0 port 0: I2C bus
> [ 1.008917] fxp0 at pci0 dev 10 function 0: i82550 Ethernet (rev. 0x0c)
> [ 1.008917] fxp0: interrupting at irq 12
> [ 1.008917] fxp0: Ethernet address 00:02:b3:29:91:b6
> [ 1.008917] inphy0 at fxp0 phy 1: i82555 10/100 media interface, rev. 4
> [ 1.008917] inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX,
> auto
> [ 1.008917] ahc1 at pci0 dev 12 function 0: Adaptec 2944 Ultra SCSI
> adapter
> [ 1.008917] ahc1: interrupting at irq 11
> [ 1.008917] ahc1: aic7880: Ultra Wide Channel A, SCSI Id=7, 16/253 SCBs
> [ 1.008917] scsibus0 at ahc1: 16 targets, 8 luns per target
> [ 1.008917] isa0 at pcib0
> [ 1.008917] lpt0 at isa0 port 0x378-0x37b irq 7
> [ 1.008917] com0 at isa0 port 0x3f8-0x3ff irq 4: ns16550a, working fifo
> [ 1.008917] com1 at isa0 port 0x2f8-0x2ff irq 3: ns16550a, working fifo
> [ 1.008917] pckbc0 at isa0 port 0x60-0x64
> [ 1.008917] attimer0 at isa0 port 0x40-0x43
> [ 1.008917] pcppi0 at isa0 port 0x61
> [ 1.008917] midi0 at pcppi0: PC speaker
> [ 1.008917] sysbeep0 at pcppi0
> [ 1.008917] isapnp0 at isa0 port 0x279
> [ 1.008917] fdc0 at isa0 port 0x3f0-0x3f7 irq 6 drq 2
> [ 1.008917] attimer0: attached to pcppi0
> [ 1.008917] isapnp0: no ISA Plug 'n Play devices found
> [ 1.008917] timecounter: Timecounter "clockinterrupt" frequency 100
> Hz quality 0
> [ 1.399270] scsibus0: waiting 2 seconds for devices to settle...
> [ 1.399270] fd0 at fdc0 drive 0: 1.44MB, 80 cyl, 2 head, 18 sec
> [ 1.439264] uhub0 at usb0: NetBSD (0000) UHCI root hub (0000), class
> 9/0, rev 1.00/1.00, addr 1
> [ 1.439264] uhub0: 2 ports with 2 removable, self powered
> [ 1.439264] IPsec: Initialized Security Association Processing.
> [ 3.939302] uhidev0 at uhub0 port 2 configuration 1 interface 0
> [ 3.939302] uhidev0: Microsoft (0x45e)
> Natural<2147483586><2147483566> Ergonomic Keyboard 4000 (0xdb), rev
> 2.00/1.73, addr 2, iclass 3/1
> [ 3.959302] ukbd0 at uhidev0
> [ 4.369307] wskbd0 at ukbd0: console keyboard, using wsdisplay0
> [ 4.369307] uhidev1 at uhub0 port 2 configuration 1 interface 1
> [ 4.369307] uhidev1: Microsoft (0x45e)
> Natural<2147483586><2147483566> Ergonomic Keyboard 4000 (0xdb), rev
> 2.00/1.73, addr 2, iclass 3/0
> [ 4.389309] uhidev1: 1 report ids
> [ 4.389309] uhid0 at uhidev1 reportid 1: input=7, output=0, feature=0
> [ 4.429308] wd0 at atabus0 drive 0
> [ 4.429308] wd0: <SAMSUNG SV3012H>
> [ 4.429308] wd0: drive supports 16-sector PIO transfers, LBA addressing
> [ 4.429308] wd0: 28667 MB, 58246 cyl, 16 head, 63 sec, 512
> bytes/sect x 58711968 sectors
> [ 4.529311] wd0: 32-bit data port
> [ 4.529311] wd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA
> mode 5 (Ultra/100)
> [ 4.529311] wd0(piixide0:0:0): using PIO mode 4, Ultra-DMA mode 2
> (Ultra/33) (using DMA)
> [ 4.529311] atapibus0 at atabus1: 2 targets
> [ 4.539311] cd0 at atapibus0 drive 0: <TSSTcorpDVD-ROM SH-D162D, ,
> SB00> cdrom removable
> [ 4.559309] cd0: 32-bit data port
> [ 4.559309] cd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA
> mode 2 (Ultra/33)
> [ 4.559309] cd0(piixide0:1:0): using PIO mode 4, Ultra-DMA mode 2
> (Ultra/33) (using DMA)
> [ 7.379352] boot device: wd0
> [ 7.379352] root on wd0a dumps on wd0b
> [ 7.409356] root file system type: ffs
> [ 7.419356] kern.module.path=/stand/i386/9.0/modules
> [ 27.509669] wsdisplay0: screen 1 added (80x25, vt100 emulation)
> [ 27.519672] wsdisplay0: screen 2 added (80x25, vt100 emulation)
> [ 27.529674] wsdisplay0: screen 3 added (80x25, vt100 emulation)
> [ 27.539673] wsdisplay0: screen 4 added (80x25, vt100 emulation)
>
>
>
>
>
>
> Am 15.04.20 um 17:36 schrieb Mouse:
>>> Meanwhile I gave another machine a try, slightly newer, this time
>>> booting from an USB stick, and right after the kernel has loaded (I
>>> believe those magic numbers at the very start with the rotating pipes
>>> indicate the kernel)
>>
>> Generally, yes.
>>
>>> the system reboots. Before any further boot messages appear.
>>
>> This can indicate that you're actually trying to boot NetBSD/amd64 on a
>> CPU that does not have 64-bit support. It can also indicate various
>> other things, though; I mention this just in case you managed to pick
>> up the amd64 version by mistake. (It would be nice if this were
>> something NetBSD/amd64 could detect and print a message about, but I
>> don't know enough about the relevant details to know how feasible that
>> would be.)
>>
>> One note - there could be more messages printed, followed closely
>> enough by the reset that you don't get a chance to see them. One thing
>> that can help in that case, if the machine has a real serial port, is
>> to tell the booter to switch to the serial port for console. Then the
>> reset shouldn't lose more than, at most, the last character or two of
>> console output. (In my experience, this is "consdev com0" or the like
>> at the > prompt. If you just get the booter banner back on video
>> console, the machine does not have a serial port, or at least not in
>> the form the booter understands.)
>>
>> /~\ The ASCII Mouse
>> \ / Ribbon Campaign
>> X Against HTML [email protected]
>> / \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
>>
>