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] [day] [month] [year] [list]

Message-ID: <20080506163206.GA2211@ska.dandreoli.com>
Date:	Tue, 6 May 2008 18:32:06 +0200
From:	Domenico Andreoli <cavokz@...il.com>
To:	Kyle McMartin <kyle@...artin.ca>
Cc:	Grant Grundler <grundler@...isc-linux.org>,
	James Bottomley <James.Bottomley@...senPartnership.com>,
	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 Tue, Apr 22, 2008 at 08:54:38PM -0400, Kyle McMartin wrote:
> On Tue, Apr 22, 2008 at 06:44:40PM -0600, Grant Grundler wrote:
> > 
> > *nod* I don't expect CPUs to show up in inventory if they are
> > deconfigured in BCH. Maybe J-class firmware has this wrong? *shrug*
> > Something worth checking I guess.
> > 
> 
> i booted the kernel from my rp3440 on my j6000. i also get this cpu1 is
> stuck message. putting a panic in the SMP C-code entrypoint is never
> hit.
> 
> most oddly, putting a hpmc-causing insn sequence in the entry point
> doesn't trigger either, so the cpu isn't coming out of the rendezvous.
> 
> even more oddly, the stwa insn in the bring up code looks fine.

still nothing changed with 2.6.26-rc1-00110-ga153063

cheers,
Domenico

-----[ Domenico Andreoli, aka cavok
 --[ http://www.dandreoli.com/gpgkey.asc
   ---[ 3A0F 2F80 F79C 678A 8936  4FEE 0677 9033 A20E BC50
--
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/