public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dylan Griffiths <Dylan_G@bigfoot.com>
To: klink@clouddancer.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Annoying kernel behaviour
Date: Sun, 24 Jun 2001 13:46:48 -0600	[thread overview]
Message-ID: <3B3643A8.F3FE1E92@bigfoot.com> (raw)
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> <20010624114655.3D187784C4@mail.clouddancer.com>

Colonel wrote:
> 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?

I would expect the IRQ to shift as the system has a different
motherboard/processor than it did in December.


           CPU0       
  0:    3208074          XT-PIC  timer
  1:          2          XT-PIC  keyboard
  2:          0          XT-PIC  cascade
 10:          1          XT-PIC  bttv
 12:      10444          XT-PIC  eth0
 14:      12366          XT-PIC  ide0
 15:         67          XT-PIC  ide1
NMI:          0 
ERR:          0

There are no conflicts, and PCI should be able to share anyways.

That machine, being a server, is only accesible via the network.  And when
all my SSH sessions to it died, and the pings weren't pinging, I went over
to the server corner, attached a monitor to the machaine and tried the magic
sysrq on the keyboard after verifying that I couldn't get a local response. 
As I said, I can easily lock an entire system in a way that corrupts files
even on a synchronuslly mounted partition from userland with no warning, no
error messages.

Waht part of this do you fail to grasp?


--
    www.kuro5hin.org -- technology and culture, from the trenches.

  reply	other threads:[~2001-06-24 19:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-23  1:24 Annoying kernel behaviour Dylan Griffiths
     [not found] ` <9h0r6s$fe7$1@ns1.clouddancer.com>
2001-06-23  9:05   ` Colonel
2001-06-24 10:37     ` Dylan Griffiths
     [not found]       ` <9h4ft5$1ku$1@ns1.clouddancer.com>
2001-06-24 11:46         ` Colonel
2001-06-24 19:46           ` Dylan Griffiths [this message]
     [not found]             ` <9h5gbc$3mb$1@ns1.clouddancer.com>
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=3B3643A8.F3FE1E92@bigfoot.com \
    --to=dylan_g@bigfoot.com \
    --cc=klink@clouddancer.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