LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Debian
User Name
Password
Debian This forum is for the discussion of Debian Linux.

Notices

Reply
 
Search this Thread
Old 09-19-2006, 06:04 PM   #1
kmoffat
Member
 
Registered: Jul 2003
Location: near Seattle
Distribution: Debian/Ubuntu/Suse
Posts: 240
Blog Entries: 2

Rep: Reputation: 30
'Bad page state' error?


The following (or something similar) shows up now and then in my xterm when running debian etch with gnome:

Code:
ken@noisy:~$
Message from syslogd@drip23 at Tue Sep 19 15:55:03 2006 ...
drip23 kernel: page:b126e9c0 flags:0x80000000 mapping:00000020 mapcount:0 count:0

Message from syslogd@drip23 at Tue Sep 19 15:55:03 2006 ...
drip23 kernel: Trying to fix it up, but a reboot is needed

Message from syslogd@drip23 at Tue Sep 19 15:55:03 2006 ...
drip23 kernel: Backtrace:

Message from syslogd@drip23 at Tue Sep 19 15:55:03 2006 ...
drip23 kernel: Bad page state in process 'events/0'

Anyone have an idea what's going on here?
 
Old 09-22-2006, 06:40 AM   #2
basileus
Member
 
Registered: Nov 2004
Location: Turku, Finland
Distribution: Debian, Ubuntu, Gentoo
Posts: 388

Rep: Reputation: 30
Message from syslogd@drip23 at Tue Sep 19 15:55:03 2006 ...
drip23 kernel: Bad page state in process 'events/0'

Could this have something to do with some input device, like a touch, mouse, keyboard or something? That's my guess. I'd try changing to a different kernel if no obvious hardware flaw can be found.
 
Old 09-22-2006, 07:03 AM   #3
PTrenholme
Senior Member
 
Registered: Dec 2004
Location: Olympia, WA, USA
Distribution: Fedora, (K)Ubuntu
Posts: 4,147

Rep: Reputation: 330Reputation: 330Reputation: 330Reputation: 330
Not sure, but I believe that the "page" to which the message refers is a block of memory, so you might have a bad RAM chip set. Many "live" cd's include an option to boot memchk to test for memory problems. Some distribution installation CDs also give you an option to check your memory chip sets.

Note, however, that the checks can be quite time consuming. (I ran one once on a 1 Gb system, and it took half a day to isolate the problem.)

Another possibility is that your RAM is so small that your swap file is in use, and you've got a bad spot in the swap partition. If the memchk doesn't find any problem, try creating a different swap partition, and switching your system to use it. (This possibility is not very likely, since the disk hardware will ussually detect the problem before your swapped memory page is returned, and a different error message is generated. Often your system just "hangs" on disk I/O errors.)

Another possibility: Excessive heat in your system. Do you monitor you system using, e.g., GKrellM or a similar monitoring program?

Last edited by PTrenholme; 09-22-2006 at 07:04 AM.
 
Old 10-01-2006, 07:16 PM   #4
kmoffat
Member
 
Registered: Jul 2003
Location: near Seattle
Distribution: Debian/Ubuntu/Suse
Posts: 240
Blog Entries: 2

Original Poster
Rep: Reputation: 30
Sorry about the delay. I have gkrellm which reports no sensors found (may need to install something?). When I run mbmon (I think that's it, but I'm elsewhere now so not sure) it shows temps within acceptable limits. Maybe I'll run that all night, piped to a file. If a lock occurs I can see what the last temp was.

The mb is an old msi with an athlon t-bird, which runs warm, so I moved it out of my desk enclosure, which helps. Also, I recently replaced a dvd and cd-rw with a combo drive, but I don't think that would cause lock-ups.
 
Old 10-01-2006, 07:37 PM   #5
Dutch Master
Senior Member
 
Registered: Dec 2005
Posts: 1,673

Rep: Reputation: 122Reputation: 122
Try installing lm-sensors to get messages on the onboard sensors.
 
Old 10-01-2006, 08:24 PM   #6
kmoffat
Member
 
Registered: Jul 2003
Location: near Seattle
Distribution: Debian/Ubuntu/Suse
Posts: 240
Blog Entries: 2

Original Poster
Rep: Reputation: 30
Done, will experiment later, thanks.

EDIT;
well, when I call 'sensors' from the command line it shows:

# sensors
Can't access procfs/sysfs file
Unable to find i2c bus information;
For 2.6 kernels, make sure you have mounted sysfs and libsensors
was compiled with sysfs support!
For older kernels, make sure you have done 'modprobe i2c-proc'!

Last edited by kmoffat; 10-01-2006 at 08:57 PM.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Bad free_hot_cold page trainee Slackware 3 02-08-2006 11:28 AM
Bad page state at prep_new_page Curtux Mandriva 4 01-24-2006 05:56 AM
Bad page state at prep_new_page JimBass Linux - Newbie 2 08-18-2005 01:50 PM
RTL-8139 card left in bad state after Windows Hibernate andrewb758 Linux - Networking 3 06-25-2004 12:52 PM
Bad Request when web page loading wmartino Linux - Networking 2 09-14-2003 09:25 AM


All times are GMT -5. The time now is 11:05 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration