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]

Date:	Tue, 22 Apr 2008 11:53:15 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Jiri Slaby <jirislaby@...il.com>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	"Rafael J. Wysocki" <rjw@...k.pl>, paulmck@...ux.vnet.ibm.com,
	David Miller <davem@...emloft.net>,
	linux-kernel@...r.kernel.org, akpm@...ux-foundation.org,
	linux-ext4@...r.kernel.org, herbert@...dor.apana.org.au,
	Zdenek Kabelac <zdenek.kabelac@...il.com>
Subject: Re: 2.6.25-git2: BUG: unable to handle kernel paging request at
	ffffffffffffffff


* Jiri Slaby <jirislaby@...il.com> wrote:

>> What do you do to trigger this? Any particular load? Is it still just 
>> doing suspend/resume, or do you have something else that you are 
>> playing with?
>
> Yesterday I did 2 suspend/resumes after 1 hour of uptime and ran 
> git-status for a fraction of a second until it was killed. So I can 
> perfectly reproduce it when I suspend, resume and produce some io 
> load. I guess it's time to bisect 2.6.25-rc8-mm2 as I'm able to 
> reproduce it the best and haven't seen that bug in -rc8-mm1 for over 
> week of suspending and working.

the most dangerous x86 change we added was the PAT stuff. Does it 
influence the crashes in any way if you boot with 'nopat' or if you 
disable CONFIG_X86_PAT=y into the .config?

the other area was the DMA ops change - that should be rather trivial on 
64-bit though.

	Ingo
--
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