GNU bug report logs - #40396
linux-libre - BUG: Bad page state in process

Previous Next

Package: guix;

Reported by: lle-bout <at> zaclys.net (Léo Le Bouter)

Date: Thu, 2 Apr 2020 23:38:02 UTC

Severity: normal

Done: Leo Famulari <leo <at> famulari.name>

Bug is archived. No further changes may be made.

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 40396 in the body.
You can then email your comments to 40396 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox

Report forwarded to bug-guix <at> gnu.org:
bug#40396; Package guix. (Thu, 02 Apr 2020 23:38:02 GMT) Full text and rfc822 format available.
Acknowledgement sent to lle-bout <at> zaclys.net (Léo Le Bouter):
New bug report received and forwarded. Copy sent to bug-guix <at> gnu.org. (Thu, 02 Apr 2020 23:38:02 GMT) Full text and rfc822 format available.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: lle-bout <at> zaclys.net (Léo Le Bouter)
To: bug-guix <at> gnu.org
Subject: linux-libre - BUG: Bad page state in process
Date: Fri, 03 Apr 2020 01:23:05 +0200

[Message part 1 (text/plain, inline)]
Hello,

I've been seeing many of those:

> BUG: Bad page state in process <process_name>

in my `dmesg` logs.

After few of them, my whole machine freezes and I need to reboot.
RAM is not faulty, but other hardware could be, not sure.

I'm confused what the cause of this bug is, all information I could find
online does not mention causes or is about all sort of causes, for the
same bug message.

`dmesg` log :


[dmesg_bug_1 (text/plain, attachment)]
[Message part 3 (text/plain, inline)]
Another.. :


[dmesg_fault_1 (text/plain, attachment)]
[Message part 5 (text/plain, inline)]
Thanks
Information forwarded to bug-guix <at> gnu.org:
bug#40396; Package guix. (Sat, 04 Apr 2020 00:03:02 GMT) Full text and rfc822 format available.

Message #8 received at 40396 <at> debbugs.gnu.org (full text, mbox):

From: Leo Le Bouter <lle-bout <at> zaclys.net>
To: lle-bout <at> zaclys.net
Cc: 40396 <at> debbugs.gnu.org
Subject: Re: bug#40396: linux-libre - BUG: Bad page state in process
Date: Sat, 04 Apr 2020 00:02:33 +0200

[Message part 1 (text/plain, inline)]
Memory may be faulty after all. I ran a memtest86+ and it shows errors,
usermode memtester did not. 

This can be closed!
[Message part 2 (text/html, inline)]
Reply sent to Leo Famulari <leo <at> famulari.name>:
You have taken responsibility. (Sat, 04 Apr 2020 03:35:01 GMT) Full text and rfc822 format available.
Notification sent to lle-bout <at> zaclys.net (Léo Le Bouter):
bug acknowledged by developer. (Sat, 04 Apr 2020 03:35:02 GMT) Full text and rfc822 format available.

Message #13 received at 40396-done <at> debbugs.gnu.org (full text, mbox):

From: Leo Famulari <leo <at> famulari.name>
To: Leo Le Bouter <lle-bout <at> zaclys.net>
Cc: 40396-done <at> debbugs.gnu.org
Subject: Re: bug#40396: linux-libre - BUG: Bad page state in process
Date: Fri, 3 Apr 2020 23:34:09 -0400

On Sat, Apr 04, 2020 at 12:02:33AM +0200, Leo Le Bouter via Bug reports for GNU Guix wrote:
> Memory may be faulty after all. I ran a memtest86+ and it shows errors,
> usermode memtester did not.
> 
> This can be closed!

Okay, let us know if you keep having trouble after replacing the memory
module.
bug archived. Request was from Debbugs Internal Request <help-debbugs <at> gnu.org> to internal_control <at> debbugs.gnu.org. (Sat, 02 May 2020 11:24:07 GMT) Full text and rfc822 format available.
This bug report was last modified 5 years and 127 days ago.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.