[Xen-bugs] [Bug 176] x86_64 - Unable to boot domU

[bugzilla-daemon@xxxxxxxxxxxxxxxxxxx]

http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=176


etomsch@xxxxxxxxxx changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |etomsch@xxxxxxxxxx
             Status|RESOLVED                    |REOPENED
         Resolution|FIXED                       |




------- Additional Comments From etomsch@xxxxxxxxxx  2005-09-21 16:00 -------
I've still the same problem here on a PentiumD:

Kernel-output on Dom0:
Unable to handle kernel NULL pointer dereference at 0000000000000038 RIP: 
<ffffffff801623b8>{generic_page_range+93}
PGD 0 
Oops: 0000 [1] SMP 
CPU 0 
Modules linked in:
Pid: 5942, comm: kxbwatch Not tainted 2.6.12-xen0-br11
RIP: e030:[<ffffffff801623b8>] <ffffffff801623b8>{generic_page_range+93}
RSP: e02b:ffff88003aa29468  EFLAGS: 00010202
RAX: 0000000000000c20 RBX: ffffc20000518000 RCX: 0000000000000068
RDX: 0000000000000000 RSI: ffffc20000518000 RDI: 0000000000000068
RBP: 00000000ba739000 R08: ffff88003aa29530 R09: 0000000000000001
R10: 00000000000000a0 R11: 0000000000000202 R12: 0000000000001000
R13: ffff88003aa29538 R14: 0000000000000001 R15: 0000000000000010
FS:  0000000000000000(0000) GS:ffffffff805b9680(0000) knlGS:0000000000000000
CS:  e033 DS: 0000 ES: 0000
Process kxbwatch (pid: 5942, threadinfo ffff88003aa28000, task ffff88003b5590b0)
Stack: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 
       0000000000000000 0000000000000000 ffffc20000519000 0000000000000c20 
       ffff88003aa29530 ffffffff801206c0 
Call Trace:<ffffffff801206c0>{direct_remap_area_pte_fn+0} <ffffffff80120818>
{__direct_remap_pfn_range+280}
       <ffffffff802e89c2>{task_in_intr+0} <ffffffff80119ed9>{monotonic_clock+78}
       <ffffffff80403df9>{thread_return+0} <ffffffff80403e58>{thread_return+95}
       <ffffffff80119ed9>{monotonic_clock+78} 
<ffffffff80119ed9>{monotonic_clock+78}
       <ffffffff80403df9>{thread_return+0} 
<ffffffff80119ed9>{monotonic_clock+78}
       <ffffffff80403df9>{thread_return+0} <ffffffff80403e58>{thread_return+95}
       <ffffffff80403df9>{thread_return+0} <ffffffff80403e58>{thread_return+95}
       <ffffffff80119ed9>{monotonic_clock+78} <ffffffff80147e6a>{finish_wait+65}
       <ffffffff802d9775>{xs_input_avail+60} <ffffffff802d993c>{xb_read+440}
       <ffffffff80147eb1>{autoremove_wake_function+0} 
<ffffffff80244c79>{vsscanf+1596}
       <ffffffff80244d31>{sscanf+136} <ffffffff802d9c44>{xs_talkv+263}
       <ffffffff802d9cfd>{xs_single+62} <ffffffff802da4a2>{xenbus_gather+299}
       <ffffffff80117100>{xen_send_IPI_mask+255} 
<ffffffff8016a9de>{__get_vm_area+397}
       <ffffffff802deeb5>{netif_map+137} 
<ffffffff802de737>{frontend_changed+443}
       <ffffffff80147934>{keventd_create_kthread+0} 
<ffffffff802da893>{watch_thread+375}
       <ffffffff80147eb1>{autoremove_wake_function+0} 
<ffffffff80147eb1>{autoremove_wake_function
+0}
       <ffffffff802da71c>{watch_thread+0} <ffffffff801478f9>{kthread+218}
       <ffffffff801128d7>{child_rip+8} 
<ffffffff80147934>{keventd_create_kthread+0}
       <ffffffff8014781f>{kthread+0} <ffffffff801128cf>{child_rip+0}
       

Code: 48 8b 52 38 48 89 4c 24 18 48 01 d0 48 89 44 24 38 e8 3a 2c 
RIP <ffffffff801623b8>{generic_page_range+93} RSP <ffff88003aa29468>
CR2: 0000000000000038
 
DomU:
VFS: Cannot open root device "sdb2" or unknown-block(0,0)
Please append a correct "root=" boot option
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

all that after a few seconds hang at xen_blk, ending with
xen_blk:Timeout connecting to device!

I think thats the same problem as previously. I'm working with the latest hg 
pull'ed xen-unstable

-- 
Configure bugmail: 
http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-bugs