killing requests for dead queue [RESOLVIDO]

removido
(usa Nenhuma)

Enviado em 09/12/2011 - 20:52h

boa noite pessoal!

alguém tem sofrido com problemas de montagens de dispositivos USB, leia-se modens 3G?

acontece que recentemente tenho acompanhado as mensagens em /var/log/messages e está tipicamente assim quando conecto meu modem 3G:


Dec 9 20:04:28 localhost kernel: [ 278.239102] option 1-5:1.0: GSM modem (1-port) converter detected
Dec 9 20:04:28 localhost kernel: [ 278.239231] usb 1-5: GSM modem (1-port) converter now attached to ttyUSB0
Dec 9 20:04:28 localhost kernel: [ 278.239289] option 1-5:1.1: GSM modem (1-port) converter detected
Dec 9 20:04:28 localhost kernel: [ 278.239341] usb 1-5: GSM modem (1-port) converter now attached to ttyUSB1
Dec 9 20:04:28 localhost kernel: [ 278.239450] scsi12 : usb-storage 1-5:1.2
Dec 9 20:04:28 localhost kernel: [ 278.239585] option 1-5:1.3: GSM modem (1-port) converter detected
Dec 9 20:04:28 localhost kernel: [ 278.239650] usb 1-5: GSM modem (1-port) converter now attached to ttyUSB2
Dec 9 20:04:28 localhost usb_modeswitch: switched to 19d2:0031 (ZTE, Incorporated: ZTE CDMA Technologies MSM)
Dec 9 20:04:29 localhost kernel: [ 279.238155] scsi 12:0:0:0: Direct-Access ZTE MMC Storage 2.31 PQ: 0 ANSI: 2
Dec 9 20:04:29 localhost kernel: [ 279.239267] scsi: killing requests for dead queue
Dec 9 20:04:29 localhost kernel: [ 279.239340] scsi: killing requests for dead queue
Dec 9 20:04:29 localhost kernel: [ 279.239400] scsi: killing requests for dead queue
Dec 9 20:04:29 localhost kernel: [ 279.239462] scsi: killing requests for dead queue
Dec 9 20:04:29 localhost kernel: [ 279.240496] sd 12:0:0:0: [sdc] Attached SCSI removable disk
Dec 9 20:04:29 localhost kernel: [ 279.240514] scsi: killing requests for dead queue
Dec 9 20:04:29 localhost kernel: [ 279.241532] scsi: killing requests for dead queue
Dec 9 20:04:29 localhost kernel: [ 279.241665] scsi: killing requests for dead queue
Dec 9 20:04:29 localhost kernel: [ 279.242678] scsi: killing requests for dead queue


Simplesmente o usb-modeswitch não consegue liberar o dispositivo para uso e isso fica num loop infinito, cheguei ao cúmulo de removê-lo e passar a ejetar o dispositivo com o eject para conseguir utilizar essa maravilha de serviço chamado net 3G:

$ sudo eject /dev/sr1

Dec 9 20:10:45 localhost kernel: [ 655.483665] usb 1-5: USB disconnect, device number 39
Dec 9 20:10:45 localhost kernel: [ 655.483841] option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0
Dec 9 20:10:45 localhost kernel: [ 655.483857] option 1-5:1.0: device disconnected
Dec 9 20:10:45 localhost kernel: [ 655.483935] option1 ttyUSB1: GSM modem (1-port) converter now disconnected from ttyUSB1
Dec 9 20:10:45 localhost kernel: [ 655.483969] option 1-5:1.1: device disconnected
Dec 9 20:10:45 localhost kernel: [ 655.484461] scsi: killing requests for dead queue
Dec 9 20:10:45 localhost kernel: [ 655.485902] option1 ttyUSB2: GSM modem (1-port) converter now disconnected from ttyUSB2
Dec 9 20:10:45 localhost kernel: [ 655.485923] option 1-5:1.3: device disconnected


O log após o uso do eject e a conexão iniciada pelo wvdial:

