linux-kernel - Re: IDE cs5530 hda: lost interrupt

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 08 Nov 2006 18:53:53 -0500
From:	Mark Lord <lkml@....ca>
To:	Saulo <slima@....gov.br>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: IDE cs5530 hda: lost interrupt

Saulo wrote:
> Hi all,
> 
> any help is wellcome...
> 
> --------------------
> CPU: NSC Geode(TM) Integrated Processor by National Semi stepping 02
> ...
> ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
> CS5530: ide CONTROLLER AT pci SLOT 0000:00:12.2
> CS5530: chipset revision 0
> CS5530: not 100% native mode: will probe irqs later
> PCI: Enabling bus mastering for device 0000:00:12.2
> PCI: Setting latency timer of device 0000:00:12.2 to 64
>     ide0: BM-DMA at 0xfc00-0xfc07, BIOS settings: hda:pio, hdb:pio
>     ide1: BM-DMA at 0xfc08-0xfc0f, BIOS settings: hdc:pio, hdd:pio
> hda: CF 32MB, CFA DISK drive
> hda: IRQ probe failed (0xfeba)    >>> I think my problem may start here, 
> but when I fix to IRQ 14 in try_to_identify() to hda the problem persist
> ide0 at 0x1f0-0x1f7,0x3f6 on irq14
> hdc: Hitachi CV 5.1.1, CFA DISK drive
> ide1 at 0x170-0x177,0x376 on irq 15 (serialized with ide0)
> hda: max request size: 128KiB
> hda: 62976 sectors (32MB) w/1KiB Cache, CHS=492/4/32
> hda:<4>hda: lost interrupt
> hda: lost interrupt
> hda: lost interrupt
> ...
...

Send me one of those devices and I'll fix it.

Cheers
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/