<---- template headericclude ----->
Fedora 18 woes: Tainted Kernel- (flags:GW) ?
FedoraForum.org - Fedora Support Forums and Community
Results 1 to 8 of 8
  1. #1
    Join Date
    Nov 2008
    Posts
    117
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Fedora 18 woes: Tainted Kernel- (flags:GW) ?

    I am a reluctant convert from Fedora-14 to Fedora 18. On the new installation,
    I have been getting dozens of these kernel problem messages:
    A kernel problem occurred, but your kernel has been tainted (flags GW).
    Kernel maintainers are unable to diagnose tainted reports.
    Reading through previous discussions about tainted kernels, I understand
    that this happens if you have installed proprietary modules.
    However, I have no proprietary drivers at all.
    All software on this computer is from fedora, fedora-updates and rpmfusion*.
    (I have installed only the widely used MP3 encoders etc. from rpmfusion).

    The bug reporter interface will not let me delete all these reports at one go --
    I must individually select each one and delete. Nor will it let me cut and paste the message!
    I have had to retype the message above - I hope it is accurate.

    I also get warnings about some problems with drivers/gpu/drm/i915/intel_pm.c.
    This driver was installed by anaconda, so should not be the source of kernel "tainting".

    How do I make my kernel untainted and pristine?

  2. #2
    pjfg Guest

    Re: Fedora 18 woes: Tainted Kernel- (flags:GW) ?

    Run "dmesg | grep taints" and see if that reports any module.

  3. #3
    Join Date
    Mar 2007
    Posts
    35
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Fedora 18 woes: Tainted Kernel- (flags:GW) ?

    I am also getting this, in Fedora 17. Grepping for taint in dmesg produces no output.

    ---------- Post added at 12:09 AM ---------- Previous post was at 12:01 AM ----------

    Aaah, but grep -i taint does.

    Feb 18 19:42:01 idefix kernel: [21813.107963] Pid: 7, comm: kworker/u:0H Not tainted 3.7.3-101.fc17.i686 #1
    Feb 18 19:42:01 idefix kernel: [21813.108500] Pid: 7, comm: kworker/u:0H Tainted: G W 3.7.3-101.fc17.i686 #1
    Feb 18 19:42:10 idefix kernel: [21822.766054] Pid: 544, comm: bluetoothd Tainted: G W 3.7.3-101.fc17.i686 #1
    Feb 18 19:42:11 idefix kernel: [21823.267103] Pid: 2674, comm: khidpd_04614b01 Tainted: G W 3.7.3-101.fc17.i686 #1 LENOVO 2008AL8/2008AL8

    I don't think that I have done anything specific to get anything that should taint the kernel, so why is my use of bluetooth tainting the kernel?

  4. #4
    pjfg Guest

    Re: Fedora 18 woes: Tainted Kernel- (flags:GW) ?

    It appears that the G flag is for a GPL licensed module (outside of the linux kernel) so it could be some module bundled with the Fedora install quite legitimately. A P flag would signal a proprietary module such as the fglrx (AMD Catalyst).

    The should be a message indicating the module name as it loads. If you are grep'ing the output of dmesg and not getting a module name returned could be due to the message buffer having filled and over-written the message. Try immediately after booting.

  5. #5
    Join Date
    Aug 2009
    Posts
    11,397
    Mentioned
    98 Post(s)
    Tagged
    0 Thread(s)

    Re: Fedora 18 woes: Tainted Kernel- (flags:GW) ?

    Well, the first message tells him that the kernel is not tainted. Once it gets the first oops, then the kernel is tainted. That is by design. A kernel that has crashed is marked as tainted.

    It's not a module being loaded that is tainting the kernel, It is a previous crash.

  6. #6
    Join Date
    Mar 2007
    Posts
    35
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Fedora 18 woes: Tainted Kernel- (flags:GW) ?

    Aah, that makes sense (W being a previous crash).
    Last edited by pfps; 20th February 2013 at 01:49 AM.

  7. #7
    Join Date
    Nov 2008
    Posts
    117
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Fedora 18 woes: Tainted Kernel- (flags:GW) ?

    Thanks DBelton. dmesg did not report a tainted message for me, either.
    Quote Originally Posted by DBelton
    Well, the first message tells him that the kernel is not tainted. Once it gets the first oops, then the kernel is tainted. That is by design. A kernel that has crashed is marked as tainted.

    It's not a module being loaded that is tainting the kernel, It is a previous crash.
    The gpu related message that I reported in my first submission probably results in
    Code:
    dmesg |grep taint
    [  516.507239] Pid: 819, comm: Xorg Not tainted 3.7.8-202.fc18.i686.PAE #1
    I understand the messages a little better now. However, the problem (and the associated annoyance caused by the user interface) still remains.

  8. #8
    Join Date
    Jul 2004
    Location
    Scotland
    Posts
    53
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Fedora 18 woes: Tainted Kernel- (flags:GW) ?

    I'm getting this as well since I installed Fedora 18 and updated (a few days ago). I think it's down to the Intel graphics module and dpms (display power management signalling) - Although I can't reproduce by changing the brightness using keyboard shortcusts on my dell xps m1330n

    from /var/log/messages:

    Code:
    ar 17 13:15:05 c4111um systemd[1]: Started Hostname Service.
    Mar 17 13:17:06 c4111um kernel: [ 2059.004577] ------------[ cut here ]------------
    Mar 17 13:17:06 c4111um kernel: [ 2059.004637] WARNING: at drivers/gpu/drm/i915/intel_display.c:3882 intel_modeset_check_state+0x
    4ce/0x610 [i915]()
    Mar 17 13:17:06 c4111um kernel: [ 2059.004641] Hardware name: XPS M1330                       
    Mar 17 13:17:06 c4111um kernel: [ 2059.004645] wrong connector dpms state
    Mar 17 13:17:06 c4111um kernel: [ 2059.004647] Modules linked in: fuse ebtable_nat nf_conntrack_netbios_ns nf_conntrack_broadcast
     ipt_MASQUERADE ip6table_mangle ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6 iptable_nat nf_nat_ipv4 nf_nat be2iscsi iscsi_boot_s
    ysfs iptable_mangle bnx2i cnic uio nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack cxgb4i cxgb4 cxgb3i ebtable_filter 
    bnep ebtables bluetooth cxgb3 ip6table_filter mdio libcxgbi ip6_tables ib_iser rdma_cm ib_addr iw_cm ib_cm ib_sa ib_mad ib_core i
    scsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi dm_crypt uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core videodev 
    snd_hda_codec_hdmi arc4 media iwl3945 iwlegacy snd_hda_codec_idt mac80211 snd_hda_intel snd_hda_codec snd_hwdep snd_seq snd_seq_d
    evice r592 memstick iTCO_wdt iTCO_vendor_support tg3 ptp pps_core i2c_i801 coretemp lpc_ich snd_pcm snd_page_alloc snd_timer micr
    ocode cfg80211 snd soundcore rfkill mfd_core dell_laptop dell_wmi sparse_keymap dcdbas uinput i915 firewire_ohci i2c_algo_bit drm
    _kms_helper firewire_core crc_itu_t sdhci_pci sdhci mmc_core drm i2c_core wmi video
    Mar 17 13:17:06 c4111um kernel: [ 2059.004782] Pid: 792, comm: X Not tainted 3.8.3-201.fc18.x86_64 #1
    Mar 17 13:17:06 c4111um kernel: [ 2059.004785] Call Trace:

    and a grep of dmesg:
    Code:
    [root@c4111um ~]# dmesg | grep -i taint
    [ 1063.623850] Pid: 924, comm: X Not tainted 3.8.3-201.fc18.x86_64 #1
    [ 1063.624388] Pid: 924, comm: X Tainted: G        W    3.8.3-201.fc18.x86_64 #1
    [ 1063.624894] Pid: 924, comm: X Tainted: G        W    3.8.3-201.fc18.x86_64 #1
    [ 1063.625384] Pid: 924, comm: X Tainted: G        W    3.8.3-201.fc18.x86_64 #1
    [ 1063.625818] Pid: 924, comm: X Tainted: G        W    3.8.3-201.fc18.x86_64 #1
    [ 1273.307925] Pid: 924, comm: X Tainted: G        W    3.8.3-201.fc18.x86_64 #1
    [ 1273.308471] Pid: 924, comm: X Tainted: G        W    3.8.3-201.fc18.x86_64 #1
    [ 1273.308910] Pid: 924, comm: X Tainted: G        W    3.8.3-201.fc18.x86_64 #1
    [ 1273.309373] Pid: 924, comm: X Tainted: G        W    3.8.3-201.fc18.x86_64 #1
    [ 1273.309812] Pid: 924, comm: X Tainted: G        W    3.8.3-201.fc18.x86_64 #1
    [ 2120.981881] Pid: 924, comm: X Tainted: G        W    3.8.3-201.fc18.x86_64 #1
    [ 2120.982412] Pid: 924, comm: X Tainted: G        W    3.8.3-201.fc18.x86_64 #1
    (and a lot more of those!)

    has anyone got any pointers about what to look at next? I have the same problem as the original poster in that the KDE "notifications" pop up all the time and it takes a while to manually clear each notification.

    ---------- Post added at 03:22 PM ---------- Previous post was at 03:17 PM ----------

    hmmm, looks like I'm not the only one:

    https://bugzilla.redhat.com/show_bug.cgi?id=922403
    https://bugzilla.redhat.com/show_bug.cgi?id=919699
    https://bugzilla.redhat.com/show_bug.cgi?id=918861

Similar Threads

  1. Kernel tainted message
    By broadstairs in forum Using Fedora
    Replies: 0
    Last Post: 30th November 2012, 02:13 PM
  2. F17 Kernel Tainted
    By KitchiRUs in forum Using Fedora
    Replies: 13
    Last Post: 16th September 2012, 06:23 PM
  3. Tainted Kernel
    By zedth2 in forum Using Fedora
    Replies: 6
    Last Post: 3rd June 2012, 05:06 PM
  4. Replies: 7
    Last Post: 18th February 2012, 01:51 PM
  5. New Kernel Tainted?
    By Magickman in forum Using Fedora
    Replies: 13
    Last Post: 16th February 2011, 11:29 PM

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
[[template footer(Guest)]]