Bug 783054 - [abrt] kernel: BUG: sleeping function called from invalid context at mm/memory.c:3905
Summary: [abrt] kernel: BUG: sleeping function called from invalid context at mm/memor...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 19
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:9f80e6231d8d551dfc53e0afca5...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-19 07:30 UTC by Nicolas Mailhot
Modified: 2013-04-23 17:27 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-04-23 17:27:58 UTC
Type: ---


Attachments (Terms of Use)

Description Nicolas Mailhot 2012-01-19 07:30:22 UTC
libreport version: 2.0.8
abrt_version:   2.0.7
cmdline:        ro root=/dev/VolGroup00/systeme SYSFONT=latarcyrheb-sun16 LANG=fr_FR.UTF-8 KEYTABLE=fr-latin9 quiet
kernel:         3.2.1-5.fc17.x86_64
reason:         BUG: sleeping function called from invalid context at mm/memory.c:3905
time:           jeu. 19 janv. 2012 08:09:58 CET

backtrace:
:BUG: sleeping function called from invalid context at mm/memory.c:3905
:in_atomic(): 1, irqs_disabled(): 0, pid: 17265, name: NetworkManager
:INFO: lockdep is turned off.
:Pid: 17265, comm: NetworkManager Not tainted 3.2.1-5.fc17.x86_64 #1
:Call Trace:
: [<ffffffff8105db4a>] __might_sleep+0x13a/0x1f0
: [<ffffffff81165fa8>] might_fault+0x38/0xb0
: [<ffffffff8152b230>] ? sock_def_write_space+0x160/0x160
: [<ffffffff81535bff>] put_cmsg+0x6f/0x110
: [<ffffffff8156a85b>] netlink_recvmsg+0x34b/0x4a0
: [<ffffffff81525c7d>] sock_recvmsg+0xfd/0x130
: [<ffffffff81166015>] ? might_fault+0xa5/0xb0
: [<ffffffff81165fcc>] ? might_fault+0x5c/0xb0
: [<ffffffff81525416>] __sys_recvmsg+0x146/0x2f0
: [<ffffffff811acb35>] ? fget_light+0x45/0x3e0
: [<ffffffff811acbc2>] ? fget_light+0xd2/0x3e0
: [<ffffffff811acb35>] ? fget_light+0x45/0x3e0
: [<ffffffff81528879>] sys_recvmsg+0x49/0x90
: [<ffffffff8167b8c2>] system_call_fastpath+0x16/0x1b

