From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: linux@hazard.jcu.cz (Jan Marek)
Cc: dwmw2@infradead.org (David Woodhouse),
linux-kernel@vger.kernel.org (linux-kernel)
Subject: Re: Cannot unlock spinlock... Was: Problem in yenta.c, 2nd edition
Date: Wed, 7 Nov 2001 10:30:39 +0000 (GMT) [thread overview]
Message-ID: <E161Pyh-0003hb-00@the-village.bc.nu> (raw)
In-Reply-To: <20011107111056.E11351@hazard.jcu.cz> from "Jan Marek" at Nov 07, 2001 11:10:56 AM
> 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.
next prev parent reply other threads:[~2001-11-07 10:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3BE2D37A.D32C6DB1@zip.com.au>
2001-11-05 10:29 ` [Fwd: Re: Problem in yenta.c, 2nd edition] Jan Marek
2001-11-06 11:34 ` Cannot unlock spinlock... Was: Problem in yenta.c, 2nd edition Jan Marek
2001-11-06 22:40 ` David Woodhouse
2001-11-07 9:40 ` Jan Marek
2001-11-07 9:59 ` David Woodhouse
2001-11-07 10:07 ` Jan Marek
2001-11-07 10:10 ` Jan Marek
2001-11-07 10:30 ` Alan Cox [this message]
2001-11-07 10:29 ` David Woodhouse
2001-11-07 10:47 ` Alan Cox
2001-11-07 10:55 ` Jan Marek
2001-11-07 15:04 ` Doug McNaught
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=E161Pyh-0003hb-00@the-village.bc.nu \
--to=alan@lxorguk.ukuu.org.uk \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@hazard.jcu.cz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.