Date: Fri, 19 Nov 2010 18:23:50 -0200 From: "Nenhum_de_Nos" <matheus@eternamente.info> To: pyunyh@gmail.com Cc: freebsd-usb@freebsd.org Subject: Re: usb/140883: [axe] [usb8] USB gigabit ethernet hangs after short period of traffic Message-ID: <9ecdf40489022c754096ac1f388a605f.squirrel@eternamente.info> In-Reply-To: <20101119192731.GB13317@michelle.cdnetworks.com> References: <201011181510.oAIFA7SZ034209@freefall.freebsd.org> <833a33ce5369c53c6db220b79e379092.squirrel@eternamente.info> <20101118202426.GB8512@michelle.cdnetworks.com> <bab43754fb4c3361ef0d990af3c3bd07.squirrel@eternamente.info> <20101119000618.GC8512@michelle.cdnetworks.com> <32aed4c0a483f26c662dd513ea718a78.squirrel@eternamente.info> <20101119013857.GE8512@michelle.cdnetworks.com> <8ca59ffdfef13423f8a34d81cfdefc49.squirrel@eternamente.info> <20101119171324.GA13317@michelle.cdnetworks.com> <603efbe44ab6deefcd86905280566f32.squirrel@eternamente.info> <20101119192731.GB13317@michelle.cdnetworks.com>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] On Fri, November 19, 2010 17:27, Pyun YongHyeon wrote: > On Fri, Nov 19, 2010 at 04:23:20PM -0200, Nenhum_de_Nos wrote: >> >> On Fri, November 19, 2010 15:13, Pyun YongHyeon wrote: >> > On Fri, Nov 19, 2010 at 03:19:26AM -0200, Nenhum_de_Nos wrote: >> >> >> >> On Thu, November 18, 2010 23:38, Pyun YongHyeon wrote: >> >> > On Thu, Nov 18, 2010 at 10:40:10PM -0200, Nenhum_de_Nos wrote: >> >> >> >> >> >> On Thu, November 18, 2010 22:06, Pyun YongHyeon wrote: >> >> >> > On Thu, Nov 18, 2010 at 09:12:13PM -0200, Nenhum_de_Nos wrote: >> >> >> >> >> >> >> >> On Thu, November 18, 2010 18:24, Pyun YongHyeon wrote: >> >> >> >> > On Thu, Nov 18, 2010 at 04:20:51PM -0200, Nenhum_de_Nos >> wrote: >> >> >> >> >> >> >> >> >> >> On Thu, November 18, 2010 13:10, Derrick Brashear wrote: >> >> >> >> >> > The following reply was made to PR usb/140883; it has been >> >> noted >> >> >> by >> >> >> >> >> GNATS. >> >> >> >> >> > >> >> >> >> >> > From: Derrick Brashear <shadow@gmail.com> >> >> >> >> >> > To: bug-followup@FreeBSD.org, sub.mesa@gmail.com >> >> >> >> >> > Cc: >> >> >> >> >> > Subject: Re: usb/140883: [axe] [usb8] USB gigabit ethernet >> >> hangs >> >> >> >> after >> >> >> >> >> > short >> >> >> >> >> > period of traffic >> >> >> >> >> > Date: Thu, 18 Nov 2010 09:36:50 -0500 >> >> >> >> >> > >> >> >> >> >> > Pyun has provided an updated driver which avoids several >> >> issues >> >> >> >> >> > including using a too-large transmit buffer (the chipset >> >> claims >> >> >> >> only >> >> >> >> >> > 8k) but none of the fixes worked until he disabled frame >> >> >> combining >> >> >> >> >> for >> >> >> >> >> > transmit. With only a single packet being sent per frame >> (as >> >> >> was >> >> >> >> the >> >> >> >> >> > case in FreeBSD 7, apparently) seems to make the issue go >> >> away. >> >> >> >> None >> >> >> >> >> > of the cases I could use to reproduce the issue now >> happen. >> >> >> >> >> > >> >> >> >> >> > -- >> >> >> >> >> > Derrick >> >> >> >> >> >> >> >> >> >> is this already in 8-stable ? I have a couple of axe(4) >> based >> >> >> nic's >> >> >> >> >> they're not ok on 8-stable. I've talked to Pyun before, and >> >> that >> >> >> time >> >> >> >> >> seemed do solve the issue (with gigabit belkin axe based) >> but >> >> now >> >> >> I >> >> >> >> >> can't >> >> >> >> >> get them to work anymore. even fast ethernet linksys axe are >> >> just >> >> >> >> dying >> >> >> >> >> when in a bridge (switched to OpenBSD to have it working). >> >> >> >> >> >> >> >> >> >> how ca I try this to help ? >> >> >> >> >> >> >> >> >> > >> >> >> >> > I uploaded updated if_axe.c/if_axereg.h to the following URL. >> >> >> >> > http://people.freebsd.org/~yongari/axe/if_axe.c >> >> >> >> > http://people.freebsd.org/~yongari/axe/if_axereg.h >> >> >> >> > >> >> >> >> > That files seem to fix axe(4) hang which were seen on >> AX88772A >> >> >> >> > controller. One of most notable changes are removing >> combining >> >> >> >> > multiple TX frames in TX path such that this change may >> result >> >> in >> >> >> >> > sub-optimal performance for most axe(4) controllers. However >> it >> >> >> >> > seems that change makes Derrick's controller work without >> >> problems. >> >> >> >> > Generally I prefer driver stability over performance so if >> this >> >> >> >> > change also fixes other axe(4) stability issues reported so >> far, >> >> I >> >> >> >> > want to check in the change. >> >> >> >> > >> >> >> >> > Thanks. >> >> >> >> >> >> >> >> well, >> >> >> >> >> >> >> >> things did got better here. but the link state UP and DOWN are >> >> still >> >> >> >> there :( >> >> >> >> >> >> >> >> ugen2.3: <vendor 0x050d> at usbus2 >> >> >> >> axe1: <vendor 0x050d product 0x5055, rev 2.00/0.01, addr 3> on >> >> usbus2 >> >> >> >> axe1: PHYADDR 0xe0:0x01 >> >> >> >> miibus2: <MII bus> on axe1 >> >> >> >> ukphy2: <Generic IEEE 802.3u media interface> PHY 1 on miibus2 >> >> >> >> ukphy2: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, >> >> 1000baseT, >> >> >> > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ >> >> >> >> 1000baseT-FD >> >> >> >> X, auto >> >> >> > >> >> >> > It seems you have PHY driver issue. Normally all gigabit PHYs >> >> >> > should have their own PHY driver since most PHYs hardwares tend >> to >> >> >> > have a special register that reports link state changes. >> >> >> > Show me the output of "devinfo -rv | grep phy". >> >> >> >> >> >> there you are: >> >> >> >> >> >> devinfo -rv|grep phy >> >> >> ukphy1 pnpinfo oui=0xec6 model=0x1 rev=0x1 at >> >> phyno=16 >> >> >> ukphy2 pnpinfo oui=0xa080 model=0x28 rev=0x2 at >> >> >> phyno=1 >> >> >> ukphy0 pnpinfo oui=0x4063 model=0x32 rev=0xa at >> phyno=1 >> >> >> >> >> > >> >> > Hmm.... You have many ukphys there. :-) I think the PHY attached to >> >> > the USB controller is ukphy2. The OUI indicates its maker is ASIX. >> >> > Unfortunately there is no dedicated PHY driver for this PHY. I >> >> > guess it may use a modified CICADA PHY though. Updated driver to >> >> > force GPIO configuration for this PHY. Would you try again after >> >> > downloading if_axe.c/if_axereg.h? It may show >> >> > "unknown PHY mode : 0xXX" if my guess is wrong. >> >> back to this, no problem of unknown PHY: >> >> ugen2.2: <vendor 0x13b1> at usbus2 >> axe0: <vendor 0x13b1 product 0x0018, rev 2.00/0.01, addr 2> on usbus2 >> axe0: PHYADDR 0xe0:0x10 >> Root mount waiting for: usbus2 >> miibus1: <MII bus> on axe0 >> ukphy1: <Generic IEEE 802.3u media interface> PHY 16 on miibus1 >> ukphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto >> ue0: <USB Ethernet> on axe0 >> ue0: Ethernet address: my mac here >> ugen2.3: <vendor 0x050d> at usbus2 >> axe1: <vendor 0x050d product 0x5055, rev 2.00/0.01, addr 3> on usbus2 >> axe1: PHYADDR 0xe0:0x01 >> Trying to mount root from ufs:/dev/ad0s3a >> miibus2: <MII bus> on axe1 >> ukphy2: <Generic IEEE 802.3u media interface> PHY 1 on miibus2 >> ukphy2: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, >> 1000baseT-FDX, auto >> ue1: <USB Ethernet> on axe1 >> ue1: Ethernet address: my other mac here >> >> the ping still shows problems (on gbit controller at 100BaseTX): >> >> 62 packets transmitted, 55 packets received, 11.3% packet loss >> round-trip min/avg/max/stddev = 0.873/1.957/51.408/6.730 ms >> >> when in gigabit, no good: >> > > Ok, try again after downloading new if_axe.c and let me know > the output "EEPROM data : 0xXX, phymode : 0xXX" shown on your > console. never got to see that message. I saw the diff to previous version, and did boot into verbose mode (dmesg attached). there were just the belkin gigabit nic on boot. after, the linksys USB200M: axe1: <vendor 0x13b1 product 0x0018, rev 2.00/0.01, addr 3> on usbus2 axe1: PHYADDR 0xe0:0x10 miibus2: <MII bus> on axe1 ukphy1: <Generic IEEE 802.3u media interface> PHY 16 on miibus2 ukphy1: OUI 0x000ec6, model 0x0001, rev. 1 ukphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto ue1: <USB Ethernet> on axe1 ue1: bpf attached invalid media SR 0x700 invalid media SR 0x700 and the other gigabit: ugen2.4: <vendor 0x050d> at usbus2 axe2: <vendor 0x050d product 0x5055, rev 2.00/0.01, addr 4> on usbus2 axe2: PHYADDR 0xe0:0x01 miibus3: <MII bus> on axe2 truephy1: <ET1011 10/100/1000baseT PHY> PHY 1 on miibus3 truephy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT-FDX, auto ue2: <USB Ethernet> on axe2 ue2: bpf attached ue2: Ethernet address: my mac here ue2: link state changed to DOWN and never got to see the EEPROM message. >> ping 192.168.1.3 >> PING 192.168.1.3 (192.168.1.3): 56 data bytes >> 64 bytes from 192.168.1.3: icmp_seq=2 ttl=128 time=1.533 ms >> 64 bytes from 192.168.1.3: icmp_seq=3 ttl=128 time=1001.806 ms >> 64 bytes from 192.168.1.3: icmp_seq=4 ttl=128 time=1.151 ms >> 64 bytes from 192.168.1.3: icmp_seq=5 ttl=128 time=1001.860 ms >> 64 bytes from 192.168.1.3: icmp_seq=6 ttl=128 time=1.317 ms >> 64 bytes from 192.168.1.3: icmp_seq=7 ttl=128 time=1.036 ms >> 64 bytes from 192.168.1.3: icmp_seq=8 ttl=128 time=1001.899 ms >> 64 bytes from 192.168.1.3: icmp_seq=9 ttl=128 time=1.273 ms >> ping: sendto: No route to host >> ping: sendto: No route to host >> ping: sendto: No route to host >> 64 bytes from 192.168.1.3: icmp_seq=16 ttl=128 time=0.992 ms >> 64 bytes from 192.168.1.3: icmp_seq=18 ttl=128 time=0.860 ms >> ping: sendto: No route to host >> 64 bytes from 192.168.1.3: icmp_seq=25 ttl=128 time=1.132 ms >> ping: sendto: No route to host >> 64 bytes from 192.168.1.3: icmp_seq=34 ttl=128 time=3003.569 ms >> 64 bytes from 192.168.1.3: icmp_seq=35 ttl=128 time=2002.963 ms >> 64 bytes from 192.168.1.3: icmp_seq=36 ttl=128 time=1002.208 ms >> 64 bytes from 192.168.1.3: icmp_seq=37 ttl=128 time=1.454 ms >> ^C >> --- 192.168.1.3 ping statistics --- >> 38 packets transmitted, 15 packets received, 60.5% packet loss >> round-trip min/avg/max/stddev = 0.860/601.670/3003.569/880.104 ms >> >> and: >> >> ue1: link state changed to DOWN >> ue1: link state changed to UP >> ue1: link state changed to DOWN >> ue1: link state changed to UP >> ue1: link state changed to DOWN >> ue1: link state changed to UP >> ue1: link state changed to DOWN >> ue1: link state changed to UP >> ue1: link state changed to DOWN >> ue1: link state changed to UP >> ue1: link state changed to DOWN >> ue1: link state changed to UP >> ue1: link state changed to DOWN >> ue1: link state changed to UP >> ue1: link state changed to DOWN >> ue1: link state changed to UP >> >> >> I downloaded again from above links and are the same as the last: >> >> >> >> valfenda# md5 if_axe* >> >> MD5 (if_axe.c) = 388b7aa84f0d2471f8b144033103618b >> >> MD5 (if_axe.c.original) = c528c7cb5eb964a792d4c14dfaed47cf >> >> MD5 (if_axe.c.v1) = 388b7aa84f0d2471f8b144033103618b >> >> MD5 (if_axereg.h) = 10f85490cab59b8e40de261fd7ad81a5 >> >> MD5 (if_axereg.h.original) = 46f37d0f02a3c09463ceec58b743c6ce >> >> MD5 (if_axereg.h.v1) = 10f85490cab59b8e40de261fd7ad81a5 >> >> >> >> .original are files from 8-stable (via csup) >> >> .v1 are the files from http://people.freebsd.org/~yongari/axe/ >> >> downloaded >> >> when the fist test using those files were made. >> >> regular .c files were downloaded now when I read this mail. >> >> >> >> did you uploaded some new version in >> >> http://people.freebsd.org/~yongari/axe/ ? or I didn't got it ? :) >> >> >> > >> > Oops, it seems I forgot to upload it after modifying it. >> > Please download again. MD5 should be >> > 507a672946e7c0394e83c79d1a12c9b5 (if_axe.c) and >> > 10f85490cab59b8e40de261fd7ad81a5 (if_axereg.h) >> > >> >> should this modified version be a good test to fast ethernet axe nics >> ? >> >> my >> >> linksys USB200M failed when in bridge after some time of use :( same >> > >> > Yes, the change made in if_axe.c is for AX88178, AX88772 and >> > AX8872A. The change has no effect for AX88172. Your controller would >> > be either AX88772 or AX88772A so chances are good to see different >> > behavior than ever before. >> >> I have no idea on how to see this ... is there anyway ? >> > > From the output you posted: > axe0: <vendor 0x13b1 product 0x0018, rev 2.00/0.01, addr 2> on usbus2 > axe0: PHYADDR 0xe0:0x10 > product is 0x0018 which means Cisco USB200M V2 and its controller > is AX88772A. great :) >> >> hardware I'm testing now. and the nics are ok, tested in OpenBSD with >> >> same >> >> hardware and same bridge and same pf conf file. >> >> >> >> thanks, >> >> >> >> matheus >> >> by the way, you would not know if an interrupt storm on the irq of the >> fast ethernet axe would have anything to do with its driver, right ? it >> just happens when in bridge mode (I figured out why the bridge was >> stopping working - the other nic keeps working fine). >> > > Normally bridge mode will put the controller into promiscuous mode. > If there is a bug in setting promiscuous mode, you should have seen > it whenever you use tcpdump on that interface. So if you run > tcpdump on that interface, do you see interrupt storm? > If you don't, it would be different issue, I guess. I'm trying this, usb nic out of bridge, its own IP, tcpdump and iperf. few minutes and no problem so far. let's see in some time. when bridging for my DSL, it got something around 1~3Mbps of traffic. and in less then a night (8 hours) the usb nic would say goodbye ... thanks again, matheus -- We will call you cygnus, The God of balance you shall be A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? http://en.wikipedia.org/wiki/Posting_style [-- Attachment #2 --] 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 8.1-STABLE #2: Fri Nov 5 01:52:06 BRT 2010 root@valfenda.apartnet:/usr/obj/usr/src/sys/valfenda i386 Preloaded elf kernel "/boot/kernel/kernel" at 0xc1017000. Timecounter "i8254" frequency 1193182 Hz quality 0 Calibrating TSC clock ... TSC clock: 798130096 Hz CPU: Transmeta(tm) Crusoe(tm) Processor TM5700 (798.13-MHz 586-class CPU) Origin = "GenuineTMx86" Id = 0x543 Family = 5 Model = 4 Stepping = 3 Features=0x84893f<FPU,VME,DE,PSE,TSC,MSR,CX8,SEP,CMOV,PN,MMX> Processor revision 1.5.0.2 Code Morphing Software revision 4.5.2-12-11 20040614 15:00 official release 4.5.2#1 real memory = 538968064 (514 MB) Physical memory chunk(s): 0x0000000000001000 - 0x0000000000099fff, 626688 bytes (153 pages) 0x0000000000100000 - 0x00000000003fffff, 3145728 bytes (768 pages) 0x0000000001426000 - 0x000000001e6f1fff, 489472000 bytes (119500 pages) avail memory = 489926656 (467 MB) x86bios: IVT 0x000000-0x0004ff at 0xc0000000 x86bios: SSEG 0x010000-0x01ffff at 0xc331c000 x86bios: EBDA 0x09f000-0x09ffff at 0xc009f000 x86bios: ROM 0x0a0000-0x0effff at 0xc00a0000 bios32: Found BIOS32 Service Directory header at 0xc00f9de0 bios32: Entry = 0xfa260 (c00fa260) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xf0000+0xa290 pnpbios: Found PnP BIOS data at 0xc00facf0 pnpbios: Entry = f0000:ad20 Rev = 1.0 Other BIOS signatures found: ULE: setup cpu 0 wlan: <802.11 Link Layer> null: <null device, zero device> random: <entropy source, Software, Yarrow> nfslock: pseudo-device io: <I/O> kbd: new array size 4 kbd1 at kbdmux0 mem: <memory> hptrr: RocketRAID 17xx/2xxx SATA controller driver v1.2 ACPI: RSDP 0xf6620 00014 (v00 I-BASE) ACPI: RSDT 0x1eff3000 00028 (v01 I-BASE AWRDACPI 42302E31 AWRD 00000000) ACPI: FACP 0x1eff3040 00074 (v01 I-BASE AWRDACPI 42302E31 AWRD 00000000) ACPI: DSDT 0x1eff30c0 01C16 (v01 I-BASE AWRDACPI 00001000 MSFT 0100000C) ACPI: FACS 0x1eff0000 00040 npx0: INT 16 interface acpi0: <I-BASE AWRDACPI> on motherboard acpi0: [MPSAFE] acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: Sleep Button (fixed) acpi0: wakeup code va 0xc3159000 pa 0x1000 pci_open(1): mode 1 addr port (0x0cf8) is 0x80000058 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=80] is there (id=03951279) pcibios: BIOS version 2.10 acpi_bus_number: root bus has no _BBN, assuming 0 AcpiOsDerivePciId: \\_SB_.PCI0.VT86.SB70 -> bus 0 dev 17 func 0 acpi_bus_number: root bus has no _BBN, assuming 0 AcpiOsDerivePciId: \\_SB_.PCI0.VT86.PIRQ -> bus 0 dev 17 func 0 acpi0: reservation of 0, a0000 (3) failed acpi0: reservation of 100000, 1eef0000 (3) failed ACPI timer: 0/1054 0/6 0/6 0/6 0/7 0/8 0/6 0/8 0/6 0/5 -> 0 Timecounter "ACPI-safe" frequency 3579545 Hz quality 850 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0 cpu0: <ACPI CPU> on acpi0 cpu0: switching to generic Cx mode pci_link0: Index IRQ Rtd Ref IRQs Initial Probe 0 15 N 0 1 3 4 5 6 7 10 11 12 14 15 Validation 0 15 N 0 1 3 4 5 6 7 10 11 12 14 15 After Disable 0 255 N 0 1 3 4 5 6 7 10 11 12 14 15 pci_link1: Index IRQ Rtd Ref IRQs Initial Probe 0 5 N 0 1 3 4 5 6 7 10 11 12 14 15 Validation 0 5 N 0 1 3 4 5 6 7 10 11 12 14 15 After Disable 0 255 N 0 1 3 4 5 6 7 10 11 12 14 15 pci_link2: Index IRQ Rtd Ref IRQs Initial Probe 0 10 N 0 1 3 4 5 6 7 10 11 12 14 15 Validation 0 10 N 0 1 3 4 5 6 7 10 11 12 14 15 After Disable 0 255 N 0 1 3 4 5 6 7 10 11 12 14 15 pci_link3: Index IRQ Rtd Ref IRQs Initial Probe 0 11 N 0 1 3 4 5 6 7 10 11 12 14 15 Validation 0 11 N 0 1 3 4 5 6 7 10 11 12 14 15 After Disable 0 255 N 0 1 3 4 5 6 7 10 11 12 14 15 acpi_button0: <Power Button> on acpi0 pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff,0x4000-0x407f,0x4080-0x40ff,0x5000-0x500f on acpi0 ACPI: Found matching pin for 0.13.INTA at func 0: 11 ACPI: Found matching pin for 0.9.INTA at func 0: 15 ACPI: Found matching pin for 0.9.INTB at func 1: 5 ACPI: Found matching pin for 0.9.INTC at func 2: 10 ACPI: Found matching pin for 0.18.INTA at func 0: 15 pci0: <ACPI PCI bus> on pcib0 pci0: domain=0, physical bus=0 found-> vendor=0x1279, dev=0x0395, revid=0x04 domain=0, bus=0, slot=0, func=0 class=06-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0006, statreg=0x2200, cachelnsz=0 (dwords) lattimer=0x20 (960 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) map[10]: type Memory, range 32, base 0xe8000000, size 20, enabled found-> vendor=0x1279, dev=0x0396, revid=0x00 domain=0, bus=0, slot=0, func=1 class=05-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0000, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x1279, dev=0x0397, revid=0x00 domain=0, bus=0, slot=0, func=2 class=05-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0000, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x1279, dev=0x0399, revid=0x00 domain=0, bus=0, slot=0, func=3 class=05-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0000, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x1106, dev=0x3038, revid=0x61 domain=0, bus=0, slot=9, func=0 class=0c-03-00, hdrtype=0x00, mfdev=1 cmdreg=0x0147, statreg=0x0210, cachelnsz=8 (dwords) lattimer=0x20 (960 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=15 powerspec 2 supports D0 D1 D2 D3 current D0 map[20]: type I/O Port, range 32, base 0xe000, size 5, enabled pcib0: matched entry for 0.9.INTA (src \\_SB_.PCI0.LNKA:0) pcib0: slot 9 INTA routed to irq 15 via \\_SB_.PCI0.LNKA unknown: Reserved 0x20 bytes for rid 0x20 type 4 at 0xe000 found-> vendor=0x1106, dev=0x3038, revid=0x61 domain=0, bus=0, slot=9, func=1 class=0c-03-00, hdrtype=0x00, mfdev=1 cmdreg=0x0147, statreg=0x0210, cachelnsz=8 (dwords) lattimer=0x20 (960 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=b, irq=5 powerspec 2 supports D0 D1 D2 D3 current D0 map[20]: type I/O Port, range 32, base 0xe100, size 5, enabled pcib0: matched entry for 0.9.INTB (src \\_SB_.PCI0.LNKB:0) pcib0: slot 9 INTB routed to irq 5 via \\_SB_.PCI0.LNKB unknown: Reserved 0x20 bytes for rid 0x20 type 4 at 0xe100 found-> vendor=0x1106, dev=0x3104, revid=0x63 domain=0, bus=0, slot=9, func=2 class=0c-03-20, hdrtype=0x00, mfdev=1 cmdreg=0x0147, statreg=0x0210, cachelnsz=8 (dwords) lattimer=0x20 (960 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=c, irq=10 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type Memory, range 32, base 0xe8131000, size 8, enabled pcib0: matched entry for 0.9.INTC (src \\_SB_.PCI0.LNKC:0) pcib0: slot 9 INTC routed to irq 10 via \\_SB_.PCI0.LNKC unknown: Reserved 0x100 bytes for rid 0x10 type 3 at 0xe8131000 found-> vendor=0x1002, dev=0x5159, revid=0x00 domain=0, bus=0, slot=13, func=0 class=03-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0187, statreg=0x0290, cachelnsz=8 (dwords) lattimer=0x20 (960 ns), mingnt=0x08 (2000 ns), maxlat=0x00 (0 ns) intpin=a, irq=11 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type Prefetchable Memory, range 32, base 0xe0000000, size 27, enabled map[14]: type I/O Port, range 32, base 0xe200, size 8, enabled map[18]: type Memory, range 32, base 0xe8120000, size 16, enabled pcib0: matched entry for 0.13.INTA (src \\_SB_.PCI0.LNKD:0) pcib0: slot 13 INTA routed to irq 11 via \\_SB_.PCI0.LNKD found-> vendor=0x1106, dev=0x8231, revid=0x10 domain=0, bus=0, slot=17, func=0 class=06-01-00, hdrtype=0x00, mfdev=1 cmdreg=0x0087, statreg=0x0210, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) powerspec 2 supports D0 D3 current D0 found-> vendor=0x1106, dev=0x0571, revid=0x06 domain=0, bus=0, slot=17, func=1 class=01-01-8a, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x0290, cachelnsz=0 (dwords) lattimer=0x20 (960 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) powerspec 2 supports D0 D3 current D0 map[20]: type I/O Port, range 32, base 0xe300, size 4, enabled found-> vendor=0x1106, dev=0x8235, revid=0x10 domain=0, bus=0, slot=17, func=4 class=06-80-00, hdrtype=0x00, mfdev=0 cmdreg=0x0000, statreg=0x0290, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) powerspec 2 supports D0 D3 current D0 found-> vendor=0x1106, dev=0x3065, revid=0x51 domain=0, bus=0, slot=18, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0147, statreg=0x0210, cachelnsz=8 (dwords) lattimer=0x20 (960 ns), mingnt=0x03 (750 ns), maxlat=0x08 (2000 ns) intpin=a, irq=15 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type I/O Port, range 32, base 0xe600, size 8, enabled map[14]: type Memory, range 32, base 0xe8130000, size 8, enabled pcib0: matched entry for 0.18.INTA (src \\_SB_.PCI0.LNKA:0) pcib0: slot 18 INTA routed to irq 15 via \\_SB_.PCI0.LNKA 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) uhci0: <VIA 83C572 USB controller> port 0xe000-0xe01f irq 15 at device 9.0 on pci0 uhci0: [MPSAFE] uhci0: [ITHREAD] usbus0: <VIA 83C572 USB controller> on uhci0 uhci1: <VIA 83C572 USB controller> port 0xe100-0xe11f irq 5 at device 9.1 on pci0 uhci1: [MPSAFE] uhci1: [ITHREAD] usbus1: <VIA 83C572 USB controller> on uhci1 ehci0: <VIA VT6202 USB 2.0 controller> mem 0xe8131000-0xe81310ff irq 10 at device 9.2 on pci0 ehci0: [MPSAFE] ehci0: [ITHREAD] ehci0: Dropped interrupts workaround enabled usbus2: EHCI version 1.0 usbus2: <VIA VT6202 USB 2.0 controller> on ehci0 vgapci0: <VGA-compatible display> port 0xe200-0xe2ff mem 0xe0000000-0xe7ffffff,0xe8120000-0xe812ffff irq 11 at device 13.0 on pci0 isab0: <PCI-ISA bridge> at device 17.0 on pci0 isa0: <ISA bus> on isab0 atapci0: <VIA 8231 UDMA100 controller> port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xe300-0xe30f at device 17.1 on pci0 atapci0: Reserved 0x10 bytes for rid 0x20 type 4 at 0xe300 ata0: <ATA channel 0> on atapci0 atapci0: Reserved 0x8 bytes for rid 0x10 type 4 at 0x1f0 atapci0: Reserved 0x1 bytes for rid 0x14 type 4 at 0x3f6 ata0: reset tp1 mask=03 ostat0=50 ostat1=00 ata0: stat0=0x50 err=0x01 lsb=0x00 msb=0x00 ata0: stat1=0x00 err=0x01 lsb=0x00 msb=0x00 ata0: reset tp2 stat0=50 stat1=00 devices=0x1 ata0: [MPSAFE] ata0: [ITHREAD] ata1: <ATA channel 1> on atapci0 atapci0: Reserved 0x8 bytes for rid 0x18 type 4 at 0x170 atapci0: Reserved 0x1 bytes for rid 0x1c type 4 at 0x376 ata1: reset tp1 mask=00 ostat0=ff ostat1=ff ata1: [MPSAFE] ata1: [ITHREAD] pci0: <bridge> at device 17.4 (no driver attached) vr0: <VIA VT6102 Rhine II 10/100BaseTX> port 0xe600-0xe6ff mem 0xe8130000-0xe81300ff irq 15 at device 18.0 on pci0 vr0: Quirks: 0x0 vr0: Revision: 0x51 vr0: Reserved 0x100 bytes for rid 0x10 type 4 at 0xe600 miibus0: <MII bus> on vr0 ukphy0: <Generic IEEE 802.3u media interface> PHY 1 on miibus0 ukphy0: OUI 0x004063, model 0x0032, rev. 10 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto vr0: bpf attached vr0: Ethernet address: 00:13:21:ee:8d:d4 vr0: [MPSAFE] vr0: [ITHREAD] atrtc0: <AT realtime clock> port 0x70-0x73 irq 8 on acpi0 atrtc0: registered as a time-of-day clock (resolution 1000000us) ppc0: using extended I/O port range ppc0: SPP EPP ppc0: <Parallel port> port 0x378-0x37f irq 7 on acpi0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode ppc0: [MPSAFE] ppc0: [ITHREAD] ppbus0: <Parallel port bus> on ppc0 plip0: <PLIP network interface> on ppbus0 plip0: bpf attached plip0: [MPSAFE] plip0: [ITHREAD] lpt0: <Printer> on ppbus0 lpt0: [MPSAFE] lpt0: [ITHREAD] lpt0: Interrupt-driven port ppi0: <Parallel I/O> on ppbus0 atkbdc0: <Keyboard controller (i8042)> port 0x60,0x64 irq 1 on acpi0 atkbd0: <AT Keyboard> irq 1 on atkbdc0 atkbd: the current kbd controller command byte 0047 atkbd: keyboard ID 0x41ab (2) kbd0 at atkbd0 kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x3d0000 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] psm0: unable to allocate IRQ unknown: status reg test failed ff unknown: status reg test failed ff unknown: status reg test failed ff unknown: status reg test failed ff unknown: status reg test failed ff unknown: status reg test failed ff ex_isa_identify() pnp_identify: Trying Read_Port at 203 pnp_identify: Trying Read_Port at 243 pnp_identify: Trying Read_Port at 283 pnp_identify: Trying Read_Port at 2c3 pnp_identify: Trying Read_Port at 303 pnp_identify: Trying Read_Port at 343 pnp_identify: Trying Read_Port at 383 pnp_identify: Trying Read_Port at 3c3 PNP Identify complete isa_probe_children: disabling PnP devices pmtimer0 on isa0 isa_probe_children: probing non-PnP devices orm0: <ISA Option ROMs> at iomem 0xc0000-0xc8fff,0xcc000-0xd5fff pnpid ORM0000 on isa0 sc0: <System console> on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sc0: fb0, kbd1, terminal emulator: scteken (teken terminal) vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 isa_probe_children: probing PnP devices acpi_throttle0: <ACPI CPU Throttling> on cpu0 acpi_throttle0: P_CNT from P_BLK 0x4010 Device configuration finished. procfs registered Timecounter "TSC" frequency 798130096 Hz quality 800 Timecounters tick every 1.000 msec vlan: initialized, using hash tables with chaining lo0: bpf attached pfsync0: bpf attached pflog0: bpf attached hptrr: no controller detected. ata0: Identifying devices: 00000001 ata0: New devices: 00000001 usbus0: 12Mbps Full Speed USB v1.0 usbus1: 12Mbps Full Speed USB v1.0 usbus2: 480Mbps High Speed USB v2.0 ata0-master: pio=PIO4 wdma=WDMA2 udma=UDMA33 cable=40 wire ugen0.1: <VIA> at usbus0 uhub0: <VIA UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus0 ugen1.1: <VIA> at usbus1 uhub1: <VIA UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus1 ugen2.1: <VIA> at usbus2 uhub2: <VIA EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus2 ad0: setting UDMA33 ad0: 5859MB <HMS360606D5CF00 DP6AC30H> at ata0-master UDMA33 ad0: 12000556 sectors [11905C/16H/63S] 16 sectors/interrupt 1 depth queue GEOM: new disk ad0 ad0: VIA check1 failed ad0: Adaptec check1 failed ad0: LSI (v3) check1 failed ad0: LSI (v2) check1 failed uhub0: 2 ports with 2 removable, self powered uhub1: 2 ports with 2 removable, self powered ad0: FreeBSD check1 failed ata1: Identifying devices: 00000000 ata1: New devices: 00000000 ATA PseudoRAID loaded uhub2: 4 ports with 4 removable, self powered Root mount waiting for: usbus2 ugen2.2: <vendor 0x050d> at usbus2 axe0: <vendor 0x050d product 0x5055, rev 2.00/0.01, addr 2> on usbus2 axe0: PHYADDR 0xe0:0x01 Trying to mount root from ufs:/dev/ad0s3a ct_to_ts([2010-11-19 19:58:06]) = 1290196686.000000000 start_init: trying /sbin/init miibus1: <MII bus> on axe0 truephy0: <ET1011 10/100/1000baseT PHY> PHY 1 on miibus1 truephy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT-FDX, auto ue0: <USB Ethernet> on axe0 ue0: bpf attached ue0: Ethernet address: 00:11:50:e7:39:e9 bridge0: bpf attached bridge0: Ethernet address: de:d5:37:8f:3f:c2 splash: image decoder found: green_saver ue0: link state changed to DOWN ue0: link state changed to UP ue0: link state changed to DOWN ue0: link state changed to UP ue0: link state changed to DOWN ue0: link state changed to UP ue0: link state changed to DOWN ue0: link state changed to UP ue0: link state changed to DOWN ue0: link state changed to UP ue0: link state changed to DOWN ue0: link state changed to UP ue0: link state changed to DOWN ue0: link state changed to UP ue0: link state changed to DOWN ue0: link state changed to UP ue0: link state changed to DOWN ue0: link state changed to UP
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9ecdf40489022c754096ac1f388a605f.squirrel>