From: Ted Kaczmarek <tedkaz@optonline.net>
To: xen-devel <xen-devel@lists.xensource.com>
Subject: xen_blk: can't get major 8 with name sd
Date: Thu, 13 Oct 2005 21:53:07 -0400 [thread overview]
Message-ID: <1129254787.12282.167.camel@pluto.linsolutions.com> (raw)
This happens randomly, more often than not the next xm create will
succeed. Don't think kernel config is related as I use almost identical
setup on my UP machine, but I use the work around for dev designations
on all the vm configs. With that setup I get 100% success on creation of
domU's with changeset: 7353:29db5bded574, this changeset would not boot
dom0 on the SMP machine.
Tyan 2462 SMP , FC4 dom0
changeset: 7369:92c6021f23e4
tag: tip
parent: 7368:7b9547485703
parent: 7367:10c93f58b041
user: emellor@leeni.uk.xensource.com
date: Thu Oct 13 10:26:44 2005 +0100
summary: Merge.
register_blkdev: cannot get major 8 for sd
xen_blk: can't get major 8 with name sd
Unable to handle kernel NULL pointer dereference at virtual address
00000104
printing eip:
c0254428
*pde = ma 00000000 pa 55555000
Oops: 0002 [#1]
SMP
Modules linked in:
CPU: 0
EIP: 0061:[<c0254428>] Not tainted VLI
EFLAGS: 00010286 (2.6.12-xenU)
EIP is at blk_start_queue+0x8/0x60
eax: 00000000 ebx: 00000000 ecx: 00000000 edx: fbffc000
esi: c12e0004 edi: c12b2d85 ebp: c119bf9c esp: c119bf28
ds: 007b es: 007b ss: 0069
Process xenwatch (pid: 10, threadinfo=c119a000 task=c006e580)
Stack: c0264862 c12e0000 c0266a8e 00000000 c12e0000 c026759c c12e0000
00000000
00000802 00000000 00000200 c12e0000 c02f8387 c119bf78 c03056b9
c02f6db2
c119bf70 00000000 00000200 00080000 00000000 c02674b0 c12b2a60
c119a000
Call Trace:
[<c0264862>] xenbus_dev_ok+0x32/0x60
[<c0266a8e>] kick_pending_request_queues+0x1e/0x40
[<c026759c>] watch_for_status+0xec/0x140
[<c02674b0>] watch_for_status+0x0/0x140
[<c0264e77>] xenwatch_thread+0x87/0x140
[<c01363c0>] autoremove_wake_function+0x0/0x60
[<c0264df0>] xenwatch_thread+0x0/0x140
[<c0135ea7>] kthread+0xc7/0xd0
[<c0135de0>] kthread+0x0/0xd0
[<c010782d>] kernel_thread_helper+0x5/0x18
Code: 00 00 00 8b 44 24 04 8b 48 60 ff e1 8d b4 26 00 00 00 00 81 44 24
04 a0 00 00 00 e9 e3 26 00 00 8d 76 00 53 83 ec 04 8b 5c 24 0c <f0> 0f
ba b3 04 01 00 00 02 f0 0f ba ab 04 01 00 00 06 19 c0 85
<6>IP: routing cache hash table of 1024 buckets, 8Kbyte
Going to run tests on same box and changset with Centos 4.1 as well
tomorrow.
Regards,
Ted
reply other threads:[~2005-10-14 1:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1129254787.12282.167.camel@pluto.linsolutions.com \
--to=tedkaz@optonline.net \
--cc=xen-devel@lists.xensource.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.