Re: [OT] Problemas com DMA e Kernel 2.4
Isso e causado porque voce esta com o servico
smartmontools, ou smartd desabilitado.
smartctl -i /dev/hda
Se aparecer como disable
Voce tem duas opcoes, habilite o SMART no setup da sua
maquina ou habilite o smartd no arquivo
/etc/default/smartmontools
As mensagens irao parar em seguida.
Marcos
--- Gian Nicodemus <gian@pruonckk.org> escreveu:
> Caro amigo ja verificou este hd em outro computador
> que tenha a mesma
> distro que o seu?
>
>
>
>
>
> Gian Nicodemus
> Técnico em hardware
> gian@pruonckk.org
> http://gean.pruonckk.org
> Viva o Software LIVRE!!
>
> > Salve povo.
> >
> > Estou com o Debian Etch e Kernel 2.4.31, que
> compilei na mão. Meus
> > discos estão dispostos da seguinte forma:
> >
> > Primary Master (hda): SAMSUNG SP4002H 40GiB UDMA 2
> > Secondary Master (hdb): Maxtor 2B020H1 20GiB UDMA
> 2
> > Primary Slave (hdc): QUANTUM FIREBALLlct20 30GiB
> UDMA 2
> > Secondary Slave (hdd): hdd: HL-DT-ST DVDRAM
> GSA-4163B UDMA 2
> >
> > Durante o boot (e as vezes quando o computador
> está em funcionamento)
> > eu recebo a seguinte mensagem:
> >
> > hdc: dma_intr: status=0x51 { DriveReady
> SeekComplete Error }
> > hdc: dma_intr: error=0x84 { DriveStatusError
> BadCRC }
> > hdc: dma_intr: status=0x51 { DriveReady
> SeekComplete Error }
> > hdc: dma_intr: error=0x84 { DriveStatusError
> BadCRC }
> > hdc: dma_intr: status=0x51 { DriveReady
> SeekComplete Error }
> > hdc: dma_intr: error=0x84 { DriveStatusError
> BadCRC }
> > hdc: dma_intr: status=0x51 { DriveReady
> SeekComplete Error }
> > hdc: dma_intr: error=0x84 { DriveStatusError
> BadCRC }
> > ide1: reset: success
> > hdc: DMA disabled
> >
> > Quando deu essa mensagem da primeira vez, eu mudei
> o UDMA do hdc, que
> > estava com 5, para 2. Achei que iria funcionar,
> mas continuou dando
> > esse erro. Achei que poderia ser o flat cable,
> bem, troquei-o, mas não
> > resolveu. Tudo funciona normalmente, o computador
> não trava, só que as
> > vezes esse erro ocorre. Consigo gravar CDs e DVDs
> normalmente, sem
> > nenhm problema. Qual será a razão desse erro? Será
> que o meu Quantum
> > foi pro saco? Será o flat cable? Alguém já teve
> algum erro parecido?
> >
> > Agradeço qualquer colaboração e desde já me
> desculpo por ser OFF-TOPIC.
> >
> > Abraços,
> > Gustavo
> >
> > PS. Segue o meu dmesg:
> >
> > Linux version 2.4.31 (root@fingolfin) (gcc version
> 3.3.5 (Debian
> > 1:3.3.5-13)) #5 Mon Jul 18 20:19:33 BRT 2005
> > BIOS-provided physical RAM map:
> > BIOS-e820: 0000000000000000 - 000000000009fc00
> (usable)
> > BIOS-e820: 000000000009fc00 - 00000000000a0000
> (reserved)
> > BIOS-e820: 00000000000f0000 - 0000000000100000
> (reserved)
> > BIOS-e820: 0000000000100000 - 0000000017ffc000
> (usable)
> > BIOS-e820: 0000000017ffc000 - 0000000017fff000
> (ACPI data)
> > BIOS-e820: 0000000017fff000 - 0000000018000000
> (ACPI NVS)
> > BIOS-e820: 00000000fec00000 - 00000000fec01000
> (reserved)
> > BIOS-e820: 00000000fee00000 - 00000000fee01000
> (reserved)
> > BIOS-e820: 00000000ffff0000 - 0000000100000000
> (reserved)
> > 383MB LOWMEM available.
> > On node 0 totalpages: 98300
> > zone(0): 4096 pages.
> > zone(1): 94204 pages.
> > zone(2): 0 pages.
> > ACPI: RSDP (v000 ASUS
> ) @ 0x000f6810
> > ACPI: RSDT (v001 ASUS P4S333 0x42302e31 MSFT
> 0x31313031) @ 0x17ffc000
> > ACPI: FADT (v001 ASUS P4S333 0x42302e31 MSFT
> 0x31313031) @ 0x17ffc100
> > ACPI: BOOT (v001 ASUS P4S333 0x42302e31 MSFT
> 0x31313031) @ 0x17ffc040
> > ACPI: MADT (v001 ASUS P4S333 0x42302e31 MSFT
> 0x31313031) @ 0x17ffc080
> > ACPI: DSDT (v001 ASUS P4S333 0x00001000 MSFT
> 0x0100000b) @ 0x00000000
> > Kernel command line: auto BOOT_IMAGE=Linux2431 ro
> root=301 hdd=ide-scsi
> > ide_setup: hdd=ide-scsi
> > Initializing CPU#0
> > Detected 1715.282 MHz processor.
> > Console: colour VGA+ 80x25
> > Calibrating delay loop... 3420.97 BogoMIPS
> > Memory: 385888k/393200k available (1708k kernel
> code, 6924k reserved,
> > 598k data, 96k init, 0k highmem)
> > Dentry cache hash table entries: 65536 (order: 7,
> 524288 bytes)
> > Inode cache hash table entries: 32768 (order: 6,
> 262144 bytes)
> > Mount cache hash table entries: 512 (order: 0,
> 4096 bytes)
> > Buffer cache hash table entries: 32768 (order: 5,
> 131072 bytes)
> > Page-cache hash table entries: 131072 (order: 7,
> 524288 bytes)
> > CPU: Trace cache: 12K uops, L1 D cache: 8K
> > CPU: L2 cache: 256K
> > Intel machine check architecture supported.
> > Intel machine check reporting enabled on CPU#0.
> > CPU: After generic, caps: 3febfbff 00000000
> 00000000 00000000
> > CPU: Common caps: 3febfbff 00000000
> 00000000 00000000
> > CPU: Intel(R) Pentium(R) 4 CPU 1.70GHz stepping 02
> > Enabling fast FPU save and restore... done.
> > Enabling unmasked SIMD FPU exception support...
> done.
> > Checking 'hlt' instruction... OK.
> > ACPI: IRQ9 SCI: Level Trigger.
> > POSIX conformance testing by UNIFIX
> > ACPI: Subsystem revision 20040326
> > PCI: PCI BIOS revision 2.10 entry at 0xf1580, last
> bus=1
> > PCI: Using configuration type 1
> > ACPI: Interpreter enabled
> > ACPI: Using PIC for interrupt routing
> > ACPI: System [ACPI] (supports S0 S1 S4 S5)
> > ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10
> *11 12 14 15)
> > ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7
> *10 11 12 14 15)
> > ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 7
> 10 11 12 14 15)
> > ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 10
> 11 12 14 15) *0,
> > disabled.
> > ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10
> 11 12 14 15) *9
> > ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10
> 11 12 14 15) *0,
> > disabled.
> > ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10
> 11 12 14 15) *0,
> > disabled.
> > ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10
> 11 12 14 15) *9
> > ACPI: PCI Root Bridge [PCI0] (00:00)
> > PCI: Probing PCI hardware (bus 00)
> > ACPI: PCI Interrupt Routing Table
> [\_SB_.PCI0._PRT]
> > ACPI: PCI Interrupt Routing Table
> [\_SB_.PCI0.PCI1._PRT]
> > PCI: Probing PCI hardware
> > ACPI: PCI Interrupt Link [LNKE] enabled at IRQ 11
> > ACPI: PCI Interrupt Link [LNKH] enabled at IRQ 10
> > ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 10
> > ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 5
> > ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 11
> > PCI: Using ACPI for IRQ routing
> > isapnp: Scanning for PnP cards...
> > isapnp: No Plug & Play device found
> > Linux NET4.0 for Linux 2.4
> > Based upon Swansea University Computer Society
> NET3.039
> > Initializing RT netlink socket
> > Starting kswapd
> > Journalled Block Device driver loaded
> > devfs: v1.12c (20020818) Richard Gooch
> (rgooch@atnf.csiro.au)
> > devfs: boot_options: 0x1
> > ACPI: Power Button (FF) [PWRF]
> > ACPI: Processor [CPU0] (supports C1)
> > pty: 256 Unix98 ptys configured
>
=== message truncated ===
__________________________________________________
Converse com seus amigos em tempo real com o Yahoo! Messenger
http://br.download.yahoo.com/messenger/
Reply to: