LinuxQuestions.org - __radix_tree_lookup errors with 4.14.x and Firefox

- Linux - Kernel (https://www.linuxquestions.org/questions/linux-kernel-70/)

- - __radix_tree_lookup errors with 4.14.x and Firefox (https://www.linuxquestions.org/questions/linux-kernel-70/__radix_tree_lookup-errors-with-4-14-x-and-firefox-4175629287/)

__radix_tree_lookup errors with 4.14.x and Firefox

Greetings, LQ community. I've been having this problem since 4.14.0 and Firefox Quantum. It happens almost every time I use Firefox. 99% of the time it only happens on ad-heavy Internet sites such as Yahoo and Amazon, although it has also happened within a minute of launching a Google search.

I never had this problem before Firefox changed to its Quantum engine, and never had it in kernels 4.13.x and earlier. I can use Chromium or Seamonkey all day with no problems.

First I thought it might be extensions, since they had to be replaced with the new format. I uninstalled down to only NoScript, AdBlock, Persona, and VideoDownloadHelper. I also tried with a fresh profile. No luck. I also thought it might be the nvidia 340.x legacy driver. I upgraded my GTX260 to a GTX750Ti using the latest 390.x - still no luck. I also thought it might be related to system monitors, so I disabled conky and gkrellm, but it still happens.

When the error happens, I get a single pc speaker beep then the browser will no longer load any pages. I can open a different browser, though, and work from there. Also, occasionally, after the error, when shutting down it will get stuck umounting filesystems.

I'm running Slackware 14.2 32-bit with kernel 4.14.39, on a ASRock 970M with 16GB RAM (using PAE). CPU is AMD Phenom II x2 unlocked to x4 using the ASRock's core unlocker. Nvidia driver is version 390.48 and I don't have any other 3rd party kernel modules. I dual boot with Win7 Enterprise 32-bit, and the same Firefox version with the same addons has no problems.

I have searched several times for information about radix_tree in kernel errors but found nothing. The error output contains references to swap but I do not use swap. Below is a the most recent such error, copied from a rxvt window that was open at the time:

Code:

Message from syslogd@Chimera at Fri Apr 27 07:56:40 2018 ...

Chimera kernel: [ 1890.260988] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./970M Pro3, BIOS P1.30 09/01/2015



Message from syslogd@Chimera at Fri Apr 27 07:56:40 2018 ...

Chimera kernel: [ 1890.260989] task: e834a200 task.stack: e59fa000



Message from syslogd@Chimera at Fri Apr 27 07:56:40 2018 ...

Chimera kernel: [ 1890.261007]  pagecache_get_page+0x1f/0x220



Message from syslogd@Chimera at Fri Apr 27 07:56:40 2018 ...

Chimera kernel: [ 1890.260999] Call Trace:



Message from syslogd@Chimera at Fri Apr 27 07:56:40 2018 ...

Chimera kernel: [ 1890.261005]  find_get_entry+0x1d/0x110



Message from syslogd@Chimera at Fri Apr 27 07:56:40 2018 ...

Chimera kernel: [ 1890.260987] CPU: 2 PID: 2226 Comm: gdbus Tainted: P          O    4.14.37-smp #1



Message from syslogd@Chimera at Fri Apr 27 07:56:40 2018 ...

Chimera kernel: [ 1890.261021]  handle_mm_fault+0x598/0xd90



Message from syslogd@Chimera at Fri Apr 27 07:56:40 2018 ...

Chimera kernel: [ 1890.261031]  common_exception+0x65/0x7e



Message from syslogd@Chimera at Fri Apr 27 07:56:40 2018 ...

Chimera kernel: [ 1890.261025]  __do_page_fault+0x17b/0x420



Message from syslogd@Chimera at Fri Apr 27 07:56:40 2018 ...

Chimera kernel: [ 1890.261026]  do_page_fault+0x24/0x100



Message from syslogd@Chimera at Fri Apr 27 07:56:40 2018 ...

Chimera kernel: [ 1890.261017]  ? lru_cache_add_active_or_unevictable+0x2c/0x90



Message from syslogd@Chimera at Fri Apr 27 07:56:40 2018 ...

Chimera kernel: [ 1890.261040] Code: e8 0f 84 50 ff ff ff e9 90 fe ff ff 8d b6 00 00 00 00 8d bc 27 00 00 00 00 55 89 e5 57 56 53 83 ec 08 89 45 f0 89 4d ec 8b 45 f0 <8b> 58 04 89 d8 83 e0 03 83 f8 01 0f 85 9f 00 00 00 89 d8 83 e0



Message from syslogd@Chimera at Fri Apr 27 07:56:40 2018 ...

Chimera kernel: [ 1890.261014]  do_swap_page+0x122/0x660



Message from syslogd@Chimera at Fri Apr 27 07:56:40 2018 ...

Chimera kernel: [ 1890.261059] EIP: __radix_tree_lookup+0x12/0xe0 SS:ESP: 0068:e59fbdc8



Message from syslogd@Chimera at Fri Apr 27 07:56:40 2018 ...

Chimera kernel: [ 1890.261011]  swap_readahead_detect+0x66/0x2d0



Message from syslogd@Chimera at Fri Apr 27 07:56:40 2018 ...

Chimera kernel: [ 1890.261028]  ? vmalloc_sync_all+0x10/0x10

Message from syslogd@Chimera at Fri Apr 27 07:56:40 2018 ...

Chimera kernel: [ 1890.261009]  lookup_swap_cache+0x35/0x100





Message from syslogd@Chimera at Fri Apr 27 07:56:40 2018 ...

Chimera kernel: [ 1890.261019]  ? wp_page_copy+0x2f0/0x580



Message from syslogd@Chimera at Fri Apr 27 07:56:40 2018 ...

Chimera kernel: [ 1890.261002]  radix_tree_lookup_slot+0x11/0x30



Message from syslogd@Chimera at Fri Apr 27 07:56:40 2018 ...

Chimera kernel: [ 1890.261039]  ? vmalloc_sync_all+0x10/0x10

Thanks in advance for any ideas. I hope I included all of the relevant info.

There have been some fixes in this area in later 4.14. Would you mind to get the latest 4.14 kernel (4.14.40 as of today) and check if this got fixed?

Thank you for the reply. I installed .40 yesterday and upgraded Firefox to 60.0 this morning. I have had Firefox open for 3 hours now using Amazon, Yahoo and Facebook and so far so good. I'll keep checking and hoping it is fixed.

It happened again this morning. Twice. First, I had used Firefox for a few minutes to download the files to build the mono-5.0.1.1 SlackBuild. When the downloads finished I closed Firefox and proceeded to begin the SlackBuild. All was fine for several minutes until the kernel crashed in the middle of compiling mono. I rebooted and remained at the CLI - no X running. I went straight to the directory where the mono SlackBuild files are located and started the build. Less than five minutes into it - crash!

This time I was able to see some lines at the top of the crash log that I did not get previously. The references to smp #1 make me think it might be a compatibility issue between the kernel and my cpu. Something that is triggered and then blows up under cpu load? I guess it had previously been coincidence that it always crashed during/after using Firefox.

Code:

May 13 08:26:02 Chimera kernel: [ 6050.815209] BUG: unable to handle kernel NULL pointer dereference at 00000008

May 13 08:26:02 Chimera kernel: [ 6050.815220] IP: __radix_tree_lookup+0x12/0xe0

May 13 08:26:02 Chimera kernel: [ 6050.815225] Oops: 0000 [#1] SMP

May 13 08:26:02 Chimera kernel: [ 6050.815227] Modules linked in: snd_seq_dummy snd_seq_oss snd_emu10k1_synth snd_emux_synth snd_seq_midi_emul snd_seq_virmidi snd_seq_midi snd_hrtimer snd_seq_midi_event snd_seq arc4 pcspkr pci_stub vboxpci(O) vboxnetadp(O) vboxnetflt(O) vboxdrv(O) cfg80211 ipv6 sg nls_utf8 cifs ccm nls_iso8859_1 nls_cp437 fuse gspca_zc3xx joydev hid_generic gspca_main v4l2_common usbhid videodev hid uas usb_storage nvidia_drm(PO) nvidia_modeset(PO) i2c_dev evdev nvidia(PO) drm_kms_helper syscopyarea sysfillrect snd_hda_intel sysimgblt snd_emu10k1 snd_hda_codec fb_sys_fops kvm_amd snd_hda_core drm kvm snd_util_mem snd_ac97_codec ac97_bus snd_hwdep snd_rawmidi snd_seq_device snd_pcm irqbypass snd_timer k10temp hwmon snd i2c_piix4 ipmi_devintf ipmi_msghandler i2c_core soundcore ati_agp agpgart ohci_pci ohci_hcd button

May 13 08:26:02 Chimera kernel: [ 6050.815260]  loop

May 13 08:26:02 Chimera kernel: [ 6050.815263] CPU: 0 PID: 11626 Comm: Threadpool work Tainted: P          O    4.14.40-smp #1

I am currently booted into the official kernel 4.4.118. So far I've installed the nvidia proprietary driver, launched my Fluxbox desktop, built my mono SlackBuild followed by KeePass, and now using Firefox to write this post. If I continue to have no problems in 4.4.118 I think my best solution will be to stay with 4.4.x

I've been using my computer most of the day today, booted into kernel 4.4.118, and using Firefox 60.0. No problems. I've pretty much decided to use the 4.4 kernel as my primary and keep 4.14.40 as a backup. At least until Pat moves Slackware to a newer kernel. I'm still curious if the error sounds like a bug in the kernel source or a problem in my kernel config.