All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: Christoph Lameter <clameter@sgi.com>
Cc: "Luck, Tony" <tony.luck@intel.com>, David Chinner <dgc@sgi.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	lkml <linux-kernel@vger.kernel.org>,
	linux-ia64@vger.kernel.org, Sam Ravnborg <sam@ravnborg.org>
Subject: Re: BUG: sleeping function called from invalid context at kernel/fork.c:385
Date: Wed, 30 May 2007 23:55:47 +0000	[thread overview]
Message-ID: <465E0F03.6000103@oracle.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0705301652100.3731@schroedinger.engr.sgi.com>

Christoph Lameter wrote:
> On Wed, 30 May 2007, Randy Dunlap wrote:
> 
>>> Right. I have no idea where to look. The function has no name? Or is the 
>>> segment .exit.text referenced by namne in .init.text?
>> Maybe 'objdump drivers/built-in.o and then grep that output (file)
>> for /exit.text/ ...

OK.  I would write the file to disk and view it with an editor.
Then at each occurrence of /exit.text/, see if it's inside an __init function...


> clameter@schroedinger:~/software/slub$ objdump -t drivers/built-in.o |grep "exit.text"
> 0000000000000000 l    d  .exit.text     0000000000000000 .exit.text
> 0000000000000000 l    d  *ABS*  0000000000000000 .rela.exit.text
> 0000000000000000 l    d  .IA_64.unwind_info.exit.text   0000000000000000 .IA_64.unwind_info.exit.text
> 0000000000000000 l    d  .IA_64.unwind.exit.text        0000000000000000 .IA_64.unwind.exit.text
> 0000000000000000 l    d  *ABS*  0000000000000000 .rela.IA_64.unwind.exit.text
> 0000000000000000 l     F .exit.text     0000000000000050 pcie_portdrv_exit
> 0000000000000060 l     F .exit.text     0000000000000040 aer_service_exit
> 00000000000000a0 l     F .exit.text     0000000000000040 pci_hotplug_exit
> 00000000000000e0 l     F .exit.text     00000000000000b0 pcied_cleanup
> 00000000000001a0 l     F .exit.text     0000000000000160 mspec_exit
> 0000000000000300 l     F .exit.text     0000000000000010 efi_rtc_exit
> 0000000000000320 l     F .exit.text     0000000000000010 agp_exit
> 0000000000000340 l     F .exit.text     00000000000000a0 sn_sal_module_exit
> 00000000000003e0 l     F .exit.text     0000000000000040 firmware_class_exit
> 0000000000000420 l     F .exit.text     0000000000000110 rd_cleanup
> 0000000000000540 l     F .exit.text     00000000000001d0 loop_exit
> 0000000000000720 l     F .exit.text     0000000000000040 tg3_cleanup
> 0000000000000760 l     F .exit.text     0000000000000040 idedisk_exit
> 00000000000007a0 l     F .exit.text     0000000000000040 ide_cdrom_exit
> 00000000000007e0 l     F .exit.text     00000000000000a0 exit_scsi
> 0000000000000880 l     F .exit.text     0000000000000080 spi_transport_exit
> 0000000000000900 l     F .exit.text     00000000000000a0 fc_transport_exit
> 00000000000009a0 l     F .exit.text     00000000000000e0 sas_transport_exit
> 0000000000000a80 l     F .exit.text     0000000000000040 sas_class_exit
> 0000000000000ac0 l     F .exit.text     0000000000000040 qla1280_exit
> 0000000000000b00 l     F .exit.text     0000000000000140 qla2x00_module_exit
> 0000000000000c40 l     F .exit.text     00000000000000a0 exit_sd
> 0000000000000ce0 l     F .exit.text     0000000000000060 ata_exit
> 0000000000000d40 l     F .exit.text     0000000000000040 vsc_sata_exit
> 0000000000000d80 l     F .exit.text     00000000000000d0 fusion_exit
> 0000000000000e60 l     F .exit.text     00000000000000e0 mptspi_exit
> 0000000000000f40 l     F .exit.text     00000000000000d0 mptfc_exit
> 0000000000001020 l     F .exit.text     00000000000000f0 mptsas_exit
> 0000000000001120 l     F .exit.text     0000000000000060 cdrom_exit
> 0000000000001180 l     F .exit.text     0000000000000080 input_exit
> 0000000000001200 l     F .exit.text     0000000000000070 mousedev_exit
> 0000000000001280 l     F .exit.text     0000000000000040 multipath_exit
> 00000000000012c0 l     F .exit.text     0000000000000240 md_exit
> 0000000000001500 l     F .exit.text     0000000000000090 dm_exit
> 00000000000015a0 l     F .exit.text     0000000000000170 efivars_exit
> 0000000000001720 l     F .exit.text     0000000000000010 hid_exit
> 


