WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

RE: [Xen-users] kernel panic on boot of dom0

To: "Ian P. Christian" <pookey@xxxxxxxxxxxx>, <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-users] kernel panic on boot of dom0
From: "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
Date: Fri, 18 Nov 2005 15:55:07 -0000
Cc: Ernst Bachmann <e.bachmann@xxxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, ian.pratt@xxxxxxxxxxxx
Delivery-date: Fri, 18 Nov 2005 15:57:28 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcXsU7ed7E7Kwiy9QGmA0LdTI+el3AABDlEQ
Thread-topic: [Xen-users] kernel panic on boot of dom0
Are you importing the block device as scsi? e.g. sda? 

If so, try IDE hda.

The scsi major has already been grabbed. 

Ian  

> -----Original Message-----
> From: Ian P. Christian [mailto:pookey@xxxxxxxxxxxx] 
> Sent: 18 November 2005 15:21
> To: xen-users@xxxxxxxxxxxxxxxxxxx
> Cc: Ian Pratt; Ernst Bachmann; xen-devel; ian.pratt@xxxxxxxxxxxx
> Subject: Re: [Xen-users] kernel panic on boot of dom0
> 
> On Friday 18 November 2005 14:59, Ian P. Christian wrote:
> > I'll recompile a kernel starting with teh defaults specified in 
> > xen0_defconfig, and see how things go.
> 
> Well, no opps on boot now, but having attempted to start a 
> domU, I'm seeing what apepars to the the same opps as before.
> 
> Thanks for your help people, much appreciated
> 
> # xm create /etc/xen/auto/ttylinux -c
> Using config file "/etc/xen/auto/ttylinux".
> Started domain ttylinux
> Linux version 2.6.12.6.5-xen (root@bb3) (gcc version 3.4.4 
> (Gentoo 3.4.4-r1, ssp-3.4.4-1.0, pie-8.7.8)) #2 SMP Fri Nov 
> 18 15:47:14 GMT 2005 BIOS-provided physical RAM map:
>  Xen: 0000000000000000 - 0000000004000000 (usable) 0MB 
> HIGHMEM available.
> 72MB LOWMEM available.
> IRQ lockup detection disabled
> Built 1 zonelists
> Kernel command line:  ip=1.2.3.4:1.2.3.4::::eth0:off 
> root=/dev/sda1 ro Initializing CPU#0 PID hash table entries: 
> 512 (order: 9, 8192 bytes) Xen reported: 2800.104 MHz processor.
> Dentry cache hash table entries: 16384 (order: 4, 65536 
> bytes) Inode-cache hash table entries: 8192 (order: 3, 32768 
> bytes) vmalloc area: c5000000-fb7fe000, maxmem 34000000
> Memory: 62320k/73728k available (1369k kernel code, 3072k 
> reserved, 404k data, 128k init, 0k highmem) Checking if this 
> processor honours the WP bit even in supervisor mode... Ok.
> Mount-cache hash table entries: 512
> CPU: Trace cache: 12K uops, L1 D cache: 16K
> CPU: L2 cache: 1024K
> Enabling fast FPU save and restore... done.
> Enabling unmasked SIMD FPU exception support... done.
> Checking 'hlt' instruction... disabled
> Brought up 1 CPUs
> NET: Registered protocol family 16
> xenbus_probe_init
> Brought up 1 CPUs
> xen_mem: Initialising balloon driver.
> SCSI subsystem initialized
> Grant table initialized
> Number of CPUs sharing cache didn't match any known set of 
> CPUs Number of CPUs sharing cache didn't match any known set 
> of CPUs Initializing Cryptographic API io scheduler noop 
> registered io scheduler anticipatory registered io scheduler 
> deadline registered io scheduler cfq registered RAMDISK 
> driver initialized: 16 RAM disks of 4096K size 1024 blocksize 
> Xen virtual console successfully installed as tty1 
> Event-channel device installed.
> xen_net: Initialising virtual ethernet driver.
> NET: Registered protocol family 2
> Registering block device major 8
> 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:
> c01dfaa7
> *pde = ma 00000000 pa 55555000
> Oops: 0002 [#1]
> SMP
> Modules linked in:
> CPU:    0
> EIP:    0061:[<c01dfaa7>]    Not tainted VLI
> EFLAGS: 00010296   (2.6.12.6.5-xen)
> EIP is at blk_start_queue+0x8/0x4f
> eax: 00000000   ebx: 00000000   ecx: 00000000   edx: fbfc4000
> esi: c039c004   edi: c03fbc23   ebp: c0345f6c   esp: c0345efc
> ds: 007b   es: 007b   ss: 0069
> Process xenwatch (pid: 7, threadinfo=c0344000 task=c032fa20)
> Stack: 00000000 c039c000 c01f107a 00000000 c039c000 c01f1aa3 
> c039c000 00000000
>        00000801 00000000 00000200 c039c000 c02640d1 c0345f48 
> c026a147 c0263cc7
>        c0345f4c 00000000 00007d00 00000000 00000200 c0345f8c 
> c0345f98 c03fbac0 Call Trace:
>  [<c01f107a>] kick_pending_request_queues+0x1e/0x33
>  [<c01f1aa3>] watch_for_status+0xed/0x135  [<c01ef665>] 
> xenwatch_thread+0x10e/0x133  [<c01317f2>] 
> autoremove_wake_function+0x0/0x57  [<c01317f2>] 
> autoremove_wake_function+0x0/0x57  [<c01ef557>] 
> xenwatch_thread+0x0/0x133  [<c0131324>] kthread+0xba/0xf0  
> [<c013126a>] kthread+0x0/0xf0  [<c0107911>] 
> kernel_thread_helper+0x5/0xb
> Code: d2 75 01 c3 89 44 24 04 8b 48 60 ff e1 8b 44 24 04 8b 
> 48 60 ff e1 81 44
> 24 04 a0 00 00 00 e9 95 24 00 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 512 buckets, 4Kbytes TCP 
> established hash table entries: 4096 (order: 3, 32768 bytes) 
> TCP bind hash table entries: 4096 (order: 3, 32768 bytes)
> TCP: Hash tables configured (established 4096 bind 4096)
> NET: Registered protocol family 1
> NET: Registered protocol family 17
> VFS: Cannot open root device "sda1" 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)
> 
> -- 
> Ian P. Christian ~ http://pookey.co.uk
> 

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