From: Jan Marek <linux@hazard.jcu.cz>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Cannot unlock spinlock... Was: Problem in yenta.c, 2nd edition
Date: Wed, 7 Nov 2001 11:55:09 +0100 [thread overview]
Message-ID: <20011107115509.F11351@hazard.jcu.cz> (raw)
In-Reply-To: <20011107111056.E11351@hazard.jcu.cz> <E161Pyh-0003hb-00@the-village.bc.nu>
In-Reply-To: <E161Pyh-0003hb-00@the-village.bc.nu>
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
next prev parent reply other threads:[~2001-11-07 10:56 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
2001-11-07 10:29 ` David Woodhouse
2001-11-07 10:47 ` Alan Cox
2001-11-07 10:55 ` Jan Marek [this message]
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=20011107115509.F11351@hazard.jcu.cz \
--to=linux@hazard.jcu.cz \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
/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.