Strona 1 z 1

Jak zrobić aby port usb nie był odłączany co jakiś czas, tylko pracował cały czas?

: 23 czerwca 2011, 21:56
autor: dhapollo
Witam.

Mam problem tak jak autor tematu. Mianowicie zmieniłem kieszeń sieciową na dysk usb podpięty do serwera.
Dysk jest montowany przy starcie systemu i działa elegancko w sieci.
Problemem jest to, że co jakiś czas muszę wykonać restart serwera ponieważ jest odłączany port usb. Po restarcie systemu dalej jest ok przez jakiś czas.

Podejrzewam że to właśnie zarządzanie energią jest temu winne.

Kod: Zaznacz cały

root@pingwin:~# uname -a
Linux pingwin 2.6.32-5-686 #1 SMP Tue Mar 8 21:36:00 UTC 2011 i686 GNU/Linux

Kod: Zaznacz cały

root@pingwin:~# dpkg --print-architecture
i386

Kod: Zaznacz cały

root@pingwin:~# lspci -k
00:00.0 Host bridge: Intel Corporation Mobile 945GME Express Memory Controller Hub (rev 03)
        Subsystem: Acer Incorporated [ALI] Device 015b
        Kernel driver in use: agpgart-intel
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GME Express Integrated Graphics Controller (rev 03)
        Subsystem: Acer Incorporated [ALI] Device 015b
00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03)
        Subsystem: Acer Incorporated [ALI] Device 015b
00:1b.0 Audio device: Intel Corporation N10/ICH 7 Family High Definition Audio Controller (rev 02)
        Subsystem: Acer Incorporated [ALI] Device 015b
        Kernel driver in use: HDA Intel
00:1c.0 PCI bridge: Intel Corporation N10/ICH 7 Family PCI Express Port 1 (rev 02)
        Kernel driver in use: pcieport
00:1c.1 PCI bridge: Intel Corporation N10/ICH 7 Family PCI Express Port 2 (rev 02)
        Kernel driver in use: pcieport
00:1c.2 PCI bridge: Intel Corporation N10/ICH 7 Family PCI Express Port 3 (rev 02)
        Kernel driver in use: pcieport
00:1c.3 PCI bridge: Intel Corporation N10/ICH 7 Family PCI Express Port 4 (rev 02)
        Kernel driver in use: pcieport
00:1d.0 USB Controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller #1 (rev 02)
        Subsystem: Acer Incorporated [ALI] Device 015b
        Kernel driver in use: uhci_hcd
00:1d.1 USB Controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller #2 (rev 02)
        Subsystem: Acer Incorporated [ALI] Device 015b
        Kernel driver in use: uhci_hcd
00:1d.2 USB Controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller #3 (rev 02)
        Subsystem: Acer Incorporated [ALI] Device 015b
        Kernel driver in use: uhci_hcd
00:1d.3 USB Controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller #4 (rev 02)
        Subsystem: Acer Incorporated [ALI] Device 015b
        Kernel driver in use: uhci_hcd
00:1d.7 USB Controller: Intel Corporation N10/ICH 7 Family USB2 EHCI Controller (rev 02)
        Subsystem: Acer Incorporated [ALI] Device 015b
        Kernel driver in use: ehci_hcd
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2)
00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 02)
        Subsystem: Acer Incorporated [ALI] Device 015b
00:1f.2 IDE interface: Intel Corporation 82801GBM/GHM (ICH7 Family) SATA IDE Controller (rev 02)
        Subsystem: Acer Incorporated [ALI] Device 015b
        Kernel driver in use: ata_piix
00:1f.3 SMBus: Intel Corporation N10/ICH 7 Family SMBus Controller (rev 02)
        Subsystem: Acer Incorporated [ALI] Device 015b
        Kernel driver in use: i801_smbus
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 02)
        Subsystem: Acer Incorporated [ALI] Device 015b
        Kernel driver in use: r8169
03:00.0 Ethernet controller: Atheros Communications Inc. AR5001 Wireless Network Adapter (rev 01)
        Subsystem: Foxconn International, Inc. Device e008
        Kernel driver in use: ath5k
04:00.0 System peripheral: JMicron Technology Corp. SD/MMC Host Controller
        Subsystem: Acer Incorporated [ALI] Device 015b
        Kernel driver in use: sdhci-pci
04:00.2 SD Host controller: JMicron Technology Corp. Standard SD Host Controller
        Subsystem: Acer Incorporated [ALI] Device 015b
04:00.3 System peripheral: JMicron Technology Corp. MS Host Controller
        Subsystem: Acer Incorporated [ALI] Device 015b
        Kernel driver in use: jmb38x_ms
04:00.4 System peripheral: JMicron Technology Corp. xD Host Controller
        Subsystem: Acer Incorporated [ALI] Device 015b

