From: Brice Goglin <Brice.Goglin@ens-lyon.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Andrew Morton <akpm@osdl.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.15-mm4
Date: Sat, 14 Jan 2006 23:24:02 -0500 [thread overview]
Message-ID: <43C9CE62.9070302@ens-lyon.org> (raw)
In-Reply-To: <20060115040741.GA23968@elte.hu>
Ingo Molnar wrote:
>* Brice Goglin <Brice.Goglin@ens-lyon.org> wrote:
>
>
>
>>Hi Andrew,
>>
>>I get the following badness when booting mm4 on my thinkpad T43:
>>
>>hdaps: IBM ThinkPad T43 detected.
>>hdaps: initial latch check good (0x01).
>>Time: acpi_pm clocksource has been installed.
>>input: hdaps as /class/input/input3
>>hdaps: driver successfully loaded.
>>Non-volatile memory driver v1.2
>>Badness in __mutex_trylock_slowpath at kernel/mutex.c:281
>> [<c01251cf>] mutex_trylock+0x5a/0xe7
>> [<e09c02d2>] hdaps_inputdev_poll+0xd/0xbd [hdaps]
>> [<c011befc>] run_timer_softirq+0x105/0x147
>> [<c0118a0b>] __do_softirq+0x34/0x7d
>> [<c0118a76>] do_softirq+0x22/0x26
>> [<c0104a64>] do_IRQ+0x22/0x2a
>> [<c01033ce>] common_interrupt+0x1a/0x20
>>kjournald starting. Commit interval 5 seconds
>>
>>
>
>Could you try the patch below?
>
>
>
Yes, it does fix it. What's the bug ? The mutexes are supposed to work
where semaphores do, aren't they ?
Brice
next prev parent reply other threads:[~2006-01-15 4:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-14 15:34 2.6.15-mm4 Brice Goglin
2006-01-15 4:07 ` 2.6.15-mm4 Ingo Molnar
2006-01-15 4:24 ` Brice Goglin [this message]
2006-01-15 4:42 ` 2.6.15-mm4 Ingo Molnar
-- strict thread matches above, loose matches on Subject: below --
2006-01-14 13:51 2.6.15-mm4 Andrew Morton
2006-01-14 22:49 ` 2.6.15-mm4 Reuben Farrelly
2006-01-16 4:08 ` 2.6.15-mm4 Tejun Heo
2006-01-14 23:10 ` 2.6.15-mm4 Reuben Farrelly
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=43C9CE62.9070302@ens-lyon.org \
--to=brice.goglin@ens-lyon.org \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.