From: klink@clouddancer.com (Colonel)
To: Dylan_G@bigfoot.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Annoying kernel behaviour
Date: Sun, 24 Jun 2001 04:46:55 -0700 (PDT) [thread overview]
Message-ID: <20010624114655.3D187784C4@mail.clouddancer.com> (raw)
In-Reply-To: <9h4ft5$1ku$1@ns1.clouddancer.com>
In-Reply-To: <3B33EFC0.D9C930D5@bigfoot.com> <9h0r6s$fe7$1@ns1.clouddancer.com> <20010623090542.6019D7846F@mail.clouddancer.com> <3B35C2FA.37F57964@bigfoot.com> <9h4ft5$1ku$1@ns1.clouddancer.com>
In clouddancer.list.kernel, you wrote:
>bttv0: Bt848 (rev 18) at 00:0f.0, irq: 10, latency: 64, memory: 0xd79ff000
> ** ^^ this worked in 2.2.19 as
>bttv0: Brooktree Bt848 (rev 18) bus: 0, devfn: 88, irq: 11, memory:
>
>It shouldn't matter, as userspace programs should not be able te fuck te
>kernel over in such a complete instant deadlock. There is something
Ah, notice that the IRQ shifted? Perhaps there is something else on
irq 10, such as the SCSI controller? My video cards always end up on
that IRQ, perhaps the computer is still accessible via the network?
--
"Or heck, let's just make the VM a _real_ Neural Network, that self
trains itself to the load you put on the system. Hideously complex and
evil? Well, why not wire up that roach on the floor, eating that stale
cheese doodle. It can't do any worse job on VM that some of the VM
patches I've seen..." -- Jason McMullan
ditto
next prev parent reply other threads:[~2001-06-24 11:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9h0r6s$fe7$1@ns1.clouddancer.com>
2001-06-23 1:24 ` Dylan Griffiths
2001-06-23 9:05 ` Colonel
2001-06-24 10:37 ` Dylan Griffiths
2001-06-24 11:46 ` Colonel [this message]
2001-06-24 19:46 ` Dylan Griffiths
2001-06-25 3:22 ` Colonel
2001-06-25 7:41 ` Gerd Knorr
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=20010624114655.3D187784C4@mail.clouddancer.com \
--to=klink@clouddancer.com \
--cc=Dylan_G@bigfoot.com \
--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 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®