View previous topic :: View next topic |
Author |
Message |
randomlego n00b
Joined: 13 Sep 2004 Posts: 1
|
Posted: Mon Sep 13, 2004 9:29 am Post subject: Problems with SGI O2 r5k netboot (CRIME memory error) |
|
|
Greetings!
I have an SGI O2 r5k, and I'm trying to netboot the ip32-r5k-20040806.img file from the site listed in the Gentoo-MIPS install document (~kumba).
At the prom prompt, I enter:
bootp()/tftpboot/ip32-r5k-20040806.img console=ttyS0 root=/dev/ram0
It finds the image, the kernel boots fine, the drives are found, etc. And then:
RAMDISK: Compressed image found at block 0
VFS: Mounted root (ext2 filesystem) readonly.
Freeing prom memory: 5824kb freed
Freeing unused kernel memory: 6200k freed
init started: BusyBox v1.00-rc2 (2004.08.01-07:14+0000) multi-call binary
CRIME memory error at 0x3fff03e0 ST 0x0201000<INV,GBE,NONFATAL>
CRIME memory error at 0x####### ST 0x0201000<INV,GBE,NONFATAL>
CRIME memory error at 0x####### ST 0x0201000<INV,GBE,NONFATAL>
CRIME memory error at 0x####### ST 0x0201000<INV,GBE,NONFATAL>
(note: the #'s change, the 0x0201000 does not)
This continues for as long as I let it run. I tried searching google to no avail -- the only similar message I found was on a netbsd-mips list, and it wasn't very helpful.
Any help would be very much appreciated. :)
Lego |
|
Back to top |
|
|
Kumba Developer
Joined: 16 Jul 2002 Posts: 393 Location: Sigma 957
|
Posted: Tue Sep 14, 2004 9:08 am Post subject: |
|
|
Ah, yeah, *that* error.
I'm honestly not sure what triggers it, but my general idea has been that if you want to use serial console, make sure monitor/kb/mouse is completely unplugged from the machine, the "console" envvar in the PROM is set to "d1" (first serial port), and power the system down for ~30secs, then try again.
What triggered it for me, was rebooting under serial console, switching to the framebuffer to boot, then rebooting and trying again under serial. My belief is something in memory isn't fully cleared, and when the serial driver gets used again, it does something. I solved it by powering off for ~30secs and powering on again. Whether this is the true issue or not, I'm not sure. the O2 really needs someone knowledgeable in the framebuffer system (or someone skilled in framebuffers in general) to take a crack at it and see if anything can be improved.
--Kumba _________________ "The past tempts us, the present confuses us, the future frightens us. And our lives slip away, moment by moment, lost in that vast, terrible in-between."
--Emperor Turhan, Centauri Republic |
|
Back to top |
|
|
|
|
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 vote in polls in this forum
|
|