Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver
Ian FREISLICH wrote: Weongyo Jeong wrote: Do you want me to test anything else ? OK. The patch is ready to test. Could you please test it with attached patch? No panic this time. I also don't get these messages any more: May 10 23:25:36 mini kernel: bwn0: unsupported rate 0 May 10 23:26:13 mini last message repeated 2 times May 10 23:28:29 mini last message repeated 320 times May 10 23:28:32 mini last message repeated 61 times May 10 23:29:42 mini shutdown: reboot by ianf: It still doesn't associate with my AP until I destroy the wlan interface and create it again: But, after about 12 hours it reduced the rate to 36mbit/s OFDM with large amounts of time either not transmitting or not recieving - 86% packet loss over 5 minutes. Ian -- Ian Freislich ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Panic @r207844; current process: flowcleaner Fatal trap 12: page fault while in kernel mode
On Mon, May 10, 2010 at 02:32:14PM -0700, K. Macy wrote: Could you please try with 207902? ... I saved that environment (documented elsewhere ini the thread), then performed the normal (for me) daily update, this time, to r207911. Again, I see a panic during transition from single-user mode to multi-user mode: ... 3 Select option, [Enter] for default 3 3 or [Space] to pause timer 9 3 @DY GDB: no debug ports present KDB: debugger backends: ddb KDB: current backend: ddb Copyright (c) 1992-2010 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 9.0-CURRENT #156 r207911: Tue May 11 05:55:18 PDT 2010 r...@freebeast.catwhisker.org:/usr/obj/usr/src/sys/GENERIC i386 WARNING: WITNESS option enabled, expect reduced performance. Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(TM) CPU 3.60GHz (3614.55-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf41 Family = f Model = 4 Stepping = 1 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0x659dSSE3,DTES64,MON,DS_CPL,EST,TM2,CNXT-ID,CX16,xTPR AMD Features=0x2010NX,LM TSC: P-state invariant real memory = 2147483648 (2048 MB) avail memory = 2086129664 (1989 MB) ACPI APIC Table: PTLTD APIC FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs FreeBSD/SMP: 2 package(s) x 1 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 6 ioapic0 Version 2.0 irqs 0-23 on motherboard ioapic1 Version 2.0 irqs 24-47 on motherboard ioapic2 Version 2.0 irqs 48-71 on motherboard kbd1 at kbdmux0 acpi0: PTLTD RSDT on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x1008-0x100b on acpi0 cpu0: ACPI CPU on acpi0 cpu1: ACPI CPU on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 pci0: unknown at device 0.1 (no driver attached) pci0: base peripheral at device 1.0 (no driver attached) pcib1: ACPI PCI-PCI bridge irq 16 at device 2.0 on pci0 pci1: ACPI PCI bus on pcib1 pcib2: ACPI PCI-PCI bridge at device 0.0 on pci1 pci2: ACPI PCI bus on pcib2 aac0: Adaptec SCSI RAID 2200S mem 0xdc00-0xdfff irq 24 at device 1.0 on pci2 aac0: Enable Raw I/O aac0: New comm. interface enabled aac0: [ITHREAD] aac0: Adaptec 2200S, aac driver 2.1.9-1 aacp0: SCSI Passthrough Bus on aac0 aacp1: SCSI Passthrough Bus on aac0 pcib3: ACPI PCI-PCI bridge at device 0.2 on pci1 pci3: ACPI PCI bus on pcib3 em0: Intel(R) PRO/1000 Legacy Network Connection 1.0.1 port 0x2000-0x203f mem 0xd820-0xd821 irq 54 at device 2.0 on pci3 em0: [FILTER] em0: Ethernet address: 00:30:48:2d:32:6a em1: Intel(R) PRO/1000 Legacy Network Connection 1.0.1 port 0x2040-0x207f mem 0xd822-0xd823 irq 55 at device 2.1 on pci3 em1: [FILTER] em1: Ethernet address: 00:30:48:2d:32:6b pcib4: ACPI PCI-PCI bridge irq 16 at device 4.0 on pci0 pci4: ACPI PCI bus on pcib4 pcib5: ACPI PCI-PCI bridge irq 16 at device 6.0 on pci0 pci5: ACPI PCI bus on pcib5 uhci0: Intel 82801EB (ICH5) USB controller USB-A port 0x1400-0x141f irq 16 at device 29.0 on pci0 uhci0: [ITHREAD] usbus0: Intel 82801EB (ICH5) USB controller USB-A on uhci0 uhci1: Intel 82801EB (ICH5) USB controller USB-B port 0x1420-0x143f irq 19 at device 29.1 on pci0 uhci1: [ITHREAD] usbus1: Intel 82801EB (ICH5) USB controller USB-B on uhci1 uhci2: Intel 82801EB (ICH5) USB controller USB-C port 0x1440-0x145f irq 18 at device 29.2 on pci0 uhci2: [ITHREAD] usbus2: Intel 82801EB (ICH5) USB controller USB-C on uhci2 uhci3: Intel 82801EB (ICH5) USB controller USB-D port 0x1460-0x147f irq 16 at device 29.3 on pci0 uhci3: [ITHREAD] usbus3: Intel 82801EB (ICH5) USB controller USB-D on uhci3 ehci0: Intel 82801EB/R (ICH5) USB 2.0 controller mem 0xd8001000-0xd80013ff irq 23 at device 29.7 on pci0 ehci0: [ITHREAD] usbus4: EHCI version 1.0 usbus4: Intel 82801EB/R (ICH5) USB 2.0 controller on ehci0 pcib6: ACPI PCI-PCI bridge at device 30.0 on pci0 pci6: ACPI PCI bus on pcib6 vgapci0: VGA-compatible display port 0x3000-0x30ff mem 0xd900-0xd9ff,0xd830-0xd8300fff irq 17 at device 1.0 on pci6 isab0: PCI-ISA bridge at device 31.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel ICH5 UDMA100 controller port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x14a0-0x14af at device 31.1 on pci0 ata0: ATA channel 0 on atapci0 ata0: [ITHREAD] ata1: ATA channel 1 on atapci0 ata1: [ITHREAD] pci0: serial bus, SMBus at device 31.3 (no driver attached) acpi_button0: Power Button on acpi0 atrtc0: AT realtime clock port 0x70-0x77 irq 8 on acpi0 atkbdc0: Keyboard controller (i8042) port 0x60,0x64 irq 1 on acpi0 atkbd0: AT Keyboard irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0:
Re: HEADS UP: 64-bit quotas going in to head today
Ivan Voras ivo...@freebsd.org writes: Just wondering - does the quota code have that much impact on the file system that it's still today left out of the GENERIC kernel? It adds quite a bit of code to pretty much every UFS VOP. I haven't benchmarked or profiled it, so I have no idea how much it affects performance, but I suspect it's noticeable for disk-intensive workloads such as busy databases. DES -- Dag-Erling Smørgrav - d...@des.no ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
[PATCH:] psm(4) IntelliMouse Explorer KVM hack breaks my mouse
(..and older vbox versions.)
Hi!
I just saw this vbox ticket:
http://www.virtualbox.org/ticket/6488
(`Mouse wheel scrolling interpredted as click events in guest - fixed
after the 3.1.6 release')
..which sounded just like what a physical mouse I have (MS `IntelliMouse
Optical 1.1A' according to whats printed on the bottom) did outside of
a VM too, so I got curious and patched my psm driver to disable the KVM
hack mentioned in that ticket which was introduced back in Apr 2000 by
this commit:
http://svn.freebsd.org/viewvc/base?view=revisionrevision=58923
(`Add temporary workaround to fool some clever KVM switch products
which think they know the IntelliMouse 4-byte packet and believe,
wrongly, that any other protocols use 3-byte packets.')
..and indeed, now the stray click events are gone for me too! :)
So now I made a patch that allows disabling that KVM hack via device
hints, appended below. (hint.psm.0.flags=0x1 - or do you guys
think the hack should be disabled by default instead?)
Cheers,
Juergen
Index: src/sys/dev/atkbdc/psm.c
===
RCS file: /home/scvs/src/sys/dev/atkbdc/psm.c,v
retrieving revision 1.104.2.2
diff -u -p -r1.104.2.2 psm.c
--- src/sys/dev/atkbdc/psm.c20 Aug 2009 20:23:28 - 1.104.2.2
+++ src/sys/dev/atkbdc/psm.c11 May 2010 18:06:01 -
@@ -326,6 +326,7 @@ static devclass_t psm_devclass;
#definePSM_CONFIG_HOOKRESUME 0x2000 /* hook the system resume event
*/
#definePSM_CONFIG_INITAFTERSUSPEND 0x4000 /* init the device at the
resume event */
#definePSM_CONFIG_SYNCHACK 0x8000 /* enable `out-of-sync' hack */
+#definePSM_CONFIG_NOKVMHACK0x1 /* disable IntelliMouse
Explorer KVM hack */
#definePSM_CONFIG_FLAGS\
(PSM_CONFIG_RESOLUTION | \
@@ -337,7 +338,8 @@ static devclass_t psm_devclass;
PSM_CONFIG_FORCETAP | \
PSM_CONFIG_IGNPORTERROR | \
PSM_CONFIG_HOOKRESUME |\
-PSM_CONFIG_INITAFTERSUSPEND)
+PSM_CONFIG_INITAFTERSUSPEND | \
+PSM_CONFIG_NOKVMHACK)
/* other flags (flags) */
#definePSM_FLAGS_FINGERDOWN0x0001 /* VersaPad finger down */
@@ -3779,20 +3781,23 @@ enable_msexplorer(struct psm_softc *sc)
sc-hw.hwid = id;
sc-hw.buttons = 5; /* IntelliMouse Explorer XXX */
- /*
-* XXX: this is a kludge to fool some KVM switch products
-* which think they are clever enough to know the 4-byte IntelliMouse
-* protocol, and assume any other protocols use 3-byte packets.
-* They don't convey 4-byte data packets from the IntelliMouse Explorer
-* correctly to the host computer because of this!
-* The following sequence is actually IntelliMouse's wake up
-* sequence; it will make the KVM think the mouse is IntelliMouse
-* when it is in fact IntelliMouse Explorer.
-*/
- for (i = 0; i sizeof(rate0)/sizeof(rate0[0]); ++i)
- if (set_mouse_sampling_rate(kbdc, rate0[i]) != rate0[i])
- break;
- id = get_aux_id(kbdc);
+ if (!(sc-config PSM_CONFIG_NOKVMHACK)) {
+ /*
+* XXX: this is a kludge to fool some KVM switch products
+* which think they are clever enough to know the 4-byte
+* IntelliMouse protocol, and assume any other protocols
+* use 3-byte packets.
+* They don't convey 4-byte data packets from the IntelliMouse
+* Explorer correctly to the host computer because of this!
+* The following sequence is actually IntelliMouse's wake up
+* sequence; it will make the KVM think the mouse is
+* IntelliMouse when it is in fact IntelliMouse Explorer.
+*/
+ for (i = 0; i sizeof(rate0)/sizeof(rate0[0]); ++i)
+ if (set_mouse_sampling_rate(kbdc, rate0[i]) != rate0[i])
+ break;
+ id = get_aux_id(kbdc);
+ }
return (TRUE);
}
Index: src/share/man/man4/psm.4
===
RCS file: /home/scvs/src/share/man/man4/psm.4,v
retrieving revision 1.49.2.1
diff -u -p -r1.49.2.1 psm.4
--- src/share/man/man4/psm.43 Aug 2009 08:13:06 - 1.49.2.1
+++ src/share/man/man4/psm.411 May 2010 18:04:16 -
@@ -349,6 +349,11 @@ after the `resume' event.
It has no effect unless the
.Em HOOKRESUME
flag is set as well.
+.It bit 16 NOKVMHACK
+This flag disables the IntelliMouse Explorer protocol KVM switch
+workaround that makes some virtual machine's mouse emulations as well
+as at least one physical IntelliMouse Optical model misbehave
+(causing the scroll wheel to produce stray click events.)
.El
.Sh LOADER TUNABLES
Extended support for Synaptics touchpads can be enabled by setting
Addition of lzma/xz compression to HEAD
Hello! Just FYI: noticed addition of lzma directory to BSD.include.dist mtree file. Well, now it seems to work! /* Test file size 264 MiB */ [wep4035] ~ ll /usr/local/tinderbox/jails/9-amd64/9-amd64.tar -rw-r--r-- 1 root wheel 277209600 Apr 20 20:58 /usr/local/tinderbox/jails/9-amd64/9-amd64.tar /* Cache file in memory */ [wep4035] ~ cat /usr/local/tinderbox/jails/9-amd64/9-amd64.tar /dev/null /* 30 seconds to gzip it */ [wep4035] ~ time tar -cvzf 9-amd64.tar.tar.gz /usr/local/tinderbox/jails/9-amd64/9-amd64.tar tar: Removing leading '/' from member names a usr/local/tinderbox/jails/9-amd64/9-amd64.tar 30.043u 0.541s 0:15.32 199.6% 37+2093k 0+747io 0pf+0w /* 64 seconds to bzip2 it */ [wep4035] ~ time tar -cvjf 9-amd64.tar.tar.bz2 /usr/local/tinderbox/jails/9-amd64/9-amd64.tar tar: Removing leading '/' from member names a usr/local/tinderbox/jails/9-amd64/9-amd64.tar 63.454u 0.686s 0:32.09 199.8% 37+2108k 0+650io 1pf+0w /* And 140 seconds to xz it */ [wep4035] ~ time tar -cvJf 9-amd64.tar.tar.xz /usr/local/tinderbox/jails/9-amd64/9-amd64.tar tar: Removing leading '/' from member names a usr/local/tinderbox/jails/9-amd64/9-amd64.tar 277.625u 0.857s 2:19.26 199.9% 37+2092k 0+432io 0pf+0w /* Resulting sizes : */ [wep4035] ~ ll 9-amd64.tar.tar.* -rw-r--r-- 1 lexx lexx 84830128 May 11 21:07 9-amd64.tar.tar.bz2 -rw-r--r-- 1 lexx lexx 97667581 May 11 21:07 9-amd64.tar.tar.gz -rw-r--r-- 1 lexx lexx 56366908 May 11 21:10 9-amd64.tar.tar.xz /* 3.5 seconds to gunzip the file (mostly IO-limited) */ [wep4035] ~ cat 9-amd64.tar.tar.gz /dev/null [wep4035] ~ time tar -xvf 9-amd64.tar.tar.gz x usr/local/tinderbox/jails/9-amd64/9-amd64.tar 2.721u 0.747s 0:03.54 97.7% 42+2365k 3+2116io 0pf+0w [wep4035] ~ rm -R usr/ /* 18 seconds to bunzip2 it */ [wep4035] ~ cat 9-amd64.tar.tar.bz2 /dev/null [wep4035] ~ time tar -xvf 9-amd64.tar.tar.bz2 x usr/local/tinderbox/jails/9-amd64/9-amd64.tar 18.136u 0.999s 0:09.59 199.3% 37+2110k 1+2116io 0pf+0w [wep4035] ~ rm -R usr/ /* And only 10 seconds to xzdec it */ [wep4035] ~ cat 9-amd64.tar.tar.xz /dev/null [wep4035] ~ time tar -xvf 9-amd64.tar.tar.xz x usr/local/tinderbox/jails/9-amd64/9-amd64.tar 10.304u 0.771s 0:05.59 198.0% 38+2164k 3+2116io 0pf+0w [wep4035] ~ rm -R usr/ Thanks to all involved in bringing it to HEAD! Alexey. P.S. I'm not claiming any statistical validity of provided timings nor that the testing procedure is correct. It is just to show that tar in HEAD now works with lzma/xz compression. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: HEADS UP: 64-bit quotas going in to head today
On Tue, May 11, 2010 at 07:33:00PM +0200, Dag-Erling Sm??rgrav wrote: Ivan Voras ivo...@freebsd.org writes: Just wondering - does the quota code have that much impact on the file system that it's still today left out of the GENERIC kernel? It adds quite a bit of code to pretty much every UFS VOP. I haven't benchmarked or profiled it, so I have no idea how much it affects performance, but I suspect it's noticeable for disk-intensive workloads such as busy databases. No, it does not. Essentially, it adds one or two function calls per vop that allocate or deallocate blocks or inodes, and the function bodies verify two array members and return if those are NULL. My assertion is that this overhead is negligible. I intended to move quota code to kern/vfs_quota.c, because it actually is fs-agnostic, and can be used by any fs that does block and inode-based allocation of some space. In particular, tmpfs could use it. After that, I planned to enable option QUOTA for GENERIC. Also please note that ufs_quota.c is compiled into the kernel unconditionally (or rather, conditional on option UFS), and only hooks are placed under #ifdef QUOTA. pgpzLj9ZyKRzL.pgp Description: PGP signature
Re: fsck unable to read disk sectors
the problem is getting more awkward. if i do `fsck /dev/label/rootfs` fsck complains that it cannot read a specific sector of my hdd as i mentioned before. if i run fsck on the device node directly using `fsck /dev/ada0p3` however, fsck succeeds. what i did was to boot into single user mode with / being mounted read only. for some reason however fsck will check /dev/label/rootfs in write mode, but if i want fsck to check ada0p3 it will only do so in read mode. this looks like something is really broken. right now the only way to get the clean flag set on my hdd is to boot from a livefs cd and then run `fsck /dev/ada0p3` (again: `fsck /dev/label/rootfs` will NOT succeed). this is the output of `glabel status` btw: Name Status Components label/boot N/A ada0p1 gptid/e52df583-e446-11de-bb92-000fb58207c8 N/A ada0p1 label/swap N/A ada0p2 label/rootfs N/A ada0p3 cheers. On Tue, Mar 30, 2010 at 2:08 AM, Paul B Mahol one...@gmail.com wrote: On 3/29/10, Alexander Best alexbes...@wwu.de wrote: hi there, when doing fsck on my / fs i get this error: Cannot Read BLK. 471617640 and The Following Disk Sectors could not be read: 471617643. after this message the partition gets marked dirty. i performed the following steps to verify the problem: 1) dd if=/dev/ada0 of=/dev/null bs=1m 2) fsck / under freebsd 7 3) mount -u -o snapshot /.snap/snapshot1 / fsck_ffs /.snap/snapshot1 all three steps showed no problem with that harddrive whatsoever. also smartd doesn't complain about anything. i'm running HEAD (r205860) on amd64. this is the output of `dmesg -a|grep ada0`: ada0 at ahcich2 bus 0 scbus3 target 0 lun 0 ada0: SAMSUNG SP2504C VT100-50 ATA-7 SATA 2.x device ada0: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) ada0: Command Queueing enabled ada0: 238474MB (488395055 512 byte sectors: 16H 63S/T 16383C) Last time I tried ahci on dead disk it did not complained at all (usually I get dead LBA listed on console). -- Alexander Best ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: fsck unable to read disk sectors
i've posted a log here which is pretty self explanatory: http://pastebin.com/tn3NiDDW On Tue, May 11, 2010 at 10:13 PM, Alexander Best alexbes...@uni-muenster.de wrote: the problem is getting more awkward. if i do `fsck /dev/label/rootfs` fsck complains that it cannot read a specific sector of my hdd as i mentioned before. if i run fsck on the device node directly using `fsck /dev/ada0p3` however, fsck succeeds. what i did was to boot into single user mode with / being mounted read only. for some reason however fsck will check /dev/label/rootfs in write mode, but if i want fsck to check ada0p3 it will only do so in read mode. this looks like something is really broken. right now the only way to get the clean flag set on my hdd is to boot from a livefs cd and then run `fsck /dev/ada0p3` (again: `fsck /dev/label/rootfs` will NOT succeed). this is the output of `glabel status` btw: Name Status Components label/boot N/A ada0p1 gptid/e52df583-e446-11de-bb92-000fb58207c8 N/A ada0p1 label/swap N/A ada0p2 label/rootfs N/A ada0p3 cheers. On Tue, Mar 30, 2010 at 2:08 AM, Paul B Mahol one...@gmail.com wrote: On 3/29/10, Alexander Best alexbes...@wwu.de wrote: hi there, when doing fsck on my / fs i get this error: Cannot Read BLK. 471617640 and The Following Disk Sectors could not be read: 471617643. after this message the partition gets marked dirty. i performed the following steps to verify the problem: 1) dd if=/dev/ada0 of=/dev/null bs=1m 2) fsck / under freebsd 7 3) mount -u -o snapshot /.snap/snapshot1 / fsck_ffs /.snap/snapshot1 all three steps showed no problem with that harddrive whatsoever. also smartd doesn't complain about anything. i'm running HEAD (r205860) on amd64. this is the output of `dmesg -a|grep ada0`: ada0 at ahcich2 bus 0 scbus3 target 0 lun 0 ada0: SAMSUNG SP2504C VT100-50 ATA-7 SATA 2.x device ada0: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) ada0: Command Queueing enabled ada0: 238474MB (488395055 512 byte sectors: 16H 63S/T 16383C) Last time I tried ahci on dead disk it did not complained at all (usually I get dead LBA listed on console). -- Alexander Best -- Alexander Best ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
[mini headsup] updating from 7.x to -CURRENT after lzma import
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, The recent lzma import has enabled libarchive's lzma support. However, it have come to our attention that building -HEAD on earlier FreeBSD versions (specifically, 7.x after 700044 through 8.x before 800022) have been broken. The reason behind this is that 'make buildworld' will build a new ar(1) binary which links to libarchive, causing build to break on these systems. A hack-ish patch can be used to relieve this: http://people.freebsd.org/~delphij/for_review/patch-lzmabuild.diff Alternatively, one can update to 8-STABLE before jumping to 9-CURRENT. Another way to work around this is to build and install lzma static library before doing 'make buildworld': cd /usr/src make buildenv cd lib/liblzma make obj make depend make -DNO_PIC -DWITHOUT_PROFILE -DNO_SHARED all make -DNO_PIC -DWITHOUT_PROFILE -DNO_SHARED install We are working on a better solution for this and sorry for the breakage. Cheers, - -- Xin LI delp...@delphij.nethttp://www.delphij.net/ FreeBSD - The Power to Serve! Live free or die -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.14 (FreeBSD) iQEcBAEBAgAGBQJL6epPAAoJEATO+BI/yjfB37MIAJ+Xy9sftRRwdc1n61UDxeGd iy08OvhZesQltDOIaezFSET250HVtUG0Z+aenaxgMV8tzfRysK1FNdBozWCE0hbY cgyIy/bi1JOEP2F2qiFLyKIRtZSSoMJkMEegKEFlRC21rQBmWCRBK0zPrnq/sgTS qyLB83QrlJsH7tLS301ac0r8bK1TdvOc21EyXvtbmWa5fZjpJMrwwhcSevUgOAci DYixML6SMLcxai/kz3lAbUbxXiecm0tg9uUYQR7T94nCFpxde5tu8KMNx4jsoC8x cS2VdToswpCtIVc2PuTotl3A1WGMUFUM45KWk2UzBP40nn+r0G/cVpCgx/7BpzY= =nPLF -END PGP SIGNATURE- ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: fsck unable to read disk sectors
On Tue, May 11, 2010 at 10:15:13PM +0200, Alexander Best wrote: i've posted a log here which is pretty self explanatory: http://pastebin.com/tn3NiDDW On Tue, May 11, 2010 at 10:13 PM, Alexander Best alexbes...@uni-muenster.de wrote: the problem is getting more awkward. if i do `fsck /dev/label/rootfs` fsck complains that it cannot read a specific sector of my hdd as i mentioned before. if i run fsck on the device node directly using `fsck /dev/ada0p3` however, fsck succeeds. So this is not hardware it is bad partitioning. what i did was to boot into single user mode with / being mounted read only. for some reason however fsck will check /dev/label/rootfs in write mode, but if i want fsck to check ada0p3 it will only do so in read mode. this looks like something is really broken. right now the only way to get the clean flag set on my hdd is to boot from a livefs cd and then run `fsck /dev/ada0p3` (again: `fsck /dev/label/rootfs` will NOT succeed). One of the typical problems users have is that they forget that adding a label takes one sector, so the labeled device is smaller. This is no problem if you create the filesystem on the labeled drive, but often enough people add the label after creating the filesystem. Everything seems to work fine until the FS decides to use that special sector. I wouldn't add a label for ufs anyway, since UFS has labeling itself, which is also handled by glabel module and doesn't require extra space. Just setup the ufs label with tunefs -L and use the resulting /dev/ufs/... device. You only need extra label for swap, but this is not problem, since it has no persistent ondisk structures. this is the output of `glabel status` btw: Name Status Components label/boot N/A ada0p1 gptid/e52df583-e446-11de-bb92-000fb58207c8 N/A ada0p1 label/swap N/A ada0p2 label/rootfs N/A ada0p3 cheers. On Tue, Mar 30, 2010 at 2:08 AM, Paul B Mahol one...@gmail.com wrote: On 3/29/10, Alexander Best alexbes...@wwu.de wrote: hi there, when doing fsck on my / fs i get this error: Cannot Read BLK. 471617640 and The Following Disk Sectors could not be read: 471617643. after this message the partition gets marked dirty. i performed the following steps to verify the problem: 1) dd if=/dev/ada0 of=/dev/null bs=1m 2) fsck / under freebsd 7 3) mount -u -o snapshot /.snap/snapshot1 / fsck_ffs /.snap/snapshot1 all three steps showed no problem with that harddrive whatsoever. also smartd doesn't complain about anything. i'm running HEAD (r205860) on amd64. this is the output of `dmesg -a|grep ada0`: ada0 at ahcich2 bus 0 scbus3 target 0 lun 0 ada0: SAMSUNG SP2504C VT100-50 ATA-7 SATA 2.x device ada0: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) ada0: Command Queueing enabled ada0: 238474MB (488395055 512 byte sectors: 16H 63S/T 16383C) Last time I tried ahci on dead disk it did not complained at all (usually I get dead LBA listed on console). -- B.Walter be...@bwct.de http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Panic @r207844; current process: flowcleaner Fatal trap 12: page fault while in kernel mode
Please try 207949 Thanks, Kip On Tue, May 11, 2010 at 6:18 AM, David Wolfskill da...@catwhisker.org wrote: On Mon, May 10, 2010 at 02:32:14PM -0700, K. Macy wrote: Could you please try with 207902? ... I saved that environment (documented elsewhere ini the thread), then performed the normal (for me) daily update, this time, to r207911. Again, I see a panic during transition from single-user mode to multi-user mode: ... 3 Select option, [Enter] for default 3 3 or [Space] to pause timer 9 3 �...@dy GDB: no debug ports present KDB: debugger backends: ddb KDB: current backend: ddb Copyright (c) 1992-2010 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 9.0-CURRENT #156 r207911: Tue May 11 05:55:18 PDT 2010 r...@freebeast.catwhisker.org:/usr/obj/usr/src/sys/GENERIC i386 WARNING: WITNESS option enabled, expect reduced performance. Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(TM) CPU 3.60GHz (3614.55-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf41 Family = f Model = 4 Stepping = 1 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0x659dSSE3,DTES64,MON,DS_CPL,EST,TM2,CNXT-ID,CX16,xTPR AMD Features=0x2010NX,LM TSC: P-state invariant real memory = 2147483648 (2048 MB) avail memory = 2086129664 (1989 MB) ACPI APIC Table: PTLTD APIC FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs FreeBSD/SMP: 2 package(s) x 1 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 6 ioapic0 Version 2.0 irqs 0-23 on motherboard ioapic1 Version 2.0 irqs 24-47 on motherboard ioapic2 Version 2.0 irqs 48-71 on motherboard kbd1 at kbdmux0 acpi0: PTLTD RSDT on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x1008-0x100b on acpi0 cpu0: ACPI CPU on acpi0 cpu1: ACPI CPU on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 pci0: unknown at device 0.1 (no driver attached) pci0: base peripheral at device 1.0 (no driver attached) pcib1: ACPI PCI-PCI bridge irq 16 at device 2.0 on pci0 pci1: ACPI PCI bus on pcib1 pcib2: ACPI PCI-PCI bridge at device 0.0 on pci1 pci2: ACPI PCI bus on pcib2 aac0: Adaptec SCSI RAID 2200S mem 0xdc00-0xdfff irq 24 at device 1.0 on pci2 aac0: Enable Raw I/O aac0: New comm. interface enabled aac0: [ITHREAD] aac0: Adaptec 2200S, aac driver 2.1.9-1 aacp0: SCSI Passthrough Bus on aac0 aacp1: SCSI Passthrough Bus on aac0 pcib3: ACPI PCI-PCI bridge at device 0.2 on pci1 pci3: ACPI PCI bus on pcib3 em0: Intel(R) PRO/1000 Legacy Network Connection 1.0.1 port 0x2000-0x203f mem 0xd820-0xd821 irq 54 at device 2.0 on pci3 em0: [FILTER] em0: Ethernet address: 00:30:48:2d:32:6a em1: Intel(R) PRO/1000 Legacy Network Connection 1.0.1 port 0x2040-0x207f mem 0xd822-0xd823 irq 55 at device 2.1 on pci3 em1: [FILTER] em1: Ethernet address: 00:30:48:2d:32:6b pcib4: ACPI PCI-PCI bridge irq 16 at device 4.0 on pci0 pci4: ACPI PCI bus on pcib4 pcib5: ACPI PCI-PCI bridge irq 16 at device 6.0 on pci0 pci5: ACPI PCI bus on pcib5 uhci0: Intel 82801EB (ICH5) USB controller USB-A port 0x1400-0x141f irq 16 at device 29.0 on pci0 uhci0: [ITHREAD] usbus0: Intel 82801EB (ICH5) USB controller USB-A on uhci0 uhci1: Intel 82801EB (ICH5) USB controller USB-B port 0x1420-0x143f irq 19 at device 29.1 on pci0 uhci1: [ITHREAD] usbus1: Intel 82801EB (ICH5) USB controller USB-B on uhci1 uhci2: Intel 82801EB (ICH5) USB controller USB-C port 0x1440-0x145f irq 18 at device 29.2 on pci0 uhci2: [ITHREAD] usbus2: Intel 82801EB (ICH5) USB controller USB-C on uhci2 uhci3: Intel 82801EB (ICH5) USB controller USB-D port 0x1460-0x147f irq 16 at device 29.3 on pci0 uhci3: [ITHREAD] usbus3: Intel 82801EB (ICH5) USB controller USB-D on uhci3 ehci0: Intel 82801EB/R (ICH5) USB 2.0 controller mem 0xd8001000-0xd80013ff irq 23 at device 29.7 on pci0 ehci0: [ITHREAD] usbus4: EHCI version 1.0 usbus4: Intel 82801EB/R (ICH5) USB 2.0 controller on ehci0 pcib6: ACPI PCI-PCI bridge at device 30.0 on pci0 pci6: ACPI PCI bus on pcib6 vgapci0: VGA-compatible display port 0x3000-0x30ff mem 0xd900-0xd9ff,0xd830-0xd8300fff irq 17 at device 1.0 on pci6 isab0: PCI-ISA bridge at device 31.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel ICH5 UDMA100 controller port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x14a0-0x14af at device 31.1 on pci0 ata0: ATA channel 0 on atapci0 ata0: [ITHREAD] ata1: ATA channel 1 on atapci0 ata1: [ITHREAD] pci0: serial bus, SMBus at device 31.3 (no driver attached)
Re: [mini headsup] updating from 7.x to -CURRENT after lzma import
On Tue, May 11, 2010 at 04:37:51PM -0700, Xin LI wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, The recent lzma import has enabled libarchive's lzma support. However, it have come to our attention that building -HEAD on earlier FreeBSD versions (specifically, 7.x after 700044 through 8.x before 800022) have been broken. The reason behind this is that 'make buildworld' will build a new ar(1) binary which links to libarchive, causing build to break on these systems. A hack-ish patch can be used to relieve this: http://people.freebsd.org/~delphij/for_review/patch-lzmabuild.diff Alternatively, one can update to 8-STABLE before jumping to 9-CURRENT. Another way to work around this is to build and install lzma static library before doing 'make buildworld': cd /usr/src make buildenv cd lib/liblzma make obj make depend make -DNO_PIC -DWITHOUT_PROFILE -DNO_SHARED all make -DNO_PIC -DWITHOUT_PROFILE -DNO_SHARED install We are working on a better solution for this and sorry for the breakage. The project policy is to require at least recent STABLE_(X-1) to build HEAD. The heads up is good thing, but functionality broken is only provided on best effort basis. pgpnqdBV3VTSn.pgp Description: PGP signature
Re: Panic @r207844; current process: flowcleaner Fatal trap 12: page fault while in kernel mode
On Tue, May 11, 2010 at 08:30:09PM -0700, K. Macy wrote: Please try 207949 ... The panic (this time) didn't show up until about 10 seconds after the login: prompt showed up on the serial console. Here's what it looks like: ... 3 Select option, [Enter] for default 3 3 or [Space] to pause timer 9 3 @DY GDB: no debug ports present KDB: debugger backends: ddb KDB: current backend: ddb Copyright (c) 1992-2010 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 9.0-CURRENT #157 r207911M: Tue May 11 20:54:25 PDT 2010 r...@freebeast.catwhisker.org:/usr/obj/usr/src/sys/GENERIC i386 WARNING: WITNESS option enabled, expect reduced performance. Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(TM) CPU 3.60GHz (3614.55-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf41 Family = f Model = 4 Stepping = 1 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0x659dSSE3,DTES64,MON,DS_CPL,EST,TM2,CNXT-ID,CX16,xTPR AMD Features=0x2010NX,LM TSC: P-state invariant real memory = 2147483648 (2048 MB) avail memory = 2086129664 (1989 MB) ACPI APIC Table: PTLTD APIC FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs FreeBSD/SMP: 2 package(s) x 1 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 6 ioapic0 Version 2.0 irqs 0-23 on motherboard ioapic1 Version 2.0 irqs 24-47 on motherboard ioapic2 Version 2.0 irqs 48-71 on motherboard kbd1 at kbdmux0 acpi0: PTLTD RSDT on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x1008-0x100b on acpi0 cpu0: ACPI CPU on acpi0 cpu1: ACPI CPU on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 pci0: unknown at device 0.1 (no driver attached) pci0: base peripheral at device 1.0 (no driver attached) pcib1: ACPI PCI-PCI bridge irq 16 at device 2.0 on pci0 pci1: ACPI PCI bus on pcib1 pcib2: ACPI PCI-PCI bridge at device 0.0 on pci1 pci2: ACPI PCI bus on pcib2 aac0: Adaptec SCSI RAID 2200S mem 0xdc00-0xdfff irq 24 at device 1.0 on pci2 aac0: Enable Raw I/O aac0: New comm. interface enabled aac0: [ITHREAD] aac0: Adaptec 2200S, aac driver 2.1.9-1 aacp0: SCSI Passthrough Bus on aac0 aacp1: SCSI Passthrough Bus on aac0 pcib3: ACPI PCI-PCI bridge at device 0.2 on pci1 pci3: ACPI PCI bus on pcib3 em0: Intel(R) PRO/1000 Legacy Network Connection 1.0.1 port 0x2000-0x203f mem 0xd820-0xd821 irq 54 at device 2.0 on pci3 em0: [FILTER] em0: Ethernet address: 00:30:48:2d:32:6a em1: Intel(R) PRO/1000 Legacy Network Connection 1.0.1 port 0x2040-0x207f mem 0xd822-0xd823 irq 55 at device 2.1 on pci3 em1: [FILTER] em1: Ethernet address: 00:30:48:2d:32:6b pcib4: ACPI PCI-PCI bridge irq 16 at device 4.0 on pci0 pci4: ACPI PCI bus on pcib4 pcib5: ACPI PCI-PCI bridge irq 16 at device 6.0 on pci0 pci5: ACPI PCI bus on pcib5 uhci0: Intel 82801EB (ICH5) USB controller USB-A port 0x1400-0x141f irq 16 at device 29.0 on pci0 uhci0: [ITHREAD] usbus0: Intel 82801EB (ICH5) USB controller USB-A on uhci0 uhci1: Intel 82801EB (ICH5) USB controller USB-B port 0x1420-0x143f irq 19 at device 29.1 on pci0 uhci1: [ITHREAD] usbus1: Intel 82801EB (ICH5) USB controller USB-B on uhci1 uhci2: Intel 82801EB (ICH5) USB controller USB-C port 0x1440-0x145f irq 18 at device 29.2 on pci0 uhci2: [ITHREAD] usbus2: Intel 82801EB (ICH5) USB controller USB-C on uhci2 uhci3: Intel 82801EB (ICH5) USB controller USB-D port 0x1460-0x147f irq 16 at device 29.3 on pci0 uhci3: [ITHREAD] usbus3: Intel 82801EB (ICH5) USB controller USB-D on uhci3 ehci0: Intel 82801EB/R (ICH5) USB 2.0 controller mem 0xd8001000-0xd80013ff irq 23 at device 29.7 on pci0 ehci0: [ITHREAD] usbus4: EHCI version 1.0 usbus4: Intel 82801EB/R (ICH5) USB 2.0 controller on ehci0 pcib6: ACPI PCI-PCI bridge at device 30.0 on pci0 pci6: ACPI PCI bus on pcib6 vgapci0: VGA-compatible display port 0x3000-0x30ff mem 0xd900-0xd9ff,0xd830-0xd8300fff irq 17 at device 1.0 on pci6 isab0: PCI-ISA bridge at device 31.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel ICH5 UDMA100 controller port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x14a0-0x14af at device 31.1 on pci0 ata0: ATA channel 0 on atapci0 ata0: [ITHREAD] ata1: ATA channel 1 on atapci0 ata1: [ITHREAD] pci0: serial bus, SMBus at device 31.3 (no driver attached) acpi_button0: Power Button on acpi0 atrtc0: AT realtime clock port 0x70-0x77 irq 8 on acpi0 atkbdc0: Keyboard controller (i8042) port 0x60,0x64 irq 1 on acpi0 atkbd0: AT Keyboard irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] psm0: PS/2 Mouse irq 12 on atkbdc0 psm0:
Re: Panic @r207844; current process: flowcleaner Fatal trap 12: page fault while in kernel mode
On Tue, May 11, 2010 at 9:24 PM, David Wolfskill da...@catwhisker.org wrote: On Tue, May 11, 2010 at 08:30:09PM -0700, K. Macy wrote: Please try 207949 ... The panic (this time) didn't show up until about 10 seconds after the login: prompt showed up on the serial console. Here's what it looks like: ... 3 Select option, [Enter] for default 3 3 or [Space] to pause timer 9 3 �...@dy GDB: no debug ports present KDB: debugger backends: ddb KDB: current backend: ddb Copyright (c) 1992-2010 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 9.0-CURRENT #157 r207911M: Tue May 11 20:54:25 PDT 2010 r...@freebeast.catwhisker.org:/usr/obj/usr/src/sys/GENERIC i386 WARNING: WITNESS option enabled, expect reduced performance. Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(TM) CPU 3.60GHz (3614.55-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf41 Family = f Model = 4 Stepping = 1 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0x659dSSE3,DTES64,MON,DS_CPL,EST,TM2,CNXT-ID,CX16,xTPR AMD Features=0x2010NX,LM TSC: P-state invariant real memory = 2147483648 (2048 MB) avail memory = 2086129664 (1989 MB) ACPI APIC Table: PTLTD APIC FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs FreeBSD/SMP: 2 package(s) x 1 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 6 ioapic0 Version 2.0 irqs 0-23 on motherboard ioapic1 Version 2.0 irqs 24-47 on motherboard ioapic2 Version 2.0 irqs 48-71 on motherboard kbd1 at kbdmux0 acpi0: PTLTD RSDT on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x1008-0x100b on acpi0 cpu0: ACPI CPU on acpi0 cpu1: ACPI CPU on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 pci0: unknown at device 0.1 (no driver attached) pci0: base peripheral at device 1.0 (no driver attached) pcib1: ACPI PCI-PCI bridge irq 16 at device 2.0 on pci0 pci1: ACPI PCI bus on pcib1 pcib2: ACPI PCI-PCI bridge at device 0.0 on pci1 pci2: ACPI PCI bus on pcib2 aac0: Adaptec SCSI RAID 2200S mem 0xdc00-0xdfff irq 24 at device 1.0 on pci2 aac0: Enable Raw I/O aac0: New comm. interface enabled aac0: [ITHREAD] aac0: Adaptec 2200S, aac driver 2.1.9-1 aacp0: SCSI Passthrough Bus on aac0 aacp1: SCSI Passthrough Bus on aac0 pcib3: ACPI PCI-PCI bridge at device 0.2 on pci1 pci3: ACPI PCI bus on pcib3 em0: Intel(R) PRO/1000 Legacy Network Connection 1.0.1 port 0x2000-0x203f mem 0xd820-0xd821 irq 54 at device 2.0 on pci3 em0: [FILTER] em0: Ethernet address: 00:30:48:2d:32:6a em1: Intel(R) PRO/1000 Legacy Network Connection 1.0.1 port 0x2040-0x207f mem 0xd822-0xd823 irq 55 at device 2.1 on pci3 em1: [FILTER] em1: Ethernet address: 00:30:48:2d:32:6b pcib4: ACPI PCI-PCI bridge irq 16 at device 4.0 on pci0 pci4: ACPI PCI bus on pcib4 pcib5: ACPI PCI-PCI bridge irq 16 at device 6.0 on pci0 pci5: ACPI PCI bus on pcib5 uhci0: Intel 82801EB (ICH5) USB controller USB-A port 0x1400-0x141f irq 16 at device 29.0 on pci0 uhci0: [ITHREAD] usbus0: Intel 82801EB (ICH5) USB controller USB-A on uhci0 uhci1: Intel 82801EB (ICH5) USB controller USB-B port 0x1420-0x143f irq 19 at device 29.1 on pci0 uhci1: [ITHREAD] usbus1: Intel 82801EB (ICH5) USB controller USB-B on uhci1 uhci2: Intel 82801EB (ICH5) USB controller USB-C port 0x1440-0x145f irq 18 at device 29.2 on pci0 uhci2: [ITHREAD] usbus2: Intel 82801EB (ICH5) USB controller USB-C on uhci2 uhci3: Intel 82801EB (ICH5) USB controller USB-D port 0x1460-0x147f irq 16 at device 29.3 on pci0 uhci3: [ITHREAD] usbus3: Intel 82801EB (ICH5) USB controller USB-D on uhci3 ehci0: Intel 82801EB/R (ICH5) USB 2.0 controller mem 0xd8001000-0xd80013ff irq 23 at device 29.7 on pci0 ehci0: [ITHREAD] usbus4: EHCI version 1.0 usbus4: Intel 82801EB/R (ICH5) USB 2.0 controller on ehci0 pcib6: ACPI PCI-PCI bridge at device 30.0 on pci0 pci6: ACPI PCI bus on pcib6 vgapci0: VGA-compatible display port 0x3000-0x30ff mem 0xd900-0xd9ff,0xd830-0xd8300fff irq 17 at device 1.0 on pci6 isab0: PCI-ISA bridge at device 31.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel ICH5 UDMA100 controller port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x14a0-0x14af at device 31.1 on pci0 ata0: ATA channel 0 on atapci0 ata0: [ITHREAD] ata1: ATA channel 1 on atapci0 ata1: [ITHREAD] pci0: serial bus, SMBus at device 31.3 (no driver attached) acpi_button0: Power Button on acpi0 atrtc0: AT realtime clock port 0x70-0x77 irq 8 on acpi0 atkbdc0: Keyboard controller
