[SOLVED] Startup fails with. "BUG: unable to handle kernel paging request at <address>"
FedoraForum.org - Fedora Support Forums and Community
Results 1 to 6 of 6
  1. #1
    Join Date
    Sep 2013
    Location
    upstate NY
    Posts
    168
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Startup fails with. "BUG: unable to handle kernel paging request at <address>"

    EDIT: Its not just the DELL. Its happening on 3 different machine that were all working just fine until recent kernels.

    1) The already mentioned DELL
    2) An AMD with a K9N6PGM2-V motherboard
    3) An AMD with a A785GM-LE motherboard

    I think the fact that it started happening on 3 separate machines at at the same upgrade point, rules out hardware issues.

    Recent kernel have been giving me startup problems on several of my machines including an old Dell Precision 490 that I have linux running on for years.

    The error looks something like as follows...

    [ 69.308791] BUG: unable to handle kernel paging request at fffffc74db000008
    [ 69.308888] #PF error: [normal kernel read fault]
    [ 69.308974] PGD 0 P4D 0
    [ 69.309060] Oops: 0000 [#1] SMP PTI
    [ 69.309147] CPU: 0 PID: 927 Comm: Xorg Tainted: P OE 5.1.18-300.fc30.x86_64 #1
    [ 69.309275] Hardware name: Dell Inc. Precision WorkStation 490 /0GU083, BIOS A08 04/25/2008
    [ 69.309410] RIP: 0010:kfree+0x4e/0x190
    [ 69.309496] Code: 80 48 01 df 0f 82 48 01 00 00 48 c7 c0 00 00 00 80 48 2b 05 c4 aa ed 00 48 01 c7 48 c1 ef 0c 48 c1 e7 06 48 03 3d a2 aa ed 00 <48> 8b 47 08 48 8d 50 ff a8 01 48 0f 45 fa 48 8b 57 08 48 8d 42 ff
    [ 69.309674] RSP: 0018:ffffae7201d6fd18 EFLAGS: 00010286
    [ 69.309761] RAX: 000060b540000000 RBX: 000090f100000001 RCX: fffff8ae48be8100
    [ 69.309850] RDX: 0000000000000001 RSI: ffff9f4c72a29a00 RDI: fffffc74db000000
    [ 69.309939] RBP: ffff9f4c72a29a00 R08: 0000000000000000 R09: 0000000000000000
    [ 69.310029] R10: ffff9f4c77403001 R11: fffff8ae48ca8a20 R12: ffffffffc1489eba
    [ 69.310118] R13: 0000000000000007 R14: 0000000000000001 R15: 0000000000000000
    [ 69.310208] FS: 00007fa98e196a80(0000) GS:ffff9f4c77a00000(0000) knlGS:0000000000000000
    [ 69.310336] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    [ 69.310424] CR2: fffffc74db000008 CR3: 0000000230df6000 CR4: 00000000000006f0
    [ 69.310513] Call Trace:
    [ 69.310608] nv_drm_atomic_crtc_destroy_state+0x1a/0x40 [nvidia_drm]
    [ 69.310737] drm_atomic_state_default_clear+0xfb/0x290 [drm]
    [ 69.310843] __drm_atomic_state_free+0x13/0x50 [drm]
    [ 69.310932] nv_drm_atomic_helper_disable_all+0xaf/0x240 [nvidia_drm]
    [ 69.311023] nv_drm_master_drop+0x22/0x60 [nvidia_drm]
    [ 69.311121] drm_drop_master+0x1e/0x40 [drm]
    [ 69.311222] drm_master_release+0x110/0x150 [drm]
    [ 69.311321] drm_file_free.part.0+0x2ee/0x300 [drm]
    [ 69.311420] drm_release+0x4b/0x80 [drm]
    [ 69.311508] __fput+0xbc/0x230
    [ 69.311595] task_work_run+0x87/0xa0
    [ 69.311683] exit_to_usermode_loop+0xc2/0xd0
    [ 69.311770] do_syscall_64+0x14c/0x170
    [ 69.311858] entry_SYSCALL_64_after_hwframe+0x44/0xa9
    [ 69.311946] RIP: 0033:0x7fa98e6e6c55

    It will happen several times in a row then boot up fine.

    memtest86 does not flag any errors.

    Any ideas?
    Last edited by kingsombra; 20th July 2019 at 07:39 PM.

  2. #2
    Join Date
    Sep 2013
    Location
    upstate NY
    Posts
    168
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Startup fails with. "BUG: unable to handle kernel paging request at <address>"

    I believe that this is being caused because the 5.1 kernels require a patch to be made to akmods-nvidia-390XX and I do not think rpmfusion has applied the patch yet.

  3. #3
    Join Date
    Sep 2013
    Location
    upstate NY
    Posts
    168
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Startup fails with. "BUG: unable to handle kernel paging request at <address>"

    I am dropping rpmfusion all together. Every problem I have ever had can be traced right back to them.

    My problem was solved by using the nicely detailed and clear instructions in "If Not True Then False" webpage

    https://www.if-not-true-then-false.c...-nvidia-guide/

  4. #4
    Join Date
    Apr 2009
    Location
    central NY, USA
    Posts
    1,284
    Mentioned
    1 Post(s)
    Tagged
    0 Thread(s)

    Re: Startup fails with. "BUG: unable to handle kernel paging request at <address>"

    I didn't read thoroughly, but it appears you're using the proprietary driver (which works). Just be aware that you will need to re-install it every time the Kernel is updated. The rpmfusion install took care of much of that, but I think I remember reading it's not being updated.
    Change - the only constant.

  5. #5
    Join Date
    Sep 2013
    Location
    upstate NY
    Posts
    168
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Startup fails with. "BUG: unable to handle kernel paging request at <address>"

    The current rpmfusion 390xxs are not working...

    https://bugzilla.rpmfusion.org/show_bug.cgi?id=5311

  6. #6
    Join Date
    Sep 2013
    Location
    upstate NY
    Posts
    168
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Startup fails with. "BUG: unable to handle kernel paging request at <address>"

    Oh and one last little thing. I just upgraded kernel 5.1.19 to 5.1.20 and DKMS worked perfectly. No reinstall of drivers needed.

Similar Threads

  1. Replies: 0
    Last Post: 12th August 2015, 10:32 AM
  2. Replies: 6
    Last Post: 10th May 2011, 02:04 AM
  3. Replies: 2
    Last Post: 27th December 2010, 09:46 AM
  4. BUG: unable to handle kernel paging request at 014000b9
    By pastet89 in forum Fedora 13 Development Branch
    Replies: 5
    Last Post: 18th May 2010, 11:32 PM
  5. BUG: unable to handle kernel paging request at [xxxx]
    By tamar in forum Servers & Networking
    Replies: 2
    Last Post: 10th November 2009, 06:12 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •