From: krispa <krishnapavan@gmail.com>
To: linux-mips@linux-mips.org
Subject: kernel dump in dev_change_flags
Date: Thu, 13 Nov 2008 03:26:55 -0800 (PST) [thread overview]
Message-ID: <20478996.post@talk.nabble.com> (raw)
Hello all
I am porting a virtual interface driver from 2.4 to 2.6 .
i was able to create a virtual interface successfully
using ioctl command i was able to create the interface. and was able to set
various parameters of
the interface , but when i try to bring up the interface i get the following
dump.
i tried locking using rtnl_lock and spin_lock_irqsave ...during that time
the system got hung ...
as of now i am using spin_lock for the critical region and get the following
dump.
can any one please suggest me how do i go about to resolve the issue.
Jan 1 00:02:57 localhost kernel: BUG: soft lockup detected on CPU#1!
Jan 1 00:02:57 localhost kernel: Call Trace:
Jan 1 00:02:57 localhost kernel: [<ffffffff81123570>] dump_stack+0x8/0x48
Jan 1 00:02:57 localhost kernel: [<ffffffff81187864>]
softlockup_tick+0x1c4/0x238
Jan 1 00:02:57 localhost kernel: [<ffffffff8115d6ac>]
update_process_times+0x44/0x98
Jan 1 00:02:57 localhost kernel: [<ffffffff81101644>]
octeon_main_timer_interrupt+0x194/0x1a0
Jan 1 00:02:57 localhost kernel: [<ffffffff81187fa0>]
handle_IRQ_event+0xf0/0x490
Jan 1 00:02:57 localhost kernel: [<ffffffff8118a430>]
handle_percpu_irq+0x98/0x118
Jan 1 00:02:57 localhost kernel: [<ffffffff81105550>]
plat_irq_dispatch+0x100/0x270
Jan 1 00:02:57 localhost kernel: [<ffffffff8111c3c0>] ret_from_irq+0x0/0x4
Jan 1 00:02:57 localhost kernel: [<ffffffff8143febc>] _spin_lock+0x6c/0xc0
Jan 1 00:02:57 localhost kernel: [<c0000000000b0cbc>] vif_open+0x84/0x3e8
[cavium_vidd]
Jan 1 00:02:57 localhost kernel: [<ffffffff81385b50>] dev_open+0x68/0xd8
Jan 1 00:02:57 localhost kernel: [<ffffffff813817cc>]
dev_change_flags+0x144/0x188
Jan 1 00:02:57 localhost kernel: [<c0000000000af774>]
vif_devinet_ioctl+0x2fc/0x8b8 [cavium_vidd]
Jan 1 00:02:57 localhost kernel: [<c0000000000aeb94>]
VIDD_ioctl+0x824/0xf70 [cavium_vidd]
Jan 1 00:02:57 localhost kernel: [<ffffffff813848e0>] dev_ioctl+0x320/0x560
Jan 1 00:02:57 localhost kernel: [<ffffffff8137221c>]
sock_ioctl+0x1bc/0x3f8
Jan 1 00:02:57 localhost kernel: [<ffffffff811cfbe0>] do_ioctl+0x40/0xd0
Jan 1 00:02:57 localhost kernel: [<ffffffff811cfcf0>] vfs_ioctl+0x80/0x3e8
Jan 1 00:02:57 localhost kernel: [<ffffffff811d012c>] sys_ioctl+0xd4/0x1b8
Jan 1 00:02:57 localhost kernel: [<ffffffff811277b4>]
syscall_trace_entry+0x78/0x98
Jan 1 00:02:57 localhost kernel:
-Thanks in advance
Krishna
--
View this message in context: http://www.nabble.com/kernel-dump-in-dev_change_flags-tp20478996p20478996.html
Sent from the linux-mips main mailing list archive at Nabble.com.
reply other threads:[~2008-11-13 11:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20478996.post@talk.nabble.com \
--to=krishnapavan@gmail.com \
--cc=linux-mips@linux-mips.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.