From: Saulo <slima@tse.gov.br>
To: Mark Lord <lkml@rtr.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: IDE cs5530 hda: lost interrupt
Date: Thu, 09 Nov 2006 10:59:54 -0300 [thread overview]
Message-ID: <4553345A.3090305@tse.gov.br> (raw)
In-Reply-To: <45526E11.9000503@rtr.ca>
Mark Lord wrote:
> 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
> -
Sorry... I would like but I can´t send one of this device to you. If you
have any idea about this problem, any help is wellcome.
Saulo
prev parent reply other threads:[~2006-11-09 13:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-08 22:05 IDE cs5530 hda: lost interrupt Saulo
2006-11-08 21:44 ` Alan Cox
[not found] ` <45525EB0.1070907@tse.gov.br>
2006-11-08 21:59 ` Alan Cox
2006-11-08 23:17 ` Saulo
2006-11-09 13:30 ` Saulo
2006-11-09 13:28 ` Alan Cox
2006-11-08 22:56 ` Saulo
2006-11-08 23:53 ` Mark Lord
2006-11-09 13:59 ` Saulo [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4553345A.3090305@tse.gov.br \
--to=slima@tse.gov.br \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@rtr.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox