colinux-devel — Cooperative Linux development mailing list

Re: [coLinux-devel] coLinux compiling & signing

[Mike F. <vap...@gm...>]

On Wed, Nov 11, 2009 at 16:20, Henry Nestler wrote:
> Mike Frysinger wrote:
>> so if there is interest in me handling the signing steps, we should be
>> able to get this integrated into the release process fairly easy.  the
>> steps would be:
>>  - whoever builds the coLinux release also runs `inf2cat` on tap
>> driver (netdriver/)
>
> Can I (or you) run inf2cat without to have the build source? So, directly
> from binary? I ask, because I don't have the old build environment any more.
> It's truely old from 2006.

the only thing inf2cat needs is exactly the same thing that end users
need.  so the .inf file and any files the .inf file refers to.  that
means if you really wanted to, any previous release could be
retroactively signed with just the released binaries on the sf
download page.  this step doesnt require any certs as it just collects
file hashes in the .cat for people to sign later on.

>>  - send an archive of all binaries over to me (i.e. the stuff in
>> coLinux-0.7.5.exe)
>>  - i'll sign all the binaries and send it back
>
> Many thanks for your offer. It would be nice to have the tap driver signed.
> This driver is truely old, but we no need to change it for long time. So,
> signing the TAP would be a very cool step. We should start with that for the
> 0.7.6-rc2

all the programs can be signed if you wanted, not just the drivers.
but maybe we'll stick to just the drivers so as to keep things simple.
 if the TAP driver is rarely recompiled, then i would have to sign it
less often and you wouldnt have to rely on me as much.

> For the release build: I have no problem to run a final Windows script. I
> also need Windows for testing. ;-) Only have problem to setup the
> environment every time.

if the WDK allowed redistribution, i'd put together a small zip for
people to use, but it doesnt.  when you install the current WDK 7.0.0,
the only thing you need is the stuff under ...\bin\selfsign\.  which
is like 400KB.  so if you create a small zip of that dir for personal
use (it'll be just the inf2cat.exe and supplemental dll/xml files it
uses at runtime), you should be able to unpack that onto any Windows
machine and have it work fine.

as for the signing, i think you only need the small signtool.exe
program in ...\bin\x86\ as this largely uses dlls installed with
Windows itself, and it is native code rather than written in .NET.

this is just my understanding of things ... i havent rigorously tested
these shortcuts, so YMMV.

>>   - this step can be done under Windows or via Mono (and thus under Linux)
>
> Would this also run under Wine?

i'm not sure.  some of these programs require .NET (so you'd have to
install the .NET runtime under Wine), and some require wintrust.dll
which Wine has a mostly stub implementation for.  i guess on your
personal system, you could copy it from Windows' system32 dir and then
configure your Wine to use that rather than its internal version.
this is the point where i said screw it and just went with Mono ;),
but if all these things worked, you might be able to get signtool and
inf2cat working under Wine.
-mike

Re: [coLinux-devel] coLinux compiling & signing

[Henry N. <hen...@ar...>]

Hello Mike,

first: Thank for your words in the Wiki!

Mike Frysinger wrote:
> some questions about the compiling&  driver signing process.
>   - is coLinux compiled completely via mingw (linux.sys included) ?
>    

Yes.

>   - is the TAP driver compiled from source, or is it taken from openvpn
> and only the .inf file is customized ?
>
>   - if it's compiled, is it done via mingw ?
>    

We have changed source and the INF. Than it was build with Windows DDK.
The source exist in SVN. You can get it with:

svn checkout 
http://colinux.svn.sourceforge.net/svnroot/colinux/branches/stable/src/colinux/os/winnt/kernel/tap-win32/ 
colinux-tap-win32

Here is a live view:
http://colinux.svn.sourceforge.net/viewvc/colinux/branches/devel/src/colinux/os/winnt/kernel/tap-win32/


> i filled out the 64bit wiki page on the steps needed to get things
> going all by yourself.  unfortunately, i'm not aware of a 32bit OS
> that requires driver signing, so i cant test/answer the question wrt
> linux.sys handling.  maybe signing just the linux.sys is sufficient ?
> if a 64bit coLinux existed, i could test that pretty quickly (since i
> have a 64bit Win7 install) ...
>
> so if there is interest in me handling the signing steps, we should be
> able to get this integrated into the release process fairly easy.  the
> steps would be:
>   - whoever builds the coLinux release also runs `inf2cat` on tap
> driver (netdriver/)
>    

Can I (or you) run inf2cat without to have the build source? So, 
directly from binary? I ask, because I don't have the old build 
environment any more. It's truely old from 2006.

>    - this step currently requires Windows ... so i could take care of
> it if it's too much hassle for the release guy, but i'd prefer to not
> ...
>   - send an archive of all binaries over to me (i.e. the stuff in
> coLinux-0.7.5.exe)
>   - i'll sign all the binaries and send it back
>
>    

Many thanks for your offer. It would be nice to have the tap driver 
signed. This driver is truely old, but we no need to change it for long 
time. So, signing the TAP would be a very cool step. We should start 
with that for the 0.7.6-rc2

For the release build: I have no problem to run a final Windows script. 
I also need Windows for testing. ;-) Only have problem to setup the 
environment every time.

>    - this step can be done under Windows or via Mono (and thus under Linux)
>    

Would this also run under Wine?

-- 
Henry N.

[coLinux-devel] coLinux compiling & signing

[Mike F. <vap...@gm...>]

some questions about the compiling & driver signing process.
 - is coLinux compiled completely via mingw (linux.sys included) ?
 - is the TAP driver compiled from source, or is it taken from openvpn
and only the .inf file is customized ?
 - if it's compiled, is it done via mingw ?

now, a little background from my side.  my group in ADI creates a
coLinux installer based on the official coLinux releases that
automates a lot of the setup steps.  basically i take the latest
stable release and source, add a hook to the initrd, and tweak the
nsis install script.  then during the install, the initrd hook is used
to create the initial rootfs and populate it with a Debian install,
and a simple network (slirp/tap) between the host and coLinux is
created.  we're not recompiling any of the released binaries (i use 7z
to unpack the release executable).  this is all done because many of
our users do not want to or cannot dual boot a real Linux system for
our development tools.  coLinux helps fill this gap very nicely.

all of our work is available from a public svn:
http://blackfin.uclinux.org/gf/project/bfin-colinux/scmsvn/trunk/

in light of the signing requirements of newer operating systems, ive
had to learn the driver signing process myself to work with some of
our USB open source drivers.  since we rely on coLinux for our Windows
users, we're interested in keeping the install process smooth there
too.  so you guys can either drop ~$500 USD on getting your own
authenticode certs to sign the programs/drivers, or i can take care of
signing things.  i'm going to be doing it anyways for our installers,
but i figured i could save you guys a bit of hassle and money.

i filled out the 64bit wiki page on the steps needed to get things
going all by yourself.  unfortunately, i'm not aware of a 32bit OS
that requires driver signing, so i cant test/answer the question wrt
linux.sys handling.  maybe signing just the linux.sys is sufficient ?
if a 64bit coLinux existed, i could test that pretty quickly (since i
have a 64bit Win7 install) ...

so if there is interest in me handling the signing steps, we should be
able to get this integrated into the release process fairly easy.  the
steps would be:
 - whoever builds the coLinux release also runs `inf2cat` on tap
driver (netdriver/)
  - this step currently requires Windows ... so i could take care of
it if it's too much hassle for the release guy, but i'd prefer to not
...
 - send an archive of all binaries over to me (i.e. the stuff in
coLinux-0.7.5.exe)
 - i'll sign all the binaries and send it back
  - this step can be done under Windows or via Mono (and thus under Linux)
the hashes of the code itself will be unchanged (the Windows PE format
allows for embedding of signatures in the binary metadata itself, but
outside of the code/data sections), so you can verify i havent gone
and injected malicious code/backdoors/etc...  and if any modifications
to the binaries are made after signing, the signature will be rendered
invalid (since it signs the PE content), and i dont have to worry
about my signatures being associated with malicious stuff after ive
tested & signed things.
-mike

[coLinux-devel] [ colinux-Bugs-2895531 ] mkfs.ext3 freezes on scsi disks

[SourceForge.net <no...@so...>]

Bugs item #2895531, was opened at 2009-11-10 23:34
Message generated for change (Comment added) made by germansalvador
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2895531&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: Crash / BSOD
Group: v0.7.x (release)
Status: Open
Resolution: Accepted
Priority: 5
Private: No
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: mkfs.ext3 freezes on scsi disks

Initial Comment:
I have tryed to make a mkfs.ext3 on /dev/sda1, wich is the only partition crreated on a scsi disk, backed by a plain file. 
I am using 0.7.5 with the debian lenny root filesystem image. The scsi parameter I am adding to the conf file is just
    scsi0=disk,j:\test.bin   (test.bin is a 8 GB empty file)

What happens is that mkfs starts quickly, but soon slows down, and can even freeze colinux. Sometimes it crashes windows also.
This also happened on the latest devel snapshot, and also when the scsi backing is a raw device.

Tested con Windows XP SP2

----------------------------------------------------------------------

Comment By: German Salvador (germansalvador)
Date: 2009-11-11 09:48

Message:
I have tried with the 20091110 snapshot, downloaded from
http://www.henrynestler.com/colinux/testing/stable-0.7.6/20091110-Snapshot/stable-coLinux-20091110.exe,
and the bug is still there.

About the memory, I tried with several options, but it makes no
difference. Now I'm trying with the default debian-lenny.conf, wich has the
mem line commented.



----------------------------------------------------------------------

Comment By: Henry N. (henryn)
Date: 2009-11-11 01:51

Message:
Ok, have seen it with 0.7.6-rc1
scsi0=disk,j:\test.bin,8192
Created primary partition on /dev/sda with fdisk
mkfs.ext3 /dev/sda1
...
First coLinux stops doing, no keyboard reaction, The host is idle. Some
seconds later, the host is no accessible. The mouse can move, and
window-frames (GUI) can move with it. But, can not start taskmanager, and
all of the windows-explorer hangs. It seams, that the complete filesystem
is locked.

----------------------------------------------------------------------

Comment By: Henry N. (henryn)
Date: 2009-11-11 00:22

Message:
Please try 0.7.6-rc1 from todays build (with kernel 2.6.22.18), or the
devel build after 2009-11-05 with kernel 2.6.25.20 - Because a bug #2890857
inside scsi driver was fixed last days.

How many memory you have configured or used inside Linux?
I ask, because we have fixed an other bug #2893343 this weekend.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2895531&group_id=98788

[coLinux-devel] autobuild org.colinux.devel 20091110 22:04:12

[coLinux a. <col...@he...>]

The autobuild system has detected a new revision in the source repository.
Review last changed from changelog.txt, also attached in mail.

Download the compiled version:
http://www.henrynestler.com/colinux/autobuild/devel-20091110/

 colinux-0.8.0-20091110.src.tgz  (834404 Bytes)
 daemons-0.8.0-20091110.dbg.zip  (590939 Bytes)
 daemons-0.8.0-20091110.zip  (477785 Bytes)

Note, the autobuild compilation does not include an installer.
Remember to reload the driver with these commands:

	colinux-daemon.exe --remove-driver
	colinux-daemon.exe --install-driver

The vmlinux and modules are up to date. Please use last version from
http://www.henrynestler.com/colinux/autobuild/devel-20091108/

The autobuild compilations are not official releases of Cooperative Linux
software.  There is no warranty that any autobuild version is stable.  If
use this autobuild version, please give us feedback of your experience.

Job runs on machine with 64 bit version of gcc 4.1.2.
A service from http://gcc.gnu.org/wiki/CompileFarm

-- 
Lots of fun with newest version,
Henry Nestler
------------------------------------------------------------------------
r1290 | henryn | 2009-11-10 22:04:12 +0000 (Tue, 10 Nov 2009) | 2 lines
Changed paths:
   M /branches/devel/bin/build-cross.sh

* Don't search for `gcc` without prefix, if --gcc-guest-build was configured.
(fixed by Peter Kuznetsov)
------------------------------------------------------------------------

[coLinux-devel] [ colinux-Bugs-2895531 ] mkfs.ext3 freezes on scsi disks

[SourceForge.net <no...@so...>]

Bugs item #2895531, was opened at 2009-11-10 23:34
Message generated for change (Comment added) made by henryn
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2895531&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: Crash / BSOD
Group: v0.7.x (release)
Status: Open
>Resolution: Accepted
Priority: 5
Private: No
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: mkfs.ext3 freezes on scsi disks

Initial Comment:
I have tryed to make a mkfs.ext3 on /dev/sda1, wich is the only partition crreated on a scsi disk, backed by a plain file. 
I am using 0.7.5 with the debian lenny root filesystem image. The scsi parameter I am adding to the conf file is just
    scsi0=disk,j:\test.bin   (test.bin is a 8 GB empty file)

What happens is that mkfs starts quickly, but soon slows down, and can even freeze colinux. Sometimes it crashes windows also.
This also happened on the latest devel snapshot, and also when the scsi backing is a raw device.

Tested con Windows XP SP2

----------------------------------------------------------------------

>Comment By: Henry N. (henryn)
Date: 2009-11-11 01:51

Message:
Ok, have seen it with 0.7.6-rc1
scsi0=disk,j:\test.bin,8192
Created primary partition on /dev/sda with fdisk
mkfs.ext3 /dev/sda1
...
First coLinux stops doing, no keyboard reaction, The host is idle. Some
seconds later, the host is no accessible. The mouse can move, and
window-frames (GUI) can move with it. But, can not start taskmanager, and
all of the windows-explorer hangs. It seams, that the complete filesystem
is locked.

----------------------------------------------------------------------

Comment By: Henry N. (henryn)
Date: 2009-11-11 00:22

Message:
Please try 0.7.6-rc1 from todays build (with kernel 2.6.22.18), or the
devel build after 2009-11-05 with kernel 2.6.25.20 - Because a bug #2890857
inside scsi driver was fixed last days.

How many memory you have configured or used inside Linux?
I ask, because we have fixed an other bug #2893343 this weekend.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2895531&group_id=98788

[coLinux-devel] [ colinux-Bugs-2895531 ] mkfs.ext3 freezes on scsi disks

[SourceForge.net <no...@so...>]

Bugs item #2895531, was opened at 2009-11-10 23:34
Message generated for change (Comment added) made by henryn
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2895531&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: Crash / BSOD
Group: v0.7.x (release)
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: mkfs.ext3 freezes on scsi disks

Initial Comment:
I have tryed to make a mkfs.ext3 on /dev/sda1, wich is the only partition crreated on a scsi disk, backed by a plain file. 
I am using 0.7.5 with the debian lenny root filesystem image. The scsi parameter I am adding to the conf file is just
    scsi0=disk,j:\test.bin   (test.bin is a 8 GB empty file)

What happens is that mkfs starts quickly, but soon slows down, and can even freeze colinux. Sometimes it crashes windows also.
This also happened on the latest devel snapshot, and also when the scsi backing is a raw device.

Tested con Windows XP SP2

----------------------------------------------------------------------

>Comment By: Henry N. (henryn)
Date: 2009-11-11 00:22

Message:
Please try 0.7.6-rc1 from todays build (with kernel 2.6.22.18), or the
devel build after 2009-11-05 with kernel 2.6.25.20 - Because a bug #2890857
inside scsi driver was fixed last days.

How many memory you have configured or used inside Linux?
I ask, because we have fixed an other bug #2893343 this weekend.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2895531&group_id=98788

[coLinux-devel] [ colinux-Bugs-2893343 ] host BSOD on with 20091105

[SourceForge.net <no...@so...>]

Bugs item #2893343, was opened at 2009-11-06 16:25
Message generated for change (Settings changed) made by henryn
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2893343&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: Crash / BSOD
Group: v0.8.x (devel)
>Status: Closed
Resolution: Fixed
>Priority: 7
Private: No
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Henry N. (henryn)
Summary: host BSOD on with 20091105

Initial Comment:
with snapshot 0.8.0-20091105, the host got BSOD. no problem with 0.8.0-20090905.
downloaded from http://www.colinux.org/snapshots/
os: windows xp sp3 with all hotfix installed

i have retried many time, double check file permission, no luck

----------------------------------------------------------------------

>Comment By: Henry N. (henryn)
Date: 2009-11-11 00:16

Message:
Now, also fixed for the stable release 0.7.6-rc1 and committed to SVN
release r1291.
Download available from Snapshot page.


----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2009-11-10 17:29

Message:
no crash with ram=any value. looks like it's fixed. thanks for your great
work

----------------------------------------------------------------------

Comment By: Henry N. (henryn)
Date: 2009-11-08 13:51

Message:
Real memory limit was 984 MB all times.
With value of 1000 MB "vmalloc" and "lowmem" overlaps the "colinux" shared
host memory and would crash, if Linux would use all of this memory later.

Here is a virtual memory layout with adjusted pointers for vmalloc:
    fixmap  : 0xffffc000 - 0xfffff000   (  12 kB)
    colinux : 0xfe800000 - 0xffc00000   (  20 MB)
    vmalloc : 0xfe000000 - 0xfe7fe000   (   7 MB)
    lowmem  : 0xc0000000 - 0xfd800000   ( 984 MB)

Fixed in SVN revision r1285.
New snapshot available.



----------------------------------------------------------------------

Comment By: Henry N. (henryn)
Date: 2009-11-07 15:22

Message:
Thanks. Think, the new kernel uses more "reserved" memory.
I have successfully tested up to mem=984 with and without PAE in Windows
boot.ini.
Is 984M also working in your environment? Than I would change the limit to
that value.


----------------------------------------------------------------------

Comment By: Xuefer (xuefer)
Date: 2009-11-07 14:09

Message:
btw, no crash if i configure as:

mem=1024
init=/bin/sh

looks like there's some memory overrun colinux compiled with new kernel
while 1024M ram is in use

----------------------------------------------------------------------

Comment By: Xuefer (xuefer)
Date: 2009-11-07 14:06

Message:
reproduced only with big ram configured for colinux
===================
ram=960 -> no problem
ram=992 (960+32) -> guest crash
ram=1024 -> host crash

===================
colinux-daemon output:
Cooperative Linux Daemon, 0.8.0
Daemon compiled on Thu Nov  5 23:08:04 2009

using 'vmlinux' as kernel image
configuring 992 MB of virtual RAM
selected cobd0 for sda2, mapping to '\Device\Harddisk0\Partition2'
selected cobd1 for sda3, mapping to '\Device\Harddisk0\Partition3'
selected cobd2 for sda5, mapping to '\Device\Harddisk0\Partition4'
configured NDIS bridge at 'coLinux' device as eth1
MAC address: 00:ff:4f:0d:e7:c0
mapping cofs0 to \DosDevices\c:\app\system\colinux\
mapping cofs1 to \DosDevices\c:\
mapping cofs2 to \DosDevices\d:\
mapping cofs3 to \DosDevices\i:\
mapping cofs4 to \DosDevices\g:\
kernel boot parameters: 'video0=4 root=/dev/sda3 bootlevel=c.boot
softlevel=c.default'
creating monitor
PID: 2300
colinux: launching console
executing: colinux-console-fltk -a 2300
launching daemon for conet1
executing: colinux-ndis-net-daemon -i 2300 -u 1 -n "coLinux" -mac
00:ff:4f:0d:e7:c0 -p 1
colinux: booting
Ndis bridge probe on "1394 连接"
Ndis bridge probe on "本地连接"
Ndis bridge probe on "WAN"
Ndis bridge probe on "Bluetooth"
Ndis bridge probe on "VirtualBox Host-Only Network"
Ndis bridge probe on "VirtualBox Host-Only Network"
Ndis bridge probe on "VirtualBox Host-Only Network"
Ndis bridge probe on "VirtualBox Host-Only Network"
Ndis bridge probe on "coLinux"
conet-ndis-daemon: Bridge on: coLinux
Linux version 2.6.25.20-co-0.8.0 (hn@hn-dt) (gcc version 4.2.1 (SUSE
Linux)) #1 PREEMPT Thu Nov 5 23:06:10 CET 2009
992MB LOWMEM available.
Entering add_active_range(0, 0, 253952) 0 entries of 256 used
Zone PFN ranges:
  Normal          0 ->   253952
Movable zone start PFN for each node
early_node_map[1] active PFN ranges
    0:        0 ->   253952
On node 0 totalpages: 253952
  Normal zone: 1984 pages used for memmap
  Normal zone: 0 pages reserved
  Normal zone: 251968 pages, LIFO batch:31
  Movable zone: 0 pages used for memmap
Built 1 zonelists in Zone order, mobility grouping on.  Total pages:
251968
Kernel command line: video0=4 root=/dev/sda3 bootlevel=c.boot
softlevel=c.default
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
Setting proxy interrupt vectors
PID hash table entries: 4096 (order: 12, 16384 bytes)
Console: colour CoCON 80x25
console [tty0] enabled
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Memory: 1002624k/1015808k available (2029k kernel code, 0k reserved, 618k
data, 156k init, 0k highmem)
      .init : 0xcCPA: page pool initialized 1 of 1 pages preallocated
Calibrating delay loop... 14522.77 BogoMIPS (lpj=72613888)
Security Framework initialized
SELinux:  Disabled at boot.
Capability LSM initialized
Mount-cache hash table entries: 512
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 512K (64 bytes/line)
Compat vDSO mapped to ffffe000.
CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 3800+ stepping 02
Checking 'hlt' instruction... OK.
Freeing SMP alternatives: 0k freed
net_namespace: 536 bytes
NET: Registered protocol family 16
SCSI subsystem initialized
PCI: Probing PCI hardware
PCI: Probing PCI hardware (bus 00)
NET: Registered protocol family 2
IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
TCP bind hash table entries: 65536 (order: 6, 262144 bytes)
TCP: Hash tables configured (established 131072 bind 65536)
TCP reno registered
audit: initializing netlink socket (disabled)
colinux: Linux VM terminated
colinux: Kernel panic: Attempted to kill init!
shutting down
Pipe broken, exiting
daemon cleanup
rc=0b14b800 exit=0

===================

kernel output: (no idea how to paste kernel output as text)
see http://paste.ubuntu.com.cn/i46371

cannot attach a screenshot file here as i didn't open this bug

----------------------------------------------------------------------

Comment By: Henry N. (henryn)
Date: 2009-11-06 21:43

Message:
Do clean upgrade steps by step:
* Download archive "daemons-0.8.0-20091105.zip" form:
http://www.henrynestler.com/colinux/testing/devel-0.8.0/20091105-Snapshot/packages/
* Unpack all the files into new directory, for example to
c:\coLinux-2.6.25
* Copy your colinux config file or your BAT file from old installation
into the new directory. Edit the new config- or bat- file and add the full
path for your image files (cobd, scsi or hda). - If you not have used full
path names before.
* Remove or comment out the "initrd=initrd.gz" from config, and save the
config.
* Stop all running colinux
* Open command prompt on old installation directory
* Remove the driver
  colinux-daemon --remove-driver
* Check, that the driver is truely removed:
  colinux-daemon --status-driver
* Reboot your windows now!
* Open command prompt on the new directory and perform the manual
install:
  colinux-daemon --install-driver
* Reboot your Windows now!
  (This step is need, if the start would crash at next step.)
* Run your new colinux versioon from new directory.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2893343&group_id=98788

[coLinux-devel] [ colinux-Bugs-2895531 ] mkfs.ext3 freezes on scsi disks

[SourceForge.net <no...@so...>]

Bugs item #2895531, was opened at 2009-11-10 22:34
Message generated for change (Tracker Item Submitted) made by nobody
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2895531&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: Crash / BSOD
Group: v0.7.x (release)
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: mkfs.ext3 freezes on scsi disks

Initial Comment:
I have tryed to make a mkfs.ext3 on /dev/sda1, wich is the only partition crreated on a scsi disk, backed by a plain file. 
I am using 0.7.5 with the debian lenny root filesystem image. The scsi parameter I am adding to the conf file is just
    scsi0=disk,j:\test.bin   (test.bin is a 8 GB empty file)

What happens is that mkfs starts quickly, but soon slows down, and can even freeze colinux. Sometimes it crashes windows also.
This also happened on the latest devel snapshot, and also when the scsi backing is a raw device.

Tested con Windows XP SP2

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2895531&group_id=98788

[coLinux-devel] [ colinux-Bugs-2893343 ] host BSOD on with 20091105

[SourceForge.net <no...@so...>]

Bugs item #2893343, was opened at 2009-11-06 15:25
Message generated for change (Comment added) made by nobody
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2893343&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: Crash / BSOD
Group: v0.8.x (devel)
Status: Open
Resolution: Fixed
Priority: 5
Private: No
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Henry N. (henryn)
Summary: host BSOD on with 20091105

Initial Comment:
with snapshot 0.8.0-20091105, the host got BSOD. no problem with 0.8.0-20090905.
downloaded from http://www.colinux.org/snapshots/
os: windows xp sp3 with all hotfix installed

i have retried many time, double check file permission, no luck

----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2009-11-10 16:29

Message:
no crash with ram=any value. looks like it's fixed. thanks for your great
work

----------------------------------------------------------------------

Comment By: Henry N. (henryn)
Date: 2009-11-08 12:51

Message:
Real memory limit was 984 MB all times.
With value of 1000 MB "vmalloc" and "lowmem" overlaps the "colinux" shared
host memory and would crash, if Linux would use all of this memory later.

Here is a virtual memory layout with adjusted pointers for vmalloc:
    fixmap  : 0xffffc000 - 0xfffff000   (  12 kB)
    colinux : 0xfe800000 - 0xffc00000   (  20 MB)
    vmalloc : 0xfe000000 - 0xfe7fe000   (   7 MB)
    lowmem  : 0xc0000000 - 0xfd800000   ( 984 MB)

Fixed in SVN revision r1285.
New snapshot available.



----------------------------------------------------------------------

Comment By: Henry N. (henryn)
Date: 2009-11-07 14:22

Message:
Thanks. Think, the new kernel uses more "reserved" memory.
I have successfully tested up to mem=984 with and without PAE in Windows
boot.ini.
Is 984M also working in your environment? Than I would change the limit to
that value.


----------------------------------------------------------------------

Comment By: Xuefer (xuefer)
Date: 2009-11-07 13:09

Message:
btw, no crash if i configure as:

mem=1024
init=/bin/sh

looks like there's some memory overrun colinux compiled with new kernel
while 1024M ram is in use

----------------------------------------------------------------------

Comment By: Xuefer (xuefer)
Date: 2009-11-07 13:06

Message:
reproduced only with big ram configured for colinux
===================
ram=960 -> no problem
ram=992 (960+32) -> guest crash
ram=1024 -> host crash

===================
colinux-daemon output:
Cooperative Linux Daemon, 0.8.0
Daemon compiled on Thu Nov  5 23:08:04 2009

using 'vmlinux' as kernel image
configuring 992 MB of virtual RAM
selected cobd0 for sda2, mapping to '\Device\Harddisk0\Partition2'
selected cobd1 for sda3, mapping to '\Device\Harddisk0\Partition3'
selected cobd2 for sda5, mapping to '\Device\Harddisk0\Partition4'
configured NDIS bridge at 'coLinux' device as eth1
MAC address: 00:ff:4f:0d:e7:c0
mapping cofs0 to \DosDevices\c:\app\system\colinux\
mapping cofs1 to \DosDevices\c:\
mapping cofs2 to \DosDevices\d:\
mapping cofs3 to \DosDevices\i:\
mapping cofs4 to \DosDevices\g:\
kernel boot parameters: 'video0=4 root=/dev/sda3 bootlevel=c.boot
softlevel=c.default'
creating monitor
PID: 2300
colinux: launching console
executing: colinux-console-fltk -a 2300
launching daemon for conet1
executing: colinux-ndis-net-daemon -i 2300 -u 1 -n "coLinux" -mac
00:ff:4f:0d:e7:c0 -p 1
colinux: booting
Ndis bridge probe on "1394 连接"
Ndis bridge probe on "本地连接"
Ndis bridge probe on "WAN"
Ndis bridge probe on "Bluetooth"
Ndis bridge probe on "VirtualBox Host-Only Network"
Ndis bridge probe on "VirtualBox Host-Only Network"
Ndis bridge probe on "VirtualBox Host-Only Network"
Ndis bridge probe on "VirtualBox Host-Only Network"
Ndis bridge probe on "coLinux"
conet-ndis-daemon: Bridge on: coLinux
Linux version 2.6.25.20-co-0.8.0 (hn@hn-dt) (gcc version 4.2.1 (SUSE
Linux)) #1 PREEMPT Thu Nov 5 23:06:10 CET 2009
992MB LOWMEM available.
Entering add_active_range(0, 0, 253952) 0 entries of 256 used
Zone PFN ranges:
  Normal          0 ->   253952
Movable zone start PFN for each node
early_node_map[1] active PFN ranges
    0:        0 ->   253952
On node 0 totalpages: 253952
  Normal zone: 1984 pages used for memmap
  Normal zone: 0 pages reserved
  Normal zone: 251968 pages, LIFO batch:31
  Movable zone: 0 pages used for memmap
Built 1 zonelists in Zone order, mobility grouping on.  Total pages:
251968
Kernel command line: video0=4 root=/dev/sda3 bootlevel=c.boot
softlevel=c.default
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
Setting proxy interrupt vectors
PID hash table entries: 4096 (order: 12, 16384 bytes)
Console: colour CoCON 80x25
console [tty0] enabled
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Memory: 1002624k/1015808k available (2029k kernel code, 0k reserved, 618k
data, 156k init, 0k highmem)
      .init : 0xcCPA: page pool initialized 1 of 1 pages preallocated
Calibrating delay loop... 14522.77 BogoMIPS (lpj=72613888)
Security Framework initialized
SELinux:  Disabled at boot.
Capability LSM initialized
Mount-cache hash table entries: 512
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 512K (64 bytes/line)
Compat vDSO mapped to ffffe000.
CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 3800+ stepping 02
Checking 'hlt' instruction... OK.
Freeing SMP alternatives: 0k freed
net_namespace: 536 bytes
NET: Registered protocol family 16
SCSI subsystem initialized
PCI: Probing PCI hardware
PCI: Probing PCI hardware (bus 00)
NET: Registered protocol family 2
IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
TCP bind hash table entries: 65536 (order: 6, 262144 bytes)
TCP: Hash tables configured (established 131072 bind 65536)
TCP reno registered
audit: initializing netlink socket (disabled)
colinux: Linux VM terminated
colinux: Kernel panic: Attempted to kill init!
shutting down
Pipe broken, exiting
daemon cleanup
rc=0b14b800 exit=0

===================

kernel output: (no idea how to paste kernel output as text)
see http://paste.ubuntu.com.cn/i46371

cannot attach a screenshot file here as i didn't open this bug

----------------------------------------------------------------------

Comment By: Henry N. (henryn)
Date: 2009-11-06 20:43

Message:
Do clean upgrade steps by step:
* Download archive "daemons-0.8.0-20091105.zip" form:
http://www.henrynestler.com/colinux/testing/devel-0.8.0/20091105-Snapshot/packages/
* Unpack all the files into new directory, for example to
c:\coLinux-2.6.25
* Copy your colinux config file or your BAT file from old installation
into the new directory. Edit the new config- or bat- file and add the full
path for your image files (cobd, scsi or hda). - If you not have used full
path names before.
* Remove or comment out the "initrd=initrd.gz" from config, and save the
config.
* Stop all running colinux
* Open command prompt on old installation directory
* Remove the driver
  colinux-daemon --remove-driver
* Check, that the driver is truely removed:
  colinux-daemon --status-driver
* Reboot your windows now!
* Open command prompt on the new directory and perform the manual
install:
  colinux-daemon --install-driver
* Reboot your Windows now!
  (This step is need, if the start would crash at next step.)
* Run your new colinux versioon from new directory.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2893343&group_id=98788

[coLinux-devel] [ colinux-Bugs-2893343 ] host BSOD on with 20091105

[SourceForge.net <no...@so...>]

Bugs item #2893343, was opened at 2009-11-06 16:25
Message generated for change (Settings changed) made by henryn
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2893343&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: Crash / BSOD
Group: v0.8.x (devel)
Status: Open
>Resolution: Fixed
Priority: 5
Private: No
Submitted By: Nobody/Anonymous (nobody)
>Assigned to: Henry N. (henryn)
Summary: host BSOD on with 20091105

Initial Comment:
with snapshot 0.8.0-20091105, the host got BSOD. no problem with 0.8.0-20090905.
downloaded from http://www.colinux.org/snapshots/
os: windows xp sp3 with all hotfix installed

i have retried many time, double check file permission, no luck

----------------------------------------------------------------------

>Comment By: Henry N. (henryn)
Date: 2009-11-08 13:51

Message:
Real memory limit was 984 MB all times.
With value of 1000 MB "vmalloc" and "lowmem" overlaps the "colinux" shared
host memory and would crash, if Linux would use all of this memory later.

Here is a virtual memory layout with adjusted pointers for vmalloc:
    fixmap  : 0xffffc000 - 0xfffff000   (  12 kB)
    colinux : 0xfe800000 - 0xffc00000   (  20 MB)
    vmalloc : 0xfe000000 - 0xfe7fe000   (   7 MB)
    lowmem  : 0xc0000000 - 0xfd800000   ( 984 MB)

Fixed in SVN revision r1285.
New snapshot available.



----------------------------------------------------------------------

Comment By: Henry N. (henryn)
Date: 2009-11-07 15:22

Message:
Thanks. Think, the new kernel uses more "reserved" memory.
I have successfully tested up to mem=984 with and without PAE in Windows
boot.ini.
Is 984M also working in your environment? Than I would change the limit to
that value.


----------------------------------------------------------------------

Comment By: Xuefer (xuefer)
Date: 2009-11-07 14:09

Message:
btw, no crash if i configure as:

mem=1024
init=/bin/sh

looks like there's some memory overrun colinux compiled with new kernel
while 1024M ram is in use

----------------------------------------------------------------------

Comment By: Xuefer (xuefer)
Date: 2009-11-07 14:06

Message:
reproduced only with big ram configured for colinux
===================
ram=960 -> no problem
ram=992 (960+32) -> guest crash
ram=1024 -> host crash

===================
colinux-daemon output:
Cooperative Linux Daemon, 0.8.0
Daemon compiled on Thu Nov  5 23:08:04 2009

using 'vmlinux' as kernel image
configuring 992 MB of virtual RAM
selected cobd0 for sda2, mapping to '\Device\Harddisk0\Partition2'
selected cobd1 for sda3, mapping to '\Device\Harddisk0\Partition3'
selected cobd2 for sda5, mapping to '\Device\Harddisk0\Partition4'
configured NDIS bridge at 'coLinux' device as eth1
MAC address: 00:ff:4f:0d:e7:c0
mapping cofs0 to \DosDevices\c:\app\system\colinux\
mapping cofs1 to \DosDevices\c:\
mapping cofs2 to \DosDevices\d:\
mapping cofs3 to \DosDevices\i:\
mapping cofs4 to \DosDevices\g:\
kernel boot parameters: 'video0=4 root=/dev/sda3 bootlevel=c.boot
softlevel=c.default'
creating monitor
PID: 2300
colinux: launching console
executing: colinux-console-fltk -a 2300
launching daemon for conet1
executing: colinux-ndis-net-daemon -i 2300 -u 1 -n "coLinux" -mac
00:ff:4f:0d:e7:c0 -p 1
colinux: booting
Ndis bridge probe on "1394 连接"
Ndis bridge probe on "本地连接"
Ndis bridge probe on "WAN"
Ndis bridge probe on "Bluetooth"
Ndis bridge probe on "VirtualBox Host-Only Network"
Ndis bridge probe on "VirtualBox Host-Only Network"
Ndis bridge probe on "VirtualBox Host-Only Network"
Ndis bridge probe on "VirtualBox Host-Only Network"
Ndis bridge probe on "coLinux"
conet-ndis-daemon: Bridge on: coLinux
Linux version 2.6.25.20-co-0.8.0 (hn@hn-dt) (gcc version 4.2.1 (SUSE
Linux)) #1 PREEMPT Thu Nov 5 23:06:10 CET 2009
992MB LOWMEM available.
Entering add_active_range(0, 0, 253952) 0 entries of 256 used
Zone PFN ranges:
  Normal          0 ->   253952
Movable zone start PFN for each node
early_node_map[1] active PFN ranges
    0:        0 ->   253952
On node 0 totalpages: 253952
  Normal zone: 1984 pages used for memmap
  Normal zone: 0 pages reserved
  Normal zone: 251968 pages, LIFO batch:31
  Movable zone: 0 pages used for memmap
Built 1 zonelists in Zone order, mobility grouping on.  Total pages:
251968
Kernel command line: video0=4 root=/dev/sda3 bootlevel=c.boot
softlevel=c.default
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
Setting proxy interrupt vectors
PID hash table entries: 4096 (order: 12, 16384 bytes)
Console: colour CoCON 80x25
console [tty0] enabled
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Memory: 1002624k/1015808k available (2029k kernel code, 0k reserved, 618k
data, 156k init, 0k highmem)
      .init : 0xcCPA: page pool initialized 1 of 1 pages preallocated
Calibrating delay loop... 14522.77 BogoMIPS (lpj=72613888)
Security Framework initialized
SELinux:  Disabled at boot.
Capability LSM initialized
Mount-cache hash table entries: 512
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 512K (64 bytes/line)
Compat vDSO mapped to ffffe000.
CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 3800+ stepping 02
Checking 'hlt' instruction... OK.
Freeing SMP alternatives: 0k freed
net_namespace: 536 bytes
NET: Registered protocol family 16
SCSI subsystem initialized
PCI: Probing PCI hardware
PCI: Probing PCI hardware (bus 00)
NET: Registered protocol family 2
IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
TCP bind hash table entries: 65536 (order: 6, 262144 bytes)
TCP: Hash tables configured (established 131072 bind 65536)
TCP reno registered
audit: initializing netlink socket (disabled)
colinux: Linux VM terminated
colinux: Kernel panic: Attempted to kill init!
shutting down
Pipe broken, exiting
daemon cleanup
rc=0b14b800 exit=0

===================

kernel output: (no idea how to paste kernel output as text)
see http://paste.ubuntu.com.cn/i46371

cannot attach a screenshot file here as i didn't open this bug

----------------------------------------------------------------------

Comment By: Henry N. (henryn)
Date: 2009-11-06 21:43

Message:
Do clean upgrade steps by step:
* Download archive "daemons-0.8.0-20091105.zip" form:
http://www.henrynestler.com/colinux/testing/devel-0.8.0/20091105-Snapshot/packages/
* Unpack all the files into new directory, for example to
c:\coLinux-2.6.25
* Copy your colinux config file or your BAT file from old installation
into the new directory. Edit the new config- or bat- file and add the full
path for your image files (cobd, scsi or hda). - If you not have used full
path names before.
* Remove or comment out the "initrd=initrd.gz" from config, and save the
config.
* Stop all running colinux
* Open command prompt on old installation directory
* Remove the driver
  colinux-daemon --remove-driver
* Check, that the driver is truely removed:
  colinux-daemon --status-driver
* Reboot your windows now!
* Open command prompt on the new directory and perform the manual
install:
  colinux-daemon --install-driver
* Reboot your Windows now!
  (This step is need, if the start would crash at next step.)
* Run your new colinux versioon from new directory.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2893343&group_id=98788

[coLinux-devel] [ colinux-Bugs-2893343 ] host BSOD on with 20091105

[SourceForge.net <no...@so...>]

Bugs item #2893343, was opened at 2009-11-06 16:25
Message generated for change (Comment added) made by henryn
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2893343&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: Crash / BSOD
Group: v0.8.x (devel)
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: host BSOD on with 20091105

Initial Comment:
with snapshot 0.8.0-20091105, the host got BSOD. no problem with 0.8.0-20090905.
downloaded from http://www.colinux.org/snapshots/
os: windows xp sp3 with all hotfix installed

i have retried many time, double check file permission, no luck

----------------------------------------------------------------------

>Comment By: Henry N. (henryn)
Date: 2009-11-07 15:22

Message:
Thanks. Think, the new kernel uses more "reserved" memory.
I have successfully tested up to mem=984 with and without PAE in Windows
boot.ini.
Is 984M also working in your environment? Than I would change the limit to
that value.


----------------------------------------------------------------------

Comment By: Xuefer (xuefer)
Date: 2009-11-07 14:09

Message:
btw, no crash if i configure as:

mem=1024
init=/bin/sh

looks like there's some memory overrun colinux compiled with new kernel
while 1024M ram is in use

----------------------------------------------------------------------

Comment By: Xuefer (xuefer)
Date: 2009-11-07 14:06

Message:
reproduced only with big ram configured for colinux
===================
ram=960 -> no problem
ram=992 (960+32) -> guest crash
ram=1024 -> host crash

===================
colinux-daemon output:
Cooperative Linux Daemon, 0.8.0
Daemon compiled on Thu Nov  5 23:08:04 2009

using 'vmlinux' as kernel image
configuring 992 MB of virtual RAM
selected cobd0 for sda2, mapping to '\Device\Harddisk0\Partition2'
selected cobd1 for sda3, mapping to '\Device\Harddisk0\Partition3'
selected cobd2 for sda5, mapping to '\Device\Harddisk0\Partition4'
configured NDIS bridge at 'coLinux' device as eth1
MAC address: 00:ff:4f:0d:e7:c0
mapping cofs0 to \DosDevices\c:\app\system\colinux\
mapping cofs1 to \DosDevices\c:\
mapping cofs2 to \DosDevices\d:\
mapping cofs3 to \DosDevices\i:\
mapping cofs4 to \DosDevices\g:\
kernel boot parameters: 'video0=4 root=/dev/sda3 bootlevel=c.boot
softlevel=c.default'
creating monitor
PID: 2300
colinux: launching console
executing: colinux-console-fltk -a 2300
launching daemon for conet1
executing: colinux-ndis-net-daemon -i 2300 -u 1 -n "coLinux" -mac
00:ff:4f:0d:e7:c0 -p 1
colinux: booting
Ndis bridge probe on "1394 连接"
Ndis bridge probe on "本地连接"
Ndis bridge probe on "WAN"
Ndis bridge probe on "Bluetooth"
Ndis bridge probe on "VirtualBox Host-Only Network"
Ndis bridge probe on "VirtualBox Host-Only Network"
Ndis bridge probe on "VirtualBox Host-Only Network"
Ndis bridge probe on "VirtualBox Host-Only Network"
Ndis bridge probe on "coLinux"
conet-ndis-daemon: Bridge on: coLinux
Linux version 2.6.25.20-co-0.8.0 (hn@hn-dt) (gcc version 4.2.1 (SUSE
Linux)) #1 PREEMPT Thu Nov 5 23:06:10 CET 2009
992MB LOWMEM available.
Entering add_active_range(0, 0, 253952) 0 entries of 256 used
Zone PFN ranges:
  Normal          0 ->   253952
Movable zone start PFN for each node
early_node_map[1] active PFN ranges
    0:        0 ->   253952
On node 0 totalpages: 253952
  Normal zone: 1984 pages used for memmap
  Normal zone: 0 pages reserved
  Normal zone: 251968 pages, LIFO batch:31
  Movable zone: 0 pages used for memmap
Built 1 zonelists in Zone order, mobility grouping on.  Total pages:
251968
Kernel command line: video0=4 root=/dev/sda3 bootlevel=c.boot
softlevel=c.default
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
Setting proxy interrupt vectors
PID hash table entries: 4096 (order: 12, 16384 bytes)
Console: colour CoCON 80x25
console [tty0] enabled
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Memory: 1002624k/1015808k available (2029k kernel code, 0k reserved, 618k
data, 156k init, 0k highmem)
      .init : 0xcCPA: page pool initialized 1 of 1 pages preallocated
Calibrating delay loop... 14522.77 BogoMIPS (lpj=72613888)
Security Framework initialized
SELinux:  Disabled at boot.
Capability LSM initialized
Mount-cache hash table entries: 512
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 512K (64 bytes/line)
Compat vDSO mapped to ffffe000.
CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 3800+ stepping 02
Checking 'hlt' instruction... OK.
Freeing SMP alternatives: 0k freed
net_namespace: 536 bytes
NET: Registered protocol family 16
SCSI subsystem initialized
PCI: Probing PCI hardware
PCI: Probing PCI hardware (bus 00)
NET: Registered protocol family 2
IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
TCP bind hash table entries: 65536 (order: 6, 262144 bytes)
TCP: Hash tables configured (established 131072 bind 65536)
TCP reno registered
audit: initializing netlink socket (disabled)
colinux: Linux VM terminated
colinux: Kernel panic: Attempted to kill init!
shutting down
Pipe broken, exiting
daemon cleanup
rc=0b14b800 exit=0

===================

kernel output: (no idea how to paste kernel output as text)
see http://paste.ubuntu.com.cn/i46371

cannot attach a screenshot file here as i didn't open this bug

----------------------------------------------------------------------

Comment By: Henry N. (henryn)
Date: 2009-11-06 21:43

Message:
Do clean upgrade steps by step:
* Download archive "daemons-0.8.0-20091105.zip" form:
http://www.henrynestler.com/colinux/testing/devel-0.8.0/20091105-Snapshot/packages/
* Unpack all the files into new directory, for example to
c:\coLinux-2.6.25
* Copy your colinux config file or your BAT file from old installation
into the new directory. Edit the new config- or bat- file and add the full
path for your image files (cobd, scsi or hda). - If you not have used full
path names before.
* Remove or comment out the "initrd=initrd.gz" from config, and save the
config.
* Stop all running colinux
* Open command prompt on old installation directory
* Remove the driver
  colinux-daemon --remove-driver
* Check, that the driver is truely removed:
  colinux-daemon --status-driver
* Reboot your windows now!
* Open command prompt on the new directory and perform the manual
install:
  colinux-daemon --install-driver
* Reboot your Windows now!
  (This step is need, if the start would crash at next step.)
* Run your new colinux versioon from new directory.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2893343&group_id=98788

[coLinux-devel] [ colinux-Bugs-2893343 ] host BSOD on with 20091105

[SourceForge.net <no...@so...>]

Bugs item #2893343, was opened at 2009-11-06 23:25
Message generated for change (Comment added) made by xuefer
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2893343&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: Crash / BSOD
Group: v0.8.x (devel)
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: host BSOD on with 20091105

Initial Comment:
with snapshot 0.8.0-20091105, the host got BSOD. no problem with 0.8.0-20090905.
downloaded from http://www.colinux.org/snapshots/
os: windows xp sp3 with all hotfix installed

i have retried many time, double check file permission, no luck

----------------------------------------------------------------------

Comment By: Xuefer (xuefer)
Date: 2009-11-07 21:09

Message:
btw, no crash if i configure as:

mem=1024
init=/bin/sh

looks like there's some memory overrun colinux compiled with new kernel
while 1024M ram is in use

----------------------------------------------------------------------

Comment By: Xuefer (xuefer)
Date: 2009-11-07 21:06

Message:
reproduced only with big ram configured for colinux
===================
ram=960 -> no problem
ram=992 (960+32) -> guest crash
ram=1024 -> host crash

===================
colinux-daemon output:
Cooperative Linux Daemon, 0.8.0
Daemon compiled on Thu Nov  5 23:08:04 2009

using 'vmlinux' as kernel image
configuring 992 MB of virtual RAM
selected cobd0 for sda2, mapping to '\Device\Harddisk0\Partition2'
selected cobd1 for sda3, mapping to '\Device\Harddisk0\Partition3'
selected cobd2 for sda5, mapping to '\Device\Harddisk0\Partition4'
configured NDIS bridge at 'coLinux' device as eth1
MAC address: 00:ff:4f:0d:e7:c0
mapping cofs0 to \DosDevices\c:\app\system\colinux\
mapping cofs1 to \DosDevices\c:\
mapping cofs2 to \DosDevices\d:\
mapping cofs3 to \DosDevices\i:\
mapping cofs4 to \DosDevices\g:\
kernel boot parameters: 'video0=4 root=/dev/sda3 bootlevel=c.boot
softlevel=c.default'
creating monitor
PID: 2300
colinux: launching console
executing: colinux-console-fltk -a 2300
launching daemon for conet1
executing: colinux-ndis-net-daemon -i 2300 -u 1 -n "coLinux" -mac
00:ff:4f:0d:e7:c0 -p 1
colinux: booting
Ndis bridge probe on "1394 连接"
Ndis bridge probe on "本地连接"
Ndis bridge probe on "WAN"
Ndis bridge probe on "Bluetooth"
Ndis bridge probe on "VirtualBox Host-Only Network"
Ndis bridge probe on "VirtualBox Host-Only Network"
Ndis bridge probe on "VirtualBox Host-Only Network"
Ndis bridge probe on "VirtualBox Host-Only Network"
Ndis bridge probe on "coLinux"
conet-ndis-daemon: Bridge on: coLinux
Linux version 2.6.25.20-co-0.8.0 (hn@hn-dt) (gcc version 4.2.1 (SUSE
Linux)) #1 PREEMPT Thu Nov 5 23:06:10 CET 2009
992MB LOWMEM available.
Entering add_active_range(0, 0, 253952) 0 entries of 256 used
Zone PFN ranges:
  Normal          0 ->   253952
Movable zone start PFN for each node
early_node_map[1] active PFN ranges
    0:        0 ->   253952
On node 0 totalpages: 253952
  Normal zone: 1984 pages used for memmap
  Normal zone: 0 pages reserved
  Normal zone: 251968 pages, LIFO batch:31
  Movable zone: 0 pages used for memmap
Built 1 zonelists in Zone order, mobility grouping on.  Total pages:
251968
Kernel command line: video0=4 root=/dev/sda3 bootlevel=c.boot
softlevel=c.default
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
Setting proxy interrupt vectors
PID hash table entries: 4096 (order: 12, 16384 bytes)
Console: colour CoCON 80x25
console [tty0] enabled
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Memory: 1002624k/1015808k available (2029k kernel code, 0k reserved, 618k
data, 156k init, 0k highmem)
      .init : 0xcCPA: page pool initialized 1 of 1 pages preallocated
Calibrating delay loop... 14522.77 BogoMIPS (lpj=72613888)
Security Framework initialized
SELinux:  Disabled at boot.
Capability LSM initialized
Mount-cache hash table entries: 512
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 512K (64 bytes/line)
Compat vDSO mapped to ffffe000.
CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 3800+ stepping 02
Checking 'hlt' instruction... OK.
Freeing SMP alternatives: 0k freed
net_namespace: 536 bytes
NET: Registered protocol family 16
SCSI subsystem initialized
PCI: Probing PCI hardware
PCI: Probing PCI hardware (bus 00)
NET: Registered protocol family 2
IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
TCP bind hash table entries: 65536 (order: 6, 262144 bytes)
TCP: Hash tables configured (established 131072 bind 65536)
TCP reno registered
audit: initializing netlink socket (disabled)
colinux: Linux VM terminated
colinux: Kernel panic: Attempted to kill init!
shutting down
Pipe broken, exiting
daemon cleanup
rc=0b14b800 exit=0

===================

kernel output: (no idea how to paste kernel output as text)
see http://paste.ubuntu.com.cn/i46371

cannot attach a screenshot file here as i didn't open this bug

----------------------------------------------------------------------

Comment By: Henry N. (henryn)
Date: 2009-11-07 04:43

Message:
Do clean upgrade steps by step:
* Download archive "daemons-0.8.0-20091105.zip" form:
http://www.henrynestler.com/colinux/testing/devel-0.8.0/20091105-Snapshot/packages/
* Unpack all the files into new directory, for example to
c:\coLinux-2.6.25
* Copy your colinux config file or your BAT file from old installation
into the new directory. Edit the new config- or bat- file and add the full
path for your image files (cobd, scsi or hda). - If you not have used full
path names before.
* Remove or comment out the "initrd=initrd.gz" from config, and save the
config.
* Stop all running colinux
* Open command prompt on old installation directory
* Remove the driver
  colinux-daemon --remove-driver
* Check, that the driver is truely removed:
  colinux-daemon --status-driver
* Reboot your windows now!
* Open command prompt on the new directory and perform the manual
install:
  colinux-daemon --install-driver
* Reboot your Windows now!
  (This step is need, if the start would crash at next step.)
* Run your new colinux versioon from new directory.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2893343&group_id=98788

[coLinux-devel] [ colinux-Bugs-2893343 ] host BSOD on with 20091105

[SourceForge.net <no...@so...>]

Bugs item #2893343, was opened at 2009-11-06 23:25
Message generated for change (Comment added) made by xuefer
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2893343&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: Crash / BSOD
Group: v0.8.x (devel)
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: host BSOD on with 20091105

Initial Comment:
with snapshot 0.8.0-20091105, the host got BSOD. no problem with 0.8.0-20090905.
downloaded from http://www.colinux.org/snapshots/
os: windows xp sp3 with all hotfix installed

i have retried many time, double check file permission, no luck

----------------------------------------------------------------------

Comment By: Xuefer (xuefer)
Date: 2009-11-07 21:06

Message:
reproduced only with big ram configured for colinux
===================
ram=960 -> no problem
ram=992 (960+32) -> guest crash
ram=1024 -> host crash

===================
colinux-daemon output:
Cooperative Linux Daemon, 0.8.0
Daemon compiled on Thu Nov  5 23:08:04 2009

using 'vmlinux' as kernel image
configuring 992 MB of virtual RAM
selected cobd0 for sda2, mapping to '\Device\Harddisk0\Partition2'
selected cobd1 for sda3, mapping to '\Device\Harddisk0\Partition3'
selected cobd2 for sda5, mapping to '\Device\Harddisk0\Partition4'
configured NDIS bridge at 'coLinux' device as eth1
MAC address: 00:ff:4f:0d:e7:c0
mapping cofs0 to \DosDevices\c:\app\system\colinux\
mapping cofs1 to \DosDevices\c:\
mapping cofs2 to \DosDevices\d:\
mapping cofs3 to \DosDevices\i:\
mapping cofs4 to \DosDevices\g:\
kernel boot parameters: 'video0=4 root=/dev/sda3 bootlevel=c.boot
softlevel=c.default'
creating monitor
PID: 2300
colinux: launching console
executing: colinux-console-fltk -a 2300
launching daemon for conet1
executing: colinux-ndis-net-daemon -i 2300 -u 1 -n "coLinux" -mac
00:ff:4f:0d:e7:c0 -p 1
colinux: booting
Ndis bridge probe on "1394 连接"
Ndis bridge probe on "本地连接"
Ndis bridge probe on "WAN"
Ndis bridge probe on "Bluetooth"
Ndis bridge probe on "VirtualBox Host-Only Network"
Ndis bridge probe on "VirtualBox Host-Only Network"
Ndis bridge probe on "VirtualBox Host-Only Network"
Ndis bridge probe on "VirtualBox Host-Only Network"
Ndis bridge probe on "coLinux"
conet-ndis-daemon: Bridge on: coLinux
Linux version 2.6.25.20-co-0.8.0 (hn@hn-dt) (gcc version 4.2.1 (SUSE
Linux)) #1 PREEMPT Thu Nov 5 23:06:10 CET 2009
992MB LOWMEM available.
Entering add_active_range(0, 0, 253952) 0 entries of 256 used
Zone PFN ranges:
  Normal          0 ->   253952
Movable zone start PFN for each node
early_node_map[1] active PFN ranges
    0:        0 ->   253952
On node 0 totalpages: 253952
  Normal zone: 1984 pages used for memmap
  Normal zone: 0 pages reserved
  Normal zone: 251968 pages, LIFO batch:31
  Movable zone: 0 pages used for memmap
Built 1 zonelists in Zone order, mobility grouping on.  Total pages:
251968
Kernel command line: video0=4 root=/dev/sda3 bootlevel=c.boot
softlevel=c.default
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
Setting proxy interrupt vectors
PID hash table entries: 4096 (order: 12, 16384 bytes)
Console: colour CoCON 80x25
console [tty0] enabled
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Memory: 1002624k/1015808k available (2029k kernel code, 0k reserved, 618k
data, 156k init, 0k highmem)
      .init : 0xcCPA: page pool initialized 1 of 1 pages preallocated
Calibrating delay loop... 14522.77 BogoMIPS (lpj=72613888)
Security Framework initialized
SELinux:  Disabled at boot.
Capability LSM initialized
Mount-cache hash table entries: 512
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 512K (64 bytes/line)
Compat vDSO mapped to ffffe000.
CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 3800+ stepping 02
Checking 'hlt' instruction... OK.
Freeing SMP alternatives: 0k freed
net_namespace: 536 bytes
NET: Registered protocol family 16
SCSI subsystem initialized
PCI: Probing PCI hardware
PCI: Probing PCI hardware (bus 00)
NET: Registered protocol family 2
IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
TCP bind hash table entries: 65536 (order: 6, 262144 bytes)
TCP: Hash tables configured (established 131072 bind 65536)
TCP reno registered
audit: initializing netlink socket (disabled)
colinux: Linux VM terminated
colinux: Kernel panic: Attempted to kill init!
shutting down
Pipe broken, exiting
daemon cleanup
rc=0b14b800 exit=0

===================

kernel output: (no idea how to paste kernel output as text)
see http://paste.ubuntu.com.cn/i46371

cannot attach a screenshot file here as i didn't open this bug

----------------------------------------------------------------------

Comment By: Henry N. (henryn)
Date: 2009-11-07 04:43

Message:
Do clean upgrade steps by step:
* Download archive "daemons-0.8.0-20091105.zip" form:
http://www.henrynestler.com/colinux/testing/devel-0.8.0/20091105-Snapshot/packages/
* Unpack all the files into new directory, for example to
c:\coLinux-2.6.25
* Copy your colinux config file or your BAT file from old installation
into the new directory. Edit the new config- or bat- file and add the full
path for your image files (cobd, scsi or hda). - If you not have used full
path names before.
* Remove or comment out the "initrd=initrd.gz" from config, and save the
config.
* Stop all running colinux
* Open command prompt on old installation directory
* Remove the driver
  colinux-daemon --remove-driver
* Check, that the driver is truely removed:
  colinux-daemon --status-driver
* Reboot your windows now!
* Open command prompt on the new directory and perform the manual
install:
  colinux-daemon --install-driver
* Reboot your Windows now!
  (This step is need, if the start would crash at next step.)
* Run your new colinux versioon from new directory.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2893343&group_id=98788

[coLinux-devel] [ colinux-Bugs-2893417 ] host BSOD on with 20091105 - ID: 2893343

[SourceForge.net <no...@so...>]

Bugs item #2893417, was opened at 2009-11-06 17:49
Message generated for change (Settings changed) made by henryn
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2893417&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: None
Status: Deleted
Resolution: None
Priority: 5
>Private: Yes
Submitted By: Peter Kuznetsov (peter_kuznetsov)
Assigned to: Nobody/Anonymous (nobody)
Summary: host BSOD on with 20091105 - ID: 2893343

Initial Comment:
I've had the same problem, but now it works fine.
Try to do next:
1. Make copy of your working image.
2. Add this copy as second image to config file or command line of colinux-daemon.exe in old coLinux directory.
3. Start your working coLinux and remove /lib/modules/2.6.25.20-co-0.8.0 folder from copy of the image. 
4. Set this copy as root image for version 20091105.
5. If you install version 20091105 from packages, rename 'modules-2.6.25.20-co-0.8.0-20091105.tgz' to 'vmlinux-modules.tar.gz'.
6. Add line  'initrd=initrd.gz' to coLinux config file or command line of colinux-daemon.exe
7. Start new version.

Peter.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2893417&group_id=98788

[coLinux-devel] [ colinux-Bugs-2890868 ] coLinux error in SCSI-driver with DVD-image?

[SourceForge.net <no...@so...>]

Bugs item #2890868, was opened at 2009-11-02 19:44
Message generated for change (Settings changed) made by henryn
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2890868&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: Crash / BSOD
Group: None
Status: Deleted
Resolution: None
Priority: 5
>Private: Yes
Submitted By: Peter Kuznetsov (peter_kuznetsov)
Assigned to: Nobody/Anonymous (nobody)
Summary: coLinux error in SCSI-driver with DVD-image?

Initial Comment:

Summary.
=======
Version 0.8.0 with kernel 2.6.25.20: 
  ...
  Driver 'sd' needs updating - please use bus_type methods
  Driver 'sr' needs updating - please use bus_type methods
  ...
  scsi1: unhandled opcode: 51
  ...
  Kernel panic - not syncing: COSCSI: response: use_sg (2) > 1!

Version 0.8.0 with kernel 2.6.22.18:
Version 0.7.5:
Version 0.7.4:
  ...
  scsi1: unhandled opcode: 5a
  scsi1: unhandled opcode: 51
  ...
  (System continue working)

Version 0.7.3:
Version 0.7.2:
  Don't work.

Some details.
============
  File "run.bat":
  --------------
    set COLINUX_CONSOLE_FONT=Lucida Console:12
    set COLINUX_CONSOLE_EXIT_ON_DETACH=1

    colinux-daemon.exe --remove-driver
    colinux-daemon.exe --install-driver

    colinux-daemon.exe @config.cfg -v 3 -t nt

    colinux-daemon.exe --remove-driver

  File "config.cfg":
  ----------------
    cocon=160x79

    mem=512

    kernel=vmlinux
    initrd=initrd.gz

    # Flat part of vmdk (with MBR)
    scsi0=disk,"Debian-5.0.3-KDE-00.flat"  
    scsi1=disk,"O:\VIRT_DISK\VDISKS\swap_scsi_0.flat"  # flat part of vmdk
    scsi2=cdrom,"J:\OS\Linux\$DEBIAN\Debian\5.0.3\debian-503-i386-DVD-1.iso"

    root=/dev/sda1
    ro

    eth0=slirp

  File "/etc/fstab" (without editing after installation):
  ----------------
    # /etc/fstab: static file system information.
    #
    # <file system> <mount point>   <type>  <options>       <dump>  <pass>
    proc            /proc           proc    defaults        0       0
    /dev/sda1       /               ext3    errors=remount-ro 0       1
    /dev/sdb1       none            swap    sw              0       0
    /dev/scd0       /media/cdrom0   udf,iso9660 user,noauto     0       0
    /dev/fd0        /media/floppy0  auto    rw,user,noauto  0       0

  In whole system after installation I've edited only one file "/etc/X11/default-display-manager":
    #/usr/bin/kdm
    echo "null" > /etc/X11/default-display-manager 

Relevant output.
===============
  Version 0.8.0 with kernel 2.6.25.20 (kernel panic): 
  --------------------------------------------------
    scsi0 : Cooperative Linux SCSI Adapter
    scsi 0:0:0:0: Direct-Access     coLinux  CODISK           1.01 PQ: 0 ANSI: 5
    scsi 0:0:1:0: Direct-Access     coLinux  CODISK           1.01 PQ: 0 ANSI: 5
    scsi 0:0:2:0: CD-ROM            coLinux  COCD             1.01 PQ: 0 ANSI: 2
    Driver 'sd' needs updating - please use bus_type methods   <----------------------PK!!!
    sd 0:0:0:0: [sda] 6291456 512-byte hardware sectors (3221 MB)
    sd 0:0:0:0: [sda] Write Protect is off
    sd 0:0:0:0: [sda] Mode Sense: 1f 00 10 08
    sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA
    sd 0:0:0:0: [sda] 6291456 512-byte hardware sectors (3221 MB)
    sd 0:0:0:0: [sda] Write Protect is off
    sd 0:0:0:0: [sda] Mode Sense: 1f 00 10 08
    sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA
     sda: sda1
    sd 0:0:0:0: [sda] Attached SCSI disk
    sd 0:0:1:0: [sdb] 4194304 512-byte hardware sectors (2147 MB)
    sd 0:0:1:0: [sdb] Write Protect is off
    sd 0:0:1:0: [sdb] Mode Sense: 1f 00 10 08
    sd 0:0:1:0: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA
    sd 0:0:1:0: [sdb] 4194304 512-byte hardware sectors (2147 MB)
    sd 0:0:1:0: [sdb] Write Protect is off
    sd 0:0:1:0: [sdb] Mode Sense: 1f 00 10 08
    sd 0:0:1:0: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA
     sdb: sdb1
    sd 0:0:1:0: [sdb] Attached SCSI disk
    Driver 'sr' needs updating - please use bus_type methods   <----------------------PK!!!
    sr0: scsi3-mmc drive: 32x/32x cd/rw xa/form2 cdda tray
    Uniform CD-ROM driver Revision: 3.20
    sr 0:0:2:0: Attached scsi CD-ROM sr0
    ...
    scsi2: unhandled opcode: 51
    sd 0:0:0:0: Attached scsi generic sg0 type 0
    sd 0:0:1:0: Attached scsi generic sg1 type 0
    sr 0:0:2:0: Attached scsi generic sg2 type 5
    scsi2: unhandled opcode: 51
    ...
    Kernel panic - not syncing: COSCSI: response: use_sg (2) > 1! <-------------------PK!!!

    colinux: Linux VM terminated
    colinux: Kernel panic: COSCSI: response: use_sg (2) > 1!

    console: Monitor3116: Detached

    Q:\coLinux\$Debian\Debian\5.0.3-co-080_2.6.25.20>colinux-daemon.exe --remove-driver
    Cooperative Linux Daemon, 0.8.0
    Daemon compiled on Sun Sep 27 12:50:20 2009

    ============================================================================

  Version 0.8.0 with kernel 2.6.22.18 (working):
  ---------------------------------------------
    scsi0 : Cooperative Linux SCSI Adapter
    scsi 0:0:0:0: Direct-Access     coLinux  CODISK           1.01 PQ: 0 ANSI: 5
    scsi 0:0:1:0: Direct-Access     coLinux  CODISK           1.01 PQ: 0 ANSI: 5
    scsi 0:0:2:0: CD-ROM            coLinux  COCD             1.01 PQ: 0 ANSI: 2
    sd 0:0:0:0: [sda] 6291456 512-byte hardware sectors (3221 MB)
    sd 0:0:0:0: [sda] Write Protect is off
    sd 0:0:0:0: [sda] Mode Sense: 1f 00 10 08
    sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA
    sd 0:0:0:0: [sda] 6291456 512-byte hardware sectors (3221 MB)
    sd 0:0:0:0: [sda] Write Protect is off
    sd 0:0:0:0: [sda] Mode Sense: 1f 00 10 08
    sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA
     sda: sda1
    sd 0:0:0:0: [sda] Attached SCSI disk
    sd 0:0:1:0: [sdb] 4194304 512-byte hardware sectors (2147 MB)
    sd 0:0:1:0: [sdb] Write Protect is off
    sd 0:0:1:0: [sdb] Mode Sense: 1f 00 10 08
    sd 0:0:1:0: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA
    sd 0:0:1:0: [sdb] 4194304 512-byte hardware sectors (2147 MB)
    sd 0:0:1:0: [sdb] Write Protect is off
    sd 0:0:1:0: [sdb] Mode Sense: 1f 00 10 08
    sd 0:0:1:0: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA
     sdb: sdb1
    sd 0:0:1:0: [sdb] Attached SCSI disk
    sr0: scsi3-mmc drive: 32x/32x cd/rw xa/form2 cdda tray
    Uniform CD-ROM driver Revision: 3.20
    sr 0:0:2:0: Attached scsi CD-ROM sr0
    .......................................
    scsi2: unhandled opcode: 51                                   <-------------------PK!!!
    sd 0:0:0:0: Attached scsi generic sg0 type 0
    sd 0:0:1:0: Attached scsi generic sg1 type 0
    sr 0:0:2:0: Attached scsi generic sg2 type 5
    .......................................
    scsi2: unhandled opcode: 5a                                   <-------------------PK!!!
    scsi2: unhandled opcode: 51
    scsi2: unhandled opcode: 51
    scsi2: unhandled opcode: 5a
    scsi2: unhandled opcode: 5a
    ...
    sd 0:0:1:0: [sdb] Synchronizing SCSI cache
    sd 0:0:0:0: [sda] Synchronizing SCSI cache

    ===============================================================================

    If you need some additional testing of coLinux-0.8.0 with kernel 2.6.25.20, mail me, I can do it. 
    Many thanks for very usefull system!!!

    With best regards, Peter.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2890868&group_id=98788

[coLinux-devel] [ colinux-Bugs-2890857 ] SCSI: Kernel panic - "response: use_sg (2) > 1"

[SourceForge.net <no...@so...>]

Bugs item #2890857, was opened at 2009-11-02 19:32
Message generated for change (Settings changed) made by henryn
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2890857&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: Crash / BSOD
Group: None
Status: Closed
Resolution: None
Priority: 5
Private: No
Submitted By: Peter Kuznetsov (peter_kuznetsov)
Assigned to: Nobody/Anonymous (nobody)
Summary: SCSI: Kernel panic - "response: use_sg (2) > 1"

Initial Comment:

Summary.
=======
Version 0.8.0 with kernel 2.6.25.20: 
  ...
  Driver 'sd' needs updating - please use bus_type methods
  Driver 'sr' needs updating - please use bus_type methods
  ...
  scsi1: unhandled opcode: 51
  ...
  Kernel panic - not syncing: COSCSI: response: use_sg (2) > 1!

Version 0.8.0 with kernel 2.6.22.18:
Version 0.7.5:
Version 0.7.4:
  ...
  scsi1: unhandled opcode: 5a
  scsi1: unhandled opcode: 51
  ...
  (System continue working)

Version 0.7.3:
Version 0.7.2:
  Don't work.

