From: Ingo Molnar <mingo@elte.hu>
To: Sitsofe Wheeler <sitsofe@yahoo.com>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
Frederic Weisbecker <fweisbec@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: What made this bug report better? (was Re: Poking ieee80211_default_rc_algo causes kernel lockups)
Date: Fri, 20 Feb 2009 12:31:07 +0100 [thread overview]
Message-ID: <20090220113107.GK28581@elte.hu> (raw)
In-Reply-To: <20090220102705.GA2884@silver.sucs.org>
* Sitsofe Wheeler <sitsofe@yahoo.com> wrote:
> On Tue, Feb 17, 2009 at 10:07:27AM +1030, Rusty Russell wrote:
> >
> > Thanks, done, and I'll send to Linus and -stable immediately.
>
> I'm curious - only two days after I reposted this the problem
> [1] it appears to have been resolved. When I posted it the
> first time [2] I only received one reply (privately) and that
> was from Greg wondering why I had only sent the email to him
> (which was an unfortunate problem and down to how I was trying
> to send LKML mails at the time).
>
> What happened this time that made things succesful? Was the
> original mail too big? Did it not make it to the list?
>
> [1] http://groups.google.com/group/fa.linux.kernel/browse_frm/thread/2a816ca521d72494/bd607c7e143def6f?#bd607c7e143def6f
> [2] http://groups.google.com/group/fa.linux.kernel/browse_frm/thread/d4a6ce26360613fa/b362792a2debced6?#b362792a2debced6
It does not seem to have made it to everyone - it's not in my
lkml folder for example. Sometimes vger eats emails. Filing a
bugzilla for reproducible bugs makes sense - especially if you
see that no action has been taken by anyone.
But note that even with expanded Cc:s and a properly working
list it needed Frederic's excellent function-graph trace and
analysis.
A crash in the wireless code rarely gets tracked back to a core
kernel module support bug, and it would have taken quite some
time for someone to make that connection.
Ingo
next prev parent reply other threads:[~2009-02-20 11:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-15 16:09 Poking ieee80211_default_rc_algo causes kernel lockups Sitsofe Wheeler
2009-02-15 17:02 ` Frederic Weisbecker
2009-02-15 19:24 ` Sitsofe Wheeler
2009-02-15 19:41 ` Frederic Weisbecker
2009-02-15 21:02 ` Sitsofe Wheeler
2009-02-16 1:40 ` Frederic Weisbecker
2009-02-16 2:37 ` Frederic Weisbecker
2009-02-15 19:35 ` Frederic Weisbecker
2009-02-16 10:10 ` Rusty Russell
2009-02-16 17:59 ` Frederic Weisbecker
2009-02-16 23:37 ` Rusty Russell
2009-02-20 10:27 ` What made this bug report better? (was Re: Poking ieee80211_default_rc_algo causes kernel lockups) Sitsofe Wheeler
2009-02-20 11:31 ` Ingo Molnar [this message]
2009-02-24 3:13 ` Rusty Russell
2009-02-24 8:16 ` What made this bug report better? Sitsofe Wheeler
2009-02-24 17:58 ` Frederic Weisbecker
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=20090220113107.GK28581@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=sitsofe@yahoo.com \
/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®