Kod: Zaznacz cały

Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 064e:d101 Suyin Corp. Acer CrystalEye Webcam
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Jak zrobić aby port usb nie był odłączany co jakiś czas, tylko pracował cały czas?


Dodane:
W logach znalazłem:

Kod: Zaznacz cały

Jun 23 21:52:53 pingwin smbd[14924]:   angels (::ffff:192.168.1.19) closed connection to service netlogon
Jun 23 21:52:55 pingwin kernel: [181981.906337] EXT2-fs error (device sdb1): ext2_get_inode: unable to read inode block - inode=32769, block=655
Jun 23 21:52:55 pingwin kernel: [181981.906740] EXT2-fs error (device sdb1): ext2_get_inode: unable to read inode block - inode=16285697, block=
Jun 23 21:52:55 pingwin kernel: [181981.907108] EXT2-fs error (device sdb1): ext2_get_inode: unable to read inode block - inode=37322780, block=
Jun 23 21:52:55 pingwin kernel: [181981.907472] EXT2-fs error (device sdb1): ext2_get_inode: unable to read inode block - inode=6471681, block=1
Jun 23 21:52:55 pingwin kernel: [181981.907836] EXT2-fs error (device sdb1): ext2_get_inode: unable to read inode block - inode=131073, block=26
Jun 23 21:52:55 pingwin kernel: [181981.908209] EXT2-fs error (device sdb1): ext2_get_inode: unable to read inode block - inode=163841, block=32
Jun 23 21:52:55 pingwin kernel: [181981.908578] EXT2-fs error (device sdb1): ext2_get_inode: unable to read inode block - inode=39829505, block=
Jun 23 21:52:55 pingwin kernel: [181981.908939] EXT2-fs error (device sdb1): ext2_get_inode: unable to read inode block - inode=212993, block=42
Jun 23 21:52:55 pingwin kernel: [181981.909446] EXT2-fs error (device sdb1): ext2_get_inode: unable to read inode block - inode=11, block=1027
Jun 23 21:52:55 pingwin kernel: [181981.909986] EXT2-fs error (device sdb1): ext2_get_inode: unable to read inode block - inode=39862273, block=
Jun 23 21:52:55 pingwin kernel: [181981.910377] EXT2-fs error (device sdb1): ext2_get_inode: unable to read inode block - inode=5111809, block=1
Jun 23 21:52:55 pingwin kernel: [181981.910743] EXT2-fs error (device sdb1): ext2_get_inode: unable to read inode block - inode=37191681, block=
Jun 23 21:52:55 pingwin kernel: [181981.911107] EXT2-fs error (device sdb1): ext2_get_inode: unable to read inode block - inode=42582019, block=
Jun 23 21:52:55 pingwin kernel: [181981.911474] EXT2-fs error (device sdb1): ext2_get_inode: unable to read inode block - inode=12, block=1027
Jun 23 21:52:55 pingwin kernel: [181981.911836] EXT2-fs error (device sdb1): ext2_get_inode: unable to read inode block - inode=37175299, block=
Jun 23 21:52:55 pingwin kernel: [181981.912213] EXT2-fs error (device sdb1): ext2_get_inode: unable to read inode block - inode=17, block=1027
Jun 23 21:52:55 pingwin kernel: [181981.912591] EXT2-fs error (device sdb1): ext2_get_inode: unable to read inode block - inode=52215823, block=
Jun 23 21:52:55 pingwin kernel: [181981.912961] EXT2-fs error (device sdb1): ext2_get_inode: unable to read inode block - inode=52232207, block=
Jun 23 21:52:55 pingwin kernel: [181981.913492] EXT2-fs error (device sdb1): ext2_get_inode: unable to read inode block - inode=52264970, block=
Jun 23 21:52:55 pingwin kernel: [181981.914058] EXT2-fs error (device sdb1): ext2_get_inode: unable to read inode block - inode=12369930, block=
Jun 23 21:52:58 pingwin kernel: [181984.852699] EXT2-fs error (device sdb1): ext2_get_inode: unable to read inode block - inode=5111809, block=1

: 24 czerwca 2011, 12:40
autor: markossx
Kiedyś ktoś mi podpowiedział by rozwiązać to w cronie za pomocą:

Kod: Zaznacz cały

fdisk -l /dev/sdX >/dev/null 2>&1
Może jest jakiś inny sposób, chętnie wypróbuję :)

: 25 czerwca 2011, 17:28
autor: dhapollo
A co to polecenie robi?

: 25 czerwca 2011, 18:21
autor: markossx
A podręcznik systemowy? Ogólnie mówiąc pobudza /dev/sdX...

: 27 lipca 2011, 15:07
autor: dhapollo
Od dzisiaj zaczynam urlop, wrócę to zobaczę i powiem czy działa.

Dodane:
Niestety posiadam spore braki w podstawach, i nie mogę tego ogarnąć