From: "Alexey Dobriyan" <adobriyan@gmail.com>
To: "Holger Kiehl" <Holger.Kiehl@dwd.de>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: sysfs: duplicate filename '74' can not be created
Date: Mon, 3 Mar 2008 18:50:01 +0300 [thread overview]
Message-ID: <b6fcc0a0803030750t1430171dib6497c980deee265@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0803031444570.17218@diagnostix.dwd.de>
On 3/3/08, Holger Kiehl <Holger.Kiehl@dwd.de> wrote:
> I get this approx. 4 hours after booting into 2.6.24.3 (2.6.23.16 worked
> fine). This system has 4 CPU's (single core) and 8GB ram. Here some more
> details:
>
>
> Mar 3 13:36:56 helena -- MARK --
> Mar 3 13:50:01 helena kernel: sysfs: duplicate filename '74' can not be
> created
> Mar 3 13:50:01 helena kernel: WARNING: at fs/sysfs/dir.c:424 sysfs_add_one()
> Mar 3 13:54:05 helena kernel: Code: 48 8b 04 c2 49 89 04 24 55 9d 31 c0
> c1 eb 0f 48 85 d2 0f 95
> Mar 3 13:54:05 helena kernel: RIP [<ffffffff80279170>]
> __kmalloc_track_caller+0x85/0xb9
> Mar 3 13:54:05 helena kernel: RSP <ffff8101dad09da8>
> Mar 3 13:54:05 helena kernel: ---[ end trace b8695bfb4832866d ]---
> Any idea what is causing this? Kernel 2.6.23.* seems to be fine.
Turn CONFIG_USER_SCHED off.
I'll look at why oops happened.
next prev parent reply other threads:[~2008-03-03 15:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-03 14:58 Holger Kiehl
2008-03-03 15:50 ` Alexey Dobriyan [this message]
2008-03-03 16:05 ` Holger Kiehl
2008-03-03 16:14 ` Holger Kiehl
2008-03-03 16:17 ` Alexey Dobriyan
2008-03-04 16:09 Alexey Dobriyan
2008-03-04 16:33 ` Dhaval Giani
2008-03-04 19:24 ` Greg KH
2008-03-05 8:59 ` Dhaval Giani
2008-03-06 6:00 ` Greg KH
2008-03-06 9:15 ` Alexey Dobriyan
2008-03-07 7:32 ` Holger Kiehl
2008-03-07 7:24 ` Holger Kiehl
2008-03-07 7:56 ` Holger Kiehl
2008-03-13 7:33 ` Holger Kiehl
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=b6fcc0a0803030750t1430171dib6497c980deee265@mail.gmail.com \
--to=adobriyan@gmail.com \
--cc=Holger.Kiehl@dwd.de \
--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
Powered by JetHome