Menu

Debian distro upgrade crashes coLinux?

Help
2007-04-27
2013-05-09
  • Ricky Ng-Adam

    Ricky Ng-Adam - 2007-04-27

    Hello!

    On:

    -Debian GNU/Linux 4.0
    -Linux colinux 2.6.11-co-0.6.3-rc4 #1 Sun Jan 15 05:48:14 UTC 2006 i686 GNU/Linux
    -On top of Win XP sp2

    I started with a apt-get install dist-upgrade. coLinux crashed while installing xcursor-themes. Now, any call to apt-get result in:

    colinux:~# apt-get install
    E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem.

    If I try this:

    colinux:~# dpkg --configure -a --debug=2000
    Setting up xcursor-themes (1.0.1-5) ...

    I immediately get on the console...

    Monitor0: Broken pipe
    Monitor0: Detached

    Anyone else has seen this problem?

    Thanks,

    Ricky

     
    • Henry N.

      Henry N. - 2007-05-11

      Run the debug-daemon.exe, before you run these commands.
      I'm afraid, you got an kernel panic and colinux was shortly closed, on the console you will only see the broken pipe.  Kernel panic are ofen on memory size limits.  Incrase the size of swapfile.

      Debugger for 0.6.4 use the same parameters as in 0.8.0, you should get the example and more from here:
      http://www.henrynestler.com/colinux/source/0.8.0-doc/debugging.txt

       
      • Neil Grant

        Neil Grant - 2007-12-24

        I am experiencing the same problem.
        I tried to record the details of the crash "colinux-debug-daemon.exe -d -p -s prints=255,misc=255 > msg.log" but not sure if I have captured the relevant facilities.

        uname -a : Linux colinux 2.6.12-co-0.7.1 #1 Sun Dec 31 20:25:16 UTC 2006 i686 GNU/Linux
        debian image from sf.net - Debian-3.0r2.ext3-mit-backports.1gb.bz2 

          <log  module="colinux-driver" file="src/colinux/kernel/monitor.c" timestamp="00000450.91052715  " local_index="29842" facility="2" function="callback_return_messages" line="333" level="12" driver_index="29906">
        <string>sending messages to linux (0 bytes)
        </string>
        </log>
          <log  module="colinux-daemon" file="src/colinux/os/winnt/user/misc.c" timestamp="00000450.91054557  " local_index="39" facility="3" function="co_terminal_printv" line="37" level="11" driver_index="29907">
        <string>prints "colinux: Linux VM terminated"
        </string>
        </log>
          <log  module="colinux-daemon" file="src/colinux/os/winnt/user/misc.c" timestamp="00000450.91054640  " local_index="40" facility="3" function="co_terminal_printv" line="37" level="11" driver_index="29908">
        <string>prints "colinux: BUG at mm/rmap.c:493"
        </string>
        </log>
          <log  module="colinux-daemon" file="src/colinux/user/daemon.c" timestamp="00000450.91054819  " local_index="41" facility="0" function="co_daemon_end_monitor" line="849" level="10" driver_index="29909">
        <string>shutting down
        </string>
        </log>

         
    • Henry N.

      Henry N. - 2008-01-08

      The line "colinux: BUG at mm/rmap.c:493" is interesting. But it is very old binary to trace it now.

      Typicaly candidate for this bug was the "dmidecode" or "laptopmode" in some setup scripts for Xserver and tools. This known bug was fixed 2007-07-12 (SVN revision 651 for coLinux 0.7.1), see details in Bug #1643371:
      http://sourceforge.net/tracker/?func=detail&atid=622063&aid=1643371&group_id=98788

      In build Dec 31 2006, used by Neil, this bug was not fixed. You should use the released version
      Release: 0.7.1, Kernel: 2.6.12, Build date: 14-Jul-2007

      If that not helps, please give the recent release candidate 0.7.2 from http://www.colinux.org/snapshots/ a try.

       
    • Ion

      Ion - 2008-01-08

      The same thing happened to me, for the same package/same version, and it was in 2006! ;o)

      I thought I could retrace what I did to fix it, but no, I can't find the log with the info... if I recall correctly, I just repeatedly tried to pass the "dpkg --configure -a" and it finally worked, like 3 days later!

      One thing I find but is incomplete, I CDed to "/var/cache/apt/archives/" and passed "dpkg -D022 --configure -a"; but since that log is incompleted, I cannot say if that fixed it! The following log - 3 days later! - contains the info for an "apt-get update + apt-get dist-upgrade", so everything was back to normal...

      I hope this could help and was not for nothing!

       

Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.