LinuxQuestions.org
Visit Jeremy's Blog.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 06-09-2021, 12:29 PM   #1
Ook
Member
 
Registered: Apr 2004
Location: Hell, Arizona (July - 118 degrees)
Distribution: Slackware 14.2 soon to be Slackware 15
Posts: 663

Rep: Reputation: 127Reputation: 127
BUG: unable to handle page fault


Slackware current, 5.10.32 kernel.

Can some kind soul tall me what this means? The first line says unable to handle page fault. That means to me that an instruction to read memory (from ram or disk?) was issued but the memory block was not in the cpu cache, so it tried to retrieve it but failed. Is that correct? I'm getting a lot of these, and they seem to be related to copying large amounts of data from another machine on the network. At the same time, the i/o from the remote machine fails.

Code:
Wed Jun  9 09:52:16 2021] BUG: unable to handle page fault for address: 0000000001000034
[Wed Jun  9 09:52:16 2021] #PF: supervisor read access in kernel mode
[Wed Jun  9 09:52:16 2021] #PF: error_code(0x0000) - not-present page
[Wed Jun  9 09:52:16 2021] PGD 10d90d067 P4D 10d90d067 PUD 10dcfc067 PMD 0 
[Wed Jun  9 09:52:16 2021] Oops: 0000 [#4] SMP NOPTI
[Wed Jun  9 09:52:16 2021] CPU: 4 PID: 30005 Comm: rsync Tainted: G      D           5.10.32 #1
[Wed Jun  9 09:52:16 2021] Hardware name: System manufacturer System Product Name/PRIME X370-A, BIOS 5222 10/15/2019
[Wed Jun  9 09:52:16 2021] RIP: 0010:find_get_entry+0x80/0x170
[Wed Jun  9 09:52:16 2021] Code: e7 e8 84 6e 6f 00 48 89 c7 48 3d 06 04 00 00 74 e4 48 3d 02 04 00 00 74 dc 48 85 c0 0f 84 bb 00 00 00 a8 01 0f 85 b8 00 00 00 <8b> 40 34 85 c0 74 c4 8d 50 01 f0 0f b1 57 34 75 f2 48 8b 54 24 18
[Wed Jun  9 09:52:16 2021] RSP: 0018:ffffa40682427d10 EFLAGS: 00010246
[Wed Jun  9 09:52:16 2021] RAX: 0000000001000000 RBX: 0000000000000000 RCX: 0000000000000000
[Wed Jun  9 09:52:16 2021] RDX: 0000000000000002 RSI: ffff8dbfab418248 RDI: 0000000001000000
[Wed Jun  9 09:52:16 2021] RBP: 0000000000003582 R08: ffff8dbfab459ff2 R09: ffffa40682427b2b
[Wed Jun  9 09:52:16 2021] R10: 00000000000035d8 R11: 0000000000000001 R12: ffff8dbf1f9019f8
[Wed Jun  9 09:52:16 2021] R13: 0000000000006080 R14: 0000000000000000 R15: 0000000000000036
[Wed Jun  9 09:52:16 2021] FS:  00007f8d65d9a740(0000) GS:ffff8dc5be900000(0000) knlGS:0000000000000000
[Wed Jun  9 09:52:16 2021] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[Wed Jun  9 09:52:16 2021] CR2: 0000000001000034 CR3: 000000010ddd8000 CR4: 00000000003506e0
[Wed Jun  9 09:52:16 2021] Call Trace:
[Wed Jun  9 09:52:16 2021]  pagecache_get_page+0x44/0x380
[Wed Jun  9 09:52:16 2021]  generic_file_buffered_read+0x100/0xa90
[Wed Jun  9 09:52:16 2021]  new_sync_read+0x115/0x1a0
[Wed Jun  9 09:52:16 2021]  vfs_read+0xf4/0x180
[Wed Jun  9 09:52:16 2021]  ksys_read+0x5f/0xe0
[Wed Jun  9 09:52:16 2021]  do_syscall_64+0x33/0x80
[Wed Jun  9 09:52:16 2021]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
[Wed Jun  9 09:52:16 2021] RIP: 0033:0x7f8d65edb90e
[Wed Jun  9 09:52:16 2021] Code: c0 e9 e6 fe ff ff 50 48 8d 3d 9e 4c 0a 00 e8 09 ec 01 00 66 0f 1f 84 00 00 00 00 00 64 8b 04 25 18 00 00 00 85 c0 75 14 0f 05 <48> 3d 00 f0 ff ff 77 5a c3 66 0f 1f 84 00 00 00 00 00 48 83 ec 28
[Wed Jun  9 09:52:16 2021] RSP: 002b:00007ffca76350a8 EFLAGS: 00000246 ORIG_RAX: 0000000000000000
[Wed Jun  9 09:52:16 2021] RAX: ffffffffffffffda RBX: 00000000014c4660 RCX: 00007f8d65edb90e
[Wed Jun  9 09:52:16 2021] RDX: 0000000000040400 RSI: 0000000001956d40 RDI: 0000000000000005
[Wed Jun  9 09:52:16 2021] RBP: 0000000000040400 R08: 0000000003577000 R09: 000000003de02fe5
[Wed Jun  9 09:52:16 2021] R10: 000000002a8cfd53 R11: 0000000000000246 R12: 0000000000000400
[Wed Jun  9 09:52:16 2021] R13: 00000000000002a0 R14: 0000000000000400 R15: 0000000000040400
[Wed Jun  9 09:52:16 2021] Modules linked in: cfg80211 8021q garp mrp stp llc ipv6 hid_generic usbhid hid eeepc_wmi asus_wmi battery sparse_keymap rfkill evdev wmi_bmof snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi snd_hda_intel snd_intel_dspcfg nouveau soundwire_intel soundwire_generic_allocation snd_soc_core mxm_wmi snd_compress snd_pcm_dmaengine video soundwire_cadence snd_hda_codec ttm snd_hda_core drm_kms_helper snd_hwdep drm snd_pcm kvm snd_timer agpgart irqbypass r8169 crct10dif_pclmul i2c_algo_bit crc32_pclmul snd fb_sys_fops realtek ghash_clmulni_intel xhci_pci syscopyarea soundcore mdio_devres xhci_pci_renesas sysfillrect sysimgblt libphy rapl ac97_bus ccp xhci_hcd i2c_piix4 i2c_core k10temp gpio_amdpt wmi gpio_generic acpi_cpufreq button loop
[Wed Jun  9 09:52:16 2021] CR2: 0000000001000034
[Wed Jun  9 09:52:16 2021] ---[ end trace c0ee8c51f3c50a87 ]---
[Wed Jun  9 09:52:16 2021] RIP: 0010:find_get_entries+0xc0/0x310
[Wed Jun  9 09:52:16 2021] Code: c5 48 85 ed 0f 84 a3 00 00 00 48 81 fd 06 04 00 00 0f 84 a3 00 00 00 48 81 fd 02 04 00 00 0f 84 42 01 00 00 40 f6 c5 01 75 6a <8b> 45 34 85 c0 0f 84 31 01 00 00 8d 50 01 f0 0f b1 55 34 75 ee 48
[Wed Jun  9 09:52:16 2021] RSP: 0018:ffffa40683cc7ba0 EFLAGS: 00210246
[Wed Jun  9 09:52:16 2021] RAX: 0000000000000016 RBX: ffffa40683cc7cb8 RCX: 00000000005e3e16
[Wed Jun  9 09:52:16 2021] RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffff8dbfab41b478
[Wed Jun  9 09:52:16 2021] RBP: ffffefd806ae3b40 R08: 0000000000000015 R09: ffffffffffffffff
[Wed Jun  9 09:52:16 2021] R10: ffff8dc5df37bd00 R11: 00000000001ab891 R12: ffffa40683cc7c38
[Wed Jun  9 09:52:16 2021] R13: 000000000000000f R14: 000000000000000d R15: 000000000000000f
[Wed Jun  9 09:52:16 2021] FS:  00007f8d65d9a740(0000) GS:ffff8dc5be900000(0000) knlGS:0000000000000000
[Wed Jun  9 09:52:16 2021] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[Wed Jun  9 09:52:16 2021] CR2: 0000000001000034 CR3: 000000010ddd8000 CR4: 00000000003506e0
 
Old 06-10-2021, 09:13 AM   #2
business_kid
LQ Guru
 
Registered: Jan 2006
Location: Ireland
Distribution: Slackware, RPi OS, Mint & Android
Posts: 12,840

Rep: Reputation: 1676Reputation: 1676Reputation: 1676Reputation: 1676Reputation: 1676Reputation: 1676Reputation: 1676Reputation: 1676Reputation: 1676Reputation: 1676Reputation: 1676
Personally, I have never seen an error begin with the word "Bug:" I think the beginning was before that.

It's definitely some memory read error, but it's unusual to have 'supervisor mode.' The thing I'm wondering is, why doesn't the kernel throw a Segmentation fault like other memory errors and panic, or kill the process?
 
Old 06-10-2021, 09:58 AM   #3
Ser Olmy
Senior Member
 
Registered: Jan 2012
Distribution: Slackware
Posts: 3,063

Rep: Reputation: Disabled
The "Bug" message means the kernel code has hit a BUG_ON exception. And the cause seems to be a pretty serious error in the code:
Code:
[Wed Jun  9 09:52:16 2021] #PF: error_code(0x0000) - not-present page
The question is, which code? According to the splat, you're running a "tainted" kernel, meaning you've probably inserted a pre-compiled module (driver) of some sort:
Code:
[Wed Jun  9 09:52:16 2021] CPU: 4 PID: 30005 Comm: rsync Tainted: G      D           5.10.32 #1
Which non-kernel driver/module are you using?
 
Old 06-10-2021, 03:15 PM   #4
TheRealGrogan
Member
 
Registered: Oct 2010
Location: Ontario, Canada
Distribution: Slackware, LFS, Manjaro (for gaming)
Posts: 438

Rep: Reputation: 277Reputation: 277Reputation: 277
Getting a "BUG" exception taints the kernel. In this case it would have been tainted already though. G - there is a non GPL module loaded. D - Oops or Bug occurred. The process executing when the exception occurred was rsync (Comm name of process)

The supervisor read access in kernel mode message on such a page fault error is common. (Not saying I understand it... just that I've seen it lots)

It could be a bug in the kernel, or a module that's loaded, or chipset/memory issues. I'd be less confident that it's a module, as it looks like a page cache read that failed.

P.S. I'd probably try a different kernel first, and see if the problem occurs.

Last edited by TheRealGrogan; 06-10-2021 at 03:17 PM.
 
Old 06-10-2021, 04:03 PM   #5
Petri Kaukasoina
Member
 
Registered: Mar 2007
Posts: 689

Rep: Reputation: 447Reputation: 447Reputation: 447Reputation: 447Reputation: 447
G means all the loaded modules are GPL compatible. P would mean a proprietary module.

The OP told there were a lot of those BUGS. The first one in the log was "Not tainted", and all the rest are "Tainted: G D". (D means the kernel was tainted because of an OOPS or BUG.)
 
1 members found this post helpful.
Old 06-10-2021, 04:32 PM   #6
TheRealGrogan
Member
 
Registered: Oct 2010
Location: Ontario, Canada
Distribution: Slackware, LFS, Manjaro (for gaming)
Posts: 438

Rep: Reputation: 277Reputation: 277Reputation: 277
So then a G in a tainted message, means "not tainted because of that"? Seems pointless. I guess I thought that if that field was there, there was something wrong with a module license.
 
Old 06-11-2021, 12:00 AM   #7
Ser Olmy
Senior Member
 
Registered: Jan 2012
Distribution: Slackware
Posts: 3,063

Rep: Reputation: Disabled
Quote:
Originally Posted by TheRealGrogan View Post
So then a G in a tainted message, means "not tainted because of that"? Seems pointless. I guess I thought that if that field was there, there was something wrong with a module license.
I knew the 'G' meant all modules were using GPL-compatible licenses, but I thought that it at least indicated that some form of external module was loaded.

But no, I was wrong about that. The flag is either 'G' or 'P', indicating GPL or proprietary licensing; it cannot be blank. There's a separate flag for out-of-tree modules, and that was not set in this case.

So Petri Kaukasoina must be correct, and the "tainted" message is just an indication that the splat that was posted was not the first occurrence of a BUG exception. The OP is most likely running a stock kernel.

That leaves a kernel bug or faulty hardware.

@Ook: Are you using a wired or a wireless connection? Can you switch from one to the other and see if the problem persists?
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

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

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



Similar Threads
Thread Thread Starter Forum Replies Last Post
BUG: unable to handle kernel NULL pointer dereference at pan64 SUSE / openSUSE 1 03-10-2015 08:05 AM
Bug: unable to handle kernel NULL pointer dereference at 0000000000000020 chikidu Linux - Kernel 4 09-26-2012 07:43 PM
BUG: unable to handle kernel NULL pointer dereference at 00000200 xhfahy Linux - Kernel 0 08-25-2012 10:50 PM
kprobe-fault handler(how to generate page fault) hnshashi Linux - Newbie 0 11-13-2008 12:25 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

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

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