visopsys.org

Visopsys Forums
It is currently Tue Apr 24, 2018 1:53 pm

All times are UTC




Post new topic Reply to topic  [ 18 posts ]  Go to page 1, 2  Next
Author Message
 Post subject: Testing request
PostPosted: Sun Oct 12, 2014 2:32 pm 
Offline
User avatar

Joined: Tue Nov 16, 2010 7:20 pm
Posts: 463
Hi all,

I'm wrapping up work on the 0.75 release. I've added APIC (advanced interrupt controller) support. It's a really crucial part of the kernel - if it doesn't work properly, a lot of hardware support fails. I've been developing and testing with VMware and several real systems, but I would feel better if some of you guys could give it a try on your hardware, or other emulators.

I've uploaded custom debug text-mode images here:
http://visopsys.org/files/visopsys/visopsys-2014-10-12-iso.zip (ISO image)
http://visopsys.org/files/visopsys/visopsys-2014-10-12-usb-img.zip (USB stick image)

APIC support will currently only enable if your system implements the multiprocessor specification (most recent machines do). Otherwise it will default to the old PIC mode.

At boot time, these images will output a bunch of message that will help me see how well everything is working. It will show entries from the multiprocessor tables, APIC initialization, and PCI devices. If you can snap photos of the screen and post them here, that would be very helpful. You can use the 'page up' and 'page down' keys to scroll up and down through pages of messages.

Here are examples (from VMware)

Enumerating the multiprocessor table entries, which contain info about motherboard/BIOS interrupt pin wirings/assignments:
Attachment:
multi_processor.png
multi_processor.png [ 446.15 KiB | Viewed 10722 times ]


Initializing the APICs, using the info from the multiprocessor tables:
Attachment:
apic_initialization.png
apic_initialization.png [ 803.38 KiB | Viewed 10722 times ]


Enumerating the PCI devices and reassigning interrupt numbers to their new APIC vectors:
Attachment:
pci_enumeration1.png
pci_enumeration1.png [ 300.3 KiB | Viewed 10722 times ]

Attachment:
pci_enumeration2.png
pci_enumeration2.png [ 167.13 KiB | Viewed 10722 times ]


The 'lsdev' command will show the device tree, and you can see whether your USB controllers and devices seem to be detected and working (an interrupt number of 255 indicates a problem).

The 'disks' command will show your logical disks/partitions, and you can run the 'fdisk' (Disk Manager) command in text mode as well, to see whether your IDE/SATA controllers are functioning correctly.


Top
 Profile  
 
 Post subject: Re: Testing request
PostPosted: Mon Oct 13, 2014 3:34 am 
Offline
User avatar

Joined: Tue May 20, 2014 5:19 pm
Posts: 80
Hello Andy:

I tried the iso image for Visopsys version .75:

The DEBUG diagnostic messages appeared as you've posted in your attachments (plus or minus) - until the following appeared:

USB Bus controller

warning::kernelUsbUhciDriver.c:runQueue(503)
Transaction error on TD1 contStatus=184007ff first active=1

Warning::kernelUSBUhciDriver.c:debugTransError(186)
UHCI: Trans desc IN: stalled

Error::kernelUSBDriver.c:kernelUSBDevConnect(1067)
Error setting device address

Error::kernelUsbUhciDriver.c:doDetectDevices(831)
Error enumerating new USB device

Detecting hardware: IDE disk controller SYSTEM
HALTED:Panic at kernelMultitasker.c:kernelException(2022)
Double fault (page fault) while processing a page exception.

I've attached a dmesg from a freebsd OS on the same machine, as well as a pci-config listing.

You sure have set up great debug output - lots of info. I suppose I could get more with serial. Anyway, I probably just have stuff that's too old (about 2000 vintage). Hope it's good for some insight.

- Ron


Top
 Profile  
 
 Post subject: Re: Testing request
PostPosted: Mon Oct 13, 2014 3:34 am 
Offline
User avatar

Joined: Tue May 20, 2014 5:19 pm
Posts: 80
Sorry, the board is saying that the files I tried to upload with txt extensions are not allowed?

I attempted to upload pci-config.txt and log-dmesg.txt

- Ron


Top
 Profile  
 
 Post subject: Re: Testing request
PostPosted: Mon Oct 13, 2014 12:52 pm 
Offline
User avatar

Joined: Tue Feb 14, 2012 12:40 am
Posts: 103
Try just Pastebin or copy paste in here within code /code tags

_________________
Image
Image


Top
 Profile  
 
 Post subject: Re: Testing request
PostPosted: Mon Oct 13, 2014 2:09 pm 
Offline
User avatar

Joined: Tue May 20, 2014 5:19 pm
Posts: 80
Ap0r: tnx for the hint. Since Pastebin goes away after awhile, I'll just post it outright:

First, the pci-config.txt:


Code:
hostb0@pci0:0:0:0:      class=0x060000 card=0x00000000 chip=0x06911106 rev=0xc4 hdr=0x00
pcib1@pci0:0:1:0:       class=0x060400 card=0x00000000 chip=0x85981106 rev=0x00 hdr=0x01
isab0@pci0:0:7:0:       class=0x060100 card=0x00001106 chip=0x06861106 rev=0x40 hdr=0x00
atapci0@pci0:0:7:1:     class=0x01018a card=0x00000000 chip=0x05711106 rev=0x06 hdr=0x00
uhci0@pci0:0:7:2:       class=0x0c0300 card=0x12340925 chip=0x30381106 rev=0x16 hdr=0x00
uhci1@pci0:0:7:3:       class=0x0c0300 card=0x12340925 chip=0x30381106 rev=0x16 hdr=0x00
hostb1@pci0:0:7:4:      class=0x060000 card=0x00000000 chip=0x30571106 rev=0x40 hdr=0x00
rl0@pci0:0:14:0:        class=0x020000 card=0x813910ec chip=0x813910ec rev=0x10 hdr=0x00
none0@pci0:0:15:0:      class=0x040100 card=0x00000000 chip=0x60051013 rev=0x01 hdr=0x00
vgapci0@pci0:0:16:0:    class=0x030000 card=0x97501023 chip=0x97501023 rev=0xf3 hdr=0x00


Top
 Profile  
 
 Post subject: Re: Testing request
PostPosted: Mon Oct 13, 2014 2:23 pm 
Offline
User avatar

Joined: Tue May 20, 2014 5:19 pm
Posts: 80
Hope the board doesn't choke on this one:

log-dmesg.txt:

Code:
Oct 12 09:54:11 steelhullketch syslogd: kernel boot file is /boot/kernel/kernel
Oct 12 09:54:11 steelhullketch kernel: ACPI BIOS Error (bug): A valid RSDP was not found (20130823/tbxfroot-223)
Oct 12 09:54:11 steelhullketch kernel: Copyright (c) 1992-2014 The FreeBSD Project.
Oct 12 09:54:11 steelhullketch kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
Oct 12 09:54:11 steelhullketch kernel: The Regents of the University of California. All rights reserved.
Oct 12 09:54:11 steelhullketch kernel: FreeBSD is a registered trademark of The FreeBSD Foundation.
Oct 12 09:54:11 steelhullketch kernel: FreeBSD 10.0-RELEASE #0 r260789: Fri Jan 17 01:46:25 UTC 2014
Oct 12 09:54:11 steelhullketch kernel: root@snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC i386
Oct 12 09:54:11 steelhullketch kernel: FreeBSD clang version 3.3 (tags/RELEASE_33/final 183502) 20130610
Oct 12 09:54:11 steelhullketch kernel: CPU: Intel Pentium III (868.66-MHz 686-class CPU)
Oct 12 09:54:11 steelhullketch kernel: Origin = "GenuineIntel"  Id = 0x68a  Family = 0x6  Model = 0x8  Stepping = 10
Oct 12 09:54:11 steelhullketch kernel: Features=0x387fbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,
Oct 12 09:54:11 steelhullketch kernel: real memory  = 134217728 (128 MB)
Oct 12 09:54:11 steelhullketch kernel: avail memory = 107745280 (102 MB)
Oct 12 09:54:11 steelhullketch kernel: MPTable: <OEM00000 PROD00000000>
Oct 12 09:54:11 steelhullketch kernel: Event timer "LAPIC" quality 400
Oct 12 09:54:11 steelhullketch kernel: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
Oct 12 09:54:11 steelhullketch kernel: FreeBSD/SMP: 2 package(s) x 1 core(s)
Oct 12 09:54:11 steelhullketch kernel: cpu0 (BSP): APIC ID:  0
Oct 12 09:54:11 steelhullketch kernel: cpu1 (AP): APIC ID:  1
Oct 12 09:54:11 steelhullketch kernel: ioapic0: Assuming intbase of 0
Oct 12 09:54:11 steelhullketch kernel: ioapic0 <Version 1.1> irqs 0-23 on motherboard
Oct 12 09:54:11 steelhullketch kernel: kbd1 at kbdmux0
Oct 12 09:54:11 steelhullketch kernel: random: <Software, Yarrow> initialized
Oct 12 09:54:11 steelhullketch kernel: ACPI BIOS Error (bug): A valid RSDP was not found (20130823/tbxfroot-223)
Oct 12 09:54:11 steelhullketch kernel: ACPI: Table initialisation failed: AE_NOT_FOUND
Oct 12 09:54:11 steelhullketch kernel: ACPI: Try disabling either ACPI or apic support.
Oct 12 09:54:11 steelhullketch kernel: pcib0: <MPTable Host-PCI bridge> pcibus 0 on motherboard
Oct 12 09:54:11 steelhullketch kernel: pci0: <PCI bus> on pcib0
Oct 12 09:54:11 steelhullketch kernel: agp0: <VIA 82C691 (Apollo Pro) host to PCI bridge> on hostb0
Oct 12 09:54:11 steelhullketch kernel: agp0: aperture size is 64M
Oct 12 09:54:11 steelhullketch kernel: pcib1: <PCI-PCI bridge> at device 1.0 on pci0
Oct 12 09:54:11 steelhullketch kernel: pci1: <PCI bus> on pcib1
Oct 12 09:54:11 steelhullketch kernel: isab0: <PCI-ISA bridge> at device 7.0 on pci0
Oct 12 09:54:11 steelhullketch kernel: isa0: <ISA bus> on isab0
Oct 12 09:54:11 steelhullketch kernel: atapci0: <VIA 82C686B UDMA100 controller> port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x
Oct 12 09:54:11 steelhullketch kernel: ata0: <ATA channel> at channel 0 on atapci0
Oct 12 09:54:11 steelhullketch kernel: ata1: <ATA channel> at channel 1 on atapci0
Oct 12 09:54:11 steelhullketch kernel: uhci0: <VIA 83C572 USB controller> port 0xd400-0xd41f irq 5 at device 7.2 on pci0
Oct 12 09:54:11 steelhullketch kernel: usbus0 on uhci0
Oct 12 09:54:11 steelhullketch kernel: uhci1: <VIA 83C572 USB controller> port 0xd800-0xd81f irq 5 at device 7.3 on pci0
Oct 12 09:54:11 steelhullketch kernel: usbus1 on uhci1
Oct 12 09:54:11 steelhullketch kernel: rl0: <RealTek 8139 10/100BaseTX> port 0xec00-0xecff mem 0xd5831000-0xd58310ff irq 11
Oct 12 09:54:11 steelhullketch kernel: miibus0: <MII bus> on rl0
Oct 12 09:54:11 steelhullketch kernel: rlphy0: <RealTek internal media interface> PHY 0 on miibus0
Oct 12 09:54:11 steelhullketch kernel: rlphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
Oct 12 09:54:11 steelhullketch kernel: rl0: Ethernet address: 00:0e:2e:0f:99:1b
Oct 12 09:54:11 steelhullketch kernel: rl0: Ethernet address: 00:0e:2e:0f:99:1b
Oct 12 09:54:11 steelhullketch kernel: pci0: <multimedia, audio> at device 15.0 (no driver attached)
Oct 12 09:54:11 steelhullketch kernel: vgapci0: <VGA-compatible display> mem 0xd5400000-0xd57fffff,0xd5800000-0xd581ffff,0xd
Oct 12 09:54:11 steelhullketch kernel: vgapci0: Boot video device
Oct 12 09:54:11 steelhullketch kernel: cpu0 on motherboard
Oct 12 09:54:11 steelhullketch kernel: cpu1 on motherboard
Oct 12 09:54:11 steelhullketch kernel: pmtimer0 on isa0
Oct 12 09:54:11 steelhullketch kernel: attimer0: <AT timer> at port 0x40-0x43 irq 0 pnpid PNP0100 on isa0
Oct 12 09:54:11 steelhullketch kernel: Timecounter "i8254" frequency 1193182 Hz quality 0
Oct 12 09:54:11 steelhullketch kernel: Event timer "i8254" frequency 1193182 Hz quality 100
Oct 12 09:54:11 steelhullketch kernel: atrtc0: <AT realtime clock> at port 0x70-0x71 irq 8 pnpid PNP0b00 on isa0
Oct 12 09:54:11 steelhullketch kernel: Event timer "RTC" frequency 32768 Hz quality 0
Oct 12 09:54:11 steelhullketch kernel: atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 irq 1 pnpid PNP0303 on isa0
Oct 12 09:54:11 steelhullketch kernel: atkbd0: <AT Keyboard> irq 1 on atkbdc0
Oct 12 09:54:11 steelhullketch kernel: kbd0 at atkbd0
Oct 12 09:54:11 steelhullketch kernel: atkbd0: [GIANT-LOCKED]
Oct 12 09:54:11 steelhullketch kernel: unknown: <PNP0c01> can't assign resources (memory)
Oct 12 09:54:11 steelhullketch kernel: fdc0: <Enhanced floppy controller> at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 pnpid PNP070
Oct 12 09:54:11 steelhullketch kernel: fd0: <1440-KB 3.5" drive> on fdc0 drive 0
Oct 12 09:54:11 steelhullketch kernel: uart0: <16550 or compatible> at port 0x3f8-0x3ff irq 4 flags 0x10 pnpid PNP0501 on is
Oct 12 09:54:11 steelhullketch kernel: uart1: <16550 or compatible> at port 0x2f8-0x2ff irq 3 pnpid PNP0501 on isa0
Oct 12 09:54:11 steelhullketch kernel: ppc0: <Standard parallel printer port> at port 0x378-0x37f irq 7 pnpid PNP0400 on isa
Oct 12 09:54:11 steelhullketch kernel: ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode
Oct 12 09:54:11 steelhullketch kernel: ppbus0: <Parallel port bus> on ppc0
Oct 12 09:54:11 steelhullketch kernel: lpt0: <Printer> on ppbus0
Oct 12 09:54:11 steelhullketch kernel: lpt0: Interrupt-driven port
Oct 12 09:54:11 steelhullketch kernel: ppi0: <Parallel I/O> on ppbus0
Oct 12 09:54:11 steelhullketch kernel: orm0: <ISA Option ROM> at iomem 0xc0000-0xcbfff pnpid ORM0000 on isa0
Oct 12 09:54:11 steelhullketch kernel: sc0: <System console> at flags 0x100 on isa0
Oct 12 09:54:11 steelhullketch kernel: sc0: VGA <16 virtual consoles, flags=0x300>
Oct 12 09:54:11 steelhullketch kernel: vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
Oct 12 09:54:11 steelhullketch kernel: unknown: <PNP0c01> can't assign resources (memory)
Oct 12 09:54:11 steelhullketch kernel: Timecounters tick every 1.000 msec
Oct 12 09:54:11 steelhullketch kernel: usbus0: 12Mbps Full Speed USB v1.0
Oct 12 09:54:11 steelhullketch kernel: usbus1: 12Mbps Full Speed USB v1.0
Oct 12 09:54:11 steelhullketch kernel: ugen0.1: <VIA> at usbus0
Oct 12 09:54:11 steelhullketch kernel: uhub0: <VIA UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus0
Oct 12 09:54:11 steelhullketch kernel: ugen1.1: <VIA> at usbus1
Oct 12 09:54:11 steelhullketch kernel: uhub1: <VIA UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus1
Oct 12 09:54:11 steelhullketch kernel: ada0 at ata0 bus 0 scbus0 target 0 lun 0
Oct 12 09:54:11 steelhullketch kernel: ada0: <ST340016A 3.19> ATA-5 device
Oct 12 09:54:11 steelhullketch kernel: ada0: Serial Number 3HS5ALTV
Oct 12 09:54:11 steelhullketch kernel: ada0: 100.000MB/s transfers (UDMA5, PIO 8192bytes)
Oct 12 09:54:11 steelhullketch kernel: ada0: 38166MB (78165360 512 byte sectors: 16H 63S/T 16383C)
Oct 12 09:54:11 steelhullketch kernel: ada0: Previously was known as ad0
Oct 12 09:54:11 steelhullketch kernel: cd0 at ata1 bus 0 scbus1 target 0 lun 0
Oct 12 09:54:11 steelhullketch kernel: cd0: <LITE-ON LTR-24102M 4DS3> Removable CD-ROM SCSI-0 device
Oct 12 09:54:11 steelhullketch kernel: cd0: <LITE-ON LTR-24102M 4DS3> Removable CD-ROM SCSI-0 device
Oct 12 09:54:11 steelhullketch kernel: cd0: 33.300MB/s transfers (UDMA2, ATAPI 12bytes, PIO 65534bytes)
Oct 12 09:54:11 steelhullketch kernel: cd0: Attempt to query device size failed: NOT READY, Medium not present
Oct 12 09:54:11 steelhullketch kernel: random: unblocking device.
Oct 12 09:54:11 steelhullketch kernel: SMP: AP CPU #1 Launched!
Oct 12 09:54:11 steelhullketch kernel: uhub0: 2 ports with 2 removable, self powered
Oct 12 09:54:11 steelhullketch kernel: uhub1: 2 ports with 2 removable, self powered
Oct 12 09:54:11 steelhullketch kernel: Root mount waiting for: usbus1 usbus0
Oct 12 09:54:11 steelhullketch kernel: ugen0.2: <vendor 0x0566> at usbus0
Oct 12 09:54:11 steelhullketch kernel: ukbd0: <vendor 0x0566 product 0x3107, class 0/0, rev 1.10/1.00, addr 2> on usbus0
Oct 12 09:54:11 steelhullketch kernel: kbd2 at ukbd0
Oct 12 09:54:11 steelhullketch kernel: ugen1.2: <vendor 0x05e3> at usbus1
Oct 12 09:54:11 steelhullketch kernel: ugen0.3: <Microsoft> at usbus0
Oct 12 09:54:11 steelhullketch kernel: Root mount waiting for: usbus0
Oct 12 09:54:11 steelhullketch kernel: Trying to mount root from ufs:/dev/ada0p2 [rw]...
Oct 12 09:54:11 steelhullketch kernel: warning: total configured swap (488448 pages) exceeds maximum recommended amount (215
Oct 12 09:54:11 steelhullketch kernel: warning: increase kern.maxswzone or reduce amount of swap.
Oct 12 09:54:11 steelhullketch kernel: uhid0: <vendor 0x0566 product 0x3107, class 0/0, rev 1.10/1.00, addr 2> on usbus0
Oct 12 09:54:11 steelhullketch kernel: ums0: <Microsoft Microsoft 3-Button Mouse with IntelliEyeTM, class 0/0, rev 1.10/3.00
Oct 12 09:54:11 steelhullketch kernel: ums0: error reading report description
Oct 12 09:54:11 steelhullketch kernel: device_attach: ums0 attach returned 12
Oct 12 09:54:11 steelhullketch kernel: ugen0.2: <vendor 0x0566> at usbus0 (disconnected)
Oct 12 09:54:11 steelhullketch kernel: ukbd0: at uhub0, port 1, addr 2 (disconnected)
Oct 12 09:54:11 steelhullketch kernel: uhid0: at uhub0, port 1, addr 2 (disconnected)
Oct 12 09:54:11 steelhullketch kernel: ugen0.2: <vendor 0x0566> at usbus0
Oct 12 09:54:11 steelhullketch kernel: ukbd0: <vendor 0x0566 product 0x3107, class 0/0, rev 1.10/1.00, addr 2> on usbus0
Oct 12 09:54:11 steelhullketch kernel: kbd2 at ukbd0
Oct 12 09:54:11 steelhullketch kernel: uhid0: <vendor 0x0566 product 0x3107, class 0/0, rev 1.10/1.00, addr 2> on usbus0
Oct 12 09:54:11 steelhullketch kernel: ugen0.3: <Microsoft> at usbus0 (disconnected)
Oct 12 09:54:11 steelhullketch kernel: ugen0.3: <Microsoft> at usbus0
Oct 12 09:54:11 steelhullketch kernel: ums0: <Microsoft Microsoft 3-Button Mouse with IntelliEyeTM, class 0/0, rev 1.10/3.00
Oct 12 09:54:11 steelhullketch kernel: ums0: error reading report description
Oct 12 09:54:11 steelhullketch kernel: device_attach: ums0 attach returned 12
Oct 12 09:54:11 steelhullketch kernel: ugen0.2: <vendor 0x0566> at usbus0 (disconnected)
Oct 12 09:54:11 steelhullketch kernel: ukbd0: at uhub0, port 1, addr 2 (disconnected)
Oct 12 09:54:11 steelhullketch kernel: uhid0: at uhub0, port 1, addr 2 (disconnected)
Oct 12 09:54:11 steelhullketch devd: Executing '/etc/rc.d/syscons setkeyboard /dev/kbd0'
Oct 12 09:54:12 steelhullketch kernel: moused: unable to open /dev/psm0: No such file or directory
Oct 12 09:54:12 steelhullketch kernel: .
Oct 12 09:54:12 steelhullketch kernel: ugen0.2: <vendor 0x0566> at usbus0
Oct 12 09:54:12 steelhullketch kernel: ukbd0: <vendor 0x0566 product 0x3107, class 0/0, rev 1.10/1.00, addr 2> on usbus0
Oct 12 09:54:12 steelhullketch kernel: kbd2 at ukbd0
Oct 12 09:54:12 steelhullketch kernel: uhid0: <vendor 0x0566 product 0x3107, class 0/0, rev 1.10/1.00, addr 2> on usbus0
Oct 12 09:54:12 steelhullketch devd: Executing '/etc/rc.d/syscons setkeyboard /dev/ukbd0'
Oct 12 09:54:12 steelhullketch kernel: ugen0.3: <Microsoft> at usbus0 (disconnected)
Oct 12 09:54:13 steelhullketch kernel: ugen0.3: <Microsoft> at usbus0
Oct 12 09:54:13 steelhullketch kernel: ums0: <Microsoft Microsoft 3-Button Mouse with IntelliEyeTM, class 0/0, rev 1.10/3.00
Oct 12 09:54:13 steelhullketch kernel: ums0: 3 buttons and [XYZ] coordinates ID=0
Oct 12 09:54:13 steelhullketch devd: Executing '/etc/rc.d/moused quietstart ums0' at port 0x70-0x71 irq 8 pnpid PNP0b00 on isa0
Oct 12 09  Executing '/etc/rc



The FreeBSD dmesg should be good for a hardware overall info snapshot. Is there a visopsys.org page for a quickstart on official/preferred best-buildhost-env and setup for serial debugging, etc?

Also, I could add the usbdev list, but that wouldn't be a showstopper for running on my system.


Top
 Profile  
 
 Post subject: Re: Testing request
PostPosted: Mon Oct 13, 2014 3:55 pm 
Offline
User avatar

Joined: Tue Nov 16, 2010 7:20 pm
Posts: 463
Thanks very much Ron,

From your first post, and from looking at the dmesg output, it looks as though the Visopsys kernel should be alright with this hardware. FreeBSD does complain about the ACPI RSDT, which Visopsys does try to parse at startup, but that's now done earlier than the USB and IDE initialization (and only really used for powering off, at this point) so that's unlikely to be the source of the crash. It looks like a crash in the IDE initialization.

Did version 0.74 run OK on that system? There have been some changes made to the IDE code. Perhaps I could post another couple of debug images you could run? One just to try disabling the APIC code, and maybe another with APIC enabled, but more debugging messages turned on for IDE. If you have time to try that, would you prefer a USB stick image or ISO?

Andy


Top
 Profile  
 
 Post subject: Re: Testing request
PostPosted: Mon Oct 13, 2014 6:50 pm 
Offline
User avatar

Joined: Tue May 20, 2014 5:19 pm
Posts: 80
Hi again Andy:

Tnx for looking at the dmesg. Visopsys .74 ran fine on my other machine, but crashed on this one. Unfortunately, this is the machine I could dedicate to Visopsys ;) I don't remember anything about the crash info, but could give it another go.