Some details.
============
  File "run.bat":
  --------------
    set COLINUX_CONSOLE_FONT=Lucida Console:12
    set COLINUX_CONSOLE_EXIT_ON_DETACH=1

    colinux-daemon.exe --remove-driver
    colinux-daemon.exe --install-driver

    colinux-daemon.exe @config.cfg -v 3 -t nt

    colinux-daemon.exe --remove-driver

  File "config.cfg":
  ----------------
    cocon=160x79

    mem=512

    kernel=vmlinux
    initrd=initrd.gz

    # Flat part of vmdk (with MBR)
    scsi0=disk,"Debian-5.0.3-KDE-00.flat"  
    scsi1=disk,"O:\VIRT_DISK\VDISKS\swap_scsi_0.flat"  # flat part of vmdk
    scsi2=cdrom,"J:\OS\Linux\$DEBIAN\Debian\5.0.3\debian-503-i386-DVD-1.iso"

    root=/dev/sda1
    ro

    eth0=slirp

  File "/etc/fstab" (without editing after installation):
  ----------------
    # /etc/fstab: static file system information.
    #
    # <file system> <mount point>   <type>  <options>       <dump>  <pass>
    proc            /proc           proc    defaults        0       0
    /dev/sda1       /               ext3    errors=remount-ro 0       1
    /dev/sdb1       none            swap    sw              0       0
    /dev/scd0       /media/cdrom0   udf,iso9660 user,noauto     0       0
    /dev/fd0        /media/floppy0  auto    rw,user,noauto  0       0

  In whole system after installation I've edited only one file "/etc/X11/default-display-manager":
    #/usr/bin/kdm
    echo "null" > /etc/X11/default-display-manager 

Relevant output.
===============
  Version 0.8.0 with kernel 2.6.25.20 (kernel panic): 
  --------------------------------------------------
    scsi0 : Cooperative Linux SCSI Adapter
    scsi 0:0:0:0: Direct-Access     coLinux  CODISK           1.01 PQ: 0 ANSI: 5
    scsi 0:0:1:0: Direct-Access     coLinux  CODISK           1.01 PQ: 0 ANSI: 5
    scsi 0:0:2:0: CD-ROM            coLinux  COCD             1.01 PQ: 0 ANSI: 2
    Driver 'sd' needs updating - please use bus_type methods   <----------------------PK!!!
    sd 0:0:0:0: [sda] 6291456 512-byte hardware sectors (3221 MB)
    sd 0:0:0:0: [sda] Write Protect is off
    sd 0:0:0:0: [sda] Mode Sense: 1f 00 10 08
    sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA
    sd 0:0:0:0: [sda] 6291456 512-byte hardware sectors (3221 MB)
    sd 0:0:0:0: [sda] Write Protect is off
    sd 0:0:0:0: [sda] Mode Sense: 1f 00 10 08
    sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA
     sda: sda1
    sd 0:0:0:0: [sda] Attached SCSI disk
    sd 0:0:1:0: [sdb] 4194304 512-byte hardware sectors (2147 MB)
    sd 0:0:1:0: [sdb] Write Protect is off
    sd 0:0:1:0: [sdb] Mode Sense: 1f 00 10 08
    sd 0:0:1:0: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA
    sd 0:0:1:0: [sdb] 4194304 512-byte hardware sectors (2147 MB)
    sd 0:0:1:0: [sdb] Write Protect is off
    sd 0:0:1:0: [sdb] Mode Sense: 1f 00 10 08
    sd 0:0:1:0: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA
     sdb: sdb1
    sd 0:0:1:0: [sdb] Attached SCSI disk
    Driver 'sr' needs updating - please use bus_type methods   <----------------------PK!!!
    sr0: scsi3-mmc drive: 32x/32x cd/rw xa/form2 cdda tray
    Uniform CD-ROM driver Revision: 3.20
    sr 0:0:2:0: Attached scsi CD-ROM sr0
    ...
    scsi2: unhandled opcode: 51
    sd 0:0:0:0: Attached scsi generic sg0 type 0
    sd 0:0:1:0: Attached scsi generic sg1 type 0
    sr 0:0:2:0: Attached scsi generic sg2 type 5
    scsi2: unhandled opcode: 51
    ...
    Kernel panic - not syncing: COSCSI: response: use_sg (2) > 1! <-------------------PK!!!

    colinux: Linux VM terminated
    colinux: Kernel panic: COSCSI: response: use_sg (2) > 1!

    console: Monitor3116: Detached

    Q:\coLinux\$Debian\Debian\5.0.3-co-080_2.6.25.20>colinux-daemon.exe --remove-driver
    Cooperative Linux Daemon, 0.8.0
    Daemon compiled on Sun Sep 27 12:50:20 2009

    ============================================================================

  Version 0.8.0 with kernel 2.6.22.18 (working):
  ---------------------------------------------
    scsi0 : Cooperative Linux SCSI Adapter
    scsi 0:0:0:0: Direct-Access     coLinux  CODISK           1.01 PQ: 0 ANSI: 5
    scsi 0:0:1:0: Direct-Access     coLinux  CODISK           1.01 PQ: 0 ANSI: 5
    scsi 0:0:2:0: CD-ROM            coLinux  COCD             1.01 PQ: 0 ANSI: 2
    sd 0:0:0:0: [sda] 6291456 512-byte hardware sectors (3221 MB)
    sd 0:0:0:0: [sda] Write Protect is off
    sd 0:0:0:0: [sda] Mode Sense: 1f 00 10 08
    sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA
    sd 0:0:0:0: [sda] 6291456 512-byte hardware sectors (3221 MB)
    sd 0:0:0:0: [sda] Write Protect is off
    sd 0:0:0:0: [sda] Mode Sense: 1f 00 10 08
    sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA
     sda: sda1
    sd 0:0:0:0: [sda] Attached SCSI disk
    sd 0:0:1:0: [sdb] 4194304 512-byte hardware sectors (2147 MB)
    sd 0:0:1:0: [sdb] Write Protect is off
    sd 0:0:1:0: [sdb] Mode Sense: 1f 00 10 08
    sd 0:0:1:0: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA
    sd 0:0:1:0: [sdb] 4194304 512-byte hardware sectors (2147 MB)
    sd 0:0:1:0: [sdb] Write Protect is off
    sd 0:0:1:0: [sdb] Mode Sense: 1f 00 10 08
    sd 0:0:1:0: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA
     sdb: sdb1
    sd 0:0:1:0: [sdb] Attached SCSI disk
    sr0: scsi3-mmc drive: 32x/32x cd/rw xa/form2 cdda tray
    Uniform CD-ROM driver Revision: 3.20
    sr 0:0:2:0: Attached scsi CD-ROM sr0
    .......................................
    scsi2: unhandled opcode: 51                                   <-------------------PK!!!
    sd 0:0:0:0: Attached scsi generic sg0 type 0
    sd 0:0:1:0: Attached scsi generic sg1 type 0
    sr 0:0:2:0: Attached scsi generic sg2 type 5
    .......................................
    scsi2: unhandled opcode: 5a                                   <-------------------PK!!!
    scsi2: unhandled opcode: 51
    scsi2: unhandled opcode: 51
    scsi2: unhandled opcode: 5a
    scsi2: unhandled opcode: 5a
    ...
    sd 0:0:1:0: [sdb] Synchronizing SCSI cache
    sd 0:0:0:0: [sda] Synchronizing SCSI cache

    ===============================================================================

    If you need some additional testing of coLinux-0.8.0 with kernel 2.6.25.20, mail me, I can do it. 
    Many thanks for very usefull system!!!

    With best regards, Peter.


----------------------------------------------------------------------

Comment By: Henry N. (henryn)
Date: 2009-11-06 22:30

Message:
SVN revisions r1282 fixed this bug in Kernel 2.6.25.20, and r1284 in
2.6.22.18.

----------------------------------------------------------------------

Comment By: Peter Kuznetsov (peter_kuznetsov)
Date: 2009-11-03 22:39

Message:
Henry, 
I close this  tracker and will wait for next autobuild with kernel
2.6.25.20 (it is closer to 2.6.26.2, which is used in Debian 5.0.3).

With many thanks, Peter.

----------------------------------------------------------------------

Comment By: Henry N. (henryn)
Date: 2009-11-03 21:58

Message:
The warnings
  Driver 'sd' needs updating - please use bus_type methods
  Driver 'sr' needs updating - please use bus_type methods
are harmless.

The Bug at
  COSCSI: response: use_sg (2) > 1!
is more a real problem. There a variable has two buffers, but the caller
of function only should fill a single buffer, and the function can only run
with a single buffer. If that bug line was triggered, then something is
real wrong. I will try to replace the "panic" into a "warning". So we would
see the stack backtrace from callers.




----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2890857&group_id=98788

[coLinux-devel] [ colinux-Bugs-2890857 ] SCSI: Kernel panic - "response: use_sg (2) > 1"

[SourceForge.net <no...@so...>]

Bugs item #2890857, was opened at 2009-11-02 19:32
Message generated for change (Settings changed) made by henryn
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2890857&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: Crash / BSOD
Group: None
Status: Closed
Resolution: None
Priority: 5
Private: No
Submitted By: Peter Kuznetsov (peter_kuznetsov)
Assigned to: Nobody/Anonymous (nobody)
>Summary: SCSI: Kernel panic - "response: use_sg (2) > 1"

Initial Comment:

Summary.
=======
Version 0.8.0 with kernel 2.6.25.20: 
  ...
  Driver 'sd' needs updating - please use bus_type methods
  Driver 'sr' needs updating - please use bus_type methods
  ...
  scsi1: unhandled opcode: 51
  ...
  Kernel panic - not syncing: COSCSI: response: use_sg (2) > 1!

Version 0.8.0 with kernel 2.6.22.18:
Version 0.7.5:
Version 0.7.4:
  ...
  scsi1: unhandled opcode: 5a
  scsi1: unhandled opcode: 51
  ...
  (System continue working)

Version 0.7.3:
Version 0.7.2:
  Don't work.

Some details.
============
  File "run.bat":
  --------------
    set COLINUX_CONSOLE_FONT=Lucida Console:12
    set COLINUX_CONSOLE_EXIT_ON_DETACH=1

    colinux-daemon.exe --remove-driver
    colinux-daemon.exe --install-driver

    colinux-daemon.exe @config.cfg -v 3 -t nt

    colinux-daemon.exe --remove-driver

  File "config.cfg":
  ----------------
    cocon=160x79

    mem=512

    kernel=vmlinux
    initrd=initrd.gz

    # Flat part of vmdk (with MBR)
    scsi0=disk,"Debian-5.0.3-KDE-00.flat"  
    scsi1=disk,"O:\VIRT_DISK\VDISKS\swap_scsi_0.flat"  # flat part of vmdk
    scsi2=cdrom,"J:\OS\Linux\$DEBIAN\Debian\5.0.3\debian-503-i386-DVD-1.iso"

    root=/dev/sda1
    ro

    eth0=slirp

  File "/etc/fstab" (without editing after installation):
  ----------------
    # /etc/fstab: static file system information.
    #
    # <file system> <mount point>   <type>  <options>       <dump>  <pass>
    proc            /proc           proc    defaults        0       0
    /dev/sda1       /               ext3    errors=remount-ro 0       1
    /dev/sdb1       none            swap    sw              0       0
    /dev/scd0       /media/cdrom0   udf,iso9660 user,noauto     0       0
    /dev/fd0        /media/floppy0  auto    rw,user,noauto  0       0

  In whole system after installation I've edited only one file "/etc/X11/default-display-manager":
    #/usr/bin/kdm
    echo "null" > /etc/X11/default-display-manager 

Relevant output.
===============
  Version 0.8.0 with kernel 2.6.25.20 (kernel panic): 
  --------------------------------------------------
    scsi0 : Cooperative Linux SCSI Adapter
    scsi 0:0:0:0: Direct-Access     coLinux  CODISK           1.01 PQ: 0 ANSI: 5
    scsi 0:0:1:0: Direct-Access     coLinux  CODISK           1.01 PQ: 0 ANSI: 5
    scsi 0:0:2:0: CD-ROM            coLinux  COCD             1.01 PQ: 0 ANSI: 2
    Driver 'sd' needs updating - please use bus_type methods   <----------------------PK!!!
    sd 0:0:0:0: [sda] 6291456 512-byte hardware sectors (3221 MB)
    sd 0:0:0:0: [sda] Write Protect is off
    sd 0:0:0:0: [sda] Mode Sense: 1f 00 10 08
    sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA
    sd 0:0:0:0: [sda] 6291456 512-byte hardware sectors (3221 MB)
    sd 0:0:0:0: [sda] Write Protect is off
    sd 0:0:0:0: [sda] Mode Sense: 1f 00 10 08
    sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA
     sda: sda1
    sd 0:0:0:0: [sda] Attached SCSI disk
    sd 0:0:1:0: [sdb] 4194304 512-byte hardware sectors (2147 MB)
    sd 0:0:1:0: [sdb] Write Protect is off
    sd 0:0:1:0: [sdb] Mode Sense: 1f 00 10 08
    sd 0:0:1:0: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA
    sd 0:0:1:0: [sdb] 4194304 512-byte hardware sectors (2147 MB)
    sd 0:0:1:0: [sdb] Write Protect is off
    sd 0:0:1:0: [sdb] Mode Sense: 1f 00 10 08
    sd 0:0:1:0: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA
     sdb: sdb1
    sd 0:0:1:0: [sdb] Attached SCSI disk
    Driver 'sr' needs updating - please use bus_type methods   <----------------------PK!!!
    sr0: scsi3-mmc drive: 32x/32x cd/rw xa/form2 cdda tray
    Uniform CD-ROM driver Revision: 3.20
    sr 0:0:2:0: Attached scsi CD-ROM sr0
    ...
    scsi2: unhandled opcode: 51
    sd 0:0:0:0: Attached scsi generic sg0 type 0
    sd 0:0:1:0: Attached scsi generic sg1 type 0
    sr 0:0:2:0: Attached scsi generic sg2 type 5
    scsi2: unhandled opcode: 51
    ...
    Kernel panic - not syncing: COSCSI: response: use_sg (2) > 1! <-------------------PK!!!

    colinux: Linux VM terminated
    colinux: Kernel panic: COSCSI: response: use_sg (2) > 1!

    console: Monitor3116: Detached

    Q:\coLinux\$Debian\Debian\5.0.3-co-080_2.6.25.20>colinux-daemon.exe --remove-driver
    Cooperative Linux Daemon, 0.8.0
    Daemon compiled on Sun Sep 27 12:50:20 2009

    ============================================================================

  Version 0.8.0 with kernel 2.6.22.18 (working):
  ---------------------------------------------
    scsi0 : Cooperative Linux SCSI Adapter
    scsi 0:0:0:0: Direct-Access     coLinux  CODISK           1.01 PQ: 0 ANSI: 5
    scsi 0:0:1:0: Direct-Access     coLinux  CODISK           1.01 PQ: 0 ANSI: 5
    scsi 0:0:2:0: CD-ROM            coLinux  COCD             1.01 PQ: 0 ANSI: 2
    sd 0:0:0:0: [sda] 6291456 512-byte hardware sectors (3221 MB)
    sd 0:0:0:0: [sda] Write Protect is off
    sd 0:0:0:0: [sda] Mode Sense: 1f 00 10 08
    sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA
    sd 0:0:0:0: [sda] 6291456 512-byte hardware sectors (3221 MB)
    sd 0:0:0:0: [sda] Write Protect is off
    sd 0:0:0:0: [sda] Mode Sense: 1f 00 10 08
    sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA
     sda: sda1
    sd 0:0:0:0: [sda] Attached SCSI disk
    sd 0:0:1:0: [sdb] 4194304 512-byte hardware sectors (2147 MB)
    sd 0:0:1:0: [sdb] Write Protect is off
    sd 0:0:1:0: [sdb] Mode Sense: 1f 00 10 08
    sd 0:0:1:0: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA
    sd 0:0:1:0: [sdb] 4194304 512-byte hardware sectors (2147 MB)
    sd 0:0:1:0: [sdb] Write Protect is off
    sd 0:0:1:0: [sdb] Mode Sense: 1f 00 10 08
    sd 0:0:1:0: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA
     sdb: sdb1
    sd 0:0:1:0: [sdb] Attached SCSI disk
    sr0: scsi3-mmc drive: 32x/32x cd/rw xa/form2 cdda tray
    Uniform CD-ROM driver Revision: 3.20
    sr 0:0:2:0: Attached scsi CD-ROM sr0
    .......................................
    scsi2: unhandled opcode: 51                                   <-------------------PK!!!
    sd 0:0:0:0: Attached scsi generic sg0 type 0
    sd 0:0:1:0: Attached scsi generic sg1 type 0
    sr 0:0:2:0: Attached scsi generic sg2 type 5
    .......................................
    scsi2: unhandled opcode: 5a                                   <-------------------PK!!!
    scsi2: unhandled opcode: 51
    scsi2: unhandled opcode: 51
    scsi2: unhandled opcode: 5a
    scsi2: unhandled opcode: 5a
    ...
    sd 0:0:1:0: [sdb] Synchronizing SCSI cache
    sd 0:0:0:0: [sda] Synchronizing SCSI cache

    ===============================================================================

    If you need some additional testing of coLinux-0.8.0 with kernel 2.6.25.20, mail me, I can do it. 
    Many thanks for very usefull system!!!

    With best regards, Peter.


