BIOS-e820: 0000000000000000 - 000000000009f800 (usable) BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved) BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved) BIOS-e820: 0000000000100000 - 000000003fff0000 (usable) BIOS-e820: 000000003fff0000 - 000000003fff3000 (ACPI NVS) BIOS-e820: 000000003fff3000 - 0000000040000000 (ACPI data) BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved) BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved) BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved) Warning only 896MB will be used. Use a HIGHMEM enabled kernel. On node 0 totalpages: 229376 zone(0): 4096 pages. zone(1): 225280 pages. zone(2): 0 pages. Kernel command line: BOOT_IMAGE=Linux ro root=301 Detected 1660.022 MHz processor. Console: colour dummy device 80x25 Calibrating delay loop... 3309.56 BogoMIPS Page-cache hash table entries: 262144 (order: 8, 1048576 bytes) CPU: AMD Sempron(tm) 2400+ stepping 01 POSIX conformance testing by UNIFIX mtrr: v1.40 (20010327) Richard Gooch (rgooch@atnf.csiro.au) mtrr: detected mtrr type: Intel PCI: Probing PCI hardware (bus 00) Initializing RT netlink socket Starting kswapd Console: switching to colour frame buffer device 128x48 pty: 512 Unix98 ptys configured RAMDISK driver initialized: 16 RAM disks of 7777K size 1024 blocksize hda: WDC WD1600JB-00FUA0, ATA DISK drive blk: queue c03af460, I/O limit 4095Mb (mask 0xffffffff) hdc: PLEXTOR DVD-ROM PX-116A2 0100, ATAPI CD/DVD-ROM drive ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 ide1 at 0x170-0x177,0x376 on irq 15 hda: attached ide-disk driver. hda: host protected area => 1 hdc: attached ide-cdrom driver. kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter, errno = 2 ssage repeated 2 times 8regs : 2378.400 MB/sec 32regs : 1585.200 MB/sec pIII_sse : 2040.800 MB/sec pII_mmx : 3883.200 MB/sec p5_mmx : 4961.200 MB/sec raid5: using function: pIII_sse (2040.800 MB/sec) FAT: bogus logical sector size 0 ssage repeated 2 times reiserfs: found format "3.6" with standard journal reiserfs: checking transaction log (device ide0(3,1)) ... for (ide0(3,1)) ide0(3,1):Using r5 hash to sort names VFS: Mounted root (reiserfs filesystem) readonly. agpgart: Unsupported Via chipset (device id: 0269), you might want to try agp_try_unsupported=1. reiserfs: found format "3.6" with standard journal reiserfs: checking transaction log (device ide0(3,6)) ... for (ide0(3,6)) ide0(3,6):Using r5 hash to sort names reiserfs: found format "3.6" with standard journal reiserfs: checking transaction log (device ide0(3,7)) ... for (ide0(3,7)) ide0(3,7):Using r5 hash to sort names 3c59x: Donald Becker and others. www.scyld.com/network/vortex.html shpchp: shpc_init : shpc_cap_offset == 0 /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed shpchp: shpc_init : shpc_cap_offset == 0 /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed shpchp: shpc_init : shpc_cap_offset == 0 /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed shpchp: shpc_init : shpc_cap_offset == 0 /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed shpchp: shpc_init : shpc_cap_offset == 0 /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed shpchp: shpc_init : shpc_cap_offset == 0 /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed shpchp: shpc_init : shpc_cap_offset == 0 /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed shpchp: shpc_init : shpc_cap_offset == 0 /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed shpchp: shpc_init : shpc_cap_offset == 0 /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed shpchp: shpc_init : shpc_cap_offset == 0 /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed shpchp: shpc_init : shpc_cap_offset == 0 /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed shpchp: shpc_init : shpc_cap_offset == 0 /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed shpchp: shpc_init : shpc_cap_offset == 0 /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed shpchp: shpc_init : shpc_cap_offset == 0 /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed shpchp: shpc_init : shpc_cap_offset == 0 /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed shpchp: shpc_init : shpc_cap_offset == 0 /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed shpchp: shpc_init : shpc_cap_offset == 0 /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed shpchp: shpc_init : shpc_cap_offset == 0 /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed shpchp: shpc_init : shpc_cap_offset == 0 /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed shpchp: shpc_init : shpc_cap_offset == 0 /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed Unable to handle kernel NULL pointer dereference at virtual address 0000002c printing eip: c015363f *pde = 00000000 Oops: 0000 CPU: 0 EIP: 0010:[] Not tainted EFLAGS: 00010246 eax: 00000000 ebx: f690d480 ecx: f38d4000 edx: 00000000 esi: f38d5d74 edi: fffffffb ebp: 00000000 esp: f38d5c70 ds: 0018 es: 0018 ss: 0018 Process reboot (pid: 5270, stackpage=f38d5000) Stack: c0108ba4 f38d5c7c 00000002 00000000 000000c0 00000000 00000000 00000000 00000005 00000802 00000000 00000000 00000000 00000000 f690d480 0804ad14 00000000 f6e58900 00000000 c0153d50 f38d5d74 f6e58900 f38d5d3c f79beea0 Call Trace: [] [] [] [] [] [] [] [] [] Code: 8b 48 2c 8d 41 1c ba 01 00 ff ff 0f c1 10 85 d2 0f 85 72 1c Linux version 2.4.31 (root@tree) (gcc version 3.3.5) #6 Sun Jun 5 19:04:47 PDT 2005 BIOS-e820: 0000000000000000 - 000000000009f800 (usable) BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved) BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved) BIOS-e820: 0000000000100000 - 000000003fff0000 (usable) BIOS-e820: 000000003fff0000 - 000000003fff3000 (ACPI NVS) BIOS-e820: 000000003fff3000 - 0000000040000000 (ACPI data) BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved) BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved) BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved) Warning only 896MB will be used. Use a HIGHMEM enabled kernel. On node 0 totalpages: 229376 zone(0): 4096 pages. zone(1): 225280 pages. zone(2): 0 pages. Kernel command line: BOOT_IMAGE=Linux ro root=301 Detected 1660.022 MHz processor. Console: colour dummy device 80x25 Calibrating delay loop... 3309.56 BogoMIPS Page-cache hash table entries: 262144 (order: 8, 1048576 bytes) CPU: AMD Sempron(tm) 2400+ stepping 01 POSIX conformance testing by UNIFIX mtrr: v1.40 (20010327) Richard Gooch (rgooch@atnf.csiro.au) mtrr: detected mtrr type: Intel PCI: Probing PCI hardware (bus 00) Initializing RT netlink socket Starting kswapd Console: switching to colour frame buffer device 128x48 pty: 512 Unix98 ptys configured RAMDISK driver initialized: 16 RAM disks of 7777K size 1024 blocksize hda: WDC WD1600JB-00FUA0, ATA DISK drive blk: queue c03af460, I/O limit 4095Mb (mask 0xffffffff) hdc: PLEXTOR DVD-ROM PX-116A2 0100, ATAPI CD/DVD-ROM drive ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 ide1 at 0x170-0x177,0x376 on irq 15 hda: attached ide-disk driver. hda: host protected area => 1 hdc: attached ide-cdrom driver. kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter, errno = 2 ssage repeated 2 times 8regs : 2378.400 MB/sec 32regs : 1585.200 MB/sec pIII_sse : 2020.800 MB/sec pII_mmx : 3883.200 MB/sec p5_mmx : 4961.200 MB/sec raid5: using function: pIII_sse (2020.800 MB/sec) FAT: bogus logical sector size 0 ssage repeated 2 times reiserfs: found format "3.6" with standard journal reiserfs: checking transaction log (device ide0(3,1)) ... for (ide0(3,1)) reiserfs: replayed 43 transactions in 0 seconds ide0(3,1):Using r5 hash to sort names VFS: Mounted root (reiserfs filesystem) readonly. agpgart: Unsupported Via chipset (device id: 0269), you might want to try agp_try_unsupported=1. reiserfs: found format "3.6" with standard journal reiserfs: checking transaction log (device ide0(3,6)) ... for (ide0(3,6)) reiserfs: replayed 5 transactions in 0 seconds ide0(3,6):Using r5 hash to sort names reiserfs: found format "3.6" with standard journal reiserfs: checking transaction log (device ide0(3,7)) ... for (ide0(3,7)) reiserfs: replayed 2 transactions in 0 seconds ide0(3,7):Using r5 hash to sort names 3c59x: Donald Becker and others. www.scyld.com/network/vortex.html Unable to handle kernel NULL pointer dereference at virtual address 0000002c printing eip: c015363f *pde = 00000000 Oops: 0000 CPU: 0 EIP: 0010:[] Not tainted EFLAGS: 00010246 eax: 00000000 ebx: f65ac480 ecx: f31a4000 edx: 00000000 esi: f31a5d74 edi: fffffffb ebp: 00000000 esp: f31a5c70 ds: 0018 es: 0018 ss: 0018 Process id (pid: 4094, stackpage=f31a5000) Stack: c0108ba4 f31a5c7c 00000002 00000000 0000023c 00000000 00000000 00000000 00000005 00000802 00000000 00000000 00000000 00000000 f65ac480 0804c88c 00000000 f66af970 00000000 c0153d50 f31a5d74 f66af970 f31a5d3c f773eb40 Call Trace: [] [] [] [] [] [] [] [] [] Code: 8b 48 2c 8d 41 1c ba 01 00 ff ff 0f c1 10 85 d2 0f 85 72 1c <1>Unable to handle kernel paging request at virtual address 010000d4 printing eip: c0128884 *pde = 00000000 Oops: 0000 CPU: 0 EIP: 0010:[] Not tainted EFLAGS: 00010206 eax: 010000cc ebx: 08048000 ecx: 00000080 edx: f76a9134 esi: 00000080 edi: f7dab5c0 ebp: 0000009d esp: f730fe5c ds: 0018 es: 0018 ss: 0018 Process bash (pid: 4085, stackpage=f730f000) Stack: c0129cbc f76a9134 00000080 f7dab5c0 0000009d f76a9080 f76a9134 f66af270 f773c4f0 f773e360 00000000 f773e360 c0125e73 f773c4f0 080c8000 00000000 f7311320 00000000 bffff5c8 bffff570 00000000 c01080ba 00000001 f773e360 Call Trace: [] [] [] [] [] [] [] [] [] [] [] Code: 39 50 08 74 07 8b 40 10 eb f2 89 f6 39 48 0c 75 f4 ff 40 14 <6>hub.c: new USB device 00:10.4-7, assigned address 2 usb.c: USB device 2 (vend/prod 0xea0/0x2168) is not claimed by any active driver. Vendor: TinyDisk Model: 2004-07-30 Rev: 2.00 Type: Direct-Access ANSI SCSI revision: 02 Attached scsi removable disk sda at scsi0, channel 0, id 0, lun 0 Current 00:00: sns = 70 6 ASC=28 ASCQ= 0 Raw sense data:0x70 0x00 0x06 0x00 0x00 0x00 0x00 0x0a 0x00 0x00 0x00 0x00 0x28 0x00 0x00 0x00 0x00 0x00 SCSI device sda: 256000 512-byte hdwr sectors (131 MB) sda: Write Protect is off