| |
|
 |
|
 |
|
|
|
| |
|
|
xen-devel
RE: [Xen-devel] crash on starting new domain
Can you reproduce this with a 2.0-testing kernel? Are you sure your
iscsi modules were actually built against this kernel version?
Ian
> Okay it wasn't hung afterall, it just took a while to reboot.
> I've managed to get an oops dump from the console:
>
> Unable to handle kernel paging request at virtual address
> c7e70000 printing eip:
> c88eadbb
> *pde = ma 0141d067 pa 0001d067
> *pte = ma 00000000 pa 55555000
> [pg0+140185564/1003249664]
> journal_commit_transaction+0xc3c/0xf80 [jbd]
> [autoremove_wake_function+0/96]
> autoremove_wake_function+0x0/0x60 [find_get_page+39/80]
> find_get_page+0x27/0x50 [autoremove_wake_function+0/96]
> autoremove_wake_function+0x0/0x60 [pg0+140194829/1003249664]
> kjournald+0xcd/0x1f0 [jbd] [autoremove_wake_function+0/96]
> autoremove_wake_function+0x0/0x60
> [autoremove_wake_function+0/96]
> autoremove_wake_function+0x0/0x60 [ret_from_fork+6/28]
> ret_from_fork+0x6/0x1c [pg0+140194592/1003249664]
> commit_timeout+0x0/0x10 [jbd] [pg0+140194624/1003249664]
> kjournald+0x0/0x1f0 [jbd] [kernel_thread_helper+5/16]
> kernel_thread_helper+0x5/0x10
> Oops: 0002 [#1]
> Modules linked in: nfsd exportfs lockd sunrpc tlan 8021q loop
> ext3 jbd mbcache crc32c libcrc32c iscsi_sfnet
> scsi_transport_iscsi dm_mod sd_mod scsi_mod e1000 eepro100
> CPU: 0
> EIP: 0061:[pg0+140197307/1003249664] Not tainted VLI
> EFLAGS: 00011206 (2.6.10-xen0)
> EIP is at journal_get_descriptor_buffer+0x6b/0xb0 [jbd]
> eax: 00000000 ebx: c757eb3c ecx: 00000400 edx: 00001000
> esi: 00000000 edi: c7e70000 ebp: c79bbec0 esp: c797bdc0
> ds: 007b es: 007b ss: 0069
> Process kjournald (pid: 856, threadinfo=c797a000 task=c1288a60)
> Stack: c05b81c0 00000624 00001000 00000624 c6eae92c c61ce920
> c72baf8c 00000000 <I stopped cleaning it up at this point>
> Apr 6 01:41:52 xen1
> kernel: c88e7fdc c79bbec0 c61ce920 00000008 00000622 c10f6a60
> c797a000 c797a000
>
> Apr 6 01:41:52 xen1 kernel: 00000000 00000000
> 00000000 00000000
> 00000000 c6eaec8c 00000622 00000000
> Apr 6 01:41:52 xen1 kernel: Call Trace:
>
> Apr 6
> 01:41:52 xen1 kernel: [pg0+140185564/1003249664]
> journal_commit_transaction+0xc3c/0xf80 [jbd]
> Apr 6 01:41:52 xen1 kernel:
> [autoremove_wake_function+0/96] autoremove_wake_function+0x0/0x60
> Apr 6 01:41:52 xen1 kernel:
> [find_get_page+39/80] find_get_page+0x27/0x50
> Apr 6 01:41:52 xen1 kernel:
> [autoremove_wake_function+0/96] autoremove_wake_function+0x0/0x60
> Apr 6 01:41:52 xen1 kernel:
> [pg0+140194829/1003249664] kjournald+0xcd/0x1f0 [jbd]
> Apr 6 01:41:52 xen1 kernel:
> [autoremove_wake_function+0/96] autoremove_wake_function+0x0/0x60
> Apr 6 01:41:52 xen1
> kernel: [autoremove_wake_function+0/96]
> autoremove_wake_function+0x0/0x60
> Apr 6
> 01:41:52 xen1 kernel: [ret_from_fork+6/28] ret_from_fork+0x6/0x1c
> Apr
> 6 01:41:52
> xen1 kernel: [pg0+140194592/1003249664] commit_timeout+0x0/0x10 [jbd]
> Apr 6
> 01:41:52 xen1 kernel: [pg0+140194624/1003249664]
> kjournald+0x0/0x1f0 [jbd]
>
> Apr 6
> 01:41:52 xen1 kernel: [kernel_thread_helper+5/16]
> kernel_thread_helper+0x5/0x10
>
> Apr 6 01:41:52 xen1 kernel: Code: 04 8b 85 88 00 00 00 89 04
> 24 e8 11 8e 86 f7 89 c3 0f ba 28 02 19 c0 85 c0 75 46 8b 95
> 8c 00 00 00 89 f0 8b 7b 18 89 d1 c1 e9 02 <f3> ab f6 c2 02 74
> 02 66 ab f6 c2 01 74 01 aa 0f ba 2b 00 89 d8
>
> ipt_limit
>
> > -----Original Message-----
> > From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx [mailto:xen-devel-
> > bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of James Harper
> > Sent: Tuesday, 5 April 2005 14:38
> > To: xen-devel@xxxxxxxxxxxxxxxxxxx
> > Subject: [Xen-devel] crash on starting new domain
> >
> > I've just built some shiny xen 2.0.5 kernel packages for
> debian using
> > the stuff in 'experimental', and cannot seem to create a new domain.
> The
> > whole machine just reboots. I've caught the first line of a kernel
> oops
> > but haven't got physical access to the machine at the moment.
> >
> > The console of the domain looks like this:
> >
> > Adding 262136k swap on /dev/hda2. Priority:-1 extents:1 EXT3-fs
> > warning: mounting fs with errors, running e2fsck is
> recommended
> > EXT3 FS on hda1, internal journal
> > hwclock is unable to get I/O port access: the iopl(3) call failed.
> > System time was Tue Apr 5 15:31:42 UTC 2005.
> > Setting the System Clock using the Hardware Clock as reference...
> > hwclock is unable to get I/O port access: the iopl(3) call failed.
> > SysteSegmentation fault
> >
> > Any ideas? It's an SMP machine if that makes any
> difference. The exact
> > same setup was working a few stable versions ago. It's just decided
> not
> > to reboot anymore so I'll have to get someone in the office
> to reboot
> it
> > for me.
> >
> > James
> >
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@xxxxxxxxxxxxxxxxxxx
> > http://lists.xensource.com/xen-devel
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
>
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
| |
|
Home