Discussion:
Logs and dumps for kernel panics to collect and analyze?
(too old to reply)
Ant
2010-03-06 07:12:30 UTC
Permalink
Hello.

Is /var/log/syslog the only place where Linux keeps records of kernel
(v2.6.30 and v2.6.32) panics? dmesg and /var/log/messages doesn't seem
to show anything about the crashes unless I am misreading them. I am
trying to figure out a rare and random kernel panic issue on my old
Debian box.

I know it's not X because I exited it, logged out of bash, went into
fullscreen text console's login screen (I boot up my Debian to text
mode, log into bash, and use startx command to go to X), and saw a bunch
of datas (e.g., memory addresses and codes) on my screen from the kernel
crash. However, its data dump was too long and my computer was in frozen
mode with two blinking PS/2 keyboard lights (caps and scroll lock) so I
couldn't scroll up or copy and paste.

I poked around in my Debian and on the Web. I read that kernel panic
errors/datas can be found in /var/log/syslog (dmesg didn't show me
anything related to Kernel panics that I could find) like:

# cat /var/log/syslog
...
Mar 4 23:12:07 foobar smartd[2647]: Device: /dev/hda, SMART Usage
Attribute: 194 Temperature_Celsius changed from 30 to 31
...
Mar 5 15:11:31 foobar smartd[2610]: Device: /dev/hda, SMART Prefailure
Attribute: 1 Raw_Read_Error_Rate changed from 58 to 59
Mar 5 15:11:31 foobar smartd[2610]: Device: /dev/hda, SMART Usage
Attribute: 195 Hardware_ECC_Recovered changed from 58 to 59
Mar 5 15:15:01 foobar /USR/SBIN/CRON[8815]: (root) CMD (command -v
debian-sa1 > /dev/null && debian-sa1 1 1)
Mar 5 15:17:01 foobar /USR/SBIN/CRON[11199]: (root) CMD ( cd / &&
run-parts --report /etc/cron.hourly)
Mar 5 15:25:01 foobar /USR/SBIN/CRON[20721]: (root) CMD (command -v
debian-sa1 > /dev/null && debian-sa1 1 1)
Mar 5 15:35:01 foobar /USR/SBIN/CRON[32588]: (root) CMD (command -v
debian-sa1 > /dev/null && debian-sa1 1 1)
Mar 5 15:45:01 foobar /USR/SBIN/CRON[12129]: (root) CMD (command -v
debian-sa1 > /dev/null && debian-sa1 1 1)
Mar 5 15:55:01 foobar /USR/SBIN/CRON[23947]: (root) CMD (command -v
debian-sa1 > /dev/null && debian-sa1 1 1)
< rebooted my crashed PC from its kernel panic >
Mar 5 21:05:19 foobar syslogd 1.5.0#5: restart.
...

I couldn't find any similiar from an earlier one like (don't think
smartctl with /dev/hda is it?):
...
Mar 5 05:17:01 foobar /USR/SBIN/CRON[26833]: (root) CMD ( cd / &&
run-parts --report /etc/cron.hourly)
Mar 5 05:25:01 foobar /USR/SBIN/CRON[29514]: (root) CMD (command -v
debian-sa1 > /dev/null && debian-sa1 1 1)
Mar 5 05:35:01 foobar /USR/SBIN/CRON[372]: (root) CMD (command -v
debian-sa1 > /dev/null && debian-sa1 1 1)
Mar 5 05:45:01 foobar /USR/SBIN/CRON[3772]: (root) CMD (command -v
debian-sa1 > /dev/null && debian-sa1 1 1)
Mar 5 05:55:01 foobar /USR/SBIN/CRON[7160]: (root) CMD (command -v
debian-sa1 > /dev/null && debian-sa1 1 1)
Mar 5 06:41:19 foobar syslogd 1.5.0#5: restart.
...

I saw LKCD (http://lkcd.sourceforge.net/ and
http://sourceforge.net/projects/lkcd/files/), but it seems to be
outdated? I also couldn't find a Debian package of it, so I don't know
if I should even try it to get more datas.

And yes, I already tried memtest86+ v4.00 and it came out no errors
after six hours with its default tests. I will try it again later just
in case.

Thank you in advance. :)
--
"If I find one beer can in that car, it's over!" --Red; "And no donuts
either! Ants!" --Kitty from That '70s Show pilot
/\___/\
/ /\ /\ \ Phil./Ant @ http://antfarm.ma.cx (Personal Web Site)
| |o o| | Ant's Quality Foraged Links: http://aqfl.net
\ _ / Nuke ANT from e-mail address: ***@earthlink.netANT
( ) or ***@zimage.com
Ant is currently not listening to any songs on his home computer.
Mark Hobley
2010-03-06 10:08:02 UTC
Permalink
Post by Ant
Is /var/log/syslog the only place where Linux keeps records of kernel
(v2.6.30 and v2.6.32) panics? dmesg and /var/log/messages doesn't seem
to show anything about the crashes unless I am misreading them. I am
trying to figure out a rare and random kernel panic issue on my old
Debian box.
Is it a panic, or is it a crash?
Post by Ant
I know it's not X because I exited it, logged out of bash, went into
fullscreen text console's login screen (I boot up my Debian to text
mode, log into bash, and use startx command to go to X), and saw a bunch
of datas (e.g., memory addresses and codes) on my screen from the kernel
crash.
What type of computer are you using? What type of CPU does it have?
There are some issues with invalid instructions being embedded into the kernel
which causes a similar problem on IA32 compatible machines. (A 486 build
contains non-IA32 instructions).

Write down what you see, and lose the rest. The information does not get
logged.

Mark.
--
Mark Hobley
Linux User: #370818 http://markhobley.yi.org/
Ant
2010-03-06 15:33:12 UTC
Permalink
Post by Mark Hobley
Post by Ant
Is /var/log/syslog the only place where Linux keeps records of kernel
(v2.6.30 and v2.6.32) panics? dmesg and /var/log/messages doesn't seem
to show anything about the crashes unless I am misreading them. I am
trying to figure out a rare and random kernel panic issue on my old
Debian box.
Is it a panic, or is it a crash?
Panic since my box frozen, required a reboot, and had flashing keyboard
lights.
Post by Mark Hobley
Post by Ant
I know it's not X because I exited it, logged out of bash, went into
fullscreen text console's login screen (I boot up my Debian to text
mode, log into bash, and use startx command to go to X), and saw a bunch
of datas (e.g., memory addresses and codes) on my screen from the kernel
crash.
What type of computer are you using? What type of CPU does it have?
There are some issues with invalid instructions being embedded into the kernel
which causes a similar problem on IA32 compatible machines. (A 486 build
contains non-IA32 instructions).
http://alpha.zimage.com/~ant/antfarm/about/computers.txt for my
secondary computer specifications. I am currently using 2.6.32-trunk-686
#1 SMP Sun Jan 10 06:32:16 UTC 2010 i686 GNU/Linux. I was using 2.6.30
too and it had the same problem.
Post by Mark Hobley
Write down what you see, and lose the rest. The information does not get
logged.
Darn. That's a lot stuff to write down.
--
"To the ant, a few drops of dew is a flood." --Iranian
/\___/\
/ /\ /\ \ Phil./Ant @ http://antfarm.ma.cx (Personal Web Site)
| |o o| | Ant's Quality Foraged Links: http://aqfl.net
\ _ / Nuke ANT from e-mail address: ***@earthlink.netANT
( ) or ***@zimage.com
Ant is currently not listening to any songs on his home computer.
Ant
2010-03-06 17:05:12 UTC
Permalink
Uh oh. I just discovered mcelog and something new and scary in its
/var/log/syslog:

Mar 6 01:19:37 foobar kernel: [15299.988025] Machine check events logged
Mar 6 01:42:07 foobar kernel: [16649.989021] Machine check events logged
Mar 6 02:05:19 foobar -- MARK --
Mar 6 02:19:37 foobar kernel: [18899.989024] Machine check events logged
Mar 6 02:37:07 foobar kernel: [19949.988027] Machine check events logged
Mar 6 03:05:19 foobar -- MARK --
Mar 6 03:24:37 foobar kernel: [22799.989023] Machine check events logged
Mar 6 03:45:19 foobar -- MARK --
Mar 6 04:05:19 foobar -- MARK --
Mar 6 04:25:19 foobar -- MARK --
Mar 6 04:45:19 foobar -- MARK --
Mar 6 05:02:07 foobar kernel: [28649.989023] Machine check events logged
Mar 6 05:25:19 foobar -- MARK --
Mar 6 05:45:19 foobar -- MARK --
Mar 6 06:05:19 foobar -- MARK --
Mar 6 06:24:37 foobar kernel: [33599.989027] Machine check events logged
Mar 6 06:33:13 foobar syslogd 1.5.0#5: restart.
Mar 6 06:45:19 foobar -- MARK --
Mar 6 07:05:19 foobar -- MARK --
Mar 6 07:25:19 foobar -- MARK --
Mar 6 07:45:19 foobar -- MARK --
Mar 6 08:05:19 foobar -- MARK --
Mar 6 08:17:07 foobar kernel: [40349.989022] Machine check events logged
Mar 6 08:24:37 foobar kernel: [40799.988036] Machine check events logged
Mar 6 08:45:19 foobar -- MARK --
Mar 6 08:52:09 foobar mcelog: HARDWARE ERROR. This is *NOT* a software
problem!
Mar 6 08:52:09 foobar mcelog: Please contact your hardware vendor
Mar 6 08:52:09 foobar mcelog: MCE 0
Mar 6 08:52:09 foobar mcelog: CPU 1 1 instruction cache
Mar 6 08:52:09 foobar mcelog: ADDR c11b6ff0
Mar 6 08:52:09 foobar mcelog: TIME 1267894329 Sat Mar 6 08:52:09 2010
Mar 6 08:52:09 foobar mcelog: TLB parity error in virtual array
Mar 6 08:52:09 foobar mcelog: TLB error 'instruction transaction,
level 1'
Mar 6 08:52:09 foobar mcelog: STATUS 9400000000010011 MCGSTATUS 0
Mar 6 08:52:09 foobar mcelog: MCGCAP 105 APICID 1 SOCKETID 0
Mar 6 08:52:09 foobar mcelog: CPUID Vendor AMD Family 15 Model 43
Mar 6 08:52:09 foobar mcelog: HARDWARE ERROR. This is *NOT* a software
problem!
Mar 6 08:52:09 foobar mcelog: Please contact your hardware vendor
Mar 6 08:52:09 foobar mcelog: MCE 1
Mar 6 08:52:09 foobar mcelog: CPU 1 1 instruction cache
Mar 6 08:52:09 foobar mcelog: ADDR c11b6ff0
Mar 6 08:52:09 foobar mcelog: TIME 1267894329 Sat Mar 6 08:52:09 2010
Mar 6 08:52:09 foobar mcelog: TLB parity error in virtual array
Mar 6 08:52:09 foobar mcelog: TLB error 'instruction transaction,
level 1'
Mar 6 08:52:09 foobar mcelog: STATUS 9400000000010011 MCGSTATUS 0
Mar 6 08:52:09 foobar mcelog: MCGCAP 105 APICID 1 SOCKETID 0
Mar 6 08:52:09 foobar mcelog: CPUID Vendor AMD Family 15 Model 43
Mar 6 08:52:09 foobar mcelog: HARDWARE ERROR. This is *NOT* a software
problem!
Mar 6 08:52:09 foobar mcelog: Please contact your hardware vendor
Mar 6 08:52:09 foobar mcelog: MCE 2
Mar 6 08:52:09 foobar mcelog: CPU 1 1 instruction cache
Mar 6 08:52:09 foobar mcelog: ADDR c11b6ff0
Mar 6 08:52:09 foobar mcelog: TIME 1267894329 Sat Mar 6 08:52:09 2010
Mar 6 08:52:09 foobar mcelog: TLB parity error in virtual array
Mar 6 08:52:09 foobar mcelog: TLB error 'instruction transaction,
level 1'
Mar 6 08:52:09 foobar mcelog: STATUS 9400000000010011 MCGSTATUS 0
Mar 6 08:52:09 foobar mcelog: MCGCAP 105 APICID 1 SOCKETID 0
Mar 6 08:52:09 foobar mcelog: CPUID Vendor AMD Family 15 Model 43
Mar 6 08:52:09 foobar mcelog: HARDWARE ERROR. This is *NOT* a software
problem!
Mar 6 08:52:09 foobar mcelog: Please contact your hardware vendor
Mar 6 08:52:09 foobar mcelog: MCE 3
Mar 6 08:52:09 foobar mcelog: CPU 1 1 instruction cache
Mar 6 08:52:09 foobar mcelog: ADDR c11b6ff0
Mar 6 08:52:09 foobar mcelog: TIME 1267894329 Sat Mar 6 08:52:09 2010
Mar 6 08:52:09 foobar mcelog: TLB parity error in virtual array
Mar 6 08:52:09 foobar mcelog: TLB error 'instruction transaction,
level 1'
Mar 6 08:52:09 foobar mcelog: STATUS 9400000000010011 MCGSTATUS 0
Mar 6 08:52:09 foobar mcelog: MCGCAP 105 APICID 1 SOCKETID 0
Mar 6 08:52:09 foobar mcelog: CPUID Vendor AMD Family 15 Model 43
Mar 6 08:52:09 foobar mcelog: HARDWARE ERROR. This is *NOT* a software
problem!
Mar 6 08:52:09 foobar mcelog: Please contact your hardware vendor
Mar 6 08:52:09 foobar mcelog: MCE 4
Mar 6 08:52:09 foobar mcelog: CPU 1 1 instruction cache
Mar 6 08:52:09 foobar mcelog: ADDR c11b6ff0
Mar 6 08:52:09 foobar mcelog: TIME 1267894329 Sat Mar 6 08:52:09 2010
Mar 6 08:52:09 foobar mcelog: TLB parity error in virtual array
Mar 6 08:52:09 foobar mcelog: TLB error 'instruction transaction,
level 1'
Mar 6 08:52:09 foobar mcelog: STATUS 9400000000010011 MCGSTATUS 0
Mar 6 08:52:09 foobar mcelog: MCGCAP 105 APICID 1 SOCKETID 0
Mar 6 08:52:09 foobar mcelog: CPUID Vendor AMD Family 15 Model 43
Mar 6 08:52:09 foobar mcelog: HARDWARE ERROR. This is *NOT* a software
problem!
Mar 6 08:52:09 foobar mcelog: Please contact your hardware vendor
Mar 6 08:52:09 foobar mcelog: MCE 5
Mar 6 08:52:09 foobar mcelog: CPU 1 1 instruction cache
Mar 6 08:52:09 foobar mcelog: ADDR c11b6ff0
Mar 6 08:52:09 foobar mcelog: TIME 1267894329 Sat Mar 6 08:52:09 2010
Mar 6 08:52:09 foobar mcelog: TLB parity error in virtual array
Mar 6 08:52:09 foobar mcelog: TLB error 'instruction transaction,
level 1'
Mar 6 08:52:09 foobar mcelog: STATUS 9400000000010011 MCGSTATUS 0
Mar 6 08:52:09 foobar mcelog: MCGCAP 105 APICID 1 SOCKETID 0
Mar 6 08:52:09 foobar mcelog: CPUID Vendor AMD Family 15 Model 43
Mar 6 08:52:09 foobar mcelog: HARDWARE ERROR. This is *NOT* a software
problem!
Mar 6 08:52:09 foobar mcelog: Please contact your hardware vendor
Mar 6 08:52:09 foobar mcelog: MCE 6
Mar 6 08:52:09 foobar mcelog: CPU 1 1 instruction cache
Mar 6 08:52:09 foobar mcelog: ADDR c11b6ff0
Mar 6 08:52:09 foobar mcelog: TIME 1267894329 Sat Mar 6 08:52:09 2010
Mar 6 08:52:09 foobar mcelog: TLB parity error in virtual array
Mar 6 08:52:09 foobar mcelog: TLB error 'instruction transaction,
level 1'
Mar 6 08:52:09 foobar mcelog: STATUS 9400000000010011 MCGSTATUS 0
Mar 6 08:52:09 foobar mcelog: MCGCAP 105 APICID 1 SOCKETID 0
Mar 6 08:52:09 foobar mcelog: CPUID Vendor AMD Family 15 Model 43
Mar 6 08:52:09 foobar mcelog: HARDWARE ERROR. This is *NOT* a software
problem!
Mar 6 08:52:09 foobar mcelog: Please contact your hardware vendor
Mar 6 08:52:09 foobar mcelog: MCE 7
Mar 6 08:52:09 foobar mcelog: CPU 1 1 instruction cache
Mar 6 08:52:09 foobar mcelog: ADDR c11b6ff0
Mar 6 08:52:09 foobar mcelog: TIME 1267894329 Sat Mar 6 08:52:09 2010
Mar 6 08:52:09 foobar mcelog: TLB parity error in virtual array
Mar 6 08:52:09 foobar mcelog: TLB error 'instruction transaction,
level 1'
Mar 6 08:52:09 foobar mcelog: STATUS 9400000000010011 MCGSTATUS 0
Mar 6 08:52:09 foobar mcelog: MCGCAP 105 APICID 1 SOCKETID 0
Mar 6 08:52:09 foobar mcelog: CPUID Vendor AMD Family 15 Model 43
Mar 6 08:52:09 foobar mcelog: HARDWARE ERROR. This is *NOT* a software
problem!
Mar 6 08:52:09 foobar mcelog: Please contact your hardware vendor
Mar 6 08:52:09 foobar mcelog: MCE 8
Mar 6 08:52:09 foobar mcelog: CPU 1 1 instruction cache
Mar 6 08:52:09 foobar mcelog: ADDR c11b6ff0
Mar 6 08:52:09 foobar mcelog: TIME 1267894329 Sat Mar 6 08:52:09 2010
Mar 6 08:52:09 foobar mcelog: TLB parity error in virtual array
Mar 6 08:52:09 foobar mcelog: TLB error 'instruction transaction,
level 1'
Mar 6 08:52:09 foobar mcelog: STATUS 9400000000010011 MCGSTATUS 0
Mar 6 08:52:09 foobar mcelog: MCGCAP 105 APICID 1 SOCKETID 0
Mar 6 08:52:09 foobar mcelog: CPUID Vendor AMD Family 15 Model 43


What does that mean? Dying CPU (had it since 12/24/2006)? Maybe that's
why memtest86+ didn't find any problems last week.
Post by Ant
Hello.
Is /var/log/syslog the only place where Linux keeps records of kernel
(v2.6.30 and v2.6.32) panics? dmesg and /var/log/messages doesn't seem
to show anything about the crashes unless I am misreading them. I am
trying to figure out a rare and random kernel panic issue on my old
Debian box.
I know it's not X because I exited it, logged out of bash, went into
fullscreen text console's login screen (I boot up my Debian to text
mode, log into bash, and use startx command to go to X), and saw a bunch
of datas (e.g., memory addresses and codes) on my screen from the kernel
crash. However, its data dump was too long and my computer was in frozen
mode with two blinking PS/2 keyboard lights (caps and scroll lock) so I
couldn't scroll up or copy and paste.
I poked around in my Debian and on the Web. I read that kernel panic
errors/datas can be found in /var/log/syslog (dmesg didn't show me
# cat /var/log/syslog
...
Mar 4 23:12:07 foobar smartd[2647]: Device: /dev/hda, SMART Usage
Attribute: 194 Temperature_Celsius changed from 30 to 31
...
Mar 5 15:11:31 foobar smartd[2610]: Device: /dev/hda, SMART Prefailure
Attribute: 1 Raw_Read_Error_Rate changed from 58 to 59
Mar 5 15:11:31 foobar smartd[2610]: Device: /dev/hda, SMART Usage
Attribute: 195 Hardware_ECC_Recovered changed from 58 to 59
Mar 5 15:15:01 foobar /USR/SBIN/CRON[8815]: (root) CMD (command -v
debian-sa1 > /dev/null && debian-sa1 1 1)
Mar 5 15:17:01 foobar /USR/SBIN/CRON[11199]: (root) CMD ( cd / &&
run-parts --report /etc/cron.hourly)
Mar 5 15:25:01 foobar /USR/SBIN/CRON[20721]: (root) CMD (command -v
debian-sa1 > /dev/null && debian-sa1 1 1)
Mar 5 15:35:01 foobar /USR/SBIN/CRON[32588]: (root) CMD (command -v
debian-sa1 > /dev/null && debian-sa1 1 1)
Mar 5 15:45:01 foobar /USR/SBIN/CRON[12129]: (root) CMD (command -v
debian-sa1 > /dev/null && debian-sa1 1 1)
Mar 5 15:55:01 foobar /USR/SBIN/CRON[23947]: (root) CMD (command -v
debian-sa1 > /dev/null && debian-sa1 1 1)
< rebooted my crashed PC from its kernel panic >
Mar 5 21:05:19 foobar syslogd 1.5.0#5: restart.
...
I couldn't find any similiar from an earlier one like (don't think
...
Mar 5 05:17:01 foobar /USR/SBIN/CRON[26833]: (root) CMD ( cd / &&
run-parts --report /etc/cron.hourly)
Mar 5 05:25:01 foobar /USR/SBIN/CRON[29514]: (root) CMD (command -v
debian-sa1 > /dev/null && debian-sa1 1 1)
Mar 5 05:35:01 foobar /USR/SBIN/CRON[372]: (root) CMD (command -v
debian-sa1 > /dev/null && debian-sa1 1 1)
Mar 5 05:45:01 foobar /USR/SBIN/CRON[3772]: (root) CMD (command -v
debian-sa1 > /dev/null && debian-sa1 1 1)
Mar 5 05:55:01 foobar /USR/SBIN/CRON[7160]: (root) CMD (command -v
debian-sa1 > /dev/null && debian-sa1 1 1)
Mar 5 06:41:19 foobar syslogd 1.5.0#5: restart.
...
I saw LKCD (http://lkcd.sourceforge.net/ and
http://sourceforge.net/projects/lkcd/files/), but it seems to be
outdated? I also couldn't find a Debian package of it, so I don't know
if I should even try it to get more datas.
And yes, I already tried memtest86+ v4.00 and it came out no errors
after six hours with its default tests. I will try it again later just
in case.
Thank you in advance. :)
--
"What is it going to be like in eternity with God? Frankly, the capacity
of our brains cannot handle the wonder and greatness of heaven. It would
be like trying to describe the Internet to an ant." --Rick Warren's
book, The Purpose Driven Life
/\___/\
/ /\ /\ \ Phil./Ant @ http://antfarm.ma.cx (Personal Web Site)
| |o o| | Ant's Quality Foraged Links: http://aqfl.net
\ _ / Nuke ANT from e-mail address: ***@earthlink.netANT
( ) or ***@zimage.com
Ant is currently not listening to any songs on his home computer.
Darren Salt
2010-03-06 22:13:12 UTC
Permalink
I demand that Ant may or may not have written...
Post by Ant
Uh oh. I just discovered mcelog and something new and scary in its
[snip]
Post by Ant
Mar 6 08:24:37 foobar kernel: [40799.988036] Machine check events logged
Mar 6 08:45:19 foobar -- MARK --
Mar 6 08:52:09 foobar mcelog: HARDWARE ERROR. This is *NOT* a software
problem!
Mar 6 08:52:09 foobar mcelog: Please contact your hardware vendor
Mar 6 08:52:09 foobar mcelog: MCE 0
Mar 6 08:52:09 foobar mcelog: CPU 1 1 instruction cache
Mar 6 08:52:09 foobar mcelog: ADDR c11b6ff0
Mar 6 08:52:09 foobar mcelog: TIME 1267894329 Sat Mar 6 08:52:09 2010
Mar 6 08:52:09 foobar mcelog: TLB parity error in virtual array
Mar 6 08:52:09 foobar mcelog: TLB error 'instruction transaction,
level 1'
Mar 6 08:52:09 foobar mcelog: STATUS 9400000000010011 MCGSTATUS 0
Mar 6 08:52:09 foobar mcelog: MCGCAP 105 APICID 1 SOCKETID 0
Mar 6 08:52:09 foobar mcelog: CPUID Vendor AMD Family 15 Model 43
[snip duplicate entries]

Ouch.
Post by Ant
What does that mean? Dying CPU (had it since 12/24/2006)?
12/12/2007? ;-)

(Hint: use ISO8601 date formats or use month names. Broken-endian dates can
all too easily cause error; fortunately, that one's unambiguous.)

Anyway, it does look like a fault in that CPU. I'd certainly be considering
replacing it, though due to your earlier mention of kernel panics, I wouldn't
rule out board problems either; are there any visible signs of hardware
problems (leaky/bulging capacitors etc.)? Checking the PSU is probably also
worthwhile.

(http://en.wikipedia.org/wiki/Translation_lookaside_buffer describes the
affected area of the CPU.)
Post by Ant
Maybe that's why memtest86+ didn't find any problems last week.
That doesn't seem to be relevant.
(And that one hasn't happened yet.)
Post by Ant
Post by Ant
Is /var/log/syslog the only place where Linux keeps records of kernel
(v2.6.30 and v2.6.32) panics? dmesg and /var/log/messages doesn't seem to
show anything about the crashes unless I am misreading them. I am trying
to figure out a rare and random kernel panic issue on my old Debian box.
http://www.mjmwired.net/kernel/Documentation/networking/netconsole.txt

That needs a second computer, but it will at least allow most panics to be
captured. (Exceptions include hard hangs, where there may be no panic which
can be reported, and problems which affect the network interface over which
the log is being sent.)

[snip]
--
| Darren Salt | linux at youmustbejoking | nr. Ashington, | Doon
| using Debian GNU/Linux | or ds ,demon,co,uk | Northumberland | Army
| + They're after you...

I'd like to, but I'm going to count the bristles in my toothbrush.
Ant
2010-03-07 08:13:24 UTC
Permalink
Post by Darren Salt
Post by Ant
Uh oh. I just discovered mcelog and something new and scary in its
[snip]
Post by Ant
Mar 6 08:24:37 foobar kernel: [40799.988036] Machine check events logged
Mar 6 08:45:19 foobar -- MARK --
Mar 6 08:52:09 foobar mcelog: HARDWARE ERROR. This is *NOT* a software
problem!
Mar 6 08:52:09 foobar mcelog: Please contact your hardware vendor
Mar 6 08:52:09 foobar mcelog: MCE 0
Mar 6 08:52:09 foobar mcelog: CPU 1 1 instruction cache
Mar 6 08:52:09 foobar mcelog: ADDR c11b6ff0
Mar 6 08:52:09 foobar mcelog: TIME 1267894329 Sat Mar 6 08:52:09 2010
Mar 6 08:52:09 foobar mcelog: TLB parity error in virtual array
Mar 6 08:52:09 foobar mcelog: TLB error 'instruction transaction,
level 1'
Mar 6 08:52:09 foobar mcelog: STATUS 9400000000010011 MCGSTATUS 0
Mar 6 08:52:09 foobar mcelog: MCGCAP 105 APICID 1 SOCKETID 0
Mar 6 08:52:09 foobar mcelog: CPUID Vendor AMD Family 15 Model 43
[snip duplicate entries]
Ouch.
:(
Post by Darren Salt
Post by Ant
What does that mean? Dying CPU (had it since 12/24/2006)?
12/12/2007? ;-)
Eh?
Post by Darren Salt
(Hint: use ISO8601 date formats or use month names. Broken-endian dates can
all too easily cause error; fortunately, that one's unambiguous.)
I don't get it. :(
Post by Darren Salt
Anyway, it does look like a fault in that CPU. I'd certainly be considering
replacing it, though due to your earlier mention of kernel panics, I wouldn't
rule out board problems either; are there any visible signs of hardware
problems (leaky/bulging capacitors etc.)? Checking the PSU is probably also
worthwhile.
Hmmm, I just swapped my PSU because the old one (FSP650-80GLC PSU (650
watts) from 5/14/2007) died on 12/2009. I recalled days before,
something smelled burning but I couldn't figure out where it came from
since I had two desktops. I guess it was the PSU that went poof!

At the same time, my EVGA GeForce 8800 GT video card had to be RMA'ed
since it didn't work anymore since the new PSU still wouldn't boot the
box up at all. After getting a RMA'ed refurbished video card back, my
box was fine for a bit and then got kernel panics once in a while. Then,
it seems to become more frequently slowly. One day in February, I ran
memtest86+ v4.00 for like five hours and found lots of errors. My friend
and I narrowed it down to a 512 MB RAM and left with 2.5 GB remaining
(still plenty for an old Linux workstation!). Oh and we didn't see
anything burned, busted, etc.

It sounds like that PSU bust damaged a lot of my hardwares. Argh! I
don't have the time and resources to build another one (guess I could do
a clean install with it too :P). :(
Post by Darren Salt
(http://en.wikipedia.org/wiki/Translation_lookaside_buffer describes the
affected area of the CPU.)
Hmm, I wonder if that 512 MB RAM that memtest86 detected having errors
wasn't bad?
Post by Darren Salt
Post by Ant
Maybe that's why memtest86+ didn't find any problems last week.
That doesn't seem to be relevant.
Why do you say that? I am going to run it again soon to double check.
Post by Darren Salt
http://www.mjmwired.net/kernel/Documentation/networking/netconsole.txt
That needs a second computer, but it will at least allow most panics to be
captured. (Exceptions include hard hangs, where there may be no panic which
can be reported, and problems which affect the network interface over which
the log is being sent.)
Interesting. I wished Linux's Kernel panics would log to a file like
Windows' memory dumps from blue screens so I can use a debugger to see
what the dumps.
--
"Left right left right we're army ants. We swarm we fight. We have no
home. We roam. We race. You're lucky if we miss your place." --Douglas
Florian (The Army Ants Poem)
/\___/\
/ /\ /\ \ Phil./Ant @ http://antfarm.ma.cx (Personal Web Site)
| |o o| | Ant's Quality Foraged Links: http://aqfl.net
\ _ / Nuke ANT from e-mail address: ***@earthlink.netANT
( ) or ***@zimage.com
Ant is currently not listening to any songs on his home computer.
Darren Salt
2010-03-07 13:52:51 UTC
Permalink
I demand that Ant may or may not have written...
Post by Ant
Post by Darren Salt
Post by Ant
Uh oh. I just discovered mcelog and something new and scary in its
[snip]
Post by Ant
Mar 6 08:52:09 foobar mcelog: HARDWARE ERROR. This is *NOT* a software
problem!
Mar 6 08:52:09 foobar mcelog: Please contact your hardware vendor
Mar 6 08:52:09 foobar mcelog: MCE 0
Mar 6 08:52:09 foobar mcelog: CPU 1 1 instruction cache
Mar 6 08:52:09 foobar mcelog: ADDR c11b6ff0
Mar 6 08:52:09 foobar mcelog: TIME 1267894329 Sat Mar 6 08:52:09 2010
Mar 6 08:52:09 foobar mcelog: TLB parity error in virtual array
Mar 6 08:52:09 foobar mcelog: TLB error 'instruction transaction,
level 1'
Mar 6 08:52:09 foobar mcelog: STATUS 9400000000010011 MCGSTATUS 0
Mar 6 08:52:09 foobar mcelog: MCGCAP 105 APICID 1 SOCKETID 0
Mar 6 08:52:09 foobar mcelog: CPUID Vendor AMD Family 15 Model 43
[snip duplicate entries]
Ouch.
:(
Post by Darren Salt
Post by Ant
What does that mean? Dying CPU (had it since 12/24/2006)?
12/12/2007? ;-)
Eh?
Normalisation in progress. ;-)
Post by Ant
Post by Darren Salt
(Hint: use ISO8601 date formats or use month names. Broken-endian dates
can all too easily cause error; fortunately, that one's unambiguous.)
I don't get it. :(
Well... today is 7/3/2010 or 3/7/2010, according to locale; it is better
represented as 2010-03-07.
Post by Ant
Post by Darren Salt
Anyway, it does look like a fault in that CPU. I'd certainly be
considering replacing it, though due to your earlier mention of kernel
panics, I wouldn't rule out board problems either; are there any visible
signs of hardware problems (leaky/bulging capacitors etc.)? Checking the
PSU is probably also worthwhile.
Hmmm, I just swapped my PSU because the old one (FSP650-80GLC PSU (650
watts) from 5/14/2007) died on 12/2009. I recalled days before,
something smelled burning but I couldn't figure out where it came from
since I had two desktops. I guess it was the PSU that went poof!
I've had that happen once here. Advice given was to replace the whole lot
because of possible damage to components, and I can see where that's coming
from: brief over-voltage or over-current. (Would anybody who knows more about
your typical switched-mode PSU care to comment?)
Post by Ant
At the same time, my EVGA GeForce 8800 GT video card had to be RMA'ed since
it didn't work anymore since the new PSU still wouldn't boot the box up at
all.
Dead card, due to The Way of the Exploding PSU?
Post by Ant
After getting a RMA'ed refurbished video card back, my box was fine for a
bit and then got kernel panics once in a while. Then, it seems to become
more frequently slowly. One day in February, I ran memtest86+ v4.00 for
like five hours and found lots of errors. My friend and I narrowed it down
to a 512 MB RAM
I've seen bad RAM before. On visual inspection, it looks exactly like good
RAM.
Post by Ant
and left with 2.5 GB remaining (still plenty for an old
Linux workstation!). Oh and we didn't see anything burned, busted, etc.
That's the thing. It might not *look* damaged...
Post by Ant
It sounds like that PSU bust damaged a lot of my hardwares. Argh! I
don't have the time and resources to build another one
Yet you have the time to respond here. ;-)
Post by Ant
(guess I could do a clean install with it too :P). :(
Hmm...
Post by Ant
Post by Darren Salt
(http://en.wikipedia.org/wiki/Translation_lookaside_buffer describes the
affected area of the CPU.)
Hmm, I wonder if that 512 MB RAM that memtest86 detected having errors
wasn't bad?
Chances are that memtest86 was right. (I can see how bad memory might cause
incorrect TLB entries, but not parity errors.)
Post by Ant
Post by Darren Salt
Post by Ant
Maybe that's why memtest86+ didn't find any problems last week.
That doesn't seem to be relevant.
Why do you say that? I am going to run it again soon to double check.
It's testing the memory, and (probably) isn't making use of logical
addressing. If it isn't, then it's not going to be making use of the TLB, so
it's not going to cause MCEs. (Or perhaps they *were* happening, but
memtest86+ was ignoring them.)
Post by Ant
Post by Darren Salt
http://www.mjmwired.net/kernel/Documentation/networking/netconsole.txt
That needs a second computer, but it will at least allow most panics to be
captured. (Exceptions include hard hangs, where there may be no panic
which can be reported, and problems which affect the network interface
over which the log is being sent.)
Interesting. I wished Linux's Kernel panics would log to a file like
Windows' memory dumps from blue screens so I can use a debugger to see what
the dumps.
Logging to a file isn't an option (at this point, things are probably too far
gone for this to be practical); but they could, perhaps, be stored in some
non-volatile memory. (You'd need at least 16K for this, ideally 64K or more;
and I don't think that there's enough in your typical PC RTC.)
--
| Darren Salt | linux at youmustbejoking | nr. Ashington, | Doon
| using Debian GNU/Linux | or ds ,demon,co,uk | Northumberland | Army
| + This comment has been censored.

Would ye both eat your cake and have your cake?
Ant
2010-03-07 16:00:52 UTC
Permalink
Post by Darren Salt
Post by Ant
Post by Darren Salt
(Hint: use ISO8601 date formats or use month names. Broken-endian dates
can all too easily cause error; fortunately, that one's unambiguous.)
I don't get it. :(
Well... today is 7/3/2010 or 3/7/2010, according to locale; it is better
represented as 2010-03-07.
OH! Bah, I am an American. :P
Post by Darren Salt
Post by Ant
Post by Darren Salt
Anyway, it does look like a fault in that CPU. I'd certainly be
considering replacing it, though due to your earlier mention of kernel
panics, I wouldn't rule out board problems either; are there any visible
signs of hardware problems (leaky/bulging capacitors etc.)? Checking the
PSU is probably also worthwhile.
Hmmm, I just swapped my PSU because the old one (FSP650-80GLC PSU (650
watts) from 5/14/2007) died on 12/2009. I recalled days before,
something smelled burning but I couldn't figure out where it came from
since I had two desktops. I guess it was the PSU that went poof!
I've had that happen once here. Advice given was to replace the whole lot
because of possible damage to components, and I can see where that's coming
from: brief over-voltage or over-current. (Would anybody who knows more about
your typical switched-mode PSU care to comment?)
:( It sounds common I guess. I ran memtest86+ v4.000 overnight for over
five hours. It had two passes and almost done with the third one on its
test 8. I guess RAM is still OK!
Post by Darren Salt
Post by Ant
At the same time, my EVGA GeForce 8800 GT video card had to be RMA'ed since
it didn't work anymore since the new PSU still wouldn't boot the box up at
all.
Dead card, due to The Way of the Exploding PSU?
I guess so if it stopped working right after PSU went dead and repalced
with a new one. Or a coincident?
Post by Darren Salt
Post by Ant
After getting a RMA'ed refurbished video card back, my box was fine for a
bit and then got kernel panics once in a while. Then, it seems to become
more frequently slowly. One day in February, I ran memtest86+ v4.00 for
like five hours and found lots of errors. My friend and I narrowed it down
to a 512 MB RAM
I've seen bad RAM before. On visual inspection, it looks exactly like good
RAM.
Yeah. It's old too (four years I think)!
Post by Darren Salt
Post by Ant
and left with 2.5 GB remaining (still plenty for an old
Linux workstation!). Oh and we didn't see anything burned, busted, etc.
That's the thing. It might not *look* damaged...
Right, but you asked if there were any physical damages from our eyes. :P
Post by Darren Salt
Post by Ant
It sounds like that PSU bust damaged a lot of my hardwares. Argh! I
don't have the time and resources to build another one
Yet you have the time to respond here. ;-)
That's faster. Sometimes I do it from work too. :P
Post by Darren Salt
Post by Ant
Hmm, I wonder if that 512 MB RAM that memtest86 detected having errors
wasn't bad?
Chances are that memtest86 was right. (I can see how bad memory might cause
incorrect TLB entries, but not parity errors.)
So parity errors are from CPU only? I am not an expert in hardwares area.
Post by Darren Salt
Post by Ant
Post by Darren Salt
Post by Ant
Maybe that's why memtest86+ didn't find any problems last week.
That doesn't seem to be relevant.
Why do you say that? I am going to run it again soon to double check.
It's testing the memory, and (probably) isn't making use of logical
addressing. If it isn't, then it's not going to be making use of the TLB, so
it's not going to cause MCEs. (Or perhaps they *were* happening, but
memtest86+ was ignoring them.)
So how can I test this with another bootable tool like memtest86+?
Post by Darren Salt
Post by Ant
Interesting. I wished Linux's Kernel panics would log to a file like
Windows' memory dumps from blue screens so I can use a debugger to see what
the dumps.
Logging to a file isn't an option (at this point, things are probably too far
gone for this to be practical); but they could, perhaps, be stored in some
non-volatile memory. (You'd need at least 16K for this, ideally 64K or more;
and I don't think that there's enough in your typical PC RTC.)
Bummer. I am surprised Linux doesn't do this, but MS does with its
NT-based Windows.
--
"To the gods I am an ant, but to the ants, I am a god." --unknown
/\___/\
/ /\ /\ \ Phil./Ant @ http://antfarm.ma.cx (Personal Web Site)
| |o o| | Ant's Quality Foraged Links: http://aqfl.net
\ _ / Nuke ANT from e-mail address: ***@earthlink.netANT
( ) or ***@zimage.com
Ant is currently not listening to any songs on his home computer.
Darren Salt
2010-03-08 03:08:44 UTC
Permalink
I demand that Ant may or may not have written...
[snip]
Post by Ant
Post by Darren Salt
Post by Ant
Post by Darren Salt
Anyway, it does look like a fault in that CPU. I'd certainly be
considering replacing it, though due to your earlier mention of kernel
panics, I wouldn't rule out board problems either; are there any visible
signs of hardware problems (leaky/bulging capacitors etc.)? Checking the
PSU is probably also worthwhile.
Hmmm, I just swapped my PSU because the old one (FSP650-80GLC PSU (650
watts) from 5/14/2007) died on 12/2009. I recalled days before,
something smelled burning but I couldn't figure out where it came from
since I had two desktops. I guess it was the PSU that went poof!
I've had that happen once here. Advice given was to replace the whole lot
because of possible damage to components, and I can see where that's
coming from: brief over-voltage or over-current. (Would anybody who knows
more about your typical switched-mode PSU care to comment?)
:( It sounds common I guess.
Cheap components, I shouldn't wonder.
Post by Ant
I ran memtest86+ v4.000 overnight for over five hours. It had two passes
and almost done with the third one on its test 8. I guess RAM is still OK!
Probably. :-)
Post by Ant
Post by Darren Salt
Post by Ant
At the same time, my EVGA GeForce 8800 GT video card had to be RMA'ed
since it didn't work anymore since the new PSU still wouldn't boot the
box up at all.
Dead card, due to The Way of the Exploding PSU?
I guess so if it stopped working right after PSU went dead and repalced
with a new one. Or a coincident?
Coincidence, I'd say. Too much of one does seem rather likely.
Post by Ant
Post by Darren Salt
Post by Ant
After getting a RMA'ed refurbished video card back, my box was fine for a
bit and then got kernel panics once in a while. Then, it seems to become
more frequently slowly. One day in February, I ran memtest86+ v4.00 for
like five hours and found lots of errors. My friend and I narrowed it
down to a 512 MB RAM
I've seen bad RAM before. On visual inspection, it looks exactly like good
RAM.
Yeah. It's old too (four years I think)!
Good hardware should last quite a bit longer than that. Assuming that it /is/
good hardware, of course...
Post by Ant
Post by Darren Salt
Post by Ant
and left with 2.5 GB remaining (still plenty for an old
Linux workstation!). Oh and we didn't see anything burned, busted, etc.
That's the thing. It might not *look* damaged...
Right, but you asked if there were any physical damages from our eyes. :P
Yes, on the grounds that it's not worth looking further if you see obvious
damage. :-þ

