Bug 20058 - Kernel 4.9.0-3 fail booting with nvidia340
Summary: Kernel 4.9.0-3 fail booting with nvidia340
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal critical
Target Milestone: ---
Assignee: Kernel and Drivers maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-01-01 22:30 CET by Morgan Leijström
Modified: 2017-01-02 01:19 CET (History)
3 users (show)

See Also:
Source RPM: kernel-desktop-4.9.0-3
CVE:
Status comment:


Attachments
system log of failed boot (113.04 KB, application/octet-stream)
2017-01-01 22:32 CET, Morgan Leijström
Details

Description Morgan Leijström 2017-01-01 22:30:08 CET
(it works to boot with noveau) I attach full system log of failed boot.

Excerpt:
jan 01 21:38:43 localhost kernel: ------------[ cut here ]------------
jan 01 21:38:43 localhost kernel: WARNING: CPU: 1 PID: 2237 at fs/proc/generic.c:345 proc_register+0xe8/0x110
jan 01 21:38:43 localhost kernel: proc_dir_entry 'driver/nvidia' already registered
jan 01 21:38:43 localhost kernel: Modules linked in: nf_conntrack_snmp nvidia(PO+) nf_nat_sip xt_CHECKSUM nf_nat_pptp nf_nat_proto_gre iptable_mangle nf_nat_irc nf_nat_h323 nf_nat_ftp xt_NFLOG nfnetlink_log nf_nat_amanda xt_LOG nf_log_ipv6 ipt_MASQUERADE nf_log_common nf_nat_masquerade_ipv4 nf_conntrack_tftp iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_sip nf_conntrack_sane nf_conntrack_proto_udplite nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack_proto_sctp xt_conntrack nf_conntrack_pptp nf_conntrack_proto_gre ipt_REJECT nf_reject_ipv4 nf_conntrack_netlink nfnetlink nf_conntrack_netbios_ns nf_conntrack_broadcast xt_tcpudp nf_conntrack_irc nf_conntrack_h323 ts_kmp nf_conntrack_ftp nf_conntrack_amanda nf_conntrack tun bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter ip_tables x_tables ccm af_packet
jan 01 21:38:43 localhost kernel:  bnep msr usbhid hid snd_hda_codec_analog snd_hda_codec_generic coretemp kvm_intel iTCO_wdt iTCO_vendor_support kvm ppdev irqbypass psmouse arc4 i2c_i801 input_leds i2c_smbus iwl4965 r852 sm_common nand r592 iwlegacy nand_ecc nand_ids memstick mtd lpc_ich mac80211 btusb btrtl btbcm drm thermal btintel snd_hda_intel bluetooth snd_hda_codec thinkpad_acpi battery ac fjes snd_hda_core cfg80211 snd_hwdep snd_pcm parport_pc parport tpm_tis tpm_tis_core tpm rfkill e1000e snd_timer snd soundcore ptp pps_core shpchp joydev cuse fuse acpi_cpufreq hdaps input_polldev evdev nvram sch_fq_codel ipv6 crc_ccitt autofs4 pcmcia sdhci_pci mmc_block serio_raw uhci_hcd sdhci firewire_ohci mmc_core firewire_core yenta_socket sr_mod crc_itu_t pcmcia_rsrc pcmcia_core ehci_pci ehci_hcd usbcore usb_common wmi
jan 01 21:38:43 localhost kernel:  video button dm_mirror dm_region_hash dm_log dm_mod ide_pci_generic piix ide_core ata_generic pata_acpi ata_piix
jan 01 21:38:43 localhost kernel: CPU: 1 PID: 2237 Comm: modprobe Tainted: P           O    4.9.0-desktop-3.mga6 #1
jan 01 21:38:43 localhost kernel: Hardware name: LENOVO 64575KG/64575KG, BIOS 7LETC9WW (2.29 ) 03/18/2011
jan 01 21:38:43 localhost kernel:  ffffa2b9c1773b30 ffffffff8e417a7e ffffa2b9c1773b80 0000000000000000
jan 01 21:38:43 localhost kernel:  ffffa2b9c1773b70 ffffffff8e070a8b 000001598e419547 ffff9516752d9e80
jan 01 21:38:43 localhost kernel:  ffff951677035b40 ffff951675046ec5 ffff951677035b78 ffff951675046e40
jan 01 21:38:43 localhost kernel: Call Trace:
jan 01 21:38:43 localhost kernel:  [<ffffffff8e417a7e>] dump_stack+0x63/0x85
jan 01 21:38:43 localhost kernel:  [<ffffffff8e070a8b>] __warn+0xcb/0xf0
jan 01 21:38:43 localhost kernel:  [<ffffffff8e070aff>] warn_slowpath_fmt+0x4f/0x60
jan 01 21:38:43 localhost kernel:  [<ffffffff8e25ca78>] proc_register+0xe8/0x110
jan 01 21:38:43 localhost kernel:  [<ffffffff8e25cbb6>] proc_mkdir_data+0x66/0x90
jan 01 21:38:43 localhost kernel:  [<ffffffff8e25cbf3>] proc_mkdir_mode+0x13/0x20
jan 01 21:38:43 localhost kernel:  [<ffffffffc10f4a5d>] nv_register_procfs+0x3d/0x1b0 [nvidia]
jan 01 21:38:43 localhost kernel:  [<ffffffffc1599291>] nvidia_init_module+0x291/0x775 [nvidia]
jan 01 21:38:43 localhost kernel:  [<ffffffffc159978a>] ? nv_drm_init+0x15/0x15 [nvidia]
jan 01 21:38:43 localhost kernel:  [<ffffffffc15997db>] nvidia_frontend_init_module+0x51/0x876 [nvidia]
jan 01 21:38:43 localhost kernel:  [<ffffffff8e00217d>] do_one_initcall+0x3d/0x160
jan 01 21:38:43 localhost kernel:  [<ffffffff8e1b1671>] ? __vunmap+0x81/0xd0
jan 01 21:38:43 localhost kernel:  [<ffffffff8e1cdd88>] ? kmem_cache_alloc_trace+0x38/0x150
jan 01 21:38:43 localhost kernel:  [<ffffffff8e16d2c5>] do_init_module+0x5f/0x1f6
jan 01 21:38:43 localhost kernel:  [<ffffffff8e0f7e7d>] load_module+0x23fd/0x2990
jan 01 21:38:43 localhost kernel:  [<ffffffff8e0f47b0>] ? __symbol_put+0x40/0x40
jan 01 21:38:43 localhost kernel:  [<ffffffff8e0f8563>] SYSC_init_module+0x153/0x170
jan 01 21:38:43 localhost kernel:  [<ffffffff8e0f867e>] SyS_init_module+0xe/0x10
jan 01 21:38:43 localhost kernel:  [<ffffffff8e003a7b>] do_syscall_64+0x5b/0xc0
jan 01 21:38:43 localhost kernel:  [<ffffffff8e7456ef>] entry_SYSCALL64_slow_path+0x25/0x25
jan 01 21:38:43 localhost kernel: ---[ end trace 6b0f2c1405fd12b3 ]---
jan 01 21:38:43 localhost kernel: NVRM: failed to register procfs!
jan 01 21:38:43 localhost kernel: NVRM: request_mem_region failed for 16M @ 0xd6000000. This can
                                  NVRM: occur when a driver such as rivatv is loaded and claims
                                  NVRM: ownership of the device's registers.
