From: Andrey Borzenkov <arvidjaar@mail.ru>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Arjan van de Ven <arjan@infradead.org>,
linux-usb-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [linux-usb-devel] 2.6.18.2: lockdep warnings on rmmod ohci_hcd
Date: Mon, 6 Nov 2006 19:34:58 +0300 [thread overview]
Message-ID: <200611061934.59569.arvidjaar@mail.ru> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0611061113140.6579-100000@iolanthe.rowland.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Monday 06 November 2006 19:16, Alan Stern wrote:
> On Mon, 6 Nov 2006, Andrey Borzenkov wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > On Monday 06 November 2006 17:18, Arjan van de Ven wrote:
> > > On Mon, 2006-11-06 at 15:46 +0300, Andrey Borzenkov wrote:
> > > > I presume this is lockdep; this looks initially truncated,
> > > > unfortunately this
> > > > is how it was stored in messages. I will try to get more complete
> > > > output ig
> > > > required.
> > >
> > > the interesting bits are missing unfortunately (the first 10 lines or
> > > so).
> > >
> > > Also this will be in "dmesg" if your system actually survives...
> >
> > well, dmesg had exactly the same contents. Here full dmesg with increased
> > LOG_SHIFT.
>
> I always find it rather difficult to understand the meaning of lockdep
> warnings, but this looks a bug that was fixed in 2.6.19-rc1. The patch
> that fixed it is here:
>
> http://marc.theaimsgroup.com/?l=linux-usb-devel&m=115938807428103&w=2
>
Yes, it has fixed it. Thank you
- -andrey
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
iD8DBQFFT2QzR6LMutpd94wRAh4OAKCZHqj/W3aFgEiXp3puPLhur5Rb9ACff67R
oIpIdzM5pMypaqCajAbWLW4=
=yHf7
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2006-11-06 16:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-06 12:46 Andrey Borzenkov
2006-11-06 14:18 ` Arjan van de Ven
2006-11-06 15:33 ` Andrey Borzenkov
2006-11-06 16:16 ` [linux-usb-devel] " Alan Stern
2006-11-06 16:34 ` Andrey Borzenkov [this message]
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=200611061934.59569.arvidjaar@mail.ru \
--to=arvidjaar@mail.ru \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=stern@rowland.harvard.edu \
/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®