h4rd3r@archlinux:~$ sudo tail -f /var/log/messages.log

Dec 9 20:12:18 localhost kernel: [ 748.586649] usb 1-5: USB disconnect, device number 41
Dec 9 20:12:18 localhost kernel: [ 748.587182] scsi: killing requests for dead queue
Dec 9 20:12:23 localhost kernel: [ 753.703314] usb 1-5: new high speed USB device number 42 using ehci_hcd
Dec 9 20:12:23 localhost kernel: [ 753.832579] option 1-5:1.0: GSM modem (1-port) converter detected
Dec 9 20:12:23 localhost kernel: [ 753.832713] usb 1-5: GSM modem (1-port) converter now attached to ttyUSB0
Dec 9 20:12:23 localhost kernel: [ 753.832770] option 1-5:1.1: GSM modem (1-port) converter detected
Dec 9 20:12:23 localhost kernel: [ 753.832823] usb 1-5: GSM modem (1-port) converter now attached to ttyUSB1
Dec 9 20:12:23 localhost kernel: [ 753.832951] scsi36 : usb-storage 1-5:1.2
Dec 9 20:12:23 localhost kernel: [ 753.833063] option 1-5:1.3: GSM modem (1-port) converter detected
Dec 9 20:12:23 localhost kernel: [ 753.833125] usb 1-5: GSM modem (1-port) converter now attached to ttyUSB2
Dec 9 20:12:24 localhost kernel: [ 754.831133] scsi 36:0:0:0: Direct-Access ZTE MMC Storage 2.31 PQ: 0 ANSI: 2
Dec 9 20:12:24 localhost kernel: [ 754.832616] scsi: killing requests for dead queue
Dec 9 20:12:24 localhost kernel: [ 754.832694] scsi: killing requests for dead queue
Dec 9 20:12:24 localhost kernel: [ 754.832761] scsi: killing requests for dead queue
Dec 9 20:12:24 localhost kernel: [ 754.834101] sd 36:0:0:0: [sdc] Attached SCSI removable disk
Dec 9 20:12:24 localhost kernel: [ 754.834142] scsi: killing requests for dead queue
Dec 9 20:12:24 localhost kernel: [ 754.834146] scsi: killing requests for dead queue
Dec 9 20:12:24 localhost kernel: [ 754.835046] scsi: killing requests for dead queue
Dec 9 20:12:24 localhost kernel: [ 754.835158] scsi: killing requests for dead queue
Dec 9 20:12:24 localhost kernel: [ 754.836156] scsi: killing requests for dead queue
Dec 9 20:12:24 localhost kernel: [ 754.836264] scsi: killing requests for dead queue
Dec 9 20:12:34 localhost pppd[2119]: pppd 2.4.5 started by h4rd3r, uid 0
Dec 9 20:12:34 localhost kernel: [ 765.068119] PPP generic driver version 2.4.2
Dec 9 20:12:34 localhost pppd[2119]: Using interface ppp0
Dec 9 20:12:34 localhost pppd[2119]: Connect: ppp0 <--> /dev/ttyUSB2
Dec 9 20:12:34 localhost pppd[2119]: CHAP authentication succeeded
Dec 9 20:12:34 localhost pppd[2119]: CHAP authentication succeeded
Dec 9 20:12:34 localhost kernel: [ 765.115713] PPP BSD Compression module registered
Dec 9 20:12:34 localhost kernel: [ 765.123595] PPP Deflate Compression module registered
Dec 9 20:12:37 localhost pppd[2119]: Could not determine remote IP address: defaulting to 10.64.64.64
Dec 9 20:12:37 localhost pppd[2119]: local IP address X.X.X.X
Dec 9 20:12:37 localhost pppd[2119]: remote IP address 10.64.64.64
Dec 9 20:12:37 localhost pppd[2119]: primary DNS address 200.220.227.56
Dec 9 20:12:37 localhost pppd[2119]: secondary DNS address 200.142.130.202


Pesquisando na internet parece que isso é coisa do kernel 3.1 e que só se resolverá com um patch para a versão 3.1.5:


