linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Clemens Koller <clemens.koller@anagramm.de>
To: Zwane Mwaikambo <zwane@arm.linux.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.13.2 crash on shutdown on SMP machine
Date: Thu, 29 Sep 2005 14:20:33 +0200	[thread overview]
Message-ID: <433BDC11.7070407@anagramm.de> (raw)
In-Reply-To: <Pine.LNX.4.61.0509280812250.1684@montezuma.fsmlabs.com>

Hello, Zwane!


Zwane Mwaikambo wrote:
> On Wed, 28 Sep 2005, Clemens Koller wrote:
> 
>>Last night, right before thinking about going to bed, my newly
>>installed old SMP machine crashed after a #shutdown -h now
>>as shown below:
>>
>>linux-2.6.13.2
>>old Tyan Tomcat Board, Dual Processor, 2xPentium MMX 200MHz
>>SMP enabled, preemption enabled..
>>
>>[...]
>>Shutdown: hda
>>Power down.
>>Badness in send_IPI_mask_bitmask at arch/i386/kernel/smp.c:168
>>c010fdd5    send_IPI_mask_bitmask+0x65/0x70
>>c0110236    smp_send_reschedule+0x16/0x20
> 
> We've seen this one before, how reproducible is it for you? Could you also 
> please test a 2.6.14-rc -mm kernel?

It's reproducable... I got the same thing with a slightly different configured
2.6.13.2-npe (no preemtion, no acpi, no apm) but beside that, I got other
very strange crashes (page table something thingys?) as well during a CRUX pkgmk
tool to build i.e. samba. So I wasn't able to get the system stable enough for
more serious testing yet.
I am about to grab the latest linus' git tree and try that...

This system was running for a long time with linux without any problems
in the past. But I had to change the hdd (old one was broken) and installed
a new (CRUX) system from scratch... I migrated to 2.6.13.2 and switched over
to udev... I was running memtest86 for about half a day. It didn't show any
problems. Are there good torture tests to check if a system's hw is stable?

Thanks,
-- 
Clemens Koller
_______________________________
R&D Imaging Devices
Anagramm GmbH
Rupert-Mayer-Str. 45/1
81379 Muenchen
Germany

http://www.anagramm.de
Phone: +49-89-741518-50
Fax: +49-89-741518-19

  reply	other threads:[~2005-09-29 12:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-28 10:46 2.6.13.2 crash on shutdown on SMP machine Clemens Koller
2005-09-28 15:27 ` Zwane Mwaikambo
2005-09-29 12:20   ` Clemens Koller [this message]
2005-10-01 16:02     ` Zwane Mwaikambo
2005-10-04  9:26       ` Clemens Koller
2005-10-05 20:38         ` Zwane Mwaikambo
2005-09-28 15:29 ` Zwane Mwaikambo
2005-12-05 11:35 ` Clemens Koller
2005-12-05 20:47   ` Zwane Mwaikambo
2005-12-06 11:52     ` Clemens Koller
2005-12-06 17:01       ` Zwane Mwaikambo
2005-12-07 19:19         ` Jeff Collins
2005-12-08  5:36           ` Zwane Mwaikambo
2005-12-08 14:09         ` Clemens Koller

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=433BDC11.7070407@anagramm.de \
    --to=clemens.koller@anagramm.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zwane@arm.linux.org.uk \
    /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;
as well as URLs for NNTP newsgroup(s).