Bem vindo ao pesadelo do conflito de IRQ. ---------- Cabeçalho original -----------
De: [EMAIL PROTECTED] Para: [email protected] Cópia: Data: Sat, 30 Jun 2007 00:23:32 -0300 Assunto: Re: [AsteriskBrasil] oslec em fxo modem ambient 3200 > > As msgs eram: > Jun 28 13:48:11 linux kernel: Open Source Line Echo Canceller > Installed > Jun 28 13:48:11 linux kernel: zaptel: no version for > "oslec_echo_can_traintap" found: kernel tainted. > Jun 28 13:48:11 linux kernel: Zapata Telephony Interface Registered on > major 196 > Jun 28 13:48:11 linux kernel: Zaptel Version: > 1.4.1 > Jun 28 13:48:11 linux kernel: Zaptap registered 'sample' char driver > on major 33 > Jun 28 13:48:12 linux kernel: ACPI: PCI Interrupt 0000:00:0e.0[A] -> > GSI 17 (level, low) -> IRQ 201Jun 28 13:48:12 linux kernel: wcfxo: DAA > mode is 'FCC' > Jun 28 13:48:12 linux kernel: Found a Wildcard FXO: Generic > Clone > Jun 28 13:48:12 linux kernel: Registered tone zone 0 (United States / > North America) > Jun 28 13:48:12 linux kernel: usbcore: registered new driver > wcusb > Jun 28 13:48:12 linux kernel: Wildcard USB FXS Interface driver > registered > Jun 28 13:48:12 linux kernel: Registered tone zone 0 (United States / > North America) > Jun 28 13:48:14 linux kernel: FXO PCI Master > abort > Jun 28 13:48:14 linux last message repeated 1040 > times > Jun 28 13:48:14 linux kernel: FXO PCI Master r > abort > Jun 28 13:48:14 linux kernel: FXO PCI Master > abort > Jun 28 13:48:14 linux last message repeated 169 > times > Jun 28 13:48:14 linux kernel: FXO r > abort > Jun 28 13:48:14 linux kernel: FXO PCI Master > abort > Jun 28 13:48:14 linux last message repeated 169 times > quando reiniciei a máquina, ele encheu a tela das msgs abaixo, travou > o teclado, mouse.... foi um sofrimento pra recuperar o sistema!!! :( > Jun 28 13:51:10 linux last message repeated 169 times > Jun 28 13:51:10 linux kernel: FXO r abort > Jun 28 13:51:10 linux kernel: FXO PCI Master abort > Jun 28 13:51:10 linux last message repeated 169 times > Jun 28 13:51:10 linux kernel: FXO r ar abort > Jun 28 13:51:10 linux kernel: FXO PCI Master abort > Jun 28 13:51:10 linux last message repeated 169 times > Jun 28 13:51:10 linux kernel: Fr aborr abort > Jun 28 13:51:10 linux kernel: FXO PCI Master abort > Jun 28 13:51:10 linux last message repeated 169 times > Jun 28 13:51:10 linux kernel: <r abort > Jun 28 13:51:10 linux kernel: FXO PCI Master abort > Jun 28 13:51:10 linux last message repeated 169 times > Jun 28 13:51:10 linux kernel: FXO r abort > Jun 28 13:51:10 linux kernel: FXO PCI Master abort > Jun 28 13:51:10 linux last message repeated 169 times > Jun 28 13:51:10 linux kernel: FXO r aborr abort > Jun 28 13:51:10 linux kernel: FXO PCI Master abort > Leonardo Gomes Figueira escreveu: > > Eduardo Pereira escreveu: > > > Aos que estou usando o oslec > > é normal ele disparar o HD e levar o processamento da máquina 50%? > > > Se o HD "dispara" provavelmente algo está gerando mensagens no kernel e > o log do kernel está sendo gravado no HD, é isso que acontece ? Se for o > caso, que mensagens estão aparecendo no log ? > > Leonardo > _______________________________________________ > LIsta de discussões AsteriskBrasil.org > [EMAIL PROTECTED] > [2]http://listas.asteriskbrasil.org/mailman/listinfo/asteriskbrasil > > _______________________________________________ > Acesse o wiki AsteriskBrasil.org: > [3]http://www.asteriskbrasil.org > _______________________________________________ LIsta de discussões AsteriskBrasil.org [email protected] http://listas.asteriskbrasil.org/mailman/listinfo/asteriskbrasil _______________________________________________ Acesse o wiki AsteriskBrasil.org: http://www.asteriskbrasil.org
