missing disk device under 9-STABLE
Hi, I attempted an upgrade last night from an old 8-STABLE (25 Apr 2011) to 9-STABLE and ran into a problem where a disk apparently wasn't detected. I'm of course aware of the ATA/CAM changes, but I haven't found anything that quite explains what's happening here. I've attached dmesg output from the 8-STABLE and 9-STABLE kernels as well as the results of 'ls -l /dev/ad*' and 'zpool status' under both kernels. ZFS seems to have figured out what to do about its ad4p3 member (switching to a gptid device), but since only ada0 is detected during boot, it can't complete the pool. The weird thing is, though, that the other disk was actually detected on one reboot to the 9.0 kernel, ZFS was happy, etc. I haven't been able to reproduce it, though. Due to these problems, I haven't upgraded userland yet and am of course sticking with the 8-STABLE kernel, but I can boot into the 9-STABLE kernel at will if anyone needs more information. Thanks for any help, Jeff pool: z0 state: ONLINE scrub: none requested config: NAMESTATE READ WRITE CKSUM z0 ONLINE 0 0 0 mirrorONLINE 0 0 0 ad4p3 ONLINE 0 0 0 ad6p3 ONLINE 0 0 0 errors: No known data errors # ls -l /dev/ad* lrwxr-xr-x 1 root wheel4 Mar 3 13:36 /dev/ad4 - ada0 lrwxr-xr-x 1 root wheel6 Mar 3 13:36 /dev/ad4p1 - ada0p1 lrwxr-xr-x 1 root wheel6 Mar 3 13:36 /dev/ad4p2 - ada0p2 lrwxr-xr-x 1 root wheel6 Mar 3 13:36 /dev/ad4p3 - ada0p3 crw-r- 1 root operator0, 118 Mar 3 13:36 /dev/ada0 crw-r- 1 root operator0, 120 Mar 3 13:36 /dev/ada0p1 crw-r- 1 root operator0, 122 Mar 3 13:36 /dev/ada0p2 crw-r- 1 root operator0, 124 Mar 3 13:36 /dev/ada0p3 # zpool status pool: z0 state: DEGRADED status: One or more devices could not be opened. Sufficient replicas exist for the pool to continue functioning in a degraded state. action: Attach the missing device and online it using 'zpool online'. see: http://www.sun.com/msg/ZFS-8000-2Q scrub: none requested config: NAMESTATE READ WRITE CKSUM z0 DEGRADED 0 0 0 mirrorDEGRADED 0 0 0 gptid/96a50b26-9de7-11de-9693-00261882fc65 ONLINE 0 0 0 ad6p3 UNAVAIL 0 0 0 cannot open errors: No known data errors Copyright (c) 1992-2011 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 is a registered trademark of The FreeBSD Foundation. FreeBSD 8.2-STABLE #0 r221047: Mon Apr 25 23:03:11 EDT 2011 r...@crow.mr-happy.com:/usr/obj/usr/src/sys/GENERIC amd64 Timecounter i8254 frequency 1193182 Hz quality 0 CPU: AMD Phenom(tm) II X4 965 Processor (3411.64-MHz K8-class CPU) Origin = AuthenticAMD Id = 0x100f42 Family = 10 Model = 4 Stepping = 2 Features=0x178bfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT Features2=0x802009SSE3,MON,CX16,POPCNT AMD Features=0xee500800SYSCALL,NX,MMX+,FFXSR,Page1GB,RDTSCP,LM,3DNow!+,3DNow! AMD Features2=0x37ffLAHF,CMP,SVM,ExtAPIC,CR8,ABM,SSE4A,MAS,Prefetch,OSVW,IBS,SKINIT,WDT TSC: P-state invariant real memory = 8589934592 (8192 MB) avail memory = 7980056576 (7610 MB) ACPI APIC Table: 060509 APIC1006 FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs FreeBSD/SMP: 1 package(s) x 4 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 2 cpu3 (AP): APIC ID: 3 ACPI Warning: Optional field Pm2ControlBlock has zero address or length: 0x/0x1 (20101013/tbfadt-655) ioapic0 Version 2.1 irqs 0-23 on motherboard kbd1 at kbdmux0 acpi0: 060509 RSDT1006 on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: reservation of fee0, 1000 (3) failed acpi0: reservation of ffb8, 8 (3) failed acpi0: reservation of fec1, 20 (3) failed acpi0: reservation of 0, a (3) failed acpi0: reservation of 10, cfe0 (3) failed Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 32-bit timer at 3.579545MHz port 0x808-0x80b on acpi0 cpu0: ACPI CPU on acpi0 cpu1: ACPI CPU on acpi0 cpu2: ACPI CPU on acpi0 cpu3: ACPI CPU on acpi0 acpi_hpet0: High Precision Event Timer iomem 0xfed0-0xfed003ff on acpi0 Timecounter HPET frequency 14318180 Hz quality 900 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 pci1: ACPI PCI bus on pcib1 vgapci0: VGA-compatible display port 0xa000-0xa0ff mem 0xd000-0xdfff,0xfbbe-0xfbbe,0xfba0-0xfbaf irq 18
Re: missing disk device under 9-STABLE
On Sat, Mar 03, 2012 at 09:51:53PM +0200, Alexander Motin wrote: This looks like cause of the missing disk: ahcich1: Timeout on slot 0 port 0 ahcich1: is 0002 cs ss rs 0001 tfd 50 serr cmd 6017 ahcich1: Timeout on slot 0 port 0 ahcich1: is 0002 cs ss rs 0001 tfd 50 serr cmd 6017 It tells that controller signals interrupt, but driver haven't got it. That is even more strange after the disk on first SATA port is working fine. You may try to add to your /boot/loader.conf line: hint.ahci.0.msi=0 , or just set it via loader prompt. Alexander, Thanks, that seemed to clear the problem up, no troubles through half a dozen or more reboots. Is disabling MSI likely to have any side effects on, for example, performance or reliability? Is there any point to pursuing this as a FreeBSD problem, since I didn't have any issues under the old ATA system? I'm happy to help troubleshoot this if anyone thinks it's worth looking into. thanks, Jeff ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: missing disk device under 9-STABLE
On Sat, Mar 03, 2012 at 11:18:55PM +0200, Alexander Motin wrote: MSI interrupts could give a bit better performance. But with regular HDDs I think it is unlikely that you notice any difference. What's about about old driver, it never used MSI by default, while new one does. I see, thanks. What board and chipset do you use? Have you tried to update BIOS? Please I have not investigated a BIOS upgrade. I'll look into it. show `pciconf -lvcb` output about the controller. the AHCI driver attachment: ahci0@pci0:0:17:0: class=0x01018f card=0x43901002 chip=0x43901002 rev=0x00 hdr=0x00 vendor = 'ATI Technologies Inc' device = 'SB7x0/SB8x0/SB9x0 SATA Controller [IDE mode]' class = mass storage subclass = ATA bar [10] = type I/O Port, range 32, base 0x9000, size 8, enabled bar [14] = type I/O Port, range 32, base 0x8000, size 4, enabled bar [18] = type I/O Port, range 32, base 0x7000, size 8, enabled bar [1c] = type I/O Port, range 32, base 0x6000, size 4, enabled bar [20] = type I/O Port, range 32, base 0x5000, size 16, enabled bar [24] = type Memory, range 32, base 0xfb9ffc00, size 1024, enabled cap 05[50] = MSI supports 4 messages, 64 bit cap 12[70] = SATA Index-Data Pair the ATA driver attachment, included for completeness: atapci0@pci0:0:20:1:class=0x01018a card=0x439c1002 chip=0x439c1002 rev=0x00 hdr=0x00 vendor = 'ATI Technologies Inc' device = 'SB7x0/SB8x0/SB9x0 IDE Controller' class = mass storage subclass = ATA bar [20] = type I/O Port, range 32, base 0xff00, size 16, enabled cap 05[70] = MSI supports 2 messages thanks, Jeff ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
zpool upgrade, can't boot
Hi, I recently upgraded from 8.0-STABLE to 8.2-STABLE (Apr. 29 checkout) and upgraded my zpool (includes root FS) from v13 to v15. This is a dual-boot laptop, so I'm using MBR/boot0 and not GPT. Here's what happens when I boot: F1 Win F2 ? F3 FreeBSD F6 PXE Boot: F3 ZFS: unsupported ZFS version 15 (should be 13) No ZFS pools located, can't boot I've googled around, but I can't find anything relevant for MBR/boot0 configurations, just GPT. I've ensured that the loaders and boot0/boot1/boot2 are all new, and I rebuilt/reinstalled them in a fixit environment just to be sure. I also ran 'boot0cfg -B' (with an appropriate -b), but nothing has changed. How can I get my pool booting again? thanks, Jeff ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
sysctl(?) problem on boot in 8-STABLE
Hi, I upgraded an 8-STABLE box to r206119 and am now unable to boot multi-user. I found that it hangs at line 58/59 of /etc/rc.d/initrandom: ( ps -fauxww; sysctl -a; date; df -ib; dmesg; ps -fauxww ) \ | dd of=/dev/random bs=8k 2/dev/null when I run each of these commands by hand, I get only as far as 'sysctl -a', which seems to exit normally but leaves my keyboard unresponsive (actually acting like I'm leaning on the enter key). more digging reveals 'sysctl dev.uart' to be what triggers it. this is the entirety of dev.uart from r204154: dev.uart.0.%desc: 16550 or compatible dev.uart.0.%driver: uart dev.uart.0.%location: handle=\_SB_.PCI0.UAR1 dev.uart.0.%pnpinfo: _HID=PNP0501 _UID=1 dev.uart.0.%parent: acpi0 dev.uart.0.wake: 0 seems about the same from r206119. I've attached boot output from r206119. Any ideas? any other info I need to provide? thanks much, Jeff ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: sysctl(?) problem on boot in 8-STABLE
On Mon, Apr 05, 2010 at 10:56:22AM -0400, Jeff Blank wrote: I've attached boot output from r206119. whoops--either I didn't or it got tanked. sorry. http://web.mr-happy.com/mlf/20100405-boot-r206119.txt Jeff ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: sysctl(?) problem on boot in 8-STABLE
On Mon, Apr 05, 2010 at 09:11:39PM +0300, Mikolaj Golub wrote: On Mon, 5 Apr 2010 10:56:22 -0400 Jeff Blank wrote: when I run each of these commands by hand, I get only as far as 'sysctl -a', which seems to exit normally but leaves my keyboard unresponsive (actually acting like I'm leaning on the enter key). more digging reveals 'sysctl dev.uart' to be what triggers it. kern/143040 looks similar. Ah, you're right, it does. Could someone please take a look at that PR then? Looks like it was submitted in January but hasn't been assigned yet. thanks, Jeff ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: scp from livecd (fixit option) cd can not find /usr/bin/ssh
On Tue, Jan 19, 2010 at 12:36:12PM -0500, jhell wrote: On Tue, 19 Jan 2010 10:57, Johan@ wrote: Hello i use the livecd to save an old pc. But when i try to use scp to copy some data to our network i get the message that /usr/bin/ssh could not be found. This is the same for snapshots of stable/7 livecd too. Fixit# which ssh /mnt2/usr/bin/ssh Fixit# scp -S /mnt2/usr/bin/ssh ... Jeff ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: update to 8.0-RELEASE -- partition gone
On Wed, Dec 16, 2009 at 12:27:15PM +0100, Marian Hettwer wrote: but, hm, whats that? r...@talisker:/root# fsck /dev/ad8s1a fsck: Could not determine filesystem type If you don't have an entry for /dev/ad8s1a in your fstab, you need to specify the filesystem type with -t. Jeff ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Dell PowerEdge Virtual Media
Hi, I'm having a little trouble using the virtual media function of Dell's PowerEdge R-series (R710 in this case) iDRAC6 under FreeBSD (7.1, 8.0). This is presented as /dev/cd0, a USB/SCSI device, I guess. This is in the dmesg buffer when I boot up the existing 7.1 installation with the virtual optical drive mapped to the 8.0-RELEASE amd64 DVD image: umass0: Avocent USB Composite Device-1, class 0/0, rev 2.00/0.00, addr 2 on uhub6 [...] cd0 at umass-sim0 bus 0 target 0 lun 0 cd0: iDRAC Virtual CD 0323 Removable CD-ROM SCSI-0 device cd0: 40.000MB/s transfers cd0: cd present [1058105 x 2048 byte records] GEOM_LABEL: Label for provider cd0 is iso9660/FreeBSD_Install. However, # mount -t cd9660 /dev/cd0 /mnt mount_cd9660: /dev/cd0: Invalid argument When I boot from the DVD image via this virtual device, sysinstall comes up and works fine except for the fixit shell, at which point it wants me to insert a CD/DVD because it encounters an error mounting acd0 (and would presumably have the same problems if I attempted a fresh install). I have 'boot -v' output from such a boot attempt at http://web.mr-happy.com/mlf/8.0-bootv-dell-poweredge-r710-virtualmedia.txt in case it's useful. Please let me know what other information I can provide, and thank you for any help. Jeff ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Dell PowerEdge Virtual Media
On Tue, Dec 08, 2009 at 09:52:19AM -0800, Jeremy Chadwick wrote: On Tue, Dec 08, 2009 at 12:41:45PM -0500, Jeff Blank wrote: # mount -t cd9660 /dev/cd0 /mnt mount_cd9660: /dev/cd0: Invalid argument You want /dev/cd0c, not /dev/cd0. There is no /dev/cd0c or any other, just /dev/cd0. Jeff ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Dell PowerEdge Virtual Media
On Tue, Dec 08, 2009 at 09:54:41PM +0200, Andriy Gapon wrote: What? Are you still using 4.X? Or using some other OS? I'm using 7.1 (installed to disk) and 8.0 (DVD ISO/virtual media). Jeff ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Areca Disk Adapter Question
On Sat, Dec 05, 2009 at 07:43:35PM -0600, Karl Denninger wrote: To those who might have more experience with these boards than I do - is there a way to have them re-read the bus and export anything new (or remove anything not new) from the driver configuration? If you're talking about getting the card to find disks that were hot-attached or if you're referring to a non-RAID controller card, I'm not sure. If you're talking about creating RAID sets and such, I believe that areca-cli (ports/sysutils/areca-cli) will push changes from its rsf and vsf commands up to FreeBSD. you'd probably need to do a 'camcontrol rescan all' after making changes through the CLI utility. Jeff ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
8.0-BETA3/IPv6: route: bad keyword: cloning
Hi, Upon booting an 8.0-BETA3 system with IPv6 enabled, I saw this in the console boot output: route: bad keyword: cloning usage: route [-dnqtv] command [[modifiers] args] This looks like it's from line 1062/1063 of /etc/network.subr v1.195.2.4. This system is not an IPv6 router, so do I particularly need $ipv6_default_interface set in rc.conf? Is there a situation where -cloning (still referenced in the man page) is a valid option to route (in inet6 context at least)? If no, should I file a PR? (I searched GNATS but didn't find anything matching this.) thanks, Jeff ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: zfs on gmirror slice
On Tue, Sep 01, 2009 at 09:53:28PM +0200, Ivan Voras wrote: Maciej Jan Broniarz wrote: Is is a bad ida to create a zfs pool from a gmirrored slice? zpool create tank /dev/mirror/gm0s1g works fine, but after the reboot the filesystem failes consistency check. It *should* work. What error(s) do you get? I'm not the original poster, but I appear to be having similar problems, though it's a panic rather than a failed consistency check. I posted about it back in July, see http://lists.freebsd.org/pipermail/freebsd-stable/2009-July/051167.html I've since gotten a serial console working (needed to use uart instead of sio), so I can now provide a backtrace, this from sources around 0600 UTC on 31 Aug. My gmirror is entire disks (ad6/ad4), and my ZFS pool/filesystems are still v6, on /dev/mirror/gm0s1d. Jeff [...] WARNING: ZFS is considered to be an experimental feature in FreeBSD. Timecounters tick every 1.000 msec ZFS filesystem version 13 ZFS storage pool version 13 ad4: 152587MB SAMSUNG HE160HJ JF800-24 at ata2-master SATA300 ad6: 152587MB SAMSUNG HE160HJ JF800-24 at ata3-master SATA300 GEOM_MIRROR: Device mirror/gm0 launched (1/2). GEOM_MIRROR: Device gm0: rebuilding provider ad4. acd0: CDROM PBDS CD-ROM DH-48N1S/BD11 at ata4-master SATA150 acd1: CDRW TSSTcorp CD-RW/DVD-ROM TS-H493B/D200 at ata5-master SATA150 hdac0: HDA Codec #0: Sigmatel STAC9220 pcm0: HDA Sigmatel STAC9220 PCM #0 Analog at cad 0 nid 1 on hdac0 SMP: AP CPU #1 Launched! Trying to mount root from zfs:zgm0/root Fatal trap 12: page fault while in kernel mode cpuid = 1; apic id = 01 fault virtual address = 0x0 fault code = supervisor read data, page not present instruction pointer = 0x8:0x80da14fd stack pointer = 0x10:0xff81efd0 frame pointer = 0x10:0xff81f020 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 1 (swapper) [thread pid 1 tid 12 ] Stopped at vdev_geom_open+0x10d: movq(%r12),%rax db bt Tracing pid 1 tid 12 td 0xff000142eab0 vdev_geom_open() at vdev_geom_open+0x10d vdev_open() at vdev_open+0xa8 vdev_root_open() at vdev_root_open+0x94 vdev_open() at vdev_open+0xa8 spa_load() at spa_load+0x1d2 spa_load() at spa_load+0x461 spa_open_common() at spa_open_common+0x12d dsl_dir_open_spa() at dsl_dir_open_spa+0x279 dsl_dataset_hold() at dsl_dataset_hold+0x3b dsl_prop_get() at dsl_prop_get+0x3c zfs_mount() at zfs_mount+0x264 vfs_donmount() at vfs_donmount+0xdea kernel_mount() at kernel_mount+0x88 kernel_vmount() at kernel_vmount+0xcb vfs_mountroot_try() at vfs_mountroot_try+0x10c vfs_mountroot() at vfs_mountroot+0x32e start_init() at start_init+0x4d fork_exit() at fork_exit+0x11e fork_trampoline() at fork_trampoline+0xe --- trap 0, rip = 0, rsp = 0xff81fd30, rbp = 0 --- db ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
8.0-BETA3 and txp(4) panic: vm_phys_alloc_contig
Hi, When booting 8.0-BETA3, whether built from source under 7.2-STABLE or just using the CD (AMD64 disc1), I get a panic and a trip to the debugger. No panic if I remove my 3Com ethernet card (txp). 'pciconf -lv' output is below the boot log. Jeff GDB: no debug ports present KDB: debugger backends: ddb KDB: current backend: ddb Copyright (c) 1992-2009 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 is a registered trademark of The FreeBSD Foundation. FreeBSD 8.0-BETA3 #0: Sat Aug 22 02:00:45 UTC 2009 r...@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC WARNING: WITNESS option enabled, expect reduced performance. Timecounter i8254 frequency 1193182 Hz quality 0 CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 5600+ (2906.08-MHz K8-class CPU) Origin = AuthenticAMD Id = 0x60fb2 Stepping = 2 Features=0x178bfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT Features2=0x2001SSE3,CX16 AMD Features=0xea500800SYSCALL,NX,MMX+,FFXSR,RDTSCP,LM,3DNow!+,3DNow! AMD Features2=0x11fLAHF,CMP,SVM,ExtAPIC,CR8,Prefetch TSC: P-state invariant real memory = 4294967296 (4096 MB) avail memory = 4092305408 (3902 MB) ACPI APIC Table: DELL bMk FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs FreeBSD/SMP: 1 package(s) x 2 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0: Changing APIC ID to 4 ioapic0 Version 1.1 irqs 0-23 on motherboard kbd1 at kbdmux0 acpi0: DELL bMk on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: reservation of 0, a (3) failed acpi0: reservation of 10, bfdd (3) failed Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x1008-0x100b on acpi0 acpi_hpet0: High Precision Event Timer iomem 0xfeff-0xfeff03ff on acpi0 Timecounter HPET frequency 2500 Hz quality 900 acpi_button0: Power Button on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 pci0: memory, RAM at device 0.0 (no driver attached) pci0: memory, RAM at device 0.1 (no driver attached) pci0: memory, RAM at device 0.2 (no driver attached) pci0: memory, RAM at device 0.3 (no driver attached) pci0: memory, RAM at device 0.4 (no driver attached) pci0: memory, RAM at device 0.5 (no driver attached) pci0: memory, RAM at device 0.6 (no driver attached) pci0: memory, RAM at device 0.7 (no driver attached) pcib1: ACPI PCI-PCI bridge at device 2.0 on pci0 pci1: ACPI PCI bus on pcib1 pcib2: ACPI PCI-PCI bridge at device 3.0 on pci0 pci2: ACPI PCI bus on pcib2 bge0: Broadcom NetXtreme Gigabit Ethernet Controller, ASIC rev. 0xb002 mem 0xfd8f-0xfd8f irq 16 at device 0.0 on pci2 miibus0: MII bus on bge0 brgphy0: BCM5787 10/100/1000baseTX PHY PHY 1 on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto bge0: Ethernet address: 00:1e:c9:44:30:14 bge0: [ITHREAD] pcib3: ACPI PCI-PCI bridge at device 4.0 on pci0 pci3: ACPI PCI bus on pcib3 vgapci0: VGA-compatible display port 0xbc00-0xbcff mem 0xd000-0xdfff,0xfddf-0xfddf irq 16 at device 0.0 on pci3 vgapci1: VGA-compatible display mem 0xfdde-0xfdde at device 0.1 on pci3 pci0: memory, RAM at device 9.0 (no driver attached) isab0: PCI-ISA bridge port 0x1d00-0x1dff at device 10.0 on pci0 isa0: ISA bus on isab0 pci0: serial bus, SMBus at device 10.1 (no driver attached) pci0: memory, RAM at device 10.2 (no driver attached) ohci0: OHCI (generic) USB controller mem 0xfe02f000-0xfe02 irq 21 at device 11.0 on pci0 ohci0: [ITHREAD] usbus0: OHCI (generic) USB controller on ohci0 ehci0: EHCI (generic) USB 2.0 controller mem 0xfe02e000-0xfe02e0ff irq 22 at device 11.1 on pci0 ehci0: [ITHREAD] usbus1: EHCI version 1.0 usbus1: EHCI (generic) USB 2.0 controller on ehci0 atapci0: nVidia nForce MCP51 SATA300 controller port 0x9f0-0x9f7,0xbf0-0xbf3,0x970-0x977,0xb70-0xb73,0xe000-0xe00f mem 0xfe02d000-0xfe02dfff irq 23 at device 14.0 on pci0 atapci0: [ITHREAD] ata2: ATA channel 0 on atapci0 ata2: [ITHREAD] ata3: ATA channel 1 on atapci0 ata3: [ITHREAD] atapci1: nVidia nForce MCP51 SATA300 controller port 0x9e0-0x9e7,0xbe0-0xbe3,0x960-0x967,0xb60-0xb63,0xcc00-0xcc0f mem 0xfe02c000-0xfe02cfff irq 20 at device 15.0 on pci0 atapci1: [ITHREAD] ata4: ATA channel 0 on atapci1 ata4: [ITHREAD] ata5: ATA channel 1 on atapci1 ata5: [ITHREAD] pcib4: ACPI PCI-PCI bridge at device 16.0 on pci0 pci4: ACPI PCI bus on pcib4 txp0: 3Com 3cR990-SRV-97 Etherlink Server with 3XP Processor port 0x9c00-0x9c7f mem 0xfdcc-0xfdcf irq 16 at device 8.0 on pci4 panic: vm_phys_alloc_contig: alignment must be a power of 2 cpuid = 0 KDB: enter: panic [thread pid 0 tid 10 ] Stopped at kdb_enter+0x3d: movq$0,0x68c5b0(%rip) db bt Tracing pid 0 tid 10 td 0x80c1ae80 kdb_enter() at kdb_enter+0x3d panic() at
Re: 8.0-BETA3 and txp(4) panic: vm_phys_alloc_contig
On Mon, Aug 31, 2009 at 10:49:18AM -0700, Pyun YongHyeon wrote: Hmm, this is odd. I can't find where the alignment is not power of 2 in txp_dma_alloc(). Could you show me the line number of txp_attach+0x6f5? What's the command to do this? I thought it might be 'x/A txp_attach+0x65f', but that gave me nothing. (I don't have a crash dump to work with, just a serial console and ddb.) Jeff ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 8.0-BETA3 and txp(4) panic: vm_phys_alloc_contig
On Mon, Aug 31, 2009 at 12:29:20PM -0700, Pyun YongHyeon wrote: Hmm... never mind. Please try attached patch let me know how it goes. that seemed to do it. I didn't get a chance to test networking at all, as I ran into another (most probably unrelated) panic, but I can at least get past the point where txp0 gets detected now. thanks, Jeff ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 7.2-PRE amd64 panic when starting Xorg
On Sun, Apr 26, 2009 at 01:08:13AM -0400, Jeff Blank wrote: I've installed 7.2-PRERELEASE, csup on 20090423 at around 19:00 UTC. When I rebooted after installing world, X started (xdm in /etc/ttys) and immediately panicked the system, even before switching to the new VTY. I probably should have specified that my video chipset is a Radeon X800 (R430), PCIE, instead of letting you all go hunting for it in the attachments of my previous post. And a little more playing reveals that the panic goes away when I disable dri and dri2 in xorg.conf. I had those commented out in the previously-attached config, not realising that they're enabled by default. (Though X still doesn't seem to work quite right without those, for whatever that's worth). Jeff ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 7.2-PRE amd64 panic when starting Xorg
On Sun, Apr 26, 2009 at 01:08:13AM -0400, Jeff Blank wrote: I've installed 7.2-PRERELEASE, csup on 20090423 at around 19:00 UTC. When I rebooted after installing world, X started (xdm in /etc/ttys) and immediately panicked the system, even before switching to the new VTY. One more note: using 'date=' in a supfile, I think I've narrowed this down to the changes in sys/dev/drm on March 11, which include radeon_cp.c and radeon_irq.c. Jeff ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: bge problems under 7.2-PRERELEASE
On Thu, Apr 23, 2009 at 12:41:36AM -0700, Annelise Anderson wrote: I wanted to upgrade my stable and but now am afraid to reboot with the new kernel as I've got one of these bge0 cards. You should be able to back out fairly easily in case of most problems. When you reboot to single-user mode with the new kernel, you can test whatever you think you need to (device presence/functionality, networking, etc) before installing world. If you don't like the results, just rename or delete /boot/kernel, rename /boot/kernel.old to /boot/kernel, and reboot, no damage done (usually). dmesg reveals: brgphy0: BCM5750 10/100/1000baseTX PHY PHY 1 on miibus0 a different version of BCM, not BCM 5754 I can't speak authoritatively, but I expect you're fine. My problem appears to have a very narrow scope. Jeff ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: bge problems under 7.2-PRERELEASE
On Thu, Apr 23, 2009 at 07:19:49PM +0200, Marius Strobl wrote: So in combination with the low number of problem reports this really doesn't look like a generic problem of this Broadcom hardware or bge(4) and I just can suggest to disable MSI by setting the hw.pci.enable_msi tuneable to 0 for now. Great, this does the trick, and I'm now running today's RELENG_7. Thanks for your help, and let me know if ever you'd like me to help test possible fixes. Jeff ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: bge problems under 7.2-PRERELEASE
On Tue, Apr 21, 2009 at 09:55:10PM +0200, Marius Strobl wrote: Use the sources you have but plug in sys/dev/bge/if_bge.c rev 1.198.2.13 and sys/dev/pci/pci.c rev 1.355.2.6, this combination should work. correct. Then update if_bge.c to rev 1.198.2.14 and check whether things still work, this causes the problem to resurface. Jeff ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: bge problems under 7.2-PRERELEASE
On Tue, Apr 21, 2009 at 08:49:24PM +0200, Marius Strobl wrote: On Mon, Apr 20, 2009 at 04:46:38PM -0400, Jeff Blank wrote: I have no trouble with networking using a kernel from 20090115. This Does that working kernel include r187309 (if_bge.c rev 1.198.2.14)? nope, 1.198.2.11. If it predates it could you please check whether this is the change which breaks things for you? what's the best way to go about this? I no longer have the source tree from the working kernel. should I plug 1.198.2.11 into the sources I have and then try .14? any other files I'd need previous revisions of? or is there a different, better way to go about it? (I don't know much about time-travelling through source.) thanks, Jeff ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
bge problems under 7.2-PRERELEASE
Hi, csup today around 13:00 UTC. 'make buildworld', 'make buildkernel', 'make installkernel', reboot to single-user. # ifconfig bge0 141.219.5.33/22 up # ping 141.219.4.1 PING 141.219.4.1 (141.219.4.1): 56 data bytes ^C --- 141.219.4.1 ping statistics --- 3 packets transmitted, 0 packets received, 100.0% packet loss # ifconfig bge0 bge0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=9bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM ether 00:1e:c9:44:30:14 inet6 fe80::21e:c9ff:fe44:3014%bge0 prefixlen 64 scopeid 0x1 inet 141.219.5.33 netmask 0xfc00 broadcast 141.219.7.255 media: Ethernet autoselect (100baseTX full-duplex) status: active I have no trouble with networking using a kernel from 20090115. This is a Dell Optiplex 740, about 9 months old. make.conf and src.conf are below. dmesg and pciconf output are attached. I ran 'tcpdump -i bge0 -nn' while pinging, and this captured no packets, not even this host's ARP broadcasts. I also encountered this problem in late March as well, just after RELENG_7 became 7.2-PRERELEASE, but couldn't find time to put this information together. If there's anything else I can run to troubleshoot this, please let me know. thank you, Jeff Blank /etc/make.conf: CPUTYPE ?= k8 WITHOUT_NLS=true [port-specific options elided for brevity] /etc/src.conf: WITHOUT_ATM=true WITHOUT_GPIB=true WITHOUT_I4B=true WITHOUT_IPFILTER=true WITHOUT_IPFW=true WITHOUT_IPX=true WITHOUT_LIB32=true WITHOUT_NCP=true WITHOUT_NDIS=true WITHOUT_PPP=true WITHOUT_QUOTAS=true WITHOUT_RCMDS=true WITHOUT_SENDMAIL=true WITHOUT_SLIP=true WITHOUT_WIRELESS=true # dmesg Copyright (c) 1992-2009 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 is a registered trademark of The FreeBSD Foundation. FreeBSD 7.2-PRERELEASE #0: Mon Apr 20 12:27:26 EDT 2009 r...@bender.tc.mtu.edu:/usr/obj/usr/src/sys/GENERIC Timecounter i8254 frequency 1193182 Hz quality 0 CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 5600+ (2906.08-MHz K8-class CPU) Origin = AuthenticAMD Id = 0x60fb2 Stepping = 2 Features=0x178bfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT Features2=0x2001SSE3,CX16 AMD Features=0xea500800SYSCALL,NX,MMX+,FFXSR,RDTSCP,LM,3DNow!+,3DNow! AMD Features2=0x11fLAHF,CMP,SVM,ExtAPIC,CR8,Prefetch TSC: P-state invariant Cores per package: 2 usable memory = 4278718464 (4080 MB) avail memory = 4098314240 (3908 MB) ACPI APIC Table: DELL bMk FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 This module (opensolaris) contains code covered by the Common Development and Distribution License (CDDL) see http://opensolaris.org/os/licensing/opensolaris_license/ ioapic0: Changing APIC ID to 4 ioapic0 Version 1.1 irqs 0-23 on motherboard kbd1 at kbdmux0 acpi0: DELL bMk on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: reservation of 0, a (3) failed acpi0: reservation of 10, bfdd (3) failed Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x1008-0x100b on acpi0 acpi_hpet0: High Precision Event Timer iomem 0xfeff-0xfeff03ff on acpi0 Timecounter HPET frequency 2500 Hz quality 900 acpi_button0: Power Button on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 pci0: memory, RAM at device 0.0 (no driver attached) pci0: memory, RAM at device 0.1 (no driver attached) pci0: memory, RAM at device 0.2 (no driver attached) pci0: memory, RAM at device 0.3 (no driver attached) pci0: memory, RAM at device 0.4 (no driver attached) pci0: memory, RAM at device 0.5 (no driver attached) pci0: memory, RAM at device 0.6 (no driver attached) pci0: memory, RAM at device 0.7 (no driver attached) pcib1: ACPI PCI-PCI bridge at device 2.0 on pci0 pci1: ACPI PCI bus on pcib1 pcib2: ACPI PCI-PCI bridge at device 3.0 on pci0 pci2: ACPI PCI bus on pcib2 bge0: Broadcom NetXtreme Gigabit Ethernet Controller, ASIC rev. 0xb002 mem 0xfd8f-0xfd8f irq 16 at device 0.0 on pci2 miibus0: MII bus on bge0 brgphy0: BCM5787 10/100/1000baseTX PHY PHY 1 on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto bge0: Ethernet address: 00:1e:c9:44:30:14 bge0: [ITHREAD] pcib3: ACPI PCI-PCI bridge at device 4.0 on pci0 pci3: ACPI PCI bus on pcib3 vgapci0: VGA-compatible display port 0xbc00-0xbcff mem 0xd000-0xdfff,0xfddf-0xfddf irq 16 at device 0.0 on pci3 vgapci1: VGA-compatible display mem 0xfdde-0xfdde at device 0.1 on pci3 pci0: memory, RAM at device 9.0 (no driver attached) isab0: PCI-ISA bridge port 0x1d00-0x1dff at device 10.0 on pci0 isa0: ISA bus on isab0 pci0: serial bus, SMBus at device 10.1 (no driver attached) pci0
Re: bce(4) and rx errors
On Sun, Dec 14, 2008 at 01:36:35AM -0800, Xin LI wrote: I have not yet talked this with David but it looks like this patch would make it disappear. Applied to 7.1-RC1, and rx errors are gone. Thank you! Jeff ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: bce(4) and rx errors
On Wed, Dec 10, 2008 at 04:59:26PM +0200, Vlad GALU wrote: I have an application pulling about 220Kpps from a bce(4) card (details below). At what seems to be random times, errors start showing up on that interface (I'm watching it with netstat -w1 -I), so about 10% of the initial 220Kpps is reported as errors. I'm also seeing a pretty steady stream of errors on both bce interfaces in a Dell PowerEdge 2950 III. In my case, the source is RELENG_7_1 from ~14:00 UTC yesterday (9 Dec). Throughput does not seem to be affected. sysctl -a | egrep -i 'bce.*err' yields all zeroes, for whatever that's worth. [EMAIL PROTECTED]:0:0:0:class=0x06 card=0x80868086 chip=0x25c08086 rev=0x12 hdr=0x00 vendor = 'Intel Corporation' device = '5000X Chipset Memory Controller Hub' class = bridge subclass = HOST-PCI [EMAIL PROTECTED]:0:2:0:class=0x060400 card=0x chip=0x25e28086 rev=0x12 hdr=0x01 vendor = 'Intel Corporation' device = '5000 Series Chipset PCIe x4 Port 2' class = bridge subclass = PCI-PCI [EMAIL PROTECTED]:0:3:0:class=0x060400 card=0x chip=0x25e38086 rev=0x12 hdr=0x01 vendor = 'Intel Corporation' device = '5000 Series Chipset PCIe x4 Port 3' class = bridge subclass = PCI-PCI [EMAIL PROTECTED]:0:4:0:class=0x060400 card=0x chip=0x25f88086 rev=0x12 hdr=0x01 vendor = 'Intel Corporation' device = '5000 Series Chipset PCIe x8 Port 4-5' class = bridge subclass = PCI-PCI [EMAIL PROTECTED]:0:5:0:class=0x060400 card=0x chip=0x25e58086 rev=0x12 hdr=0x01 vendor = 'Intel Corporation' device = '5000 Series Chipset PCIe x4 Port 5' class = bridge subclass = PCI-PCI [EMAIL PROTECTED]:0:6:0:class=0x060400 card=0x chip=0x25f98086 rev=0x12 hdr=0x01 vendor = 'Intel Corporation' device = '5000 Series Chipset PCIe x8 Port 6-7' class = bridge subclass = PCI-PCI [EMAIL PROTECTED]:0:7:0:class=0x060400 card=0x chip=0x25e78086 rev=0x12 hdr=0x01 vendor = 'Intel Corporation' device = '5000 Series Chipset PCIe x4 Port 7' class = bridge subclass = PCI-PCI [EMAIL PROTECTED]:0:16:0: class=0x06 card=0x01b21028 chip=0x25f08086 rev=0x12 hdr=0x00 vendor = 'Intel Corporation' device = '5000 Series Chipset Error Reporting Registers' class = bridge subclass = HOST-PCI [EMAIL PROTECTED]:0:16:1: class=0x06 card=0x01b21028 chip=0x25f08086 rev=0x12 hdr=0x00 vendor = 'Intel Corporation' device = '5000 Series Chipset Error Reporting Registers' class = bridge subclass = HOST-PCI [EMAIL PROTECTED]:0:16:2: class=0x06 card=0x01b21028 chip=0x25f08086 rev=0x12 hdr=0x00 vendor = 'Intel Corporation' device = '5000 Series Chipset Error Reporting Registers' class = bridge subclass = HOST-PCI [EMAIL PROTECTED]:0:17:0: class=0x06 card=0x80868086 chip=0x25f18086 rev=0x12 hdr=0x00 vendor = 'Intel Corporation' device = '5000 Series Chipset Reserved Registers' class = bridge subclass = HOST-PCI [EMAIL PROTECTED]:0:19:0: class=0x06 card=0x80868086 chip=0x25f38086 rev=0x12 hdr=0x00 vendor = 'Intel Corporation' device = '5000 Series Chipset Reserved Registers' class = bridge subclass = HOST-PCI [EMAIL PROTECTED]:0:21:0: class=0x06 card=0x80868086 chip=0x25f58086 rev=0x12 hdr=0x00 vendor = 'Intel Corporation' device = '5000 Series Chipset FBD Registers' class = bridge subclass = HOST-PCI [EMAIL PROTECTED]:0:22:0: class=0x06 card=0x80868086 chip=0x25f68086 rev=0x12 hdr=0x00 vendor = 'Intel Corporation' device = '5000 Series Chipset FBD Registers' class = bridge subclass = HOST-PCI [EMAIL PROTECTED]:0:28:0: class=0x060400 card=0x01b21028 chip=0x26908086 rev=0x09 hdr=0x01 vendor = 'Intel Corporation' device = '631xESB/632xESB/3100 PCIe Root Port 1' class = bridge subclass = PCI-PCI [EMAIL PROTECTED]:0:29:0: class=0x0c0300 card=0x01b21028 chip=0x26888086 rev=0x09 hdr=0x00 vendor = 'Intel Corporation' device = '631xESB/632xESB/3100 Chipset USB Universal Host Controller' class = serial bus subclass = USB [EMAIL PROTECTED]:0:29:1: class=0x0c0300 card=0x01b21028 chip=0x26898086 rev=0x09 hdr=0x00 vendor = 'Intel Corporation' device = '631xESB/632xESB/3100 Chipset USB Universal Host Controller' class = serial bus subclass = USB [EMAIL PROTECTED]:0:29:2: class=0x0c0300 card=0x01b21028 chip=0x268a8086 rev=0x09 hdr=0x00 vendor = 'Intel Corporation' device = '631xESB/632xESB/3100 Chipset USB Universal Host Controller' class =
can't see non-root writes to /dev/console
I just upgraded a RELENG_7 (amd64) box from 20080714 to latest (which seems to be from a few days ago--no changes from Monday morning's csup to today's) and can no longer see the effect of writing to /dev/console as non-root. When I log in using xdm, my user owns /dev/console, mode 0622 (-rw--w--w-), and I start an 'xterm -C'. But when I, for example, echo foo /dev/console I see nothing in the console xterm. No error messages, and echo exits 0. If I su to root and do the same, I get 'foo' in the same console xterm. Syslog messages to /dev/console also appear, of course. All the above applies to xconsole as well, not just xterm. I did recompile xterm from 20080616 ports, but it didn't fix the issue (didn't expect it to, as xterm clearly has no trouble attaching and reading). So my echo is getting lost in the kernel, I guess. Known problem? Intentional change? Something else? thanks, Jeff ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: can't see non-root writes to /dev/console
On Wed, Sep 10, 2008 at 04:34:51PM -0400, Jeff Blank wrote: I just upgraded a RELENG_7 (amd64) box from 20080714 to latest (which seems to be from a few days ago--no changes from Monday morning's csup to today's) and can no longer see the effect of writing to /dev/console as non-root. Sorry, I should have mentioned that my kernel is GENERIC + 'options DEVICE_POLLING'. And I guess I havn't updated my kernel config file since the last time amd64/GENERIC changed, but the only (other) differences are that I don't have device lines for igb, age, et, or jme. Jeff ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: bus_dmamem_alloc failed to align memory properly
On Mon, Jun 23, 2008 at 10:50:40AM -1000, Clifton Royston wrote: I can not be completely sure, but believe this may be a cross-OS problem with Xorg support of this specific ATI card family. Interesting. Thanks for the tip. If you don't want to spend a lot of time on this, I'd try a different video card; I have a strong suspicion that your problems are not FreeBSD related and would go away with that change. Cool, I'll try a Radeon X1550 on Monday. thanks, Jeff ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: bus_dmamem_alloc failed to align memory properly
On Tue, Jun 17, 2008 at 11:43:42AM -0400, Jeff Blank wrote: I've installed a PCI (not PCIE) video card in a FreeBSD 7-STABLE (20080616 ~19:00 UTC) amd64 system, and when Xorg starts, the kernel logs the message in the subject. Context: Jun 17 11:27:30 bender kernel: drm0: ATI Radeon RV280 9250 on vgapci0 Jun 17 11:27:30 bender kernel: info: [drm] Initialized radeon 1.25.0 20060524 Jun 17 11:27:33 bender kernel: info: [drm] Setting GART location based on new memory map Jun 17 11:27:33 bender kernel: bus_dmamem_alloc failed to align memory properly. Jun 17 11:27:33 bender kernel: info: [drm] Loading R200 Microcode Jun 17 11:27:33 bender kernel: info: [drm] writeback test succeeded in 2 usecs Jun 17 11:27:33 bender kernel: drm0: [ITHREAD] Is this anything to worry about? Part of the reason I ask is that the machine locked up hard (had to cut power) the first time I hit ctrl-alt-bs to kill Xorg, though I can't reproduce that reliably (or, really, at all just yet). Still hoping for an answer, as the PC locked up hard a few more times, always when trying to exit the X server (normal logout/all clients terminated, ctl-alt-bs, init 6). The PC is a Dell Optiplex 740. Its onboard video is NVidia NVS 210S nVidia GForce 6150, but that is disabled when an add-in video card is present (wasn't present in the 'pciconf -lv' I posted last week). What can I do to determine whether the X11 problem is bus_dmamem_alloc failed to align memory properly or something else with the card? thanks, Jeff ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
bus_dmamem_alloc failed to align memory properly
Hi, I've installed a PCI (not PCIE) video card in a FreeBSD 7-STABLE (20080616 ~19:00 UTC) amd64 system, and when Xorg starts, the kernel logs the message in the subject. Context: Jun 17 11:27:30 bender kernel: drm0: ATI Radeon RV280 9250 on vgapci0 Jun 17 11:27:30 bender kernel: info: [drm] Initialized radeon 1.25.0 20060524 Jun 17 11:27:33 bender kernel: info: [drm] Setting GART location based on new memory map Jun 17 11:27:33 bender kernel: bus_dmamem_alloc failed to align memory properly. Jun 17 11:27:33 bender kernel: info: [drm] Loading R200 Microcode Jun 17 11:27:33 bender kernel: info: [drm] writeback test succeeded in 2 usecs Jun 17 11:27:33 bender kernel: drm0: [ITHREAD] Is this anything to worry about? Part of the reason I ask is that the machine locked up hard (had to cut power) the first time I hit ctrl-alt-bs to kill Xorg, though I can't reproduce that reliably (or, really, at all just yet). Let me know if I can provide more information. full dmesg and pciconf output below. Oh, kernel is GENERIC + options DEVICE_POLLING. thanks, Jeff full dmesg: = Copyright (c) 1992-2008 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 is a registered trademark of The FreeBSD Foundation. FreeBSD 7.0-STABLE #0: Mon Jun 16 19:20:53 EDT 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/POLLING Timecounter i8254 frequency 1193182 Hz quality 0 CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 5600+ (2906.09-MHz K8-class CPU) Origin = AuthenticAMD Id = 0x60fb2 Stepping = 2 Features=0x178bfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT Features2=0x2001SSE3,CX16 AMD Features=0xea500800SYSCALL,NX,MMX+,FFXSR,RDTSCP,LM,3DNow!+,3DNow! AMD Features2=0x11fLAHF,CMP,SVM,ExtAPIC,CR8,Prefetch Cores per package: 2 usable memory = 4279500800 (4081 MB) avail memory = 4108906496 (3918 MB) ACPI APIC Table: DELL bMk FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0: Changing APIC ID to 4 ioapic0 Version 1.1 irqs 0-23 on motherboard kbd1 at kbdmux0 ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) acpi0: DELL bMk on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: reservation of 0, a (3) failed acpi0: reservation of 10, bfdd (3) failed Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x1008-0x100b on acpi0 acpi_hpet0: High Precision Event Timer iomem 0xfeff-0xfeff03ff on acpi0 Timecounter HPET frequency 2500 Hz quality 900 cpu0: ACPI CPU on acpi0 powernow0: PowerNow! K8 on cpu0 cpu1: ACPI CPU on acpi0 powernow1: PowerNow! K8 on cpu1 acpi_button0: Power Button on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 pci0: memory, RAM at device 0.0 (no driver attached) pci0: memory, RAM at device 0.1 (no driver attached) pci0: memory, RAM at device 0.2 (no driver attached) pci0: memory, RAM at device 0.3 (no driver attached) pci0: memory, RAM at device 0.4 (no driver attached) pci0: memory, RAM at device 0.5 (no driver attached) pci0: memory, RAM at device 0.6 (no driver attached) pci0: memory, RAM at device 0.7 (no driver attached) pcib1: ACPI PCI-PCI bridge at device 2.0 on pci0 pci1: ACPI PCI bus on pcib1 pcib2: ACPI PCI-PCI bridge at device 3.0 on pci0 pci2: ACPI PCI bus on pcib2 bge0: Broadcom NetXtreme Gigabit Ethernet Controller, ASIC rev. 0xb002 mem 0xfdef-0xfdef irq 16 at device 0.0 on pci2 miibus0: MII bus on bge0 brgphy0: BCM5787 10/100/1000baseTX PHY PHY 1 on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto bge0: Ethernet address: 00:1e:c9:44:30:14 bge0: [ITHREAD] pcib3: ACPI PCI-PCI bridge at device 4.0 on pci0 pci3: ACPI PCI bus on pcib3 pci0: memory, RAM at device 9.0 (no driver attached) isab0: PCI-ISA bridge port 0x1d00-0x1dff at device 10.0 on pci0 isa0: ISA bus on isab0 pci0: serial bus, SMBus at device 10.1 (no driver attached) pci0: memory, RAM at device 10.2 (no driver attached) ohci0: OHCI (generic) USB controller mem 0xfe02f000-0xfe02 irq 21 at device 11.0 on pci0 ohci0: [GIANT-LOCKED] ohci0: [ITHREAD] usb0: OHCI version 1.0, legacy support usb0: SMM does not respond, resetting usb0: OHCI (generic) USB controller on ohci0 usb0: USB revision 1.0 uhub0: nVidia OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 on usb0 uhub0: 8 ports with 8 removable, self powered ehci0: EHCI (generic) USB 2.0 controller mem 0xfe02e000-0xfe02e0ff irq 22 at device 11.1 on pci0 ehci0: [GIANT-LOCKED] ehci0: [ITHREAD] usb1: EHCI version 1.0 usb1: companion controller, 8 ports each: usb0 usb1: EHCI (generic) USB 2.0 controller on ehci0 usb1: USB revision 2.0 uhub1: nVidia EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 on usb1 uhub1: 8 ports with 8
Re: 7.0-STABLE amd64 kernel trap during boot-time device probe
On Sun, Mar 02, 2008 at 07:04:29PM +1100, Peter Jeremy wrote: It looks like there's an unexpected ATA interrupt. I can't think of any reason why either sound or netgraph would cause this - neither should be touching the hardware directly. Unless someone else has seen this before, tracking it down could be time-consuming. I think you'll need a serial console to continue. Are you still mainly interested in the 'boot -v' output, or did you have something else in mind for the serial console? I looked over the 'remote GDB' section of the handbook, and I gather I'd need a second amd64 host for that, but I unfortunately don't. Jeff ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
7.0-STABLE amd64 kernel trap during boot-time device probe
Hello, I posted this around 3 months ago and never received a response. the problem still occurs with 7.0-STABLE (csup on 20080301). I possibly incorrectly referred to it as a panic last time, when the problem was really a trap. The only steps I've really taken since I posted this originally were to upgrade world/kernel due to patches a couple times and to perform an upgrade install from the 7.0-RELEASE CD, none of which had any effect. Can anyone please help me out with this? thank you, Jeff - Forwarded message from Jeff Blank [EMAIL PROTECTED] - Date: Fri, 7 Dec 2007 00:05:57 -0500 From: Jeff Blank [EMAIL PROTECTED] To: freebsd-stable@freebsd.org Subject: 7.0-BETA4 amd64 panic during boot-time device probe I've upgraded my AMD64 box from RELENG_6 (csup on Nov. 30) to RELENG_7 (csup around 01:30 UTC Dec. 7) and am getting a kernel panic when I try to boot with seemingly any one module specified in /boot/loader.conf (XXX_load=YES). It seems to occur near the end of device probing, just before it detects the disks. This panic does not happen if no modules are specified to be loaded in /boot/loader.conf. There is also no panic if I boot without loader.conf modules but then load the modules with kldload. This problem was originally happening when I was attempting to go from 6-STABLE to 7.0-BETA4, and rebuilding 7.0B4 under 7.0B4 yields the same result. Here is console output from the panic and partial dmesg output from the successful boot (similar up to a point, some context included). I couldn't get my serial port to accept input at the debugger prompt, and my keyboard (USB) can't even Press a key on the console to reboot when I have a non-ddb/kdb/etc kernel, so I couldn't do anything once I got into the debugger. Hopefully what's below has some useful information--if not, I'll be happy to try to get it. On the subject of the kernel debugger, I used GENERIC plus options DDB options DDB_NUMSYM options GDB options KDB options KDB_TRACE and set hint.sio.0.flags=0x80 in /boot/device.hints. What am I missing to allow serial input when the debugger starts? thanks for any help, Jeff === panic === GDB: debug ports: sio GDB: current port: sio KDB: debugger backends: ddb gdb KDB: current backend: ddb Copyright (c) 1992-2007 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 is a registered trademark of The FreeBSD Foundation. FreeBSD 7.0-BETA4 #0: Thu Dec 6 23:35:34 EST 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC_DBG Timecounter i8254 frequency 1193182 Hz quality 0 CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 4400+ (2211.34-MHz K8-class CPU) Origin = AuthenticAMD Id = 0x20f32 Stepping = 2 Features=0x178bfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT Features2=0x1SSE3 AMD Features=0xe2500800SYSCALL,NX,MMX+,FFXSR,LM,3DNow!+,3DNow! AMD Features2=0x3LAHF,CMP Cores per package: 2 usable memory = 1060421632 (1011 MB) avail memory = 1021755392 (974 MB) ACPI APIC Table: Nvidia AWRDACPI FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0: Changing APIC ID to 2 ioapic0 Version 1.1 irqs 0-23 on motherboard kbd1 at kbdmux0 ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) acpi0: Nvidia AWRDACPI on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: reservation of 0, a (3) failed acpi0: reservation of 10, 3fef (3) failed Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x4008-0x400b on acpi0 cpu0: ACPI CPU on acpi0 powernow0: Cool`n'Quiet K8 on cpu0 device_attach: powernow0 attach returned 6 cpu1: ACPI CPU on acpi0 powernow1: Cool`n'Quiet K8 on cpu1 device_attach: powernow1 attach returned 6 acpi_button0: Power Button on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 pci0: memory at device 0.0 (no driver attached) isab0: PCI-ISA bridge at device 1.0 on pci0 isa0: ISA bus on isab0 pci0: serial bus, SMBus at device 1.1 (no driver attached) ohci0: OHCI (generic) USB controller mem 0xdc004000-0xdc004fff irq 21 at device 2.0 on pci0 ohci0: [GIANT-LOCKED] ohci0: [ITHREAD] usb0: OHCI version 1.0, legacy support usb0: SMM does not respond, resetting usb0: OHCI (generic) USB controller on ohci0 usb0: USB revision 1.0 uhub0: nVidia OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 on usb0 uhub0: 10 ports with 10 removable, self powered ehci0: NVIDIA nForce4 USB 2.0 controller mem 0xfeb0-0xfeb000ff irq 22 at device 2.1 on pci0 ehci0: [GIANT-LOCKED] ehci0: [ITHREAD] usb1: EHCI version 1.0 usb1: companion controller, 4 ports each: usb0 usb1: NVIDIA nForce4 USB 2.0 controller on ehci0 usb1: USB revision 2.0 uhub1: nVidia EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 on usb1 uhub1: 10 ports with 10
Re: 7.0-STABLE amd64 kernel trap during boot-time device probe
On Sun, Mar 02, 2008 at 09:56:46AM +1100, Peter Jeremy wrote: On Sat, Mar 01, 2008 at 02:44:04PM -0500, Jeff Blank wrote: /boot/loader.conf (XXX_load=YES). It seems to occur near the end of device probing, just before it detects the disks. This is likely to be when the loaded modules get probed. For what it's worth, this now (as opposed to in December/BETA4) seems to happen for only 'sound' and 'netgraph' of the modules I normally load at boot time. The modules I use that are not those two and do not depend on them, atapicam and geom_journal, do not cause the trap/panic. To be clear, I use 'sound' and 'netgraph' only because 'snd_ich' and 'ng_ubt' require them, but even if I only load 'sound' or 'netgraph' in loader.conf and not the modules that depend on them, the trap still occurs. Doing a verbose boot would probably also help. I'll do that when I get a chance to capture output better. For now, here's a stack trace from 'boot -D': KDB: stack backtrace: db_trace_self_wrapper() at 0x801bec2a = db_trace_self_wrapper+0x2a panic() at 0x8048946a = panic+0x17a trap_fatal() at 0x80747abf = trap_fatal+0x29f trap_pfault() at 0x80747ea4 = trap_pfault+0x294 trap() at 0x8074886a = trap+0x2fa calltrap() at 0x8072daee = calltrap+0x8 --- trap 0xc, rip = 0x8047d77e, rsp = 0xa062eb40, rbp = 0xa062eb60 --- _mtx_lock_sleep() at 0x8047d77e = _mtx_lock_sleep+0x4e ata_interrupt() at 0x80234184 = ata_interrupt+0x164 ata_generic_intr() at 0x80234e5f = ata_generic_intr+0x2f ithread_loop() at 0x8046ccf0 = ithread_loop+0x180 fork_exit() at 0x8046987e = fork_exit+0x11e fork_trampoline() at 0x8072debe = fork_trampoline+0xe --- trap 0, rip = 0, rsp = 0xa062ed30, rbp = 0 --- /boot/loader.conf: sound_load=YES atapicam_load=YES geom_journal_load=YES This is a hand transcription (with checked and double-checked addresses), as I don't have an available device for capturing serial console output at the moment. Is this what you need, or is there something else I should do? Thanks, Jeff ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Scheduler in Various Docs
Jason C. Wells wrote:
X-Face:
#0jV*~a}VtKS-E/!EJpH('H1Va}24dxF0oT+.R3Gu8C;xhSC+|+H84YLbMvphuRT4cp3.|8EN_(2Eix/6{.Up~u`a^}0Lnb+9Fw|[EMAIL
PROTECTED]ZwA]5%_AU?}DezfE1!H?3E$!Yve7.O+..Jnb4:'6Ey_]FtFzU9=*l$1p/@gA,Ze^5]+r(XJ+m7`/vMDc$'wy|$nE`e
The comments regarding SCHED_ULE and SCHED_4BSD are inconsistent with
information found in the email archives. LINT says ULE is experimental.
The handbook doesn't mention ULE at all. The archives say ULE is the
new recommended scheduler.
If ULE is in fact the current recommendation, then a few docs need to be
updated.
I noticed this in the sched_ule(4) man page as well. ULE is said to
be experimental and refers the reader to a non-existent BUGS section
(removed before RELENG_7 was created). The commit log also states
that ULE is no longer buggy or experimental, so at the very least,
the man page is slightly inconsistent with itself and its last commit
log.
Jeff
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
7.0-BETA4 amd64 panic during boot-time device probe
I've upgraded my AMD64 box from RELENG_6 (csup on Nov. 30) to RELENG_7 (csup around 01:30 UTC Dec. 7) and am getting a kernel panic when I try to boot with seemingly any one module specified in /boot/loader.conf (XXX_load=YES). It seems to occur near the end of device probing, just before it detects the disks. This panic does not happen if no modules are specified to be loaded in /boot/loader.conf. There is also no panic if I boot without loader.conf modules but then load the modules with kldload. This problem was originally happening when I was attempting to go from 6-STABLE to 7.0-BETA4, and rebuilding 7.0B4 under 7.0B4 yields the same result. Here is console output from the panic and partial dmesg output from the successful boot (similar up to a point, some context included). I couldn't get my serial port to accept input at the debugger prompt, and my keyboard (USB) can't even Press a key on the console to reboot when I have a non-ddb/kdb/etc kernel, so I couldn't do anything once I got into the debugger. Hopefully what's below has some useful information--if not, I'll be happy to try to get it. On the subject of the kernel debugger, I used GENERIC plus options DDB options DDB_NUMSYM options GDB options KDB options KDB_TRACE and set hint.sio.0.flags=0x80 in /boot/device.hints. What am I missing to allow serial input when the debugger starts? thanks for any help, Jeff === panic === GDB: debug ports: sio GDB: current port: sio KDB: debugger backends: ddb gdb KDB: current backend: ddb Copyright (c) 1992-2007 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 is a registered trademark of The FreeBSD Foundation. FreeBSD 7.0-BETA4 #0: Thu Dec 6 23:35:34 EST 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC_DBG Timecounter i8254 frequency 1193182 Hz quality 0 CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 4400+ (2211.34-MHz K8-class CPU) Origin = AuthenticAMD Id = 0x20f32 Stepping = 2 Features=0x178bfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT Features2=0x1SSE3 AMD Features=0xe2500800SYSCALL,NX,MMX+,FFXSR,LM,3DNow!+,3DNow! AMD Features2=0x3LAHF,CMP Cores per package: 2 usable memory = 1060421632 (1011 MB) avail memory = 1021755392 (974 MB) ACPI APIC Table: Nvidia AWRDACPI FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0: Changing APIC ID to 2 ioapic0 Version 1.1 irqs 0-23 on motherboard kbd1 at kbdmux0 ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) acpi0: Nvidia AWRDACPI on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: reservation of 0, a (3) failed acpi0: reservation of 10, 3fef (3) failed Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x4008-0x400b on acpi0 cpu0: ACPI CPU on acpi0 powernow0: Cool`n'Quiet K8 on cpu0 device_attach: powernow0 attach returned 6 cpu1: ACPI CPU on acpi0 powernow1: Cool`n'Quiet K8 on cpu1 device_attach: powernow1 attach returned 6 acpi_button0: Power Button on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 pci0: memory at device 0.0 (no driver attached) isab0: PCI-ISA bridge at device 1.0 on pci0 isa0: ISA bus on isab0 pci0: serial bus, SMBus at device 1.1 (no driver attached) ohci0: OHCI (generic) USB controller mem 0xdc004000-0xdc004fff irq 21 at device 2.0 on pci0 ohci0: [GIANT-LOCKED] ohci0: [ITHREAD] usb0: OHCI version 1.0, legacy support usb0: SMM does not respond, resetting usb0: OHCI (generic) USB controller on ohci0 usb0: USB revision 1.0 uhub0: nVidia OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 on usb0 uhub0: 10 ports with 10 removable, self powered ehci0: NVIDIA nForce4 USB 2.0 controller mem 0xfeb0-0xfeb000ff irq 22 at device 2.1 on pci0 ehci0: [GIANT-LOCKED] ehci0: [ITHREAD] usb1: EHCI version 1.0 usb1: companion controller, 4 ports each: usb0 usb1: NVIDIA nForce4 USB 2.0 controller on ehci0 usb1: USB revision 2.0 uhub1: nVidia EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 on usb1 uhub1: 10 ports with 10 removable, self powered pcm0: nVidia nForce4 port 0xdc00-0xdcff,0xe000-0xe0ff mem 0xdc003000-0xdc003fff irq 23 at device 4.0 on pci0 pcm0: [ITHREAD] pcm0: Avance Logic ALC850 AC97 Codec atapci0: nVidia nForce CK804 UDMA133 controller port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xf000-0xf00f at device 6.0 on pci0 ata0: ATA channel 0 on atapci0 ata0: [ITHREAD] ata1: ATA channel 1 on atapci0 ata1: [ITHREAD] atapci1: nVidia nForce CK804 SATA300 controller port 0x9f0-0x9f7,0xbf0-0xbf3,0x970-0x977,0xb70-0xb73,0xd800-0xd80f mem 0xdc002000-0xdc002fff irq 21 at device 7.0 on pci0 atapci1: [ITHREAD] ata2: ATA channel 0 on atapci1 ata2: [ITHREAD] ata3: ATA channel 1 on atapci1 ata3: [ITHREAD] atapci2: nVidia nForce CK804 SATA300 controller
