From: Sergey Lapin <slapinid@gmail.com>
To: linux-omap@vger.kernel.org, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org,
David Brownell <dbrownell@users.sourceforge.net>,
Felipe Balbi <felipe.balbi@nokia.com>
Subject: MUSB crash on OMAP3 board with second load of gadget
Date: Thu, 21 Jan 2010 14:26:49 +0300 [thread overview]
Message-ID: <48239d391001210326y25986d59hd10d390ef9c8ddea@mail.gmail.com> (raw)
Hi! I have crashes in MUSB code when working with USB gadget drivers.
Kernel version: linux-omap master d8ebff302ff819587377b123e900e501e4135d86
To reproduce: (USB device cable should be attached).
dd if=/dev/zero of=/tmp/disk bs=1k count=1024
mkdosfs -F 32 /tmp/disk
insmod g_mass_storage file=/tmp/disk stall=0
Wait till disk is mounted on host, then
rmmod g_mass_storage
insmod g_mass_storage file=/tmp/disk stall=0
And here we get Oops in include/linux/list.h line 93,
list_del function, which leads us to drivers/usb/musb/musb_gadget.c,
function void musb_g_giveback(
struct musb_ep *ep,
struct usb_request *request,
int status),
just at the beginning of function.
if we add
pr_debug("list.prev = %p\n", request->list.prev);
pr_debug("list.next = %p\n", request->list.next);
and we see
list.prev = 6b6b6b6b
list.next = 6b6b6b6b
And these are NOT values set during list deletion.
Any ideas where to debug from here? If I just do return from that
function in case
of list.prev = 6b6b6b6b, then there's no crash, but there's no working
USB either.
if I just ignore list_del, I have crash later, where it seems to
execute bad code
from address 0x6b6b6b6a. Please, help!
Thanks a lot,
S.
next reply other threads:[~2010-01-21 11:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-21 11:26 Sergey Lapin [this message]
2010-01-21 12:28 ` Felipe Balbi
2010-01-21 13:23 ` Sergey Lapin
2010-01-21 16:16 ` Sergey Lapin
2010-01-21 16:24 ` Felipe Balbi
2010-01-21 17:32 ` Sergey Lapin
2010-01-22 10:38 ` Sergey Lapin
2010-01-22 14:07 ` Sergey Lapin
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=48239d391001210326y25986d59hd10d390ef9c8ddea@mail.gmail.com \
--to=slapinid@gmail.com \
--cc=dbrownell@users.sourceforge.net \
--cc=felipe.balbi@nokia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-usb@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®