mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Roman Kagan <Roman.Kagan@itep.ru>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.4.11 APIC problems
Date: Thu, 11 Oct 2001 11:37:16 +0400	[thread overview]
Message-ID: <15301.19500.30733.197896@jaguar.itep.ru> (raw)

I had exactly the same problem on my HP e800.  I've tried to identify
what had changed between 2.4.10 and 2.4.11 in IO-APIC code, and I've
found out that probably the only change relevant to my uniprocessor
case is the change of the initial value of dest_mode field in struct
IO_APIC_route_entry in setup_IO_APIC_irqs() and
setup_ExtINT_IRQ0_pin() in arch/i386/kernel/io_apic.c from 1 to macro
INT_DELIVERY_MODE, which for uniprocessors was defined to be 0.

I don't claim I understand whether it is right or wrong, but the
following patch can fix _my_ problem:

--- linux/include/asm-i386/smp.h.int_delivery	Wed Oct 10 13:36:11 2001
+++ linux/include/asm-i386/smp.h	Wed Oct 10 18:17:06 2001
@@ -31,7 +31,7 @@
 #  define INT_DELIVERY_MODE 1     /* logical delivery broadcast to all procs */
 # endif
 #else
-# define INT_DELIVERY_MODE 0     /* physical delivery on LOCAL quad */
+# define INT_DELIVERY_MODE 1     /* logical delivery */
 # define TARGET_CPUS 0x01
 #endif
 

Cheers,
	Roman.

             reply	other threads:[~2001-10-11  7:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-11  7:37 Roman Kagan [this message]
2001-10-11 15:22 ` 2.4.11 APIC problems - please apply patch Martin J. Bligh
     [not found] <1002727820.29151.21.camel@plars.austin.ibm.com>
2001-10-10 20:46 ` 2.4.11 APIC problems Martin J. Bligh
     [not found] <1979423952.1002706803@mbligh.des.sequent.com>
2001-10-10 14:24 ` Paul Larson
  -- strict thread matches above, loose matches on Subject: below --
2001-10-10  9:46 Paul Larson

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=15301.19500.30733.197896@jaguar.itep.ru \
    --to=roman.kagan@itep.ru \
    --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®