LinuxQuestions.org
Visit Jeremy's Blog.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware
Reload this Page Crash of Slackware on Asrock J4205
User Name
Password
Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?

Notices


Reply
  Search this Thread
Old 01-13-2018, 10:55 AM   #1
LinuxJorgen
LQ Newbie
 
Registered: Oct 2002
Location: The Netherlands
Distribution: Centos
Posts: 4

Rep: Reputation: 0
Unhappy Crash of Slackware on Asrock J4205

Installed Slack 14.2 on New Asus Asrock J4205-ITX board.

It has crashed 4x now.

Report printed below. I suspected the Realtek r8168 ethernetdriver (installed separately), because it taints the kernel. I replaced it by the r8169, but another crash (now whithout the r8168 message).

Can please somebody help me interpreting the report?

Code:
Jan 13 16:08:00 bluehead kernel: [    0.042400] mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 4: a600000000020408
Jan 13 16:08:00 bluehead kernel: [    0.042405] mce: [Hardware Error]: TSC 0 ADDR fef13b80 
Jan 13 16:08:00 bluehead kernel: [    0.042412] mce: [Hardware Error]: PROCESSOR 0:506c9 TIME 1515859655 SOCKET 0 APIC 0 microcode 1e
Jan 13 16:08:00 bluehead kernel: [    0.222799] pci 0000:01:00.0: can't set Max Payload Size to 256; if necessary, use "pci=pcie_bus_safe" and report a bug
Jan 13 16:08:00 bluehead kernel: [    9.630329] tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does not cover the entire command/response buffer. [mem 0xfed40000-0xfed4087f flags 0x200] vs fed40080 f80
Jan 13 16:08:00 bluehead kernel: [    9.632323] tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does not cover the entire command/response buffer. [mem 0xfed40000-0xfed4087f flags 0x200] vs fed40080 f80
Jan 13 16:08:00 bluehead kernel: [    9.788458] r8168: loading out-of-tree module taints kernel.
Jan 13 16:08:00 bluehead kernel: [    9.809107] r8168  Copyright (C) 2017  Realtek NIC software team <nicfae@realtek.com> 
Jan 13 16:08:00 bluehead kernel: [    9.809107]  This program comes with ABSOLUTELY NO WARRANTY; for details, please see <http://www.gnu.org/licenses/>. 
Jan 13 16:08:00 bluehead kernel: [    9.809107]  This is free software, and you are welcome to redistribute it under certain conditions; see <http://www.gnu.org/licenses/>. 
Jan 13 16:08:00 bluehead kernel: [    9.899501] i801_smbus 0000:00:1f.1: can't derive routing for PCI INT A
Jan 13 16:08:00 bluehead kernel: [    9.900781] i801_smbus 0000:00:1f.1: PCI INT A: not connected
Jan 13 16:08:00 bluehead kernel: [   10.034885] i915 0000:00:02.0: Direct firmware load for i915/bxt_dmc_ver1_07.bin failed with error -2
Jan 13 16:08:00 bluehead kernel: [   15.915112] usb 1-3.2: device descriptor read/64, error -110
Jan 13 16:08:00 bluehead kernel: [   17.893766] sd 4:0:0:0: [sdb] No Caching mode page found
Jan 13 16:08:00 bluehead kernel: [   17.893768] sd 4:0:0:0: [sdb] Assuming drive cache: write through
Jan 13 16:08:00 bluehead kernel: [   17.955968] sd 5:0:0:0: [sdc] No Caching mode page found
Jan 13 16:08:00 bluehead kernel: [   17.957235] sd 5:0:0:0: [sdc] Assuming drive cache: write through
Jan 13 16:08:00 bluehead kernel: [   22.892465] scsi 4:0:0:1: Failed to get diagnostic page 0x1
Jan 13 16:08:00 bluehead kernel: [   22.893667] scsi 4:0:0:1: Failed to bind enclosure -19
Jan 13 16:08:00 bluehead kernel: [    0.042400] mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 4: a600000000020408
Jan 13 16:08:00 bluehead kernel: [    0.042405] mce: [Hardware Error]: TSC 0 ADDR fef13b80 
Jan 13 16:08:00 bluehead kernel: [    0.042412] mce: [Hardware Error]: PROCESSOR 0:506c9 TIME 1515859655 SOCKET 0 APIC 0 microcode 1e
Jan 13 16:08:00 bluehead kernel: [    0.222799] pci 0000:01:00.0: can't set Max Payload Size to 256; if necessary, use "pci=pcie_bus_safe" and report a bug
Jan 13 16:08:00 bluehead kernel: [    9.630329] tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does not cover the entire command/response buffer. [mem 0xfed40000-0xfed4087f flags 0x200] vs fed40080 f80
Jan 13 16:08:00 bluehead kernel: [    9.632323] tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does not cover the entire command/response buffer. [mem 0xfed40000-0xfed4087f flags 0x200] vs fed40080 f80
Jan 13 16:08:00 bluehead kernel: [    9.788458] r8168: loading out-of-tree module taints kernel.
Jan 13 16:08:00 bluehead kernel: [    9.809107] r8168  Copyright (C) 2017  Realtek NIC software team <nicfae@realtek.com> 
Jan 13 16:08:00 bluehead kernel: [    9.809107]  This program comes with ABSOLUTELY NO WARRANTY; for details, please see <http://www.gnu.org/licenses/>. 
Jan 13 16:08:00 bluehead kernel: [    9.809107]  This is free software, and you are welcome to redistribute it under certain conditions; see <http://www.gnu.org/licenses/>. 
Jan 13 16:08:00 bluehead kernel: [    9.899501] i801_smbus 0000:00:1f.1: can't derive routing for PCI INT A
Jan 13 16:08:00 bluehead kernel: [    9.900781] i801_smbus 0000:00:1f.1: PCI INT A: not connected
Jan 13 16:08:00 bluehead kernel: [   10.034885] i915 0000:00:02.0: Direct firmware load for i915/bxt_dmc_ver1_07.bin failed with error -2
Jan 13 16:08:00 bluehead kernel: [   15.915112] usb 1-3.2: device descriptor read/64, error -110
Jan 13 16:08:00 bluehead kernel: [   17.893766] sd 4:0:0:0: [sdb] No Caching mode page found
Jan 13 16:08:00 bluehead kernel: [   17.893768] sd 4:0:0:0: [sdb] Assuming drive cache: write through
Jan 13 16:08:00 bluehead kernel: [   17.955968] sd 5:0:0:0: [sdc] No Caching mode page found
Jan 13 16:08:00 bluehead kernel: [   17.957235] sd 5:0:0:0: [sdc] Assuming drive cache: write through
Jan 13 16:08:00 bluehead kernel: [   22.892465] scsi 4:0:0:1: Failed to get diagnostic page 0x1
Jan 13 16:08:00 bluehead kernel: [   22.893667] scsi 4:0:0:1: Failed to bind enclosure -19
 
Old 01-13-2018, 12:30 PM   #2
Ser Olmy
Senior Member
 
Registered: Jan 2012
Distribution: Slackware
Posts: 3,341

Rep: Reputation: Disabled
A machine check exception (mce) is a hardware error, probably something to do with memory or the CPU itself.

Take a look at this page for instructions on how to decode the error message with mcelog.
 
Old 01-13-2018, 12:52 PM   #3
LinuxJorgen
LQ Newbie
 
Registered: Oct 2002
Location: The Netherlands
Distribution: Centos
Posts: 4

Original Poster
Rep: Reputation: 0
Unhappy
Thank you. The mce issue seems to be a known issue with intel processors or AMD biosses...

https://bugzilla.redhat.com/show_bug.cgi?id=1467040

I foolishly associated the syslog loggings above with the crash. However, this seems to be 'normal' startup behaviour.

The crash results in a total freeze, with blinking keyboard leds. System can run for days, but this afternoon 3 crashes in a row. During taking in block-chain blocks.. Maybe some network related issue, but that is guessing...

No other traces in the logging than in the message log, during the reboot:

Code:
Dec 25 08:50:32 bluehead kernel: [    4.142772] BERT: Error records from previous boot:
Dec 25 08:50:32 bluehead kernel: [    4.144171] [Hardware Error]: event severity: fatal
Dec 25 08:50:32 bluehead kernel: [    4.145584] [Hardware Error]:  Error 0, type: fatal
Dec 25 08:50:32 bluehead kernel: [    4.146978] [Hardware Error]:   section type: unknown, 81212a96-09ed-4996-9471-8d729c8e69ed
Dec 25 08:50:32 bluehead kernel: [    4.148414] [Hardware Error]:   section length: 0x290
Dec 25 08:50:32 bluehead kernel: [    4.149824] [Hardware Error]:   00000000: 00000001 00000000 00000000 00020002  ................
Dec 25 08:50:32 bluehead kernel: [    4.151264] [Hardware Error]:   00000010: 00020002 00000001 00000318 00000000  ................
Dec 25 08:50:32 bluehead kernel: [    4.152695] [Hardware Error]:   00000020: 00000000 00000000 00000000 00000000  ................
Dec 25 08:50:32 bluehead kernel: [    4.153773] [Hardware Error]:   00000030: 00000000 00000000 00000000 00000000  ................
Dec 25 08:50:32 bluehead kernel: [    4.154785] [Hardware Error]:   00000040: 00000000 00000000 00000000 00000000  ................
Dec 25 08:50:32 bluehead kernel: [    4.155773] [Hardware Error]:   00000050: 00000000 00000000 00000000 00000000  ................
Dec 25 08:50:32 bluehead kernel: [    4.156728] [Hardware Error]:   00000060: 00000000 00000000 00000000 00000000  ................
Dec 25 08:50:32 bluehead kernel: [    4.157669] [Hardware Error]:   00000070: 00000000 00000000 00000000 00000000  ................
Dec 25 08:50:32 bluehead kernel: [    4.158604] [Hardware Error]:   00000080: 00000000 00000000 00000000 00000000  ................