-- 
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***

WARNING: multiple messages have this Message-ID (diff)
From: Randy Dunlap <randy.dunlap@oracle.com>
To: Christoph Lameter <clameter@sgi.com>
Cc: "Luck, Tony" <tony.luck@intel.com>, David Chinner <dgc@sgi.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	lkml <linux-kernel@vger.kernel.org>,
	linux-ia64@vger.kernel.org, Sam Ravnborg <sam@ravnborg.org>
Subject: Re: BUG: sleeping function called from invalid context at kernel/fork.c:385
Date: Wed, 30 May 2007 16:55:47 -0700	[thread overview]
Message-ID: <465E0F03.6000103@oracle.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0705301652100.3731@schroedinger.engr.sgi.com>

Christoph Lameter wrote:
> On Wed, 30 May 2007, Randy Dunlap wrote:
> 
>>> Right. I have no idea where to look. The function has no name? Or is the 
>>> segment .exit.text referenced by namne in .init.text?
>> Maybe 'objdump drivers/built-in.o and then grep that output (file)
>> for /exit.text/ ...

OK.  I would write the file to disk and view it with an editor.
Then at each occurrence of /exit.text/, see if it's inside an __init function...


> clameter@schroedinger:~/software/slub$ objdump -t drivers/built-in.o |grep "exit.text"
> 0000000000000000 l    d  .exit.text     0000000000000000 .exit.text
> 0000000000000000 l    d  *ABS*  0000000000000000 .rela.exit.text
> 0000000000000000 l    d  .IA_64.unwind_info.exit.text   0000000000000000 .IA_64.unwind_info.exit.text
> 0000000000000000 l    d  .IA_64.unwind.exit.text        0000000000000000 .IA_64.unwind.exit.text
> 0000000000000000 l    d  *ABS*  0000000000000000 .rela.IA_64.unwind.exit.text
> 0000000000000000 l     F .exit.text     0000000000000050 pcie_portdrv_exit
> 0000000000000060 l     F .exit.text     0000000000000040 aer_service_exit
> 00000000000000a0 l     F .exit.text     0000000000000040 pci_hotplug_exit
> 00000000000000e0 l     F .exit.text     00000000000000b0 pcied_cleanup
> 00000000000001a0 l     F .exit.text     0000000000000160 mspec_exit
> 0000000000000300 l     F .exit.text     0000000000000010 efi_rtc_exit
> 0000000000000320 l     F .exit.text     0000000000000010 agp_exit
> 0000000000000340 l     F .exit.text     00000000000000a0 sn_sal_module_exit
> 00000000000003e0 l     F .exit.text     0000000000000040 firmware_class_exit
> 0000000000000420 l     F .exit.text     0000000000000110 rd_cleanup
> 0000000000000540 l     F .exit.text     00000000000001d0 loop_exit
> 0000000000000720 l     F .exit.text     0000000000000040 tg3_cleanup
> 0000000000000760 l     F .exit.text     0000000000000040 idedisk_exit
> 00000000000007a0 l     F .exit.text     0000000000000040 ide_cdrom_exit
> 00000000000007e0 l     F .exit.text     00000000000000a0 exit_scsi
> 0000000000000880 l     F .exit.text     0000000000000080 spi_transport_exit
> 0000000000000900 l     F .exit.text     00000000000000a0 fc_transport_exit
> 00000000000009a0 l     F .exit.text     00000000000000e0 sas_transport_exit
> 0000000000000a80 l     F .exit.text     0000000000000040 sas_class_exit
> 0000000000000ac0 l     F .exit.text     0000000000000040 qla1280_exit
> 0000000000000b00 l     F .exit.text     0000000000000140 qla2x00_module_exit
> 0000000000000c40 l     F .exit.text     00000000000000a0 exit_sd
> 0000000000000ce0 l     F .exit.text     0000000000000060 ata_exit
> 0000000000000d40 l     F .exit.text     0000000000000040 vsc_sata_exit
> 0000000000000d80 l     F .exit.text     00000000000000d0 fusion_exit
> 0000000000000e60 l     F .exit.text     00000000000000e0 mptspi_exit
> 0000000000000f40 l     F .exit.text     00000000000000d0 mptfc_exit
> 0000000000001020 l     F .exit.text     00000000000000f0 mptsas_exit
> 0000000000001120 l     F .exit.text     0000000000000060 cdrom_exit
> 0000000000001180 l     F .exit.text     0000000000000080 input_exit
> 0000000000001200 l     F .exit.text     0000000000000070 mousedev_exit
> 0000000000001280 l     F .exit.text     0000000000000040 multipath_exit
> 00000000000012c0 l     F .exit.text     0000000000000240 md_exit
> 0000000000001500 l     F .exit.text     0000000000000090 dm_exit
> 00000000000015a0 l     F .exit.text     0000000000000170 efivars_exit
> 0000000000001720 l     F .exit.text     0000000000000010 hid_exit
> 


