From: Helge Hafting <helgehaf@aitel.hist.no>
To: Andrew Morton <akpm@digeo.com>
Cc: linux-kernel@vger.kernel.org, davem@redhat.com,
kuznet@ms2.inr.ac.ru, pekkas@netcore.fi, netdev@oss.sgi.com
Subject: Re: 2.5.46-mm1 3 uninitialized timers during boot, ipv6 related?
Date: Wed, 06 Nov 2002 14:29:18 +0100 [thread overview]
Message-ID: <3DC9192E.62600E21@aitel.hist.no> (raw)
In-Reply-To: 3DC8D423.DAD2BF1A@digeo.com
I see these aren't dangerous, but I guess they're there for
someone to see. So here they are.
Seems they have something to do with ipv6.
VFS: Mounted root (ext2 filesystem) readonly.
Mounted devfs on /dev
Freeing unused kernel memory: 308k freed
Adding 502700k swap on /dev/ide/host0/bus0/target0/lun0/part5.
Priority:-1 extents:1
NTFS volume version 1.2.
Uninitialised timer!
This is just a warning. Your computer is OK
function=0xc02b53dc, data=0xc1293aec
Call Trace:
[<c011ebc0>] check_timer_failed+0x40/0x4c
[<c02b53dc>] igmp6_timer_handler+0x0/0x50
[<c011eff1>] del_timer+0x15/0x74
[<c02b529e>] igmp6_join_group+0x8a/0x104
[<c02b455c>] igmp6_group_added+0xb0/0xbc
[<c02bcb99>] fl_create+0x1b9/0x1f8
[<c02b48a9>] ipv6_dev_mc_inc+0x281/0x294
[<c02a5a1e>] addrconf_join_solict+0x3a/0x44
[<c02a6e73>] addrconf_dad_start+0x13/0x12c
[<c02a6844>] addrconf_add_linklocal+0x28/0x40
[<c02a68f5>] addrconf_dev_config+0x99/0xa4
[<c02a69de>] addrconf_notify+0x52/0xc0
[<c0121d5a>] notifier_call_chain+0x1e/0x38
[<c024f976>] dev_open+0xa2/0xac
[<c0250a55>] dev_change_flags+0x51/0x104
[<c0281420>] devinet_ioctl+0x2bc/0x598
[<c0283827>] inet_ioctl+0x7b/0xb8
[<c02c3a9b>] packet_ioctl+0x173/0x190
[<c0249943>] sock_ioctl+0x1ef/0x218
[<c014bbf9>] sys_ioctl+0x21d/0x274
[<c0108943>] syscall_call+0x7/0xb
Uninitialised timer!
This is just a warning. Your computer is OK
function=0xc02b53dc, data=0xc1293a1c
Call Trace:
[<c011ebc0>] check_timer_failed+0x40/0x4c
[<c02b53dc>] igmp6_timer_handler+0x0/0x50
[<c011eff1>] del_timer+0x15/0x74
[<c02b529e>] igmp6_join_group+0x8a/0x104
[<c02b455c>] igmp6_group_added+0xb0/0xbc
[<c02bcb99>] fl_create+0x1b9/0x1f8
[<c02b48a9>] ipv6_dev_mc_inc+0x281/0x294
[<c02a5a1e>] addrconf_join_solict+0x3a/0x44
[<c02a6e73>] addrconf_dad_start+0x13/0x12c
[<c02a6844>] addrconf_add_linklocal+0x28/0x40
[<c02a68f5>] addrconf_dev_config+0x99/0xa4
[<c02a69de>] addrconf_notify+0x52/0xc0
[<c0121d5a>] notifier_call_chain+0x1e/0x38
[<c024f976>] dev_open+0xa2/0xac
[<c0250a55>] dev_change_flags+0x51/0x104
[<c0281420>] devinet_ioctl+0x2bc/0x598
[<c0283827>] inet_ioctl+0x7b/0xb8
[<c0249943>] sock_ioctl+0x1ef/0x218
[<c014bbf9>] sys_ioctl+0x21d/0x274
[<c0108943>] syscall_call+0x7/0xb
Uninitialised timer!
This is just a warning. Your computer is OK
function=0xc02b53dc, data=0xc1293b54
Call Trace:
[<c011ebc0>] check_timer_failed+0x40/0x4c
[<c02b53dc>] igmp6_timer_handler+0x0/0x50
[<c011eff1>] del_timer+0x15/0x74
[<c02b529e>] igmp6_join_group+0x8a/0x104
[<c02b455c>] igmp6_group_added+0xb0/0xbc
[<c02bcb99>] fl_create+0x1b9/0x1f8
[<c02b48a9>] ipv6_dev_mc_inc+0x281/0x294
[<c02a5a1e>] addrconf_join_solict+0x3a/0x44
[<c02a6e73>] addrconf_dad_start+0x13/0x12c
[<c02a6844>] addrconf_add_linklocal+0x28/0x40
[<c02a68f5>] addrconf_dev_config+0x99/0xa4
[<c02a69de>] addrconf_notify+0x52/0xc0
[<c0121d5a>] notifier_call_chain+0x1e/0x38
[<c024f976>] dev_open+0xa2/0xac
[<c0250a55>] dev_change_flags+0x51/0x104
[<c0281420>] devinet_ioctl+0x2bc/0x598
[<c0283827>] inet_ioctl+0x7b/0xb8
[<c0249943>] sock_ioctl+0x1ef/0x218
[<c014bbf9>] sys_ioctl+0x21d/0x274
[<c0108943>] syscall_call+0x7/0xb
eth0: no IPv6 routers present
next parent reply other threads:[~2002-11-06 13:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3DC8D423.DAD2BF1A@digeo.com>
2002-11-06 13:29 ` Helge Hafting [this message]
2002-11-06 16:57 ` 2.5.46-mm1 3 uninitialized timers during boot, ipv6 related? Andrew Morton
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=3DC9192E.62600E21@aitel.hist.no \
--to=helgehaf@aitel.hist.no \
--cc=akpm@digeo.com \
--cc=davem@redhat.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=pekkas@netcore.fi \
/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).