From: Stephen Hemminger <shemminger@vyatta.com>
To: Ben Greear <greearb@candelatech.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.34.1+hacks: kernel deadlock related to file-IO?
Date: Tue, 27 Jul 2010 23:14:27 -0700 [thread overview]
Message-ID: <20100727231427.1f3eb97b@nehalam> (raw)
In-Reply-To: <4C4F767D.4020002@candelatech.com>
On Tue, 27 Jul 2010 17:14:53 -0700
Ben Greear <greearb@candelatech.com> wrote:
> On 07/27/2010 04:51 PM, Stephen Hemminger wrote:
> > On Tue, 27 Jul 2010 16:11:47 -0700
> > Ben Greear<greearb@candelatech.com> wrote:
> >
> >> NOTE: This is from a hacked 2.6.34.1 kernel, with
> >> a module of my own devising loaded and in active use.
> >
> > Ben please don't ask LKML for help with problems when
> > you have a binary only module loaded...
>
> Yeah, I know..but I spent all day hacking .34 enough to
> run lockdep and get those backtraces..and they *might* be
> valid. There's a small chance someone else has seen similar
> things but not reported it for whatever reason, so maybe
> they will chime in.
>
> And finally, I will attempt to reproduce with some official
> kernels, and will report what I find one way or another.
>
> The .34 kernel has been a real bitch to get stable (You
> know things must be bad when my name's on -stable patches),
> so I wouldn't be surprised if I'm hitting another real bug.
Understand your pain. The hardest problem is often finding a reproducible case.
If the problem is not reproducible it is hard to add trace info
or use bisection.
next prev parent reply other threads:[~2010-07-28 6:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-27 23:11 2.6.34.1+hacks: kernel deadlock related to file-IO? Ben Greear
2010-07-27 23:51 ` Stephen Hemminger
2010-07-28 0:14 ` Ben Greear
2010-07-28 6:14 ` Stephen Hemminger [this message]
2010-07-28 18:14 ` Ben Greear
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=20100727231427.1f3eb97b@nehalam \
--to=shemminger@vyatta.com \
--cc=greearb@candelatech.com \
--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 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.