growbag
#1
I get this now on every boot:
p, li { white-space: pre-wrap; } <4>------------ cut here ]------------
<4>WARNING: at kernel/softirq.c:137 local_bh_enable+0x3c/0x92()
<4>Modules linked in: sha256_generic aes_x86_64 aes_generic cbc uhci_hcd dm_crypt loop dm_mod arc4 ecb crypto_blkcipher b43(N) rfkill mac80211 cfg80211 led_class input_polldev snd_hda_intel sdhci_pci snd_pcm uvcvideo snd_timer ssb compat_ioctl32 video sdhci rtc_cmos usbhid pcmcia ohci1394 snd_page_alloc sr_mod output nvidia(PX) wmi rtc_core hid snd_hwdep videodev ricoh_mmc battery mmc_core snd cdrom v4l1_compat pcmcia_core button ac ieee1394 rtc_lib i2c_nforce2 forcedeth ff_memless sg k8temp(N) soundcore pcspkr joydev i2c_core sd_mod crc_t10dif ohci_hcd ehci_hcd usbcore edd reiserfs fan ide_pci_generic amd74xx ide_core ata_generic thermal processor thermal_sys hwmon ahci pata_amd libata scsi_mod dock
<4>Supported: No
<4>Pid: 2002, comm: cryptsetup Tainted: P 2.6.27.19-3.2-default #1
<4>
<4>Call Trace:
<4> <ffffffff8020da29>] show_trace_log_lvl+0x41/0x58
<4> <ffffffff8049a3da>] dump_stack+0x69/0x6f
<4> <ffffffff8023d562>] warn_on_slowpath+0x51/0x77
<4> <ffffffff802425b3>] local_bh_enable+0x3c/0x92
<4> <ffffffff80433be7>] sk_filter+0x97/0xa0
<4> <ffffffff80441a42>] netlink_broadcast+0x220/0x386
<4> <ffffffff803614cd>] kobject_uevent_env+0x452/0x520
<4> <ffffffff803401d7>] set_disk_ro+0x58/0x8d
<4> <ffffffffa0b681d1>] __bind+0x11d/0x136 [dm_mod]
<4> <ffffffffa0b6823e>] dm_swap_table+0x54/0x70 [dm_mod]
<4> <ffffffffa0b6c766>] do_resume+0xa9/0x122 [dm_mod]
<4> <ffffffffa0b6d17d>] ctl_ioctl+0x1cb/0x213 [dm_mod]
<4> <ffffffffa0b6d1d3>] dm_ctl_ioctl+0xe/0x12 [dm_mod]
<4> <ffffffff802bd249>] vfs_ioctl+0x21/0x6c
<4> <ffffffff802bd4b6>] do_vfs_ioctl+0x222/0x231
<4> <ffffffff802bd516>] sys_ioctl+0x51/0x73
<4> <ffffffff8020bfbb>] system_call_fastpath+0x16/0x1b
<4> <00007f2761738b77>] 0x7f2761738b77
<4>
<4>— end trace 6f6c602d55bf2b45 ]—
Any ideas what it means? Thanks 
it seems like checking the system and its devises
user
#3
I am getting that error too. Everything seems to be working fine though. What scares me most is the sentence “cryptsetup Tainted”! :S
------------ cut here ]------------
WARNING: at kernel/softirq.c:137 local_bh_enable+0x2f/0x79()
Modules linked in: sha256_generic aes_i586 aes_generic cbc usbhid hid ff_memless ohci_hcd dm_crypt ext2 loop arc4 ecb crypto_blkcipher snd_hda_intel snd_pcm iwl3945 rfkill snd_timer rtc_cmos hci_usb(N) snd_page_alloc rtc_core mac80211 s
nd_hwdep snd rtc_lib pcspkr video led_class dcdbas(X) iTCO_wdt btusb joydev intel_agp sr_mod output i2c_i801 tg3 iTCO_vendor_support button wmi battery ac soundcore libphy i2c_core agpgart cdrom cfg80211 sg bluetooth linear uhci_hcd ehc
i_hcd sd_mod crc_t10dif usbcore dm_snapshot edd dm_mod ext3 mbcache jbd fan ide_pci_generic piix ide_core ata_generic ata_piix libata scsi_mod dock thermal processor thermal_sys hwmon
Supported: No
Pid: 2184, comm: cryptsetup Tainted: G 2.6.27.19-3.2-pae #1
<c01061cc>] dump_trace+0x6b/0x249
<c0106ca3>] show_trace+0x20/0x39
<c0347a23>] dump_stack+0x71/0x76
<c0129cc0>] warn_on_slowpath+0x4d/0x70
<c012e7a9>] local_bh_enable+0x2f/0x79
<c02edd8f>] sk_filter+0x7f/0x88
<c02f8c2c>] netlink_broadcast+0x1dd/0x31f
<c022c297>] kobject_uevent_env+0x439/0x4f5
<c020de10>] set_disk_ro+0x50/0x7b
<f92a7181>] __bind+0x110/0x122 [dm_mod]
<f92a71e0>] dm_swap_table+0x4d/0x66 [dm_mod]
<f92ab17b>] do_resume+0x90/0xf8 [dm_mod]
<f92aba54>] ctl_ioctl+0x1bd/0x1fb [dm_mod]
<c019c96f>] vfs_ioctl+0x1f/0x62
<c019cc03>] do_vfs_ioctl+0x167/0x172
<c019cc53>] sys_ioctl+0x45/0x5e
<c01049ad>] sysenter_do_call+0x12/0x21
<ffffe430>] 0xffffe430
=======================
--- end trace ad0a4fcb0f7ee96f ]---
As you both can see, it says nothing about ERROR, or FATAL, it says WARNING. Since everything works just let it be.
user
#5
Hi Knurpht,
you’re right, everything seems to work ok. Yet I am pretty concerned about the relationship between these two words that appear side by side:
cryptsetup Tainted
It would be quite silly to be using encrypted partitions and not worry about such a message, don’t you agree?
Cheers!
This was fixed by yesterday’s kernel update.
user
#7
2.6.27.21-0.1-pae #1 SMP 2009-03-31 14:50:44 +0200 i686 i686 i386 GNU/Linux
fixed for me too
Thanks you both!
Cheers!