Skip to contentSkip to conversation

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

Fwd: Re: Problem in yenta.c, 2nd edition Jan Marek 4 participants 12 messages Nov 5, 2001 – Nov 7, 2001 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

Jan Marek

author
#1 lore raw

Hallo l-k,

Quoted 3 lines · Andrew Morton

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

Signature · 4 lines
Ing. Jan Marek
University of South Bohemia
Academic Computer Centre
Phone: +420-38-7772080
author
#2 lore raw

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

In reply to a message not in the archive

Hallo l-k,

Quoted 8 lines · Jan Marek
Quoted 3 lines

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:

Quoted 6 lines

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

Signature · 4 lines
Ing. Jan Marek
University of South Bohemia
Academic Computer Centre
Phone: +420-38-7772080
#3 lore raw

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

Quoted 6 lines · [email protected] 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

i386/kernel/irq.c +11 -0
diff -u -r1.4.2.29 irq.c
@@ -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

author
#4 lore raw

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

In reply to Jan Marek

Hallo l-k,

Quoted 7 lines · David Woodhouse
Quoted 4 lines · [email protected] said:

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

Then problem is in the spin_unlock_irqrestore()???

Quoted 7 lines
Quoted 1 line

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...

Quoted 3 lines

--
dwmw2

Sincerely
Jan Marek

Signature · 4 lines
Ing. Jan Marek
University of South Bohemia
Academic Computer Centre
Phone: +420-38-7772080
#5 lore raw

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

Quoted 7 lines · [email protected] 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.

Quoted 1 line

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

author
#6 lore raw

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

In reply to Jan Marek

Hallo,

Quoted 5 lines · David Woodhouse
Quoted 2 lines · [email protected] said:

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

Quoted 7 lines
Quoted 4 lines

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?

Quoted 5 lines
Quoted 2 lines

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...

Quoted 2 lines

--
dwmw2

Sincerely
Jan Marek

Signature · 4 lines
Ing. Jan Marek
University of South Bohemia
Academic Computer Centre
Phone: +420-38-7772080
author
#7 lore raw

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

In reply to Jan Marek

Hallo,

Quoted 2 lines

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...

Quoted 3 lines
Quoted 3 lines

--
dwmw2

Signature · 4 lines
Ing. Jan Marek
University of South Bohemia
Academic Computer Centre
Phone: +420-38-7772080

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-

#8 lore raw

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

Quoted 11 lines

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.

#9 lore raw

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

Quoted 3 lines · [email protected] 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

#10 lore raw

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

Quoted 2 lines

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

author
#11 lore raw

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

In reply to Jan Marek

Hallo,

Quoted 4 lines · Alan Cox

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

Signature · 4 lines
Ing. Jan Marek
University of South Bohemia
Academic Computer Centre
Phone: +420-38-7772080
#12 lore raw

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

In reply to Jan Marek
Quoted 4 lines · Jan Marek

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

Signature · 2 lines
Let us cross over the river, and rest under the shade of the trees.
   --T. J. Jackson, 1863