From: Christoph Hellwig <hch@infradead.org>
To: "Ivan G." <ivangurdiev@linuxfreemail.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.4.19-pre8
Date: Fri, 3 May 2002 16:01:11 +0100 [thread overview]
Message-ID: <20020503160111.B9729@infradead.org> (raw)
In-Reply-To: <02050308321201.07377@cobra.linux>
On Fri, May 03, 2002 at 08:32:12AM -0600, Ivan G. wrote:
> Upgrading 2.4.19-pre3 to 2.4.19-pre8
> but problem is probably created by 2.4.19-pre7 where i saw apic changes
I think the following patch should fix it:
diff -uNr -Xdontdiff linux-2.4.19-pre7/arch/i386/kernel/dmi_scan.c linux/arch/i386/kernel/dmi_scan.c
--- linux-2.4.19-pre7/arch/i386/kernel/dmi_scan.c Tue Apr 16 20:49:06 2002
+++ linux/arch/i386/kernel/dmi_scan.c Tue Apr 16 20:56:03 2002
@@ -362,7 +362,7 @@
printk(KERN_INFO " *** If you see IRQ problems, in paticular SCSI resets and hangs at boot\n");
printk(KERN_INFO " *** contact your hardware vendor and ask about updates.\n");
printk(KERN_INFO " *** Building an SMP kernel may evade the bug some of the time.\n");
-#ifdef CONFIG_X86_UP_APIC
+#ifdef CONFIG_X86_UP_IOAPIC
skip_ioapic_setup = 0;
#endif
return 0;
diff -uNr -Xdontdiff linux-2.4.19-pre7/init/main.c linux/init/main.c
--- linux-2.4.19-pre7/init/main.c Tue Apr 16 20:47:46 2002
+++ linux/init/main.c Tue Apr 16 20:59:56 2002
@@ -296,8 +296,7 @@
extern int skip_ioapic_setup;
static void __init smp_init(void)
{
- if (!skip_ioapic_setup)
- APIC_init_uniprocessor();
+ APIC_init_uniprocessor();
}
#else
#define smp_init() do { } while (0)
next prev parent reply other threads:[~2002-05-03 15:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-03 14:32 Linux 2.4.19-pre8 Ivan G.
2002-05-03 15:01 ` Christoph Hellwig [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-05-03 13:16 Dieter Nützel
2002-05-03 14:27 ` Marcelo Tosatti
2002-05-03 11:09 rwhron
2002-05-02 21:51 Marcelo Tosatti
2002-05-03 0:41 ` Alan Cox
2002-05-03 10:42 ` Adrian Bunk
2002-05-03 13:43 ` Alan Cox
2002-05-03 18:07 ` Adrian Bunk
2002-05-17 2:24 ` Mike Fedyk
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=20020503160111.B9729@infradead.org \
--to=hch@infradead.org \
--cc=ivangurdiev@linuxfreemail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.