From: Keith Owens <kaos@ocs.com.au>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Help - 2.4.5 SMP doesn't boot (any more)
Date: Tue, 26 Jun 2001 14:42:16 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590693005769@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590693005768@msgid-missing>
On Tue, 26 Jun 2001 15:59:08 +0200 (CEST),
Martin Wilck <Martin.Wilck@fujitsu-siemens.com> wrote:
>Yesterday I had 2.4.5 running fine. Since today, I can't boot
>the 2.4.5 SMP kernel any more. I get a kernel panic (invalid page
>request at 0000000000000010) after SMP is enabled
>(actually the last message I see is "trying to unmount old root ...",
>but from kdb messages and the fact that uniprocessor 2.4.5 boots, it
>is clear that it is a SMP error).
That sounds like a known bug in 2.4.5 with undefined data in an inode
during root switch. Fixed in 2.4.6-pre2. The symptoms can be weird,
other people have blamed it on compilers, it is just luck if the
undefined field causes a problem or not.
Index: 5.1/fs/block_dev.c
--- 5.1/fs/block_dev.c Wed, 23 May 2001 11:55:33 +1000 kaos (linux-2.4/p/b/16_block_dev. 1.2.2.3 644)
+++ 6-pre5.1/fs/block_dev.c Sat, 09 Jun 2001 11:25:53 +1000 kaos (linux-2.4/p/b/16_block_dev. 1.2.2.4 644)
@@ -595,14 +595,15 @@ int check_disk_change(kdev_t dev)
int ioctl_by_bdev(struct block_device *bdev, unsigned cmd, unsigned long arg)
{
- kdev_t rdev = to_kdev_t(bdev->bd_dev);
struct inode inode_fake;
int res;
mm_segment_t old_fs = get_fs();
if (!bdev->bd_op->ioctl)
return -EINVAL;
- inode_fake.i_rdev=rdev;
+ memset(&inode_fake, 0, sizeof(inode_fake));
+ inode_fake.i_rdev = to_kdev_t(bdev->bd_dev);
+ inode_fake.i_bdev = bdev;
init_waitqueue_head(&inode_fake.i_wait);
set_fs(KERNEL_DS);
res = bdev->bd_op->ioctl(&inode_fake, NULL, cmd, arg);
next prev parent reply other threads:[~2001-06-26 14:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-26 13:59 [Linux-ia64] Help - 2.4.5 SMP doesn't boot (any more) Martin Wilck
2001-06-26 14:42 ` Keith Owens [this message]
2001-06-26 17:16 ` Martin Wilck
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=marc-linux-ia64-105590693005769@msgid-missing \
--to=kaos@ocs.com.au \
--cc=linux-ia64@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