Re: [XenPPC] Crash with ssh

2006-11-27 Thread Jimi Xenidis
BTW: in the future, if you are lucky enough to get xmon, please do a register dump ('r'), special register dump ('S'), and a function traceback ('t') (use '?' for help) and send that as well. -JX On Nov 27, 2006, at 12:08 PM, Jimi Xenidis wrote: On Nov 27, 2006, at 12:02 PM, Maria Butrico

Re: [XenPPC] Crash with ssh

2006-11-27 Thread Jimi Xenidis
On Nov 27, 2006, at 12:02 PM, Maria Butrico wrote: Jimi, where did you get the idea that this linux was SMP. I recall that we build Linux for SMP even though we run it UP if we boot it on a xen partition.Maybe you see something I missed. This: cso85:/ # cpu 0x2: Vector: 700 (Program

Re: [XenPPC] Crash with ssh

2006-11-27 Thread Maria Butrico
Jimi, where did you get the idea that this linux was SMP. I recall that we build Linux for SMP even though we run it UP if we boot it on a xen partition.Maybe you see something I missed. Jimi Xenidis wrote: Thanks for clarifying this Dilma, there is no Xen present if the Linux is SMP :)

Re: [XenPPC] Crash with ssh

2006-11-27 Thread Jimi Xenidis
Thanks for clarifying this Dilma, there is no Xen present if the Linux is SMP :) -JX On Nov 27, 2006, at 10:25 AM, Dilma DaSilva wrote: This is not a xen problem. I believe it's a gpfs problem on the shutdown/umount path. We're using gpfs with a kernel version that it doesn't support yet and

Re: [XenPPC] Crash with ssh

2006-11-27 Thread Dilma DaSilva
This is not a xen problem. I believe it's a gpfs problem on the shutdown/umount path. We're using gpfs with a kernel version that it doesn't support yet and I have fixed problems related to clear_inode before (Linux has changed some interfaces in the vfs layer on 2.6.17). Dilma David M Daly wri

[XenPPC] Crash with ssh

2006-11-27 Thread David M Daly
I got the following error this morning from the console on one of our JS21s. I had a program that was supposed to ssh into the blade and reboot it after shutting down GPFS. I don't think it did any of the gpfs shutdown before crashing. Here is the error message. I saw it because I happened to b