smolt_data:
:
:
:Général
:=================================
:UUID: b78fe0ae-e51d-40f8-8e68-7f2478f9cf2a
:SE: Fedora release 17 (Rawhide)
:Niveau d'exécution par défaut: 5
:Langue: fr_FR.UTF-8
:Plateforme: x86_64
:BogoMIPS: 6333.41
:Fabricant du processeurs: GenuineIntel
:Modèle de processeur: Intel(R) Core(TM)2 Duo CPU     E8500  @ 3.16GHz
:Stepping du processeur: 10
:Famille de processeur: 6
:Modèle du processeur: 23
:Nombre de processeurs: 2
:Vitesse du processeur: 2834
:Mémoire du système: 3936
:Swap du système: 4094
:Fabricant: Gigabyte Technology Co., Ltd.
:Système: EP45-DS5 
:Type d'ordinateur: Desktop
:Noyau: 3.2.1-5.fc17.x86_64
:SELinux activé: 1
:Stratégie SELinux: targeted
:SELinux strict: Permissive
:MythTV Remote: Unknown
:MythTV Role: Unknown
:MythTV Theme: Unknown
:MythTV Plugin: 
:MythTV Tuner: -1
:
:
:Périphériques
:=================================
:(32902:11808:5208:20480) pci, None, HOST/PCI, GA-EP45-DS5 Motherboard
:(32902:11809:5208:20480) pci, pcieport, PCI/PCI, GA-EP45-DS5 Motherboard
:(4332:33128:5208:57344) pci, r8169, ETHERNET, GA-EP45-DS5 Motherboard
:(32902:14896:5208:20481) pci, i801_smbus, SERIAL, GA-EP45-DS5 Motherboard
:(32902:14882:5208:45061) pci, ahci, STORAGE, GA-EP45-DS5 Motherboard
:(32902:14870:5208:20481) pci, None, PCI/ISA, GA-EP45-DS5 Motherboard
:(32902:9294:5208:20480) pci, None, PCI/PCI, GA-EP45-DS5 Motherboard
:(32902:14901:5208:20484) pci, uhci_hcd, USB, GA-EP45-DS5 Motherboard
:(32902:14900:5208:20484) pci, uhci_hcd, USB, GA-EP45-DS5 Motherboard
:(32902:14905:5208:20484) pci, uhci_hcd, USB, GA-EP45-DS5 Motherboard
:(32902:14902:5208:20484) pci, uhci_hcd, USB, GA-EP45-DS5 Motherboard
:(32902:14906:5208:20486) pci, ehci_hcd, USB, GA-EP45-DS5 Motherboard
:(32902:14908:5208:20486) pci, ehci_hcd, USB, GA-EP45-DS5 Motherboard
:(6523:9059:5208:45056) pci, pata_jmicron, STORAGE, GA-EP45-DS5 Motherboard
:(6523:9059:5208:45056) pci, ahci, STORAGE, GA-EP45-DS5 Motherboard
:(32902:14918:5208:20481) pci, pcieport, PCI/PCI, GA-EP45-DS5 Motherboard
:(32902:14912:5208:20481) pci, pcieport, PCI/PCI, GA-EP45-DS5 Motherboard
:(32902:14920:5208:20481) pci, pcieport, PCI/PCI, GA-EP45-DS5 Motherboard
:(32902:14910:5208:41218) pci, snd_hda_intel, MULTIMEDIA, GA-EP45-DS5 Motherboard
:(4354:4:4354:16385) pci, snd_emu10k1, MULTIMEDIA_AUDIO, E-MU 1010
:(32902:14903:5208:20484) pci, uhci_hcd, USB, GA-EP45-DS5 Motherboard
:(4354:16385:4354:16) pci, firewire_ohci, FIREWIRE, SB Audigy FireWire Port
:(17476:22:112:32771) pci, ivtv, MULTIMEDIA_VIDEO, WinTV PVR 150
:(32902:14904:5208:20484) pci, uhci_hcd, USB, GA-EP45-DS5 Motherboard
:(4098:43672:5963:43672) pci, snd_hda_intel, MULTIMEDIA, Sapphire HD 6450 1GB DDR3
:(4098:26489:5963:57700) pci, radeon, VIDEO, Sapphire HD 6450 1GB DDR3
:(32902:14922:5208:20481) pci, pcieport, PCI/PCI, GA-EP45-DS5 Motherboard
:(4332:33128:5208:57344) pci, r8169, ETHERNET, GA-EP45-DS5 Motherboard
:
:
:Informations sur le système de fichiers
:=================================
:device mtpt type bsize frsize blocks bfree bavail file ffree favail
:-------------------------------------------------------------------
:/dev/mapper/VolGroup00-systeme / ext4 4096 4096 12496068 6369803 5740709 3145728 2619865 2619865
:/dev/mapper/VolGroup00-utilisateur /home ext4 4096 4096 25127330 4934223 3675933 6291456 6173030 6173030
:/dev/md0 /boot ext3 4096 4096 516698 488508 462304 131072 131024 131024
:

Comment 1 Josh Boyer 2012-02-02 19:04:31 UTC
Your machine has amazing problems with NetworkManager.  You've got like 5 or 6 open bugs with traces from NM.

Can you describe your networking setup a bit?  Are you using l2tp at all?  Or some other odd setup?

Comment 2 Nicolas Mailhot 2012-02-11 15:00:38 UTC
It's a rather plain desktop system with two network interfaces

One is usually left alone (I used to plug other computers there)
The other is connected to the ipv6-capable ISP box

The local system runs a webmail instance as I've given up on evo ever working reliably, and I often need to read my mail remotely on restricted networks that only allow outgoing http/s

To permit direct local access to the webmail and avoid problems when the isp dnses are down name resolution is provided by a local caching bind server that also overrides the Internet-facing system ip with a local one

$ORIGIN .
$TTL 86400      ; 1 day
arekh.dyndns.org        IN SOA  arekh.dyndns.org. arekh.dyndns.org. (
                                5          ; serial
                                10800      ; refresh (3 hours)
                                900        ; retry (15 minutes)
                                604800     ; expire (1 week)
                                86400      ; minimum (1 day)
                                )
                        NS      arekh.dyndns.org.
arekh.dyndns.org        A       192.168.0.4

(plus a few other tweaks)

The isp box is configured to relay external http requests to this desktop

I used to run a local proxy to avoid overloading koji when I need to download many times the same rpm over a few days (since yum requires nuking its caches very time there's a problem) but I didn't have the time to figure how to make tproxy work in an IPv6 world so this part is disabled in iptables for now and squid is shut down

Comment 3 Nicolas Mailhot 2012-02-11 15:07:01 UTC
This probably mutated in bug #785346

Different symptoms, same results

Comment 4 Fedora End Of Life 2013-04-03 15:38:28 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.

(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19

Comment 5 Justin M. Forbes 2013-04-05 19:38:19 UTC
f

Comment 6 Justin M. Forbes 2013-04-23 17:27:58 UTC
This bug is being closed with INSUFFICIENT_DATA as there has not been a
response in 2 weeks.  If you are still experiencing this issue,
please reopen and attach the relevant data from the latest kernel you are
running and any data that might have been requested previously.


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