<snip>

Dec 25 08:50:32 bluehead kernel: [    4.177556] [Hardware Error]:   00000270: 00000000 00000000 00000000 00000000  ................
Dec 25 08:50:32 bluehead kernel: [    4.177849] [Hardware Error]:   00000280: 00000000 00000000 00000000 00000000  ................
Dec 25 08:50:32 bluehead kernel: [    4.178150] [Hardware Error]:  Error 1, type: fatal
Dec 25 08:50:32 bluehead kernel: [    4.178409] [Hardware Error]:   section type: unknown, 81212a96-09ed-4996-9471-8d729c8e69ed
Dec 25 08:50:32 bluehead kernel: [    4.178673] [Hardware Error]:   section length: 0x68c
Dec 25 08:50:32 bluehead kernel: [    4.178936] [Hardware Error]:   00000000: 00000001 00000000 00000001 00020003  ................
Dec 25 08:50:32 bluehead kernel: [    4.179281] [Hardware Error]:   00000010: 00020003 0000001e 000506c9 00000000  ................
Dec 25 08:50:32 bluehead kernel: [    4.179596] [Hardware Error]:   00000020: 00000000 f0010f00 00040821 00000000  ........!.......

<snip>

Dec 25 08:50:32 bluehead kernel: [    4.202640] [Hardware Error]:   00000650: 00000000 00000000 00000000 00000000  ................
Dec 25 08:50:32 bluehead kernel: [    4.202827] [Hardware Error]:   00000660: 00000000 00000000 00000000 00000000  ................
Dec 25 08:50:32 bluehead kernel: [    4.203009] [Hardware Error]:   00000670: 00000000 00000000 00000000 00000000  ................
Dec 25 08:50:32 bluehead kernel: [    4.203225] [Hardware Error]:   00000680: 00000000 00000000 00000000           ............
Dec 25 08:50:32 bluehead kernel: [    4.203406] [Hardware Error]:  Error 2, type: fatal
Dec 25 08:50:32 bluehead kernel: [    4.203597] [Hardware Error]:   section type: unknown, 81212a96-09ed-4996-9471-8d729c8e69ed
Dec 25 08:50:32 bluehead kernel: [    4.203815] [Hardware Error]:   section length: 0xb10
Dec 25 08:50:32 bluehead kernel: [    4.204048] [Hardware Error]:   00000000: 00000001 00000000 00000002 00010005  ................
Dec 25 08:50:32 bluehead kernel: [    4.204337] [Hardware Error]:   00000010: 00010005 0000001e 0000001e 00000000  ................
Dec 25 08:50:32 bluehead kernel: [    4.204603] [Hardware Error]:   00000020: 00000000 00000000 00000000 00000000  ................
Dec 25 08:50:32 bluehead kernel: [    4.204880] [Hardware Error]:   00000030: 00000000 00000000 00000000 00000000  ................

