linux-kernel - Re: [REGRESSION] 2.6.25 on parisc

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1208789018.3640.6.camel@localhost.localdomain>
Date:	Mon, 21 Apr 2008 09:43:38 -0500
From:	James Bottomley <James.Bottomley@...senPartnership.com>
To:	Domenico Andreoli <cavokz@...il.com>
Cc:	Kernel Mailing List <linux-kernel@...r.kernel.org>,
	linux-parisc@...r.kernel.org
Subject: Re: [REGRESSION] 2.6.25 on parisc - CPU 1 is stuck

On Mon, 2008-04-21 at 01:18 +0200, Domenico Andreoli wrote: 
> as soon as I booted my dual PA8600 with 2.6.25 I got 1 CPU less. The
> only other kernel I successfully used on that box is Debian's 2.6.22-3.
> 
> Debian never built 2.6.23 for parisc, 2.6.24 was still hanging last
> time I checked it, 2.6.25 did not even build until recent -rc. So I am
> not in the best position to bisect.

Try this one; it's a corrected version of debian 2.6.24-1 for parisc
systems:

http://www.parisc-linux.org/~jejb/parisc_debs/linux-image-2.6.24-1-parisc64-smp_2.6.24-5+b1_hppa.deb

It's known to boot correctly on B, A and rp3440 systems, but we don't
have a J system to try it out on.

> Here is the relevant dmesg.
> Releasing cpu 1 now, hpa=fffffffffffa2000
> SMP: CPU:1 is stuck.
> CPU(s): 2 x PA8600 (PCX-W+) at 552.000000 MHz
> Setting cache flush threshold to f84c0 (1 CPUs online)

Unfortunately that doesn't tell us anything other than the start IPI
failed for some reason.  One thing to try with the J series is a 32 bit
kernel just in case: they're the only SMP systems that will boot 32
bits, just in case you could try a 32 bit smp kernel.

As Dave Anglin said, it could be a config problem, although when I have
CPUs deconfigured by firmware, they usually don't show up in the
inventory.

James

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/