Re: [Fwd: Re: Problem in yenta.c, 2nd edition]

Re: [Fwd: Re: Problem in yenta.c, 2nd edition]

[Jan Marek]

Hallo l-k,

On Fri, Nov 02, 2001 at 09:10:18AM -0800, Andrew Morton wrote:
> 
> Try moving the block of code which requests the IRQ down
> so that it comes after the call to cardbus_register().

yes. I tried move the block, what are you wrote about... Bu the
last messages, what I got from notebook when I modprobe'd
yenta_socket is:

Yenta IRQ list 04b8, PCI irq11
Socket status: 30000010

(this messages is generated in function cardbus_register()).

And kernel freeze as before...

One's more my lspci with -vvv switch:

--- start of lspci -vvv
00:00.0 Host bridge: Intel Corporation 440BX/ZX - 82443BX/ZX Host bridge (AGP disabled) (rev 03)
	Subsystem: Compaq Computer Corporation: Unknown device b110
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ >SERR- <PERR-
	Latency: 64
	Region 0: Memory at 50000000 (32-bit, prefetchable) [size=256M]

00:04.0 CardBus bridge: Texas Instruments PCI1211
	Subsystem: Compaq Computer Corporation: Unknown device b103
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 168, cache line size 08
	Interrupt: pin A routed to IRQ 11
	Region 0: Memory at 7fffe000 (32-bit, non-prefetchable) [size=4K]
	Bus: primary=00, secondary=01, subordinate=01, sec-latency=176
	Memory window 0: 10000000-103ff000 (prefetchable)
	Memory window 1: 10400000-107ff000
	I/O window 0: 00004400-000044ff
	I/O window 1: 00004800-000048ff
	BridgeCtl: Parity- SERR- ISA- VGA- MAbort- >Reset+ 16bInt+ PostWrite+
	16-bit legacy interface ports at 0001

00:05.0 VGA compatible controller: ATI Technologies Inc 3D Rage LT Pro (rev dc) (prog-if 00 [VGA])
	Subsystem: Compaq Computer Corporation: Unknown device b11b
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR- FastB2B-
	Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 66 (2000ns min), cache line size 08
	Interrupt: pin A routed to IRQ 11
	Region 0: Memory at 41000000 (32-bit, non-prefetchable) [size=16M]
	Region 1: I/O ports at 3000 [size=256]
	Region 2: Memory at 40280000 (32-bit, non-prefetchable) [size=4K]
	Expansion ROM at <unassigned> [disabled] [size=128K]
	Capabilities: [5c] Power Management version 1
		Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:07.0 Bridge: Intel Corporation 82371AB PIIX4 ISA (rev 02)
	Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
	Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0

00:07.1 IDE interface: Intel Corporation 82371AB PIIX4 IDE (rev 01) (prog-if 80 [Master])
	Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 64
	Region 4: I/O ports at 3820 [size=16]

00:07.2 USB Controller: Intel Corporation 82371AB PIIX4 USB (rev 01) (prog-if 00 [UHCI])
	Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 64
	Interrupt: pin D routed to IRQ 11
	Region 4: I/O ports at 3800 [size=32]

00:07.3 Bridge: Intel Corporation 82371AB PIIX4 ACPI (rev 03)
	Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Interrupt: pin ? routed to IRQ 9

