| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-Id: <20090726012112.M10928@allidaho.com> Date: Sat, 25 Jul 2009 19:26:32 -0600 From: "Dialup Jon Norstog" <thursday@...idaho.com> To: Michael Cree <mcree@...on.net.nz>, Dave Airlie <airlied@...il.com> Cc: linux-alpha@...r.kernel.org, linux-kernel@...r.kernel.org, xorg@...ts.freedesktop.org Subject: Re: Kernel 2.6.30.1 Oops on Alpha Architecture when starting Xserver My experience: I have loaded linux on a number of Alphamachines, including the PWS series, XP100 and UP2000/+. Sometimes the X-erver doesn't work. And it trashes the whole install. Once that happens, you can chaNGE graphics cards but the X-serve will not recover, maybe because the kernel is implicated in the whole train wreck. I usually just wipe everything clean and re-install with a known good graphics card. It wasn't a problem back when Compaq was paying Red Hat to put together the 7.1 and 7.2 distros. There just aren't enough people working on Linux Alpha, and the whole thing has gotten rickety. IMHO jn ---------- Original Message ----------- From: Michael Cree <mcree@...on.net.nz> To: Dave Airlie <airlied@...il.com> Cc: linux-alpha@...r.kernel.org, linux-kernel@...r.kernel.org, xorg@...ts.freedesktop.org Sent: Sun, 26 Jul 2009 12:05:31 +1200 Subject: Re: Kernel 2.6.30.1 Oops on Alpha Architecture when starting Xserver > Dave Airlie wrote: > >>>> The kernel oops is: > >>>> > >>>> > >>> So its a machine check, > >>> > >>> > >> So, does this indicate a software fault (e.g. inconsistencies in kernel data > >> structures) or does it imply a hardware fault? > >> > >> > >>> Well X is trying to post the graphics card you have installed, and the > >>> machine > >>> is falling over when it does it. > >>> > >>> > >> SRM (the equivalent of a BIOS) cannot post the card on startup. But I have > >> had the card (radeon rv610) post correctly and working in the past when I > >> compiled the complete 1.5.3 Xserver myself. I had it working with both the > >> radeon and radeonhd drivers and a 2.6.29.x kernel patched to support > >> libpciaccess. > >> > > > > There is no -ati card in that machine, its got some SiS card which is > > completely > > different, maybe its some onboard card or something. > > > > No, you have misunderstood. I removed that Radeon rv610 card (that > caused the kernel oops) from the machine and replaced it with an old > SiS card I have. The behaviour changed: now the Xserver locks up on > initialisation and consumes 100% CPU. The backtrace I provided is > with the SiS card only. I thought it might be helpful to locate the > problem > (assuming that we are seeing a different symptom of the same > underlying problem). > > BTW, my attempt to CC the xorg mailing list failed. It would seem > that they are too exclusive to allow posting to their email list > without subscription. Putting up such barriers means they won't get > bug reports from such people as myself. Their loss. > > Cheers > Michael > > -- > To unsubscribe from this list: send the line "unsubscribe linux- > alpha" in the body of a message to majordomo@...r.kernel.org More > majordomo info at http://vger.kernel.org/majordomo-info.html > > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. ------- End of Original Message ------- -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists