Menu
▾
▴
[coLinux-devel] [ colinux-Bugs-1643371 ] X11-common (testing) crashes basic debian without message
|
From: SourceForge.net <no...@so...> - 2007-05-11 15:34:59
|
Bugs item #1643371, was opened at 2007-01-24 11:25 Message generated for change (Comment added) made by henryn You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=1643371&group_id=98788 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: v0.7.x (release) >Status: Pending >Resolution: Fixed Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Henry N. (henryn) Summary: X11-common (testing) crashes basic debian without message Initial Comment: in short form, without update commands and sources.list changes: colinux 0.7.1, 1.1.2007, slirp, tap, 128 mb max. ram, 128 mb swap, several different basic debian disk images tried: apt-get dist-upgrade stable apt-get dist-upgrade testing apt-get install x11-common crash colinux version 0.6.4 works fine. ---------------------------------------------------------------------- >Comment By: Henry N. (henryn) Date: 2007-05-11 17:34 Message: Logged In: YES user_id=579204 Originator: NO In source of dmidecode seen, that it maps memory and reads BIOS informations. All accesses direct to memory are not usable and would crash the host. This snapshot was fixed to disallow mapping /dev/mem. The application would get a bus error now: http://www.henrynestler.com/colinux/testing/stable-0.7.1/20070511-dmidecode/ I'm never got this BSOD. It would be interesting, are this fixed for you? I mean for coLinux 0.7.1 with kernel 2.6.12 there. ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2007-05-10 23:26 Message: Logged In: YES user_id=579204 Originator: NO Yes, 'dmidecode' tryed to mmap the /dev/mem and reading from there, and this is the bad idea under coLinux. /dev/mem should blocked (mmap_kmem in drivers/char/mem.c) ---------------------------------------------------------------------- Comment By: Ryan Underwood (runderwo) Date: 2007-03-21 15:51 Message: Logged In: YES user_id=324742 Originator: NO Upgrading libx11-6 causes the same crash. ---------------------------------------------------------------------- Comment By: Jason L. Musgrove (jmusgrove) Date: 2007-03-08 23:13 Message: Logged In: YES user_id=771536 Originator: NO "laptop-detect" appears to be a shell script in http://ftp.debian.org/debian/pool/main/l/laptop-detect/laptop-detect_0.12.1_i386.deb, and, as far as I can tell, identical in content to "laptop-detect.sh" in the tar file. The script just checks a couple of nodes inside /proc (which do not exist, so can't be the issue) and calls the binary "dmidecode" which my money is on as the cause of the failure. Here's the kicker though; now I've upgraded to 0.8 snapshot, I can't get the script, or any component inside it, to cause the crash. ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2007-03-08 21:30 Message: Logged In: YES user_id=579204 Originator: NO Found a file http://ftp.debian.org/debian/pool/main/l/laptop-detect/laptop-detect_0.12.1.tar.gz There exist a "laptop-detect.sh", but not "laptop-detect" Is this the same? Is this the same you have? ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2007-03-08 21:18 Message: Logged In: YES user_id=579204 Originator: NO Very good. Please send me the Script /usr/sbin/laptop-detect (or a link where I can get it) and the complete parmeter list from preinstaller call. I would fix it, after see, what this script does. Think, it's an illegal access to bios memory or pci device... Henry ---------------------------------------------------------------------- Comment By: Jason L. Musgrove (jmusgrove) Date: 2007-03-08 10:58 Message: Logged In: YES user_id=771536 Originator: NO I have replicated this issue with 0.7.1 with Debian unstable (128Mb RAM, 256Mb swap on cobd1, pcap-bridge on eth0, tap on eth1). My experience is that after the line "Preconfiguring packages", the colinux-daemon exits without any apparent error (nothing notable picked up by the colinux-debug-daemon either) . I believe the problem to lie in the preinst script for this package (due to the fact that it doesn't do anything after Preconfiguring) and taken the liberty of examining it - there's a call to "laptop-detect" which, when run manually, also causes colinux to exit in the same manner. To this end, I have removed the file /usr/sbin/laptop-detect (the preconfigure script checks it's presence before executing it, so there shouldn't be a dependency error for this particular script) and tried installing the package again - success. ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2007-01-30 21:09 Message: Logged In: YES user_id=579204 Originator: NO What is crashing? Complete Windows, one of colinux-*.exe daemons, or the colinux-daemon.exe self? If windows does continue running, then try to run debugging, before you start "apt-get install x11-common" on a separate windows prompt: colinux-debug-daemon.exe -d -p -s prints=31,misc=31 -f debug.xml After your crash, stop the debugging with CTRL-C and view in the debug.xml near the end. Is there a Kernel oops? Or any more informations? Can you separate the programs in x11-common, what does the crash? (I'm no debian user) Perhaps you can unpack the packet into /tmp and run any of the programs from command line? Generaly: Be shure, that you you don't install a X11 server or a program with direct hardware access, for sample a hardware detection program, that tries to detect your video card. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2007-01-30 20:49 Message: Logged In: NO colinux 0.6.4 does NOT work fine: exactly same procedures used. colinux 0.6.3 DOES work fine. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=1643371&group_id=98788 |