00:08.0 Multimedia audio controller: ESS Technology ES1978 Maestro 2E (rev 10)
	Subsystem: Compaq Computer Corporation: Unknown device b112
	Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 64 (500ns min, 6000ns max)
	Interrupt: pin A routed to IRQ 11
	Region 0: I/O ports at 3400 [size=256]
	Capabilities: [c0] Power Management version 2
		Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA PME(D0-,D1+,D2+,D3hot+,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:09.0 Communication controller: Lucent Microelectronics WinModem 56k (rev 01)
	Subsystem: Compaq Computer Corporation 56k V.90 Modem
	Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Interrupt: pin A routed to IRQ 11
	Region 0: Memory at 40000000 (32-bit, non-prefetchable) [size=256]
	Region 1: I/O ports at 2400 [size=8]
	Region 2: I/O ports at 2000 [size=256]
	Capabilities: [f8] Power Management version 2
		Flags: PMEClk- DSI+ D1- D2+ AuxCurrent=0mA PME(D0-,D1-,D2+,D3hot+,D3cold+)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
--- end of lspci -vvv

Sincerely
Jan Marek
-- 
Ing. Jan Marek
University of South Bohemia
Academic Computer Centre
Phone: +420-38-7772080

Cannot unlock spinlock... Was: Problem in yenta.c, 2nd edition

[Jan Marek]

Hallo l-k,

On Mon, Nov 05, 2001 at 11:29:00AM +0100, Jan Marek wrote:
> > 
> > Try moving the block of code which requests the IRQ down
> > so that it comes after the call to cardbus_register().
> 
> yes. I tried move the block, what are you wrote about... Bu the
> last messages, what I got from notebook when I modprobe'd
> yenta_socket is:
> 
> Yenta IRQ list 04b8, PCI irq11
> Socket status: 30000010
> 
> (this messages is generated in function cardbus_register()).
> 
> And kernel freeze as before...

I tryed to trace of function request_irq():

I found, that problem is in this code:

--- function setup_irq() from file arch/i386/kernel/irq.c

/* this was setup_x86_irq but it seems pretty generic */
int setup_irq(unsigned int irq, struct irqaction * new)
{
	int shared = 0;
	unsigned long flags;
	struct irqaction *old, **p;
	irq_desc_t *desc = irq_desc + irq;

	/*
	 * Some drivers like serial.c use request_irq() heavily,
	 * so we have to be careful not to interfere with a
	 * running system.
	 */
	if (new->flags & SA_SAMPLE_RANDOM) {
		/*
		 * This function might sleep, we want to call it first,
		 * outside of the atomic block.
		 * Yes, this might clear the entropy pool if the wrong
		 * driver is attempted to be loaded, without actually
		 * installing a new handler, but is this really a problem,
		 * only the sysadmin is able to do this.
		 */
		rand_initialize_irq(irq);
	}

	/*
	 * The following block of code has to be executed atomically
	 */
	spin_lock_irqsave(&desc->lock,flags);
	printk("setup_irq: spin_lock_irqsave()\n");
	p = &desc->action;
	if ((old = *p) != NULL) {
		/* Can't share interrupts unless both agree to */
		if (!(old->flags & new->flags & SA_SHIRQ)) {
			spin_unlock_irqrestore(&desc->lock,flags);
			return -EBUSY;
		}

		/* add new interrupt at end of irq queue */
		do {
			p = &old->next;
			old = *p;
		} while (old);
		shared = 1;
	}

	*p = new;

	if (!shared) {
		desc->depth = 0;
		desc->status &= ~(IRQ_DISABLED | IRQ_AUTODETECT | IRQ_WAITING);
		desc->handler->startup(irq);
		printk("request_irq: desc->handler->startup(irq)\n");
	}
	spin_unlock_irqrestore(&desc->lock,flags);
	printk("request_irq: spin_unlock_irqrestore()\n");

	register_irq_proc(irq);
	printk("request_irq: register_irq_proc()\n");
	return 0;
}
--- end of listing

The last message I got from kernel is: 
request_irq: desc->handler->startup(irq)

Then problem is in the spin_unlock_irqrestore()???

Any ideas, recomendations, suggestions?

Sincerely
Jan Marek
-- 
Ing. Jan Marek
University of South Bohemia
Academic Computer Centre
Phone: +420-38-7772080

Re: Cannot unlock spinlock... Was: Problem in yenta.c, 2nd edition

[David Woodhouse]

linux@hazard.jcu.cz said:
>  The last message I got from kernel is:  request_irq: desc->handler->
> startup(irq)

> Then problem is in the spin_unlock_irqrestore()???

> Any ideas, recomendations, suggestions?

It's dying in an IRQ storm. Something is permanently asserting IRQ 11, and 
unless you can work out what's doing it and make it stop, the machine will 
die whenever you enable that IRQ.

Try this hack, just to make sure:

Index: arch/i386/kernel/irq.c
===================================================================
RCS file: /inst/cvs/linux/arch/i386/kernel/irq.c,v
retrieving revision 1.4.2.29
diff -u -r1.4.2.29 irq.c
--- arch/i386/kernel/irq.c	2001/06/21 09:33:54	1.4.2.29
+++ arch/i386/kernel/irq.c	2001/08/15 16:50:01
@@ -552,6 +552,8 @@
 	spin_unlock_irqrestore(&desc->lock, flags);
 }
 
