Date: Fri, 31 Oct 2003 23:57:42 +0100 From: Adriaan de Groot <adridg@cs.kun.nl> To: amd64@freebsd.org Subject: fyi: bootstrapped Message-ID: <200310312355.30349.adridg@cs.kun.nl>
next in thread | raw e-mail | index | archive | help
Jaja, lots of noise on the list because of me. Here's my dmesg from a freshly
booted machine (Asus K8V Deluxe), with 5-CURRENT cvsupped this evening, with
the GENERIC config edited only to change the machine name. There's a couple
of things that worry me in the dmesg output, which I've marked with ### in
the output.
ACPI debug layer 0x0 debug level 0x0
Copyright (c) 1992-2003 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD 5.1-CURRENT #0: Sat Nov 1 05:56:17 GMT 2003
root@beans.ebn.kun.nl:/usr/src/sys/amd64/compile/BEANS
Preloaded elf kernel "/boot/kernel/kernel" at 0xffffffff8090f000.
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: AMD Athlon(tm) 64 Processor 3200+ (2002.57-MHz K8-class CPU)
Origin = "AuthenticAMD" Id = 0xf48 Stepping = 8
Features=0x78bfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2>
AMD Features=0xe0500000<NX,MMX+,LM,3DNow!+,3DNow!>
real memory = 1072889856 (1023 MB)
avail memory = 1008889856 (962 MB)
Pentium Pro MTRR support enabled
acpi0: <A M I OEMXSDT > on motherboard
acpi0: Power Button (fixed)
Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
pci0: <ACPI PCI bus> on pcib0
pcib1: <ACPI PCI-PCI bridge> at device 1.0 on pci0
pcib1: could not get PCI interrupt routing table for \\_SB_.PCI0.P0P1 -
AE_NOT_FOUND
### This was around a while ago already. it was worrying then, said, um ..
pci1: <ACPI PCI bus> on pcib1
atapci0: <Promise PDC20378 SATA150 controller> port
0xbc00-0xbc7f,0xcc00-0xcc0f,0xdc00-0xdc3f mem
0xcf800000-0xcf81ffff,0xcf900000-0xcf900fff irq 11 at device 8.0 on pci0
atapci0: [MPSAFE]
ata2: at 0xcf900000 on atapci0
ata2: [MPSAFE]
ata3: at 0xcf900000 on atapci0
ata3: [MPSAFE]
ata4: at 0xcf900000 on atapci0
ata4: [MPSAFE]
skc0: <3Com 3C940 Gigabit Ethernet> port 0xec00-0xecff mem
0xcfa00000-0xcfa03fff irq 10 at device 10.0 on pci0
skc0: 3Com Gigabit LOM (3C940)
sk0: <Marvell Semiconductor, Inc. Yukon> on skc0
sk0: Ethernet address: 00:0c:6e:b3:3f:38
malloc() of "512" with the following non-sleepable locks held:
exclusive sleep mutex skc0 (network driver) r = 0 (0xffffff0000bcba70) locked
@ pci/if_sk.c:1292
miibus0: <MII bus> on sk0
e1000phy0: <Marvell 88E1000 Gigabit PHY> on miibus0
lock order reversal
1st 0xffffff0000bcba70 skc0 (network driver) @ pci/if_sk.c:651
2nd 0xffffffff8077d540 kernel environment (kernel environment) @
kern/kern_environment.c:288
Stack backtrace:
e1000phy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX-FDX,
auto
### Looks like spinlocks with a potential problem
xl0: <3Com 3c905C-TX Fast Etherlink XL> port 0xb000-0xb07f mem
0xcfc00000-0xcfc0007f irq 10 at device 12.0 on pci0
xl0: Ethernet address: 00:01:02:b3:de:a6
miibus1: <MII bus> on xl0
xlphy0: <3c905C 10/100 internal PHY> on miibus1
xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
pci0: <display, VGA> at device 13.0 (no driver attached)
atapci1: <VIA 8237 SATA150 controller> port
0xd000-0xd0ff,0xd400-0xd40f,0xd800-0xd803,0xe000-0xe007,0xe400-0xe403,0xe800-0xe807
irq 10 at device 15.0 on pci0
atapci1: [MPSAFE]
### Impressive. I had it disabled in the BIOS.
ata5: at 0xe800 on atapci1
ata5: [MPSAFE]
ata6: at 0xe000 on atapci1
ata6: [MPSAFE]
atapci2: <VIA 8237 UDMA133 controller> port 0xfc00-0xfc0f at device 15.1 on
pci0
ata0: at 0x1f0 irq 14 on atapci2
ata0: [MPSAFE]
ata1: at 0x170 irq 15 on atapci2
ata1: [MPSAFE]
uhci0: <VIA 83C572 USB controller> port 0xb400-0xb41f irq 5 at device 16.0 on
pci0
usb0: <VIA 83C572 USB controller> on uhci0
usb0: USB revision 1.0
uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
uhub0: port error, restarting port 1
uhub0: port error, giving up port 1
### All my ports do this, even the ones with devices attached that
### subsequently function just fine (like the keyboard and mouse).
### Also, I have the orts set to USB 2.0, I'd expect that to be reported, no?
ums0: Logitech USB Mouse, rev 1.10/6.20, addr 2, iclass 3/1
ums0: 3 buttons and Z dir.
uhub0: port error, restarting port 2
uhub0: port error, giving up port 2
ukbd0: Logitech Logitech USB Keyboard, rev 1.10/15.00, addr 3, iclass 3/1
kbd0 at ukbd0
uhci1: <VIA 83C572 USB controller> port 0xb800-0xb81f irq 5 at device 16.1 on
pci0
usb1: <VIA 83C572 USB controller> on uhci1
usb1: USB revision 1.0
uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub1: 2 ports with 2 removable, self powered
uhub1: port error, restarting port 1
uhub1: port error, giving up port 1
uhub1: port error, restarting port 2
uhub1: port error, giving up port 2
uhci2: <VIA 83C572 USB controller> port 0xc000-0xc01f irq 10 at device 16.2 on
pci0
usb2: <VIA 83C572 USB controller> on uhci2
usb2: USB revision 1.0
uhub2: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub2: 2 ports with 2 removable, self powered
uhub2: port error, restarting port 1
uhub2: port error, giving up port 1
uhub2: port error, restarting port 2
uhub2: port error, giving up port 2
uhci3: <VIA 83C572 USB controller> port 0xc400-0xc41f irq 10 at device 16.3 on
pci0
usb3: <VIA 83C572 USB controller> on uhci3
usb3: USB revision 1.0
uhub3: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub3: 2 ports with 2 removable, self powered
uhub3: port error, restarting port 1
uhub3: port error, giving up port 1
uhub3: port error, restarting port 2
uhub3: port error, giving up port 2
pci0: <serial bus, USB> at device 16.4 (no driver attached)
isab0: <PCI-ISA bridge> at device 17.0 on pci0
isa0: <ISA bus> on isab0
pcm0: <VIA VT8233X> port 0xc800-0xc8ff irq 11 at device 17.5 on pci0
pcm0: <Analog Devices AD1980 AC97 Codec>
fdc0: <Enhanced floppy controller (i82077, NE72065 or clone)> port
0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0
fdc0: FIFO enabled, 8 bytes threshold
ppc0 port 0x378-0x37f irq 7 on acpi0
ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode
ppbus0: <Parallel port bus> on ppc0
plip0: <PLIP network interface> on ppbus0
lpt0: <Printer> on ppbus0
lpt0: Interrupt-driven port
ppi0: <Parallel I/O> on ppbus0
sio0: configured irq 3 not in bitmap of probed irqs 0
sio0: port may not be enabled
sio0 port 0x2f8-0x2ff irq 3 on acpi0
sio0: type 16550A
sio1: configured irq 4 not in bitmap of probed irqs 0
sio1: port may not be enabled
sio1 port 0x3f8-0x3ff irq 4 on acpi0
sio1: type 16550A
acpi_button0: <Power Button> on acpi0
acpi_button1: <Sleep Button> on acpi0
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0
npx0: <math processor> on motherboard
npx0: INT 16 interface
orm0: <Option ROMs> at iomem 0xc8000-0xc87ff,0xc0000-0xc7fff on isa0
atkbdc0: <Keyboard controller (i8042)> at port 0x64,0x60 on isa0
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
Timecounter "TSC" frequency 2002570881 Hz quality 800
Timecounters tick every 10.000 msec
GEOM: create disk ad0 dp=0xffffff003c8662c0
ad0: 2014MB <WDC AC22100L> [4092/16/63] at ata0-master UDMA33
acd0: CDROM <OEM CD-ROM F563E> at ata1-slave PIO4
GEOM: create disk ad4 dp=0xffffff003c5256c0
ad4: 117246MB <Maxtor 6Y120M0> [238216/16/63] at ata2-master UDMA133
Mounting root from ufs:/dev/ad0s1a
WARNING: / was not properly dismounted
WARNING: /usr was not properly dismounted
/usr: mount pending error: blocks 928 files 1
### This was just the reboot after buildkernel hanging and giving
### up on two buffers. Not something to worry about now with new
### kernel and world.
Buildworld took _way_ longer than the promised 14 minutes, but that's probably
just what you get when you have /usr on an ATA33 drive and /usr/src on a
faster one.
For my next goal, KDE-on-CURRENT-on-amd64, fetching lots of ports is needed,
lots of downloads to go .. but in the meantime, is there anything useful I
can do for you? You in the sense of the amd64 list, that is. I can push the
system as a typical desktop user would (which isn't that hard), muck with the
stuff I'm worried about above, or mess with the ed driver (because I've got
one). The latter two will probably generate more questions on my part, I
think. Aside from attending the Device Driver talk at EuroBSDcon last year,
I've not done much of this kind of stuff before.
Hm, 1290u 1230s 44:59 before buildworld craps out in ipfstat. Remind me again
how to resume broken buildworlds?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200310312355.30349.adridg>