About the test images, sure I can boot them up for you! More debug info is very interesting to me. Turn it on -vvv! And - the ISO is better for me, have plenty of CDs to burn. Have to do it that way, because this machine is so old such that the BIOS doesn't do USB boots.

-Ron


Top
 Profile  
 
 Post subject: Re: Testing request
PostPosted: Mon Oct 13, 2014 11:59 pm 
Offline
User avatar

Joined: Tue Nov 16, 2010 7:20 pm
Posts: 463
Great! OK, here are ISO images:
http://visopsys.org/files/visopsys/visopsys-2014-10-14-noapic-iso.zip (no APIC)
http://visopsys.org/files/visopsys/visopsys-2014-10-14-idedebug-iso.zip (IDE debugging)

If you want to save yourself some CDs, you can use Plop Boot, which will boot from a CD, and then allow you to boot from USB:
http://www.plop.at/en/bootmanager/download.html

If you want to try that, then these are the corresponding USB images:
http://visopsys.org/files/visopsys/visopsys-2014-10-14-noapic-usb-img.zip (no APIC)
http://visopsys.org/files/visopsys/visopsys-2014-10-14-idedebug-usb-img.zip (IDE debugging)

You should 'dd' the unzipped USB images directly to a major device (e.g. /dev/sdb). The images replace the partition table, so only use a stick that doesn't contain anything you need (and you'll have to re-partition and reinitialize it later).


Top
 Profile  
 
 Post subject: Re: Testing request
PostPosted: Tue Oct 14, 2014 3:58 am 
Offline
User avatar

Joined: Tue May 20, 2014 5:19 pm
Posts: 80
Ok Andy - the first run was with the IDEDebug image. The last page of debug output follows:

Code:
DEBUG IDE controller 0 using standard interrupt=14
DEBUG IDE controller 0 using standard interrupt=15
DEBUG IDE controller 0 using legacy I/O ports 01f0-01f7 & 03f6
DEBUG IDE controller 0 using legacy I/O ports 0170-0177 & 0376
DEBUG IDE turn on interrupt 14
DEBUG IDE disk 00 driverDetect:2828 expect interrupt
DEBUG IDE turn on interrupt 15
DEBUG IDE disk 00 driverDetect:2859 expect interrupt
DEBUG IDE detect disks on controller 0
DEBUG IDE try to detect disk 0:0
DEBUG IDE reset channel 0 (disk 00)
DEBUG IDE channel 0 reset signature 01, 01, 00, 00
DEBUG IDE channel 0 (disk 00) reset indicates non-packet device
DEBUG IDE channel 0 reset finished
DEBUG IDE disk 00 driverDetect:2899 expect interrupt
DEBUG IDE select disk 00
DEBUG IDE reset channel 0 (disk 00)
DEBUG IDE channel 0 reset signature 01, 01, 00, 00
DEBUG IDE channel 0 (disk 00) reset indicates non-packet device
DEBUG IDE channel 0 reset finished
DEBUG IDE identify disk 00
DEBUG IDE disk 00 identify:1106 expect interupt
DEBUG IDE select disk 00
DEBUG IDE disk 00 write command file 28-bit
DEBUG IDE primary interrupt
DEBUG IDE controller 0 primary interrupt 14 #0
DEBUG IDE disk 00 wait (poll) for interupt 14 ack=0
DEBUG IDE disk 00 identify succeeded
DEBUG IDE disk 00 read identify data
DEBUG IDE disk 00 identify:1139 ack interrupt 14 #0
DEBUG IDE disk 0:0 number of cylinders calculation is manual was 16383
DEBUG IDE disk 0:0 number of cylinders calculation is manual now 77545
DEBUG IDE disk 0:0 cylinders=77545 heads=16 sectors=63
DEBUG IDE try to detect disk 0:1
DEBUG IDE disk 01 driverDetect:2899 expect interrupt
DEBUG IDE select disk 01
DEBUG IDE primary interrupt
DEBUG IDE controller 0 primary interrupt 14 #1
DEBUG IDE reset channel 0 (disk 01)
DEBUG IDE channel 0 reset signature 01, 01, 00, 00
DEBUG IDE channel 0 (disk 01) reset indicates non-packet driver
DEBUG IDE channel 0 reset finished
DEBUG IDE identify disk 01
DEBUG IDE disk 01 identify:1106 expect interrupt
DEBUG IDE select disk 01
DEBUG IDE disk 01 write command file 28-bit
DEBUG IDE disk 01 wait (poll) for interrupt 14 ack=0
SYSTEM HALTED:Panic at kernelMultiTasker.c:kernelException(2022)
Double fault (page fault) while processing a page fault exception


Will try to run the other image in the morning. Good night!


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 18 posts ]  Go to page 1, 2  Next

All times are UTC


Who is online

Users browsing this forum: No registered users and 2 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
cron
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group