From: Pavel Machek <pavel@suse.cz>
To: Carl Thompson <cet@carlthompson.net>
Cc: vda <vda@port.imtp.ilyichevsk.odessa.ua>, linux-kernel@vger.kernel.org
Subject: Re: hard lock using combination of devices
Date: Tue, 17 Feb 2004 23:33:20 +0100 [thread overview]
Message-ID: <20040217223319.GB666@elf.ucw.cz> (raw)
In-Reply-To: <20040217061400.z9r4gss0gsockws4@carlthompson.net>
Hi!
> >>> Your box share IRQs in a big way :)
> >>
> >>Your point?
> >
> >While shared interrupts can in theory work right,
> >lots of hardware and/or drivers do not handle
> >that.
>
> First, the two devices in question are not on the same interrupt. Second,
> it
> is very difficult in this day in age to build a system without interrupt
> sharing. While I agree that it's better to have as few devices sharing as
> possible, there are simply too many devices in modern systems and too few
> interrupts. Interrupt sharing needs to work on modern hardware and needs to
> work in Linux. This notebook is pretty typical in its interrupt
> distribution
> CPU0
> 0: 41027968 XT-PIC timer
> 1: 26061 XT-PIC i8042
> 2: 0 XT-PIC cascade
> 8: 1 XT-PIC rtc
> 9: 2020 XT-PIC acpi
> 10: 2187181 XT-PIC yenta, driverloader
> 11: 111 XT-PIC ALI 5451
> 12: 2399118 XT-PIC i8042
> 14: 169829 XT-PIC ide0
> 15: 1 XT-PIC ide1
> NMI: 0
> LOC: 41036749
> ERR: 275764
> MIS: 0
Does that mean you are actually using windows driver for your wireless
card? At that point ... no wonder it breaks ;-).
Pavel
--
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]
next prev parent reply other threads:[~2004-02-17 22:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-17 5:41 Carl Thompson
2004-02-17 6:54 ` vda
2004-02-17 7:14 ` Carl Thompson
2004-02-17 9:49 ` vda
2004-02-17 14:14 ` Carl Thompson
2004-02-17 14:39 ` Richard B. Johnson
2004-02-17 20:30 ` Carl Thompson
2004-02-17 22:33 ` Pavel Machek [this message]
2004-02-18 0:32 ` Carl Thompson
2004-02-18 22:13 ` Vlasenko Denis
2004-02-18 23:20 ` Carl Thompson
2004-02-19 21:04 ` Vlasenko Denis
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=20040217223319.GB666@elf.ucw.cz \
--to=pavel@suse.cz \
--cc=cet@carlthompson.net \
--cc=linux-kernel@vger.kernel.org \
--cc=vda@port.imtp.ilyichevsk.odessa.ua \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®