-- 
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***

  reply	other threads:[~2007-05-30 23:55 UTC|newest]

Thread overview: 81+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-23  6:31 BUG: sleeping function called from invalid context at kernel/fork.c:385 David Chinner
2007-05-23  6:43 ` BUG: sleeping function called from invalid context at Andrew Morton
2007-05-23  6:43   ` BUG: sleeping function called from invalid context at kernel/fork.c:385 Andrew Morton
2007-05-23 17:44   ` Luck, Tony
2007-05-23 17:44     ` Luck, Tony
2007-05-30  3:30     ` David Chinner
2007-05-30  3:30       ` David Chinner
2007-05-30  4:44       ` David Chinner
2007-05-30  4:44         ` David Chinner
2007-05-30 20:11   ` Luck, Tony
2007-05-30 20:11     ` Luck, Tony
2007-05-30 22:39     ` BUG: sleeping function called from invalid context at Christoph Lameter
2007-05-30 22:39       ` BUG: sleeping function called from invalid context at kernel/fork.c:385 Christoph Lameter
2007-05-31  0:53     ` David Chinner
2007-05-31  0:53       ` David Chinner
2007-06-04  5:14       ` Peter Chubb
2007-06-04  5:14         ` Peter Chubb
2007-05-30 23:19   ` Luck, Tony
2007-05-30 23:19     ` Luck, Tony
2007-05-30 23:31     ` BUG: sleeping function called from invalid context at Christoph Lameter
2007-05-30 23:31       ` BUG: sleeping function called from invalid context at kernel/fork.c:385 Christoph Lameter
2007-05-30 23:34       ` BUG: sleeping function called from invalid context at Randy Dunlap
2007-05-30 23:34         ` BUG: sleeping function called from invalid context at kernel/fork.c:385 Randy Dunlap
2007-05-30 23:53         ` BUG: sleeping function called from invalid context at Christoph Lameter
2007-05-30 23:53           ` BUG: sleeping function called from invalid context at kernel/fork.c:385 Christoph Lameter
2007-05-30 23:55           ` Randy Dunlap [this message]
2007-05-30 23:55             ` Randy Dunlap
2007-05-31  0:09             ` BUG: sleeping function called from invalid context at Christoph Lameter
2007-05-31  0:09               ` BUG: sleeping function called from invalid context at kernel/fork.c:385 Christoph Lameter
2007-05-31  6:12               ` BUG: sleeping function called from invalid context at Randy Dunlap
2007-05-31  6:12                 ` BUG: sleeping function called from invalid context at kernel/fork.c:385 Randy Dunlap
2007-05-31  4:43       ` Sam Ravnborg
2007-05-31  4:43         ` Sam Ravnborg
2007-05-30 23:56   ` Yu, Fenghua
2007-05-30 23:56     ` Yu, Fenghua
2007-05-31  2:37   ` Luck, Tony
2007-05-31  2:37     ` Luck, Tony
2007-05-31  3:19     ` BUG: sleeping function called from invalid context at Christoph Lameter
2007-05-31  3:19       ` BUG: sleeping function called from invalid context at kernel/fork.c:385 Christoph Lameter
2007-05-31 15:20       ` Prarit Bhargava
2007-05-31 15:20         ` Prarit Bhargava
2007-05-31 19:54         ` Sam Ravnborg
2007-05-31 19:54           ` Sam Ravnborg
2007-05-31 20:04         ` Sam Ravnborg
2007-05-31 20:04           ` Sam Ravnborg
2007-05-31 20:08           ` [PATCH] net/hp100: fix section mismatch warning Sam Ravnborg
2007-05-31 20:08             ` Sam Ravnborg
2007-05-31 20:17           ` [PATCH] kvm: fix section mismatch warning in kvm-intel.o Sam Ravnborg
2007-05-31 20:17             ` Sam Ravnborg
2007-05-31 20:24           ` [PATCH] acpi: fix section mismatch warning in asus_acpi.o Sam Ravnborg
2007-05-31 20:24             ` Sam Ravnborg
2007-05-31 20:29             ` [PATCH] acpi: fix section mismatch warning in asus + toshiba Sam Ravnborg
2007-05-31 20:29               ` Sam Ravnborg
2007-05-31 20:46           ` [PATCH] isdn: fix section mismatch warnings Sam Ravnborg
2007-05-31 20:46             ` Sam Ravnborg
2007-05-31 20:51           ` [PATCH] microcode: fix section mismatch warning Sam Ravnborg
2007-05-31 20:51             ` Sam Ravnborg
2007-05-31 20:42         ` BUG: sleeping function called from invalid context at Christoph Lameter
2007-05-31 20:42           ` BUG: sleeping function called from invalid context at kernel/fork.c:385 Christoph Lameter
2007-06-01  3:18   ` Luck, Tony
2007-06-01  3:18     ` Luck, Tony
2007-06-01  3:31     ` Prarit Bhargava
2007-06-01  3:31       ` Prarit Bhargava
2007-06-01  4:05       ` BUG: sleeping function called from invalid context at Christoph Lameter
2007-06-01  4:05         ` BUG: sleeping function called from invalid context at kernel/fork.c:385 Christoph Lameter
2007-06-01  4:17         ` Sam Ravnborg
2007-06-01  4:17           ` Sam Ravnborg
2007-06-01  4:45           ` BUG: sleeping function called from invalid context at Christoph Lameter
2007-06-01  4:45             ` BUG: sleeping function called from invalid context at kernel/fork.c:385 Christoph Lameter
2007-06-01  6:42             ` Sam Ravnborg
2007-06-01  6:42               ` Sam Ravnborg
2007-06-01  8:00   ` Luck, Tony
2007-06-01  8:00     ` Luck, Tony
2007-06-01 10:30     ` Prarit Bhargava
2007-06-01 10:30       ` Prarit Bhargava
2007-06-05 14:55     ` linux-ia64 build warning messages Russ Anderson
2007-06-05 14:55       ` Russ Anderson
2007-06-07  5:00       ` Peter Chubb
2007-06-07  5:00         ` Peter Chubb
2007-06-01 10:37   ` BUG: sleeping function called from invalid context at kernel/fork.c:385 Luck, Tony
2007-06-01 10:37     ` Luck, Tony

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=465E0F03.6000103@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=clameter@sgi.com \
    --cc=dgc@sgi.com \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.org \
    --cc=tony.luck@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.