From: Terje Kvernes <terjekv@math.uio.no>
To: Torrey Hoffman <thoffman@arnor.net>
Cc: Andrew Morton <akpm@osdl.org>,
Linux-Kernel List <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org
Subject: Re: 2.6.3-rc2-mm1
Date: Sat, 14 Feb 2004 11:36:09 +0100 [thread overview]
Message-ID: <wxxisiaeyna.fsf@nommo.uio.no> (raw)
In-Reply-To: <1076630675.6006.6.camel@moria.arnor.net> (Torrey Hoffman's message of "Thu, 12 Feb 2004 16:04:35 -0800")
Torrey Hoffman <thoffman@arnor.net> writes:
> On Thu, 2004-02-12 at 01:57, Andrew Morton wrote:
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.3-rc2/2.6.3-rc2-mm1/
>
> [... list of many patches]
>
> > bk-ieee1394.patch
>
> I reported a bug in 2.6.2-rc3-mm1 and was asked to retest... result
> is it's still broken. The result is the same - even a little worse
> now, it won't get as far as running init so I have no log to post.
I'm seeing the same bug, and I have ieee1394 as a module. I can
help to debug this if need be.
> This machine has no serial port and I haven't tried the network
> logging stuff yet...
>
> But the oops looked very similar. At least the function names and the
> references to ieee1394 are the same. The 2.6.2-rc3-mm1 oops was:
>
> > ieee1394: Host added: ID:BUS[0-00:1023] GUID[00508d0000f42af5]
> > Badness in kobject_get at lib/kobject.c:431
> > Call Trace:
> > [<c02078dc>] kobject_get+0x3c/0x50
> > [<c0272fd1>] get_device+0x11/0x20
> > [<c0273c68>] bus_for_each_dev+0x78/0xd0
> > [<fc876185>] nodemgr_node_probe+0x45/0x100 [ieee1394]
> > [<fc876030>] nodemgr_probe_ne_cb+0x0/0x90 [ieee1394]
> > [<fc87654b>] nodemgr_host_thread+0x14b/0x180 [ieee1394]
> > [<fc876400>] nodemgr_host_thread+0x0/0x180 [ieee1394]
> > [<c010b285>] kernel_thread_helper+0x5/0x10
yup. this is _very_ familiar. I have the same problem with
2.6.3-rc2-mm1. I also have some devfs problems that I can't quite
pinpoint so I've rolled back to 2.6.2-mm1.
[ ... ]
--
Terje
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2004-02-14 10:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-12 9:57 2.6.3-rc2-mm1 Andrew Morton
2004-02-12 11:13 ` 2.6.3-rc2-mm1 Andrew Morton
2004-02-12 11:57 ` 2.6.3-rc2-mm1 Anton Blanchard
2004-02-12 12:09 ` 2.6.3-rc2-mm1 Andrew Morton
2004-02-12 14:40 ` 2.6.3-rc2-mm1 Zwane Mwaikambo
2004-02-12 14:46 ` 2.6.3-rc2-mm1 Anton Blanchard
2004-02-12 14:47 ` 2.6.3-rc2-mm1 Anton Blanchard
2004-02-12 11:24 ` 2.6.3-rc2-mm1 Nick Piggin
2004-02-12 14:46 ` 2.6.3-rc2-mm1 Zwane Mwaikambo
2004-02-12 15:40 ` 2.6.3-rc2-mm1 Mark Haverkamp
2004-02-12 21:38 ` 2.6.3-rc2-mm1 Andrew Morton
2004-02-12 22:33 ` 2.6.3-rc2-mm1 Nick Piggin
2004-02-12 17:06 ` 2.6.3-rc2-mm1 (compile stats) John Cherry
2004-02-12 18:43 ` 2.6.3-rc2-mm1 Alistair John Strachan
2004-02-13 0:04 ` 2.6.3-rc2-mm1 Torrey Hoffman
2004-02-14 10:36 ` Terje Kvernes [this message]
2004-02-13 21:04 ` [PATCH 2.6.3-rc2-mm1] Daniel McNeil
2004-02-14 5:27 ` 2.6.3-rc2-mm1 Glenn Johnson
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=wxxisiaeyna.fsf@nommo.uio.no \
--to=terjekv@math.uio.no \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=thoffman@arnor.net \
/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