Re: System hangs up every day
On Tue, Jan 22, 2008 at 04:01:56AM +0300, A. Rymkus wrote: > Tuesday, December 18, 2007, 11:42:19 AM, you wrote: > ??> Unfortunately my problem still doesn't have any solution. > ??> But I have an interesting observation. The gateway freezes very > ??> quickly, if torrent client programs are running on workstations. > ??> I assume the cause of the problem consists in many number of > ??> TCP/IP connections that torrent client establishes. > ??> Any ideas? > ??> Maybe I can tune somehow a TCP/IP via kernel, sysctl or pf settings? > > >> There is one FreeBSD server in our company. The server platform is: > >> Supermicro SuperServer 6014V-T2B (2x Intel > Xeon 2.8, 1Gb RAM, 3WARE > >> 3W-8006-2LP RAID-Controller). > >> The server works as: > >> - a gateway between LAN and Internet > >> - an Intranet web- and database server (Apache + MySQL + PHP) > >> - a firewall (OpenBSD pf) > >> - a transparent proxy server (Squid) > >> A mounthly traffic through this server is about 100Gb. There is about 200 > >> internet users in our conpany. > >> FreeBSD 6.2-RELEASE-p8 > > >> This server hangs up every day without any messages in the log files and > >> on the system console. A keyboard dosen't work too. I can make only hard > >> reset and after restart coredump files are not appearing. > > >> If I make and install a kernel with SMP options the system under working > >> load begins hang up every two hours. > > >> The two days "Memtest" gave no result. > >> I tried to install the newest Intel ethernet adapter driver, but without > >> any results. > >> As an experiment I tried also to plug a system HDD to another sever > >> platform (SuperServer 6015V-TB), but system hanging didn't stop. > >> I think that it is not only hardware problem. > >> Linux (Gentoo) and Windows server 2003 on this hardware were working fine. > > Got same problem in 6.2 based on VMWare ESX 3.0, with both type of > provided adapters type - lnc & em. System just hangs one adapter first, then > hangs completely. > Can this problem be solved by cvsup'g and rebuilding whole world, or > I have to wait for 7.0-RELEASE? ;) The interesting thing about these reported problems is that I cannot reproduce them on any of our boxes. Here's the hardware, and the network traffic that occurs on them over a month period of time: * Supermicro SuperServer 5015M-T - Single E6420 CPU (dual core), 2GB RAM (non-ECC) - RELENG_7, SMP enabled, using ULE scheduler - apache 2.2, mysql 5, PHP 5, postfix - load is usually 0.40 (mainly httpd and mysqld) - em0: 10gbit/month, em1: 8gbit/month * Supermicro SuperServer 5015M-T - Single E6420 CPU (dual core), 2GB RAM (non-ECC) - RELENG_6, SMP enabled, using 4BSD scheduler - mysql 5, ntpd, bind, postfix, and ircd-ratbox - load is usually 0.09 (mainly mysqld) - em0: 7gbit/month, em1: 42gbit/month * Supermicro SuperServer 5014C-MR - Single Pentium 4 CPU, 3GB RAM (non-ECC) - RELENG_6, SMP disabled, using 4BSD scheduler - apache 2.2, PHP 5, bind, postfix, shell services - load is usually 0.08 - bge0: 30gbit/month, bge1: 32gbit/month * Supermicro SuperServer 5013C-T - Single Pentium 4 CPU, 1GB RAM (non-ECC) - RELENG_6, SMP disabled, using 4BSD scheduler - bind, postfix, miscellaneous minor stuff - load is usually 0.03 - em0: 5gbit/month, em1: 41gbit/month * Supermicro SuperServer 5010E - Single Pentium 3 CPU, 512MB RAM (non-ECC) - RELENG_6, SMP disabled, using 4BSD scheduler - apache 2.0, mysql 5, bind, sendmail - load is usually 0.05 - fxp0: 2gbit/month, fxp1: 5.1gbit/month All machines have pf(4) enabled and in use, but are not routing traffic as a gateway; they simply provide content and other services. Based on what you've described, I'm left thinking there could be some BIOS-related setting which is tickling a bug under FreeBSD, or something along those lines. By the way, hard-resetting the box will not cause a kernel panic, thus there will be no coredumps to examine. Additionally, there's a chicken-and-egg situation which is causing savecore(8) to not create any coredumps from panics anyways -- see PR 118255 for details of that. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: System hangs up every day
Hello everybody Unfortunately my problem still doesn't have any solution. But I have an interesting observation. The gateway freezes very quickly, if torrent client programs are running on workstations. I assume the cause of the problem consists in many number of TCP/IP connections that torrent client establishes. Any ideas? Maybe I can tune somehow a TCP/IP via kernel, sysctl or pf settings? > There is one FreeBSD server in our company. The server platform is: > Supermicro SuperServer 6014V-T2B (2x Intel > Xeon 2.8, 1Gb RAM, 3WARE > 3W-8006-2LP RAID-Controller). > The server works as: > - a gateway between LAN and Internet > - an Intranet web- and database server (Apache + MySQL + PHP) > - a firewall (OpenBSD pf) > - a transparent proxy server (Squid) > A mounthly traffic through this server is about 100Gb. There is about 200 > internet users in our conpany. > FreeBSD 6.2-RELEASE-p8 > This server hangs up every day without any messages in the log files and on > the system console. A keyboard dosen't work too. I can make only hard reset > and after restart coredump files are not appearing. > If I make and install a kernel with SMP options the system under working load > begins hang up every two hours. > The two days "Memtest" gave no result. > I tried to install the newest Intel ethernet adapter driver, but without any > results. > As an experiment I tried also to plug a system HDD to another sever platform > (SuperServer 6015V-TB), but system hanging didn't stop. > I think that it is not only hardware problem. > Linux (Gentoo) and Windows server 2003 on this hardware were working fine. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: System hangs up every day
> > > I have written already, that I tried to plug a system HDD > to another sever with the same configuration; on the new > platform the system hanging didn't stop. The RAID controller > remained the same, but it has the own error log and it is clear. > > > > em0: > > :)) > > >> > options MP_WATCHDOG > >> > options SW_WATCHDOG > > Try to compile the GENERIC SMP kernel with all ALTQ options > but without > watchdog options. Maybe this will work. The watchdog options whare turned off initially and the server froze often. I enabled watchdog in order not to reset my server manually. It works. :) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: System hangs up every day
Дмитрий Комалеев <[EMAIL PROTECTED]> writes: > I have written already, that I tried to plug a system HDD to another sever > with the same configuration; on the new platform the system hanging didn't > stop. The RAID controller remained the same, but it has the own error log > and it is clear. > em0: :)) >> > options MP_WATCHDOG >> > options SW_WATCHDOG Try to compile the GENERIC SMP kernel with all ALTQ options but without watchdog options. Maybe this will work. -- One cannot sell the earth upon which the people walk Tacunka Witco ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: System hangs up every day
> > A system failure of this sort (one which leaves no log entries of any > kind) is generally a hardware fault; memory stick failures tend to > cause kernel panics and easy repeatability. > > I would suggest examining the hardware components, the motherboard > could have some faulty capacitors (burst, leaking, or swollen); the > fans on the processors could be failing causing a lockup, the power > supply fans could be failing causing an undervolt and lockup, but this > usually makes the system reset. > > You get the idea, your symptoms are pointing to hardware > issues in my opinion. I have written already, that I tried to plug a system HDD to another sever with the same configuration; on the new platform the system hanging didn't stop. The RAID controller remained the same, but it has the own error log and it is clear. > > On 10/31/07, Дмитрий Комалеев <[EMAIL PROTECTED]> wrote: > > Hello everybody > > > > I have a big problem > > > > There is one FreeBSD server in our company. The server > platform is: Supermicro SuperServer 6014V-T2B (2x Intel Xeon > 2.8, 1Gb RAM, 3WARE 3W-8006-2LP RAID-Controller). > > The server works as: > > - a gateway between LAN and Internet > > - an Intranet web- and database server (Apache + MySQL + PHP) > > - a firewall (OpenBSD pf) > > - a transparent proxy server (Squid) > > A mounthly traffic through this server is about 100Gb. > There is about 200 internet users in our conpany. > > Here is a part of my dmesg-listing: > > > > 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 6.2-RELEASE-p8 #2: Thu Oct 11 19:51:25 MSD 2007 > > [EMAIL PROTECTED]:/usr/obj/usr/src/sys/KERNEL01_NOSMP > > module_register: module pci/em already exists! > > Module pci/em failed to register: 17 > > ACPI APIC Table: > > Timecounter "i8254" frequency 1193182 Hz quality 0 > > CPU: Intel(R) Xeon(TM) CPU 2.80GHz (2800.12-MHz 686-class CPU) > > Origin = "GenuineIntel" Id = 0xf43 Stepping = 3 > > > Features=0xbfebfbff SS,HTT,TM,PBE> > > Features2=0x641d> > > AMD Features=0x2000 > > Logical CPUs per core: 2 > > real memory = 1073479680 (1023 MB) > > avail memory = 1041465344 (993 MB) > > ioapic0 irqs 0-23 on motherboard > > ioapic1 irqs 24-47 on motherboard > > ichwd module loaded > > kbd1 at kbdmux0 > > ath_hal: 0.9.17.2 (AR5210, AR5211, AR5212, RF5111, RF5112, > RF2413, RF5413) > > acpi0: on motherboard > > acpi0: Power Button (fixed) > > Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 > > acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 > > cpu0: on acpi0 > > acpi_throttle0: on cpu0 > > pcib0: port 0xcf8-0xcff on acpi0 > > pci0: on pcib0 > > pcib1: irq 16 at device 2.0 on pci0 > > pci1: on pcib1 > > pcib2: irq 16 at device 3.0 on pci0 > > pci2: on pcib2 > > pcib3: at device 28.0 on pci0 > > pci3: on pcib3 > > twe0: <3ware Storage Controller. Driver version > 1.50.01.002> port 0xbc00-0xbc0f mem > 0xfc9ffc00-0xfc9ffc0f,0xfc00-0xfc7f irq 24 at device > 1.0 on pci3 > > twe0: [GIANT-LOCKED] > > twe0: 2 ports, Firmware FE8S 1.05.00.068, BIOS BE7X 1.08.00.048 > > em0: > port 0xb800-0xb83f mem 0xfc9c-0xfc9d irq 26 at device > 3.0 on pci3 > > em0: Ethernet address: 00:30:48:58:4d:2a > > em0: [FAST] > > em1: > port 0xb400-0xb43f mem 0xfc9a-0xfc9b irq 27 at device > 4.0 on pci3 > > em1: Ethernet address: 00:30:48:58:4d:2b > > em1: [FAST] > > uhci0: port 0xe800-0xe81f > irq 16 at device 29.0 on pci0 > > uhci0: [GIANT-LOCKED] > > usb0: on uhci0 > > usb0: USB revision 1.0 > > uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > > uhub0: 2 ports with 2 removable, self powered > > uhci1: port 0xec00-0xec1f > irq 19 at device 29.1 on pci0 > > uhci1: [GIANT-LOCKED] > > usb1: on uhci1 > > usb1: USB revision 1.0 > > uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > > uhub1: 2 ports with 2 removable, self powered > > pci0: at device 29.4 (no driver attached) > > pci0: at device > 29.5 (no driver attached) > > ehci0: mem > 0xfebffc00-0xfebf irq 23 at device 29.7 on pci0 > > ehci0: [GIANT-LOCKED] > > usb2: EHCI version 1.0 > > usb2: companion controllers, 2 ports each: usb0 usb1 > > usb2: on ehci0 > > usb2: USB revision 2.0 > > uhub2: Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 > > uhub2: 4 ports with 4 removable, self powered > > pcib4: at device 30.0 on pci0 > > pci4: on pcib4 > > pci4: at device 5.0 (no driver attached) > > isab0: at device 31.0 on pci0 > > isa0: on isab0 > > atapci0: port > 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xfc00-0xfc0f at device > 31.1 on pci0 > > ata0: on atapci0 > > ata1: on atapci0 > > pci0: at device 31.3 (no driver attached) > > acpi_button0: on acpi0 > > acpi_button1: on acpi0 > > sio0: configu
Re: System hangs up every day
On Wednesday 31 October 2007, Дмитрий Комалеев wrote: > Hello everybody > > I have a big problem > > There is one FreeBSD server in our company. The server platform is: > Supermicro SuperServer 6014V-T2B (2x Intel Xeon 2.8, 1Gb RAM, 3WARE > 3W-8006-2LP RAID-Controller). The server works as: > - a gateway between LAN and Internet > - an Intranet web- and database server (Apache + MySQL + PHP) > - a firewall (OpenBSD pf) Do you use any user or group rules as part of your pf.conf? If so, you should take a look at the pf.conf(5) man page - specificly the BUGS section. > - a transparent proxy server (Squid) > A mounthly traffic through this server is about 100Gb. There is about > 200 internet users in our conpany. Here is a part of my dmesg-listing: > > 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 6.2-RELEASE-p8 #2: Thu Oct 11 19:51:25 MSD 2007 > [EMAIL PROTECTED]:/usr/obj/usr/src/sys/KERNEL01_NOSMP > module_register: module pci/em already exists! > Module pci/em failed to register: 17 > ACPI APIC Table: > Timecounter "i8254" frequency 1193182 Hz quality 0 > CPU: Intel(R) Xeon(TM) CPU 2.80GHz (2800.12-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0xf43 Stepping = 3 > > Features=0xbfebfbffE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE> > Features2=0x641d> > AMD Features=0x2000 > Logical CPUs per core: 2 > real memory = 1073479680 (1023 MB) > avail memory = 1041465344 (993 MB) > ioapic0 irqs 0-23 on motherboard > ioapic1 irqs 24-47 on motherboard > ichwd module loaded > kbd1 at kbdmux0 > ath_hal: 0.9.17.2 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, > RF5413) acpi0: on motherboard > acpi0: Power Button (fixed) > Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 > acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 > cpu0: on acpi0 > acpi_throttle0: on cpu0 > pcib0: port 0xcf8-0xcff on acpi0 > pci0: on pcib0 > pcib1: irq 16 at device 2.0 on pci0 > pci1: on pcib1 > pcib2: irq 16 at device 3.0 on pci0 > pci2: on pcib2 > pcib3: at device 28.0 on pci0 > pci3: on pcib3 > twe0: <3ware Storage Controller. Driver version 1.50.01.002> port > 0xbc00-0xbc0f mem 0xfc9ffc00-0xfc9ffc0f,0xfc00-0xfc7f irq 24 at > device 1.0 on pci3 twe0: [GIANT-LOCKED] > twe0: 2 ports, Firmware FE8S 1.05.00.068, BIOS BE7X 1.08.00.048 > em0: port > 0xb800-0xb83f mem 0xfc9c-0xfc9d irq 26 at device 3.0 on pci3 > em0: Ethernet address: 00:30:48:58:4d:2a > em0: [FAST] > em1: port > 0xb400-0xb43f mem 0xfc9a-0xfc9b irq 27 at device 4.0 on pci3 > em1: Ethernet address: 00:30:48:58:4d:2b > em1: [FAST] > uhci0: port 0xe800-0xe81f irq 16 at > device 29.0 on pci0 uhci0: [GIANT-LOCKED] > usb0: on uhci0 > usb0: USB revision 1.0 > uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > uhub0: 2 ports with 2 removable, self powered > uhci1: port 0xec00-0xec1f irq 19 at > device 29.1 on pci0 uhci1: [GIANT-LOCKED] > usb1: on uhci1 > usb1: USB revision 1.0 > uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > uhub1: 2 ports with 2 removable, self powered > pci0: at device 29.4 (no driver attached) > pci0: at device 29.5 (no driver > attached) ehci0: mem > 0xfebffc00-0xfebf irq 23 at device 29.7 on pci0 ehci0: > [GIANT-LOCKED] > usb2: EHCI version 1.0 > usb2: companion controllers, 2 ports each: usb0 usb1 > usb2: on ehci0 > usb2: USB revision 2.0 > uhub2: Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 > uhub2: 4 ports with 4 removable, self powered > pcib4: at device 30.0 on pci0 > pci4: on pcib4 > pci4: at device 5.0 (no driver attached) > isab0: at device 31.0 on pci0 > isa0: on isab0 > atapci0: port > 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xfc00-0xfc0f at device 31.1 on > pci0 ata0: on atapci0 > ata1: on atapci0 > pci0: at device 31.3 (no driver attached) > acpi_button0: on acpi0 > acpi_button1: on acpi0 > sio0: configured irq 4 not in bitmap of probed irqs 0 > sio0: port may not be enabled > sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on > acpi0 sio0: type 16550A > sio1: configured irq 3 not in bitmap of probed irqs 0 > sio1: port may not be enabled > sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 > sio1: type 16550A > fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq > 2 on acpi0 fdc0: [FAST] > fd0: <1440-KB 3.5" drive> on fdc0 drive 0 > ppc0: port 0x378-0x37f,0x778-0x77f irq 7 > drq 3 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in > COMPATIBLE mode ppc0: FIFO with 16/16/9 bytes threshold > ppbus0: on ppc0 > plip0: on ppbus0 > lpt0: on ppbus0 > lpt0: Interrupt-driven port > ppi0: on ppbus0 > atkbdc0: port 0x60,0x64 irq 1 on acpi0 > atkbd0: irq 1 on atkbdc0 > kbd0 at atkbd0 > atkbd0: [GIANT-LOCKED] > psm0: irq 12 on atkbdc0 > psm0: [GIA
Re: System hangs up every day
A system failure of this sort (one which leaves no log entries of any kind) is generally a hardware fault; memory stick failures tend to cause kernel panics and easy repeatability. I would suggest examining the hardware components, the motherboard could have some faulty capacitors (burst, leaking, or swollen); the fans on the processors could be failing causing a lockup, the power supply fans could be failing causing an undervolt and lockup, but this usually makes the system reset. You get the idea, your symptoms are pointing to hardware issues in my opinion. David Or as I've seen a few times a power supply that cannot handle the load. You have 2 CPU's and a few hard disks which are sucking electricity. What rating power supply are you using? I've found FreeBSD to be finicky about hardware. If the hardware is all good it works perfectly and never lets you down. Something starts going faulty and FreeBSD hangs. Other OS's tend to chug along unpredictably instead. If it's not the power supply it's possibly the raid card. I'm asuming you used the same raid card when you moved the drives to the other server. Just my 2c -Clay On 10/31/07, Дмитрий Комалеев <[EMAIL PROTECTED]> wrote: Hello everybody I have a big problem There is one FreeBSD server in our company. The server platform is: Supermicro SuperServer 6014V-T2B (2x Intel Xeon 2.8, 1Gb RAM, 3WARE 3W-8006-2LP RAID-Controller). The server works as: - a gateway between LAN and Internet - an Intranet web- and database server (Apache + MySQL + PHP) - a firewall (OpenBSD pf) - a transparent proxy server (Squid) A mounthly traffic through this server is about 100Gb. There is about 200 internet users in our conpany. Here is a part of my dmesg-listing: 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 6.2-RELEASE-p8 #2: Thu Oct 11 19:51:25 MSD 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/KERNEL01_NOSMP module_register: module pci/em already exists! Module pci/em failed to register: 17 ACPI APIC Table: Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(TM) CPU 2.80GHz (2800.12-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf43 Stepping = 3 Features=0xbfebfbff Features2=0x641d> AMD Features=0x2000 Logical CPUs per core: 2 real memory = 1073479680 (1023 MB) avail memory = 1041465344 (993 MB) ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-47 on motherboard ichwd module loaded kbd1 at kbdmux0 ath_hal: 0.9.17.2 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) acpi0: on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 cpu0: on acpi0 acpi_throttle0: on cpu0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: irq 16 at device 2.0 on pci0 pci1: on pcib1 pcib2: irq 16 at device 3.0 on pci0 pci2: on pcib2 pcib3: at device 28.0 on pci0 pci3: on pcib3 twe0: <3ware Storage Controller. Driver version 1.50.01.002> port 0xbc00-0xbc0f mem 0xfc9ffc00-0xfc9ffc0f,0xfc00-0xfc7f irq 24 at device 1.0 on pci3 twe0: [GIANT-LOCKED] twe0: 2 ports, Firmware FE8S 1.05.00.068, BIOS BE7X 1.08.00.048 em0: port 0xb800-0xb83f mem 0xfc9c-0xfc9d irq 26 at device 3.0 on pci3 em0: Ethernet address: 00:30:48:58:4d:2a em0: [FAST] em1: port 0xb400-0xb43f mem 0xfc9a-0xfc9b irq 27 at device 4.0 on pci3 em1: Ethernet address: 00:30:48:58:4d:2b em1: [FAST] uhci0: port 0xe800-0xe81f irq 16 at device 29.0 on pci0 uhci0: [GIANT-LOCKED] usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: port 0xec00-0xec1f irq 19 at device 29.1 on pci0 uhci1: [GIANT-LOCKED] usb1: on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered pci0: at device 29.4 (no driver attached) pci0: at device 29.5 (no driver attached) ehci0: mem 0xfebffc00-0xfebf irq 23 at device 29.7 on pci0 ehci0: [GIANT-LOCKED] usb2: EHCI version 1.0 usb2: companion controllers, 2 ports each: usb0 usb1 usb2: on ehci0 usb2: USB revision 2.0 uhub2: Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub2: 4 ports with 4 removable, self powered pcib4: at device 30.0 on pci0 pci4: on pcib4 pci4: at device 5.0 (no driver attached) isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xfc00-0xfc0f at device 31.1 on pci0 ata0: on atapci0 ata1: on atapci0 pci0: at device 31.3 (no driver attached) acpi_button0: on acpi0 acpi_button1: on acpi0 sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: <16550A-compatible COM port> port
