From: Pavel Roskin <proski@gnu.org>
To: Maxim Levitsky <maximlevitsky@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
iwlwifi maling list <ipw3945-devel@lists.sourceforge.net>
Subject: Re: [BUG] Current head of wireless testing unusable
Date: Sat, 25 Jul 2009 17:52:35 -0400 [thread overview]
Message-ID: <1248558755.11389.21.camel@mj> (raw)
In-Reply-To: <1248531054.15242.16.camel@maxim-laptop>
On Sat, 2009-07-25 at 17:10 +0300, Maxim Levitsky wrote:
> I probably should work more to did these bugs out myself, but anyway I
> want to let you know what I currently see.
>
> First system oopses just after NM starts up, happens always, and after
> planting few test points bug happens somewhere in following lines.
We are discussing a bug in the scan state machine in another thread,
which could have nasty consequences in not caught. And I don't quite
understand why my system was catching it immediately, maybe because I'm
using gcc 4.4, which has array bounds checking.
I have also seen two oopses in the code unrelated to wireless
networking, one of which lead to my .bash_history becoming empty.
So please be extra careful. It would be great if somebody could test
the current kernel extensively with kmemcheck an other options and
bisect the bad commit, whether it's wireless related or not.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2009-07-25 21:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-25 14:10 [BUG] Current head of wireless testing unusable Maxim Levitsky
2009-07-25 21:52 ` Pavel Roskin [this message]
2009-07-25 22:31 ` Maxim Levitsky
2009-07-25 22:53 ` Maxim Levitsky
2009-07-26 5:25 ` Marcel Holtmann
2009-07-26 6:34 ` [ipw3945-devel] " John Ranson
2009-07-26 10:14 ` Maxim Levitsky
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=1248558755.11389.21.camel@mj \
--to=proski@gnu.org \
--cc=ipw3945-devel@lists.sourceforge.net \
--cc=linux-wireless@vger.kernel.org \
--cc=maximlevitsky@gmail.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;
as well as URLs for NNTP newsgroup(s).