LinuxSir.cn,穿越时空的Linuxsir!

 找回密码
 注册
搜索
热搜: shell linux mysql
查看: 1126|回复: 1

求解“注销、关机时鼠标不动,黑屏,接下来死机”

[复制链接]
发表于 2007-7-7 17:17:15 | 显示全部楼层 |阅读模式
刚刚解决slackware11启动问题,现在又出现死机问题,请大家帮忙,谢谢!

syslog日志及dmesg命令如下:

一、syslog日志

Jul  7 17:03:37 localhost kernel: mtrr: no more MTRRs available
Jul  7 17:05:08 localhost kernel: Linux version 2.4.33.3 (root@tree) (gcc version 3.4.6) #1 Fri Sep 1 01:48:52 CDT 2006
Jul  7 17:05:08 localhost kernel:  BIOS-e820: 0000000000000000 - 000000000009f000 (usable)
Jul  7 17:05:08 localhost kernel:  BIOS-e820: 000000000009f000 - 00000000000a0000 (reserved)
Jul  7 17:05:08 localhost kernel:  BIOS-e820: 00000000000d2000 - 00000000000d4000 (reserved)
Jul  7 17:05:08 localhost kernel:  BIOS-e820: 00000000000dc000 - 0000000000100000 (reserved)
Jul  7 17:05:08 localhost kernel:  BIOS-e820: 0000000000100000 - 000000001ff60000 (usable)
Jul  7 17:05:08 localhost kernel:  BIOS-e820: 000000001ff60000 - 000000001ff77000 (ACPI data)
Jul  7 17:05:08 localhost kernel:  BIOS-e820: 000000001ff77000 - 000000001ff79000 (ACPI NVS)
Jul  7 17:05:08 localhost kernel:  BIOS-e820: 000000001ff80000 - 0000000020000000 (reserved)
Jul  7 17:05:08 localhost kernel:  BIOS-e820: 00000000ff800000 - 0000000100000000 (reserved)
Jul  7 17:05:08 localhost kernel: On node 0 totalpages: 130912
Jul  7 17:05:08 localhost kernel: zone(0): 4096 pages.
Jul  7 17:05:08 localhost kernel: zone(1): 126816 pages.
Jul  7 17:05:08 localhost kernel: zone(2): 0 pages.
Jul  7 17:05:08 localhost kernel: Kernel command line: BOOT_IMAGE=2.4.33 ro root=301
Jul  7 17:05:08 localhost kernel: Detected 1495.187 MHz processor.
Jul  7 17:05:08 localhost kernel: Console: colour dummy device 80x25
Jul  7 17:05:08 localhost kernel: Calibrating delay loop... 2981.88 BogoMIPS
Jul  7 17:05:08 localhost kernel: Page-cache hash table entries: 131072 (order: 7, 524288 bytes)
Jul  7 17:05:08 localhost kernel: CPU: Intel(R) Pentium(R) M processor 1500MHz stepping 05
Jul  7 17:05:08 localhost kernel: POSIX conformance testing by UNIFIX
Jul  7 17:05:08 localhost kernel: mtrr: v1.40 (20010327) Richard Gooch (rgooch@atnf.csiro.au)
Jul  7 17:05:08 localhost kernel: mtrr: detected mtrr type: Intel
Jul  7 17:05:08 localhost kernel: PCI: Probing PCI hardware (bus 00)
Jul  7 17:05:08 localhost kernel: Transparent bridge - Intel Corp. 82801BAM/CAM PCI Bridge
Jul  7 17:05:08 localhost kernel: Initializing RT netlink socket
Jul  7 17:05:08 localhost kernel: Starting kswapd
Jul  7 17:05:08 localhost kernel: Console: switching to colour frame buffer device 128x48
Jul  7 17:05:08 localhost kernel: pty: 512 Unix98 ptys configured
Jul  7 17:05:08 localhost kernel: RAMDISK driver initialized: 16 RAM disks of 7777K size 1024 blocksize
Jul  7 17:05:08 localhost kernel: PCI: Enabling device 00:1f.1 (0005 -> 0007)
Jul  7 17:05:08 localhost kernel: hda: SAMSUNG HM080HC, ATA DISK drive
Jul  7 17:05:08 localhost kernel: hdc: HL-DT-STCD-RW/DVD DRIVE GCC-4242N, ATAPI CD/DVD-ROM drive
Jul  7 17:05:08 localhost kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Jul  7 17:05:08 localhost kernel: ide1 at 0x170-0x177,0x376 on irq 15
Jul  7 17:05:08 localhost kernel: hda: attached ide-disk driver.
Jul  7 17:05:08 localhost kernel: hda: host protected area => 1
Jul  7 17:05:08 localhost kernel: hdc: attached ide-cdrom driver.
Jul  7 17:05:08 localhost kernel: kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter, errno = 2
Jul  7 17:05:08 localhost last message repeated 2 times
Jul  7 17:05:08 localhost kernel:    8regs     :  2767.200 MB/sec
Jul  7 17:05:08 localhost kernel:    32regs    :  1710.400 MB/sec
Jul  7 17:05:08 localhost kernel:    pIII_sse  :  3852.800 MB/sec
Jul  7 17:05:08 localhost kernel:    pII_mmx   :  4076.000 MB/sec
Jul  7 17:05:08 localhost kernel:    p5_mmx    :  4076.000 MB/sec
Jul  7 17:05:08 localhost kernel: raid5: using function: pIII_sse (3852.800 MB/sec)
Jul  7 17:05:08 localhost kernel: VFS: Mounted root (ext3 filesystem) readonly.
Jul  7 17:05:16 localhost kernel: shpchp: shpc_init : shpc_cap_offset == 0
Jul  7 17:05:16 localhost kernel: shpchp: shpc_init : shpc_cap_offset == 0
Jul  7 17:05:16 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device
Jul  7 17:05:16 localhost insmod: /lib/modules/2.4.33.3/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
Jul  7 17:05:16 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed
Jul  7 17:05:16 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device
Jul  7 17:05:16 localhost insmod: /lib/modules/2.4.33.3/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
Jul  7 17:05:16 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed
Jul  7 17:05:16 localhost kernel: shpchp: shpc_init : shpc_cap_offset == 0
Jul  7 17:05:16 localhost kernel: shpchp: shpc_init : shpc_cap_offset == 0
Jul  7 17:05:16 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device
Jul  7 17:05:16 localhost insmod: /lib/modules/2.4.33.3/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
Jul  7 17:05:16 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed
Jul  7 17:05:16 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device
Jul  7 17:05:16 localhost insmod: /lib/modules/2.4.33.3/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
Jul  7 17:05:16 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed
Jul  7 17:05:16 localhost kernel: shpchp: shpc_init : shpc_cap_offset == 0
Jul  7 17:05:16 localhost kernel: shpchp: shpc_init : shpc_cap_offset == 0
Jul  7 17:05:16 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device
Jul  7 17:05:16 localhost insmod: /lib/modules/2.4.33.3/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
Jul  7 17:05:16 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed
Jul  7 17:05:17 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device
Jul  7 17:05:17 localhost insmod: /lib/modules/2.4.33.3/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
Jul  7 17:05:17 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed
Jul  7 17:05:17 localhost kernel: shpchp: shpc_init : shpc_cap_offset == 0
Jul  7 17:05:17 localhost kernel: shpchp: shpc_init : shpc_cap_offset == 0
Jul  7 17:05:17 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device
Jul  7 17:05:17 localhost insmod: /lib/modules/2.4.33.3/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
Jul  7 17:05:17 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed
Jul  7 17:05:17 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device
Jul  7 17:05:17 localhost insmod: /lib/modules/2.4.33.3/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
Jul  7 17:05:17 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed
Jul  7 17:05:17 localhost kernel: shpchp: shpc_init : shpc_cap_offset == 0
Jul  7 17:05:17 localhost kernel: shpchp: shpc_init : shpc_cap_offset == 0
Jul  7 17:05:17 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device
Jul  7 17:05:17 localhost insmod: /lib/modules/2.4.33.3/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
Jul  7 17:05:17 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed
Jul  7 17:05:17 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device
Jul  7 17:05:17 localhost insmod: /lib/modules/2.4.33.3/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
Jul  7 17:05:17 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed
Jul  7 17:05:17 localhost kernel: shpchp: shpc_init : shpc_cap_offset == 0
Jul  7 17:05:17 localhost kernel: shpchp: shpc_init : shpc_cap_offset == 0
Jul  7 17:05:17 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device
Jul  7 17:05:17 localhost insmod: /lib/modules/2.4.33.3/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
Jul  7 17:05:17 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed
Jul  7 17:05:17 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device
Jul  7 17:05:17 localhost insmod: /lib/modules/2.4.33.3/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
Jul  7 17:05:17 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed
Jul  7 17:05:17 localhost kernel: usb.c: USB device 2 (vend/prod 0x4b3/0x3107) is not claimed by any active driver.
Jul  7 17:05:17 localhost kernel: shpchp: shpc_init : shpc_cap_offset == 0
Jul  7 17:05:17 localhost kernel: shpchp: shpc_init : shpc_cap_offset == 0
Jul  7 17:05:17 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device
Jul  7 17:05:17 localhost insmod: /lib/modules/2.4.33.3/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
Jul  7 17:05:17 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed
Jul  7 17:05:17 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device
Jul  7 17:05:17 localhost insmod: /lib/modules/2.4.33.3/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
Jul  7 17:05:17 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed
Jul  7 17:05:17 localhost kernel: shpchp: shpc_init : shpc_cap_offset == 0
Jul  7 17:05:17 localhost kernel: shpchp: shpc_init : shpc_cap_offset == 0
Jul  7 17:05:17 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device
Jul  7 17:05:17 localhost insmod: /lib/modules/2.4.33.3/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
Jul  7 17:05:17 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed
Jul  7 17:05:17 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device
Jul  7 17:05:17 localhost insmod: /lib/modules/2.4.33.3/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
Jul  7 17:05:17 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed
Jul  7 17:05:18 localhost kernel: shpchp: shpc_init : shpc_cap_offset == 0
Jul  7 17:05:18 localhost kernel: shpchp: shpc_init : shpc_cap_offset == 0
Jul  7 17:05:18 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device
Jul  7 17:05:18 localhost insmod: /lib/modules/2.4.33.3/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
Jul  7 17:05:18 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed
Jul  7 17:05:18 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device
Jul  7 17:05:18 localhost insmod: /lib/modules/2.4.33.3/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
Jul  7 17:05:18 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed
Jul  7 17:05:18 localhost kernel: shpchp: shpc_init : shpc_cap_offset == 0
Jul  7 17:05:18 localhost kernel: shpchp: shpc_init : shpc_cap_offset == 0
Jul  7 17:05:18 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device
Jul  7 17:05:18 localhost insmod: /lib/modules/2.4.33.3/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
Jul  7 17:05:18 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed
Jul  7 17:05:18 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device
Jul  7 17:05:18 localhost insmod: /lib/modules/2.4.33.3/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
Jul  7 17:05:18 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed
Jul  7 17:05:18 localhost kernel: shpchp: shpc_init : shpc_cap_offset == 0
Jul  7 17:05:18 localhost kernel: shpchp: shpc_init : shpc_cap_offset == 0
Jul  7 17:05:18 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device
Jul  7 17:05:18 localhost insmod: /lib/modules/2.4.33.3/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
Jul  7 17:05:18 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed
Jul  7 17:05:18 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device
Jul  7 17:05:18 localhost insmod: /lib/modules/2.4.33.3/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
Jul  7 17:05:18 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed
Jul  7 17:05:18 localhost kernel: shpchp: shpc_init : shpc_cap_offset == 0
Jul  7 17:05:18 localhost kernel: shpchp: shpc_init : shpc_cap_offset == 0
Jul  7 17:05:18 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device
Jul  7 17:05:18 localhost insmod: /lib/modules/2.4.33.3/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
Jul  7 17:05:18 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed
Jul  7 17:05:18 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device
Jul  7 17:05:18 localhost insmod: /lib/modules/2.4.33.3/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
Jul  7 17:05:18 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed
Jul  7 17:05:18 localhost kernel: shpchp: shpc_init : shpc_cap_offset == 0
Jul  7 17:05:18 localhost kernel: shpchp: shpc_init : shpc_cap_offset == 0
Jul  7 17:05:18 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device
Jul  7 17:05:18 localhost insmod: /lib/modules/2.4.33.3/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
Jul  7 17:05:18 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed
Jul  7 17:05:18 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device
Jul  7 17:05:18 localhost insmod: /lib/modules/2.4.33.3/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
Jul  7 17:05:18 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed
Jul  7 17:05:18 localhost kernel: shpchp: shpc_init : shpc_cap_offset == 0
Jul  7 17:05:18 localhost kernel: shpchp: shpc_init : shpc_cap_offset == 0
Jul  7 17:05:18 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device
Jul  7 17:05:18 localhost insmod: /lib/modules/2.4.33.3/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
Jul  7 17:05:18 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed
Jul  7 17:05:19 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device
Jul  7 17:05:19 localhost insmod: /lib/modules/2.4.33.3/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
Jul  7 17:05:19 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed
Jul  7 17:05:19 localhost kernel: shpchp: shpc_init : shpc_cap_offset == 0
Jul  7 17:05:19 localhost kernel: shpchp: shpc_init : shpc_cap_offset == 0
Jul  7 17:05:19 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device
Jul  7 17:05:19 localhost insmod: /lib/modules/2.4.33.3/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
Jul  7 17:05:19 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed
Jul  7 17:05:19 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device
Jul  7 17:05:19 localhost insmod: /lib/modules/2.4.33.3/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
Jul  7 17:05:19 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed
Jul  7 17:05:19 localhost kernel: shpchp: shpc_init : shpc_cap_offset == 0
Jul  7 17:05:19 localhost kernel: shpchp: shpc_init : shpc_cap_offset == 0
Jul  7 17:05:19 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device
Jul  7 17:05:19 localhost insmod: /lib/modules/2.4.33.3/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
Jul  7 17:05:19 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed
Jul  7 17:05:19 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device
Jul  7 17:05:19 localhost insmod: /lib/modules/2.4.33.3/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
Jul  7 17:05:19 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed
Jul  7 17:05:22 localhost kernel: shpchp: shpc_init : shpc_cap_offset == 0
Jul  7 17:05:22 localhost kernel: shpchp: shpc_init : shpc_cap_offset == 0
Jul  7 17:05:22 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device
Jul  7 17:05:22 localhost insmod: /lib/modules/2.4.33.3/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
Jul  7 17:05:22 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed
Jul  7 17:05:22 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device
Jul  7 17:05:22 localhost insmod: /lib/modules/2.4.33.3/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
Jul  7 17:05:22 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed
Jul  7 17:05:22 localhost kernel: shpchp: shpc_init : shpc_cap_offset == 0
Jul  7 17:05:22 localhost kernel: shpchp: shpc_init : shpc_cap_offset == 0
Jul  7 17:05:22 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device
Jul  7 17:05:22 localhost insmod: /lib/modules/2.4.33.3/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
Jul  7 17:05:22 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed
Jul  7 17:05:22 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device
Jul  7 17:05:22 localhost insmod: /lib/modules/2.4.33.3/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
Jul  7 17:05:22 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed
Jul  7 17:05:22 localhost kernel: shpchp: shpc_init : shpc_cap_offset == 0
Jul  7 17:05:22 localhost kernel: shpchp: shpc_init : shpc_cap_offset == 0
Jul  7 17:05:22 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device
Jul  7 17:05:22 localhost insmod: /lib/modules/2.4.33.3/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
Jul  7 17:05:22 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed
Jul  7 17:05:23 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device
Jul  7 17:05:23 localhost insmod: /lib/modules/2.4.33.3/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
Jul  7 17:05:23 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed
Jul  7 17:05:23 localhost kernel: shpchp: shpc_init : shpc_cap_offset == 0
Jul  7 17:05:23 localhost kernel: shpchp: shpc_init : shpc_cap_offset == 0
Jul  7 17:05:23 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device
Jul  7 17:05:23 localhost insmod: /lib/modules/2.4.33.3/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
Jul  7 17:05:23 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed
Jul  7 17:05:23 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device
Jul  7 17:05:23 localhost insmod: /lib/modules/2.4.33.3/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
Jul  7 17:05:23 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed
Jul  7 17:05:23 localhost kernel: shpchp: shpc_init : shpc_cap_offset == 0
Jul  7 17:05:23 localhost kernel: shpchp: shpc_init : shpc_cap_offset == 0
Jul  7 17:05:23 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device
Jul  7 17:05:23 localhost insmod: /lib/modules/2.4.33.3/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
Jul  7 17:05:23 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed
Jul  7 17:05:23 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device
Jul  7 17:05:23 localhost insmod: /lib/modules/2.4.33.3/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
Jul  7 17:05:23 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed
Jul  7 17:05:23 localhost kernel: shpchp: shpc_init : shpc_cap_offset == 0
Jul  7 17:05:23 localhost kernel: shpchp: shpc_init : shpc_cap_offset == 0
Jul  7 17:05:23 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device
Jul  7 17:05:23 localhost insmod: /lib/modules/2.4.33.3/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
Jul  7 17:05:23 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed
Jul  7 17:05:23 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device
Jul  7 17:05:23 localhost insmod: /lib/modules/2.4.33.3/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
Jul  7 17:05:23 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed
Jul  7 17:05:23 localhost kernel: shpchp: shpc_init : shpc_cap_offset == 0
Jul  7 17:05:23 localhost kernel: shpchp: shpc_init : shpc_cap_offset == 0
Jul  7 17:05:23 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device
Jul  7 17:05:23 localhost insmod: /lib/modules/2.4.33.3/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
Jul  7 17:05:23 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed
Jul  7 17:05:23 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device
Jul  7 17:05:23 localhost insmod: /lib/modules/2.4.33.3/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
Jul  7 17:05:23 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed
Jul  7 17:05:23 localhost kernel: shpchp: shpc_init : shpc_cap_offset == 0
Jul  7 17:05:23 localhost kernel: shpchp: shpc_init : shpc_cap_offset == 0
Jul  7 17:05:23 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device
Jul  7 17:05:23 localhost insmod: /lib/modules/2.4.33.3/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
Jul  7 17:05:23 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed
Jul  7 17:05:23 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device
Jul  7 17:05:23 localhost insmod: /lib/modules/2.4.33.3/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
Jul  7 17:05:23 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed
Jul  7 17:05:24 localhost kernel: shpchp: shpc_init : shpc_cap_offset == 0
Jul  7 17:05:24 localhost kernel: shpchp: shpc_init : shpc_cap_offset == 0
Jul  7 17:05:24 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device
Jul  7 17:05:24 localhost insmod: /lib/modules/2.4.33.3/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
Jul  7 17:05:24 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed
Jul  7 17:05:24 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device
Jul  7 17:05:24 localhost insmod: /lib/modules/2.4.33.3/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
Jul  7 17:05:24 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed
Jul  7 17:05:24 localhost kernel: shpchp: shpc_init : shpc_cap_offset == 0
Jul  7 17:05:24 localhost kernel: shpchp: shpc_init : shpc_cap_offset == 0
Jul  7 17:05:24 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device
Jul  7 17:05:24 localhost insmod: /lib/modules/2.4.33.3/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
Jul  7 17:05:24 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed
Jul  7 17:05:24 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device
Jul  7 17:05:24 localhost insmod: /lib/modules/2.4.33.3/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
Jul  7 17:05:24 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed
Jul  7 17:05:24 localhost kernel: shpchp: shpc_init : shpc_cap_offset == 0
Jul  7 17:05:24 localhost kernel: shpchp: shpc_init : shpc_cap_offset == 0
Jul  7 17:05:24 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device
Jul  7 17:05:24 localhost insmod: /lib/modules/2.4.33.3/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
Jul  7 17:05:24 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed
Jul  7 17:05:24 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device
Jul  7 17:05:24 localhost insmod: /lib/modules/2.4.33.3/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
Jul  7 17:05:24 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed
Jul  7 17:05:24 localhost kernel: shpchp: shpc_init : shpc_cap_offset == 0
Jul  7 17:05:24 localhost kernel: shpchp: shpc_init : shpc_cap_offset == 0
Jul  7 17:05:24 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device
Jul  7 17:05:24 localhost insmod: /lib/modules/2.4.33.3/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
Jul  7 17:05:24 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed
Jul  7 17:05:24 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device
Jul  7 17:05:24 localhost insmod: /lib/modules/2.4.33.3/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
Jul  7 17:05:24 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed
Jul  7 17:05:24 localhost kernel: shpchp: shpc_init : shpc_cap_offset == 0
Jul  7 17:05:24 localhost kernel: shpchp: shpc_init : shpc_cap_offset == 0
Jul  7 17:05:24 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device
Jul  7 17:05:24 localhost insmod: /lib/modules/2.4.33.3/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
Jul  7 17:05:24 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed
Jul  7 17:05:24 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device
Jul  7 17:05:24 localhost insmod: /lib/modules/2.4.33.3/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
Jul  7 17:05:24 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed
Jul  7 17:05:24 localhost kernel: shpchp: shpc_init : shpc_cap_offset == 0
Jul  7 17:05:24 localhost kernel: shpchp: shpc_init : shpc_cap_offset == 0
Jul  7 17:05:24 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device
Jul  7 17:05:24 localhost insmod: /lib/modules/2.4.33.3/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
Jul  7 17:05:24 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed
Jul  7 17:05:25 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device
Jul  7 17:05:25 localhost insmod: /lib/modules/2.4.33.3/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
Jul  7 17:05:25 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed
Jul  7 17:05:25 localhost kernel: shpchp: shpc_init : shpc_cap_offset == 0
Jul  7 17:05:25 localhost kernel: shpchp: shpc_init : shpc_cap_offset == 0
Jul  7 17:05:25 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device
Jul  7 17:05:25 localhost insmod: /lib/modules/2.4.33.3/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
Jul  7 17:05:25 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed
Jul  7 17:05:25 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device
Jul  7 17:05:25 localhost insmod: /lib/modules/2.4.33.3/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
Jul  7 17:05:25 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed
Jul  7 17:05:25 localhost kernel: shpchp: shpc_init : shpc_cap_offset == 0
Jul  7 17:05:25 localhost kernel: shpchp: shpc_init : shpc_cap_offset == 0
Jul  7 17:05:25 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device
Jul  7 17:05:25 localhost insmod: /lib/modules/2.4.33.3/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
Jul  7 17:05:25 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed
Jul  7 17:05:25 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device
Jul  7 17:05:25 localhost insmod: /lib/modules/2.4.33.3/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
Jul  7 17:05:25 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed
Jul  7 17:05:25 localhost kernel: shpchp: shpc_init : shpc_cap_offset == 0
Jul  7 17:05:25 localhost kernel: shpchp: shpc_init : shpc_cap_offset == 0
Jul  7 17:05:25 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device
Jul  7 17:05:25 localhost insmod: /lib/modules/2.4.33.3/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
Jul  7 17:05:25 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed
Jul  7 17:05:25 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device
Jul  7 17:05:25 localhost insmod: /lib/modules/2.4.33.3/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
Jul  7 17:05:25 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed
Jul  7 17:05:25 localhost kernel: shpchp: shpc_init : shpc_cap_offset == 0
Jul  7 17:05:25 localhost kernel: shpchp: shpc_init : shpc_cap_offset == 0
Jul  7 17:05:25 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device
Jul  7 17:05:25 localhost insmod: /lib/modules/2.4.33.3/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
Jul  7 17:05:25 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed
Jul  7 17:05:25 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device
Jul  7 17:05:25 localhost insmod: /lib/modules/2.4.33.3/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
Jul  7 17:05:25 localhost insmod: /lib/modules/2.4.33.3/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed
Jul  7 17:05:50 localhost dnsmasq: failed to create listening socket: Address already in use
Jul  7 17:05:50 localhost dnsmasq: FAILED to start up

二、dmesg命令

s: INFO: recovery required on readonly filesystem.
EXT3-fs: write access will be enabled during recovery.
kjournald starting.  Commit interval 5 seconds
EXT3-fs: ide0(3,1): orphan cleanup on readonly fs
ext3_orphan_cleanup: deleting unreferenced inode 2121742
ext3_orphan_cleanup: deleting unreferenced inode 2121732
ext3_orphan_cleanup: deleting unreferenced inode 2121046
ext3_orphan_cleanup: deleting unreferenced inode 1047664
ext3_orphan_cleanup: deleting unreferenced inode 1047663
ext3_orphan_cleanup: deleting unreferenced inode 1047662
ext3_orphan_cleanup: deleting unreferenced inode 1047661
ext3_orphan_cleanup: deleting unreferenced inode 1047660
ext3_orphan_cleanup: deleting unreferenced inode 1047658
ext3_orphan_cleanup: deleting unreferenced inode 1992517
ext3_orphan_cleanup: deleting unreferenced inode 1992516
EXT3-fs: ide0(3,1): 11 orphan inodes deleted
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
Freeing unused kernel memory: 124k freed
Adding Swap: 997880k swap-space (priority -1)
EXT3 FS 2.4-0.9.19, 19 August 2002 on ide0(3,1), internal journal
Linux agpgart interface v0.99 (c) Jeff Hartmann
agpgart: Maximum main memory to use for agp memory: 439M
agpgart: Detected Intel(R) 855PM chipset
agpgart: AGP aperture is 256M @ 0xd0000000
scsi0 : SCSI host adapter emulation for IDE ATAPI devices
Linux Kernel Card Services 3.1.22
  options:  [pci] [cardbus] [pm]
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
Intel ISA PCIC probe: not found.
Databook TCIC-2 PCMCIA probe: not found.
PCI: Found IRQ 11 for device 02:00.0
PCI: Sharing IRQ 11 with 00:1d.0
PCI: Sharing IRQ 11 with 01:00.0
PCI: Sharing IRQ 11 with 02:01.0
PCI: Found IRQ 11 for device 02:00.1
PCI: Sharing IRQ 11 with 00:1f.3
PCI: Sharing IRQ 11 with 00:1f.5
PCI: Sharing IRQ 11 with 00:1f.6
Yenta ISA IRQ mask 0x06b8, PCI irq 11
Socket status: 30000086
Yenta ISA IRQ mask 0x06b8, PCI irq 11
Socket status: 30000086
cs: IO port probe 0x0c00-0x0cff: clean.
cs: IO port probe 0x0820-0x08ff: clean.
cs: IO port probe 0x0800-0x080f: clean.
cs: IO port probe 0x03e0-0x04ff: excluding 0x4d0-0x4d7
cs: IO port probe 0x0100-0x03af: clean.
cs: IO port probe 0x0a00-0x0aff: clean.
Intel(R) PRO/1000 Network Driver - version 5.7.6-k1
Copyright (c) 1999-2004 Intel Corporation.
PCI: Found IRQ 11 for device 02:01.0
PCI: Sharing IRQ 11 with 00:1d.0
PCI: Sharing IRQ 11 with 01:00.0
PCI: Sharing IRQ 11 with 02:00.0
e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection
PCI: Found IRQ 11 for device 00:1f.5
PCI: Sharing IRQ 11 with 00:1f.3
PCI: Sharing IRQ 11 with 00:1f.6
PCI: Sharing IRQ 11 with 02:00.1
PCI: Setting latency timer of device 00:1f.5 to 64
intel8x0_measure_ac97_clock: measured 59491 usecs
intel8x0: clocking to 48000
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
pciehp: PCI Express Hot Plug Controller Driver version: 0.5
i810_rng hardware driver 0.9.8 loaded
usb.c: registered new driver usbdevfs
usb.c: registered new driver hub
PCI: Found IRQ 11 for device 00:1d.7
PCI: Setting latency timer of device 00:1d.7 to 64
ehci_hcd 00:1d.7: Intel Corp. 82801DB USB2
ehci_hcd 00:1d.7: irq 11, pci mem e0b09000
usb.c: new USB bus registered, assigned bus number 1
ehci_hcd 00:1d.7: enabled 64bit PCI DMA
PCI: cache line size of 32 is not supported by device 00:1d.7
ehci_hcd 00:1d.7: USB 2.0 enabled, EHCI 1.00, driver 2003-Dec-29/2.4
hub.c: USB hub found
hub.c: 6 ports detected
uhci.c: USB Universal Host Controller Interface driver v1.1
PCI: Found IRQ 11 for device 00:1d.0
PCI: Sharing IRQ 11 with 01:00.0
PCI: Sharing IRQ 11 with 02:00.0
PCI: Sharing IRQ 11 with 02:01.0
PCI: Setting latency timer of device 00:1d.0 to 64
uhci.c: USB UHCI at I/O 0x1800, IRQ 11
usb.c: new USB bus registered, assigned bus number 2
hub.c: USB hub found
hub.c: 2 ports detected
PCI: Found IRQ 11 for device 00:1d.1
PCI: Setting latency timer of device 00:1d.1 to 64
uhci.c: USB UHCI at I/O 0x1820, IRQ 11
usb.c: new USB bus registered, assigned bus number 3
hub.c: USB hub found
hub.c: 2 ports detected
PCI: Found IRQ 11 for device 00:1d.2
PCI: Sharing IRQ 11 with 00:1f.1
PCI: Sharing IRQ 11 with 02:02.0
PCI: Setting latency timer of device 00:1d.2 to 64
uhci.c: USB UHCI at I/O 0x1840, IRQ 11
usb.c: new USB bus registered, assigned bus number 4
hub.c: USB hub found
hub.c: 2 ports detected
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
pciehp: PCI Express Hot Plug Controller Driver version: 0.5
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
pciehp: PCI Express Hot Plug Controller Driver version: 0.5
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
pciehp: PCI Express Hot Plug Controller Driver version: 0.5
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
pciehp: PCI Express Hot Plug Controller Driver version: 0.5
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
hub.c: new USB device 00:1d.1-1, assigned address 2
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
pciehp: PCI Express Hot Plug Controller Driver version: 0.5
usb.c: USB device 2 (vend/prod 0x4b3/0x3107) is not claimed by any active driver.
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
pciehp: PCI Express Hot Plug Controller Driver version: 0.5
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
pciehp: PCI Express Hot Plug Controller Driver version: 0.5
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
pciehp: PCI Express Hot Plug Controller Driver version: 0.5
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
pciehp: PCI Express Hot Plug Controller Driver version: 0.5
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
pciehp: PCI Express Hot Plug Controller Driver version: 0.5
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
pciehp: PCI Express Hot Plug Controller Driver version: 0.5
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
pciehp: PCI Express Hot Plug Controller Driver version: 0.5
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
pciehp: PCI Express Hot Plug Controller Driver version: 0.5
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
pciehp: PCI Express Hot Plug Controller Driver version: 0.5
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
pciehp: PCI Express Hot Plug Controller Driver version: 0.5
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
usb.c: registered new driver usbmouse
input0: USB HIDBP Mouse 04b3:3107 on usb3:2.0
usbmouse.c: v1.6:USB HID Boot Protocol mouse driver
usb.c: registered new driver hiddev
usb.c: registered new driver hid
hid-core.c: v1.8.1 Andreas Gal, Vojtech Pavlik <vojtech@suse.cz>
hid-core.c: USB HID support drivers
mice: PS/2 mouse device common for all mice
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
pciehp: PCI Express Hot Plug Controller Driver version: 0.5
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
pciehp: PCI Express Hot Plug Controller Driver version: 0.5
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
pciehp: PCI Express Hot Plug Controller Driver version: 0.5
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
pciehp: PCI Express Hot Plug Controller Driver version: 0.5
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
pciehp: PCI Express Hot Plug Controller Driver version: 0.5
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
pciehp: PCI Express Hot Plug Controller Driver version: 0.5
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
pciehp: PCI Express Hot Plug Controller Driver version: 0.5
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
pciehp: PCI Express Hot Plug Controller Driver version: 0.5
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
pciehp: PCI Express Hot Plug Controller Driver version: 0.5
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
pciehp: PCI Express Hot Plug Controller Driver version: 0.5
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
pciehp: PCI Express Hot Plug Controller Driver version: 0.5
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
pciehp: PCI Express Hot Plug Controller Driver version: 0.5
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
pciehp: PCI Express Hot Plug Controller Driver version: 0.5
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
pciehp: PCI Express Hot Plug Controller Driver version: 0.5
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
pciehp: PCI Express Hot Plug Controller Driver version: 0.5
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
pciehp: PCI Express Hot Plug Controller Driver version: 0.5
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
pciehp: PCI Express Hot Plug Controller Driver version: 0.5
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
pciehp: PCI Express Hot Plug Controller Driver version: 0.5
scsi singledevice 0 0 0 0
scsi singledevice 0 0 1 0
scsi singledevice 0 0 2 0
scsi singledevice 0 0 3 0
scsi singledevice 0 0 4 0
scsi singledevice 0 0 5 0
scsi singledevice 0 0 6 0
scsi singledevice 0 0 7 0
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
parport0: PC-style at 0x3bc [PCSPP,TRISTATE]
lp0: using parport0 (polling).
NET4: AppleTalk 0.18a for Linux NET4.0
mtrr: no more MTRRs available
mtrr: no more MTRRs available
mtrr: no more MTRRs available
 楼主| 发表于 2007-7-9 07:38:41 | 显示全部楼层
为什么没人帮我啊,我现在好痛苦,本本老是强制性关机!5555~~~~
回复 支持 反对

使用道具 举报

您需要登录后才可以回帖 登录 | 注册

本版积分规则

快速回复 返回顶部 返回列表