linux-ext4 - Re: 2.6.25-git2: BUG: unable to handle kernel paging request at ffffffffffffffff

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: <48118EAB.5040004@gmail.com>
Date:	Fri, 25 Apr 2008 09:56:27 +0200
From:	Jiri Slaby <jirislaby@...il.com>
To:	David Miller <davem@...emloft.net>
CC:	torvalds@...ux-foundation.org, zdenek.kabelac@...il.com,
	mingo@...e.hu, rjw@...k.pl, paulmck@...ux.vnet.ibm.com,
	linux-kernel@...r.kernel.org, akpm@...ux-foundation.org,
	linux-ext4@...r.kernel.org, herbert@...dor.apana.org.au,
	penberg@...helsinki.fi, clameter@....com
Subject: Re: 2.6.25-git2: BUG: unable to handle kernel paging request at ffffffffffffffff

On 04/25/2008 09:49 AM, David Miller wrote:
> From: Jiri Slaby <jirislaby@...il.com>
> Date: Fri, 25 Apr 2008 09:42:43 +0200
> 
>> On 04/25/2008 03:35 AM, David Miller wrote:
>>> From: Jiri Slaby <jirislaby@...il.com>
>>> Date: Fri, 25 Apr 2008 00:26:18 +0200
>>>
>>>> ff00aa00deadcc22 ff00aa00deadcc22 ff00aa00deadcc22 ff00aa00deadccf0 
>>> 0xf0...  Is this a 4-cpu machine?
>> It's a 2 cores machine.
> 
> Two hyperthreads per-core?

Hmm, how to find out? I suppose it will show up 4 (virtual) processors in 
cpuinfo, right? Although there is ht bit in cpuinfo on each core and 
CONFIG_X86_HT=y, I don't see 4 cpus.

> If so that could match up to the pattern.  It is just one theory
> though.  The wireless possibility holds just as much weight.

The mac80211 is theory too so far :).


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