Bug 1449 - sleeping function called from invalid context
Summary: sleeping function called from invalid context
Status: CLOSED PATCH_ALREADY_AVAILABLE
Alias: None
Product: Drivers
Classification: Unclassified
Component: IEEE1394 (show other bugs)
Hardware: i386 Linux
: P2 normal
Assignee: Ben Collins
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-10-29 08:27 UTC by Andrew Novikov
Modified: 2004-07-17 17:45 UTC (History)
1 user (show)

See Also:
Kernel Version: 2.6.0-test9
Subsystem:
Regression: ---
Bisected commit-id:


Attachments

Description Andrew Novikov 2003-10-29 08:27:56 UTC
During the boot process I get the following messages: 
 
ohci1394: $Rev: 1045 $ Ben Collins <bcollins@debian.org> 
PCI: Enabling device 0000:02:00.0 (0110 -> 0112) 
ohci1394_0: OHCI-1394 1.1 (PCI): IRQ=[9]  MMIO=[e8204000-e82047ff]  Max 
Packet=[2048] 
Debug: sleeping function called from invalid context at mm/slab.c:1856 
in_atomic():1, irqs_disabled():0 
Call Trace: 
 [<c011c42a>] __might_sleep+0xab/0xcd 
 [<c013ffbe>] __kmalloc+0x88/0x8f 
 [<d097d274>] hpsb_create_hostinfo+0x60/0xdd [ieee1394] 
 [<d0981c7e>] nodemgr_add_host+0x24/0x130 [ieee1394] 
 [<d09397bd>] ohci_initialize+0x212/0x21a [ohci1394] 
 [<d097da69>] highlevel_add_host+0x6f/0x73 [ieee1394] 
 [<d097d09e>] hpsb_add_host+0x6d/0x93 [ieee1394] 
 [<d093d960>] ohci1394_pci_probe+0x48b/0x599 [ohci1394] 
 [<d093b7a7>] ohci_irq_handler+0x0/0x7b6 [ohci1394] 
 [<c0200f01>] pci_device_probe_static+0x4d/0x5e 
 [<c0200f4a>] __pci_device_probe+0x38/0x4b 
 [<c0200f89>] pci_device_probe+0x2c/0x48 
 [<c026724c>] bus_match+0x3d/0x65 
 [<c0267365>] driver_attach+0x59/0x83 
 [<c0267629>] bus_add_driver+0x9d/0xaf 
 [<c0267a27>] driver_register+0x31/0x35 
 [<c0201140>] pci_register_driver+0x5b/0x80 
 [<d0942015>] ohci1394_init+0x15/0x3e [ohci1394] 
 [<c01345ed>] sys_init_module+0x14e/0x2a3 
 [<c010a2f9>] sysenter_past_esp+0x52/0x71 
 
ieee1394: Host added: ID:BUS[0-00:1023]  GUID[00023f2a1d000cf8]
Comment 1 Ben Collins 2003-10-29 09:24:09 UTC
This is fixed in the SVN tree, is known and will be merged to 2.6 after 2.6.0 is
released.
Comment 2 Adrian Bunk 2004-07-17 17:45:59 UTC
According to the comment of Ben, it should already have been fixed in recent 2.6
kernels.

Please report if this isn't true.

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