From: fonseka@gmail.com
To: linux-kernel@vger.kernel.org
Subject: BUG: scheduling while atomic
Date: Fri, 2 Jun 2006 10:39:01 +0100 [thread overview]
Message-ID: <79a6fb1e0606020239i49c38effxc688c12f94d5da41@mail.gmail.com> (raw)
hi there!
recently I'm trying putting snmpd working on a old machine and ran into
problems... everytime i try to spawn the snmpd process I got a kernel
backtrace as follows, and the process never cames up:
Jun 2 10:02:55 apophis scheduling while atomic: snmpd/0x00000001/26757
Jun 2 10:02:55 apophis [<c035ea98>] schedule+0x5a8/0x6a0
Jun 2 10:02:55 apophis [<c035f4b1>] schedule_timeout+0x51/0xa0
Jun 2 10:02:55 apophis [<c0124a50>] process_timeout+0x0/0x10
Jun 2 10:02:55 apophis [<c0124cb8>] msleep+0x28/0x40
Jun 2 10:02:55 apophis [<c02867fc>] rhine_disable_linkmon+0x7c/0x140
Jun 2 10:02:55 apophis [<c0286705>] rhine_enable_linkmon+0x45/0xc0
Jun 2 10:02:55 apophis [<c02868ef>] mdio_read+0x2f/0xf0
Jun 2 10:02:55 apophis [<c021c042>] copy_to_user+0x42/0x60
Jun 2 10:02:55 apophis [<c028904d>] generic_mii_ioctl+0x11d/0x1c0
Jun 2 10:02:55 apophis [<c02880e0>] netdev_ioctl+0x0/0x70
Jun 2 10:02:55 apophis [<c0288127>] netdev_ioctl+0x47/0x70
Jun 2 10:02:55 apophis [<c02de19c>] dev_ifsioc+0x13c/0x440
Jun 2 10:02:55 apophis [<c02de6e4>] dev_ioctl+0x244/0x2b0
Jun 2 10:02:55 apophis [<c02d2ab4>] sock_ioctl+0x114/0x250
Jun 2 10:02:55 apophis [<c01743de>] do_ioctl+0x9e/0xb0
Jun 2 10:02:55 apophis [<c0174595>] vfs_ioctl+0x65/0x200
Jun 2 10:02:55 apophis [<c0174775>] sys_ioctl+0x45/0x70
Jun 2 10:02:55 apophis [<c01030cb>] sysenter_past_esp+0x54/0x75
I've tried with 2.6.15 and 2.6.16 with no sucess
using gcc 3.4.5
binutils 2.16.1
glibc 2.3.6
if you need any more info please just ask me
TIA
--
Will work for bandwidth
next reply other threads:[~2006-06-02 9:39 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-02 9:39 fonseka [this message]
2006-06-02 12:37 ` Roger Luethi
2006-06-02 14:07 ` fonseka
2006-12-08 15:47 Christian
2009-06-19 18:15 Sergey Senozhatsky
2009-06-20 17:43 ` Rabin Vincent
2009-06-20 18:54 ` Sergey Senozhatsky
2009-06-22 9:04 ` Alan Cox
2009-06-22 9:57 ` Alan Cox
2009-06-22 11:33 ` Sergey Senozhatsky
2009-06-22 12:36 ` Alan Cox
2009-06-22 13:59 ` Sergey Senozhatsky
2009-07-06 7:55 ` Herbert Xu
2009-06-27 11:10 Michael Guntsche
2009-06-27 13:06 ` Alan Cox
2009-06-27 16:07 ` Michael Guntsche
2009-07-06 7:43 ` Herbert Xu
2009-07-06 8:31 ` Herbert Xu
2009-07-06 15:28 ` Michael Guntsche
2009-07-06 15:32 ` Alan Cox
2009-07-06 17:17 ` Alan Cox
2009-07-06 18:07 ` Michael Guntsche
2009-07-06 18:18 ` Alan Cox
2009-07-06 18:37 ` Michael Guntsche
2009-07-06 10:00 ` Alan Cox
2010-08-27 7:59 Sergey Senozhatsky
2010-08-27 19:02 ` Rafael J. Wysocki
2010-08-28 6:42 ` Pavel Machek
2010-08-30 7:29 ` Sergey Senozhatsky
2010-08-30 10:04 ` Sergey Senozhatsky
2012-02-13 8:08 Florian Tobias Schandinat
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=79a6fb1e0606020239i49c38effxc688c12f94d5da41@mail.gmail.com \
--to=fonseka@gmail.com \
--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®