<snip>

Dec 25 08:50:32 bluehead kernel: [    4.245571] [Hardware Error]:   00000aa0: 00000000 00000000 00000000 00000000  ................
Dec 25 08:50:32 bluehead kernel: [    4.245756] [Hardware Error]:   00000ab0: 00000000 00000000 00000000 00000000  ................
Dec 25 08:50:32 bluehead kernel: [    4.245936] [Hardware Error]:   00000ac0: 00000000 00000000 00000000 00000000  ................
Dec 25 08:50:32 bluehead kernel: [    4.246145] [Hardware Error]:   00000ad0: 00000000 00000000 00000000 00000000  ................
Dec 25 08:50:32 bluehead kernel: [    4.246331] [Hardware Error]:   00000ae0: 00000000 00000000 00000000 00000000  ................
Dec 25 08:50:32 bluehead kernel: [    4.246511] [Hardware Error]:   00000af0: 00000000 00000000 00000000 00000000  ................
Dec 25 08:50:32 bluehead kernel: [    4.246689] [Hardware Error]:   00000b00: 00000000 00000000 00000000 00000000  ................
Last edited by LinuxJorgen; 01-13-2018 at 12:57 PM.
 
Old 01-13-2018, 01:20 PM   #4
Ser Olmy
Senior Member
 
Registered: Jan 2012
Distribution: Slackware
Posts: 3,341

Rep: Reputation: Disabled
If the keyboard LEDs are blinking it's a kernel panic, not a "freeze".

When a panic occurs, detailed information about the crash is dumped to the main display. Unfortunately, unless the screen resolution is very high, the important bits are likely to scroll off the top of the screen. Also, if the display is in sleep/powersave mode when the panic occurs, it'll probably just remain inactive.

Is this system by any chance equipped with a serial port?
 
Old 01-13-2018, 02:47 PM   #5
LinuxJorgen
LQ Newbie
 
Registered: Oct 2002
Location: The Netherlands
Distribution: Centos
Posts: 4

Original Poster
Rep: Reputation: 0
Quote:
Originally Posted by Ser Olmy View Post
If the keyboard LEDs are blinking it's a kernel panic, not a "freeze".

When a panic occurs, detailed information about the crash is dumped to the main display. Unfortunately, unless the screen resolution is very high, the important bits are likely to scroll off the top of the screen. Also, if the display is in sleep/powersave mode when the panic occurs, it'll probably just remain inactive.

Is this system by any chance equipped with a serial port?
Thanx for responding.

I run the XFCE Xwindow manager. It simply freezes without a message. I can disable it and run from the plain old command line. That would probably show the panic message.

Yes, its got a serial port. You suggest connecting a device with a terminal? E.g. Raspberry Pi? :-)
 
Old 01-13-2018, 02:59 PM   #6
Ser Olmy
Senior Member
 
Registered: Jan 2012
Distribution: Slackware
Posts: 3,341

Rep: Reputation: Disabled
You're right; a panic might not be visible when you're running a GUI. Try with just the command line, but don't be surprised if all you get to see is the bottom few lines of a lengthy stack dump.

Serial consoles are excellent for capturing lengthy console output. Most terminal emulators have configurable scrollback buffers and many can even log to a file.

You can instruct the kernel to duplicate all console output to a serial port with the "console=" kernel parameter. For instance, console=tty0 console=ttyS0,9600n8 will cause all messages to be sent to both the regular console and the first serial port.
 
1 members found this post helpful.
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Slackware 14.1 64 bit crash kerszi Slackware 11 06-02-2014 05:36 PM
Slackware Crash Behaviour boler Slackware 3 02-23-2011 07:08 AM
xmms crash xine crash mplayer crash paledread Linux - Software 9 03-09-2004 07:09 AM
Slackware X Crash! skate Linux - Newbie 4 09-26-2003 02:30 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware

All times are GMT -5. The time now is 03:02 PM.

Contact Us - Advertising Info - Rules - Privacy - LQ Merchandise - Donations - Contributing Member - LQ Sitemap -
Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration