Linux SCSI subsystem development
 help / color / mirror / Atom feed
From: Doug Ledford <dledford@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@redhat.com>, linux-scsi@vger.kernel.org
Subject: 2.5.43 IO-APIC bug and spinlock deadlock
Date: Wed, 16 Oct 2002 23:33:02 -0400	[thread overview]
Message-ID: <20021017033302.GP8159@redhat.com> (raw)

IO-APIC bug: regular kernel, UP, no IO-APIC or APIC on UP enabled, compile
fails (does *everyone* run SMP or at least UP + APIC now?)

spinlock deadlock: run an smp kernel on a up machine.  On mine here all I 
have to do is try to boot to multiuser mode, it won't make it through the 
startup scripts before it locks up by trying to reenter common_interrupt 
on the only CPU.  Seems like an SMP kernel on UP hardware doesn't disable 
interrupts properly maybe?  I get task lists via alt-sysreq when the 
machine should be hardlocked I think.  Anyway, this is what has been 
tricking me into thinking I had an IDE problem.  IDE is innocent, it's the 
core interrupt handling code.

Back to work on scsi stuff now that I have a decently running 2.5.43
system, I'll let someone else deal with these.

-- 
  Doug Ledford <dledford@redhat.com>     919-754-3700 x44233
         Red Hat, Inc. 
         1801 Varsity Dr.
         Raleigh, NC 27606
  

             reply	other threads:[~2002-10-17  3:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-17  3:33 Doug Ledford [this message]
2002-10-17  4:28 ` 2.5.43 IO-APIC bug and spinlock deadlock Doug Ledford
2002-10-17  4:40   ` Andrew Morton
2002-10-17  5:13     ` Doug Ledford
2002-10-17  8:29       ` Mikael Pettersson
2002-10-17  4:49 ` Zwane Mwaikambo
2002-10-18 19:39 ` Bill Davidsen

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=20021017033302.GP8159@redhat.com \
    --to=dledford@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mingo@redhat.com \
    /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