public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nick Orlov <bugfixer@list.ru>
To: linux-kernel <linux-kernel@vger.kernel.org>
Cc: linux-netdev <linux-netdev@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>
Subject: netdevice name corruption is still present in 2.6.18-rc6-mm1
Date: Fri, 08 Sep 2006 23:29:39 -0400	[thread overview]
Message-ID: <20060909032939.GA3087@nickolas.homeunix.com> (raw)

Andrew,

I would like to confirm that issue with netdevice name corruption
is still present in 2.6.18-rc6-mm1 and extremely easy to reproduce
(at least on my system) with 100% hit rate.

All I have to do is 'sudo /etc/init.d/networking stop'. And here we go:

Sep  8 22:50:11 nickolas kernel: [events/1:7]: Changing netdevice name from [ath0] to [\200^C^Bб\206]

Does not look like an userspace issue at all...

Last kernel which is known to be working (for me) is 2.6.18-rc1-mm2.
Sorry, I now that a lot of things had changed since then,
but I was somewhat busy last couple of months...

Please let me know if I can help somehow to debug it.

Thank you,
	Nick Orlov.

P.S. I admit that I'm using "binary only atheros driver" which makes
this report a lot less legit. But seems like people experiencing the
very same issue w/o any closed-source drivers loaded...

P.P.S I don't even have NetworkManager executable on my system
(Debian unstable updated on daily basis), so NetworkManager have
nothing to do with it.

-- 
With best wishes,
	Nick Orlov.


             reply	other threads:[~2006-09-09  3:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-09  3:29 Nick Orlov [this message]
2006-09-09  5:26 ` netdevice name corruption is still present in 2.6.18-rc6-mm1 Andrew Morton
2006-09-09 14:19 ` Patrick McHardy
2006-09-10  2:07 ` Nick Orlov
2006-09-10  2:11   ` Nick Orlov
2006-09-10  9:40   ` Patrick McHardy
2006-09-14  3:36     ` David Miller

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=20060909032939.GA3087@nickolas.homeunix.com \
    --to=bugfixer@list.ru \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox