Re: 2.6.10 smp kernel locks up on boot
Hallo John,
I had the same promlem last week. Frederik Schueler has make a new kernel for
smp. Hier is his mail:
---------- Weitergeleitete Nachricht ----------
Return-Path: <freddy@lowpingbastards.de>
Received: from mail.tzv.fal.de ([unix socket])
by dcs (Cyrus v2.1.4-Debian2.1.4-20) with LMTP; Sat, 26 Feb 2005 15:45:55
+0100
X-Sieve: CMU Sieve 2.1
Received: from localhost (localhost.localdomain [127.0.0.1])
by mail.tzv.fal.de (Postfix) with ESMTP id C90F08300CC
for <most@tzv.local>; Sat, 26 Feb 2005 15:45:55 +0100 (CET)
Received: from mail.tzv.fal.de ([127.0.0.1])
by localhost (dcs [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
id 11232-04 for <most@tzv.local>;
Sat, 26 Feb 2005 15:45:55 +0100 (CET)
Received: from defiant.lowpingbastards.de (defiant.lowpingbastards.de
[213.178.77.226])
by mail.tzv.fal.de (Postfix) with ESMTP id 306F88300C0
for <most@tzv.fal.de>; Sat, 26 Feb 2005 15:45:55 +0100 (CET)
Received: from defiant.lowpingbastards.de (freddy@localhost.lowpingbastards.de
[127.0.0.1])
by defiant.lowpingbastards.de (8.13.3/8.13.3/Debian-6) with ESMTP id
j1QEjXJ1013258;
Sat, 26 Feb 2005 15:45:33 +0100
Received: (from freddy@localhost)
by defiant.lowpingbastards.de (8.13.3/8.13.3/Submit) id j1QEjN83013255;
Sat, 26 Feb 2005 15:45:23 +0100
Date: Sat, 26 Feb 2005 15:45:23 +0100
From: Frederik Schueler <fs@lowpingbastards.de>
To: Monika Strack <most@tzv.fal.de>,
Valerio Aimale <vga@seirad.com>,
Alex Page <alex.page@cancer.org.uk>
Subject: pre-release 2.6.10 kernel images
Message-ID: <20050226144523.GG7989@mail.lowpingbastards.de>
Mime-Version: 1.0
Content-Type: multipart/signed;
micalg=pgp-sha1;
protocol="application/pgp-signature";
boundary="3U8TY7m7wOx7RL1F"
Content-Disposition: inline
User-Agent: Mutt/1.5.6+20040907i
X-Virus-Scanned: by amavisd-new
X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at tzv.fal.de
X-Spam-Status: No, hits=-1.7 tagged_above=-999.0 required=5.0 tests=BAYES_00
X-Spam-Level:
Status: R
X-Status: NC
X-KMail-EncryptionState:
X-KMail-SignatureState:
X-KMail-MDN-Sent:
Hello,
I have prepared kernel images based on hopefully fixed 2.6.10 kernel
sources, wich address the problems you reported: kernel-panic on boot on
amd64 smp systems.
Could you please give the kernel image found at
deb http://debian-amd64.alioth.debian.org/pure64/kernel-test/ ./
a try, there are unreleased packages based on a SVN version of
kernel-source, and only intended to see if the SMP issues are fixed now.
If you still cannot successfully boot the kernel, please send me a
complete Call Trace, if possible.
Thanks in advice for your help
Frederik Schueler
--
ENOSIG
-------------------------------------------------------
--
________________________________________________________________________________
Monika Strack
Institut fuer Tierzucht
Bundesforschungsanstalt fuer Landwirtschaft
31535 Neustadt e-mail: most@tzv.fal.de
Germany Tel: +49 5034 /871 154
Fax: +49 5034 /871 239
_______________________________________________________________________________
Am Dienstag, 1. März 2005 09:57 schrieb John Rigg:
> I've just done a new pure64 installation on my dual Opteron using
> 19-02-2005 netinst. This went smoothly until I tried to upgrade to the
> current 2.6.10 smp kernel
> (kernel-image-2.6.10-9-amd64-k8-smp_2.6.10-4_amd64.deb). It caused a lockup
> on first reboot with the following message:
>
> modprobe [909] trap invalid operand rip: 2a956ea248 rsp: 7fbffff818 error:
> 0 NMI Watchdog detected LOCKUP on CPU0CPU 0
> Modules linked in: ext3 jbd mbcache
>
> Subsequent hard reboot caused a lockup without the first line of the
> above message. In both cases the lockup followed a long list of error
> messages regarding various modules, eg.
> ERROR: Removing 'trm290': Device or resource busy
> There were so many of these they scrolled off the screen.
>
> I then tried an earlier version of this kernel which I had saved on a CD
> (kernel-image-2.6.10-9-amd64-k8-smp_2.6.10-2_amd64.deb) and it works fine.
>
> A diff shows no difference between the kernel configs except the
> earlier one has CONFIG_INPUT_MOUSEDEV_PSAUX_ENABLE=y and the new one
> doesn't contain this line.
>
> The motherboard is MSI K8T Master2 FAR (VIA K8T800/VT8237) with
> 2 x Opteron 240, 2 x 512MB RAM with chip-kill ECC enabled.
>
> Anyone got any ideas why this is happening?
>
> Regards,
> John
--
________________________________________________________________________________
Monika Strack
Institut fuer Tierzucht
Bundesforschungsanstalt fuer Landwirtschaft
31535 Neustadt e-mail: most@tzv.fal.de
Germany Tel: +49 5034 /871 154
Fax: +49 5034 /871 239
_______________________________________________________________________________
Reply to: