ATAng lockups (Re: geom-ata forever cycle)
Sat, Nov 22, 2003 at 13:08:10, netch (Valentin Nechayev) wrote about geom-ata forever cycle: VN 5.1-current of 2003-11-20 hangs during kernel initialization with forever VN cycle around geom partitioning detection and ATA read failure. VN Message rate is too fast to record, no stopping is available, no serial VN console. VN Previous 5-current on this machine was of 2003-05-23. VN How to diagnose? Well, I restricted time interval to between 2003-08-18 and 2003-08-25, so it is ATAng. Also tested 2003-11-20 and 2003-10-06 with the same result. Different poses were seen: - forever cycle around GEOM detecting - simple lockup - panic(initiate_write_inodeblock_ufs1: already started) - another kinds of panic and all have common sign - impossibility of driver to dig itself out of lockup (switch to PIO, reset bus, etc.) Dirty fix works to set hw.ata.ata_dma=0 in loader; moreover, `atacontrol mode 1 udma100 -' doesn't cause problems, but `atacontrol mode 0 udma33 -' drops system to broken state in a few minutes. Please say how to dig this problem. Full verbose dmesg.boot (from 2003-08-18 kernel) and config (unchanged) was put in previous letters and can be resent personally. Entries, bound with ATA, in first problematic (2003-08-25) dmesg.boot: pcib0: Intel 82815 (i815 GMCH) Host To Hub bridge at pcibus 0 on motherboard atapci0: Intel ICH2 UDMA100 controller port 0xf000-0xf00f at device 31.1 on pci0 ata0: pre reset mask=03 ostat0=50 ostat2=00 ata0-master: ATAPI 00 00 ata0-slave: ATAPI 14 eb ata0: after reset mask=03 stat0=50 stat1=00 ata0-master: ATA 01 a5 ata0: devices=09 ata0: at 0x1f0 irq 14 on atapci0 ata0-slave: pio=0x0c wdma=0x22 udma=0x42 cable=40pin ata0-master: pio=0x0c wdma=0x22 udma=0x44 cable=40pin ad0: setting PIO4 on Intel ICH2 chip ad0: IBM-DJNA-351520/J56OA30K ATA-4 disk at ata0-master ad0: 14664MB (30033360 sectors), 29795 C, 16 H, 63 S, 512 B ad0: 16 secs/int, 1 depth queue, PIO4 acd0: setting PIO4 on Intel ICH2 chip acd0: CD-540E/1.0A CDROM drive at ata0 as slave acd0: read 6890KB/s (6890KB/s), 128KB buffer, PIO4 (remind that it is with hw.ata.ata_dma=0) -netch- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
geom-ata forever cycle
5.1-current of 2003-11-20 hangs during kernel initialization with forever cycle around geom partitioning detection and ATA read failure. Message rate is too fast to record, no stopping is available, no serial console. Previous 5-current on this machine was of 2003-05-23. How to diagnose? dmesg of May's current says: start_init: trying /sbin/init ad0: UDMA ICRC error cmd=read fsbn 4397730 of 4397730-4397857 retrying ad0: UDMA ICRC error cmd=read fsbn 4398442 of 4398442-4398569 retrying ad0: UDMA ICRC error cmd=read fsbn 4398442 of 4398442-4398569 retrying ad0: UDMA ICRC error cmd=read fsbn 4398442 of 4398442-4398569 retrying ad0: UDMA ICRC error cmd=read fsbn 4398442 of 4398442-4398569ad0: success settin g PIO4 on Intel ICH2 chip falling back to PIO mode Main FreeBSD here is 4.9-release which doesn't complaint to crc errors. Kernel config wasn't changed: machine i386 cpu I486_CPU cpu I586_CPU cpu I686_CPU ident nn15 maxusers0 #To statically compile in device wiring instead of /boot/device.hints hints GENERIC.hints #Default places to look for devices. makeoptions DEBUG=-g#Build kernel with gdb(1) debug symbols options SCHED_4BSD options INET#InterNETworking options INET6 #IPv6 communications protocols options FFS #Berkeley Fast Filesystem options SOFTUPDATES #Enable FFS soft updates support #optionsUFS_ACL #Support for access control lists options UFS_DIRHASH #Improve performance on big directories options MSDOSFS #MSDOS Filesystem options CD9660 #ISO 9660 Filesystem options PROCFS #Process filesystem (requires PSEUDOFS) options PSEUDOFS#Pseudo-filesystem framework options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options COMPAT_FREEBSD4 #Compatible with FreeBSD4 options KTRACE #ktrace(1) support options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores options _KPOSIX_PRIORITY_SCHEDULING #Posix P1003_1B real-time extensions options KBD_INSTALL_CDEV# install a CDEV entry in /dev # Debugging for use in -current options DDB #Enable the kernel debugger options INVARIANTS #Enable calls of extra sanity checking options INVARIANT_SUPPORT #Extra sanity checks of internal structures, required by INVARIANTS options WITNESS #Enable checks to detect deadlocks and cycles options WITNESS_SKIPSPIN#Don't run witness on spinlocks for speed device isa device pci # ATA and ATAPI devices device ata device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives options ATA_STATIC_ID #Static device numbering # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc # AT keyboard controller device atkbd # AT keyboard device psm # PS/2 mouse device vga # VGA video card driver device splash # Splash screen and screen saver support # syscons is the default console driver, resembling an SCO console device sc device agp # support several AGP chipsets # Floating point support - do not disable. device npx # Add suspend/resume support for the i8254. device pmtimer # Serial (COM) ports device sio # 8250, 16[45]50 based serial ports # Pseudo devices - the number indicates how many units to allocate. device random # Entropy device device ether device loop# Network loopback device ppp # Kernel PPP device tun # Packet tunnel. device pty # Pseudo-ttys (telnet etc) device md # Memory disks # The `bpf' device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! device bpf # Berkeley packet filter device speaker #Play IBM BASIC-style noises out your speaker # To include support for VGA VESA video modes options VESA # Turn on extra debugging checks and output for VESA support. options VESA_DEBUG # Enable i386 a.out binary support options COMPAT_AOUT # Enable the linux-like proc filesystem support (requires COMPAT_LINUX # and PSEUDOFS) options COMPAT_LINUX options LINPROCFS options MSGBUF_SIZE=131072 #options
Re: geom-ata forever cycle
Personally I dont think this is GEOM related. I had a drive start doing this to me (happens often as I work in a large datacenter) and the drive is about to die. What brand drive is it and how old is it? You may waanna look into replacing the drive if you have that option. I had one tonight that did that to me, swap the drive, fixed. Regards, Nick H. Network Operations Center [EMAIL PROTECTED] Please rate my performance! http://www.supportteam.net/rate.php3 Please submit all new support requests to http://ticketmonster.hostingsupport.com/ --- Privileged/Confidential Information may be contained in this message. If you are not the addressee indicated in this message (or responsible for delivery of the message to such person), you may not copy or deliver this message to anyone. In such case, you should destroy this message and kindly notify the sender by reply email. Please advise immediately if you or your employer do not consent to Internet email for messages of this kind. Opinions, conclusions and other information in this message that do not relate to the official business of my firm shall be understood as neither given nor endorsed by it. - Original Message - From: Valentin Nechayev [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Saturday, November 22, 2003 5:08 AM Subject: geom-ata forever cycle 5.1-current of 2003-11-20 hangs during kernel initialization with forever cycle around geom partitioning detection and ATA read failure. Message rate is too fast to record, no stopping is available, no serial console. Previous 5-current on this machine was of 2003-05-23. How to diagnose? dmesg of May's current says: start_init: trying /sbin/init ad0: UDMA ICRC error cmd=read fsbn 4397730 of 4397730-4397857 retrying ad0: UDMA ICRC error cmd=read fsbn 4398442 of 4398442-4398569 retrying ad0: UDMA ICRC error cmd=read fsbn 4398442 of 4398442-4398569 retrying ad0: UDMA ICRC error cmd=read fsbn 4398442 of 4398442-4398569 retrying ad0: UDMA ICRC error cmd=read fsbn 4398442 of 4398442-4398569ad0: success settin g PIO4 on Intel ICH2 chip falling back to PIO mode Main FreeBSD here is 4.9-release which doesn't complaint to crc errors. Kernel config wasn't changed: machine i386 cpu I486_CPU cpu I586_CPU cpu I686_CPU ident nn15 maxusers 0 #To statically compile in device wiring instead of /boot/device.hints hints GENERIC.hints #Default places to look for devices. makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols options SCHED_4BSD options INET #InterNETworking options INET6 #IPv6 communications protocols options FFS #Berkeley Fast Filesystem options SOFTUPDATES #Enable FFS soft updates support #options UFS_ACL #Support for access control lists options UFS_DIRHASH #Improve performance on big directories options MSDOSFS #MSDOS Filesystem options CD9660 #ISO 9660 Filesystem options PROCFS #Process filesystem (requires PSEUDOFS) options PSEUDOFS #Pseudo-filesystem framework options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options COMPAT_FREEBSD4 #Compatible with FreeBSD4 options KTRACE #ktrace(1) support options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores options _KPOSIX_PRIORITY_SCHEDULING #Posix P1003_1B real-time extensions options KBD_INSTALL_CDEV # install a CDEV entry in /dev # Debugging for use in -current options DDB #Enable the kernel debugger options INVARIANTS #Enable calls of extra sanity checking options INVARIANT_SUPPORT #Extra sanity checks of internal structures, required by INVARIANTS options WITNESS #Enable checks to detect deadlocks and cycles options WITNESS_SKIPSPIN #Don't run witness on spinlocks for speed device isa device pci # ATA and ATAPI devices device ata device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives options ATA_STATIC_ID #Static device numbering # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc # AT keyboard controller device atkbd # AT keyboard device psm # PS/2 mouse device vga # VGA video card driver device splash # Splash screen and screen saver support # syscons is the default console driver, resembling an SCO console device sc device agp # support several AGP chipsets # Floating point support - do not disable. device npx # Add suspend/resume support for the i8254. device pmtimer # Serial (COM) ports device sio # 8250, 16[45]50 based serial ports # Pseudo devices - the number indicates how many units to allocate. device random # Entropy device device ether device loop # Network loopback device ppp # Kernel PPP device tun # Packet tunnel. device pty # Pseudo-ttys (telnet etc) device md # Memory disks # The `bpf' device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! device bpf # Berkeley packet filter device speaker #Play IBM BASIC-style noises
Re: geom-ata forever cycle
Here's a snippet of dmesg that was before the drive was swapped: Nov 22 09:58:04 juan kernel: ad3: UDMA ICRC error cmd=read fsbn 0 of 0-15 retrying Nov 22 09:58:04 juan last message repeated 2 times Nov 22 09:58:04 juan kernel: ad3: UDMA ICRC error cmd=read fsbn 0 of 0-15 falling back to PIO mode Nov 22 09:58:40 juan kernel: ad2: UDMA ICRC error cmd=write fsbn 1756413 of 1756413-1756497 retrying Nov 22 09:58:40 juan last message repeated 2 times Nov 22 09:58:41 juan kernel: ad2: UDMA ICRC error cmd=write fsbn 34624421 of 34624421-34624548 retrying Nov 22 09:58:42 juan kernel: ad2: UDMA ICRC error cmd=write fsbn 41273248 of 41273248-41273374 retrying Nov 22 09:58:42 juan last message repeated 2 times Nov 22 09:58:42 juan kernel: ad2: UDMA ICRC error cmd=write fsbn 41273248 of 41273248-41273374 falling back to PIO mode After replacing the drive, error gone. Regards, Nick H. Network Operations Center [EMAIL PROTECTED] Please rate my performance! http://www.supportteam.net/rate.php3 Please submit all new support requests to http://ticketmonster.hostingsupport.com/ --- Privileged/Confidential Information may be contained in this message. If you are not the addressee indicated in this message (or responsible for delivery of the message to such person), you may not copy or deliver this message to anyone. In such case, you should destroy this message and kindly notify the sender by reply email. Please advise immediately if you or your employer do not consent to Internet email for messages of this kind. Opinions, conclusions and other information in this message that do not relate to the official business of my firm shall be understood as neither given nor endorsed by it. - Original Message - From: Nick H. -- Network Operations [EMAIL PROTECTED] To: Valentin Nechayev [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Saturday, November 22, 2003 5:45 AM Subject: Re: geom-ata forever cycle Personally I dont think this is GEOM related. I had a drive start doing this to me (happens often as I work in a large datacenter) and the drive is about to die. What brand drive is it and how old is it? You may waanna look into replacing the drive if you have that option. I had one tonight that did that to me, swap the drive, fixed. Regards, Nick H. Network Operations Center [EMAIL PROTECTED] Please rate my performance! http://www.supportteam.net/rate.php3 Please submit all new support requests to http://ticketmonster.hostingsupport.com/ --- Privileged/Confidential Information may be contained in this message. If you are not the addressee indicated in this message (or responsible for delivery of the message to such person), you may not copy or deliver this message to anyone. In such case, you should destroy this message and kindly notify the sender by reply email. Please advise immediately if you or your employer do not consent to Internet email for messages of this kind. Opinions, conclusions and other information in this message that do not relate to the official business of my firm shall be understood as neither given nor endorsed by it. - Original Message - From: Valentin Nechayev [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Saturday, November 22, 2003 5:08 AM Subject: geom-ata forever cycle 5.1-current of 2003-11-20 hangs during kernel initialization with forever cycle around geom partitioning detection and ATA read failure. Message rate is too fast to record, no stopping is available, no serial console. Previous 5-current on this machine was of 2003-05-23. How to diagnose? dmesg of May's current says: start_init: trying /sbin/init ad0: UDMA ICRC error cmd=read fsbn 4397730 of 4397730-4397857 retrying ad0: UDMA ICRC error cmd=read fsbn 4398442 of 4398442-4398569 retrying ad0: UDMA ICRC error cmd=read fsbn 4398442 of 4398442-4398569 retrying ad0: UDMA ICRC error cmd=read fsbn 4398442 of 4398442-4398569 retrying ad0: UDMA ICRC error cmd=read fsbn 4398442 of 4398442-4398569ad0: success settin g PIO4 on Intel ICH2 chip falling back to PIO mode Main FreeBSD here is 4.9-release which doesn't complaint to crc errors. Kernel config wasn't changed: machine i386 cpu I486_CPU cpu I586_CPU cpu I686_CPU ident nn15 maxusers 0 #To statically compile in device wiring instead of /boot/device.hints hints GENERIC.hints #Default places to look for devices. makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols options SCHED_4BSD options INET #InterNETworking options INET6 #IPv6 communications protocols options FFS #Berkeley Fast Filesystem options SOFTUPDATES #Enable FFS soft updates support #options UFS_ACL #Support for access control lists options UFS_DIRHASH #Improve performance on big directories options MSDOSFS #MSDOS Filesystem options CD9660 #ISO 9660 Filesystem options PROCFS #Process filesystem
Re: geom-ata forever cycle
Sat, Nov 22, 2003 at 05:45:09, nickh wrote about Re: geom-ata forever cycle: Personally I dont think this is GEOM related. I had a drive start doing Yes, it is ATAng related, AFAIS, but triggers GEOM forever cycle. this to me (happens often as I work in a large datacenter) and the drive is about to die. What brand drive is it and how old is it? You may waanna look into replacing the drive if you have that option. I had one tonight that did that to me, swap the drive, fixed. System has IBM DJNA-351520 and IBM IC35L040AVER07. They are alive and good. All other systems, including Win98, RedHat 8.0, FreeBSD 4.9 and FreeBSD-5.1 of May 2003, works well with these drivers. Hence, only fresh -current is broken. Full dmesg.boot of oldest -current follows. Copyright (c) 1992-2003 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.1-BETA-20030523 #2: Sun May 25 00:28:30 EEST 2003 root@:/var/obj/var/HEAD/src/sys/nn15 Preloaded elf kernel /boot/kernel/kernel at 0xc044c000. Preloaded elf module /boot/modules/if_rl.ko at 0xc044c1f4. Preloaded elf module /boot/modules/miibus.ko at 0xc044c2a0. Calibrating clock(s) ... i8254 clock: 1193010 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter i8254 frequency 1193182 Hz Calibrating TSC clock ... TSC clock: 799435869 Hz Timecounter TSC frequency 799435869 Hz CPU: Intel Celeron (799.44-MHz 686-class CPU) Origin = GenuineIntel Id = 0x686 Stepping = 6 Features=0x383f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE real memory = 268369920 (255 MB) Physical memory chunk(s): 0x1000 - 0x0009efff, 647168 bytes (158 pages) 0x00473000 - 0x0fb31fff, 258732032 bytes (63167 pages) avail memory = 255709184 (243 MB) bios32: Found BIOS32 Service Directory header at 0xc00fad00 bios32: Entry = 0xfb190 (c00fb190) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xf+0xb1c0 pnpbios: Found PnP BIOS data at 0xc00fbbb0 pnpbios: Entry = f:bbe0 Rev = 1.0 Other BIOS signatures found: null: null device, zero device random: entropy source mem: memory I/O Pentium Pro MTRR support enabled VESA: information block 56 45 53 41 00 03 00 01 00 01 01 00 00 00 22 00 00 01 80 00 05 02 07 01 00 01 1a 01 00 01 23 01 00 01 00 01 01 01 02 01 03 01 04 01 05 01 06 01 07 01 08 01 09 01 0a 01 0b 01 0c 01 0e 01 0f 01 VESA: 33 mode(s) found VESA: v3.0, 8192k memory, flags:0x1, mode table:0xc03ac7c2 (122) VESA: NVidia VESA: NVidia Corporation Riva TNT Chip Rev B1 npx0: math processor on motherboard npx0: INT 16 interface pci_open(1):mode 1 addr port (0x0cf8) is 0x8058 pci_open(1a): mode1res=0x8000 (0x8000) pci_cfgcheck: device 0 [class=06] [hdr=00] is there (id=11308086) pcibios: BIOS version 2.10 Using $PIR table, 10 entries at 0xc00fded0 PCI-Only Interrupts: 5 9 11 Location Bus Device Pin Link IRQs slot 1 02A 0x60 3 4 5 7 9 10 11 14 15 slot 1 02B 0x61 3 4 5 7 9 10 11 14 15 slot 1 02C 0x62 3 4 5 7 9 10 11 14 15 slot 1 02D 0x63 3 4 5 7 9 10 11 14 15 slot 2 28A 0x68 3 4 5 7 9 10 11 14 15 slot 2 28B 0x69 3 4 5 7 9 10 11 14 15 slot 2 28C 0x6a 3 4 5 7 9 10 11 14 15 slot 2 28D 0x6b 3 4 5 7 9 10 11 14 15 slot 3 20A 0x60 3 4 5 7 9 10 11 14 15 slot 3 20B 0x61 3 4 5 7 9 10 11 14 15 slot 3 20C 0x62 3 4 5 7 9 10 11 14 15 slot 3 20D 0x63 3 4 5 7 9 10 11 14 15 slot 4 21A 0x61 3 4 5 7 9 10 11 14 15 slot 4 21B 0x62 3 4 5 7 9 10 11 14 15 slot 4 21C 0x63 3 4 5 7 9 10 11 14 15 slot 4 21D 0x60 3 4 5 7 9 10 11 14 15 slot 5 26A 0x62 3 4 5 7 9 10 11 14 15 slot 5 26B 0x63 3 4 5 7 9 10 11 14 15 slot 5 26C 0x60 3 4 5 7 9 10 11 14 15 slot 5 26D 0x61 3 4 5 7 9 10 11 14 15 slot 6 27A 0x63 3 4 5 7 9 10 11 14 15 slot 6 27B 0x60 3 4 5 7 9 10 11 14 15 slot 6 27C 0x61 3 4 5 7 9 10 11 14 15 slot 6 27D 0x62 3 4 5 7 9 10 11 14 15 slot 7 29A 0x61 3 4 5 7 9 10 11 14 15 slot 7 29B 0x62 3 4 5 7 9 10 11 14 15 slot 7 29C 0x63 3 4 5 7 9 10 11 14 15 slot 7 29D 0x60 3 4 5 7 9 10 11 14 15 slot 8 2 10A 0x62 3 4 5 7 9 10 11 14 15 slot 8 2 10B 0x63 3 4 5 7 9 10 11 14 15 slot 8 2 10C 0x60 3 4 5 7 9 10 11 14 15 slot 8 2 10D 0x61 3 4 5 7 9 10 11 14 15 embedded0 31A 0x60 3 4 5 7 9 10 11 14 15 embedded0 31B 0x61 3 4 5 7 9 10 11 14 15 embedded0 31C 0x6b 3 4 5 7 9 10 11 14 15 embedded0 31D 0x63 3 4 5 7 9 10 11 14 15 embedded01
Re: geom-ata forever cycle
heh. IBM? It's bad. All of the ones that I had (also running -current from within 24 hours) that were spitting that were bad (All were POS IBMs too!). Just my guess, however. Regards, Nick H. Network Operations Center [EMAIL PROTECTED] Please rate my performance! http://www.supportteam.net/rate.php3 Please submit all new support requests to http://ticketmonster.hostingsupport.com/ --- Privileged/Confidential Information may be contained in this message. If you are not the addressee indicated in this message (or responsible for delivery of the message to such person), you may not copy or deliver this message to anyone. In such case, you should destroy this message and kindly notify the sender by reply email. Please advise immediately if you or your employer do not consent to Internet email for messages of this kind. Opinions, conclusions and other information in this message that do not relate to the official business of my firm shall be understood as neither given nor endorsed by it. - Original Message - From: Valentin Nechayev [EMAIL PROTECTED] To: Nick H. -- Network Operations [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Saturday, November 22, 2003 8:21 AM Subject: Re: geom-ata forever cycle Sat, Nov 22, 2003 at 05:45:09, nickh wrote about Re: geom-ata forever cycle: Personally I dont think this is GEOM related. I had a drive start doing Yes, it is ATAng related, AFAIS, but triggers GEOM forever cycle. this to me (happens often as I work in a large datacenter) and the drive is about to die. What brand drive is it and how old is it? You may waanna look into replacing the drive if you have that option. I had one tonight that did that to me, swap the drive, fixed. System has IBM DJNA-351520 and IBM IC35L040AVER07. They are alive and good. All other systems, including Win98, RedHat 8.0, FreeBSD 4.9 and FreeBSD-5.1 of May 2003, works well with these drivers. Hence, only fresh -current is broken. Full dmesg.boot of oldest -current follows. Copyright (c) 1992-2003 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.1-BETA-20030523 #2: Sun May 25 00:28:30 EEST 2003 root@:/var/obj/var/HEAD/src/sys/nn15 Preloaded elf kernel /boot/kernel/kernel at 0xc044c000. Preloaded elf module /boot/modules/if_rl.ko at 0xc044c1f4. Preloaded elf module /boot/modules/miibus.ko at 0xc044c2a0. Calibrating clock(s) ... i8254 clock: 1193010 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter i8254 frequency 1193182 Hz Calibrating TSC clock ... TSC clock: 799435869 Hz Timecounter TSC frequency 799435869 Hz CPU: Intel Celeron (799.44-MHz 686-class CPU) Origin = GenuineIntel Id = 0x686 Stepping = 6 Features=0x383f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV, PAT,PSE36,MMX,FXSR,SSE real memory = 268369920 (255 MB) Physical memory chunk(s): 0x1000 - 0x0009efff, 647168 bytes (158 pages) 0x00473000 - 0x0fb31fff, 258732032 bytes (63167 pages) avail memory = 255709184 (243 MB) bios32: Found BIOS32 Service Directory header at 0xc00fad00 bios32: Entry = 0xfb190 (c00fb190) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xf+0xb1c0 pnpbios: Found PnP BIOS data at 0xc00fbbb0 pnpbios: Entry = f:bbe0 Rev = 1.0 Other BIOS signatures found: null: null device, zero device random: entropy source mem: memory I/O Pentium Pro MTRR support enabled VESA: information block 56 45 53 41 00 03 00 01 00 01 01 00 00 00 22 00 00 01 80 00 05 02 07 01 00 01 1a 01 00 01 23 01 00 01 00 01 01 01 02 01 03 01 04 01 05 01 06 01 07 01 08 01 09 01 0a 01 0b 01 0c 01 0e 01 0f 01 VESA: 33 mode(s) found VESA: v3.0, 8192k memory, flags:0x1, mode table:0xc03ac7c2 (122) VESA: NVidia VESA: NVidia Corporation Riva TNT Chip Rev B1 npx0: math processor on motherboard npx0: INT 16 interface pci_open(1): mode 1 addr port (0x0cf8) is 0x8058 pci_open(1a): mode1res=0x8000 (0x8000) pci_cfgcheck: device 0 [class=06] [hdr=00] is there (id=11308086) pcibios: BIOS version 2.10 Using $PIR table, 10 entries at 0xc00fded0 PCI-Only Interrupts: 5 9 11 Location Bus Device Pin Link IRQs slot 1 02A 0x60 3 4 5 7 9 10 11 14 15 slot 1 02B 0x61 3 4 5 7 9 10 11 14 15 slot 1 02C 0x62 3 4 5 7 9 10 11 14 15 slot 1 02D 0x63 3 4 5 7 9 10 11 14 15 slot 2 28A 0x68 3 4 5 7 9 10 11 14 15 slot 2 28B 0x69 3 4 5 7 9 10 11 14 15 slot 2 28C 0x6a 3 4 5 7 9 10 11 14 15 slot 2 28D 0x6b 3 4 5 7 9 10 11 14 15 slot 3 20A 0x60 3 4 5 7 9 10 11 14 15 slot 3 20B 0x61 3 4 5 7 9 10 11 14 15 slot 3 20C 0x62 3 4 5 7 9 10 11 14 15 slot 3 20D 0x63 3 4 5 7 9 10 11 14