[snip]
Post by Ant
Post by Darren Salt
Post by Ant
Hmm, I wonder if that 512 MB RAM that memtest86 detected having errors
wasn't bad?
Chances are that memtest86 was right. (I can see how bad memory might
cause incorrect TLB entries, but not parity errors.)
So parity errors are from CPU only? I am not an expert in hardwares area.
If you happen to be using ECC RAM, errors can be reported from that too.
Hopefully, they'd be correctable ones...
Post by Ant
Post by Darren Salt
Post by Ant
Post by Darren Salt
Post by Ant
Maybe that's why memtest86+ didn't find any problems last week.
That doesn't seem to be relevant.
Why do you say that? I am going to run it again soon to double check.
It's testing the memory, and (probably) isn't making use of logical
addressing. If it isn't, then it's not going to be making use of the TLB,
so it's not going to cause MCEs. (Or perhaps they *were* happening, but
memtest86+ was ignoring them.)
So how can I test this with another bootable tool like memtest86+?
Boot from USB or CD, drop to a text console, stress it with a kernel compile
or something (preferably without touching disk). Wait. :-)
Post by Ant
Post by Darren Salt
Post by Ant
Interesting. I wished Linux's Kernel panics would log to a file like
Windows' memory dumps from blue screens so I can use a debugger to see
what the dumps.
Logging to a file isn't an option (at this point, things are probably too
far gone for this to be practical); but they could, perhaps, be stored in
some non-volatile memory. (You'd need at least 16K for this, ideally 64K
or more; and I don't think that there's enough in your typical PC RTC.)
Bummer. I am surprised Linux doesn't do this, but MS does with its
NT-based Windows.
Given suitable storage, and the right kernel options...
--
| Darren Salt | linux at youmustbejoking | nr. Ashington, | Doon
| using Debian GNU/Linux | or ds ,demon,co,uk | Northumberland | Army
| + http://www.youmustbejoking.demon.co.uk/ & http://tlasd.wordpress.com/

Scotty: "It's comin' apart, lad!"
Ant
2010-03-08 07:42:11 UTC
Permalink
Post by Darren Salt
Yes, on the grounds that it's not worth looking further if you see obvious
damage. :-þ
No obvious damages from a few weeks ago when my friend (hardware person)
and I checked.
Post by Darren Salt
[snip]
Post by Ant
Post by Darren Salt
Post by Ant
Hmm, I wonder if that 512 MB RAM that memtest86 detected having errors
wasn't bad?
Chances are that memtest86 was right. (I can see how bad memory might
cause incorrect TLB entries, but not parity errors.)
So parity errors are from CPU only? I am not an expert in hardwares area.
If you happen to be using ECC RAM, errors can be reported from that too.
Hopefully, they'd be correctable ones...
Hmm, I don't know if my RAM uses ECC? How can I check?
Post by Darren Salt
Post by Ant
So how can I test this with another bootable tool like memtest86+?
Boot from USB or CD, drop to a text console, stress it with a kernel compile
or something (preferably without touching disk). Wait. :-)
Hmm, I did that in my regular Debian and no problems! I used sys_basher,
unrar 10 GB of datas, etc. I can't make it happen with stress tests.
Most of the kernel panics happened when idled! :D
--
"The Hunam Tiger ant has been known to consume an entire meal before the
picnic guest arrive." --12th century Tang Dynasty proverb.
/\___/\
/ /\ /\ \ Phil./Ant @ http://antfarm.ma.cx (Personal Web Site)
| |o o| | Ant's Quality Foraged Links: http://aqfl.net
\ _ / Nuke ANT from e-mail address: ***@earthlink.netANT
( ) or ***@zimage.com
Ant is currently not listening to any songs on his home computer.
Darren Salt
2010-03-08 13:56:30 UTC
Permalink
I demand that Ant may or may not have written...
[snip]
Post by Ant
Post by Darren Salt
Post by Ant
Post by Darren Salt
Post by Ant
Hmm, I wonder if that 512 MB RAM that memtest86 detected having errors
wasn't bad?
Chances are that memtest86 was right. (I can see how bad memory might
cause incorrect TLB entries, but not parity errors.)
So parity errors are from CPU only? I am not an expert in hardwares area.
If you happen to be using ECC RAM, errors can be reported from that too.
Hopefully, they'd be correctable ones...
Hmm, I don't know if my RAM uses ECC? How can I check?
dmidecode will tell you. ECC was also "a bit" more expensive, although when I
last looked at memory prices etc., I noticed ECC showing up a lot more and
relatively inexpensively.
Post by Ant
Post by Darren Salt
Post by Ant
So how can I test this with another bootable tool like memtest86+?
Boot from USB or CD, drop to a text console, stress it with a kernel
compile or something (preferably without touching disk). Wait. :-)
Hmm, I did that in my regular Debian and no problems! I used sys_basher,
unrar 10 GB of datas, etc. I can't make it happen with stress tests. Most
of the kernel panics happened when idled! :D
Fine; then let it idle for a while too...
--
| Darren Salt | linux at youmustbejoking | nr. Ashington, | Doon
| using Debian GNU/Linux | or ds ,demon,co,uk | Northumberland | Army
| + http://www.youmustbejoking.demon.co.uk/ & http://tartarus.org/ds/

You will hear good news from one you thought unfriendly to you.
Ant
2010-03-08 16:09:12 UTC
Permalink
Post by Darren Salt
Post by Ant
Post by Darren Salt
Post by Ant
So parity errors are from CPU only? I am not an expert in hardwares area.
If you happen to be using ECC RAM, errors can be reported from that too.
Hopefully, they'd be correctable ones...
Hmm, I don't know if my RAM uses ECC? How can I check?
dmidecode will tell you. ECC was also "a bit" more expensive, although when I
last looked at memory prices etc., I noticed ECC showing up a lot more and
relatively inexpensively.
I don't see any ECC enabled:
# dmidecode
# dmidecode 2.9
SMBIOS 2.3 present.
42 structures occupying 1380 bytes.
Table at 0x000F0000.

Handle 0x0000, DMI type 0, 20 bytes
BIOS Information
Vendor: Phoenix Technologies, LTD
Version: 6.00 PG
Release Date: 07/21/2006
Address: 0xE0000
Runtime Size: 128 kB
ROM Size: 512 kB
Characteristics:
ISA is supported
PCI is supported
PNP is supported
APM is supported
BIOS is upgradeable
BIOS shadowing is allowed
Boot from CD is supported
Selectable boot is supported
BIOS ROM is socketed
EDD is supported
5.25"/360 KB floppy services are supported (int 13h)
5.25"/1.2 MB floppy services are supported (int 13h)
3.5"/720 KB floppy services are supported (int 13h)
3.5"/2.88 MB floppy services are supported (int 13h)
Print screen service is supported (int 5h)
8042 keyboard services are supported (int 9h)
Serial services are supported (int 14h)
Printer services are supported (int 17h)
CGA/mono video services are supported (int 10h)
ACPI is supported
USB legacy is supported
LS-120 boot is supported
ATAPI Zip drive boot is supported
BIOS boot specification is supported

Handle 0x0001, DMI type 1, 25 bytes
System Information
Manufacturer: MICRO-STAR INTERNATIONAL CO., LTD
Product Name: MS-7125
Version: 3.0
Serial Number:
UUID: Not Present
Wake-up Type: Power Switch

Handle 0x0002, DMI type 2, 8 bytes
Base Board Information
Manufacturer: MICRO-STAR INTERNATIONAL CO., LTD
Product Name: MS-7125
Version: 3.0
Serial Number:

Handle 0x0003, DMI type 3, 17 bytes
Chassis Information
Manufacturer:
Type: Desktop
Lock: Not Present
Version:
Serial Number:
Asset Tag:
Boot-up State: Unknown
Power Supply State: Unknown
Thermal State: Unknown
Security Status: Unknown
OEM Information: 0x00000000

Handle 0x0004, DMI type 4, 35 bytes
Processor Information
Socket Designation: Socket 939
Type: Central Processor
Family: Athlon 64
Manufacturer: AMD
ID: B1 0F 02 00 FF FB 8B 17
Signature: Family 15, Model 43, Stepping 1
Flags:
FPU (Floating-point unit on-chip)
VME (Virtual mode extension)
DE (Debugging extension)
PSE (Page size extension)
TSC (Time stamp counter)
MSR (Model specific registers)
PAE (Physical address extension)
MCE (Machine check exception)
CX8 (CMPXCHG8 instruction supported)
APIC (On-chip APIC hardware supported)
SEP (Fast system call)
MTRR (Memory type range registers)
PGE (Page global enable)
MCA (Machine check architecture)
CMOV (Conditional move instruction supported)
PAT (Page attribute table)
PSE-36 (36-bit page size extension)
CLFSH (CLFLUSH instruction supported)
MMX (MMX technology supported)
FXSR (Fast floating-point save and restore)
SSE (Streaming SIMD extensions)
SSE2 (Streaming SIMD extensions 2)
HTT (Hyper-threading technology)
Version: AMD Athlon(tm) 64 X2 Dual Core Processor 4600+
Voltage: 1.3 V
External Clock: 201 MHz
Max Speed: 3000 MHz
Current Speed: 2412 MHz
Status: Populated, Enabled
Upgrade: Socket 939
L1 Cache Handle: 0x000B
L2 Cache Handle: 0x000D
L3 Cache Handle: Not Provided
Serial Number:
Asset Tag:
Part Number:

Handle 0x0005, DMI type 4, 35 bytes
Processor Information
Socket Designation: Socket 939
Type: Central Processor
Family: Athlon 64
Manufacturer: AMD
ID: B1 0F 02 00 FF FB 8B 07
Signature: Family 15, Model 43, Stepping 1
Flags:
FPU (Floating-point unit on-chip)
VME (Virtual mode extension)
DE (Debugging extension)
PSE (Page size extension)
TSC (Time stamp counter)
MSR (Model specific registers)
PAE (Physical address extension)
MCE (Machine check exception)
CX8 (CMPXCHG8 instruction supported)
APIC (On-chip APIC hardware supported)
SEP (Fast system call)
MTRR (Memory type range registers)
PGE (Page global enable)
MCA (Machine check architecture)
CMOV (Conditional move instruction supported)
PAT (Page attribute table)
PSE-36 (36-bit page size extension)
CLFSH (CLFLUSH instruction supported)
MMX (MMX technology supported)
FXSR (Fast floating-point save and restore)
SSE (Streaming SIMD extensions)
SSE2 (Streaming SIMD extensions 2)
Version: AMD Athlon(tm) 64 X2 Dual Core Processor 4600+
Voltage: 1.3 V
External Clock: 201 MHz
Max Speed: 3000 MHz
Current Speed: 2412 MHz
Status: Populated, Enabled
Upgrade: Socket 939
L1 Cache Handle: 0x000C
L2 Cache Handle: 0x000E
L3 Cache Handle: Not Provided
Serial Number:
Asset Tag:
Part Number:

Handle 0x0006, DMI type 5, 24 bytes
Memory Controller Information
Error Detecting Method: 64-bit ECC
Error Correcting Capabilities:
None
Supported Interleave: One-way Interleave
Current Interleave: One-way Interleave
Maximum Memory Module Size: 4096 MB
Maximum Total Memory Size: 16384 MB
Supported Speeds:
70 ns
60 ns
50 ns
Supported Memory Types:
Standard
DIMM
Memory Module Voltage: 2.9 V
Associated Memory Slots: 4
0x0007
0x0008
0x0009
0x000A
Enabled Error Correcting Capabilities: None

Handle 0x0007, DMI type 6, 12 bytes
Memory Module Information
Socket Designation: A0
Bank Connections: 0 1
Current Speed: 7 ns
Type: Unknown EDO
Installed Size: 512 MB (Double-bank Connection)
Enabled Size: 512 MB (Double-bank Connection)
Error Status: OK

Handle 0x0008, DMI type 6, 12 bytes
Memory Module Information
Socket Designation: A1
Bank Connections: 2 3
Current Speed: 7 ns
Type: Unknown EDO
Installed Size: 512 MB (Double-bank Connection)
Enabled Size: 512 MB (Double-bank Connection)
Error Status: OK

Handle 0x0009, DMI type 6, 12 bytes
Memory Module Information
Socket Designation: A2
Bank Connections: 4 5
Current Speed: 7 ns
Type: Unknown EDO
Installed Size: 512 MB (Double-bank Connection)
Enabled Size: 512 MB (Double-bank Connection)
Error Status: OK

Handle 0x000A, DMI type 6, 12 bytes
Memory Module Information
Socket Designation: A3
Bank Connections: 6 7
Current Speed: 7 ns
Type: Unknown EDO
Installed Size: 1024 MB (Double-bank Connection)
Enabled Size: 1024 MB (Double-bank Connection)
Error Status: OK

Handle 0x000B, DMI type 7, 19 bytes
Cache Information
Socket Designation: Internal Cache
Configuration: Enabled, Not Socketed, Level 1
Operational Mode: Write Back
Location: Internal
Installed Size: 128 KB
Maximum Size: 128 KB
Supported SRAM Types:
Synchronous
Installed SRAM Type: Synchronous
Speed: Unknown
Error Correction Type: Unknown
System Type: Unknown
Associativity: Unknown

Handle 0x000C, DMI type 7, 19 bytes
Cache Information
Socket Designation: Internal Cache
Configuration: Enabled, Not Socketed, Level 1
Operational Mode: Write Back
Location: Internal
Installed Size: 128 KB
Maximum Size: 128 KB
Supported SRAM Types:
Synchronous
Installed SRAM Type: Synchronous
Speed: Unknown
Error Correction Type: Unknown
System Type: Unknown
Associativity: Unknown

Handle 0x000D, DMI type 7, 19 bytes
Cache Information
Socket Designation: External Cache
Configuration: Enabled, Not Socketed, Level 2
Operational Mode: Write Back
Location: Internal
Installed Size: 512 KB
Maximum Size: 512 KB
Supported SRAM Types:
Synchronous
Installed SRAM Type: Synchronous
Speed: Unknown
Error Correction Type: Unknown
System Type: Unknown
Associativity: Unknown

Handle 0x000E, DMI type 7, 19 bytes
Cache Information
Socket Designation: External Cache
Configuration: Enabled, Not Socketed, Level 2
Operational Mode: Write Back
Location: Internal
Installed Size: 512 KB
Maximum Size: 512 KB
Supported SRAM Types:
Synchronous
Installed SRAM Type: Synchronous
Speed: Unknown
Error Correction Type: Unknown
System Type: Unknown
Associativity: Unknown

Handle 0x000F, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: PRIMARY IDE
Internal Connector Type: On Board IDE
External Reference Designator: Not Specified
External Connector Type: None
Port Type: Other

Handle 0x0010, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: SECONDARY IDE
Internal Connector Type: On Board IDE
External Reference Designator: Not Specified
External Connector Type: None
Port Type: Other

Handle 0x0011, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: FDD
Internal Connector Type: On Board Floppy
External Reference Designator: Not Specified
External Connector Type: None
Port Type: 8251 FIFO Compatible

Handle 0x0012, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: COM1
Internal Connector Type: 9 Pin Dual Inline (pin 10 cut)
External Reference Designator:
External Connector Type: DB-9 male
Port Type: Serial Port 16450 Compatible

Handle 0x0013, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: COM2
Internal Connector Type: 9 Pin Dual Inline (pin 10 cut)
External Reference Designator:
External Connector Type: DB-9 male
Port Type: Serial Port 16450 Compatible

Handle 0x0014, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: LPT1
Internal Connector Type: DB-25 female
External Reference Designator:
External Connector Type: DB-25 female
Port Type: Parallel Port ECP/EPP

Handle 0x0015, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: Keyboard
Internal Connector Type: PS/2
External Reference Designator:
External Connector Type: PS/2
Port Type: Keyboard Port

Handle 0x0016, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: PS/2 Mouse
Internal Connector Type: PS/2
External Reference Designator:
External Connector Type: PS/2
Port Type: Mouse Port

Handle 0x0017, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: Not Specified
Internal Connector Type: None
External Reference Designator: USB0
External Connector Type: Other
Port Type: USB

Handle 0x0018, DMI type 9, 13 bytes
System Slot Information
Designation: PCI0
Type: 32-bit PCI
Current Usage: Available
Length: Long
ID: 1
Characteristics:
5.0 V is provided
PME signal is supported

Handle 0x0019, DMI type 9, 13 bytes
System Slot Information
Designation: PCI1
Type: 32-bit PCI
Current Usage: Available
Length: Long
ID: 2
Characteristics:
5.0 V is provided
PME signal is supported

Handle 0x001A, DMI type 9, 13 bytes
System Slot Information
Designation: PCI2
Type: 32-bit PCI
Current Usage: Available
Length: Long
ID: 3
Characteristics:
5.0 V is provided
PME signal is supported

Handle 0x001B, DMI type 9, 13 bytes
System Slot Information
Designation: PCI3
Type: 32-bit PCI
Current Usage: In Use
Length: Long
ID: 4
Characteristics:
5.0 V is provided
PME signal is supported

Handle 0x001C, DMI type 9, 13 bytes
System Slot Information
Designation: PCI4
Type: 32-bit PCI
Current Usage: Available
Length: Long
ID: 5
Characteristics:
5.0 V is provided
PME signal is supported

Handle 0x001D, DMI type 13, 22 bytes
BIOS Language Information
Installable Languages: 3
n|US|iso8859-1
n|US|iso8859-1
r|CA|iso8859-1
Currently Installed Language: n|US|iso8859-1

Handle 0x001E, DMI type 16, 15 bytes
Physical Memory Array
Location: System Board Or Motherboard
Use: System Memory
Error Correction Type: None
Maximum Capacity: 16 GB
Error Information Handle: Not Provided
Number Of Devices: 4

Handle 0x001F, DMI type 17, 27 bytes
Memory Device
Array Handle: 0x001E
Error Information Handle: Not Provided
Total Width: 64 bits
Data Width: 64 bits
Size: 512 MB
Form Factor: DIMM
Set: None
Locator: A0
Bank Locator: Bank0/1
Type: Unknown
Type Detail: None
Speed: Unknown
Manufacturer: None
Serial Number: None
Asset Tag: None
Part Number: None

Handle 0x0020, DMI type 17, 27 bytes
Memory Device
Array Handle: 0x001E
Error Information Handle: Not Provided
Total Width: 64 bits
Data Width: 64 bits
Size: 512 MB
Form Factor: DIMM
Set: None
Locator: A1
Bank Locator: Bank2/3
Type: Unknown
Type Detail: None
Speed: Unknown
Manufacturer: None
Serial Number: None
Asset Tag: None
Part Number: None

Handle 0x0021, DMI type 17, 27 bytes
Memory Device
Array Handle: 0x001E
Error Information Handle: Not Provided
Total Width: 64 bits
Data Width: 64 bits
Size: 512 MB
Form Factor: DIMM
Set: None
Locator: A2
Bank Locator: Bank4/5
Type: Unknown
Type Detail: None
Speed: Unknown
Manufacturer: None
Serial Number: None
Asset Tag: None
Part Number: None

Handle 0x0022, DMI type 17, 27 bytes
Memory Device
Array Handle: 0x001E
Error Information Handle: Not Provided
Total Width: 64 bits
Data Width: 64 bits
Size: 1024 MB
Form Factor: DIMM
Set: None
Locator: A3
Bank Locator: Bank6/7
Type: Unknown
Type Detail: None
Speed: Unknown
Manufacturer: None
Serial Number: None
Asset Tag: None
Part Number: None

Handle 0x0023, DMI type 19, 15 bytes
Memory Array Mapped Address
Starting Address: 0x00000000000
Ending Address: 0x0009FFFFFFF
Range Size: 2560 MB
Physical Array Handle: 0x001E
Partition Width: 0

Handle 0x0024, DMI type 20, 19 bytes
Memory Device Mapped Address
Starting Address: 0x00000000000
Ending Address: 0x0001FFFFFFF
Range Size: 512 MB
Physical Device Handle: 0x001F
Memory Array Mapped Address Handle: 0x0023
Partition Row Position: 1

Handle 0x0025, DMI type 20, 19 bytes
Memory Device Mapped Address
Starting Address: 0x00020000000
Ending Address: 0x0003FFFFFFF
Range Size: 512 MB
Physical Device Handle: 0x0020
Memory Array Mapped Address Handle: 0x0023
Partition Row Position: 1

Handle 0x0026, DMI type 20, 19 bytes
Memory Device Mapped Address
Starting Address: 0x00040000000
Ending Address: 0x0005FFFFFFF
Range Size: 512 MB
Physical Device Handle: 0x0021
Memory Array Mapped Address Handle: 0x0023
Partition Row Position: 1

Handle 0x0027, DMI type 20, 19 bytes
Memory Device Mapped Address
Starting Address: 0x00060000000
Ending Address: 0x0009FFFFFFF
Range Size: 1 GB
Physical Device Handle: 0x0022
Memory Array Mapped Address Handle: 0x0023
Partition Row Position: 1

Handle 0x0028, DMI type 32, 11 bytes
System Boot Information
Status: No errors detected

Handle 0x0029, DMI type 127, 4 bytes
End Of Table


FYI from a just booted up Debian:
$ dmesg
[ 0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Linux version 2.6.32-trunk-686 (Debian 2.6.32-5)
(***@decadent.org.uk) (gcc version 4.3.4 (Debian 4.3.4-6) ) #1 SMP Sun
Jan 10 06:32:16 UTC 2010
[ 0.000000] KERNEL supported cpus:
[ 0.000000] Intel GenuineIntel
[ 0.000000] AMD AuthenticAMD
[ 0.000000] NSC Geode by NSC
[ 0.000000] Cyrix CyrixInstead
[ 0.000000] Centaur CentaurHauls
[ 0.000000] Transmeta GenuineTMx86
[ 0.000000] Transmeta TransmetaCPU
[ 0.000000] UMC UMC UMC UMC
[ 0.000000] BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: 0000000000000000 - 000000000009f400 (usable)
[ 0.000000] BIOS-e820: 000000000009f400 - 00000000000a0000 (reserved)
[ 0.000000] BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
[ 0.000000] BIOS-e820: 0000000000100000 - 000000009fff0000 (usable)
[ 0.000000] BIOS-e820: 000000009fff0000 - 000000009fff3000 (ACPI NVS)
[ 0.000000] BIOS-e820: 000000009fff3000 - 00000000a0000000 (ACPI data)
[ 0.000000] BIOS-e820: 00000000e0000000 - 00000000f0000000 (reserved)
[ 0.000000] BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved)
[ 0.000000] DMI 2.3 present.
[ 0.000000] Phoenix BIOS detected: BIOS may corrupt low RAM, working
around it.
[ 0.000000] e820 update range: 0000000000000000 - 0000000000010000
(usable) ==> (reserved)
[ 0.000000] last_pfn = 0x9fff0 max_arch_pfn = 0x100000
[ 0.000000] MTRR default type: uncachable
[ 0.000000] MTRR fixed ranges enabled:
[ 0.000000] 00000-9FFFF write-back
[ 0.000000] A0000-BFFFF uncachable
[ 0.000000] C0000-C7FFF write-protect
[ 0.000000] C8000-FFFFF uncachable
[ 0.000000] MTRR variable ranges enabled:
[ 0.000000] 0 base 0000000000 mask FF80000000 write-back
[ 0.000000] 1 base 0080000000 mask FFE0000000 write-back
[ 0.000000] 2 disabled
[ 0.000000] 3 disabled
[ 0.000000] 4 disabled
[ 0.000000] 5 disabled
[ 0.000000] 6 disabled
[ 0.000000] 7 disabled
[ 0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new
0x7010600070106
[ 0.000000] initial memory mapped : 0 - 01800000
[ 0.000000] init_memory_mapping: 0000000000000000-00000000373fe000
[ 0.000000] 0000000000 - 0000400000 page 4k
[ 0.000000] 0000400000 - 0037000000 page 2M
[ 0.000000] 0037000000 - 00373fe000 page 4k
[ 0.000000] kernel direct mapping tables up to 373fe000 @ 10000-16000
[ 0.000000] RAMDISK: 378f7000 - 37fef816
[ 0.000000] Allocated new RAMDISK: 00100000 - 007f8816
[ 0.000000] Move RAMDISK from 00000000378f7000 - 0000000037fef815 to
00100000 - 007f8815
[ 0.000000] ACPI: RSDP 000f9260 00014 (v00 Nvidia)
[ 0.000000] ACPI: RSDT 9fff3040 00030 (v01 Nvidia AWRDACPI 42302E31
AWRD 00000000)
[ 0.000000] ACPI: FACP 9fff30c0 00074 (v01 Nvidia AWRDACPI 42302E31
AWRD 00000000)
[ 0.000000] ACPI: DSDT 9fff3180 063C4 (v01 NVIDIA AWRDACPI 00001000
MSFT 0100000E)
[ 0.000000] ACPI: FACS 9fff0000 00040
[ 0.000000] ACPI: MCFG 9fff9680 0003C (v01 Nvidia AWRDACPI 42302E31
AWRD 00000000)
[ 0.000000] ACPI: APIC 9fff95c0 00072 (v01 Nvidia AWRDACPI 42302E31
AWRD 00000000)
[ 0.000000] ACPI: Local APIC address 0xfee00000
[ 0.000000] 1675MB HIGHMEM available.
[ 0.000000] 883MB LOWMEM available.
[ 0.000000] mapped low ram: 0 - 373fe000
[ 0.000000] low ram: 0 - 373fe000
[ 0.000000] node 0 low ram: 00000000 - 373fe000
[ 0.000000] node 0 bootmap 00012000 - 00018e80
[ 0.000000] (9 early reservations) ==> bootmem [0000000000 - 00373fe000]
[ 0.000000] #0 [0000000000 - 0000001000] BIOS data page ==>
[0000000000 - 0000001000]
[ 0.000000] #1 [0000001000 - 0000002000] EX TRAMPOLINE ==>
[0000001000 - 0000002000]
[ 0.000000] #2 [0000006000 - 0000007000] TRAMPOLINE ==>
[0000006000 - 0000007000]
[ 0.000000] #3 [0001000000 - 00014a1334] TEXT DATA BSS ==>
[0001000000 - 00014a1334]
[ 0.000000] #4 [000009f400 - 0000100000] BIOS reserved ==>
[000009f400 - 0000100000]
[ 0.000000] #5 [00014a2000 - 00014a80ae] BRK ==>
[00014a2000 - 00014a80ae]
[ 0.000000] #6 [0000010000 - 0000012000] PGTABLE ==>
[0000010000 - 0000012000]
[ 0.000000] #7 [0000100000 - 00007f8816] NEW RAMDISK ==>
[0000100000 - 00007f8816]
[ 0.000000] #8 [0000012000 - 0000019000] BOOTMAP ==>
[0000012000 - 0000019000]
[ 0.000000] found SMP MP-table at [c00f5380] f5380
[ 0.000000] Zone PFN ranges:
[ 0.000000] DMA 0x00000010 -> 0x00001000
[ 0.000000] Normal 0x00001000 -> 0x000373fe
[ 0.000000] HighMem 0x000373fe -> 0x0009fff0
[ 0.000000] Movable zone start PFN for each node
[ 0.000000] early_node_map[2] active PFN ranges
[ 0.000000] 0: 0x00000010 -> 0x0000009f
[ 0.000000] 0: 0x00000100 -> 0x0009fff0
[ 0.000000] On node 0 totalpages: 655231
[ 0.000000] free_area_init_node: node 0, pgdat c138edc0, node_mem_map
c14aa200
[ 0.000000] DMA zone: 32 pages used for memmap
[ 0.000000] DMA zone: 0 pages reserved
[ 0.000000] DMA zone: 3951 pages, LIFO batch:0
[ 0.000000] Normal zone: 1736 pages used for memmap
[ 0.000000] Normal zone: 220470 pages, LIFO batch:31
[ 0.000000] HighMem zone: 3352 pages used for memmap
[ 0.000000] HighMem zone: 425690 pages, LIFO batch:31
[ 0.000000] Using APIC driver default
[ 0.000000] Nvidia board detected. Ignoring ACPI timer override.
[ 0.000000] If you got timer trouble try acpi_use_timer_override
[ 0.000000] ACPI: PM-Timer IO Port: 0x4008
[ 0.000000] ACPI: Local APIC address 0xfee00000
[ 0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
[ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
[ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
[ 0.000000] ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
[ 0.000000] IOAPIC[0]: apic_id 2, version 17, address 0xfec00000, GSI
0-23
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 14 global_irq 14 high edge)
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 15 global_irq 15 high edge)
[ 0.000000] ACPI: IRQ9 used by override.
[ 0.000000] ACPI: IRQ14 used by override.
[ 0.000000] ACPI: IRQ15 used by override.
[ 0.000000] Enabling APIC mode: Flat. Using 1 I/O APICs
[ 0.000000] Using ACPI (MADT) for SMP configuration information
[ 0.000000] SMP: Allowing 2 CPUs, 0 hotplug CPUs
[ 0.000000] nr_irqs_gsi: 24
[ 0.000000] PM: Registered nosave memory: 000000000009f000 -
00000000000a0000
[ 0.000000] PM: Registered nosave memory: 00000000000a0000 -
00000000000f0000
[ 0.000000] PM: Registered nosave memory: 00000000000f0000 -
0000000000100000
[ 0.000000] Allocating PCI resources starting at a0000000 (gap:
a0000000:40000000)
[ 0.000000] Booting paravirtualized kernel on bare hardware
[ 0.000000] NR_CPUS:32 nr_cpumask_bits:32 nr_cpu_ids:2 nr_node_ids:1
[ 0.000000] PERCPU: Embedded 14 pages/cpu @c2c00000 s34072 r0 d23272
u2097152
[ 0.000000] pcpu-alloc: s34072 r0 d23272 u2097152 alloc=1*4194304
[ 0.000000] pcpu-alloc: [0] 0 1
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on.
Total pages: 650111
[ 0.000000] Kernel command line:
BOOT_IMAGE=/boot/vmlinuz-2.6.32-trunk-686
root=UUID=fe4a1af1-1979-49fb-9668-314a24b12890 ro quiet
[ 0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
[ 0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288
bytes)
[ 0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144
bytes)
[ 0.000000] Enabling fast FPU save and restore... done.
[ 0.000000] Enabling unmasked SIMD FPU exception support... done.
[ 0.000000] Initializing CPU#0
[ 0.000000] Initializing HighMem for node 0 (000373fe:0009fff0)
[ 0.000000] Memory: 2586644k/2621376k available (2414k kernel code,
33368k reserved, 1266k data, 368k init, 1716168k highmem)
[ 0.000000] virtual kernel memory layout:
[ 0.000000] fixmap : 0xffd56000 - 0xfffff000 (2724 kB)
[ 0.000000] pkmap : 0xff400000 - 0xff800000 (4096 kB)
[ 0.000000] vmalloc : 0xf7bfe000 - 0xff3fe000 ( 120 MB)
[ 0.000000] lowmem : 0xc0000000 - 0xf73fe000 ( 883 MB)
[ 0.000000] .init : 0xc1399000 - 0xc13f5000 ( 368 kB)
[ 0.000000] .data : 0xc125bb11 - 0xc1398560 (1266 kB)
[ 0.000000] .text : 0xc1000000 - 0xc125bb11 (2414 kB)
[ 0.000000] Checking if this processor honours the WP bit even in
supervisor mode...Ok.
[ 0.000000] SLUB: Genslabs=13, HWalign=64, Order=0-3, MinObjects=0,
CPUs=2, Nodes=1
[ 0.000000] Hierarchical RCU implementation.
[ 0.000000] NR_IRQS:1280
[ 0.000000] spurious 8259A interrupt: IRQ7.
[ 0.000000] Console: colour VGA+ 80x25
[ 0.000000] console [tty0] enabled
[ 0.000000] Fast TSC calibration using PIT
[ 0.000000] Detected 2411.146 MHz processor.
[ 0.008007] Calibrating delay loop (skipped), value calculated using
timer frequency.. 4822.29 BogoMIPS (lpj=9644584)
[ 0.008027] Security Framework initialized
[ 0.008037] SELinux: Disabled at boot.
[ 0.008045] Mount-cache hash table entries: 512
[ 0.008228] Initializing cgroup subsys ns
[ 0.008233] Initializing cgroup subsys cpuacct
[ 0.008236] Initializing cgroup subsys devices
[ 0.008238] Initializing cgroup subsys freezer
[ 0.008240] Initializing cgroup subsys net_cls
[ 0.008265] CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64
bytes/line)
[ 0.008267] CPU: L2 Cache: 512K (64 bytes/line)
[ 0.008270] CPU: Physical Processor ID: 0
[ 0.008271] CPU: Processor Core ID: 0
[ 0.008275] mce: CPU supports 5 MCE banks
[ 0.008301] Performance Events: AMD PMU driver.
[ 0.008308] ... version: 0
[ 0.008309] ... bit width: 48
[ 0.008311] ... generic registers: 4
[ 0.008312] ... value mask: 0000ffffffffffff
[ 0.008314] ... max period: 00007fffffffffff
[ 0.008315] ... fixed-purpose events: 0
[ 0.008317] ... event mask: 000000000000000f
[ 0.008322] Checking 'hlt' instruction... OK.
[ 0.024998] ACPI: Core revision 20090903
[ 0.036578] ..TIMER: vector=0x30 apic1=0 pin1=0 apic2=-1 pin2=-1
[ 0.076888] CPU0: AMD Athlon(tm) 64 X2 Dual Core Processor 4600+
stepping 01
[ 0.080001] Booting processor 1 APIC 0x1 ip 0x6000
[ 0.012000] Initializing CPU#1
[ 0.012000] Calibrating delay using timer specific routine.. 4822.54
BogoMIPS (lpj=9645093)
[ 0.012000] CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64
bytes/line)
[ 0.012000] CPU: L2 Cache: 512K (64 bytes/line)
[ 0.012000] CPU: Physical Processor ID: 0
[ 0.012000] CPU: Processor Core ID: 1
[ 0.164102] CPU1: AMD Athlon(tm) 64 X2 Dual Core Processor 4600+
stepping 01
[ 0.164235] Brought up 2 CPUs
[ 0.164238] Total of 2 processors activated (9644.83 BogoMIPS).
[ 0.164417] CPU0 attaching sched-domain:
[ 0.164420] domain 0: span 0-1 level MC
[ 0.164422] groups: 0 1
[ 0.164427] CPU1 attaching sched-domain:
[ 0.164428] domain 0: span 0-1 level MC
[ 0.164430] groups: 1 0
[ 0.164591] devtmpfs: initialized
[ 0.164973] regulator: core version 0.5
[ 0.165034] NET: Registered protocol family 16
[ 0.165124] ACPI: bus type pci registered
[ 0.165203] PCI: MCFG configuration 0: base e0000000 segment 0 buses
0 - 255
[ 0.165207] PCI: MCFG area at e0000000 reserved in E820
[ 0.165208] PCI: Using MMCONFIG for extended config space
[ 0.165210] PCI: Using configuration type 1 for base access
[ 0.165535] bio: create slab <bio-0> at 0
[ 0.166252] ACPI: EC: Look up EC in DSDT
[ 0.173314] ACPI: Interpreter enabled
[ 0.173323] ACPI: (supports S0 S1 S4 S5)
[ 0.173344] ACPI: Using IOAPIC for interrupt routing
[ 0.180210] ACPI: No dock devices found.
[ 0.181094] ACPI: PCI Root Bridge [PCI0] (0000:00)
[ 0.181192] HPET not enabled in BIOS. You might try hpet=force boot
option
[ 0.181210] pci 0000:00:01.1: reg 10 io port: [0xfc00-0xfc1f]
[ 0.181217] pci 0000:00:01.1: reg 20 io port: [0x4c00-0x4c3f]
[ 0.181221] pci 0000:00:01.1: reg 24 io port: [0x4c40-0x4c7f]
[ 0.181231] pci 0000:00:01.1: PME# supported from D3hot D3cold
[ 0.181234] pci 0000:00:01.1: PME# disabled
[ 0.181252] pci 0000:00:02.0: reg 10 32bit mmio: [0xfe02f000-0xfe02ffff]
[ 0.181268] pci 0000:00:02.0: supports D1 D2
[ 0.181270] pci 0000:00:02.0: PME# supported from D0 D1 D2 D3hot D3cold
[ 0.181272] pci 0000:00:02.0: PME# disabled
[ 0.181290] pci 0000:00:02.1: reg 10 32bit mmio: [0xfeb00000-0xfeb000ff]
[ 0.181308] pci 0000:00:02.1: supports D1 D2
[ 0.181310] pci 0000:00:02.1: PME# supported from D0 D1 D2 D3hot D3cold
[ 0.181313] pci 0000:00:02.1: PME# disabled
[ 0.181333] pci 0000:00:04.0: reg 10 io port: [0xf000-0xf0ff]
[ 0.181337] pci 0000:00:04.0: reg 14 io port: [0xec00-0xecff]
[ 0.181341] pci 0000:00:04.0: reg 18 32bit mmio: [0xfe02d000-0xfe02dfff]
[ 0.181354] pci 0000:00:04.0: supports D1 D2
[ 0.181374] pci 0000:00:06.0: reg 20 io port: [0xe000-0xe00f]
[ 0.181396] pci 0000:00:07.0: reg 10 io port: [0x9f0-0x9f7]
[ 0.181400] pci 0000:00:07.0: reg 14 io port: [0xbf0-0xbf3]
[ 0.181404] pci 0000:00:07.0: reg 18 io port: [0x970-0x977]
[ 0.181407] pci 0000:00:07.0: reg 1c io port: [0xb70-0xb73]
[ 0.181411] pci 0000:00:07.0: reg 20 io port: [0xcc00-0xcc0f]
[ 0.181414] pci 0000:00:07.0: reg 24 32bit mmio: [0xfe02b000-0xfe02bfff]
[ 0.181436] pci 0000:00:08.0: reg 10 io port: [0x9e0-0x9e7]
[ 0.181439] pci 0000:00:08.0: reg 14 io port: [0xbe0-0xbe3]
[ 0.181443] pci 0000:00:08.0: reg 18 io port: [0x960-0x967]
[ 0.181446] pci 0000:00:08.0: reg 1c io port: [0xb60-0xb63]
[ 0.181450] pci 0000:00:08.0: reg 20 io port: [0xb800-0xb80f]
[ 0.181454] pci 0000:00:08.0: reg 24 32bit mmio: [0xfe02a000-0xfe02afff]
[ 0.181485] pci 0000:00:0a.0: reg 10 32bit mmio: [0xfe029000-0xfe029fff]
[ 0.181489] pci 0000:00:0a.0: reg 14 io port: [0xb400-0xb407]
[ 0.181503] pci 0000:00:0a.0: supports D1 D2
[ 0.181505] pci 0000:00:0a.0: PME# supported from D0 D1 D2 D3hot D3cold
[ 0.181508] pci 0000:00:0a.0: PME# disabled
[ 0.181538] pci 0000:00:0b.0: PME# supported from D0 D1 D2 D3hot D3cold
[ 0.181540] pci 0000:00:0b.0: PME# disabled
[ 0.181570] pci 0000:00:0c.0: PME# supported from D0 D1 D2 D3hot D3cold
[ 0.181572] pci 0000:00:0c.0: PME# disabled
[ 0.181601] pci 0000:00:0d.0: PME# supported from D0 D1 D2 D3hot D3cold
[ 0.181604] pci 0000:00:0d.0: PME# disabled
[ 0.181635] pci 0000:00:0e.0: PME# supported from D0 D1 D2 D3hot D3cold
[ 0.181637] pci 0000:00:0e.0: PME# disabled
[ 0.181731] pci 0000:01:09.0: reg 10 32bit mmio: [0xfdeff000-0xfdefffff]
[ 0.181735] pci 0000:01:09.0: reg 14 io port: [0xac00-0xac3f]
[ 0.181740] pci 0000:01:09.0: reg 18 32bit mmio: [0xfdd00000-0xfddfffff]
[ 0.181752] pci 0000:01:09.0: reg 30 32bit mmio pref: [0x000000-0x0fffff]
[ 0.181763] pci 0000:01:09.0: supports D1 D2
[ 0.181765] pci 0000:01:09.0: PME# supported from D0 D1 D2 D3hot D3cold
[ 0.181768] pci 0000:01:09.0: PME# disabled
[ 0.181787] pci 0000:00:09.0: transparent bridge
[ 0.181790] pci 0000:00:09.0: bridge io port: [0xa000-0xafff]
[ 0.181793] pci 0000:00:09.0: bridge 32bit mmio: [0xfdc00000-0xfdefffff]
[ 0.181796] pci 0000:00:09.0: bridge 32bit mmio pref:
[0xfdf00000-0xfdffffff]
[ 0.181825] pci 0000:00:0b.0: bridge io port: [0x9000-0x9fff]
[ 0.181828] pci 0000:00:0b.0: bridge 32bit mmio: [0xfdb00000-0xfdbfffff]
[ 0.181831] pci 0000:00:0b.0: bridge 64bit mmio pref:
[0xfda00000-0xfdafffff]
[ 0.181859] pci 0000:00:0c.0: bridge io port: [0x8000-0x8fff]
[ 0.181862] pci 0000:00:0c.0: bridge 32bit mmio: [0xfd900000-0xfd9fffff]
[ 0.181866] pci 0000:00:0c.0: bridge 64bit mmio pref:
[0xfd800000-0xfd8fffff]
[ 0.181895] pci 0000:00:0d.0: bridge io port: [0x7000-0x7fff]
[ 0.181898] pci 0000:00:0d.0: bridge 32bit mmio: [0xfd700000-0xfd7fffff]
[ 0.181901] pci 0000:00:0d.0: bridge 64bit mmio pref:
[0xfd600000-0xfd6fffff]
[ 0.181925] pci 0000:05:00.0: reg 10 32bit mmio: [0xfa000000-0xfaffffff]
[ 0.181932] pci 0000:05:00.0: reg 14 64bit mmio pref:
[0xd0000000-0xdfffffff]
[ 0.181940] pci 0000:05:00.0: reg 1c 64bit mmio: [0xf8000000-0xf9ffffff]
[ 0.181944] pci 0000:05:00.0: reg 24 io port: [0x6c00-0x6c7f]
[ 0.181949] pci 0000:05:00.0: reg 30 32bit mmio pref: [0x000000-0x01ffff]
[ 0.181995] pci 0000:00:0e.0: bridge io port: [0x6000-0x6fff]
[ 0.181998] pci 0000:00:0e.0: bridge 32bit mmio: [0xf8000000-0xfbffffff]
[ 0.182001] pci 0000:00:0e.0: bridge 64bit mmio pref:
[0xd0000000-0xdfffffff]
[ 0.182010] pci_bus 0000:00: on NUMA node 0
[ 0.182014] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
[ 0.182226] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.HUB0._PRT]
[ 0.236287] ACPI: PCI Interrupt Link [LNK1] (IRQs 3 4 5 7 9 10 11 12
14 15) *0, disabled.
[ 0.236429] ACPI: PCI Interrupt Link [LNK2] (IRQs 3 4 5 7 9 10 11 12
14 15) *0, disabled.
[ 0.236567] ACPI: PCI Interrupt Link [LNK3] (IRQs 3 4 5 *7 9 10 11 12
14 15)
[ 0.236704] ACPI: PCI Interrupt Link [LNK4] (IRQs 3 4 *5 7 9 10 11 12
14 15)
[ 0.236839] ACPI: PCI Interrupt Link [LNK5] (IRQs 3 4 5 7 9 10 11 12
14 15) *0, disabled.
[ 0.236976] ACPI: PCI Interrupt Link [LUBA] (IRQs 3 4 5 *7 9 10 11 12
14 15)
[ 0.237111] ACPI: PCI Interrupt Link [LUBB] (IRQs 3 4 5 7 9 10 11 12
14 15) *0, disabled.
[ 0.237248] ACPI: PCI Interrupt Link [LMAC] (IRQs 3 4 5 7 9 10 *11 12
14 15)
[ 0.237385] ACPI: PCI Interrupt Link [LACI] (IRQs *3 4 5 7 9 10 11 12
14 15)
[ 0.237522] ACPI: PCI Interrupt Link [LMCI] (IRQs 3 4 5 7 9 *10 11 12
14 15)
[ 0.237658] ACPI: PCI Interrupt Link [LSMB] (IRQs *3 4 5 7 9 10 11 12
14 15)
[ 0.237795] ACPI: PCI Interrupt Link [LUB2] (IRQs 3 4 *5 7 9 10 11 12
14 15)
[ 0.237931] ACPI: PCI Interrupt Link [LIDE] (IRQs 3 4 5 7 9 10 11 12
14 15) *0, disabled.
[ 0.238077] ACPI: PCI Interrupt Link [LSID] (IRQs 3 4 5 7 9 10 *11 12
14 15)
[ 0.238221] ACPI: PCI Interrupt Link [LFID] (IRQs 3 4 5 7 9 *10 11 12
14 15)
[ 0.238365] ACPI: PCI Interrupt Link [LPCA] (IRQs 3 4 5 7 9 10 11 12
14 15) *0, disabled.
[ 0.238520] ACPI: PCI Interrupt Link [APC1] (IRQs 16) *0, disabled.
[ 0.238671] ACPI: PCI Interrupt Link [APC2] (IRQs 17) *0, disabled.
[ 0.238821] ACPI: PCI Interrupt Link [APC3] (IRQs 18) *0
[ 0.238972] ACPI: PCI Interrupt Link [APC4] (IRQs 19) *0
[ 0.239068] ACPI: PCI Interrupt Link [APC5] (IRQs *16), disabled.
[ 0.239230] ACPI: PCI Interrupt Link [APCF] (IRQs 20 21 22 23) *0
[ 0.239388] ACPI: PCI Interrupt Link [APCG] (IRQs 20 21 22 23) *0,
disabled.
[ 0.239546] ACPI: PCI Interrupt Link [APCH] (IRQs 20 21 22 23) *0
[ 0.239703] ACPI: PCI Interrupt Link [APCJ] (IRQs 20 21 22 23) *0
[ 0.239860] ACPI: PCI Interrupt Link [APCK] (IRQs 20 21 22 23) *0
[ 0.240027] ACPI: PCI Interrupt Link [APCS] (IRQs 20 21 22 23) *0
[ 0.240184] ACPI: PCI Interrupt Link [APCL] (IRQs 20 21 22 23) *0
[ 0.240342] ACPI: PCI Interrupt Link [APCZ] (IRQs 20 21 22 23) *0,
disabled.
[ 0.240507] ACPI: PCI Interrupt Link [APSI] (IRQs 20 21 22 23) *0
[ 0.240673] ACPI: PCI Interrupt Link [APSJ] (IRQs 20 21 22 23) *0
[ 0.240838] ACPI: PCI Interrupt Link [APCP] (IRQs 20 21 22 23) *0,
disabled.
[ 0.240953] vgaarb: device added:
PCI:0000:05:00.0,decodes=io+mem,owns=io+mem,locks=none
[ 0.240955] vgaarb: loaded
[ 0.241044] PCI: Using ACPI for IRQ routing
[ 0.241194] Switching to clocksource jiffies
[ 0.242416] pnp: PnP ACPI init
[ 0.242428] ACPI: bus type pnp registered
[ 0.246873] pnp 00:0c: mem resource (0xf0000-0xf3fff) overlaps
0000:01:09.0 BAR 6 (0x0-0xfffff), disabling
[ 0.246877] pnp 00:0c: mem resource (0xf4000-0xf7fff) overlaps
0000:01:09.0 BAR 6 (0x0-0xfffff), disabling
[ 0.246881] pnp 00:0c: mem resource (0xf8000-0xfbfff) overlaps
0000:01:09.0 BAR 6 (0x0-0xfffff), disabling
[ 0.246884] pnp 00:0c: mem resource (0xfc000-0xfffff) overlaps
0000:01:09.0 BAR 6 (0x0-0xfffff), disabling
[ 0.246888] pnp 00:0c: mem resource (0x0-0x9ffff) overlaps
0000:01:09.0 BAR 6 (0x0-0xfffff), disabling
[ 0.246930] pnp: PnP ACPI: found 13 devices
[ 0.246931] ACPI: ACPI bus type pnp unregistered
[ 0.246935] PnPBIOS: Disabled by ACPI PNP
[ 0.246948] system 00:01: ioport range 0x4000-0x407f has been reserved
[ 0.246951] system 00:01: ioport range 0x4080-0x40ff has been reserved
[ 0.246954] system 00:01: ioport range 0x4400-0x447f has been reserved
[ 0.246957] system 00:01: ioport range 0x4480-0x44ff has been reserved
[ 0.246959] system 00:01: ioport range 0x4800-0x487f has been reserved
[ 0.246962] system 00:01: ioport range 0x4880-0x48ff has been reserved
[ 0.246967] system 00:02: ioport range 0x4d0-0x4d1 has been reserved
[ 0.246970] system 00:02: ioport range 0x290-0x29e has been reserved
[ 0.246977] system 00:0b: iomem range 0xe0000000-0xefffffff has been
reserved
[ 0.246982] system 00:0c: iomem range 0x9fff0000-0x9fffffff could not
be reserved
[ 0.246985] system 00:0c: iomem range 0xffff0000-0xffffffff has been
reserved
[ 0.246988] system 00:0c: iomem range 0x100000-0x9ffeffff could not
be reserved
[ 0.246991] system 00:0c: iomem range 0xfec00000-0xfec00fff could not
be reserved
[ 0.246994] system 00:0c: iomem range 0xfee00000-0xfeefffff has been
reserved
[ 0.246997] system 00:0c: iomem range 0xfefff000-0xfeffffff has been
reserved
[ 0.247000] system 00:0c: iomem range 0xfff80000-0xfff80fff has been
reserved
[ 0.247003] system 00:0c: iomem range 0xfff90000-0xfffbffff has been
reserved
[ 0.247006] system 00:0c: iomem range 0xfffed000-0xfffeffff has been
reserved
[ 0.281782] Switching to clocksource acpi_pm
[ 0.281879] pci 0000:00:09.0: PCI bridge, secondary bus 0000:01
[ 0.281879] pci 0000:00:09.0: IO window: 0xa000-0xafff
[ 0.281879] pci 0000:00:09.0: MEM window: 0xfdc00000-0xfdefffff
[ 0.281879] pci 0000:00:09.0: PREFETCH window: 0xfdf00000-0xfdffffff
[ 0.281879] pci 0000:00:0b.0: PCI bridge, secondary bus 0000:02
[ 0.281879] pci 0000:00:0b.0: IO window: 0x9000-0x9fff
[ 0.281879] pci 0000:00:0b.0: MEM window: 0xfdb00000-0xfdbfffff
[ 0.281879] pci 0000:00:0b.0: PREFETCH window:
0x000000fda00000-0x000000fdafffff
[ 0.281879] pci 0000:00:0c.0: PCI bridge, secondary bus 0000:03
[ 0.281879] pci 0000:00:0c.0: IO window: 0x8000-0x8fff
[ 0.281879] pci 0000:00:0c.0: MEM window: 0xfd900000-0xfd9fffff
[ 0.281879] pci 0000:00:0c.0: PREFETCH window:
0x000000fd800000-0x000000fd8fffff
[ 0.281879] pci 0000:00:0d.0: PCI bridge, secondary bus 0000:04
[ 0.281879] pci 0000:00:0d.0: IO window: 0x7000-0x7fff
[ 0.281879] pci 0000:00:0d.0: MEM window: 0xfd700000-0xfd7fffff
[ 0.281879] pci 0000:00:0d.0: PREFETCH window:
0x000000fd600000-0x000000fd6fffff
[ 0.281879] pci 0000:00:0e.0: PCI bridge, secondary bus 0000:05
[ 0.281879] pci 0000:00:0e.0: IO window: 0x6000-0x6fff
[ 0.281879] pci 0000:00:0e.0: MEM window: 0xf8000000-0xfbffffff
[ 0.281879] pci 0000:00:0e.0: PREFETCH window:
0x000000d0000000-0x000000dfffffff
[ 0.281879] pci 0000:00:09.0: setting latency timer to 64
[ 0.281879] pci 0000:00:0b.0: setting latency timer to 64
[ 0.281879] pci 0000:00:0c.0: setting latency timer to 64
[ 0.281879] pci 0000:00:0d.0: setting latency timer to 64
[ 0.281879] pci 0000:00:0e.0: setting latency timer to 64
[ 0.281879] pci_bus 0000:00: resource 0 io: [0x00-0xffff]
[ 0.281879] pci_bus 0000:00: resource 1 mem: [0x000000-0xffffffff]
[ 0.281879] pci_bus 0000:01: resource 0 io: [0xa000-0xafff]
[ 0.281879] pci_bus 0000:01: resource 1 mem: [0xfdc00000-0xfdefffff]
[ 0.281879] pci_bus 0000:01: resource 2 pref mem [0xfdf00000-0xfdffffff]
[ 0.281879] pci_bus 0000:01: resource 3 io: [0x00-0xffff]
[ 0.281879] pci_bus 0000:01: resource 4 mem: [0x000000-0xffffffff]
[ 0.281879] pci_bus 0000:02: resource 0 io: [0x9000-0x9fff]
[ 0.281879] pci_bus 0000:02: resource 1 mem: [0xfdb00000-0xfdbfffff]
[ 0.281879] pci_bus 0000:02: resource 2 pref mem [0xfda00000-0xfdafffff]
[ 0.281879] pci_bus 0000:03: resource 0 io: [0x8000-0x8fff]
[ 0.281879] pci_bus 0000:03: resource 1 mem: [0xfd900000-0xfd9fffff]
[ 0.281879] pci_bus 0000:03: resource 2 pref mem [0xfd800000-0xfd8fffff]
[ 0.281879] pci_bus 0000:04: resource 0 io: [0x7000-0x7fff]
[ 0.281879] pci_bus 0000:04: resource 1 mem: [0xfd700000-0xfd7fffff]
[ 0.281879] pci_bus 0000:04: resource 2 pref mem [0xfd600000-0xfd6fffff]
[ 0.281879] pci_bus 0000:05: resource 0 io: [0x6000-0x6fff]
[ 0.281879] pci_bus 0000:05: resource 1 mem: [0xf8000000-0xfbffffff]
[ 0.281879] pci_bus 0000:05: resource 2 pref mem [0xd0000000-0xdfffffff]
[ 0.281879] NET: Registered protocol family 2
[ 0.281879] IP route cache hash table entries: 32768 (order: 5,
131072 bytes)
[ 0.281879] TCP established hash table entries: 131072 (order: 8,
1048576 bytes)
[ 0.282339] TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
[ 0.283171] TCP: Hash tables configured (established 131072 bind 65536)
[ 0.283175] TCP reno registered
[ 0.283324] NET: Registered protocol family 1
[ 0.300091] pci 0000:00:00.0: Found enabled HT MSI Mapping
[ 0.300096] pci 0000:00:0b.0: Found disabled HT MSI Mapping
[ 0.300103] pci 0000:00:00.0: Found enabled HT MSI Mapping
[ 0.300108] pci 0000:00:0b.0: Linking AER extended capability
[ 0.300142] pci 0000:00:00.0: Found enabled HT MSI Mapping
[ 0.300146] pci 0000:00:0c.0: Found disabled HT MSI Mapping
[ 0.300153] pci 0000:00:00.0: Found enabled HT MSI Mapping
[ 0.300155] pci 0000:00:0c.0: Linking AER extended capability
[ 0.300192] pci 0000:00:00.0: Found enabled HT MSI Mapping
[ 0.300196] pci 0000:00:0d.0: Found disabled HT MSI Mapping
[ 0.300203] pci 0000:00:00.0: Found enabled HT MSI Mapping
[ 0.300205] pci 0000:00:0d.0: Linking AER extended capability
[ 0.300245] pci 0000:00:00.0: Found enabled HT MSI Mapping
[ 0.300250] pci 0000:00:0e.0: Found disabled HT MSI Mapping
[ 0.300256] pci 0000:00:00.0: Found enabled HT MSI Mapping
[ 0.300259] pci 0000:00:0e.0: Linking AER extended capability
[ 0.300274] pci 0000:01:09.0: Firmware left e100 interrupts enabled;
disabling
[ 0.300284] pci 0000:05:00.0: Boot video device
[ 0.300349] Unpacking initramfs...
[ 0.485635] Freeing initrd memory: 7138k freed
[ 0.496964] audit: initializing netlink socket (disabled)
[ 0.496986] type=2000 audit(1268034175.496:1): initialized
[ 0.497268] highmem bounce pool size: 64 pages
[ 0.497273] HugeTLB registered 4 MB page size, pre-allocated 0 pages
[ 0.498572] VFS: Disk quotas dquot_6.5.2
[ 0.498629] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[ 0.498713] msgmni has been set to 1715
[ 0.498918] alg: No test for stdrng (krng)
[ 0.498969] Block layer SCSI generic (bsg) driver version 0.4 loaded
(major 253)
[ 0.498972] io scheduler noop registered
[ 0.498974] io scheduler anticipatory registered
[ 0.498976] io scheduler deadline registered
[ 0.499007] io scheduler cfq registered (default)
[ 0.499114] pcieport 0000:00:0b.0: irq 24 for MSI/MSI-X
[ 0.499120] pcieport 0000:00:0b.0: setting latency timer to 64
[ 0.499184] pcieport 0000:00:0c.0: irq 25 for MSI/MSI-X
[ 0.499188] pcieport 0000:00:0c.0: setting latency timer to 64
[ 0.499245] pcieport 0000:00:0d.0: irq 26 for MSI/MSI-X
[ 0.499249] pcieport 0000:00:0d.0: setting latency timer to 64
[ 0.499309] pcieport 0000:00:0e.0: irq 27 for MSI/MSI-X
[ 0.499313] pcieport 0000:00:0e.0: setting latency timer to 64
[ 0.499438] isapnp: Scanning for PnP cards...
[ 0.851944] isapnp: No Plug & Play device found
[ 0.853192] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[ 0.853281] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[ 0.853550] 00:08: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[ 0.853695] PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] at
0x60,0x64 irq 1,12
[ 0.856650] serio: i8042 KBD port at 0x60,0x64 irq 1
[ 0.856658] serio: i8042 AUX port at 0x60,0x64 irq 12
[ 0.856721] mice: PS/2 mouse device common for all mice
[ 0.856746] Driver 'rtc_cmos' needs updating - please use bus_type
methods
[ 0.856775] rtc_cmos 00:04: RTC can wake from S4
[ 0.856806] rtc_cmos 00:04: rtc core: registered rtc_cmos as rtc0
[ 0.856829] rtc0: alarms up to one year, y3k, 242 bytes nvram
[ 0.856840] cpuidle: using governor ladder
[ 0.856842] cpuidle: using governor menu
[ 0.856847] No iBFT detected.
[ 0.857194] TCP cubic registered
[ 0.857329] NET: Registered protocol family 10
[ 0.857770] lo: Disabled Privacy Extensions
[ 0.858055] Mobile IPv6
[ 0.858058] NET: Registered protocol family 17
[ 0.858077] Using IPI No-Shortcut mode
[ 0.858143] registered taskstats version 1
[ 0.858423] rtc_cmos 00:04: setting system clock to 2010-03-08
07:42:56 UTC (1268034176)
[ 0.858470] Freeing unused kernel memory: 368k freed
[ 0.858953] Write protecting the kernel text: 2416k
[ 0.858976] Write protecting the kernel read-only data: 872k
[ 0.887978] input: AT Translated Set 2 keyboard as
/devices/platform/i8042/serio0/input/input0
[ 0.940512] fan PNP0C0B:00: registered as cooling_device0
[ 0.940519] ACPI: Fan [FAN] (on)
[ 0.943695] thermal LNXTHERM:01: registered as thermal_zone0
[ 0.943704] ACPI: Thermal Zone [THRM] (22 C)
[ 1.089114] usbcore: registered new interface driver usbfs
[ 1.089144] usbcore: registered new interface driver hub
[ 1.089232] usbcore: registered new device driver usb
[ 1.092488] SCSI subsystem initialized
[ 1.098824] forcedeth: Reverse Engineered nForce ethernet driver.
Version 0.64.
[ 1.099153] ACPI: PCI Interrupt Link [APCH] enabled at IRQ 23
[ 1.099167] forcedeth 0000:00:0a.0: PCI INT A -> Link[APCH] -> GSI 23
(level, low) -> IRQ 23
[ 1.099172] forcedeth 0000:00:0a.0: setting latency timer to 64
[ 1.099238] nv_probe: set workaround bit for reversed mac addr
[ 1.109566] libata version 3.00 loaded.
[ 1.120615] Uniform Multi-Platform E-IDE driver
[ 1.121937] input: Power Button as
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1
[ 1.121949] ACPI: Power Button [PWRB]
[ 1.122064] input: Power Button as
/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
[ 1.122067] ACPI: Power Button [PWRF]
[ 1.125114] e100: Intel(R) PRO/100 Network Driver, 3.5.24-k2-NAPI
[ 1.125117] e100: Copyright(c) 1999-2006 Intel Corporation
[ 1.127208] ACPI: PCI Interrupt Link [APC4] enabled at IRQ 19
[ 1.127224] e100 0000:01:09.0: PCI INT A -> Link[APC4] -> GSI 19
(level, low) -> IRQ 19
[ 1.127301] e100 0000:01:09.0: setting latency timer to 64
[ 1.129695] Floppy drive(s): fd0 is 1.44M
[ 1.130528] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 1.148619] FDC 0 is a post-1991 82077
[ 1.150027] e100 0000:01:09.0: PME# disabled
[ 1.150725] e100: eth0: e100_probe: addr 0xfdeff000, irq 19, MAC addr
00:d0:b7:85:0a:3f
[ 1.616818] forcedeth 0000:00:0a.0: ifname eth1, PHY OUI 0x5043 @ 1,
addr 00:16:17:94:32:d6
[ 1.616822] forcedeth 0000:00:0a.0: highdma csum gbit lnktim desc-v3
[ 1.617271] ACPI: PCI Interrupt Link [APCL] enabled at IRQ 22
[ 1.617287] ehci_hcd 0000:00:02.1: PCI INT B -> Link[APCL] -> GSI 22
(level, low) -> IRQ 22
[ 1.617321] ehci_hcd 0000:00:02.1: setting latency timer to 64
[ 1.617324] ehci_hcd 0000:00:02.1: EHCI Host Controller
[ 1.617379] ehci_hcd 0000:00:02.1: new USB bus registered, assigned
bus number 1
[ 1.617428] ehci_hcd 0000:00:02.1: debug port 1
[ 1.617434] ehci_hcd 0000:00:02.1: cache line size of 64 is not supported
[ 1.617460] ehci_hcd 0000:00:02.1: irq 22, io mem 0xfeb00000
[ 1.629025] ehci_hcd 0000:00:02.1: USB 2.0 started, EHCI 1.00
[ 1.629062] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[ 1.629064] usb usb1: New USB device strings: Mfr=3, Product=2,
SerialNumber=1
[ 1.629067] usb usb1: Product: EHCI Host Controller
[ 1.629069] usb usb1: Manufacturer: Linux 2.6.32-trunk-686 ehci_hcd
[ 1.629071] usb usb1: SerialNumber: 0000:00:02.1
[ 1.629185] usb usb1: configuration #1 chosen from 1 choice
[ 1.629220] hub 1-0:1.0: USB hub found
[ 1.629233] hub 1-0:1.0: 10 ports detected
[ 1.629306] sata_nv 0000:00:07.0: version 3.5
[ 1.629647] ACPI: PCI Interrupt Link [APSI] enabled at IRQ 21
[ 1.629655] sata_nv 0000:00:07.0: PCI INT A -> Link[APSI] -> GSI 21
(level, low) -> IRQ 21
[ 1.629723] sata_nv 0000:00:07.0: setting latency timer to 64
[ 1.629923] scsi0 : sata_nv
[ 1.630075] scsi1 : sata_nv
[ 1.630229] ata1: SATA max UDMA/133 cmd 0x9f0 ctl 0xbf0 bmdma 0xcc00
irq 21
[ 1.630232] ata2: SATA max UDMA/133 cmd 0x970 ctl 0xb70 bmdma 0xcc08
irq 21
[ 1.630255] amd74xx 0000:00:06.0: UDMA133 controller
[ 1.630258] amd74xx 0000:00:06.0: IDE controller (0x10de:0x0053 rev 0xf2)
[ 1.630283] amd74xx 0000:00:06.0: not 100% native mode: will probe
irqs later
[ 1.630289] ide0: BM-DMA at 0xe000-0xe007
[ 1.630297] ide1: BM-DMA at 0xe008-0xe00f
[ 1.630305] Probing IDE interface ide0...
[ 1.639989] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[ 1.916093] hda: ST380011A, ATA DISK drive
[ 1.940021] ata1: SATA link down (SStatus 0 SControl 300)
[ 2.252017] ata2: SATA link down (SStatus 0 SControl 300)
[ 2.252027] hdb: QUANTUM FIREBALLP LM15, ATA DISK drive
[ 2.252069] hda: host max PIO5 wanted PIO255(auto-tune) selected PIO4
[ 2.252505] hda: UDMA/100 mode selected
[ 2.252757] hdb: host max PIO5 wanted PIO255(auto-tune) selected PIO4
[ 2.252997] hdb: UDMA/66 mode selected
[ 2.253327] Probing IDE interface ide1...
[ 2.988089] hdc: TOSHIBA DVD-ROM SD-M1612, ATAPI CD/DVD-ROM drive
[ 3.828014] hdd: PLEXTOR CD-R PX-W1210A, ATAPI CD/DVD-ROM drive
[ 3.828042] hdc: host max PIO5 wanted PIO255(auto-tune) selected PIO4
[ 3.828423] hdc: UDMA/33 mode selected
[ 3.829011] hdd: host max PIO5 wanted PIO255(auto-tune) selected PIO4
[ 3.829094] hdd: MWDMA2 mode selected
[ 3.829208] ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
[ 3.858018] ide1 at 0x170-0x177,0x376 on irq 15
[ 3.867504] ACPI: PCI Interrupt Link [APSJ] enabled at IRQ 20
[ 3.867520] sata_nv 0000:00:08.0: PCI INT A -> Link[APSJ] -> GSI 20
(level, low) -> IRQ 20
[ 3.867608] sata_nv 0000:00:08.0: setting latency timer to 64
[ 3.869041] scsi2 : sata_nv
[ 3.869114] scsi3 : sata_nv
[ 3.869298] ata3: SATA max UDMA/133 cmd 0x9e0 ctl 0xbe0 bmdma 0xb800
irq 20
[ 3.869301] ata4: SATA max UDMA/133 cmd 0x960 ctl 0xb60 bmdma 0xb808
irq 20
[ 3.869614] ACPI: PCI Interrupt Link [APCF] enabled at IRQ 23
[ 3.869620] ohci_hcd 0000:00:02.0: PCI INT A -> Link[APCF] -> GSI 23
(level, low) -> IRQ 23
[ 3.869643] ohci_hcd 0000:00:02.0: setting latency timer to 64
[ 3.869646] ohci_hcd 0000:00:02.0: OHCI Host Controller
[ 3.869666] ohci_hcd 0000:00:02.0: new USB bus registered, assigned
bus number 2
[ 3.869699] ohci_hcd 0000:00:02.0: irq 23, io mem 0xfe02f000
[ 3.926024] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001
[ 3.926027] usb usb2: New USB device strings: Mfr=3, Product=2,
SerialNumber=1
[ 3.926030] usb usb2: Product: OHCI Host Controller
[ 3.926032] usb usb2: Manufacturer: Linux 2.6.32-trunk-686 ohci_hcd
[ 3.926035] usb usb2: SerialNumber: 0000:00:02.0
[ 3.926137] usb usb2: configuration #1 chosen from 1 choice
[ 3.926167] hub 2-0:1.0: USB hub found
[ 3.926178] hub 2-0:1.0: 10 ports detected
[ 4.180020] ata3: SATA link down (SStatus 0 SControl 300)
[ 4.300023] usb 2-7: new low speed USB device using ohci_hcd and
address 2
[ 4.492022] ata4: SATA link down (SStatus 0 SControl 300)
[ 4.503320] ide-cd driver 5.00
[ 4.504845] ide-cd: hdc: ATAPI 48X DVD-ROM drive, 512kB Cache
[ 4.504850] Uniform CD-ROM driver Revision: 3.20
[ 4.505463] ide-gd driver 1.18
[ 4.505521] hda: max request size: 512KiB
[ 4.505752] hda: 156301488 sectors (80026 MB) w/2048KiB Cache,
CHS=16383/255/63
[ 4.505918] hda: cache flushes supported
[ 4.505987] hda: hda1 hda2 <
[ 4.518990] ide-cd: hdd: ATAPI 32X CD-ROM CD-R/RW drive, 2048kB Cache
[ 4.521629] hda5 hda6 hda7 hda8 hda9 hda10 hda11 hda12 >
[ 4.589379] hdb: max request size: 128KiB
[ 4.589644] hdb: 29336832 sectors (15020 MB) w/1900KiB Cache,
CHS=29104/16/63
[ 4.589648] hdb: cache flushes not supported
[ 4.589688] hdb: hdb1
[ 4.684044] usb 2-7: New USB device found, idVendor=051d, idProduct=0002
[ 4.684049] usb 2-7: New USB device strings: Mfr=3, Product=1,
SerialNumber=2
[ 4.684052] usb 2-7: Product: Back-UPS RS 1500 FW:8.g8 .D USB FW:g8
[ 4.684054] usb 2-7: Manufacturer: American Power Conversion
[ 4.684056] usb 2-7: SerialNumber: QB0512132444
[ 4.684170] usb 2-7: configuration #1 chosen from 1 choice
[ 4.700584] usbcore: registered new interface driver hiddev
[ 5.765250] generic-usb 0003:051D:0002.0001: hiddev96,hidraw0: USB
HID v1.10 Device [American Power Conversion Back-UPS RS 1500 FW:8.g8 .D
USB FW:g8 ] on usb-0000:00:02.0-7/input0
[ 5.765296] usbcore: registered new interface driver usbhid
[ 5.765300] usbhid: v2.6:USB HID core driver
[ 5.805220] PM: Starting manual resume from disk
[ 5.853276] kjournald starting. Commit interval 5 seconds
[ 5.853289] EXT3-fs: mounted filesystem with ordered data mode.
[ 7.858131] udev: starting version 151
[ 8.309571] udev: renamed network interface eth0 to eth1
[ 8.343294] udev: renamed network interface eth1_rename to eth0
[ 8.474515] input: PC Speaker as /devices/platform/pcspkr/input/input3
[ 8.479342] processor LNXCPU:00: registered as cooling_device1
[ 8.479403] processor LNXCPU:01: registered as cooling_device2
[ 8.532665] i2c i2c-0: nForce2 SMBus adapter at 0x4c00
[ 8.532690] i2c i2c-1: nForce2 SMBus adapter at 0x4c40
[ 8.854658] Linux agpgart interface v0.103
[ 9.297024] input: ImPS/2 Generic Wheel Mouse as
/devices/platform/i8042/serio1/input/input4
[ 9.325788] nvidia: module license 'NVIDIA' taints kernel.
[ 9.325793] Disabling lock debugging due to kernel taint
[ 10.156599] ACPI: PCI Interrupt Link [APCJ] enabled at IRQ 22
[ 10.156607] Intel ICH 0000:00:04.0: PCI INT A -> Link[APCJ] -> GSI 22
(level, low) -> IRQ 22
[ 10.156653] Intel ICH 0000:00:04.0: setting latency timer to 64
[ 10.258217] ACPI: PCI Interrupt Link [APC3] enabled at IRQ 18
[ 10.258228] nvidia 0000:05:00.0: PCI INT A -> Link[APC3] -> GSI 18
(level, low) -> IRQ 18
[ 10.258234] nvidia 0000:05:00.0: setting latency timer to 64
[ 10.258540] NVRM: loading NVIDIA UNIX x86 Kernel Module 195.30 Fri
Dec 18 13:34:49 PST 2009
[ 10.476019] intel8x0_measure_ac97_clock: measured 54397 usecs (2672
samples)
[ 10.476022] intel8x0: clocking to 46905
[ 10.846831] Adding 2361512k swap on /dev/hda10. Priority:-1
extents:1 across:2361512k
[ 11.029896] EXT3 FS on hda1, internal journal
[ 11.254155] loop: module loaded
[ 11.304671] fuse init (API version 7.13)
[ 11.329457] w83627ehf: Found W83627EHG chip at 0x290
[ 11.329585] ACPI: I/O resource w83627ehf [0x295-0x296] conflicts with
ACPI region SEN1 [0x295-0x296]
[ 11.329659] ACPI: If an ACPI driver is available for this device, you
should use it instead of the native driver
[ 11.393125] device-mapper: uevent: version 1.0.3
[ 11.393364] device-mapper: ioctl: 4.15.0-ioctl (2009-04-01)
initialised: dm-***@redhat.com
[ 13.493232] kjournald starting. Commit interval 5 seconds
[ 13.493422] EXT3 FS on hda5, internal journal
[ 13.493428] EXT3-fs: mounted filesystem with ordered data mode.
[ 13.513555] kjournald starting. Commit interval 5 seconds
[ 13.513744] EXT3 FS on hda6, internal journal
[ 13.513747] EXT3-fs: mounted filesystem with ordered data mode.
[ 13.536477] kjournald starting. Commit interval 5 seconds
[ 13.536644] EXT3 FS on hda7, internal journal
[ 13.536647] EXT3-fs: mounted filesystem with ordered data mode.
[ 13.552140] kjournald starting. Commit interval 5 seconds
[ 13.552313] EXT3 FS on hda8, internal journal
[ 13.552315] EXT3-fs: mounted filesystem with ordered data mode.
[ 13.583730] kjournald starting. Commit interval 5 seconds
[ 13.583924] EXT3 FS on hda9, internal journal
[ 13.583926] EXT3-fs: mounted filesystem with ordered data mode.
[ 13.658673] kjournald starting. Commit interval 5 seconds
[ 13.658891] EXT3 FS on hda11, internal journal
[ 13.658897] EXT3-fs: mounted filesystem with ordered data mode.
[ 13.666848] kjournald starting. Commit interval 5 seconds
[ 13.667033] EXT3 FS on hda12, internal journal
[ 13.667035] EXT3-fs: mounted filesystem with ordered data mode.
[ 13.677528] kjournald starting. Commit interval 5 seconds
[ 13.677845] EXT3 FS on hdb1, internal journal
[ 13.677847] EXT3-fs: mounted filesystem with ordered data mode.
[ 15.727563] ip_tables: (C) 2000-2006 Netfilter Core Team
[ 15.769306] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
[ 15.770017] CONFIG_NF_CT_ACCT is deprecated and will be removed soon.
Please use
[ 15.770019] nf_conntrack.acct=1 kernel parameter, acct=1 nf_conntrack
module option or
[ 15.770021] sysctl net.netfilter.nf_conntrack_acct=1 to enable it.
[ 19.289728] powernow-k8: Found 1 AMD Athlon(tm) 64 X2 Dual Core
Processor 4600+ processors (2 cpu cores) (version 2.20.00)
[ 19.289754] [Firmware Bug]: powernow-k8: No compatible ACPI _PSS
objects found.
[ 19.289755] [Firmware Bug]: powernow-k8: Try again with latest BIOS.
[ 27.560017] eth0: no IPv6 routers present
[ 31.438830] hdd: task_pio_intr: status=0x51 { DriveReady SeekComplete
Error }
[ 31.439014] hdd: task_pio_intr: error=0x04 { AbortedCommand }
[ 31.439150] hdd: possibly failed opcode: 0xec
[ 33.392823] vboxdrv: Trying to deactivate the NMI watchdog permanently...
[ 33.392829] vboxdrv: Warning: 2.6.31+ kernel detected. Most likely
the hardware performance
[ 33.392830] vboxdrv: counter framework which can generate NMIs is
active. You have to prevent
[ 33.392832] vboxdrv: the usage of hardware performance counters by
[ 33.392833] vboxdrv: echo 2 > /proc/sys/kernel/perf_counter_paranoid
[ 33.393072] vboxdrv: Found 2 processor cores.
[ 33.393219] vboxdrv: fAsync=1 offMin=0x1ad284 offMax=0x1ad284
[ 33.393883] vboxdrv: TSC mode is 'asynchronous', kernel timer mode is
'normal'.
[ 33.393885] vboxdrv: Successfully loaded version 3.1.4 (interface
0x00100001).
[ 36.692837] lp: driver loaded but no devices found
[ 36.707066] ppdev: user-space parallel port driver
Post by Darren Salt
Post by Ant
Post by Darren Salt
Post by Ant
So how can I test this with another bootable tool like memtest86+?
Boot from USB or CD, drop to a text console, stress it with a kernel
compile or something (preferably without touching disk). Wait. :-)
Hmm, I did that in my regular Debian and no problems! I used sys_basher,
unrar 10 GB of datas, etc. I can't make it happen with stress tests. Most
of the kernel panics happened when idled! :D
Fine; then let it idle for a while too...
Um, how with the tests?
--
"A centipede is an ant made to Canadian/government specs." --unknown
/\___/\
/ /\ /\ \ Phil./Ant @ http://antfarm.ma.cx (Personal Web Site)
| |o o| | Ant's Quality Foraged Links: http://aqfl.net
\ _ / Nuke ANT from e-mail address: ***@earthlink.netANT
( ) or ***@zimage.com
Ant is currently not listening to any songs on his home computer.
Ant
2010-03-08 16:20:04 UTC
Permalink
FYI, idling in KNOPPIX v6.2.1 boot CD for in text mode/console over five
hours overnight had no problems and errors. I didn't see any machine
check errors in its dmesg. I couldn't get mcelog to work (can't find
/dev/mcelog) as well.
--
"A marvelous creature. A model of specialization... Who else could suck
an ant up his nose and enjoy it?" --About anteaters, "B.C." strip by
Johnny Hart
/\___/\
/ /\ /\ \ Phil./Ant @ http://antfarm.ma.cx (Personal Web Site)
| |o o| | Ant's Quality Foraged Links: http://aqfl.net
\ _ / Nuke ANT from e-mail address: ***@earthlink.netANT
( ) or ***@zimage.com
Ant is currently not listening to any songs on his home computer.
Ant
2010-03-07 20:01:52 UTC
Permalink
I ran memtest86+ v4.00 overnight again for over five hours and no errors
after two passed test. The third test was on test #8, and I was sure
that would pass too so I aborted it and rebooted to use the box.

