Hi Mark,
Does this ring a bell with you? I'm getting the error below with latest QEMU+KVM on a G5.
Alex
2015-04-15 23:54:36: C>> annot manage 'ethernet controller' PCI device type 'network': 2015-04-15 23:54:36: >> 8086 100e (2 0 0) 2015-04-15 23:54:36: 2015-04-15 23:54:36: >> ============================================================= 2015-04-15 23:54:36: >> OpenBIOS 1.1 [Mar 12 2015 08:09] 2015-04-15 23:54:36: >> Configuration device id QEMU version 1 machine id 1 2015-04-15 23:54:36: >> CPUs: 1 2015-04-15 23:54:36: >> Memory: 512M 2015-04-15 23:54:36: >> UUID: 00000000-0000-0000-0000-000000000000 2015-04-15 23:54:36: >> CPU type PowerPC,G4 2015-04-15 23:54:36: milliseconds isn't unique. 2015-04-16 00:06:57: (Process terminated with status 0)
On 21/04/15 12:36, Alexander Graf wrote:
Hi Mark,
Does this ring a bell with you? I'm getting the error below with latest QEMU+KVM on a G5.
Alex
2015-04-15 23:54:36: C>> annot manage 'ethernet controller' PCI device type 'network': 2015-04-15 23:54:36: >> 8086 100e (2 0 0) 2015-04-15 23:54:36: 2015-04-15 23:54:36: >> ============================================================= 2015-04-15 23:54:36: >> OpenBIOS 1.1 [Mar 12 2015 08:09] 2015-04-15 23:54:36: >> Configuration device id QEMU version 1 machine id 1 2015-04-15 23:54:36: >> CPUs: 1 2015-04-15 23:54:36: >> Memory: 512M 2015-04-15 23:54:36: >> UUID: 00000000-0000-0000-0000-000000000000 2015-04-15 23:54:36: >> CPU type PowerPC,G4 2015-04-15 23:54:36: milliseconds isn't unique. 2015-04-16 00:06:57: (Process terminated with status 0)
Yeah, it's harmless. It's there because I moved SPARC over to use an interrupt-driven counter for milliseconds with the eventual aim of adding alarms if required. However since this isn't yet complete, the fallback is for PPC to redefine its own milliseconds word based on the CPU tick register which is why the warning appears on the serial console.
At some point I'll switch it over to using a decrementer interrupt at which point the warning will go away, a lot of timer cruft can be removed, and there is potential for adding alarms later if required.
ATB,
Mark.
On 04/21/2015 02:22 PM, Mark Cave-Ayland wrote:
On 21/04/15 12:36, Alexander Graf wrote:
Hi Mark,
Does this ring a bell with you? I'm getting the error below with latest QEMU+KVM on a G5.
Alex
2015-04-15 23:54:36: C>> annot manage 'ethernet controller' PCI device type 'network': 2015-04-15 23:54:36: >> 8086 100e (2 0 0) 2015-04-15 23:54:36: 2015-04-15 23:54:36: >> ============================================================= 2015-04-15 23:54:36: >> OpenBIOS 1.1 [Mar 12 2015 08:09] 2015-04-15 23:54:36: >> Configuration device id QEMU version 1 machine id 1 2015-04-15 23:54:36: >> CPUs: 1 2015-04-15 23:54:36: >> Memory: 512M 2015-04-15 23:54:36: >> UUID: 00000000-0000-0000-0000-000000000000 2015-04-15 23:54:36: >> CPU type PowerPC,G4 2015-04-15 23:54:36: milliseconds isn't unique. 2015-04-16 00:06:57: (Process terminated with status 0)
Yeah, it's harmless. It's there because I moved SPARC over to use an interrupt-driven counter for milliseconds with the eventual aim of adding alarms if required. However since this isn't yet complete, the fallback is for PPC to redefine its own milliseconds word based on the CPU tick register which is why the warning appears on the serial console.
Well, this is the last thing happening on any console. VGA doesn't even get initialized ;).
Alex
At some point I'll switch it over to using a decrementer interrupt at which point the warning will go away, a lot of timer cruft can be removed, and there is potential for adding alarms later if required.
ATB,
Mark.
On 21/04/15 13:21, Alexander Graf wrote:
On 04/21/2015 02:22 PM, Mark Cave-Ayland wrote:
On 21/04/15 12:36, Alexander Graf wrote:
Hi Mark,
Does this ring a bell with you? I'm getting the error below with latest QEMU+KVM on a G5.
Alex
2015-04-15 23:54:36: C>> annot manage 'ethernet controller' PCI device type 'network': 2015-04-15 23:54:36: >> 8086 100e (2 0 0) 2015-04-15 23:54:36: 2015-04-15 23:54:36: >> ============================================================= 2015-04-15 23:54:36: >> OpenBIOS 1.1 [Mar 12 2015 08:09] 2015-04-15 23:54:36: >> Configuration device id QEMU version 1 machine id 1 2015-04-15 23:54:36: >> CPUs: 1 2015-04-15 23:54:36: >> Memory: 512M 2015-04-15 23:54:36: >> UUID: 00000000-0000-0000-0000-000000000000 2015-04-15 23:54:36: >> CPU type PowerPC,G4 2015-04-15 23:54:36: milliseconds isn't unique. 2015-04-16 00:06:57: (Process terminated with status 0)
Yeah, it's harmless. It's there because I moved SPARC over to use an interrupt-driven counter for milliseconds with the eventual aim of adding alarms if required. However since this isn't yet complete, the fallback is for PPC to redefine its own milliseconds word based on the CPU tick register which is why the warning appears on the serial console.
Well, this is the last thing happening on any console. VGA doesn't even get initialized ;).
Meh in that case I would suspect something else as the error has been there for a while :/ Does a QEMU 2.2 OpenBIOS work?
ATB,
Mark.
On 04/21/2015 02:39 PM, Mark Cave-Ayland wrote:
On 21/04/15 13:21, Alexander Graf wrote:
On 04/21/2015 02:22 PM, Mark Cave-Ayland wrote:
On 21/04/15 12:36, Alexander Graf wrote:
Hi Mark,
Does this ring a bell with you? I'm getting the error below with latest QEMU+KVM on a G5.
Alex
2015-04-15 23:54:36: C>> annot manage 'ethernet controller' PCI device type 'network': 2015-04-15 23:54:36: >> 8086 100e (2 0 0) 2015-04-15 23:54:36: 2015-04-15 23:54:36: >> ============================================================= 2015-04-15 23:54:36: >> OpenBIOS 1.1 [Mar 12 2015 08:09] 2015-04-15 23:54:36: >> Configuration device id QEMU version 1 machine id 1 2015-04-15 23:54:36: >> CPUs: 1 2015-04-15 23:54:36: >> Memory: 512M 2015-04-15 23:54:36: >> UUID: 00000000-0000-0000-0000-000000000000 2015-04-15 23:54:36: >> CPU type PowerPC,G4 2015-04-15 23:54:36: milliseconds isn't unique. 2015-04-16 00:06:57: (Process terminated with status 0)
Yeah, it's harmless. It's there because I moved SPARC over to use an interrupt-driven counter for milliseconds with the eventual aim of adding alarms if required. However since this isn't yet complete, the fallback is for PPC to redefine its own milliseconds word based on the CPU tick register which is why the warning appears on the serial console.
Well, this is the last thing happening on any console. VGA doesn't even get initialized ;).
Meh in that case I would suspect something else as the error has been there for a while :/ Does a QEMU 2.2 OpenBIOS work?
Sorry, false alarm. There was other breakage that seems to have gotten fixed in between, I was just branching off an older rc. Meh.
Sorry for the fuss,
Alex
On Tue, Apr 21, 2015 at 01:22:37PM +0100, Mark Cave-Ayland wrote:
2015-04-15 23:54:36: milliseconds isn't unique.
Yeah, it's harmless. It's there because I moved SPARC over to use an interrupt-driven counter for milliseconds with the eventual aim of adding alarms if required. However since this isn't yet complete, the fallback is for PPC to redefine its own milliseconds word based on the CPU tick register which is why the warning appears on the serial console.
Other Forth systems use "warning off" around deliberate redefinitions, you might want to do the same.
Segher
On 22/04/15 02:48, Segher Boessenkool wrote:
On Tue, Apr 21, 2015 at 01:22:37PM +0100, Mark Cave-Ayland wrote:
2015-04-15 23:54:36: milliseconds isn't unique.
Yeah, it's harmless. It's there because I moved SPARC over to use an interrupt-driven counter for milliseconds with the eventual aim of adding alarms if required. However since this isn't yet complete, the fallback is for PPC to redefine its own milliseconds word based on the CPU tick register which is why the warning appears on the serial console.
Other Forth systems use "warning off" around deliberate redefinitions, you might want to do the same.
Yeah sadly OpenBIOS doesn't implement "warning off" yet. I know this is needed for Solaris 64-bit boot, so at the very minimum there needs to be a dummy word in place...
ATB,
Mark.
On Sun, Apr 26, 2015 at 07:15:37PM +0100, Mark Cave-Ayland wrote:
Other Forth systems use "warning off" around deliberate redefinitions, you might want to do the same.
Yeah sadly OpenBIOS doesn't implement "warning off" yet. I know this is needed for Solaris 64-bit boot, so at the very minimum there needs to be a dummy word in place...
Here you go, feel free to steal / modify it as you wish.
0 VARIABLE warning
Wow that was hard ;-)
Segher
On 26/04/15 20:39, Segher Boessenkool wrote:
On Sun, Apr 26, 2015 at 07:15:37PM +0100, Mark Cave-Ayland wrote:
Other Forth systems use "warning off" around deliberate redefinitions, you might want to do the same.
Yeah sadly OpenBIOS doesn't implement "warning off" yet. I know this is needed for Solaris 64-bit boot, so at the very minimum there needs to be a dummy word in place...
Here you go, feel free to steal / modify it as you wish.
0 VARIABLE warning
Wow that was hard ;-)
Well I must say I didn't think that "on" and "off" had been implemented in OpenBIOS yet, but indeed your example does work - thanks!
ATB,
Mark.
-
Alexander Graf -
Mark Cave-Ayland -
Segher Boessenkool