jan 01 21:38:43 localhost kernel: nvidia: probe of 0000:01:00.0 failed with error -1
jan 01 21:38:43 localhost kernel: Error: Driver 'nvidia' is already registered, aborting...
jan 01 21:38:43 localhost kernel: NVRM: DRM init failed
Comment 1 Morgan Leijström 2017-01-01 22:32:41 CET
Created attachment 8827 [details]
system log of failed boot

The boot fail regarding Nvidia, enters a loop with about 1 seconds cycle
Marja Van Waes 2017-01-01 23:20:45 CET

CC: (none) => marja11
Assignee: bugsquad => kernel

Comment 2 Thomas Backlund 2017-01-01 23:36:55 CET
are you using bumblebee ?

CC: (none) => tmb

Comment 3 Thomas Backlund 2017-01-01 23:42:32 CET
never mind, its a nvidia driver issue... 

fix coming soon-ish
Comment 4 Daniel Osmari 2017-01-01 23:55:31 CET
Are you sure it isn't the kernel? I see this on top of /var/lib/dkms/nvidia340/340.101-1.mga6.nonfree/4.9.0-desktop-3.mga6/x86_64/log/make.log:



DKMS make.log for nvidia340-340.101-1.mga6.nonfree for kernel 4.9.0-desktop-3.mga6 (x86_64)
Sun Jan  1 20:26:09 BRST 2017
make: Entering directory '/var/lib/dkms/nvidia340/340.101-1.mga6.nonfree/build/uvm'
cp ../Module.symvers Module.symvers
NVIDIA UVM: CC=cc, HOST_CC=cc NV_TARGET_ARCH=x86_64
NVIDIA UVM: CONFTEST=/bin/sh ./conftest.sh cc cc x86_64 /lib/modules/4.9.0-desktop-3.mga6/build /lib/modules/4.9.0-desktop-3.mga6/build
KERNEL_SOURCES: /lib/modules/4.9.0-desktop-3.mga6/build
EXTRA_CFLAGS: -O2  -DNVIDIA_UVM_LITE_ENABLED -DLinux -D__linux__ -DNVIDIA_UVM_RM_ENABLED  -I/var/lib/dkms/nvidia340/340.101-1.mga6.nonfree/build -I./.. -I. -Wall -MD   -Wsign-compare -Wno-cast-qual -Wno-error -D__KERNEL__ -DMODULE -DNVRM -DNV_VERSION_STRING="340.101" -Wno-unused-function -Wuninitialized -fno-strict-aliasing -mno-red-zone -mcmodel=kernel -DNV_UVM_ENABLE -D__linux__ -DNV_DEV_NAME="nvidia-uvm"
NVIDIA: calling KBUILD...
make[1]: Entering directory '/usr/src/kernel-4.9.0-desktop-3.mga6'
test -e include/generated/autoconf.h -a -e include/config/auto.conf || (		\
echo >&2;							\
echo >&2 "  ERROR: Kernel configuration is invalid.";		\
echo >&2 "         include/generated/autoconf.h or include/config/auto.conf are missing.";\
echo >&2 "         Run 'make oldconfig && make prepare' on kernel src to fix it.";	\
echo >&2 ;							\
/bin/false)



And no, I don't have bumblebee.

CC: (none) => danielosmari

Comment 5 Thomas Backlund 2017-01-02 00:24:52 CET
Should be fixed with  nvidia340-340.101-2.mga6
Comment 6 Morgan Leijström 2017-01-02 00:56:38 CET
Thanks for quick action, Thomas :)

Bumblebee not installed.

Waiting for mirror to sync...
Comment 7 Morgan Leijström 2017-01-02 01:19:42 CET
Running it now

I conform it fixed :)

Status: NEW => RESOLVED
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.