On Mon Nov 23 23:46:39 1998, Anton Blanchard <[EMAIL PROTECTED]> wrote:
jmlb2> I switched back to 2.1.125 and the situation is now: jmlb2> startx as root works OK, but when you end the X-session, the kernel jmlb2> halts itself. jmlb2> xdm works OK, but if you kill xdm (/etc/init.d/xdm stop) the kernel jmlb2> commits suicide :-( > > Are you using a cgsix framebuffer? The current kernels have a problem with the > cgsix, which Davem narrowed down to the cg6_reset function. > > Do you get booted back to the PROM? If so can you get the results of: > > .locals > .registers > ctrace > > As well as your System.map I have a similar problem. I use X via startx. When I quit X, I get: Nov 24 12:28:07 tashkent kernel: Unable to handle kernel paging request at virtual address fd014000 Nov 24 12:28:07 tashkent kernel: tsk->mm->context = 0000002d Nov 24 12:28:07 tashkent kernel: tsk->mm->pgd = f55ab000 Nov 24 12:28:07 tashkent kernel: \|/ ____ \|/ Nov 24 12:28:07 tashkent kernel: "@'/ ,. \`@" Nov 24 12:28:07 tashkent kernel: /_| \__/ |_\ Nov 24 12:28:07 tashkent kernel: \__U_/ Nov 24 12:28:07 tashkent kernel: Xsun(299): Oops Nov 24 12:28:07 tashkent kernel: PSR: 040000c1 PC: f0127608 NPC: f012760c Y: 00000000 Nov 24 12:28:07 tashkent kernel: g0: 0000009c g1: ffffff7f g2: 0022b000 g3: 00000060 g4: 002ce778 g5: 00000000 g6: f546c000 g7: 00000000 Nov 24 12:28:07 tashkent kernel: o0: f000b000 o1: fd014000 o2: fd018000 o3: f01d2000 o4: f018bae0 o5: 00000001 sp: f546dd68 o7: f0125510 Nov 24 12:28:07 tashkent kernel: l0: 040000c2 l1: f001c9bc l2: f001c9ac l3: 00000004 l4: 00000001 l5: 00000002 l6: f546c000 l7: 00239bdc Nov 24 12:28:07 tashkent kernel: i0: f000b000 i1: f000b000 i2: f0125488 i3: 00000000 i4: f546c584 i5: f546c000 fp: f546ddd0 i7: f0123af8 Nov 24 12:28:07 tashkent kernel: Instruction DUMP: 8608c002 c6226004 050008ac <c6026004> 8410a280 8610c002 c6226004 c0226008 c02260c0 This set of messages also appears on the screen, which remains in VT 7. I am using the latest CVS kernel, 2.1.129 from vger (except that I am using linux/drivers/net/sunlance.c from the 2.1.129 on tsx-11, and I have turned SunOS emulation back on). I will send System.map separately. If I try to run X a second time, I get a message similar to the above, immediately. As a result, I can only run X once per boot-up. My hardware: SS 5, cgsix. --Paul Vojta, [EMAIL PROTECTED]
