From: Helge Deller <deller@gmx.de>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: John David Anglin <dave@hiauly1.hia.nrc.ca>,
dave.anglin@nrc-cnrc.gc.ca, linux-parisc@vger.kernel.org,
carlos@systemhalted.org, randolph@tausq.org
Subject: Re: Out of order unwind entry warning
Date: Mon, 02 Nov 2009 23:43:24 +0100 [thread overview]
Message-ID: <4AEF608C.9000402@gmx.de> (raw)
In-Reply-To: <1257201072.9933.2.camel@mulgrave.site>
On 11/02/2009 11:31 PM, James Bottomley wrote:
> On Mon, 2009-11-02 at 23:20 +0100, Helge Deller wrote:
>> On 11/02/2009 10:50 PM, John David Anglin wrote:
>>> sysfs: cannot create duplicate filename '/module/usbhid/sections/.text'
>>> ------------[ cut here ]------------
>>> Badness at fs/sysfs/dir.c:487
>>
>> Yes, this is known.
>> See here:
>> http://patchwork.kernel.org/patch/42190/
>> Would be nice if this could get fixed.
>
> Actually, it is fixed; the patch is upstream as commit
> 1b364bf438cf337a3818aee77d68c0713f3e1fc4
>
> The patch was designed to fix the panic that occurred. This warn on is
> coming out of the sysfs code when we try to register a duplicate section
> name. The panic that followed is what the patch fixed ... but we still
> get left with the warn on.
Yes, the crash is fixed, but still the warning is ugly.
Each time you load any module, this warning is filling up the log.
If you boot via serial console (like me) printing this warning with 9600 baud takes endless time (and you easily get up to 30 times this warning).
Helge
next prev parent reply other threads:[~2009-11-02 22:43 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-26 22:21 Out of order unwind entry warning Helge Deller
2009-10-26 23:41 ` Kyle McMartin
2009-10-27 1:50 ` Randolph Chung
2009-10-27 2:24 ` Kyle McMartin
2009-10-27 23:19 ` John David Anglin
2009-10-28 21:42 ` Helge Deller
2009-10-28 22:00 ` Helge Deller
2009-10-28 23:10 ` John David Anglin
2009-10-29 20:51 ` Helge Deller
2009-10-29 13:20 ` Carlos O'Donell
2009-10-28 22:18 ` John David Anglin
2009-10-28 22:43 ` Helge Deller
2009-10-28 22:59 ` Helge Deller
2009-10-29 2:11 ` John David Anglin
2009-10-29 16:38 ` John David Anglin
2009-10-29 19:16 ` John David Anglin
2009-10-29 20:46 ` Helge Deller
2009-10-29 21:07 ` John David Anglin
2009-10-29 22:22 ` Helge Deller
2009-10-29 23:35 ` John David Anglin
2009-10-30 22:47 ` Helge Deller
2009-10-31 0:41 ` John David Anglin
2009-10-31 2:19 ` John David Anglin
2009-10-31 7:39 ` Helge Deller
2009-11-01 23:16 ` John David Anglin
2009-11-02 1:40 ` John David Anglin
2009-11-02 2:34 ` John David Anglin
2009-11-02 21:02 ` Helge Deller
2009-11-02 21:50 ` John David Anglin
2009-11-02 22:20 ` Helge Deller
2009-11-02 22:31 ` James Bottomley
2009-11-02 22:43 ` Helge Deller [this message]
2009-11-02 22:52 ` Helge Deller
2009-11-02 23:23 ` John David Anglin
2009-11-03 21:10 ` Helge Deller
2009-11-03 21:36 ` John David Anglin
2009-11-03 21:43 ` Helge Deller
2009-11-03 21:54 ` John David Anglin
2009-11-03 22:04 ` Helge Deller
2009-11-04 0:57 ` John David Anglin
2009-11-06 23:07 ` Helge Deller
2009-11-07 20:11 ` Kyle McMartin
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=4AEF608C.9000402@gmx.de \
--to=deller@gmx.de \
--cc=James.Bottomley@HansenPartnership.com \
--cc=carlos@systemhalted.org \
--cc=dave.anglin@nrc-cnrc.gc.ca \
--cc=dave@hiauly1.hia.nrc.ca \
--cc=linux-parisc@vger.kernel.org \
--cc=randolph@tausq.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