Erros no dispositivo USB durante a inicialização?

4

Explicação

Eu acabei de criar um novo computador. Aqui estão as especificações:

Placa-mãe: Gigabyte 990FXA-UD3

CPU: AMD FX 8350

SSD: SAMSUNG 840 Pro Series MZ-7PD256BW

RAM: G.SKILL F3-1600C9Q-32GXM

Inicialmente eu tentei instalar o Linux Mint 15 com o XFCE de um Live DVD. O DVD ao vivo carregado, mas meu teclado e mouse não foram detectados ou montados, então não consegui instalá-lo. Depois de algum googling eu descobri que algumas das minhas configurações da BIOS provavelmente estavam causando o problema. Eu habilitei a pilha de rede e o controlador IOMMU (descrito aqui e aqui ) e, em seguida, os dispositivos usb começaram a funcionar e eu consegui instalar o Ubuntu 12.04.3 LTS. Mas eu realmente queria o Mint 15 com o XFCE, então eu instalei isso de novo e funcionou dessa vez! Mas então percebi que "não consegui" obter uma conexão de rede. Então eu reinstalei o Ubuntu novamente. Depois de instalar o Ubuntu, percebi que, por algum motivo, o DHCP automático não estava funcionando. Eu mudei para uma configuração manual, e depois de reiniciar o computador (não tenho certeza porque eu tive que reiniciar para obter a configuração para trabalhar) eu tinha conectividade de rede. Bem geez, eu ainda queria Mint, então eu reinstalei novamente!

Longa história curta - agora tenho o Mint 15 com o XFCE em funcionamento. Mas ainda não é perfeito. O tempo de inicialização leva uma eternidade e não há nenhuma indicação de que o computador está inicializando diferente da cor do LED no meu monitor. A tela está preta, sem qualquer informação gráfica indicando que o sistema operacional está carregando. Depois de esperar alguns minutos (eu não tenho cronometrado, mas acho que é cerca de 4 ou 5 minutos) finalmente recebo a tela de login. Mas quando tento usar o teclado ou mouse USB, eles ainda não funcionam. Eu sei que isso parece confuso porque eu disse que tudo está funcionando. Bem, o problema é que eu tenho que esperar em algum lugar entre 1 a 2 minutos antes que o teclado e o mouse funcionem. Eu posso viver com isso, mas parece que algo ainda não está funcionando direito.

Eu obtenho os mesmos resultados com o Mint 15 e o Ubuntu 12.04.3 LTS.

Assegurei que a placa-mãe tenha o BIOS mais recente instalado. Tentei atualizar os drivers para a LAN, Realtek 8111E (o site diz" driver LINUX para kernel 3.xe 2.6.xe 2.4.x "), mas quando descompartilho r8168-8.037.00. tar.bz2 o arquivo README declara "Árvore de fontes do Kernel (kernel Linux 2.6.xe 2.4.x) suportado" então eu não o instalei porque estou rodando:

$ uname -a
Linux bugger 3.8.0-25-generic #37-Ubuntu SMP Thu Jun 6 20:47:07 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

Aqui estão os snipets de / var / log / syslog. Acabei de incluir as partes pertinentes aos avisos ou erros relatados:

...
Oct 27 19:34:07 bugger kernel: [    1.531599] AMD-Vi: Event logged [IO_PAGE_FAULT device=01:00.0 domain=0x0014 address=0x00000000be9f9880 flags=0x0010]
Oct 27 19:34:07 bugger kernel: [    1.850302] usb 3-2: new high-speed USB device number 2 using ehci-pci
Oct 27 19:34:07 bugger kernel: [   16.912757] usb 3-2: device descriptor read/64, error -110
Oct 27 19:34:07 bugger kernel: [   18.217346] xhci_hcd 0000:01:00.0: can't setup
Oct 27 19:34:07 bugger kernel: [   18.217348] xhci_hcd 0000:01:00.0: USB bus 8 deregistered
Oct 27 19:34:07 bugger kernel: [   18.217375] Switching to clocksource tsc
Oct 27 19:34:07 bugger kernel: [   18.217377] xhci_hcd 0000:01:00.0: init 0000:01:00.0 fail, -110
Oct 27 19:34:07 bugger kernel: [   18.217379] xhci_hcd: probe of 0000:01:00.0 failed with error -110
...
Oct 27 19:34:07 bugger kernel: [   19.795759] [drm] Initialized nouveau 1.1.0 20120801 for 0000:03:00.0 on minor 0
Oct 27 19:34:07 bugger kernel: [   32.079049] usb 3-2: device descriptor read/64, error -110
Oct 27 19:34:07 bugger kernel: [   32.294288] usb 3-2: new high-speed USB device number 3 using ehci-pci
Oct 27 19:34:07 bugger kernel: [   47.356778] usb 3-2: device descriptor read/64, error -110
Oct 27 19:34:07 bugger kernel: [   62.522954] usb 3-2: device descriptor read/64, error -110
Oct 27 19:34:07 bugger kernel: [   62.738247] usb 3-2: new high-speed USB device number 4 using ehci-pci
Oct 27 19:34:07 bugger kernel: [   73.112154] usb 3-2: device not accepting address 4, error -110
Oct 27 19:34:07 bugger kernel: [   73.223791] usb 3-2: new high-speed USB device number 5 using ehci-pci
Oct 27 19:34:07 bugger kernel: [   83.597693] usb 3-2: device not accepting address 5, error -110
Oct 27 19:34:07 bugger kernel: [   83.597715] hub 3-0:1.0: unable to enumerate USB device on port 2
Oct 27 19:34:07 bugger kernel: [   83.733056] xor: automatically using best checksumming function:
Oct 27 19:34:07 bugger kernel: [   83.769049]    avx       :  5053.000 MB/sec
Oct 27 19:34:07 bugger kernel: [   83.770733] device-mapper: dm-raid45: initialized v0.2594b
Oct 27 19:34:07 bugger kernel: [   83.792131] Btrfs loaded
Oct 27 19:34:07 bugger kernel: [   83.813183] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
Oct 27 19:34:07 bugger kernel: [   83.872709] usb 5-3: new full-speed USB device number 2 using ohci_hcd
Oct 27 19:34:07 bugger kernel: [   83.938145] Adding 33516540k swap on /dev/sda5.  Priority:-1 extents:1 across:33516540k SS
Oct 27 19:34:07 bugger kernel: [   83.958737] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro
Oct 27 19:34:07 bugger kernel: [   83.983172] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Oct 27 19:34:07 bugger kernel: [   84.009284] lp: driver loaded but no devices found
Oct 27 19:34:07 bugger kernel: [   84.033058] usb 5-3: New USB device found, idVendor=0557, idProduct=7000
Oct 27 19:34:07 bugger kernel: [   84.033064] usb 5-3: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Oct 27 19:34:07 bugger kernel: [   84.035104] hub 5-3:1.0: USB hub found
Oct 27 19:34:07 bugger kernel: [   84.037248] hub 5-3:1.0: 4 ports detected
Oct 27 19:34:07 bugger bluetoothd[626]: Bluetooth daemon 4.101
Oct 27 19:34:07 bugger bluetoothd[626]: Starting SDP server
Oct 27 19:34:07 bugger bluetoothd[626]: DIS cannot start: GATT is disabled
Oct 27 19:34:07 bugger bluetoothd[626]: Failed to init deviceinfo plugin
Oct 27 19:34:07 bugger bluetoothd[626]: Failed to init proximity plugin
Oct 27 19:34:07 bugger bluetoothd[626]: Failed to init time plugin
Oct 27 19:34:07 bugger bluetoothd[626]: Failed to init alert plugin
Oct 27 19:34:07 bugger bluetoothd[626]: Failed to init thermometer plugin
Oct 27 19:34:07 bugger kernel: [   84.064980] Bluetooth: Core ver 2.16
Oct 27 19:34:07 bugger kernel: [   84.064995] NET: Registered protocol family 31
Oct 27 19:34:07 bugger kernel: [   84.064996] Bluetooth: HCI device and connection manager initialized
Oct 27 19:34:07 bugger kernel: [   84.065002] Bluetooth: HCI socket layer initialized
Oct 27 19:34:07 bugger kernel: [   84.065005] Bluetooth: L2CAP socket layer initialized
Oct 27 19:34:07 bugger kernel: [   84.065009] Bluetooth: SCO socket layer initialized
Oct 27 19:34:07 bugger bluetoothd[626]: Failed to init gatt_example plugin
...
Oct 27 19:34:07 bugger NetworkManager[979]: <info> monitoring kernel firmware directory '/lib/firmware'.
Oct 27 19:34:07 bugger NetworkManager[979]: <info> WiFi hardware radio set enabled
Oct 27 19:34:07 bugger NetworkManager[979]: <info> WiFi enabled by radio killswitch; enabled by state file
Oct 27 19:34:07 bugger NetworkManager[979]: <info> WWAN enabled by radio killswitch; enabled by state file
Oct 27 19:34:07 bugger NetworkManager[979]: <info> WiMAX enabled by radio killswitch; enabled by state file
Oct 27 19:34:07 bugger NetworkManager[979]: <info> Networking is enabled by state file
Oct 27 19:34:07 bugger NetworkManager[979]: <warn> failed to allocate link cache: (-10) Operation not supported
Oct 27 19:34:07 bugger NetworkManager[979]: <info> (eth0): carrier is OFF
Oct 27 19:34:07 bugger NetworkManager[979]: <info> (eth0): new Ethernet device (driver: 'r8169' ifindex: 2)
Oct 27 19:34:07 bugger NetworkManager[979]: <info> (eth0): exported as /org/freedesktop/NetworkManager/Devices/0
Oct 27 19:34:07 bugger NetworkManager[979]: <info> (eth0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Oct 27 19:34:07 bugger NetworkManager[979]: <info> (eth0): bringing up device.
Oct 27 19:34:07 bugger NetworkManager[979]: <info> monitoring kernel firmware directory '/lib/firmware'.
Oct 27 19:34:07 bugger NetworkManager[979]: <info> WiFi hardware radio set enabled
Oct 27 19:34:07 bugger NetworkManager[979]: <info> WiFi enabled by radio killswitch; enabled by state file
Oct 27 19:34:07 bugger NetworkManager[979]: <info> WWAN enabled by radio killswitch; enabled by state file
Oct 27 19:34:07 bugger NetworkManager[979]: <info> WiMAX enabled by radio killswitch; enabled by state file
Oct 27 19:34:07 bugger NetworkManager[979]: <info> Networking is enabled by state file
Oct 27 19:34:07 bugger NetworkManager[979]: <warn> failed to allocate link cache: (-10) Operation not supported
Oct 27 19:34:07 bugger NetworkManager[979]: <info> (eth0): carrier is OFF
Oct 27 19:34:07 bugger NetworkManager[979]: <info> (eth0): new Ethernet device (driver: 'r8169' ifindex: 2)
Oct 27 19:34:07 bugger NetworkManager[979]: <info> (eth0): exported as /org/freedesktop/NetworkManager/Devices/0
Oct 27 19:34:07 bugger NetworkManager[979]: <info> (eth0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Oct 27 19:34:07 bugger NetworkManager[979]: <info> (eth0): bringing up device.
...
Oct 27 19:34:08 bugger ntpdate[1265]: Can't find host ntp.ubuntu.com: System error (-11)
Oct 27 19:34:08 bugger ntpdate[1265]: no servers can be used, exiting
Oct 27 19:34:08 bugger mdm[1277]: WARNING: Plymouth is running, asking it to stop...
Oct 27 19:34:08 bugger mdm[1277]: WARNING: Plymouth stopped
Oct 27 19:34:08 bugger acpid: client connected from 1335[0:0]
Oct 27 19:34:08 bugger acpid: 1 client rule loaded
Oct 27 19:34:08 bugger kernel: [   84.925348] input: HDA NVidia HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:0b.0/0000:03:00.1/sound/card1/input10
Oct 27 19:34:08 bugger kernel: [   84.925422] input: HDA NVidia HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:0b.0/0000:03:00.1/sound/card1/input11
Oct 27 19:34:08 bugger kernel: [   84.925480] input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:0b.0/0000:03:00.1/sound/card1/input12
Oct 27 19:34:08 bugger kernel: [   84.925540] input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:0b.0/0000:03:00.1/sound/card1/input13
Oct 27 19:34:08 bugger mdm[1277]: WARNING: failed to get file info for accountService pic file: Error when getting information for file '/var/lib/AccountsService/icons/axiopisty': No such file or directory
Oct 27 19:34:08 bugger mdm[1277]: WARNING: failed to get file info for accountService pic file: Error when getting information for file '/home/axiopisty/.face': No such file or directory
Oct 27 19:34:08 bugger mdm[1277]: GLib-GIO-CRITICAL: g_file_info_get_attribute_uint64: assertion 'G_IS_FILE_INFO (info)' failed
Oct 27 19:34:08 bugger mdm[1277]: GLib-GIO-CRITICAL: g_file_info_get_attribute_uint64: assertion 'G_IS_FILE_INFO (info)' failed
...
Oct 27 19:34:10 bugger NetworkManager[979]: <warn> dnsmasq not available on the bus, can't update servers.
Oct 27 19:34:10 bugger NetworkManager[979]: <error> [1382924050.590066] [nm-dns-dnsmasq.c:402] update(): dnsmasq owner not found on bus: Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such name
Oct 27 19:34:10 bugger NetworkManager[979]: <warn> DNS: plugin dnsmasq update failed
Oct 27 19:34:10 bugger NetworkManager[979]: <info> Writing DNS information to /sbin/resolvconf
...
Oct 27 19:34:19 bugger kernel: [   99.525358] usb 7-2: device descriptor read/64, error -110
Oct 27 19:34:26 bugger NetworkManager[979]: <info> (eth0): IP6 addrconf timed out or failed.
Oct 27 19:34:26 bugger NetworkManager[979]: <info> Activation (eth0) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
Oct 27 19:34:26 bugger NetworkManager[979]: <info> Activation (eth0) Stage 4 of 5 (IPv6 Configure Timeout) started...
Oct 27 19:34:26 bugger NetworkManager[979]: <info> Activation (eth0) Stage 4 of 5 (IPv6 Configure Timeout) complete.
Oct 27 19:34:35 bugger kernel: [  114.715442] usb 7-2: device descriptor read/64, error -110
Oct 27 19:34:35 bugger kernel: [  114.954663] usb 7-2: new full-speed USB device number 3 using ohci_hcd
Oct 27 19:34:50 bugger kernel: [  130.041088] usb 7-2: device descriptor read/64, error -110
Oct 27 19:35:05 bugger kernel: [  145.231222] usb 7-2: device descriptor read/64, error -110
Oct 27 19:35:06 bugger kernel: [  145.470436] usb 7-2: new full-speed USB device number 4 using ohci_hcd
Oct 27 19:35:16 bugger kernel: [  155.844341] usb 7-2: device not accepting address 4, error -110
Oct 27 19:35:16 bugger kernel: [  155.979888] usb 7-2: new full-speed USB device number 5 using ohci_hcd
Oct 27 19:35:27 bugger kernel: [  166.353805] usb 7-2: device not accepting address 5, error -110
Oct 27 19:35:27 bugger kernel: [  166.353824] hub 7-0:1.0: unable to enumerate USB device on port 2
Oct 27 19:35:27 bugger kernel: [  166.553694] usb 5-3.1: new low-speed USB device number 3 using ohci_hcd
Oct 27 19:35:27 bugger kernel: [  166.728143] usb 5-3.1: New USB device found, idVendor=045e, idProduct=00db
Oct 27 19:35:27 bugger kernel: [  166.728150] usb 5-3.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Oct 27 19:35:27 bugger kernel: [  166.728156] usb 5-3.1: Product: Natural® Ergonomic Key
Oct 27 19:35:27 bugger kernel: [  166.728160] usb 5-3.1: Manufacturer: Microsoft
Oct 27 19:35:27 bugger mtp-probe: checking bus 5, device 3: "/sys/devices/pci0000:00/0000:00:13.0/usb5/5-3/5-3.1"
Oct 27 19:35:27 bugger mtp-probe: bus: 5, device: 3 was not an MTP device
Oct 27 19:35:27 bugger kernel: [  166.824938] usbcore: registered new interface driver usbhid
Oct 27 19:35:27 bugger kernel: [  166.824943] usbhid: USB HID core driver
...
Oct 27 21:19:55 bugger xscreensaver: pam_ecryptfs: seteuid error
...
Oct 28 08:44:31 bugger xscreensaver: pam_ecryptfs: seteuid error
...
Oct 28 15:47:38 bugger kernel: [72659.857778] nspluginwrapper[15024]: segfault at 7f856cdf91aa ip 00007f85730d97d6 sp 00007fff8719d3c8 error 4 in libc-2.17.so[7f8572fa0000+1bf000]
...
Oct 28 16:10:05 bugger NetworkManager[979]: <error> [1382998205.711047] [nm-system.c:145] nm_system_device_set_ip4_route(): (tun0): failed to set IPv4 route: Object exists
Oct 28 16:10:05 bugger NetworkManager[979]: <error> [1382998205.711229] [nm-system.c:145] nm_system_device_set_ip4_route(): (tun0): failed to set IPv4 route: Object exists
Oct 28 16:10:05 bugger NetworkManager[979]: <error> [1382998205.711388] [nm-system.c:145] nm_system_device_set_ip4_route(): (tun0): failed to set IPv4 route: Object exists
...
Oct 28 18:32:30 bugger NetworkManager[979]: <warn> DNS: plugin dnsmasq update failed
...
Oct 28 18:32:50 bugger NetworkManager[979]: <info> (eth0): IP6 addrconf timed out or failed.

Para ser claro, a LAN é um sucesso e um fracasso. Às vezes funciona (com configuração manual, não com DHCP automático) depois de iniciar o computador, e às vezes não. Os dispositivos USB funcionarão depois de esperar cerca de 2 minutos após o aparecimento da tela de login. Mas se os dispositivos USB e a LAN estão funcionando depois de uma inicialização do sistema, então eles parecem funcionar bem ... até a próxima vez que o sistema for inicializado novamente. É só errar.

Pergunta

Como pode ser visto no arquivo de log, ainda estou tendo problemas com os dispositivos USB e LAN. Como posso resolver esses problemas? Talvez algumas outras configurações da BIOS, outros drivers, ou talvez enviar um bug em algum lugar?

Obrigado.

EDITAR

Eu usei um cronômetro para saber os horários de inicialização do mouse / boot.

Boot  time: 1:53.50
Mouse time: 1:22.16
Total time: 3:15.66

Isso significa que, desde o momento em que eu pressionei o botão liga / desliga, até a tela de login demorou 1:53. Em seguida, levou um 1:22 adicional antes que o mouse e o teclado estivessem operacionais (com suporte a usb 1.0 "ohci_hcd", em vez de suporte a usb 2.0 "ehci-pci"). O tempo total antes que eu pudesse entrar na máquina era 3:15.

1:53 é uma quantidade normal de tempo para o sistema operacional inicializar devido ao hardware especificado?

    
por axiopisty 29.10.2013 / 02:18

1 resposta

1

Tente desativar o suporte do IOMMU no BIOS. Eu tenho o mesmo sistema e estou apenas começando a configurá-lo. Com o IOMMU ativado, vejo os mesmos erros IO_PAGE_FAULT device:01:00.0 ; com ele desativado, esses erros desapareceram, assim como erros relacionados de xhci_hcd (USB 3.0).

    
por Jim Paris 13.11.2013 / 01:50