From: Jurriaan <thunder7@xs4all.nl>
To: linux-kernel@vger.kernel.org
Subject: 2.6.6-mm1: nameif causes oops
Date: Thu, 13 May 2004 19:28:49 +0200 [thread overview]
Message-ID: <20040513172849.GA2188@middle.of.nowhere> (raw)
In my untainted 2.6.6-mm1 kernel, I see an oops (the one with the turtle
graphics) when booting, caused by the usage of nameif (which renames
ethernet interfaces from 'eth0' to 'adsl' for example).
dmove+0xc0/02fd
show_stack
show_registers
die
do_page_rault
error_code
sysfs_rename
kobject_rename
class_device_rename
dev_change_name
dev_ioctl
inet_ioctl
sock_ioctl
sys_ioctl
syscall_call
This is a smp (hyperthreading, single cpu) Pentium/4 system running
Debian Unstable.
I hope this is enough information, if not, let me know please.
This didn't happen in 2.6.6-rc3-mm1, by the way, which is the latest
kernel I tested before this one.
Kind regards,
Jurriaan
--
"If you hoped to arouse my deep antipathy, you have succeeded," said
Carfilhiot. "Otherwise, the occasion has been time wasted."
Jack Vance - Lyonesse
Debian (Unstable) GNU/Linux 2.6.6-rc3-mm1 2x6062 bogomips 0.08 0.03
next reply other threads:[~2004-05-13 17:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-13 17:28 Jurriaan [this message]
2004-05-13 18:06 ` Valdis.Kletnieks
2004-05-13 18:12 ` Chris Wright
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=20040513172849.GA2188@middle.of.nowhere \
--to=thunder7@xs4all.nl \
--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 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®