----------------------------------------------------------------------

>Comment By: Henry N. (henryn)
Date: 2009-11-06 22:30

Message:
SVN revisions r1282 fixed this bug in Kernel 2.6.25.20, and r1284 in
2.6.22.18.

----------------------------------------------------------------------

Comment By: Peter Kuznetsov (peter_kuznetsov)
Date: 2009-11-03 22:39

Message:
Henry, 
I close this  tracker and will wait for next autobuild with kernel
2.6.25.20 (it is closer to 2.6.26.2, which is used in Debian 5.0.3).

With many thanks, Peter.

----------------------------------------------------------------------

Comment By: Henry N. (henryn)
Date: 2009-11-03 21:58

Message:
The warnings
  Driver 'sd' needs updating - please use bus_type methods
  Driver 'sr' needs updating - please use bus_type methods
are harmless.

The Bug at
  COSCSI: response: use_sg (2) > 1!
is more a real problem. There a variable has two buffers, but the caller
of function only should fill a single buffer, and the function can only run
with a single buffer. If that bug line was triggered, then something is
real wrong. I will try to replace the "panic" into a "warning". So we would
see the stack backtrace from callers.




----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2890857&group_id=98788

[coLinux-devel] [ colinux-Bugs-2893343 ] host BSOD on with 20091105

[SourceForge.net <no...@so...>]

Bugs item #2893343, was opened at 2009-11-06 16:25
Message generated for change (Comment added) made by henryn
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2893343&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: Crash / BSOD
Group: v0.8.x (devel)
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: host BSOD on with 20091105

Initial Comment:
with snapshot 0.8.0-20091105, the host got BSOD. no problem with 0.8.0-20090905.
downloaded from http://www.colinux.org/snapshots/
os: windows xp sp3 with all hotfix installed

i have retried many time, double check file permission, no luck

----------------------------------------------------------------------

>Comment By: Henry N. (henryn)
Date: 2009-11-06 21:43

Message:
Do clean upgrade steps by step:
* Download archive "daemons-0.8.0-20091105.zip" form:
http://www.henrynestler.com/colinux/testing/devel-0.8.0/20091105-Snapshot/packages/
* Unpack all the files into new directory, for example to
c:\coLinux-2.6.25
* Copy your colinux config file or your BAT file from old installation
into the new directory. Edit the new config- or bat- file and add the full
path for your image files (cobd, scsi or hda). - If you not have used full
path names before.
* Remove or comment out the "initrd=initrd.gz" from config, and save the
config.
* Stop all running colinux
* Open command prompt on old installation directory
* Remove the driver
  colinux-daemon --remove-driver
* Check, that the driver is truely removed:
  colinux-daemon --status-driver
* Reboot your windows now!
* Open command prompt on the new directory and perform the manual
install:
  colinux-daemon --install-driver
* Reboot your Windows now!
  (This step is need, if the start would crash at next step.)
* Run your new colinux versioon from new directory.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2893343&group_id=98788

[coLinux-devel] [ colinux-Bugs-2893417 ] host BSOD on with 20091105 - ID: 2893343

[SourceForge.net <no...@so...>]

Bugs item #2893417, was opened at 2009-11-06 18:49
Message generated for change (Settings changed) made by peter_kuznetsov
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2893417&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: None
>Status: Deleted
Resolution: None
Priority: 5
Private: No
Submitted By: Peter Kuznetsov (peter_kuznetsov)
Assigned to: Nobody/Anonymous (nobody)
Summary: host BSOD on with 20091105 - ID: 2893343

Initial Comment:
I've had the same problem, but now it works fine.
Try to do next:
1. Make copy of your working image.
2. Add this copy as second image to config file or command line of colinux-daemon.exe in old coLinux directory.
3. Start your working coLinux and remove /lib/modules/2.6.25.20-co-0.8.0 folder from copy of the image. 
4. Set this copy as root image for version 20091105.
5. If you install version 20091105 from packages, rename 'modules-2.6.25.20-co-0.8.0-20091105.tgz' to 'vmlinux-modules.tar.gz'.
6. Add line  'initrd=initrd.gz' to coLinux config file or command line of colinux-daemon.exe
7. Start new version.

Peter.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2893417&group_id=98788

[coLinux-devel] [ colinux-Bugs-2893417 ] host BSOD on with 20091105 - ID: 2893343

[SourceForge.net <no...@so...>]

Bugs item #2893417, was opened at 2009-11-06 18:49
Message generated for change (Tracker Item Submitted) made by peter_kuznetsov
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2893417&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: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Peter Kuznetsov (peter_kuznetsov)
Assigned to: Nobody/Anonymous (nobody)
Summary: host BSOD on with 20091105 - ID: 2893343

Initial Comment:
I've had the same problem, but now it works fine.
Try to do next:
1. Make copy of your working image.
2. Add this copy as second image to config file or command line of colinux-daemon.exe in old coLinux directory.
3. Start your working coLinux and remove /lib/modules/2.6.25.20-co-0.8.0 folder from copy of the image. 
4. Set this copy as root image for version 20091105.
5. If you install version 20091105 from packages, rename 'modules-2.6.25.20-co-0.8.0-20091105.tgz' to 'vmlinux-modules.tar.gz'.
6. Add line  'initrd=initrd.gz' to coLinux config file or command line of colinux-daemon.exe
7. Start new version.

Peter.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2893417&group_id=98788

[coLinux-devel] [ colinux-Bugs-2893343 ] host BSOD on with 20091105

[SourceForge.net <no...@so...>]

Bugs item #2893343, was opened at 2009-11-06 15:25
Message generated for change (Tracker Item Submitted) made by nobody
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2893343&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: Crash / BSOD
Group: v0.8.x (devel)
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: host BSOD on with 20091105

Initial Comment:
with snapshot 0.8.0-20091105, the host got BSOD. no problem with 0.8.0-20090905.
downloaded from http://www.colinux.org/snapshots/
os: windows xp sp3 with all hotfix installed

i have retried many time, double check file permission, no luck

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2893343&group_id=98788

[coLinux-devel] [ colinux-Feature Requests-2891618 ] Driver name as parameter

[SourceForge.net <no...@so...>]

Feature Requests item #2891618, was opened at 2009-11-04 04:11
Message generated for change (Tracker Item Submitted) made by peter_kuznetsov
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=622066&aid=2891618&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: Interface Improvements (example)
Group: Next Release (example)
Status: Open
Priority: 5
Private: No
Submitted By: Peter Kuznetsov (peter_kuznetsov)
Assigned to: Nobody/Anonymous (nobody)
Summary: Driver name as parameter

Initial Comment:
For debuging purposes it will be very usefull to add options for changing driver  name instead of linux.sys.
Example:
  colinux-daemon.exe --remove-driver-name colinux-0.80-00.sys
  colinux-daemon.exe --install-driver-name colinux-0.80-01.sys



----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=622066&aid=2891618&group_id=98788

[coLinux-devel] [ colinux-Bugs-2890857 ] coLinux error in SCSI-driver with DVD-image?

[SourceForge.net <no...@so...>]

Bugs item #2890857, was opened at 2009-11-02 20:32
Message generated for change (Comment added) made by peter_kuznetsov
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2890857&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: Crash / BSOD
Group: None
>Status: Closed
Resolution: None
Priority: 5
Private: No
Submitted By: Peter Kuznetsov (peter_kuznetsov)
Assigned to: Nobody/Anonymous (nobody)
Summary: coLinux error in SCSI-driver with DVD-image?

Initial Comment:

Summary.
=======
Version 0.8.0 with kernel 2.6.25.20: 
  ...
  Driver 'sd' needs updating - please use bus_type methods
  Driver 'sr' needs updating - please use bus_type methods
  ...
  scsi1: unhandled opcode: 51
  ...
  Kernel panic - not syncing: COSCSI: response: use_sg (2) > 1!

Version 0.8.0 with kernel 2.6.22.18:
Version 0.7.5:
Version 0.7.4:
  ...
  scsi1: unhandled opcode: 5a
  scsi1: unhandled opcode: 51
  ...
  (System continue working)

Version 0.7.3:
Version 0.7.2:
  Don't work.

Some details.
============
  File "run.bat":
  --------------
    set COLINUX_CONSOLE_FONT=Lucida Console:12
    set COLINUX_CONSOLE_EXIT_ON_DETACH=1

    colinux-daemon.exe --remove-driver
    colinux-daemon.exe --install-driver

    colinux-daemon.exe @config.cfg -v 3 -t nt

    colinux-daemon.exe --remove-driver

  File "config.cfg":
  ----------------
    cocon=160x79

    mem=512

    kernel=vmlinux
    initrd=initrd.gz

    # Flat part of vmdk (with MBR)
    scsi0=disk,"Debian-5.0.3-KDE-00.flat"  
    scsi1=disk,"O:\VIRT_DISK\VDISKS\swap_scsi_0.flat"  # flat part of vmdk
    scsi2=cdrom,"J:\OS\Linux\$DEBIAN\Debian\5.0.3\debian-503-i386-DVD-1.iso"

    root=/dev/sda1
    ro

    eth0=slirp

  File "/etc/fstab" (without editing after installation):
  ----------------
    # /etc/fstab: static file system information.
    #
    # <file system> <mount point>   <type>  <options>       <dump>  <pass>
    proc            /proc           proc    defaults        0       0
    /dev/sda1       /               ext3    errors=remount-ro 0       1
    /dev/sdb1       none            swap    sw              0       0
    /dev/scd0       /media/cdrom0   udf,iso9660 user,noauto     0       0
    /dev/fd0        /media/floppy0  auto    rw,user,noauto  0       0

  In whole system after installation I've edited only one file "/etc/X11/default-display-manager":
    #/usr/bin/kdm
    echo "null" > /etc/X11/default-display-manager 

Relevant output.
===============
  Version 0.8.0 with kernel 2.6.25.20 (kernel panic): 
  --------------------------------------------------
    scsi0 : Cooperative Linux SCSI Adapter
    scsi 0:0:0:0: Direct-Access     coLinux  CODISK           1.01 PQ: 0 ANSI: 5
    scsi 0:0:1:0: Direct-Access     coLinux  CODISK           1.01 PQ: 0 ANSI: 5
    scsi 0:0:2:0: CD-ROM            coLinux  COCD             1.01 PQ: 0 ANSI: 2
    Driver 'sd' needs updating - please use bus_type methods   <----------------------PK!!!
    sd 0:0:0:0: [sda] 6291456 512-byte hardware sectors (3221 MB)
    sd 0:0:0:0: [sda] Write Protect is off
    sd 0:0:0:0: [sda] Mode Sense: 1f 00 10 08
    sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA
    sd 0:0:0:0: [sda] 6291456 512-byte hardware sectors (3221 MB)
    sd 0:0:0:0: [sda] Write Protect is off
    sd 0:0:0:0: [sda] Mode Sense: 1f 00 10 08
    sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA
     sda: sda1
    sd 0:0:0:0: [sda] Attached SCSI disk
    sd 0:0:1:0: [sdb] 4194304 512-byte hardware sectors (2147 MB)
    sd 0:0:1:0: [sdb] Write Protect is off
    sd 0:0:1:0: [sdb] Mode Sense: 1f 00 10 08
    sd 0:0:1:0: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA
    sd 0:0:1:0: [sdb] 4194304 512-byte hardware sectors (2147 MB)
    sd 0:0:1:0: [sdb] Write Protect is off
    sd 0:0:1:0: [sdb] Mode Sense: 1f 00 10 08
    sd 0:0:1:0: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA
     sdb: sdb1
    sd 0:0:1:0: [sdb] Attached SCSI disk
    Driver 'sr' needs updating - please use bus_type methods   <----------------------PK!!!
    sr0: scsi3-mmc drive: 32x/32x cd/rw xa/form2 cdda tray
    Uniform CD-ROM driver Revision: 3.20
    sr 0:0:2:0: Attached scsi CD-ROM sr0
    ...
    scsi2: unhandled opcode: 51
    sd 0:0:0:0: Attached scsi generic sg0 type 0
    sd 0:0:1:0: Attached scsi generic sg1 type 0
    sr 0:0:2:0: Attached scsi generic sg2 type 5
    scsi2: unhandled opcode: 51
    ...
    Kernel panic - not syncing: COSCSI: response: use_sg (2) > 1! <-------------------PK!!!

    colinux: Linux VM terminated
    colinux: Kernel panic: COSCSI: response: use_sg (2) > 1!

    console: Monitor3116: Detached

    Q:\coLinux\$Debian\Debian\5.0.3-co-080_2.6.25.20>colinux-daemon.exe --remove-driver
    Cooperative Linux Daemon, 0.8.0
    Daemon compiled on Sun Sep 27 12:50:20 2009

    ============================================================================

  Version 0.8.0 with kernel 2.6.22.18 (working):
  ---------------------------------------------
    scsi0 : Cooperative Linux SCSI Adapter
    scsi 0:0:0:0: Direct-Access     coLinux  CODISK           1.01 PQ: 0 ANSI: 5
    scsi 0:0:1:0: Direct-Access     coLinux  CODISK           1.01 PQ: 0 ANSI: 5
    scsi 0:0:2:0: CD-ROM            coLinux  COCD             1.01 PQ: 0 ANSI: 2
    sd 0:0:0:0: [sda] 6291456 512-byte hardware sectors (3221 MB)
    sd 0:0:0:0: [sda] Write Protect is off
    sd 0:0:0:0: [sda] Mode Sense: 1f 00 10 08
    sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA
    sd 0:0:0:0: [sda] 6291456 512-byte hardware sectors (3221 MB)
    sd 0:0:0:0: [sda] Write Protect is off
    sd 0:0:0:0: [sda] Mode Sense: 1f 00 10 08
    sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA
     sda: sda1
    sd 0:0:0:0: [sda] Attached SCSI disk
    sd 0:0:1:0: [sdb] 4194304 512-byte hardware sectors (2147 MB)
    sd 0:0:1:0: [sdb] Write Protect is off
    sd 0:0:1:0: [sdb] Mode Sense: 1f 00 10 08
    sd 0:0:1:0: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA
    sd 0:0:1:0: [sdb] 4194304 512-byte hardware sectors (2147 MB)
    sd 0:0:1:0: [sdb] Write Protect is off
    sd 0:0:1:0: [sdb] Mode Sense: 1f 00 10 08
    sd 0:0:1:0: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA
     sdb: sdb1
    sd 0:0:1:0: [sdb] Attached SCSI disk
    sr0: scsi3-mmc drive: 32x/32x cd/rw xa/form2 cdda tray
    Uniform CD-ROM driver Revision: 3.20
    sr 0:0:2:0: Attached scsi CD-ROM sr0
    .......................................
    scsi2: unhandled opcode: 51                                   <-------------------PK!!!
    sd 0:0:0:0: Attached scsi generic sg0 type 0
    sd 0:0:1:0: Attached scsi generic sg1 type 0
    sr 0:0:2:0: Attached scsi generic sg2 type 5
    .......................................
    scsi2: unhandled opcode: 5a                                   <-------------------PK!!!
    scsi2: unhandled opcode: 51
    scsi2: unhandled opcode: 51
    scsi2: unhandled opcode: 5a
    scsi2: unhandled opcode: 5a
    ...
    sd 0:0:1:0: [sdb] Synchronizing SCSI cache
    sd 0:0:0:0: [sda] Synchronizing SCSI cache

    ===============================================================================

    If you need some additional testing of coLinux-0.8.0 with kernel 2.6.25.20, mail me, I can do it. 
    Many thanks for very usefull system!!!

    With best regards, Peter.


----------------------------------------------------------------------

>Comment By: Peter Kuznetsov (peter_kuznetsov)
Date: 2009-11-03 23:39

Message:
Henry, 
I close this  tracker and will wait for next autobuild with kernel
2.6.25.20 (it is closer to 2.6.26.2, which is used in Debian 5.0.3).

With many thanks, Peter.

----------------------------------------------------------------------

Comment By: Henry N. (henryn)
Date: 2009-11-03 22:58

Message:
The warnings
  Driver 'sd' needs updating - please use bus_type methods
  Driver 'sr' needs updating - please use bus_type methods
are harmless.

The Bug at
  COSCSI: response: use_sg (2) > 1!
is more a real problem. There a variable has two buffers, but the caller
of function only should fill a single buffer, and the function can only run
with a single buffer. If that bug line was triggered, then something is
real wrong. I will try to replace the "panic" into a "warning". So we would
see the stack backtrace from callers.




----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2890857&group_id=98788

[coLinux-devel] [ colinux-Bugs-2890857 ] coLinux error in SCSI-driver with DVD-image?

[SourceForge.net <no...@so...>]

Bugs item #2890857, was opened at 2009-11-02 19:32
Message generated for change (Comment added) made by henryn
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2890857&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: Crash / BSOD
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Peter Kuznetsov (peter_kuznetsov)
Assigned to: Nobody/Anonymous (nobody)
Summary: coLinux error in SCSI-driver with DVD-image?

Initial Comment:

Summary.
=======
Version 0.8.0 with kernel 2.6.25.20: 
  ...
  Driver 'sd' needs updating - please use bus_type methods
  Driver 'sr' needs updating - please use bus_type methods
  ...
  scsi1: unhandled opcode: 51
  ...
  Kernel panic - not syncing: COSCSI: response: use_sg (2) > 1!

Version 0.8.0 with kernel 2.6.22.18:
Version 0.7.5:
Version 0.7.4:
  ...
  scsi1: unhandled opcode: 5a
  scsi1: unhandled opcode: 51
  ...
  (System continue working)

Version 0.7.3:
Version 0.7.2:
  Don't work.

Some details.
============
  File "run.bat":
  --------------
    set COLINUX_CONSOLE_FONT=Lucida Console:12
    set COLINUX_CONSOLE_EXIT_ON_DETACH=1

    colinux-daemon.exe --remove-driver
    colinux-daemon.exe --install-driver

    colinux-daemon.exe @config.cfg -v 3 -t nt

    colinux-daemon.exe --remove-driver

  File "config.cfg":
  ----------------
    cocon=160x79

    mem=512

    kernel=vmlinux
    initrd=initrd.gz

    # Flat part of vmdk (with MBR)
    scsi0=disk,"Debian-5.0.3-KDE-00.flat"  
    scsi1=disk,"O:\VIRT_DISK\VDISKS\swap_scsi_0.flat"  # flat part of vmdk
    scsi2=cdrom,"J:\OS\Linux\$DEBIAN\Debian\5.0.3\debian-503-i386-DVD-1.iso"

    root=/dev/sda1
    ro

    eth0=slirp

  File "/etc/fstab" (without editing after installation):
  ----------------
    # /etc/fstab: static file system information.
    #
    # <file system> <mount point>   <type>  <options>       <dump>  <pass>
    proc            /proc           proc    defaults        0       0
    /dev/sda1       /               ext3    errors=remount-ro 0       1
    /dev/sdb1       none            swap    sw              0       0
    /dev/scd0       /media/cdrom0   udf,iso9660 user,noauto     0       0
    /dev/fd0        /media/floppy0  auto    rw,user,noauto  0       0

  In whole system after installation I've edited only one file "/etc/X11/default-display-manager":
    #/usr/bin/kdm
    echo "null" > /etc/X11/default-display-manager 

Relevant output.
===============
  Version 0.8.0 with kernel 2.6.25.20 (kernel panic): 
  --------------------------------------------------
    scsi0 : Cooperative Linux SCSI Adapter
    scsi 0:0:0:0: Direct-Access     coLinux  CODISK           1.01 PQ: 0 ANSI: 5
    scsi 0:0:1:0: Direct-Access     coLinux  CODISK           1.01 PQ: 0 ANSI: 5
    scsi 0:0:2:0: CD-ROM            coLinux  COCD             1.01 PQ: 0 ANSI: 2
    Driver 'sd' needs updating - please use bus_type methods   <----------------------PK!!!
    sd 0:0:0:0: [sda] 6291456 512-byte hardware sectors (3221 MB)
    sd 0:0:0:0: [sda] Write Protect is off
    sd 0:0:0:0: [sda] Mode Sense: 1f 00 10 08
    sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA
    sd 0:0:0:0: [sda] 6291456 512-byte hardware sectors (3221 MB)
    sd 0:0:0:0: [sda] Write Protect is off
    sd 0:0:0:0: [sda] Mode Sense: 1f 00 10 08
    sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA
     sda: sda1
    sd 0:0:0:0: [sda] Attached SCSI disk
    sd 0:0:1:0: [sdb] 4194304 512-byte hardware sectors (2147 MB)
    sd 0:0:1:0: [sdb] Write Protect is off
    sd 0:0:1:0: [sdb] Mode Sense: 1f 00 10 08
    sd 0:0:1:0: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA
    sd 0:0:1:0: [sdb] 4194304 512-byte hardware sectors (2147 MB)
    sd 0:0:1:0: [sdb] Write Protect is off
    sd 0:0:1:0: [sdb] Mode Sense: 1f 00 10 08
    sd 0:0:1:0: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA
     sdb: sdb1
    sd 0:0:1:0: [sdb] Attached SCSI disk
    Driver 'sr' needs updating - please use bus_type methods   <----------------------PK!!!
    sr0: scsi3-mmc drive: 32x/32x cd/rw xa/form2 cdda tray
    Uniform CD-ROM driver Revision: 3.20
    sr 0:0:2:0: Attached scsi CD-ROM sr0
    ...
    scsi2: unhandled opcode: 51
    sd 0:0:0:0: Attached scsi generic sg0 type 0
    sd 0:0:1:0: Attached scsi generic sg1 type 0
    sr 0:0:2:0: Attached scsi generic sg2 type 5
    scsi2: unhandled opcode: 51
    ...
    Kernel panic - not syncing: COSCSI: response: use_sg (2) > 1! <-------------------PK!!!

    colinux: Linux VM terminated
    colinux: Kernel panic: COSCSI: response: use_sg (2) > 1!

    console: Monitor3116: Detached

    Q:\coLinux\$Debian\Debian\5.0.3-co-080_2.6.25.20>colinux-daemon.exe --remove-driver
    Cooperative Linux Daemon, 0.8.0
    Daemon compiled on Sun Sep 27 12:50:20 2009

    ============================================================================

  Version 0.8.0 with kernel 2.6.22.18 (working):
  ---------------------------------------------
    scsi0 : Cooperative Linux SCSI Adapter
    scsi 0:0:0:0: Direct-Access     coLinux  CODISK           1.01 PQ: 0 ANSI: 5
    scsi 0:0:1:0: Direct-Access     coLinux  CODISK           1.01 PQ: 0 ANSI: 5
    scsi 0:0:2:0: CD-ROM            coLinux  COCD             1.01 PQ: 0 ANSI: 2
    sd 0:0:0:0: [sda] 6291456 512-byte hardware sectors (3221 MB)
    sd 0:0:0:0: [sda] Write Protect is off
    sd 0:0:0:0: [sda] Mode Sense: 1f 00 10 08
    sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA
    sd 0:0:0:0: [sda] 6291456 512-byte hardware sectors (3221 MB)
    sd 0:0:0:0: [sda] Write Protect is off
    sd 0:0:0:0: [sda] Mode Sense: 1f 00 10 08
    sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA
     sda: sda1
    sd 0:0:0:0: [sda] Attached SCSI disk
    sd 0:0:1:0: [sdb] 4194304 512-byte hardware sectors (2147 MB)
    sd 0:0:1:0: [sdb] Write Protect is off
    sd 0:0:1:0: [sdb] Mode Sense: 1f 00 10 08
    sd 0:0:1:0: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA
    sd 0:0:1:0: [sdb] 4194304 512-byte hardware sectors (2147 MB)
    sd 0:0:1:0: [sdb] Write Protect is off
    sd 0:0:1:0: [sdb] Mode Sense: 1f 00 10 08
    sd 0:0:1:0: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA
     sdb: sdb1
    sd 0:0:1:0: [sdb] Attached SCSI disk
    sr0: scsi3-mmc drive: 32x/32x cd/rw xa/form2 cdda tray
    Uniform CD-ROM driver Revision: 3.20
    sr 0:0:2:0: Attached scsi CD-ROM sr0
    .......................................
    scsi2: unhandled opcode: 51                                   <-------------------PK!!!
    sd 0:0:0:0: Attached scsi generic sg0 type 0
    sd 0:0:1:0: Attached scsi generic sg1 type 0
    sr 0:0:2:0: Attached scsi generic sg2 type 5
    .......................................
    scsi2: unhandled opcode: 5a                                   <-------------------PK!!!
    scsi2: unhandled opcode: 51
    scsi2: unhandled opcode: 51
    scsi2: unhandled opcode: 5a
    scsi2: unhandled opcode: 5a
    ...
    sd 0:0:1:0: [sdb] Synchronizing SCSI cache
    sd 0:0:0:0: [sda] Synchronizing SCSI cache

    ===============================================================================

    If you need some additional testing of coLinux-0.8.0 with kernel 2.6.25.20, mail me, I can do it. 
    Many thanks for very usefull system!!!

    With best regards, Peter.


----------------------------------------------------------------------

>Comment By: Henry N. (henryn)
Date: 2009-11-03 21:58

Message:
The warnings
  Driver 'sd' needs updating - please use bus_type methods
  Driver 'sr' needs updating - please use bus_type methods
are harmless.

The Bug at
  COSCSI: response: use_sg (2) > 1!
is more a real problem. There a variable has two buffers, but the caller
of function only should fill a single buffer, and the function can only run
with a single buffer. If that bug line was triggered, then something is
real wrong. I will try to replace the "panic" into a "warning". So we would
see the stack backtrace from callers.




----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2890857&group_id=98788