Mailing List ArchiveSupport open source code!
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]tlug: New Kernel + XEmacs = BAD medicine (sound-related?)
- To: Matt Gushee <matt@example.com>
- Subject: tlug: New Kernel + XEmacs = BAD medicine (sound-related?)
- From: "Stephen J. Turnbull" <turnbull@example.com>
- Date: Tue, 21 Jul 1998 16:55:17 +0900 (JST)
- Cc: tlug@example.com
- Content-Transfer-Encoding: 7bit
- Content-Type: text/plain; charset=us-ascii
- In-Reply-To: <199807210836.RAA00457@example.com>
- References: <199807210750.QAA04176@example.com><13748.15776.258635.849234@example.com><199807210836.RAA00457@example.com>
- Reply-To: tlug@example.com
- Sender: owner-tlug@example.com
>>>>> "Matt" == Matt Gushee <matt@example.com> writes: Matt> Stephen J. Turnbull writes: >> >>>>> "Matt" == Matt Gushee <matt@example.com> writes: >> Matt> As part of my never-ending quest to get my sound card Matt> working, I compiled a new 2.0.34 kernel yesterday. It seems Matt> to work, and I finally have sound (hallelujah!), but there's Matt> a serious catch. Twice yesterday, I booted up with the new Matt> kernel, started up XEmacs, and was typing away when -- POOF! Matt> The system was hung ... couldn't do anything with the Matt> keyboard or mouse. So I had to do a hard reset. Ouch. >> Version of XEmacs? Matt> Oh, that was dumb of me. 20.3, home-built w/ glibc 2.0.5 Matt> (now using 2.0.7). Urk. I don't recall the details and am deep in preparation for taking my ladies to California so don't want to grep the archive. (The only reason I'm reading tlug is so I can stuff it into gzipped archives.) But somewhere around 2.0.7 glibc started f**king with the call sequence in such a way that XEmacs's unexec procedure got hosed (glibc initializations were doing setjmp/longjmps as I recall - Arrrgh.) It may have been a bad interaction with egcs or early versions of gcc 2.8, too. If you can give any more details, you should try comp.emacs.xemacs with this one. I hadn't heard that this combination could hose an existing XEmacs so I could be wrong. Matt> I don't run telnetd. I suppose I could, if that would be a Matt> good test strategy. This tells you whether the system died or if it's "just" the console. -- University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Institute of Policy and Planning Sciences Tel/fax: +1 (298) 53-5091 -------------------------------------------------------------- Next Meeting: 8 August, Tokyo Station Yaesu central gate 12:30 featuring Linux on multiple platforms: i386, Sparc, PA-Risc, Amiga, SGI, Alpha, PalmPilot, ... Next Nomikai: September, 19:30 Tengu TokyoEkiMae 03-3275-3691 -------------------------------------------------------------- Sponsor: PHT, makers of TurboLinux http://www.pht.co.jp
- Follow-Ups:
- tlug: New Kernel + XEmacs = BAD medicine (sound-related?)
- From: Matt Gushee <matt@example.com>
- References:
- tlug: New Kernel + XEmacs = BAD medicine (sound-related?)
- From: Matt Gushee <matt@example.com>
- tlug: New Kernel + XEmacs = BAD medicine (sound-related?)
- From: "Stephen J. Turnbull" <turnbull@example.com>
- tlug: New Kernel + XEmacs = BAD medicine (sound-related?)
- From: Matt Gushee <matt@example.com>
Home | Main Index | Thread Index
- Prev by Date: tlug: New Kernel + XEmacs = BAD medicine (sound-related?)
- Next by Date: tlug: TLUG S/N - an empirical analysis
- Prev by thread: tlug: New Kernel + XEmacs = BAD medicine (sound-related?)
- Next by thread: tlug: New Kernel + XEmacs = BAD medicine (sound-related?)
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links