From: Adrian Bunk <bunk@stusta.de>
To: Andrew Paprocki <andrew@ishiboo.com>
Cc: linux-kernel@vger.kernel.org, stefanr@s5r6.in-berlin.de,
linux1394-devel@lists.sourceforge.net
Subject: Re: 2.6 git kernel reporting bug in knodemgrd_0 during boot
Date: Sun, 29 Oct 2006 23:38:22 +0100 [thread overview]
Message-ID: <20061029223822.GH27968@stusta.de> (raw)
In-Reply-To: <76366b180610291341y7342a968ycd244753ce9bbbb7@mail.gmail.com>
On Sun, Oct 29, 2006 at 04:41:54PM -0500, Andrew Paprocki wrote:
> I just upgraded my dev box to the latest 2.6 source via git and this
> is now printing out in dmesg upon every boot. Hardware is a standard
> VIA EPIA-MII motherboard w/ nothing extra added. I can supply
> additional info if anyone requests it. -Andrew
The ieee1394 maintainers (Cc'ed) might be the best contact.
> Probing IDE interface ide0...
> hda: HITACHI_DK23DA-40, ATA DISK drive
> ieee1394: Host added: ID:BUS[0-00:1023] GUID[0040635000015f17]
> ------------[ cut here ]------------
> Kernel BUG at [verbose debug info unavailable]
The bug message with CONFIG_DEBUG_BUGVERBOSE=y set might be interesting.
> invalid opcode: 0000 [#1]
> Modules linked in:
> CPU: 0
> EIP: 0060:[<b014932e>] Not tainted VLI
> EFLAGS: 00010002 (2.6.19-rc3-g2da6dc28 #1)
> EIP is at cache_alloc_refill+0x18e/0x400
> eax: 00000000 ebx: 0000003c ecx: 00000000 edx: 00000000
> esi: bdfed770 edi: bdfed760 ebp: bdfea000 esp: bd2bbe00
> ds: 007b es: 007b ss: 0068
> Process knodemgrd_0 (pid: 174, ti=bd2ba000 task=bdfa8ab0 task.ti=bd2ba000)
> Stack: 000200d2 000000d2 bdfef0c0 bdfee1e0 0000003c 00000000 00000001
> b03a61ec
> 000000d2 b03a61ec bdfa8ab0 00000246 00001fff 000000d2 00000163
> b0149192
> be800000 b0143085 bd2bbe7c 00000002 ffffffff 00000001 000000d2
> ffffffff
> Call Trace:
> [<b0149192>] kmem_cache_alloc+0x22/0x30
> [<b0143085>] __get_vm_area_node+0x95/0x160
> [<b0143187>] get_vm_area_node+0x37/0x40
> [<b014370c>] __vmalloc_node+0x3c/0x60
> [<b014375f>] __vmalloc+0xf/0x20
> [<b0269ced>] csr1212_attach_keyval_to
> _directory+0x1d/0x60
> [<b026a52c>] csr1212_parse_keyval+0x14c/0x200
> [<b026a9be>] _csr1212_read_keyval+0x3de/0x420
> [<b0268185>] nodemgr_probe_ne+0x205/0x390
> [<b0179561>] sysfs_add_file+0x61/0x70
> [<b0268c3c>] nodemgr_host_thread+0x82c/0x980
> [<b0268410>] nodemgr_host_thread+0x0/0x980
> [<b0125a4f>] kthread+0xaf/0xe0
> [<b01259a0>] kthread+0x0/0xe0
> [<b0103d47>] kernel_thread_helper+0x7/0x10
> =======================
> Code: 04 89 37 83 7c 24 10 00 0f 8f 5a ff ff ff 8b 47 18 2b 45 00 89
> 47 18 83 7d 00 00 0f 85 61 02 00 00 f7 44 24 04 0e 80 f8 ff 74 02 <0f>
> 0b f7 44 24 04 00 20 00 00 0f 85 2d 02 00 00 8b 5c 24 04 81
> EIP: [<b014932e>] cache_alloc_refill+0x18e/0x400 SS:ESP 0068:bd2bbe00
> ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2006-10-29 22:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-29 21:41 Andrew Paprocki
2006-10-29 22:38 ` Adrian Bunk [this message]
2006-10-29 23:09 ` Stefan Richter
2006-10-29 23:26 ` Stefan Richter
2006-10-29 23:49 ` Andrew Paprocki
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=20061029223822.GH27968@stusta.de \
--to=bunk@stusta.de \
--cc=andrew@ishiboo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=stefanr@s5r6.in-berlin.de \
/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®