Bug reporting thread

General discussion about Visopsys. We'll create more specific forums if the number of posts justifies that.
User avatar
ronaldlees
Posts: 103
Joined: Tue May 20, 2014 5:19 pm

Re: Bug reporting thread

Post by ronaldlees » Mon Oct 10, 2016 2:26 pm

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
Last edited by ronaldlees on Mon Oct 10, 2016 8:14 pm, edited 2 times in total.

User avatar
ronaldlees
Posts: 103
Joined: Tue May 20, 2014 5:19 pm

Re: Bug reporting thread

Post by ronaldlees » Mon Oct 10, 2016 2:41 pm

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
Posts: 10
Joined: Mon Nov 19, 2018 8:48 pm

Re: Issue when getting file size

Post by qmastery » Tue Dec 11, 2018 6:35 pm

andymc wrote:
Mon Jan 20, 2014 11:59 pm
.
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
Attachments
help-floppy.txt
(1.95 KiB) Downloaded 30 times
original_research.txt
(1.43 KiB) Downloaded 22 times

User avatar
andymc
Posts: 499
Joined: Tue Nov 16, 2010 7:20 pm

Re: Bug reporting thread

Post by andymc » Thu Dec 13, 2018 10:40 pm

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
Posts: 1
Joined: Wed Jan 02, 2019 6:11 am

Re: Bug reporting thread

Post by sadse » Wed Jan 02, 2019 6:16 am

nextvolume wrote:
Mon Jan 20, 2014 10:21 pm
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

User avatar
andymc
Posts: 499
Joined: Tue Nov 16, 2010 7:20 pm

Re: Issue when getting file size

Post by andymc » Fri Feb 15, 2019 12:00 am

qmastery wrote:
Tue Dec 11, 2018 6:35 pm
"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
Posts: 10
Joined: Mon Nov 19, 2018 8:48 pm

Re: Issue when getting file size

Post by qmastery » Fri Feb 22, 2019 4:12 pm

andymc wrote:
Fri Feb 15, 2019 12:00 am
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! :text-bravo: By the way, do you have any news about https://visopsys.org/forums/viewtopic.p ... t=10#p1463 ? I could test your debug builds

User avatar
andymc
Posts: 499
Joined: Tue Nov 16, 2010 7:20 pm

Re: Issue when getting file size

Post by andymc » Sat Feb 23, 2019 11:10 pm

qmastery wrote:
Fri Feb 22, 2019 4:12 pm
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 :-D I do what I can!

qmastery
Posts: 10
Joined: Mon Nov 19, 2018 8:48 pm

Re: Issue when getting file size

Post by qmastery » Sun Feb 24, 2019 6:16 am

andymc wrote:
Sat Feb 23, 2019 11:10 pm
I also have a new daughter arriving in the next 48 hours or so :-D
wow Andy, my sincere congratulations to you ! :angelic-little:

Post Reply