Skip to contentSkip to conversation

lost interrupt

DISCUSSION mikeH 3 participants 7 messages May 7, 2002 – May 8, 2002

lore
Share & tools
lore

mikeH

author
#0 lore raw

Sorry if this is a repeat, I didn't see my last post come through...

I'm being plauged with "hdX: lost interrupt" messages and resultant system hangs in kernel 2.4.18 on a via 82XXXX chipset.

Who should I direct my questions to?

Thanks in advance,

MikeH

#1 lore raw

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Quoted 4 lines · mikeH

Sorry if this is a repeat, I didn't see my last post come through...

I'm being plauged with "hdX: lost interrupt" messages and resultant system hangs in kernel 2.4.18 on a via 82XXXX chipset.

I may not be the right person to answer but I had same problem (same via, same kernel, same interrupt). It helped when I turned unmasking off, i.e. try:

hdparm -u0 /dev/hdX for every X in existing disks you have problems with.

Actually I did some dirty trick too, cause I have UDMA enabled by default and compiled in via specific settings in kernel config, while at the same time I set dma off during init, so I do:

hdparm -d0a0u0 /dev/ide/host0/bus0/target0/lun0/disc (or /dev/hda).

I think -u0 is sufficient but you may try the other command too. My current dirty tricks are overreaction to problems with UDMA few kernels (and years) ago so the second command is for paranoids.

bye
T.

- --

** A C programmer asked whether computer had Buddha's nature.      **
** As the answer, master did "rm -rif" on the programmer's home    **
** directory. And then the C programmer became enlightened...      **
**                                                                 **
** Tomasz Rola          mailto:[email protected]             **

-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 5.0i for non-commercial use
Charset: noconv

iQA/AwUBPNiPKBETUsyL9vbiEQJ/uACgxwcY2jRlPKt2aBaTd4BzwAIAPoAAoK7g wYcFIwJZX+cfwmFopa5JHKA5
=hyqY
-----END PGP SIGNATURE-----

author
#2 lore raw
Quoted 11 lines · Tomasz Rola

hdparm -u0 /dev/hdX for every X in existing disks you have problems with.

hdparm -d0a0u0 /dev/ide/host0/bus0/target0/lun0/disc (or /dev/hda).

bye
T.

Thanks, I tried that but to no avail :(

To expand on the problem :

I have a creative DVD 5x drive and some unbranded CD-RW drive. The problem occurs on both when I try to rip audio.

I know for a fact they both have the capability to rip audio nicely, I have seen them do it under a 2.2.X kernel, but now I'm running 2.4.18 (I need 2.4 for my nvidia card)

However, hdparm returns this (on both drives, no matter what slave/master dma/irq combo I use)...

HDIO_GET_MULTCOUNT failed: Invalid argument

I/O support  =  0 (default 16-bit)
unmaskirq    =  0 (off)
using_dma    =  0 (off)
keepsettings =  0 (off)
HDIO_GET_NOWERR failed: Invalid argument
readonly     =  1 (on)
readahead    =  0 (off)

HDIO_GETGEO failed: Invalid argument
busstate = 1 (on)
HDIO_GET_ACOUSTIC failed: Invalid argument

See the worrying "HDIO_GET_ACOUSTIC failed: Invalid argument" ?

I'm not sure who is maintaining that part of the kernel though.

Thanks for any help,

mikeH

#3 lore raw
In reply to Tomasz Rola
Quoted 8 lines · Tomasz Rola

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Quoted 2 lines · mikeH

Sorry if this is a repeat, I didn't see my last post come through...

Quoted 9 lines
Quoted 1 line

I'm being plauged with "hdX: lost interrupt" messages and resultant system hangs in kernel 2.4.18 on a via 82XXXX chipset.

I may not be the right person to answer but I had same problem (same via, same kernel, same interrupt). It helped when I turned unmasking off, i.e. try:

hdparm -u0 /dev/hdX for every X in existing disks you have problems with.

unmasking is already off on my drive

Padraig.

#4 lore raw

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Quoted 13 lines · Padraig Brady
Quoted 12 lines · Tomasz Rola

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Quoted 4 lines · mikeH

Sorry if this is a repeat, I didn't see my last post come through...

I'm being plauged with "hdX: lost interrupt" messages and resultant system hangs in kernel 2.4.18 on a via 82XXXX chipset.

Quoted 8 lines
Quoted 6 lines

I may not be the right person to answer but I had same problem (same via, same kernel, same interrupt). It helped when I turned unmasking off, i.e. try:

hdparm -u0 /dev/hdX for every X in existing disks you have problems with.

unmasking is already off on my drive

My so called competence ends here...

bye
T.

- --

** A C programmer asked whether computer had Buddha's nature.      **
** As the answer, master did "rm -rif" on the programmer's home    **
** directory. And then the C programmer became enlightened...      **
**                                                                 **
** Tomasz Rola          mailto:[email protected]             **

-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 5.0i for non-commercial use
Charset: noconv

iQA/AwUBPNlufBETUsyL9vbiEQJeSQCeJSy+osD5VoiC7ykENLB1vfxfFmAAnicQ Ztwl52/RkGXuXej5rCvrNlEV
=cfx4
-----END PGP SIGNATURE-----

#5 lore raw
In reply to mikeH
Quoted 3 lines · mikeH

Sorry if this is a repeat, I didn't see my last post come through...

I'm being plauged with "hdX: lost interrupt" messages and resultant system hangs in kernel 2.4.18 on a via 82XXXX chipset.

I'm getting the same thing (very rarely) with a BX chipset and 2.4.16. What CPU are you using? What type of disk is the hdX?

Padraig.

author
#6 lore raw
In reply to mikeH

Its an AMD Duron 1.2ghz, the hdX is either my creative DVD 5x or my cd-rw (unbranded)

mike

Quoted 16 lines · Padraig Brady
Quoted 4 lines · mikeH

Sorry if this is a repeat, I didn't see my last post come through...

I'm being plauged with "hdX: lost interrupt" messages and resultant system hangs in kernel 2.4.18 on a via 82XXXX chipset.

I'm getting the same thing (very rarely) with a BX chipset and 2.4.16. What CPU are you using? What type of disk is the hdX?

Padraig.

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