http://www.linux-archive.org/debian-kernel/602607-silencing-killing-requests-dead-queue.html


ocorrências em outras distros:

http://lists.opensuse.org/opensuse-kernel/2011-11/msg00029.html
http://forums.fedoraforum.org/showthread.php?p=1537404
https://bbs.archlinux.org/viewtopic.php?id=130942
https://bugzilla.redhat.com/show_bug.cgi?id=756500

mais informações:

http://www.spinics.net/lists/stable-commits/msg14694.html


* aqui isso ocorre no Debian e no Arch Linux, mas não no Bodhi onde uso o kernel 3.0.

removido
(usa Nenhuma)

Enviado em 10/12/2011 - 10:14h

agora no Debian estou usando o kernel 2.6.39 do Backports e os erros cessaram:

Dec 10 09:57:12 debian kernel: [ 959.564026] usb 1-5: new high speed USB device number 14 using ehci_hcd
Dec 10 09:57:12 debian kernel: [ 959.707333] usb 1-5: New USB device found, idVendor=19d2, idProduct=2000
Dec 10 09:57:12 debian kernel: [ 959.707344] usb 1-5: New USB device strings: Mfr=2, Product=1, SerialNumber=0
Dec 10 09:57:12 debian kernel: [ 959.707351] usb 1-5: Product: ZTE CDMA Technologies MSM
Dec 10 09:57:12 debian kernel: [ 959.707357] usb 1-5: Manufacturer: ZTE, Incorporated
Dec 10 09:57:12 debian kernel: [ 959.711115] scsi13 : usb-storage 1-5:1.0
Dec 10 09:57:13 debian logger: usb_modeswitch: using overriding config file /etc/usb_modeswitch.d/19d2:2000; make sure this is intended
Dec 10 09:57:13 debian logger: usb_modeswitch: please report any new or corrected settings; otherwise, check for outdated files
Dec 10 09:57:13 debian usb_modeswitch: switching 19d2:2000 (ZTE, Incorporated: ZTE CDMA Technologies MSM)
Dec 10 09:57:15 debian kernel: [ 962.468710] usb 1-5: USB disconnect, device number 14
Dec 10 09:57:20 debian kernel: [ 967.584027] usb 1-5: new high speed USB device number 15 using ehci_hcd
Dec 10 09:57:20 debian kernel: [ 967.719816] usb 1-5: New USB device found, idVendor=19d2, idProduct=0031
Dec 10 09:57:20 debian kernel: [ 967.719826] usb 1-5: New USB device strings: Mfr=2, Product=1, SerialNumber=3
Dec 10 09:57:20 debian kernel: [ 967.719833] usb 1-5: Product: ZTE CDMA Technologies MSM
Dec 10 09:57:20 debian kernel: [ 967.719839] usb 1-5: Manufacturer: ZTE, Incorporated
Dec 10 09:57:20 debian kernel: [ 967.719844] usb 1-5: SerialNumber: 1234567890ABCDEF
Dec 10 09:57:20 debian kernel: [ 967.721869] option 1-5:1.0: GSM modem (1-port) converter detected
Dec 10 09:57:20 debian kernel: [ 967.722038] usb 1-5: GSM modem (1-port) converter now attached to ttyUSB0
Dec 10 09:57:20 debian kernel: [ 967.722190] option 1-5:1.1: GSM modem (1-port) converter detected
Dec 10 09:57:20 debian kernel: [ 967.722303] usb 1-5: GSM modem (1-port) converter now attached to ttyUSB1
Dec 10 09:57:20 debian kernel: [ 967.724908] scsi14 : usb-storage 1-5:1.2
Dec 10 09:57:20 debian kernel: [ 967.725347] option 1-5:1.3: GSM modem (1-port) converter detected
Dec 10 09:57:20 debian kernel: [ 967.725533] usb 1-5: GSM modem (1-port) converter now attached to ttyUSB2
Dec 10 09:57:21 debian usb_modeswitch: switched to 19d2:0031 (ZTE, Incorporated: ZTE CDMA Technologies MSM)
Dec 10 09:57:21 debian kernel: [ 968.734356] scsi 14:0:0:0: Direct-Access ZTE MMC Storage 2.31 PQ: 0 ANSI: 2
Dec 10 09:57:21 debian kernel: [ 968.737412] sd 14:0:0:0: Attached scsi generic sg3 type 0
Dec 10 09:57:21 debian kernel: [ 968.740298] sd 14:0:0:0: [sdc] Attached SCSI removable disk
Dec 10 09:58:53 debian pppd[3009]: pppd 2.4.5 started by root, uid 0
Dec 10 09:58:54 debian chat[3011]: abort on (BUSY)
Dec 10 09:58:54 debian chat[3011]: abort on (NO CARRIER)
Dec 10 09:58:54 debian chat[3011]: abort on (VOICE)
Dec 10 09:58:54 debian chat[3011]: abort on (NO DIALTONE)
Dec 10 09:58:54 debian chat[3011]: abort on (NO DIAL TONE)
Dec 10 09:58:54 debian chat[3011]: abort on (NO ANSWER)
Dec 10 09:58:54 debian chat[3011]: abort on (DELAYED)
Dec 10 09:58:54 debian chat[3011]: send (ATZ^M)
Dec 10 09:58:54 debian chat[3011]: expect (OK)
Dec 10 09:58:54 debian chat[3011]: ^M
Dec 10 09:58:54 debian chat[3011]: OK
Dec 10 09:58:54 debian chat[3011]: -- got it
Dec 10 09:58:54 debian chat[3011]: send (ATDT*99#^M)
Dec 10 09:58:54 debian chat[3011]: expect (CONNECT)
Dec 10 09:58:54 debian chat[3011]: ^M
Dec 10 09:58:54 debian chat[3011]: ATDT*99#^M^M
Dec 10 09:58:54 debian chat[3011]: CONNECT
Dec 10 09:58:54 debian chat[3011]: -- got it
Dec 10 09:58:54 debian chat[3011]: send (\d)
Dec 10 09:58:55 debian pppd[3009]: Serial connection established.
Dec 10 09:58:55 debian pppd[3009]: Using interface ppp0
Dec 10 09:58:55 debian pppd[3009]: Connect: ppp0 <--> /dev/ttyUSB2
Dec 10 09:58:56 debian pppd[3009]: PAP authentication succeeded
Dec 10 09:58:59 debian pppd[3009]: Could not determine remote IP address: defaulting to 10.64.64.64
Dec 10 09:58:59 debian pppd[3009]: local IP address X.X.X.X
Dec 10 09:58:59 debian pppd[3009]: remote IP address 10.64.64.64
Dec 10 09:58:59 debian pppd[3009]: primary DNS address 200.220.227.56
Dec 10 09:58:59 debian pppd[3009]: secondary DNS address 200.142.130.202

Agora vou realizar um downgrade do kernel do Arch para uma das versões disponíveis no ARM (Arch RollBack Machine)

pinduvoz
(usa Debian)

Enviado em 11/12/2011 - 06:38h

Vou aproveitar esse tópico "só seu" (rsrsr) para perguntar: - vale a pena atualizar o Kernel do Deian Squeeze?

Pergunto porque o Kernel original, o 2.6.32, está rodando muito bem, mas talvez a atualização pelo backports melhore ainda mais o desempenho do Squeeze.

removido
(usa Nenhuma)

Enviado em 11/12/2011 - 08:25h

foi parcialmente resolvido, mas começo a achar que não é especificamente por causa do kernel porque mesmo instanado o CrunchBang que usa o kernel 2.6.39 ocntinuei tendo problemas, que só resolvi removendo:

modemmanager, mobileprovideralgumacoisa e usb-modeswitch

daí instalei o porco discador da Vivo, resolvi a pendenga que ocorria com ele que ao ser instalado quebrava o APT e por enquanto está funcionando e sem queda na conexão como ocorre no Windows.

comecei a fazer uma dica lá pro meu blog sobre o uso do mesmo mas ainda não terminei.

sobre atualizar o kernel eu não deveria ter instalado o CrunchBang e sim um Debian puro, já que o CrunchBang usa bastante pacotes do Backports, assim usando o Squeeze com seu kernel eu saberia se teria algum problema ou não.

thanks por não me deixar sozinho! rsrsrs

removido
(usa Nenhuma)

Enviado em 11/12/2011 - 15:23h

de volta ao passado!

nada de modemmanager, usb-modeswitch, mobile-broadband-provider-info e network-manager (esse eu não usava mesmo!).

simplesmente colei uma conf de regras para o UDEV que eu usava antigamente e que estavam num CD de backup:

/etc/udev/rules.d/999-zte.rules

# é a mesma conf que vem no aplicativo da Vivo.
#
# udev rules file for supported cameras
#

#SUBSYSTEM!="usb_device", GOTO="phone_rules_end"
#ACTION!="add", GOTO="phone_rules_end"KERNEL=="sr*",SUBSYSTEMS=="scsi"
#ACTION!="remove", GOTO="phone_rules_end",KERNEL=="scd*",NAME="%k", ACTION=="add",
BUS=="usb",KERNEL=="sr[0-9]*", GROUP="cdrom",SYSFS{idVendor}=="19d2", SYSFS{idProduct}=="2000",SYMLINK+="MODEMCONNECTION",MODE="0666", RUN+=""
BUS=="usb",KERNEL=="sr[0-9]*", GROUP="cdrom",SYSFS{idVendor}=="19d2", SYSFS{idProduct}=="2810",SYMLINK+="MODEMCONNECTION",MODE="0666", RUN+=""

LABEL="phone_rules_end"

# hoje é necessário substituir as STRINGS 'SYSFS' por 'ATTR' para não ver mensagens de erro no início do sistema:

http://reactivated.net/writing_udev_rules.html
http://linuxindetails.wordpress.com/2009/12/30/udevd-sysfs-will-be-removed-in-a-future-udev-version-...
http://lists.debian.org/debian-user/2009/12/msg00370.html
http://forums.opensuse.org/english/get-technical-help-here/pre-release-beta/438296-spew-sysfs-will-r...
http://linux.die.net/man/8/udevadm
http://ubuntuforums.org/showthread.php?t=1496878
http://forums.fedoraforum.org/showthread.php?t=239570
http://usbpicprog.org/?page_id=13

Voltando... o modem é montado, aberto no gerenciador de arquivos como CD-ROM, demontado automaticamente e em seguida liberado para uso, seja através de qualquer app: wvdial, ppp, network-manager e por aí vai!

* testado no Debian Squeeze (CrunchBang) com os kernels 2.6.39-2 do Debian Backports e o kernel 2.6.32-5 do próprio Squeeze.


** agora farei os mesmos testes no Arch Linux apenas removendo as apps (modemmanager, usb-modeswitch, mobile-broadband-provider-info e network-manager), adicionando a regra e verificando se com o kernel 3.1.x funciona da mesma forma que no Debian.


*** é nessas hora que fico feliz por usar Linux, não pelos problemas em si, mas pela possibilidade de aprendizado, veja que uma coisa que eu utilizava na época do kernel 2.6.26 do Debian Lenny me salvou hoje que usava o kernel da série 3.1.x. Não só isso, como pelas inúmeras fontes de pesquisa disponíveis, sejam artigos, Wikis, posts de foruns e etc.

quando não houver desafios o melhor é voltar ao Windows e conviver com os vírus e trojans praquele SO.

removido
(usa Nenhuma)

Enviado em 11/12/2011 - 16:03h

no Arch tenho que usar o eject:

$ sudo eject /dev/sr1

e depois:

$ sudo pon vivo
ou
$ sudo wvdial 3g

* aqui as regras para o UDEV não funcionaram!

removido
(usa Nenhuma)

Enviado em 11/12/2011 - 20:21h

como dito lá em cima que isso era um problema que só seria resolvido com o kernel 3.1.5.x, resolvi instalar no Arch Linux o Kernel-CK 3.1.5-2:

$ sudo pacman -S linux-ck-kx linux-ck-kx-headers


Em seguida instalei as apps que eu havia removido:

$ sudo pacman -S modemmanager usb_modeswitch mobile-broadband-provider-info


E bastou editar o arquivo /etc/usb_modeswitch.setup, removendo as partes desnecessárias e deixando-o assim:

########################################################
# ZTE MF622 (aka "Onda MDC502HS")
# ZTE MF626
# ZTE MF628+ (tested version from Telia / Sweden)
# ZTE MF633
# ZTE MF636 (aka "Telstra / BigPond 7.2 Mobile Card")
# ZTE MF637
# and probably others not listed here
#
# Contributor: Joakim Wennergren and others

DefaultVendor= 0x19d2
DefaultProduct= 0x2000

TargetVendor= 0x19d2
TargetProduct= 0x0031

MessageContent="5553424312345678000000000000061e000000000000000000000000000000"
MessageContent2="5553424312345679000000000000061b000000020000000000000000000000"

NeedResponse=0


O log completo:

h4rd3r@archlinux:~$ uname -a
Linux archlinux 3.1.5-2-ck #1 SMP PREEMPT Fri Dec 9 21:31:15 EST 2011 i686 AMD Athlon(tm) II X4 630 Processor AuthenticAMD GNU/Linux

h4rd3r@archlinux:~$ sudo tail -f /var/log/messages.log
Dec 11 20:00:25 localhost squid[1362]: Beginning Validation Procedure
Dec 11 20:00:25 localhost squid[1362]: Completed Validation Procedure
Dec 11 20:00:25 localhost squid[1362]: Validated 2611 Entries
Dec 11 20:00:25 localhost squid[1362]: store_swap_size = 21284
Dec 11 20:00:25 localhost squid[1362]: storeLateRelease: released 0 objects
Dec 11 20:00:27 localhost dbus[583]: [system] Activating service name='org.freedesktop.ConsoleKit' (using servicehelper)
Dec 11 20:00:27 localhost dbus[583]: [system] Activating service name='org.freedesktop.PolicyKit1' (using servicehelper)
Dec 11 20:00:27 localhost polkitd[1481]: started daemon version 0.102 using authority implementation `local' version `0.102'
Dec 11 20:00:27 localhost dbus[583]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
Dec 11 20:00:27 localhost dbus[583]: [system] Successfully activated service 'org.freedesktop.ConsoleKit'
Dec 11 20:02:04 localhost kernel: [ 113.710039] usb 1-5: new high speed USB device number 4 using ehci_hcd
Dec 11 20:02:04 localhost kernel: [ 113.887216] Initializing USB Mass Storage driver...
Dec 11 20:02:04 localhost kernel: [ 113.887320] scsi4 : usb-storage 1-5:1.0
Dec 11 20:02:04 localhost kernel: [ 113.887442] usbcore: registered new interface driver usb-storage
Dec 11 20:02:04 localhost kernel: [ 113.887445] USB Mass Storage support registered.
Dec 11 20:02:05 localhost usb_modeswitch: switching 19d2:2000 (ZTE, Incorporated: ZTE CDMA Technologies MSM)
Dec 11 20:02:08 localhost kernel: [ 117.292351] usb 1-5: USB disconnect, device number 4
Dec 11 20:02:13 localhost kernel: [ 122.723371] usb 1-5: new high speed USB device number 5 using ehci_hcd
Dec 11 20:02:13 localhost kernel: [ 122.852905] scsi5 : usb-storage 1-5:1.2
Dec 11 20:02:13 localhost kernel: [ 122.948573] usbcore: registered new interface driver usbserial
Dec 11 20:02:13 localhost kernel: [ 122.948585] USB Serial support registered for generic
Dec 11 20:02:13 localhost kernel: [ 122.948648] usbcore: registered new interface driver usbserial_generic
Dec 11 20:02:13 localhost kernel: [ 122.948649] usbserial: USB Serial Driver core
Dec 11 20:02:13 localhost kernel: [ 122.956166] USB Serial support registered for GSM modem (1-port)
Dec 11 20:02:13 localhost kernel: [ 122.956223] option 1-5:1.0: GSM modem (1-port) converter detected
Dec 11 20:02:13 localhost kernel: [ 122.956476] usb 1-5: GSM modem (1-port) converter now attached to ttyUSB0
Dec 11 20:02:13 localhost kernel: [ 122.956510] option 1-5:1.1: GSM modem (1-port) converter detected
Dec 11 20:02:13 localhost kernel: [ 122.956649] usb 1-5: GSM modem (1-port) converter now attached to ttyUSB1
Dec 11 20:02:13 localhost kernel: [ 122.956703] option 1-5:1.3: GSM modem (1-port) converter detected
Dec 11 20:02:13 localhost kernel: [ 122.956810] usb 1-5: GSM modem (1-port) converter now attached to ttyUSB2
Dec 11 20:02:13 localhost kernel: [ 122.956823] usbcore: registered new interface driver option
Dec 11 20:02:13 localhost kernel: [ 122.956826] option: v0.7.2:USB Driver for GSM modems
Dec 11 20:02:14 localhost usb_modeswitch: switched to 19d2:0031 (ZTE, Incorporated: ZTE CDMA Technologies MSM)
Dec 11 20:02:14 localhost kernel: [ 123.851315] scsi 5:0:0:0: Direct-Access ZTE MMC Storage 2.31 PQ: 0 ANSI: 2
Dec 11 20:02:14 localhost kernel: [ 123.853799] sd 5:0:0:0: [sdc] Attached SCSI removable disk
Dec 11 20:02:38 localhost pppd[1712]: pppd 2.4.5 started by h4rd3r, uid 0
Dec 11 20:02:38 localhost kernel: [ 147.614988] PPP generic driver version 2.4.2
Dec 11 20:02:39 localhost chat[1713]: abort on (BUSY)
Dec 11 20:02:39 localhost chat[1713]: abort on (NO CARRIER)
Dec 11 20:02:39 localhost chat[1713]: abort on (VOICE)
Dec 11 20:02:39 localhost chat[1713]: abort on (NO DIALTONE)
Dec 11 20:02:39 localhost chat[1713]: abort on (NO DIAL TONE)
Dec 11 20:02:39 localhost chat[1713]: abort on (NO ANSWER)
Dec 11 20:02:39 localhost chat[1713]: abort on (DELAYED)
Dec 11 20:02:39 localhost chat[1713]: send (ATZ^M)
Dec 11 20:02:39 localhost chat[1713]: expect (OK)
Dec 11 20:02:39 localhost chat[1713]: +ZPASR: "Limited Service"
Dec 11 20:02:39 localhost chat[1713]: +ZDONR: "Not Found"
Dec 11 20:02:39 localhost chat[1713]: +ZPASR: "Limited Service"
Dec 11 20:02:39 localhost chat[1713]: +ZDONR: "Not Found"
Dec 11 20:02:39 localhost chat[1713]: +ZPASR: "Limited Service"
Dec 11 20:02:39 localhost chat[1713]: +ZDONR: "Not Found"
Dec 11 20:02:39 localhost chat[1713]: +ZPASR: "No Service"
Dec 11 20:02:39 localhost chat[1713]: +ZDONR: "VIVO",724,11,"CS_ONLY","ROAM_OFF"
Dec 11 20:02:39 localhost chat[1713]: +ZPASR: "UMTS"
Dec 11 20:02:39 localhost chat[1713]: +ZDONR: "VIVO",724,11,"CS_ONLY","ROAM_OFF"
Dec 11 20:02:39 localhost chat[1713]: +ZPASR: "UMTS"
Dec 11 20:02:39 localhost chat[1713]: +ZDONR: "VIVO",724,11,"CS_PS","ROAM_OFF"
Dec 11 20:02:39 localhost chat[1713]: +ZPASR: "UMTS"
Dec 11 20:02:39 localhost chat[1713]: +ZDONR: "VIVO",724,11,"CS_PS","ROAM_OFF"
Dec 11 20:02:39 localhost chat[1713]: +ZPASR: "UMTS"
Dec 11 20:02:39 localhost chat[1713]: +ZDONR: "VIVO",724,11,"CS_PS","ROAM_OFF"
Dec 11 20:02:39 localhost chat[1713]: +ZPASR: "UMTS"
Dec 11 20:02:39 localhost chat[1713]: AATZ^M^M
Dec 11 20:02:39 localhost chat[1713]: OK
Dec 11 20:02:39 localhost chat[1713]: -- got it
Dec 11 20:02:39 localhost chat[1713]: send (ATDT*99#^M)
Dec 11 20:02:39 localhost chat[1713]: expect (CONNECT)
Dec 11 20:02:39 localhost chat[1713]: ^M
Dec 11 20:02:39 localhost chat[1713]: ATDT*99#^M^M
Dec 11 20:02:39 localhost chat[1713]: CONNECT
Dec 11 20:02:39 localhost chat[1713]: -- got it
Dec 11 20:02:39 localhost chat[1713]: send (\d)
Dec 11 20:02:40 localhost pppd[1712]: Serial connection established.
Dec 11 20:02:40 localhost pppd[1712]: Using interface ppp0
Dec 11 20:02:40 localhost pppd[1712]: Connect: ppp0 <--> /dev/ttyUSB2
Dec 11 20:02:41 localhost pppd[1712]: CHAP authentication succeeded
Dec 11 20:02:41 localhost pppd[1712]: CHAP authentication succeeded
Dec 11 20:02:41 localhost kernel: [ 150.862484] PPP BSD Compression module registered
Dec 11 20:02:41 localhost kernel: [ 150.885171] PPP Deflate Compression module registered
Dec 11 20:02:44 localhost pppd[1712]: Could not determine remote IP address: defaulting to 10.64.64.64
Dec 11 20:02:44 localhost pppd[1712]: local IP address X.X.X.X
Dec 11 20:02:44 localhost pppd[1712]: remote IP address 10.64.64.64
Dec 11 20:02:44 localhost pppd[1712]: primary DNS address 200.220.227.56
Dec 11 20:02:44 localhost pppd[1712]: secondary DNS address 200.142.130.202

removido
(usa Nenhuma)

Enviado em 11/12/2011 - 20:28h

Aproveitando que instalei um kernel otimizado para a arquitetura do processador:

ck-kx ==> AMD K7 (Athlon/Athlon XP)/K8 (Athlon 64, Athlon 64 X2, 23xx Quad-Core Barcelona, Sempron, Sempron 64)/K10-family (Athlon X2 7x50, Phenom X3/X4, Phenom II, Athlon II X2/X3/X4, Sempron 64 (Socket AM3 only), 61xx Eight-Core Magny-Cours) specific optimizations. Enables use of some extended instructions, and passes appropriate optimization flags to GCC.

Adicionei a opção elevator=bfq na linha do kernel do arquivo /etc/default/grub:

GRUB_CMDLINE_LINUX_DEFAULT="quiet elevator=bfq vga=791"

E ao final rodei para gerar um novo grub.cfg:

$ sudo grub-mkconfig -o /boot/grub/grub.cfg

fonte:

https://wiki.archlinux.org/index.php/Linux-ck#How_to_Enable_the_BFQ_I.2FO_Scheduler

removido
(usa Nenhuma)

Enviado em 11/12/2011 - 22:24h

André (pinduvoz), amigos e a quem possa interessar;

todo o roteiro da novela está contado aqui:

http://gnu2all.blogspot.com/2011/12/o-maravilhoso-discador-do-vivo-3g-no.html