Bug reporting thread

[ronaldlees]

Hi Andy:

I bet you're BWB (busy with the baby). Congrats again!

I transferred the USB image for VIsOpSys version 0.8 to a mem stick, and ran it on real hardware (~5 year old ASUS Mini). It boots fine, displays the "install vs run" dialog, and displays the desktop when I bump the enter key. But it seems to be ignoring my mouse. I can use the tab key to navigate, and then run a command terminal, and view the /system/kernel.log file. I cut and pasted a few snippets (below), that were taken from kernel.log, but I see nothing amiss in the log that references the mouse (it's a Logitech USB mouse).

Is there a way to attach a file to this post? I could send you the entire kernel log. I always roll my eyes when I see people posting long logs on forums, and here I am doing it! Anyway, when I execute the ps utility, I can see that it says the mouse thread is running OK (with about 12% CPU usage). Any ideas?

/system/kernel.log (snippets) :

Code: Select all

Visopsys 0.8
Copyright (C) 1998-2016 J. Andrew McLaughlin
OS Loader: CPU type=2
OS Loader: CPU vendor=
OS Loader: MMS extensions=yes
OS Loader: Extended mem=1833536K
...

More snippets:

Code: Select all

Oct 10 13:47:50 2016 Measuring CPU timestamp frequency
Oct 10 13:47:50 2016 CPU timestamp frequency is 2812 MHz
Oct 10 13:47:50 2016 real-time clock (RTC) device detected
Oct 10 13:47:50 2016 DMA controller device detected
Oct 10 13:47:50 2016 PCI: RAM memory controller 0:0:0 vend:0x10de dev:0x03e2
Oct 10 13:47:50 2016   class:0x05 sub:0x00 int:0 pin=  caps=yes
Oct 10 13:47:50 2016 PCI: ISA bridge device 0:1:0 vend:0x10de dev:0x03e1
Oct 10 13:47:50 2016   class:0x06 sub:0x01 int:0 pin=  caps=no
Oct 10 13:47:50 2016 PCI: SMBus serial bus 0:1:1 vend:0x10de dev:0x03eb
Oct 10 13:47:50 2016   class:0x0c sub:0x05 int:10 pin=A caps=yes
Oct 10 13:47:50 2016 PCI: RAM memory controller 0:1:2 vend:0x10de dev:0x03f5
Oct 10 13:47:50 2016   class:0x05 sub:0x00 int:0 pin=  caps=no
Oct 10 13:47:50 2016 PCI: USB serial bus 0:2:0 vend:0x10de dev:0x03f1
Oct 10 13:47:50 2016   class:0x0c sub:0x03 int:5 pin=A caps=yes
Oct 10 13:47:50 2016 PCI: USB serial bus 0:2:1 vend:0x10de dev:0x03f2
Oct 10 13:47:50 2016   class:0x0c sub:0x03 int:11 pin=B caps=yes
Oct 10 13:47:50 2016 PCI: PCI/PCI bridge device 0:4:0 vend:0x10de dev:0x03f3
...

More snippets:

Code: Select all

Oct 10 13:47:50 2016 USB: EHCI controller USB 2.0 interrupt 11
Oct 10 13:47:51 2016 USB bus controller device detected
Oct 10 13:47:51 2016 USB: OHCI controller USB 1.0 interrupt 5
Oct 10 13:47:51 2016 USB bus controller device detected
Oct 10 13:47:51 2016 USB: SCSI mass storage 0:1 dev:3307, vend:03f0, class:08, sub:06 proto:50 usb:2.0
Oct 10 13:47:51 2016 Found PCI/ISA bridge
Oct 10 13:47:51 2016 ISA bridge device detected
Oct 10 13:47:51 2016 PS/2 keyboard device detected
Oct 10 13:47:52 2016 "hp v125w" SCSI disk device detected
Oct 10 13:47:52 2016 AHCI: Searching for controllers
Oct 10 13:47:52 2016 IDE: Searching for controllers
Oct 10 13:47:52 2016 IDE: Bus mastering PCI controller enabled
Oct 10 13:47:52 2016 IDE disk controller device detected
Oct 10 13:47:52 2016 Multitasking started
...

More snippets:

Code: Select all

Oct 10 13:47:52 2016 Disk sd0a (hard disk sd0, primary): fat16
Oct 10 13:47:52 2016 Mounting / filesystem on disk sd0a
Oct 10 13:47:52 2016 Loaded mouse pointer default from file /system/mouse/default.bmp
Oct 10 13:47:52 2016 Loaded mouse pointer busy from file /system/mouse/busy.ico
Oct 10 13:47:52 2016 Loaded mouse pointer resizeh from file /system/mouse/resizeh.bmp
Oct 10 13:47:52 2016 Loaded mouse pointer resizev from file /system/mouse/resizev.bmp
...
Oct 10 14:09:34 2016 Stopping kernel logging

[ronaldlees]

One other thing Andy:

I really like the new window decorations. The window icons look nice and crisp on my 1280x1024 screen.

I suppose I could hook up a serial cable, and try to get more debug info for you. One of the last messages in the kernel.log file was "kernel logging stopped". So - does VisOpSys still echo the logging to the serial port after boot? Or is it doing that only when using a debug image?

Finally I did see some log entries in /system/kernel.log that might point to the issue:

Code: Select all

Oct 10 16:02:12 2016 Starting window system initialization
Oct 10 16:02:12 2016 USB: keyboard human interface device 1:1 dev:c52b, vend:046d, class:03, sub:01 proto:01 usb:2.0
Oct 10 16:02:12 2016 USB keyboard device detected
Oct 10 16:02:12 2016 USB mouse device detected
Oct 10 16:02:12 2016 Window thread started
Oct 10 16:02:12 2016 Window system initialization complete
Oct 10 16:02:29 2016 Background image loaded
Oct 10 16:02:29 2016 Task menu initialized
Oct 10 16:02:29 2016 Desktop icons loaded
Oct 10 16:02:12 2016 USB keyboard device detected
Oct 10 16:02:12 2016 USB mouse device detected
Oct 10 16:02:12 2016 Window thread started
Oct 10 16:02:12 2016 Window system initialization complete
Oct 10 16:03:49 2016 Error:usb thread:kernelUsbOhciDriver.c:waitTransactionComplete(749):
Oct 10 16:03:49 2016 Transaction timed out
Oct 10 16:03:49 2016 Error:usb thread:kernelUsbDriver.c:kernelUsbDevConnect(1150):
Oct 10 16:03:49 2016 Error getting short configuration descriptor

system initialization complete
Oct 10 16:04:10 2016 Error:usb thread:kernelPage.c:findPageTableEntry(443):
Oct 10 16:04:10 2016 No page table 0
Oct 10 16:04:10 2016 Error:usb thread:kernelPage.c:kernelPageGetPhysical(1558):
Oct 10 16:04:10 2016 No page table entry for address 0x00001000
Oct 10 16:04:10 2016 Error:usb thread:kernelMemory.c:kernelMemoryRelease(878):
Oct 10 16:04:10 2016 The memory pointer is not mapped
Oct 10 16:04:10 2016 Error:usb thread:malloc.c:deallocateBlock(577):
Oct 10 16:04:10 2016 No such memory block c01c86a8 to deallocate (removeDeviceRecursive)
d:kernelPage.c:findPageTableEntry(443):

[qmastery]

.

Good day, Andy! A couple of bug reports; this is the first message
(+ now with a proposed help-floppy.txt attached )

"help" command prints a quite long list of commands, however not all of these commands are available at the floppy version. Perhaps you've decided to keep the unavailable command descriptions at "help" just in case someone modifies their Visopsys floppy to include some new commands or replace some of existing commands with other commands which aren't a part of a floppy build by default. But it is inconvenient for the users (especially newcomers) when they go through this list of commands and trying to launch them only to receive the many Unknown command "...". messages. I propose shortening this list to the commands which are really available (see the list below, hopefully everything is correct there), or at least somehow marking the unavailable commands (e.g. putting (n/f) - "not floppy" - before their names)

Second message - "Initialization failed" bug report - is at this thread - https://visopsys.org/forums/viewtopic.p ... 1440#p1440

[andymc]

Hello qmastery,

I think maybe a good, lazy way for me to do this would be for the help command to look for a binary in the $PATH, corresponding to the first column of each line, and not print lines when it can't find the command. It would be more work up-front, coding that, but it wouldn't need maintenance after that.

Right now, I maintain by hand the /system/install-files.* lists of things that get installed for 'basic' (e.g. floppy) and 'full' installs. Beyond that, I'd prefer to keep everything automated!

But also, I've developed a new software packaging/installing suite for release with 0.9, and it would be good for the 'help' command to be able to adapt on the fly to what's actually installed on the system. It will be a bit more work for it to be able to add new things dynamically, but automation seems like the way to go in that respect, also.

I'll write something on my to-do list

Andy

[sadse]

Hi, I stumbled on a major problem.
The common trick to get the size of a file:

Code: Select all

int sz;
fseek(myFile, 0, SEEK_END);
sz = ftell(myFile);
fseek(myFile, 0, SEEK_SET);

doesn't work, and reports that it is impossible to seek beyond a file..

For now, the most reliable workaround I've found is getting the size of a file by using
internal structure members, in this way:

Code: Select all

sz = myFile->f.size;

this will work, but this isn't portable and internal structure members may change in the future.

You are putting wrong parameters to fseek. Check again

[andymc]

"help" command prints a quite long list of commands, however not all of these commands are available at the floppy version. Perhaps you've decided to keep the unavailable command descriptions at "help" just in case someone modifies their Visopsys floppy to include some new commands or replace some of existing commands with other commands which aren't a part of a floppy build by default. But it is inconvenient for the users (especially newcomers) when they go through this list of commands and trying to launch them only to receive the many Unknown command "...". messages. I propose shortening this list to the commands which are really available (see the list below, hopefully everything is correct there), or at least somehow marking the unavailable commands (e.g. putting (n/f) - "not floppy" - before their names)

Hello qmastery,

This is done now, for release in 0.84 or 0.9 (whichever comes first!). The 'help' program now searches the $PATH for commands, and only prints lines for the ones it finds.

So you can, for example, delete a /programs/ binary by hand, and see that it's no longer listed when you type 'help'.

Andy

[qmastery]

This is done now, for release in 0.84 or 0.9 (whichever comes first!)

Huge thanks to you, Andy! I am going to make a 2.88MB Visopsys floppy sometime in the future (since this rare "ED" floppy format is also supported by coreboot/SeaBIOS ) and your change will be really helpful for making it user-friendly! By the way, do you have any news about https://visopsys.org/forums/viewtopic.p ... t=10#p1463 ? I could test your debug builds

[andymc]

By the way, do you have any news about https://visopsys.org/forums/viewtopic.p ... t=10#p1463 ? I could test your debug builds

Sorry mate I wish I could say I'd started on this, but right now I'm pushing to finish the 0.9 features that I've been promising for so long. I imagine that I'm still a couple of months away from finishing all that. I usually only have 2-3 hours to work on this in the evenings. I'm finishing some DIY home renovations, and I also have a new daughter arriving in the next 48 hours or so I do what I can!

[qmastery]

I also have a new daughter arriving in the next 48 hours or so

wow Andy, my sincere congratulations to you !

[dufresnep]

At first, looping with errors, finally offers install or continue...
works fine with continue (but had to use virtual keyboard rather than the usb keyboard.
usb mouse works fine.


kernel.log extract:

Visopsys 0.84
Copyright (C) 1998-2019 J. Andrew McLaughlin
OS Loader: Extended mem=3144320K
OS Loader: memory range available: 0x00000000-0x0009fbff (0K->638K)
OS Loader: memory range reserved: 0x0009fc00-0x0009ffff (639K->639K)
OS Loader: memory range reserved: 0x000e4000-0x000fffff (912K->1023K)
OS Loader: memory range available: 0x00100000-0xbff9ffff (1024K->3145343K)
OS Loader: memory range acpi reclaim: 0xbffa0000-0xbffadfff (3145344K->3145399K)
OS Loader: memory range acpi nvs: 0xbffae000-0xbffdffff (3145400K->3145599K)
OS Loader: memory range reserved: 0xbffe0000-0xbffeffff (3145600K->3145663K)
OS Loader: memory range reserved: 0xbfff0000-0xbfffffff (3145664K->3145727K)
OS Loader: memory range reserved: 0xfee00000-0xfee00fff (4175872K->4175875K)
OS Loader: memory range reserved: 0xfff00000-0xffffffff (4193280K->4194303K)
OS Loader: memory range available: 0x00000000-0x3fffffff (4194304K->5242879K)
OS Loader: video memory=14336K
OS Loader: video framebuffer=0xcf000000
OS Loader: video mode=0x118: 1024x768 @32bpp
OS Loader: video supported modes=10
OS Loader: video supports mode 0x111=640x480 @16bpp
OS Loader: video supports mode 0x112=640x480 @32bpp
OS Loader: video supports mode 0x114=800x600 @16bpp
OS Loader: video supports mode 0x115=800x600 @32bpp
OS Loader: video supports mode 0x117=1024x768 @16bpp
OS Loader: video supports mode 0x118=1024x768 @32bpp
OS Loader: video supports mode 0x11a=1280x1024 @16bpp
OS Loader: video supports mode 0x11b=1280x1024 @32bpp
OS Loader: video supports mode 0x146=1600x1200 @16bpp
OS Loader: video supports mode 0x14a=1600x1200 @32bpp
OS Loader: boot signature=0x5cdb5a8b
OS Loader: boot from CD: no
OS Loader: floppy disks=0
"Intel Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz" x86_64 CPU device detected
memory device detected
32-bit BIOS found at 0x000f0000, entry point 0x000f0010
BIOS (32-bit) device detected
Plug and Play BIOS found at 0x000f8650
BIOS (Plug and Play) device detected
multiprocessor device detected
ACPI power management device detected
PIC interrupt controller device detected
APIC interrupt controller device detected
system timer device detected
Jul 27 21:26:21 2019 Measuring CPU timestamp frequency
Jul 27 21:26:22 2019 CPU timestamp frequency is 2399 MHz
Jul 27 21:26:22 2019 real-time clock (RTC) device detected
Jul 27 21:26:22 2019 DMA controller device detected
Jul 27 21:26:22 2019 PCI: host bridge device 0:0:0 vend:0x8086 dev:0x29c0
Jul 27 21:26:22 2019 class:0x06 sub:0x00 int:0 pin= caps=yes
Jul 27 21:26:22 2019 PCI: PCI/PCI bridge device 0:1:0 vend:0x8086 dev:0x29c1
Jul 27 21:26:22 2019 class:0x06 sub:0x04 int:16 pin=A caps=yes
Jul 27 21:26:22 2019 PCI: USB serial bus 0:26:0 vend:0x8086 dev:0x2937
Jul 27 21:26:22 2019 class:0x0c sub:0x03 int:16 pin=A caps=yes
Jul 27 21:26:22 2019 PCI: USB serial bus 0:26:1 vend:0x8086 dev:0x2938
Jul 27 21:26:22 2019 class:0x0c sub:0x03 int:21 pin=B caps=yes
Jul 27 21:26:22 2019 PCI: USB serial bus 0:26:7 vend:0x8086 dev:0x293c
Jul 27 21:26:22 2019 class:0x0c sub:0x03 int:18 pin=C caps=yes
Jul 27 21:26:22 2019 PCI: high-def audio multimedia controller 0:27:0 vend:0x8086 dev:0x293e
Jul 27 21:26:22 2019 class:0x04 sub:0x03 int:22 pin=A caps=yes
Jul 27 21:26:22 2019 PCI: PCI/PCI bridge device 0:28:0 vend:0x8086 dev:0x2940
Jul 27 21:26:22 2019 class:0x06 sub:0x04 int:17 pin=A caps=yes
Jul 27 21:26:22 2019 PCI: PCI/PCI bridge device 0:28:2 vend:0x8086 dev:0x2944
Jul 27 21:26:22 2019 class:0x06 sub:0x04 int:18 pin=C caps=yes
Jul 27 21:26:22 2019 PCI: USB serial bus 0:29:0 vend:0x8086 dev:0x2934
Jul 27 21:26:22 2019 class:0x0c sub:0x03 int:23 pin=A caps=yes
Jul 27 21:26:22 2019 PCI: USB serial bus 0:29:1 vend:0x8086 dev:0x2935
Jul 27 21:26:22 2019 class:0x0c sub:0x03 int:19 pin=B caps=yes
Jul 27 21:26:22 2019 PCI: USB serial bus 0:29:2 vend:0x8086 dev:0x2936
Jul 27 21:26:22 2019 class:0x0c sub:0x03 int:18 pin=C caps=yes
Jul 27 21:26:22 2019 PCI: USB serial bus 0:29:3 vend:0x8086 dev:0x2939
Jul 27 21:26:22 2019 class:0x0c sub:0x03 int:16 pin=D caps=yes
Jul 27 21:26:22 2019 PCI: USB serial bus 0:29:7 vend:0x8086 dev:0x293a
Jul 27 21:26:22 2019 class:0x0c sub:0x03 int:23 pin=A caps=yes
Jul 27 21:26:22 2019 PCI: PCI/PCI bridge device 0:30:0 vend:0x8086 dev:0x244e
Jul 27 21:26:22 2019 class:0x06 sub:0x04 int:0 pin= caps=yes
Jul 27 21:26:22 2019 PCI: ISA bridge device 0:31:0 vend:0x8086 dev:0x2916
Jul 27 21:26:22 2019 class:0x06 sub:0x01 int:0 pin= caps=yes
Jul 27 21:26:22 2019 PCI: IDE disk controller 0:31:2 vend:0x8086 dev:0x2920
Jul 27 21:26:22 2019 class:0x01 sub:0x01 int:19 pin=B caps=yes
Jul 27 21:26:22 2019 PCI: SMBus serial bus 0:31:3 vend:0x8086 dev:0x2930
Jul 27 21:26:22 2019 class:0x0c sub:0x05 int:18 pin=C caps=no
Jul 27 21:26:22 2019 PCI: IDE disk controller 0:31:5 vend:0x8086 dev:0x2926
Jul 27 21:26:22 2019 class:0x01 sub:0x01 int:19 pin=B caps=yes
Jul 27 21:26:22 2019 PCI: FireWire serial bus 1:5:0 vend:0x11c1 dev:0x5811
Jul 27 21:26:22 2019 class:0x0c sub:0x00 int:20 pin=A caps=yes
Jul 27 21:26:22 2019 PCI: ethernet network interface 2:0:0 vend:0x10ec dev:0x8168
Jul 27 21:26:22 2019 class:0x02 sub:0x00 int:18 pin=A caps=yes
Jul 27 21:26:22 2019 PCI: VGA graphics adapter 4:0:0 vend:0x10de dev:0x10c3
Jul 27 21:26:22 2019 class:0x03 sub:0x00 int:16 pin=A caps=yes
Jul 27 21:26:22 2019 PCI: high-def audio multimedia controller 4:0:1 vend:0x10de dev:0x0be3
Jul 27 21:26:22 2019 class:0x04 sub:0x03 int:17 pin=B caps=yes
Jul 27 21:26:22 2019 PCI bus controller device detected
Jul 27 21:26:22 2019 USB: EHCI controller USB 2.0 interrupt 18
Jul 27 21:26:22 2019 USB bus controller device detected
Jul 27 21:26:22 2019 USB: EHCI controller USB 2.0 interrupt 23
Jul 27 21:26:22 2019 USB bus controller device detected
Jul 27 21:26:22 2019 USB: UHCI controller USB 1.0 interrupt 16
Jul 27 21:26:22 2019 USB bus controller device detected
Jul 27 21:26:22 2019 USB: UHCI controller USB 1.0 interrupt 21
Jul 27 21:26:22 2019 USB bus controller device detected
Jul 27 21:26:22 2019 USB: UHCI controller USB 1.0 interrupt 23
Jul 27 21:26:22 2019 USB bus controller device detected
Jul 27 21:26:22 2019 USB: UHCI controller USB 1.0 interrupt 19
Jul 27 21:26:22 2019 USB bus controller device detected
Jul 27 21:26:22 2019 USB: UHCI controller USB 1.0 interrupt 18
Jul 27 21:26:22 2019 USB bus controller device detected
Jul 27 21:26:22 2019 USB: UHCI controller USB 1.0 interrupt 16
Jul 27 21:26:22 2019 USB bus controller device detected
Jul 27 21:26:23 2019 USB: SCSI mass storage 1:1 dev:0151, vend:0bda, class:08, sub:06 proto:50 usb:2.0
Jul 27 21:26:23 2019 USB: SCSI mass storage 1:2 dev:9380, vend:058f, class:08, sub:06 proto:50 usb:2.0
Jul 27 21:26:23 2019 USB: mouse human interface device 4:1 dev:0a4c, vend:15d9, class:03, sub:01 proto:02 usb:1.10
Jul 27 21:26:24 2019 USB: keyboard human interface device 4:2 dev:0760, vend:04f2, class:03, sub:01 proto:01 usb:2.0
Jul 27 21:26:24 2019 Found PCI/ISA bridge
Jul 27 21:26:24 2019 ISA bridge device detected
Jul 27 21:26:24 2019 Error::kernelPs2KeyboardDriver.c:inPort60(119):
Jul 27 21:26:24 2019 Timeout reading port 60, port 64=16
Jul 27 21:26:24 2019 Error::kernelPs2KeyboardDriver.c:waitControllerReady(143):
Jul 27 21:26:24 2019 Controller not ready timeout, port 64=16
Jul 27 21:26:24 2019 Error::kernelPs2KeyboardDriver.c:waitControllerReady(143):
Jul 27 21:26:24 2019 Controller not ready timeout, port 64=16
Jul 27 21:26:24 2019 Error::kernelPs2KeyboardDriver.c:waitControllerReady(143):
Jul 27 21:26:24 2019 Controller not ready timeout, port 64=56
Jul 27 21:26:24 2019 Error::kernelPs2KeyboardDriver.c:inPort60(119):
Jul 27 21:26:24 2019 Timeout reading port 60, port 64=56
Jul 27 21:26:24 2019 Error::kernelPs2KeyboardDriver.c:waitControllerReady(143):
Jul 27 21:26:24 2019 Controller not ready timeout, port 64=56
Jul 27 21:26:24 2019 PS/2 keyboard device detected
Jul 27 21:26:24 2019 USB keyboard device detected
Jul 27 21:26:24 2019 Error::kernelScsiDiskDriver.c:usbScsiCommand(286):
Jul 27 21:26:24 2019 USB MS command error status 01
Jul 27 21:26:24 2019 Error::kernelScsiDiskDriver.c:scsiTestUnitReady(530):
Jul 27 21:26:24 2019 SCSI test unit ready failed
Jul 27 21:26:24 2019 Error::kernelScsiDiskDriver.c:detectTarget(784):
Jul 27 21:26:24 2019 SCSI sense error key=0x02 asc=0x3a ascq=0x00
Jul 27 21:26:24 2019 Error::kernelScsiDiskDriver.c:usbScsiCommand(286):
Jul 27 21:26:24 2019 USB MS command error status 01
Jul 27 21:26:24 2019 Error::kernelScsiDiskDriver.c:scsiTestUnitReady(530):
Jul 27 21:26:24 2019 SCSI test unit ready failed
Jul 27 21:26:24 2019 Error::kernelScsiDiskDriver.c:detectTarget(784):
Jul 27 21:26:24 2019 SCSI sense error key=0x02 asc=0x3a ascq=0x00
Jul 27 21:26:25 2019 Error::kernelScsiDiskDriver.c:usbScsiCommand(286):
Jul 27 21:26:25 2019 USB MS command error status 01
Jul 27 21:26:25 2019 Error::kernelScsiDiskDriver.c:scsiTestUnitReady(530):
Jul 27 21:26:25 2019 SCSI test unit ready failed
Jul 27 21:26:25 2019 Error::kernelScsiDiskDriver.c:detectTarget(784):
Jul 27 21:26:25 2019 SCSI sense error key=0x02 asc=0x3a ascq=0x00
Jul 27 21:26:25 2019 Error::kernelScsiDiskDriver.c:usbScsiCommand(286):
Jul 27 21:26:25 2019 USB MS command error status 01
Jul 27 21:26:25 2019 Error::kernelScsiDiskDriver.c:scsiTestUnitReady(530):
Jul 27 21:26:25 2019 SCSI test unit ready failed
Jul 27 21:26:25 2019 Error::kernelScsiDiskDriver.c:detectTarget(784):
Jul 27 21:26:25 2019 SCSI sense error key=0x02 asc=0x3a ascq=0x00
Jul 27 21:26:25 2019 Error::kernelScsiDiskDriver.c:usbScsiCommand(286):
Jul 27 21:26:25 2019 USB MS command error status 01
Jul 27 21:26:25 2019 Error::kernelScsiDiskDriver.c:scsiTestUnitReady(530):
Jul 27 21:26:25 2019 SCSI test unit ready failed
Jul 27 21:26:25 2019 Error::kernelScsiDiskDriver.c:detectTarget(784):
Jul 27 21:26:25 2019 SCSI sense error key=0x02 asc=0x3a ascq=0x00
Jul 27 21:26:25 2019 Error::kernelScsiDiskDriver.c:usbScsiCommand(286):
Jul 27 21:26:25 2019 USB MS command error status 01
Jul 27 21:26:26 2019 Error::kernelScsiDiskDriver.c:scsiTestUnitReady(530):
Jul 27 21:26:26 2019 SCSI test unit ready failed
...
Jul 27 21:27:28 2019 SCSI sense error key=0x02 asc=0x3a ascq=0x00
Jul 27 21:27:28 2019 Error::kernelScsiDiskDriver.c:detectTarget(868):
Jul 27 21:27:28 2019 Error detecting USB SCSI disk
Jul 27 21:27:29 2019 Error::kernelScsiDiskDriver.c:usbScsiCommand(286):
Jul 27 21:27:29 2019 USB MS command error status 01
Jul 27 21:27:29 2019 Error::kernelScsiDiskDriver.c:scsiTestUnitReady(530):
Jul 27 21:27:29 2019 SCSI test unit ready failed
Jul 27 21:27:29 2019 Error::kernelScsiDiskDriver.c:detectTarget(784):
Jul 27 21:27:30 2019 SCSI sense error key=0x06 asc=0x28 ascq=0x00
Jul 27 21:27:30 2019 "Generic USB Flash Disk" SCSI disk device detected
Jul 27 21:27:30 2019 AHCI: Searching for controllers
Jul 27 21:27:30 2019 IDE: Searching for controllers
Jul 27 21:27:30 2019 IDE: Bus mastering PCI controller enabled
Jul 27 21:27:30 2019 IDE disk controller device detected
Jul 27 21:27:30 2019 IDE: Bus mastering PCI controller enabled
Jul 27 21:27:30 2019 IDE disk controller device detected
Jul 27 21:27:30 2019 IDE: Disk 0:0 is an IDE hard disk
Jul 27 21:27:30 2019 IDE: Disk 0:0 model "ST380815AS"
Jul 27 21:27:31 2019 IDE: Disk 0:2 is an IDE CD/DVD
Jul 27 21:27:32 2019 IDE: Disk 0:2 model "TSSTcorp DVD+/-RW TS-H653A"
Jul 27 21:27:33 2019 IDE: Disk 0:0 supports ATA/ATAPI 7
Jul 27 21:27:33 2019 IDE: Disk 0:0 in DMA mode UDMA5
Jul 27 21:27:33 2019 IDE disk device detected
Jul 27 21:27:33 2019 IDE: Disk 0:2 no ATA/ATAPI version reported
Jul 27 21:27:33 2019 IDE: Disk 0:2 in DMA mode UDMA2
Jul 27 21:27:33 2019 IDE disk device detected
Jul 27 21:27:34 2019 USB mouse device detected
Jul 27 21:27:34 2019 USB unknown device detected
Jul 27 21:27:34 2019 USB unknown device detected
Jul 27 21:27:34 2019 Multitasking started
Jul 27 21:27:34 2019 The kernel's random seed is: 25718944585
Jul 27 21:27:34 2019 Disk sd0a (hard disk sd0, primary): fat16
Jul 27 21:27:34 2019 Disk hd0a (hard disk hd0, primary): fat32
Jul 27 21:27:34 2019 Disk hd0b (hard disk hd0, primary): ext
Jul 27 21:27:34 2019 Disk hd0c (hard disk hd0, primary): linux-swap
Jul 27 21:27:34 2019 Disk cd0 (disk cd0, primary): unknown
Jul 27 21:27:34 2019 Mounting / filesystem on disk sd0a
Jul 27 21:27:34 2019 Loaded mouse pointer default from file /system/mouse/default.bmp
Jul 27 21:27:34 2019 Loaded mouse pointer busy from file /system/mouse/busy.ico
Jul 27 21:27:34 2019 Loaded mouse pointer resizeh from file /system/mouse/resizeh.bmp
Jul 27 21:27:34 2019 Loaded mouse pointer resizev from file /system/mouse/resizev.bmp
Jul 27 21:27:34 2019 Reading kernel symbols from "/visopsys"
Jul 27 21:27:34 2019 Added network device loop, link=UP
Jul 27 21:27:34 2019 Networking initialized. Host name is "visopsys".
Jul 27 21:27:34 2019 Starting window system initialization
Jul 27 21:27:34 2019 Window thread started
Jul 27 21:27:34 2019 Window system initialization complete
Jul 27 21:27:52 2019 Error:imgboot:malloc.c:_doMalloc(759):
Jul 27 21:27:52 2019 Can't allocate zero bytes (kernelWindowSetCharSet)
Jul 27 21:27:53 2019 User admin logged in
Jul 27 21:27:53 2019 Background image loaded
Jul 27 21:27:53 2019 Task menu initialized
Jul 27 21:27:53 2019 Desktop icons loaded
Jul 27 21:28:02 2019 Mounting /hd0a filesystem on disk hd0a
Jul 27 21:28:07 2019 Mounting /hd0b filesystem on disk hd0b
Jul 27 21:28:07 2019 Warning:browse thread:kernelFilesystemExt.c:getExtData(372):
Jul 27 21:28:07 2019 Inode size (256) does not match structure size (128)
Jul 27 21:28:58 2019 Error:lsdev:kernelPage.c:findPageTableEntry(450):
Jul 27 21:28:58 2019 No page table 0
Jul 27 21:28:58 2019 Error:lsdev:kernelPage.c:kernelPageGetPhysical(1564):
Jul 27 21:28:58 2019 No page table entry for address 0x00036714
Jul 27 21:28:58 2019 Error:lsdev:kernelMemory.c:kernelMemoryReleaseSystem(699):
Jul 27 21:28:58 2019 The memory pointer is not mapped
Jul 27 21:28:58 2019 Error:lsdev:kernelPage.c:findPageTableEntry(450):
Jul 27 21:28:58 2019 No page table 0
Jul 27 21:28:58 2019 Error:lsdev:kernelPage.c:kernelPageGetPhysical(1564):
Jul 27 21:28:58 2019 No page table entry for address 0x00037e14
Jul 27 21:28:58 2019 Error:lsdev:kernelMemory.c:kernelMemoryReleaseSystem(699):
Jul 27 21:28:58 2019 The memory pointer is not mapped
Jul 28 01:16:18 2019 Stopping kernel logging

Just to mention I have a card reader.
Virtual machines usually dont have.