I just finished running sys_basher
(http://www.polybus.com/sys_basher_web/) and ran it in my Debian a few
times in the past. Still no errors or crashes.

Weird stuff.
Post by Ant
Uh oh. I just discovered mcelog and something new and scary in its
Mar 6 01:19:37 foobar kernel: [15299.988025] Machine check events logged
Mar 6 01:42:07 foobar kernel: [16649.989021] Machine check events logged
Mar 6 02:05:19 foobar -- MARK --
Mar 6 02:19:37 foobar kernel: [18899.989024] Machine check events logged
Mar 6 02:37:07 foobar kernel: [19949.988027] Machine check events logged
Mar 6 03:05:19 foobar -- MARK --
Mar 6 03:24:37 foobar kernel: [22799.989023] Machine check events logged
Mar 6 03:45:19 foobar -- MARK --
Mar 6 04:05:19 foobar -- MARK --
Mar 6 04:25:19 foobar -- MARK --
Mar 6 04:45:19 foobar -- MARK --
Mar 6 05:02:07 foobar kernel: [28649.989023] Machine check events logged
Mar 6 05:25:19 foobar -- MARK --
Mar 6 05:45:19 foobar -- MARK --
Mar 6 06:05:19 foobar -- MARK --
Mar 6 06:24:37 foobar kernel: [33599.989027] Machine check events logged
Mar 6 06:33:13 foobar syslogd 1.5.0#5: restart.
Mar 6 06:45:19 foobar -- MARK --
Mar 6 07:05:19 foobar -- MARK --
Mar 6 07:25:19 foobar -- MARK --
Mar 6 07:45:19 foobar -- MARK --
Mar 6 08:05:19 foobar -- MARK --
Mar 6 08:17:07 foobar kernel: [40349.989022] Machine check events logged
Mar 6 08:24:37 foobar kernel: [40799.988036] Machine check events logged
Mar 6 08:45:19 foobar -- MARK --
Mar 6 08:52:09 foobar mcelog: HARDWARE ERROR. This is *NOT* a software
problem!
Mar 6 08:52:09 foobar mcelog: Please contact your hardware vendor
Mar 6 08:52:09 foobar mcelog: MCE 0
Mar 6 08:52:09 foobar mcelog: CPU 1 1 instruction cache
Mar 6 08:52:09 foobar mcelog: ADDR c11b6ff0
Mar 6 08:52:09 foobar mcelog: TIME 1267894329 Sat Mar 6 08:52:09 2010
Mar 6 08:52:09 foobar mcelog: TLB parity error in virtual array
Mar 6 08:52:09 foobar mcelog: TLB error 'instruction transaction, level 1'
Mar 6 08:52:09 foobar mcelog: STATUS 9400000000010011 MCGSTATUS 0
Mar 6 08:52:09 foobar mcelog: MCGCAP 105 APICID 1 SOCKETID 0
Mar 6 08:52:09 foobar mcelog: CPUID Vendor AMD Family 15 Model 43
Mar 6 08:52:09 foobar mcelog: HARDWARE ERROR. This is *NOT* a software
problem!
Mar 6 08:52:09 foobar mcelog: Please contact your hardware vendor
Mar 6 08:52:09 foobar mcelog: MCE 1
Mar 6 08:52:09 foobar mcelog: CPU 1 1 instruction cache
Mar 6 08:52:09 foobar mcelog: ADDR c11b6ff0
Mar 6 08:52:09 foobar mcelog: TIME 1267894329 Sat Mar 6 08:52:09 2010
Mar 6 08:52:09 foobar mcelog: TLB parity error in virtual array
Mar 6 08:52:09 foobar mcelog: TLB error 'instruction transaction, level 1'
Mar 6 08:52:09 foobar mcelog: STATUS 9400000000010011 MCGSTATUS 0
Mar 6 08:52:09 foobar mcelog: MCGCAP 105 APICID 1 SOCKETID 0
Mar 6 08:52:09 foobar mcelog: CPUID Vendor AMD Family 15 Model 43
Mar 6 08:52:09 foobar mcelog: HARDWARE ERROR. This is *NOT* a software
problem!
Mar 6 08:52:09 foobar mcelog: Please contact your hardware vendor
Mar 6 08:52:09 foobar mcelog: MCE 2
Mar 6 08:52:09 foobar mcelog: CPU 1 1 instruction cache
Mar 6 08:52:09 foobar mcelog: ADDR c11b6ff0
Mar 6 08:52:09 foobar mcelog: TIME 1267894329 Sat Mar 6 08:52:09 2010
Mar 6 08:52:09 foobar mcelog: TLB parity error in virtual array
Mar 6 08:52:09 foobar mcelog: TLB error 'instruction transaction, level 1'
Mar 6 08:52:09 foobar mcelog: STATUS 9400000000010011 MCGSTATUS 0
Mar 6 08:52:09 foobar mcelog: MCGCAP 105 APICID 1 SOCKETID 0
Mar 6 08:52:09 foobar mcelog: CPUID Vendor AMD Family 15 Model 43
Mar 6 08:52:09 foobar mcelog: HARDWARE ERROR. This is *NOT* a software
problem!
Mar 6 08:52:09 foobar mcelog: Please contact your hardware vendor
Mar 6 08:52:09 foobar mcelog: MCE 3
Mar 6 08:52:09 foobar mcelog: CPU 1 1 instruction cache
Mar 6 08:52:09 foobar mcelog: ADDR c11b6ff0
Mar 6 08:52:09 foobar mcelog: TIME 1267894329 Sat Mar 6 08:52:09 2010
Mar 6 08:52:09 foobar mcelog: TLB parity error in virtual array
Mar 6 08:52:09 foobar mcelog: TLB error 'instruction transaction, level 1'
Mar 6 08:52:09 foobar mcelog: STATUS 9400000000010011 MCGSTATUS 0
Mar 6 08:52:09 foobar mcelog: MCGCAP 105 APICID 1 SOCKETID 0
Mar 6 08:52:09 foobar mcelog: CPUID Vendor AMD Family 15 Model 43
Mar 6 08:52:09 foobar mcelog: HARDWARE ERROR. This is *NOT* a software
problem!
Mar 6 08:52:09 foobar mcelog: Please contact your hardware vendor
Mar 6 08:52:09 foobar mcelog: MCE 4
Mar 6 08:52:09 foobar mcelog: CPU 1 1 instruction cache
Mar 6 08:52:09 foobar mcelog: ADDR c11b6ff0
Mar 6 08:52:09 foobar mcelog: TIME 1267894329 Sat Mar 6 08:52:09 2010
Mar 6 08:52:09 foobar mcelog: TLB parity error in virtual array
Mar 6 08:52:09 foobar mcelog: TLB error 'instruction transaction, level 1'
Mar 6 08:52:09 foobar mcelog: STATUS 9400000000010011 MCGSTATUS 0
Mar 6 08:52:09 foobar mcelog: MCGCAP 105 APICID 1 SOCKETID 0
Mar 6 08:52:09 foobar mcelog: CPUID Vendor AMD Family 15 Model 43
Mar 6 08:52:09 foobar mcelog: HARDWARE ERROR. This is *NOT* a software
problem!
Mar 6 08:52:09 foobar mcelog: Please contact your hardware vendor
Mar 6 08:52:09 foobar mcelog: MCE 5
Mar 6 08:52:09 foobar mcelog: CPU 1 1 instruction cache
Mar 6 08:52:09 foobar mcelog: ADDR c11b6ff0
Mar 6 08:52:09 foobar mcelog: TIME 1267894329 Sat Mar 6 08:52:09 2010
Mar 6 08:52:09 foobar mcelog: TLB parity error in virtual array
Mar 6 08:52:09 foobar mcelog: TLB error 'instruction transaction, level 1'
Mar 6 08:52:09 foobar mcelog: STATUS 9400000000010011 MCGSTATUS 0
Mar 6 08:52:09 foobar mcelog: MCGCAP 105 APICID 1 SOCKETID 0
Mar 6 08:52:09 foobar mcelog: CPUID Vendor AMD Family 15 Model 43
Mar 6 08:52:09 foobar mcelog: HARDWARE ERROR. This is *NOT* a software
problem!
Mar 6 08:52:09 foobar mcelog: Please contact your hardware vendor
Mar 6 08:52:09 foobar mcelog: MCE 6
Mar 6 08:52:09 foobar mcelog: CPU 1 1 instruction cache
Mar 6 08:52:09 foobar mcelog: ADDR c11b6ff0
Mar 6 08:52:09 foobar mcelog: TIME 1267894329 Sat Mar 6 08:52:09 2010
Mar 6 08:52:09 foobar mcelog: TLB parity error in virtual array
Mar 6 08:52:09 foobar mcelog: TLB error 'instruction transaction, level 1'
Mar 6 08:52:09 foobar mcelog: STATUS 9400000000010011 MCGSTATUS 0
Mar 6 08:52:09 foobar mcelog: MCGCAP 105 APICID 1 SOCKETID 0
Mar 6 08:52:09 foobar mcelog: CPUID Vendor AMD Family 15 Model 43
Mar 6 08:52:09 foobar mcelog: HARDWARE ERROR. This is *NOT* a software
problem!
Mar 6 08:52:09 foobar mcelog: Please contact your hardware vendor
Mar 6 08:52:09 foobar mcelog: MCE 7
Mar 6 08:52:09 foobar mcelog: CPU 1 1 instruction cache
Mar 6 08:52:09 foobar mcelog: ADDR c11b6ff0
Mar 6 08:52:09 foobar mcelog: TIME 1267894329 Sat Mar 6 08:52:09 2010
Mar 6 08:52:09 foobar mcelog: TLB parity error in virtual array
Mar 6 08:52:09 foobar mcelog: TLB error 'instruction transaction, level 1'
Mar 6 08:52:09 foobar mcelog: STATUS 9400000000010011 MCGSTATUS 0
Mar 6 08:52:09 foobar mcelog: MCGCAP 105 APICID 1 SOCKETID 0
Mar 6 08:52:09 foobar mcelog: CPUID Vendor AMD Family 15 Model 43
Mar 6 08:52:09 foobar mcelog: HARDWARE ERROR. This is *NOT* a software
problem!
Mar 6 08:52:09 foobar mcelog: Please contact your hardware vendor
Mar 6 08:52:09 foobar mcelog: MCE 8
Mar 6 08:52:09 foobar mcelog: CPU 1 1 instruction cache
Mar 6 08:52:09 foobar mcelog: ADDR c11b6ff0
Mar 6 08:52:09 foobar mcelog: TIME 1267894329 Sat Mar 6 08:52:09 2010
Mar 6 08:52:09 foobar mcelog: TLB parity error in virtual array
Mar 6 08:52:09 foobar mcelog: TLB error 'instruction transaction, level 1'
Mar 6 08:52:09 foobar mcelog: STATUS 9400000000010011 MCGSTATUS 0
Mar 6 08:52:09 foobar mcelog: MCGCAP 105 APICID 1 SOCKETID 0
Mar 6 08:52:09 foobar mcelog: CPUID Vendor AMD Family 15 Model 43
What does that mean? Dying CPU (had it since 12/24/2006)? Maybe that's
why memtest86+ didn't find any problems last week.
Post by Ant
Hello.
Is /var/log/syslog the only place where Linux keeps records of kernel
(v2.6.30 and v2.6.32) panics? dmesg and /var/log/messages doesn't seem
to show anything about the crashes unless I am misreading them. I am
trying to figure out a rare and random kernel panic issue on my old
Debian box.
I know it's not X because I exited it, logged out of bash, went into
fullscreen text console's login screen (I boot up my Debian to text
mode, log into bash, and use startx command to go to X), and saw a bunch
of datas (e.g., memory addresses and codes) on my screen from the kernel
crash. However, its data dump was too long and my computer was in frozen
mode with two blinking PS/2 keyboard lights (caps and scroll lock) so I
couldn't scroll up or copy and paste.
I poked around in my Debian and on the Web. I read that kernel panic
errors/datas can be found in /var/log/syslog (dmesg didn't show me
# cat /var/log/syslog
...
Mar 4 23:12:07 foobar smartd[2647]: Device: /dev/hda, SMART Usage
Attribute: 194 Temperature_Celsius changed from 30 to 31
...
Mar 5 15:11:31 foobar smartd[2610]: Device: /dev/hda, SMART Prefailure
Attribute: 1 Raw_Read_Error_Rate changed from 58 to 59
Mar 5 15:11:31 foobar smartd[2610]: Device: /dev/hda, SMART Usage
Attribute: 195 Hardware_ECC_Recovered changed from 58 to 59
Mar 5 15:15:01 foobar /USR/SBIN/CRON[8815]: (root) CMD (command -v
debian-sa1 > /dev/null && debian-sa1 1 1)
Mar 5 15:17:01 foobar /USR/SBIN/CRON[11199]: (root) CMD ( cd / &&
run-parts --report /etc/cron.hourly)
Mar 5 15:25:01 foobar /USR/SBIN/CRON[20721]: (root) CMD (command -v
debian-sa1 > /dev/null && debian-sa1 1 1)
Mar 5 15:35:01 foobar /USR/SBIN/CRON[32588]: (root) CMD (command -v
debian-sa1 > /dev/null && debian-sa1 1 1)
Mar 5 15:45:01 foobar /USR/SBIN/CRON[12129]: (root) CMD (command -v
debian-sa1 > /dev/null && debian-sa1 1 1)
Mar 5 15:55:01 foobar /USR/SBIN/CRON[23947]: (root) CMD (command -v
debian-sa1 > /dev/null && debian-sa1 1 1)
< rebooted my crashed PC from its kernel panic >
Mar 5 21:05:19 foobar syslogd 1.5.0#5: restart.
...
I couldn't find any similiar from an earlier one like (don't think
...
Mar 5 05:17:01 foobar /USR/SBIN/CRON[26833]: (root) CMD ( cd / &&
run-parts --report /etc/cron.hourly)
Mar 5 05:25:01 foobar /USR/SBIN/CRON[29514]: (root) CMD (command -v
debian-sa1 > /dev/null && debian-sa1 1 1)
Mar 5 05:35:01 foobar /USR/SBIN/CRON[372]: (root) CMD (command -v
debian-sa1 > /dev/null && debian-sa1 1 1)
Mar 5 05:45:01 foobar /USR/SBIN/CRON[3772]: (root) CMD (command -v
debian-sa1 > /dev/null && debian-sa1 1 1)
Mar 5 05:55:01 foobar /USR/SBIN/CRON[7160]: (root) CMD (command -v
debian-sa1 > /dev/null && debian-sa1 1 1)
Mar 5 06:41:19 foobar syslogd 1.5.0#5: restart.
...
I saw LKCD (http://lkcd.sourceforge.net/ and
http://sourceforge.net/projects/lkcd/files/), but it seems to be
outdated? I also couldn't find a Debian package of it, so I don't know
if I should even try it to get more datas.
And yes, I already tried memtest86+ v4.00 and it came out no errors
after six hours with its default tests. I will try it again later just
in case.
Thank you in advance. :)
--
"When the ant grows wings it is about to die." --Arabic
/\___/\
/ /\ /\ \ Phil./Ant @ http://antfarm.ma.cx (Personal Web Site)
| |o o| | Ant's Quality Foraged Links: http://aqfl.net
\ _ / Nuke ANT from e-mail address: ***@earthlink.netANT
( ) or ***@zimage.com
Ant is currently not listening to any songs on his home computer.
Tecknode
2010-03-09 17:47:57 UTC
Permalink
Post by Ant
Hello.
Is /var/log/syslog the only place where Linux keeps records of kernel
(v2.6.30 and v2.6.32) panics? dmesg and /var/log/messages doesn't seem
to show anything about the crashes unless I am misreading them. I am
trying to figure out a rare and random kernel panic issue on my old
Debian box.
I know it's not X because I exited it, logged out of bash, went into
fullscreen text console's login screen (I boot up my Debian to text
mode, log into bash, and use startx command to go to X), and saw a bunch
of datas (e.g., memory addresses and codes) on my screen from the kernel
crash. However, its data dump was too long and my computer was in frozen
mode with two blinking PS/2 keyboard lights (caps and scroll lock) so I
couldn't scroll up or copy and paste.
I poked around in my Debian and on the Web. I read that kernel panic
errors/datas can be found in /var/log/syslog (dmesg didn't show me
# cat /var/log/syslog
...
Mar 4 23:12:07 foobar smartd[2647]: Device: /dev/hda, SMART Usage
Attribute: 194 Temperature_Celsius changed from 30 to 31
...
Mar 5 15:11:31 foobar smartd[2610]: Device: /dev/hda, SMART Prefailure
Attribute: 1 Raw_Read_Error_Rate changed from 58 to 59
Mar 5 15:11:31 foobar smartd[2610]: Device: /dev/hda, SMART Usage
Attribute: 195 Hardware_ECC_Recovered changed from 58 to 59
Mar 5 15:15:01 foobar /USR/SBIN/CRON[8815]: (root) CMD (command -v
debian-sa1 > /dev/null && debian-sa1 1 1)
Mar 5 15:17:01 foobar /USR/SBIN/CRON[11199]: (root) CMD ( cd / &&
run-parts --report /etc/cron.hourly)
Mar 5 15:25:01 foobar /USR/SBIN/CRON[20721]: (root) CMD (command -v
debian-sa1 > /dev/null && debian-sa1 1 1)
Mar 5 15:35:01 foobar /USR/SBIN/CRON[32588]: (root) CMD (command -v
debian-sa1 > /dev/null && debian-sa1 1 1)
Mar 5 15:45:01 foobar /USR/SBIN/CRON[12129]: (root) CMD (command -v
debian-sa1 > /dev/null && debian-sa1 1 1)
Mar 5 15:55:01 foobar /USR/SBIN/CRON[23947]: (root) CMD (command -v
debian-sa1 > /dev/null && debian-sa1 1 1)
< rebooted my crashed PC from its kernel panic >
Mar 5 21:05:19 foobar syslogd 1.5.0#5: restart.
...
I couldn't find any similiar from an earlier one like (don't think
...
Mar 5 05:17:01 foobar /USR/SBIN/CRON[26833]: (root) CMD ( cd / &&
run-parts --report /etc/cron.hourly)
Mar 5 05:25:01 foobar /USR/SBIN/CRON[29514]: (root) CMD (command -v
debian-sa1 > /dev/null && debian-sa1 1 1)
Mar 5 05:35:01 foobar /USR/SBIN/CRON[372]: (root) CMD (command -v
debian-sa1 > /dev/null && debian-sa1 1 1)
Mar 5 05:45:01 foobar /USR/SBIN/CRON[3772]: (root) CMD (command -v
debian-sa1 > /dev/null && debian-sa1 1 1)
Mar 5 05:55:01 foobar /USR/SBIN/CRON[7160]: (root) CMD (command -v
debian-sa1 > /dev/null && debian-sa1 1 1)
Mar 5 06:41:19 foobar syslogd 1.5.0#5: restart.
...
I saw LKCD (http://lkcd.sourceforge.net/ and
http://sourceforge.net/projects/lkcd/files/), but it seems to be
outdated? I also couldn't find a Debian package of it, so I don't know
if I should even try it to get more datas.
And yes, I already tried memtest86+ v4.00 and it came out no errors
after six hours with its default tests. I will try it again later just
in case.
Thank you in advance. :)
Did you use "System" menu, Administration, Log File Viewer?

Look for "kern.log"
Ant
2010-03-10 15:17:46 UTC
Permalink
Post by Tecknode
Did you use "System" menu, Administration, Log File Viewer?
Look for "kern.log"
That's a new one (catted it in shell). What's the difference between
this and /var/log/messages and dmesg? FYI:

...
Mar 10 04:52:55 foobar kernel: [162599.988025] Machine check events logged
Mar 10 05:10:25 foobar kernel: [163649.988019] Machine check events logged
...
--
"Lay a stick of bubble gum on an anthill for instant Siamese Ant Twins."
--unknown
/\___/\
/ /\ /\ \ Phil./Ant @ http://antfarm.ma.cx (Personal Web Site)
| |o o| | Ant's Quality Foraged Links: http://aqfl.net
\ _ / Nuke ANT from e-mail address: ***@earthlink.netANT
( ) or ***@zimage.com
Ant is currently not listening to any songs on his home computer.
Joe Beanfish
2010-03-10 18:06:23 UTC
Permalink
Post by Ant
Post by Tecknode
Did you use "System" menu, Administration, Log File Viewer?
Look for "kern.log"
That's a new one (catted it in shell). What's the difference between
...
Mar 10 04:52:55 foobar kernel: [162599.988025] Machine check events logged
Mar 10 05:10:25 foobar kernel: [163649.988019] Machine check events logged
...
See your syslog conf to find out what goes to what files.
/etc/syslog.conf or /etc/rsyslog.conf or ?? depending on the syslog
package being used.
Ant
2010-03-11 16:53:33 UTC
Permalink
Post by Joe Beanfish
Post by Ant
That's a new one (catted it in shell). What's the difference between
...
Mar 10 04:52:55 foobar kernel: [162599.988025] Machine check events logged
Mar 10 05:10:25 foobar kernel: [163649.988019] Machine check events logged
...
See your syslog conf to find out what goes to what files.
/etc/syslog.conf or /etc/rsyslog.conf or ?? depending on the syslog
package being used.
# cat /etc/syslog.conf
# /etc/syslog.conf Configuration file for syslogd.
#
# For more information see syslog.conf(5)
# manpage.

#
# First some standard logfiles. Log by facility.
#

auth,authpriv.* /var/log/auth.log
*.*;auth,authpriv.none -/var/log/syslog
#cron.* /var/log/cron.log
daemon.* -/var/log/daemon.log
kern.* -/var/log/kern.log
lpr.* -/var/log/lpr.log
mail.* -/var/log/mail.log
user.* -/var/log/user.log

#
# Logging for the mail system. Split it up so that
# it is easy to write scripts to parse these files.
#
mail.info -/var/log/mail.info
mail.warn -/var/log/mail.warn
mail.err /var/log/mail.err

# Logging for INN news system
#
news.crit /var/log/news/news.crit
news.err /var/log/news/news.err
news.notice -/var/log/news/news.notice

#
# Some `catch-all' logfiles.
#
*.=debug;\
auth,authpriv.none;\
news.none;mail.none -/var/log/debug
*.=info;*.=notice;*.=warn;\
auth,authpriv.none;\
cron,daemon.none;\
mail,news.none -/var/log/messages

#
# Emergencies are sent to everybody logged in.
#
*.emerg *

#
# I like to have messages displayed on the console, but only on a virtual
# console I usually leave idle.
#
#daemon,mail.*;\
# news.=crit;news.=err;news.=notice;\
# *.=debug;*.=info;\
# *.=notice;*.=warn /dev/tty8

# The named pipe /dev/xconsole is for the `xconsole' utility. To use it,
# you must invoke `xconsole' with the `-file' option:
#
# $ xconsole -file /dev/xconsole [...]
#
# NOTE: adjust the list below, or you'll go crazy if you have a reasonably
# busy site..
#
daemon.*;mail.*;\
news.err;\
*.=debug;*.=info;\
*.=notice;*.=warn |/dev/xconsole
--
"Now I have you where I want you... where is my jar of Bull ants?" --unknown
/\___/\
/ /\ /\ \ Phil./Ant @ http://antfarm.ma.cx (Personal Web Site)
| |o o| | Ant's Quality Foraged Links: http://aqfl.net
\ _ / Nuke ANT from e-mail address: ***@earthlink.netANT
( ) or ***@zimage.com
Ant is currently not listening to any songs on his home computer.
Ant
2010-03-13 07:42:24 UTC
Permalink
A follow-up... Last night, I ran memtest86+ v4.00's test #9.
http://www.memtest86.com/tech.html#descri says: "Test 9 [Bit fade test,
90 min, 2 patterns]

The bit fade test initializes all of memory with a pattern and then
sleeps for 90 minutes. Then memory is examined to see if any memory bits
have changed. All ones and all zero patterns are used. This test takes 3
hours to complete. The Bit Fade test is not included in the normal test
sequence and must be run manually via the runtime configuration menu."

I only ran it for over 3.25 hours and it passed (only one test).
Shouldn't this test that problem? Or is that TLB somewhere else? Maybe I
need to run it longer and more?

Also, I did a cat /var/log/messages |grep mcelog and posted the long log
at http://pastie.org/867602 ... Check out of those mcelog errors.

The author of cpuburn, told me to try seven and 37 "nice -19 ./burnMMX P
&" separately. I ran them for many hours, and no problems. I am starting
to notice that the errors and kernel panics seem to only occur when my
system is idled (again, not using AMD's Cool'n'Quiet).

But wait a minute...
# dpkg -l | grep ^ii |grep cpu
ii cpufrequtils 006-2 utilities to deal with
the cpufreq Linux kernel feature
ii cpulimit 1.1-13 tool for limiting the
CPU usage of a process
ii libcpufreq0 006-2 shared library to deal
with the cpufreq Linux kernel fe

I don't think I am supposed to have these even though I disabled
cool'n'quiet and don't have powernow module. I uninstalled cpufrequtils
and cpulimit packages, but not libcpufreq0. It wanted to remove a bunch
of other things:
# apt-get remove libcpufreq0
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer
required:
libmono-addins-gui0.2-cil mono-2.0-gac geoclue-localnet libempathy30
geoclue tomboy telepathy-salut libevent-1.4-2
libgtk-vnc-1.0-0 libgnomepanel2.24-cil libglade2.0-cil libglib2.0-cil
python-software-properties cheese evolution-exchange
libgconf2.0-cil python-aptdaemon-gtk gnome-codec-install
python-aptdaemon cli-common gnome-screensaver w3c-dtd-xhtml
libnm-util1 system-config-printer libart2.0-cil libjs-jquery
epiphany-extensions seahorse empathy python-apt
libempathy-common libempathy-gtk28 gvfs-bin vinagre swfdec-gnome
libgnome2.24-cil libndesk-dbus1.0-cil seahorse-plugins
libgeoclue0 libmono-cairo2.0-cil gedit-plugins libgmime2.4-cil
software-center libmono-i18n-west2.0-cil libcryptui0
libgdu-gtk0 libmono-addins0.2-cil arj python-webkit
libmono-posix2.0-cil libmono-security2.0-cil gnome-disk-utility
libgtk2.0-cil mono-gac python-vte libnm-glib2 unattended-upgrades
python-xapian geoclue-hostip aptdaemon
python-gnupginterface telepathy-mission-control-5 python-cupsutils
libswfdec-0.8-0 libmono-sharpzip2.84-cil
libmono-corlib2.0-cil libchamplain-0.4-0 libchamplain-gtk-0.4-0
mono-runtime python-cups python-evolution
libndesk-dbus-glib1.0-cil libempathy-gtk-common hamster-applet
binfmt-support libgnome-vfs2.0-cil libavahi-ui0
transmission-common gstreamer0.10-tools lsb-release
libmono-system2.0-cil transmission-gtk
Use 'apt-get autoremove' to remove them.
The following packages will be REMOVED:
gnome gnome-applets gnome-core gnome-desktop-environment libcpufreq0
0 upgraded, 0 newly installed, 5 to remove and 126 not upgraded.
After this operation, 1,028kB disk space will be freed.
Do you want to continue [Y/n]? n


Let's see if this solves the problem?

# lsmod |grep cpu
cpufreq_powersave 602 0
cpufreq_userspace 1444 0
cpufreq_stats 1940 0
cpufreq_conservative 4018 0
xt_tcpudp 1743 92
x_tables 8335 6
xt_tcpudp,xt_limit,xt_state,ipt_LOG,ipt_REJECT,ip_tables
Post by Ant
Uh oh. I just discovered mcelog and something new and scary in its
Mar 6 01:19:37 foobar kernel: [15299.988025] Machine check events logged
Mar 6 01:42:07 foobar kernel: [16649.989021] Machine check events logged
Mar 6 02:05:19 foobar -- MARK --
Mar 6 02:19:37 foobar kernel: [18899.989024] Machine check events logged
Mar 6 02:37:07 foobar kernel: [19949.988027] Machine check events logged
Mar 6 03:05:19 foobar -- MARK --
Mar 6 03:24:37 foobar kernel: [22799.989023] Machine check events logged
Mar 6 03:45:19 foobar -- MARK --
Mar 6 04:05:19 foobar -- MARK --
Mar 6 04:25:19 foobar -- MARK --
Mar 6 04:45:19 foobar -- MARK --
Mar 6 05:02:07 foobar kernel: [28649.989023] Machine check events logged
Mar 6 05:25:19 foobar -- MARK --
Mar 6 05:45:19 foobar -- MARK --
Mar 6 06:05:19 foobar -- MARK --
Mar 6 06:24:37 foobar kernel: [33599.989027] Machine check events logged
Mar 6 06:33:13 foobar syslogd 1.5.0#5: restart.
Mar 6 06:45:19 foobar -- MARK --
Mar 6 07:05:19 foobar -- MARK --
Mar 6 07:25:19 foobar -- MARK --
Mar 6 07:45:19 foobar -- MARK --
Mar 6 08:05:19 foobar -- MARK --
Mar 6 08:17:07 foobar kernel: [40349.989022] Machine check events logged
Mar 6 08:24:37 foobar kernel: [40799.988036] Machine check events logged
Mar 6 08:45:19 foobar -- MARK --
Mar 6 08:52:09 foobar mcelog: HARDWARE ERROR. This is *NOT* a software
problem!
Mar 6 08:52:09 foobar mcelog: Please contact your hardware vendor
Mar 6 08:52:09 foobar mcelog: MCE 0
Mar 6 08:52:09 foobar mcelog: CPU 1 1 instruction cache
Mar 6 08:52:09 foobar mcelog: ADDR c11b6ff0
Mar 6 08:52:09 foobar mcelog: TIME 1267894329 Sat Mar 6 08:52:09 2010
Mar 6 08:52:09 foobar mcelog: TLB parity error in virtual array
Mar 6 08:52:09 foobar mcelog: TLB error 'instruction transaction, level 1'
Mar 6 08:52:09 foobar mcelog: STATUS 9400000000010011 MCGSTATUS 0
Mar 6 08:52:09 foobar mcelog: MCGCAP 105 APICID 1 SOCKETID 0
Mar 6 08:52:09 foobar mcelog: CPUID Vendor AMD Family 15 Model 43
Mar 6 08:52:09 foobar mcelog: HARDWARE ERROR. This is *NOT* a software
problem!
Mar 6 08:52:09 foobar mcelog: Please contact your hardware vendor
Mar 6 08:52:09 foobar mcelog: MCE 1
Mar 6 08:52:09 foobar mcelog: CPU 1 1 instruction cache
Mar 6 08:52:09 foobar mcelog: ADDR c11b6ff0
Mar 6 08:52:09 foobar mcelog: TIME 1267894329 Sat Mar 6 08:52:09 2010
Mar 6 08:52:09 foobar mcelog: TLB parity error in virtual array
Mar 6 08:52:09 foobar mcelog: TLB error 'instruction transaction, level 1'
Mar 6 08:52:09 foobar mcelog: STATUS 9400000000010011 MCGSTATUS 0
Mar 6 08:52:09 foobar mcelog: MCGCAP 105 APICID 1 SOCKETID 0
Mar 6 08:52:09 foobar mcelog: CPUID Vendor AMD Family 15 Model 43
Mar 6 08:52:09 foobar mcelog: HARDWARE ERROR. This is *NOT* a software
problem!
Mar 6 08:52:09 foobar mcelog: Please contact your hardware vendor
Mar 6 08:52:09 foobar mcelog: MCE 2
Mar 6 08:52:09 foobar mcelog: CPU 1 1 instruction cache
Mar 6 08:52:09 foobar mcelog: ADDR c11b6ff0
Mar 6 08:52:09 foobar mcelog: TIME 1267894329 Sat Mar 6 08:52:09 2010
Mar 6 08:52:09 foobar mcelog: TLB parity error in virtual array
Mar 6 08:52:09 foobar mcelog: TLB error 'instruction transaction, level 1'
Mar 6 08:52:09 foobar mcelog: STATUS 9400000000010011 MCGSTATUS 0
Mar 6 08:52:09 foobar mcelog: MCGCAP 105 APICID 1 SOCKETID 0
Mar 6 08:52:09 foobar mcelog: CPUID Vendor AMD Family 15 Model 43
Mar 6 08:52:09 foobar mcelog: HARDWARE ERROR. This is *NOT* a software
problem!
Mar 6 08:52:09 foobar mcelog: Please contact your hardware vendor
Mar 6 08:52:09 foobar mcelog: MCE 3
Mar 6 08:52:09 foobar mcelog: CPU 1 1 instruction cache
Mar 6 08:52:09 foobar mcelog: ADDR c11b6ff0
Mar 6 08:52:09 foobar mcelog: TIME 1267894329 Sat Mar 6 08:52:09 2010
Mar 6 08:52:09 foobar mcelog: TLB parity error in virtual array
Mar 6 08:52:09 foobar mcelog: TLB error 'instruction transaction, level 1'
Mar 6 08:52:09 foobar mcelog: STATUS 9400000000010011 MCGSTATUS 0
Mar 6 08:52:09 foobar mcelog: MCGCAP 105 APICID 1 SOCKETID 0
Mar 6 08:52:09 foobar mcelog: CPUID Vendor AMD Family 15 Model 43
Mar 6 08:52:09 foobar mcelog: HARDWARE ERROR. This is *NOT* a software
problem!
Mar 6 08:52:09 foobar mcelog: Please contact your hardware vendor
Mar 6 08:52:09 foobar mcelog: MCE 4
Mar 6 08:52:09 foobar mcelog: CPU 1 1 instruction cache
Mar 6 08:52:09 foobar mcelog: ADDR c11b6ff0
Mar 6 08:52:09 foobar mcelog: TIME 1267894329 Sat Mar 6 08:52:09 2010
Mar 6 08:52:09 foobar mcelog: TLB parity error in virtual array
Mar 6 08:52:09 foobar mcelog: TLB error 'instruction transaction, level 1'
Mar 6 08:52:09 foobar mcelog: STATUS 9400000000010011 MCGSTATUS 0
Mar 6 08:52:09 foobar mcelog: MCGCAP 105 APICID 1 SOCKETID 0
Mar 6 08:52:09 foobar mcelog: CPUID Vendor AMD Family 15 Model 43
Mar 6 08:52:09 foobar mcelog: HARDWARE ERROR. This is *NOT* a software
problem!
Mar 6 08:52:09 foobar mcelog: Please contact your hardware vendor
Mar 6 08:52:09 foobar mcelog: MCE 5
Mar 6 08:52:09 foobar mcelog: CPU 1 1 instruction cache
Mar 6 08:52:09 foobar mcelog: ADDR c11b6ff0
Mar 6 08:52:09 foobar mcelog: TIME 1267894329 Sat Mar 6 08:52:09 2010
Mar 6 08:52:09 foobar mcelog: TLB parity error in virtual array
Mar 6 08:52:09 foobar mcelog: TLB error 'instruction transaction, level 1'
Mar 6 08:52:09 foobar mcelog: STATUS 9400000000010011 MCGSTATUS 0
Mar 6 08:52:09 foobar mcelog: MCGCAP 105 APICID 1 SOCKETID 0
Mar 6 08:52:09 foobar mcelog: CPUID Vendor AMD Family 15 Model 43
Mar 6 08:52:09 foobar mcelog: HARDWARE ERROR. This is *NOT* a software
problem!
Mar 6 08:52:09 foobar mcelog: Please contact your hardware vendor
Mar 6 08:52:09 foobar mcelog: MCE 6
Mar 6 08:52:09 foobar mcelog: CPU 1 1 instruction cache
Mar 6 08:52:09 foobar mcelog: ADDR c11b6ff0
Mar 6 08:52:09 foobar mcelog: TIME 1267894329 Sat Mar 6 08:52:09 2010
Mar 6 08:52:09 foobar mcelog: TLB parity error in virtual array
Mar 6 08:52:09 foobar mcelog: TLB error 'instruction transaction, level 1'
Mar 6 08:52:09 foobar mcelog: STATUS 9400000000010011 MCGSTATUS 0
Mar 6 08:52:09 foobar mcelog: MCGCAP 105 APICID 1 SOCKETID 0
Mar 6 08:52:09 foobar mcelog: CPUID Vendor AMD Family 15 Model 43
Mar 6 08:52:09 foobar mcelog: HARDWARE ERROR. This is *NOT* a software
problem!
Mar 6 08:52:09 foobar mcelog: Please contact your hardware vendor
Mar 6 08:52:09 foobar mcelog: MCE 7
Mar 6 08:52:09 foobar mcelog: CPU 1 1 instruction cache
Mar 6 08:52:09 foobar mcelog: ADDR c11b6ff0
Mar 6 08:52:09 foobar mcelog: TIME 1267894329 Sat Mar 6 08:52:09 2010
Mar 6 08:52:09 foobar mcelog: TLB parity error in virtual array
Mar 6 08:52:09 foobar mcelog: TLB error 'instruction transaction, level 1'
Mar 6 08:52:09 foobar mcelog: STATUS 9400000000010011 MCGSTATUS 0
Mar 6 08:52:09 foobar mcelog: MCGCAP 105 APICID 1 SOCKETID 0
Mar 6 08:52:09 foobar mcelog: CPUID Vendor AMD Family 15 Model 43
Mar 6 08:52:09 foobar mcelog: HARDWARE ERROR. This is *NOT* a software
problem!
Mar 6 08:52:09 foobar mcelog: Please contact your hardware vendor
Mar 6 08:52:09 foobar mcelog: MCE 8
Mar 6 08:52:09 foobar mcelog: CPU 1 1 instruction cache
Mar 6 08:52:09 foobar mcelog: ADDR c11b6ff0
Mar 6 08:52:09 foobar mcelog: TIME 1267894329 Sat Mar 6 08:52:09 2010
Mar 6 08:52:09 foobar mcelog: TLB parity error in virtual array
Mar 6 08:52:09 foobar mcelog: TLB error 'instruction transaction, level 1'
Mar 6 08:52:09 foobar mcelog: STATUS 9400000000010011 MCGSTATUS 0
Mar 6 08:52:09 foobar mcelog: MCGCAP 105 APICID 1 SOCKETID 0
Mar 6 08:52:09 foobar mcelog: CPUID Vendor AMD Family 15 Model 43
What does that mean? Dying CPU (had it since 12/24/2006)? Maybe that's
why memtest86+ didn't find any problems last week.
Post by Ant
Is /var/log/syslog the only place where Linux keeps records of kernel
(v2.6.30 and v2.6.32) panics? dmesg and /var/log/messages doesn't seem
to show anything about the crashes unless I am misreading them. I am
trying to figure out a rare and random kernel panic issue on my old
Debian box.
I know it's not X because I exited it, logged out of bash, went into
fullscreen text console's login screen (I boot up my Debian to text
mode, log into bash, and use startx command to go to X), and saw a bunch
of datas (e.g., memory addresses and codes) on my screen from the kernel
crash. However, its data dump was too long and my computer was in frozen
mode with two blinking PS/2 keyboard lights (caps and scroll lock) so I
couldn't scroll up or copy and paste.
I poked around in my Debian and on the Web. I read that kernel panic
errors/datas can be found in /var/log/syslog (dmesg didn't show me
# cat /var/log/syslog
...
Mar 4 23:12:07 foobar smartd[2647]: Device: /dev/hda, SMART Usage
Attribute: 194 Temperature_Celsius changed from 30 to 31
...
Mar 5 15:11:31 foobar smartd[2610]: Device: /dev/hda, SMART Prefailure
Attribute: 1 Raw_Read_Error_Rate changed from 58 to 59
Mar 5 15:11:31 foobar smartd[2610]: Device: /dev/hda, SMART Usage
Attribute: 195 Hardware_ECC_Recovered changed from 58 to 59
Mar 5 15:15:01 foobar /USR/SBIN/CRON[8815]: (root) CMD (command -v
debian-sa1 > /dev/null && debian-sa1 1 1)
Mar 5 15:17:01 foobar /USR/SBIN/CRON[11199]: (root) CMD ( cd / &&
run-parts --report /etc/cron.hourly)
Mar 5 15:25:01 foobar /USR/SBIN/CRON[20721]: (root) CMD (command -v
debian-sa1 > /dev/null && debian-sa1 1 1)
Mar 5 15:35:01 foobar /USR/SBIN/CRON[32588]: (root) CMD (command -v
debian-sa1 > /dev/null && debian-sa1 1 1)
Mar 5 15:45:01 foobar /USR/SBIN/CRON[12129]: (root) CMD (command -v
debian-sa1 > /dev/null && debian-sa1 1 1)
Mar 5 15:55:01 foobar /USR/SBIN/CRON[23947]: (root) CMD (command -v
debian-sa1 > /dev/null && debian-sa1 1 1)
< rebooted my crashed PC from its kernel panic >
Mar 5 21:05:19 foobar syslogd 1.5.0#5: restart.
...
I couldn't find any similiar from an earlier one like (don't think
...
Mar 5 05:17:01 foobar /USR/SBIN/CRON[26833]: (root) CMD ( cd / &&
run-parts --report /etc/cron.hourly)
Mar 5 05:25:01 foobar /USR/SBIN/CRON[29514]: (root) CMD (command -v
debian-sa1 > /dev/null && debian-sa1 1 1)
Mar 5 05:35:01 foobar /USR/SBIN/CRON[372]: (root) CMD (command -v
debian-sa1 > /dev/null && debian-sa1 1 1)
Mar 5 05:45:01 foobar /USR/SBIN/CRON[3772]: (root) CMD (command -v
debian-sa1 > /dev/null && debian-sa1 1 1)
Mar 5 05:55:01 foobar /USR/SBIN/CRON[7160]: (root) CMD (command -v
debian-sa1 > /dev/null && debian-sa1 1 1)
Mar 5 06:41:19 foobar syslogd 1.5.0#5: restart.
...
I saw LKCD (http://lkcd.sourceforge.net/ and
http://sourceforge.net/projects/lkcd/files/), but it seems to be
outdated? I also couldn't find a Debian package of it, so I don't know
if I should even try it to get more datas.
And yes, I already tried memtest86+ v4.00 and it came out no errors
after six hours with its default tests. I will try it again later just
in case.
Thank you in advance. :)
--
"Trivial hurts, tiny human accidents," said Firenze, as his hooves
thudded over the mossy floor. "These are of no more significance than
the scurryings of ants to the wide universe, and are unaffected by
planetary movements." --Harry Potter book
/\___/\
/ /\ /\ \ Phil./Ant @ http://antfarm.ma.cx (Personal Web Site)
| |o o| | Ant's Quality Foraged Links: http://aqfl.net
\ _ / Nuke ANT from e-mail address: ***@earthlink.netANT
( ) or ***@zimage.com
Ant is currently not listening to any songs on his home computer.
Continue reading on narkive:
Loading...