From: Robert Gadsdon <robert@rgadsdon2.giointernet.co.uk>
To: linux kernel <linux-kernel@vger.kernel.org>
Subject: 2.6.6-rc2 - debug/trace messages
Date: Fri, 23 Apr 2004 10:11:28 +0100 [thread overview]
Message-ID: <4088DDC0.8080701@rgadsdon2.giointernet.co.uk> (raw)
The following 'debug' traces from 2.6.6-rc2:
-------------------------------------------------------------------
Debug: sleeping function called from invalid context at mm/slab.c:1954
in_atomic():1, irqs_disabled():1
Call Trace:
[<c011bf87>] __might_sleep+0xb7/0xe0
[<c014335f>] __kmalloc+0x9f/0xb0
[<f890dc84>] alloc_dma_rcv_ctx+0x64/0x3f0 [ohci1394]
[<c014b2a4>] do_no_page+0x204/0x3d0
[<f890b1ec>] ohci_devctl+0x3cc/0x640 [ohci1394]
[<c014b6a6>] handle_mm_fault+0x106/0x1b0
[<f89e8399>] hpsb_listen_channel+0x49/0x70 [ieee1394]
[<f8989dbf>] handle_iso_listen+0xcf/0x1a0 [raw1394]
[<f898ca56>] state_connected+0x116/0x2b0 [raw1394]
[<f898cc7d>] raw1394_write+0x8d/0xe0 [raw1394]
[<c015a678>] vfs_write+0xb8/0x130
[<c015a7a2>] sys_write+0x42/0x70
[<c0105dd9>] sysenter_past_esp+0x52/0x71
Debug: sleeping function called from invalid context at
include/asm/semaphore.h:119
in_atomic():1, irqs_disabled():1
Call Trace:
[<c011bf87>] __might_sleep+0xb7/0xe0
[<c0269cf4>] dma_pool_destroy+0x24/0x140
[<f890dbcb>] free_dma_rcv_ctx+0xcb/0x120 [ohci1394]
[<f890b39e>] ohci_devctl+0x57e/0x640 [ohci1394]
[<c01336e7>] unqueue_me+0x67/0xd0
[<f89e83fc>] hpsb_unlisten_channel+0x3c/0x60 [ieee1394]
[<f8989e53>] handle_iso_listen+0x163/0x1a0 [raw1394]
[<f898ca56>] state_connected+0x116/0x2b0 [raw1394]
[<f898cc7d>] raw1394_write+0x8d/0xe0 [raw1394]
[<c015a678>] vfs_write+0xb8/0x130
[<c015a7a2>] sys_write+0x42/0x70
[<c0105dd9>] sysenter_past_esp+0x52/0x71
Debug: sleeping function called from invalid context at
include/asm/semaphore.h:119
in_atomic():1, irqs_disabled():1
Call Trace:
[<c011bf87>] __might_sleep+0xb7/0xe0
[<c0269cf4>] dma_pool_destroy+0x24/0x140
[<f890dbcb>] free_dma_rcv_ctx+0xcb/0x120 [ohci1394]
[<f890b39e>] ohci_devctl+0x57e/0x640 [ohci1394]
[<c01336e7>] unqueue_me+0x67/0xd0
[<f89e83fc>] hpsb_unlisten_channel+0x3c/0x60 [ieee1394]
[<f8989e53>] handle_iso_listen+0x163/0x1a0 [raw1394]
[<f898ca56>] state_connected+0x116/0x2b0 [raw1394]
[<f898cc7d>] raw1394_write+0x8d/0xe0 [raw1394]
[<c015a678>] vfs_write+0xb8/0x130
[<c015a7a2>] sys_write+0x42/0x70
[<c0105dd9>] sysenter_past_esp+0x52/0x71
--------------------------------------------------------
The recent usb_uhci patch had been applied (to make Clie/visor sync work)
Apart from these debug/trace messages (which have not - so far - been
repeated), the system appears to be working fine...
.............................
Robert Gadsdon
.............................
reply other threads:[~2004-04-23 9:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4088DDC0.8080701@rgadsdon2.giointernet.co.uk \
--to=robert@rgadsdon2.giointernet.co.uk \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®