I have an SGI Octane which runs X.org (from http://dev.gentoo.org/~geoman/ Xstuff/monolithic/xorg-x11-6.8.99.15-r4.tbz2) without trouble if started from the console with "startx". However, every time I try to start the display manager WDM (x11-misc/wdm-1.28), I get a kernel oops. Reproducible: Always Steps to Reproduce: Oops message from dmesg: ---------- Data bus error, epc == a80000002011bb70, ra == a800000020137cc4 Oops in arch/mips/kernel/traps.c::do_be, line 361[#5]: Cpu 0 $ 0 : 0000000000000000 0000000020360000 000000007f87f098 0000000000000000 $ 4 : 000000007f87d098 a800000000004000 0000000000001000 0000000000001000 $ 8 : 0000000000000040 0000000000000000 0000000000000000 0000000000000000 $12 : 0000000000000000 000000007f87e098 a80000002008da10 0000000000000000 $16 : a800000000004000 0000000000001000 000000007f87d098 0000000000004000 $20 : 0000000000002000 0000000000000000 a8000000237bfe78 a800000000000000 $24 : 0000000000000000 000000002b527230 $28 : a8000000237bc000 a8000000237bfdf0 0000000000000001 a800000020137cc4 Hi : 0000000000000157 Lo : 00000000000001e3 epc : a80000002011bb70 both_aligned+0x18/0x74 Tainted: P ra : a800000020137cc4 read_mem+0xe4/0x178 Status: 9000fce3 KX SX UX KERNEL EXL IE Cause : 0000001c PrId : 00000927 Modules linked in: nfs lockd nfs_acl sunrpc autofs4 snd_rad1 snd_pcm snd_timer snd soundcore snd_page_alloc Process wdm (pid: 6911, threadinfo=a8000000237bc000, task=a80000002ed5f328) Stack : a800000023788980 0000000000002000 0000000000000000 000000007f87d098 a8000000237bfe78 000000007f87d098 0000000010009c10 000000007f87d088 a80000002008d718 a80000002008d68c 0000000000002000 000000007f87d098 a800000023788980 fffffffffffffff7 0000000010000000 a80000002008da60 000000002ee14cd0 0000000000004000 00000000000003fe 00000000100016a0 0000000000000008 0000000000000010 a80000002001e8e8 a80000002001e8e8 0000000000000000 ffffffff9000fce0 0000000000000fa3 0000000000000038 0000000000000008 000000007f87d098 0000000000002000 0000000034943643 0000000000000000 0000000000000400 0000000000420000 0000000010009d40 0000000000000000 0000000000000005 a80000002007db48 000000000000000c ... Call Trace: [<a80000002008d718>] vfs_read+0x180/0x198 [<a80000002008d68c>] vfs_read+0xf4/0x198 [<a80000002008da60>] sys_read+0x50/0x98 [<a80000002001e8e8>] handle_sys+0x128/0x144 [<a80000002001e8e8>] handle_sys+0x128/0x144 [<a80000002007db48>] sys_munmap+0x0/0x78 Code: cca00060 cc810060 00000000 <dca80000> dca90008 dcaa0010 dcab0018 64c6ffc0 dcac0020 ---------- The same oops, after being run through ksymoops: ---------- ksymoops 2.4.11 on mips64 2.6.13.4-mipscvs-20050914. Options used -V (default) -k /proc/ksyms (default) -l /proc/modules (default) -o /lib/modules/2.6.13.4-mipscvs-20050914/ (default) -m /usr/src/linux/System.map (default) Warning: You did not tell me where to find symbol information. I will assume that the log matches the kernel and modules that are running right now and I'll use the default options above for symbol resolution. If the current kernel and/or modules do not match the log, you can get more accurate output by telling me the kernel version and where to find map, modules, ksyms etc. ksymoops -h explains the options. Error (regular_file): read_ksyms stat /proc/ksyms failed ksymoops: No such file or directory No modules in ksyms, skipping objects No ksyms, skipping lsmod Reading Oops report from the terminal Data bus error, epc == a80000002011bb70, ra == a800000020137cc4 Cpu 0 $ 0 : 0000000000000000 0000000020360000 000000007f87f098 0000000000000000 $ 4 : 000000007f87d098 a800000000004000 0000000000001000 0000000000001000 $ 8 : 0000000000000040 0000000000000000 0000000000000000 0000000000000000 $12 : 0000000000000000 000000007f87e098 a80000002008da10 0000000000000000 $16 : a800000000004000 0000000000001000 000000007f87d098 0000000000004000 $20 : 0000000000002000 0000000000000000 a8000000237bfe78 a800000000000000 $24 : 0000000000000000 000000002b527230 $28 : a8000000237bc000 a8000000237bfdf0 0000000000000001 a800000020137cc4 Hi : 0000000000000157 Lo : 00000000000001e3 epc : a80000002011bb70 both_aligned+0x18/0x74 Tainted: P Using defaults from ksymoops -t elf32-tradbigmips -a mips:8000 Status: 9000fce3 KX SX UX KERNEL EXL IE Cause : 0000001c a8000000237bfe78 000000007f87d098 0000000010009c10 000000007f87d088 a80000002008d718 a80000002008d68c 0000000000002000 000000007f87d098 a800000023788980 fffffffffffffff7 0000000010000000 a80000002008da60 000000002ee14cd0 0000000000004000 00000000000003fe 00000000100016a0 0000000000000008 0000000000000010 a80000002001e8e8 a80000002001e8e8 0000000000000000 ffffffff9000fce0 0000000000000fa3 0000000000000038 0000000000000008 000000007f87d098 0000000000002000 0000000034943643 0000000000000000 0000000000000400 0000000000420000 0000000010009d40 0000000000000000 0000000000000005 a80000002007db48 000000000000000c Call Trace: [<a80000002008d718>] vfs_read+0x180/0x198 [<a80000002008d68c>] vfs_read+0xf4/0x198 [<a80000002008da60>] sys_read+0x50/0x98 [<a80000002001e8e8>] handle_sys+0x128/0x144 [<a80000002001e8e8>] handle_sys+0x128/0x144 [<a80000002007db48>] sys_munmap+0x0/0x78 Code: cca00060 cc810060 00000000 <dca80000> dca90008 dcaa0010 dcab0018 64c6ffc0 dcac0020 >>RA; a800000020137cc4 <read_mem+e4/178> >>$14; a80000002008da10 <sys_read+0/98> >>$31; a800000020137cc4 <read_mem+e4/178> >>PC; a80000002011bb70 <both_aligned+18/74> <===== Trace; a80000002008d718 <vfs_read+180/198> Trace; a80000002008d68c <vfs_read+f4/198> Trace; a80000002008da60 <sys_read+50/98> Trace; a80000002001e8e8 <handle_sys+128/144> Trace; a80000002001e8e8 <handle_sys+128/144> Trace; a80000002007db48 <sys_munmap+0/78> Code; a80000002011bb64 <both_aligned+c/74> 00000000 <_PC>: Code; a80000002011bb64 <both_aligned+c/74> 0: cca00060 pref 0x0,96(a1) Code; a80000002011bb68 <both_aligned+10/74> 4: cc810060 pref 0x1,96(a0) Code; a80000002011bb6c <both_aligned+14/74> 8: 00000000 nop Code; a80000002011bb70 <both_aligned+18/74> <===== c: dca80000 ld t0,0(a1) <===== Code; a80000002011bb74 <both_aligned+1c/74> 10: dca90008 ld t1,8(a1) Code; a80000002011bb78 <both_aligned+20/74> 14: dcaa0010 ld t2,16(a1) Code; a80000002011bb7c <both_aligned+24/74> 18: dcab0018 ld t3,24(a1) Code; a80000002011bb80 <both_aligned+28/74> 1c: 64c6ffc0 daddiu a2,a2,-64 Code; a80000002011bb84 <both_aligned+2c/74> 20: dcac0020 ld t4,32(a1) 1 warning and 1 error issued. Results may not be reliable. ---------- emerge --info: ---------- Portage 2.0.53_rc7 (default-linux/mips/2005.0, gcc-3.4.4, glibc-2.3.5-r2, 2.6. 13.4-mipscvs-20050914 mips64) ================================================================= System uname: 2.6.13.4-mipscvs-20050914 mips64 R10000 V2.7 FPU V0.0 Gentoo Base System version 1.12.0_pre9 ccache version 2.4 [enabled] dev-lang/python: 2.3.4-r1, 2.4.2 sys-apps/sandbox: 1.2.13 sys-devel/autoconf: 2.13, 2.59-r7 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1 sys-devel/binutils: 2.16.90.0.3 sys-devel/libtool: 1.5.20-r1 virtual/os-headers: 2.6.11-r1 ACCEPT_KEYWORDS="mips ~mips" AUTOCLEAN="yes" CBUILD="mips-unknown-linux-gnu" CFLAGS="-O2 -pipe -mips4 -mabi=32 -fweb -ftracer -frename-registers" CHOST="mips-unknown-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/lib/ X11/xkb /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/ dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/ config/ /usr/share/texmf/xdvi/ /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -pipe -mips4 -mabi=32 -fweb -ftracer -frename-registers" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig buildpkg ccache distlocks sandbox sfperms strict userpriv" GENTOO_MIRRORS="http://mirror.gentoo.se http://distfiles.gentoo.org http://www. ibiblio.org/pub/Linux/distributions/gentoo" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage" USE="mips X bash-completion berkdb bitmap-fonts cairo cups gdbm gif ip30 jpeg kerberos libwww motif ncurses nls nomultilib opengl pam perl png python readline sdl sqlite ssl tcpd tetex tiff truetype truetype-fonts type1-fonts udev unicode xml2 xv zlib userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS, MAKEOPTS, PORTDIR_OVERLAY
Is it possible to run 2.6.14 on MIPS?
There are required patches in sys-kernel/mips-sources, and that package doesn't have a 2.6.14 version. However, 2.6.14 is in the linux-mips.org Git archive, so perhaps it wouldn't be too difficult to make one. mips@gentoo.org should know more.
Well, I must say there is a reason that this was never keyworded. I tested it a loooooooong time ago on an indy, and it didn't work there. Note that it didn't oops, but it just didn't work (I forget exactly what happened). Anything that causes a kernel oops like this is definitely an upstream kernel problem, as the kernel should *never* oops. Furthermore, it is possible that this oops is Octane specific, since each mips device is practically a separate arch with a lot of different code. Your best bet is probably to ask the linux-mips@linux-mips.org mailing list. However, you have made me curious. I'll give wdm another whirl on an indy, and perhaps my O2 as well. I'd really like all the display managers to work for us. Wdm seemed interesting because it was more functional than xdm, but not as bloated with deps as kdm and gdm (both of which work just fine on mips, by the way).
Ok, I've confirmed this on ip22 (Indy). See http://dev.gentoo.org/~geoman/wdmoops.txt and http://dev.gentoo.org/~geoman/wdmstrace.txt for an oops and strace. I'm not sure what to say at this point. Note that I can only reproduce this oops when there is a server defined in /etc/X11/wdm/Xservers. For now I would say to forget about using wdm, because this seems to be a problem with the linux-mips kernel tree. For what it's worth, I'm using linux-mips git 2.6.14-rc2-g54855a75 from a couple weeks ago or so.
I, too, wanted WDM because it was the simplest DM I could find that used PAM, which is required since we use Kerberos. After compiling for two days I now run KDM (3.4.3-r1) instead, which seems to work fine. Should I report this to the linux-mips list, or will you do that since you can reproduce it yourself?
Primarily a MIPS issue...
Dead bug.
