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-devel

Re: [Xen-devel] kernel panic (04 Sep 08)

To: Daisaku Watanabe <masakichi@xxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] kernel panic (04 Sep 08)
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Wed, 08 Sep 2004 17:14:31 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 08 Sep 2004 17:33:17 +0100
Envelope-to: steven.hand@xxxxxxxxxxxx
In-reply-to: Your message of "Thu, 09 Sep 2004 00:59:12 +0900." <20040909005912.2ca17e5c.masakichi@xxxxxxxxxxxxxxxxxx>
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
Well, it's dying in the slab allocator dereferencing a bad pointer. So
I guess the AGP/DRM stuff is trashing memory. :-(

 -- Keir

> 
> Hi Ian,
> 
> Oh, wait,
> seems this kernel panic I have here might be coming 
> from the X (or agpgart) issue on Intel chipsets 
> that Gerald Britton reported recently.
> (I'm using i915G, and this kernel panic is caused
> right after startx or display manager (gdm my case) started.
> If I don't touch X, xen keeps working fine).
> 
> I thought the logs might help to see what's happening.
> Sorry if I'm confused.
> 
> Best regards,
> D
> 
> On Wed, 08 Sep 2004 02:25:24 +0100
> Ian Pratt <Ian.Pratt@xxxxxxxxxxxx> wrote:
> (snip)
> > If you're working on the unstable tree, it's always good practice
> > to rebuild xen and the tools too. Use 'make dist' (and then
> > install all the images)
> > 
> > We only maintain interface compatibility in the stable series.
> This is thrones.honeypie.net.honeypie.net (Linux i686 2.6.8.1-xen0) 00:25:59
> 
> thrones.honeypie.net login: Oops: 0000 [#1]
> PREEMPT
> Modules linked in:
> CPU:    0
> EIP:    0061:[<c013c85f>]    Not tainted
> EFLAGS: 00213202   (2.6.8.1-xen0)
> EIP is at free_block+0x43/0xcb
> eax: 000bd780   ebx: 00200200   ecx: c5fbc000   edx: c1100000
> esi: c80fff80   edi: 00000003   ebp: c80fff8c   esp: c0451e88
> ds: 0069   es: 0069   ss: 0069
> Process swapper (pid: 0, threadinfo=c0450000 task=c03e50c0)
> Stack: c01f552e c80e0090 c80fff9c c0450000 00000005 c80e1080 c80e1090 c013d093
>        c80fff80 c80e1090 00000005 c80ffe9c c80fff80 c0450000 00000001 c013d1ef
>        c80fff80 c80e1080 00000000 c80ffe9c c0450000 c80ffff0 00000400 c0450000
> Call Trace:
>  [<c01f552e>] memmove+0x4d/0x4f
> 
>  [<c013d093>] drain_array+0x7c/0xb0
> 
>  [<c013d1ef>] cache_reap+0x77/0x20c
> 
>  [<c013d384>] reap_timer_fnc+0x0/0x2c
> 
>  [<c013d38c>] reap_timer_fnc+0x8/0x2c
> 
>  [<c0124527>] run_timer_softirq+0xe3/0x1e6
> 
>  [<c012057f>] __do_softirq+0x93/0x9c
> 
>  [<c01205cd>] do_softirq+0x45/0x47
> 
>  [<c010bfdf>] do_IRQ+0x100/0x132
> 
>  [<c01092c8>] evtchn_do_upcall+0xa8/0x111
> 
>  [<c010d8d7>] hypervisor_callback+0x33/0x49
> 
>  [<c0109c22>] xen_cpu_idle+0x6a/0x8c
> 
>  [<c010ee2e>] cpu_idle+0x2c/0x35
> 
>  [<c045269d>] start_kernel+0x1a0/0x1e9
> 
>  [<c04522bc>] unknown_bootoption+0x0/0x149
> 
> Code: 8b 53 04 8b 03 89 50 04 89 02 c7 43 04 00 02 20 00 2b 4b 0c
>  <0>Kernel panic: Fatal exception in interrupt
> In interrupt handler - not syncing
 -=- MIME -=- 
This is a multi-part message in MIME format.

--Multipart=_Thu__9_Sep_2004_00_59_12_+0900_3j46i6qUqJbnEXTC
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit


Hi Ian,

Oh, wait,
seems this kernel panic I have here might be coming 
from the X (or agpgart) issue on Intel chipsets 
that Gerald Britton reported recently.
(I'm using i915G, and this kernel panic is caused
right after startx or display manager (gdm my case) started.
If I don't touch X, xen keeps working fine).

I thought the logs might help to see what's happening.
Sorry if I'm confused.

Best regards,
D

On Wed, 08 Sep 2004 02:25:24 +0100
Ian Pratt <Ian.Pratt@xxxxxxxxxxxx> wrote:
(snip)
> If you're working on the unstable tree, it's always good practice
> to rebuild xen and the tools too. Use 'make dist' (and then
> install all the images)
> 
> We only maintain interface compatibility in the stable series.

--Multipart=_Thu__9_Sep_2004_00_59_12_+0900_3j46i6qUqJbnEXTC
Content-Type: text/x-log;
 name="xen_crash_after_startx.log"
Content-Disposition: attachment;
 filename="xen_crash_after_startx.log"
Content-Transfer-Encoding: 7bit

This is thrones.honeypie.net.honeypie.net (Linux i686 2.6.8.1-xen0) 00:25:59

thrones.honeypie.net login: Oops: 0000 [#1]
PREEMPT
Modules linked in:
CPU:    0
EIP:    0061:[<c013c85f>]    Not tainted
EFLAGS: 00213202   (2.6.8.1-xen0)
EIP is at free_block+0x43/0xcb
eax: 000bd780   ebx: 00200200   ecx: c5fbc000   edx: c1100000
esi: c80fff80   edi: 00000003   ebp: c80fff8c   esp: c0451e88
ds: 0069   es: 0069   ss: 0069
Process swapper (pid: 0, threadinfo=c0450000 task=c03e50c0)
Stack: c01f552e c80e0090 c80fff9c c0450000 00000005 c80e1080 c80e1090 c013d093
       c80fff80 c80e1090 00000005 c80ffe9c c80fff80 c0450000 00000001 c013d1ef
       c80fff80 c80e1080 00000000 c80ffe9c c0450000 c80ffff0 00000400 c0450000
Call Trace:
 [<c01f552e>] memmove+0x4d/0x4f

 [<c013d093>] drain_array+0x7c/0xb0

 [<c013d1ef>] cache_reap+0x77/0x20c

 [<c013d384>] reap_timer_fnc+0x0/0x2c

 [<c013d38c>] reap_timer_fnc+0x8/0x2c

 [<c0124527>] run_timer_softirq+0xe3/0x1e6

 [<c012057f>] __do_softirq+0x93/0x9c

 [<c01205cd>] do_softirq+0x45/0x47

 [<c010bfdf>] do_IRQ+0x100/0x132

 [<c01092c8>] evtchn_do_upcall+0xa8/0x111

 [<c010d8d7>] hypervisor_callback+0x33/0x49

 [<c0109c22>] xen_cpu_idle+0x6a/0x8c

 [<c010ee2e>] cpu_idle+0x2c/0x35

 [<c045269d>] start_kernel+0x1a0/0x1e9

 [<c04522bc>] unknown_bootoption+0x0/0x149

Code: 8b 53 04 8b 03 89 50 04 89 02 c7 43 04 00 02 20 00 2b 4b 0c
 <0>Kernel panic: Fatal exception in interrupt
In interrupt handler - not syncing

--Multipart=_Thu__9_Sep_2004_00_59_12_+0900_3j46i6qUqJbnEXTC--


-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel



-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel

<Prev in Thread] Current Thread [Next in Thread>