+static unsigned int stormcount[NR_IRQS];
+
 /*
  * do_IRQ handles all normal device IRQ's (the special
  * SMP cross-CPU interrupts have their own specific
@@ -576,6 +578,15 @@
 	unsigned int status;
 
 	kstat.irqs[cpu][irq]++;
+	if (++stormcount[irq] > 200) {
+		printk(KERN_CRIT "IRQ storm detected on IRQ %d. Disabling\n", irq);
+		disable_irq(irq);
+	}
+	if(irq==0) {
+		int i; 
+		for (i=0; i<NR_IRQS; i++)
+			stormcount[i] = 0;
+	}
 	spin_lock(&desc->lock);
 	desc->handler->ack(irq);
 	/*




--
dwmw2

Re: Cannot unlock spinlock... Was: Problem in yenta.c, 2nd edition

[Jan Marek]

Hallo l-k,

On Tue, Nov 06, 2001 at 10:40:49PM +0000, David Woodhouse wrote:
> 
> linux@hazard.jcu.cz said:
> >  The last message I got from kernel is:  request_irq: desc->handler->
> > startup(irq)
> 
> > Then problem is in the spin_unlock_irqrestore()???
> 
> > Any ideas, recomendations, suggestions?
> 
> It's dying in an IRQ storm. Something is permanently asserting IRQ 11, and 
> unless you can work out what's doing it and make it stop, the machine will 
> die whenever you enable that IRQ.
> 
> Try this hack, just to make sure:

Your hack is working for me. I got message:
"IRQ storm detected on IRQ 11. Disabling"

and everythink works OK. Spinlock was unlocked, procedure
setup_irq() ended and PCMCIA package works fine...

It is possible to add your patch to the kernel?

But I don't know, what device asserted IRQ 11 to start the IRQ
storm... When I was in the function setup_irq(), I installed the
first routine to work with IRQ 11 in its IRQ queue...

Or maybe will be safe to disable concrete IRQ, when is installed
a new handler for it?

I'm sorry, I'm not kernel programmer at all, I still thinking
about it... Maybe will be my think usefull for you...

> 
> --
> dwmw2

Sincerely
Jan Marek
-- 
Ing. Jan Marek
University of South Bohemia
Academic Computer Centre
Phone: +420-38-7772080

Re: Cannot unlock spinlock... Was: Problem in yenta.c, 2nd edition

[David Woodhouse]

linux@hazard.jcu.cz said:
>  Your hack is working for me. I got message: "IRQ storm detected on
> IRQ 11. Disabling"

> and everythink works OK. Spinlock was unlocked, procedure setup_irq()
> ended and PCMCIA package works fine...

> It is possible to add your patch to the kernel? 

Absolutely not. In 2.5, we may have some code to deal with IRQ storms, but 
certainly not like that. 

> But I don't know, what device asserted IRQ 11 to start the IRQ storm..

What other PCI devices claim to be on IRQ 11? Do you have ACPI enabled (in 
the BIOS and/or in Linux)?

--
dwmw2

Re: Cannot unlock spinlock... Was: Problem in yenta.c, 2nd edition

[Jan Marek]

Hallo,

On Wed, Nov 07, 2001 at 09:59:49AM +0000, David Woodhouse wrote:
> 
> linux@hazard.jcu.cz said:
> >  Your hack is working for me. I got message: "IRQ storm detected on
> > IRQ 11. Disabling"
> 
> > and everythink works OK. Spinlock was unlocked, procedure setup_irq()
> > ended and PCMCIA package works fine...
> 
> > It is possible to add your patch to the kernel? 
> 
> Absolutely not. In 2.5, we may have some code to deal with IRQ storms, but 
> certainly not like that.

OK... But shall I apply your patch on every kernel while not
exist 2.5 kernel tree?

> 
> > But I don't know, what device asserted IRQ 11 to start the IRQ storm..
> 
> What other PCI devices claim to be on IRQ 11? Do you have ACPI enabled (in 
> the BIOS and/or in Linux)?

I have ACPI enabled and I'm attaching my lspci -vvv... Thank you
very much...

> --
> dwmw2

Sincerely
Jan Marek
-- 
Ing. Jan Marek
University of South Bohemia
Academic Computer Centre
Phone: +420-38-7772080

Re: Cannot unlock spinlock... Was: Problem in yenta.c, 2nd edition

[Jan Marek]

[-- Attachment #1: Type: text/plain, Size: 272 bytes --]

Hallo,

> I have ACPI enabled and I'm attaching my lspci -vvv... Thank you
> very much...

I'm sorry, I don't remember to attach this file... One's more...

> 
> > --
> > dwmw2
-- 
Ing. Jan Marek
University of South Bohemia
Academic Computer Centre
Phone: +420-38-7772080

[-- Attachment #2: lsp --]
[-- Type: text/plain, Size: 4582 bytes --]

00:00.0 Host bridge: Intel Corporation 440BX/ZX - 82443BX/ZX Host bridge (AGP disabled) (rev 03)
	Subsystem: Compaq Computer Corporation: Unknown device b110
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ >SERR- <PERR-
	Latency: 64
	Region 0: Memory at 50000000 (32-bit, prefetchable) [size=256M]

00:04.0 CardBus bridge: Texas Instruments PCI1211
	Subsystem: Compaq Computer Corporation: Unknown device b103
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 168, cache line size 08
	Interrupt: pin A routed to IRQ 11
	Region 0: Memory at 7fffe000 (32-bit, non-prefetchable) [size=4K]
	Bus: primary=00, secondary=01, subordinate=01, sec-latency=176
	Memory window 0: 10000000-103ff000 (prefetchable)
	Memory window 1: 10400000-107ff000
	I/O window 0: 00004400-000044ff
	I/O window 1: 00004800-000048ff
	BridgeCtl: Parity- SERR- ISA- VGA- MAbort- >Reset+ 16bInt+ PostWrite+
	16-bit legacy interface ports at 0001

00:05.0 VGA compatible controller: ATI Technologies Inc 3D Rage LT Pro (rev dc) (prog-if 00 [VGA])
	Subsystem: Compaq Computer Corporation: Unknown device b11b
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR- FastB2B-
	Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 66 (2000ns min), cache line size 08
	Interrupt: pin A routed to IRQ 11
	Region 0: Memory at 41000000 (32-bit, non-prefetchable) [size=16M]
	Region 1: I/O ports at 3000 [size=256]
	Region 2: Memory at 40280000 (32-bit, non-prefetchable) [size=4K]
	Expansion ROM at <unassigned> [disabled] [size=128K]
	Capabilities: [5c] Power Management version 1
		Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:07.0 Bridge: Intel Corporation 82371AB PIIX4 ISA (rev 02)
	Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
	Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0

00:07.1 IDE interface: Intel Corporation 82371AB PIIX4 IDE (rev 01) (prog-if 80 [Master])
	Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 64
	Region 4: I/O ports at 3820 [size=16]

00:07.2 USB Controller: Intel Corporation 82371AB PIIX4 USB (rev 01) (prog-if 00 [UHCI])
	Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 64
	Interrupt: pin D routed to IRQ 11
	Region 4: I/O ports at 3800 [size=32]

00:07.3 Bridge: Intel Corporation 82371AB PIIX4 ACPI (rev 03)
	Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Interrupt: pin ? routed to IRQ 9

00:08.0 Multimedia audio controller: ESS Technology ES1978 Maestro 2E (rev 10)
	Subsystem: Compaq Computer Corporation: Unknown device b112
	Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 64 (500ns min, 6000ns max)
	Interrupt: pin A routed to IRQ 11
	Region 0: I/O ports at 3400 [size=256]
	Capabilities: [c0] Power Management version 2
		Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA PME(D0-,D1+,D2+,D3hot+,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:09.0 Communication controller: Lucent Microelectronics WinModem 56k (rev 01)
	Subsystem: Compaq Computer Corporation 56k V.90 Modem
	Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Interrupt: pin A routed to IRQ 11
	Region 0: Memory at 40000000 (32-bit, non-prefetchable) [size=256]
	Region 1: I/O ports at 2400 [size=8]
	Region 2: I/O ports at 2000 [size=256]
	Capabilities: [f8] Power Management version 2
		Flags: PMEClk- DSI+ D1- D2+ AuxCurrent=0mA PME(D0-,D1-,D2+,D3hot+,D3cold+)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-

Re: Cannot unlock spinlock... Was: Problem in yenta.c, 2nd edition

[David Woodhouse]

alan@lxorguk.ukuu.org.uk said:
>  Can you disable the winmodem in the BIOS at all. I've seen similar
> reports of audio hangs where the IRQ was shared by a lucent winmodem -
> no idea why since it ought to be passive and minding its own business.

We know enough about that hardware to turn the IRQ off from Linux, don't we?
If it's a common problem, we could make a PCI quirk for it.

--
dwmw2

Re: Cannot unlock spinlock... Was: Problem in yenta.c, 2nd edition

[Alan Cox]

> 00:09.0 Communication controller: Lucent Microelectronics WinModem 56k (rev 01)
> 	Subsystem: Compaq Computer Corporation 56k V.90 Modem
> 	Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
> 	Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
> 	Interrupt: pin A routed to IRQ 11
> 	Region 0: Memory at 40000000 (32-bit, non-prefetchable) [size=256]
> 	Region 1: I/O ports at 2400 [size=8]
> 	Region 2: I/O ports at 2000 [size=256]
> 	Capabilities: [f8] Power Management version 2
> 		Flags: PMEClk- DSI+ D1- D2+ AuxCurrent=0mA PME(D0-,D1-,D2+,D3hot+,D3cold+)
> 		Status: D0 PME-Enable- DSel=0 DScale=0 PME-

Can you disable the winmodem in the BIOS at all. I've seen similar reports
of audio hangs where the IRQ was shared by a lucent winmodem - no idea
why since it ought to be passive and minding its own business.

Re: Cannot unlock spinlock... Was: Problem in yenta.c, 2nd edition

[Alan Cox]

> We know enough about that hardware to turn the IRQ off from Linux, don't we?
> If it's a common problem, we could make a PCI quirk for it.

Maybe. Wonder what happens if you stick it into D3 power off 

Re: Cannot unlock spinlock... Was: Problem in yenta.c, 2nd edition

[Jan Marek]

Hallo,

On Wed, Nov 07, 2001 at 10:30:39AM +0000, Alan Cox wrote:
> 
> Can you disable the winmodem in the BIOS at all. I've seen similar reports
> of audio hangs where the IRQ was shared by a lucent winmodem - no idea
> why since it ought to be passive and minding its own business.

I'm sorry, but this is the Compaq Armada notebook and in its BIOS
I can't disable even ACPI or this device :-((( Maybe it is
possible in special "BIOS setup program" which can be load from
Compaq rescue partition: however I remove this partition :-(

I can only remove this device physically from notebook...

But I have good news (maybe): when I switch off ACPI in the
kernel config, I can work with PCMCIA w/o David's patch...
(New kernel fetched from sgi CVS, because I have xfs on the root
filesystem, version is 2.4.14-xfs) ;-))))

Thank you for advice...

Sincerely
Jan Marek
-- 
Ing. Jan Marek
University of South Bohemia
Academic Computer Centre
Phone: +420-38-7772080

Re: Cannot unlock spinlock... Was: Problem in yenta.c, 2nd edition

[Doug McNaught]

Jan Marek <linux@hazard.jcu.cz> writes:

> I'm sorry, but this is the Compaq Armada notebook and in its BIOS
> I can't disable even ACPI or this device :-((( Maybe it is
> possible in special "BIOS setup program" which can be load from
> Compaq rescue partition: however I remove this partition :-(

Have you checked Compaq's website?  I know for their desktop and
server systems you can download setup floppy images that give you all
the functionality of the rescue partition (and IIRC let you recreate
the partition if you want to).  Perhaps the same is true for your
laptop.

-Doug
-- 
Let us cross over the river, and rest under the shade of the trees.
   --T. J. Jackson, 1863