Re: Difficulty upgrading to 3.7
--On July 3, 2005 12:46:00 PM -0400 Avtar Gill <[EMAIL PROTECTED]> sent: Aric Gregson wrote: Tried booting from binary 3.7 -release > on a CD (which I burned), but repeatedly received You should really consider purchasing the official CD and trying that instead. I certainly would, but the alpha install is not on the CD. I next downloaded the 3.7 -release binaries to the drive and replaced the kernel with the new kernel and tried to reboot. That did not work and is where I am now. I wouldn't try it like that. Refer to this part of the FAQ.. http://openbsd.org/faq/faq4.html#bsd.rd I got the exact same error when I tried those directions. I have reinstalled 3.6 from CD (works fine). So at least I have a working system. I'll then try this again and see what I can do about removing the pci device that appears to be holding up the install. I had a similar problem when I first tried to use 3.5, so I waited for 3.6. Maybe I have better luck with the even numbers :).
Re: Difficulty upgrading to 3.7
On Sun, Jul 03, 2005 at 01:23:16PM -0400, Ted Unangst wrote: > On Sun, 3 Jul 2005, Aric Gregson wrote: > > > Hope this is the appropriate list for this. Have tried to upgrade to > > 3.7 from 3.6 for a while a now. Tried booting from binary 3.7 -release > > on a CD (which I burned), but repeatedly received > > a hint as to arch would have been appreciated, as would the dmesg so far. > > > ohci_pci_attach(?, ?, ?, ?, ?, fcbfd00) at ohci_pci_attach+0x1a8 I had a smiliar problem with a 3.7 install. Took out my USB fob and it workd fine. Not sure why. Do you have a lot of USB devices? > > disable ohci, then try again. > > > -- > And that's why Miami is Miami. > -- BOFH excuse #69: knot in cables caused data stream to become twisted and kinked [demime 1.01d removed an attachment of type application/pgp-signature]
Re: Difficulty upgrading to 3.7
Aric Gregson wrote: Tried booting from binary 3.7 -release on a CD (which I burned), but repeatedly received You should really consider purchasing the official CD and trying that instead. I next downloaded the 3.7 -release binaries to the drive and replaced the kernel with the new kernel and tried to reboot. That did not work and is where I am now. I wouldn't try it like that. Refer to this part of the FAQ.. http://openbsd.org/faq/faq4.html#bsd.rd -- Avtar Gill | [EMAIL PROTECTED]
Re: Difficulty upgrading to 3.7
--On 7/3/05 1:23 PM -0400 Ted Unangst sent: a hint as to arch would have been appreciated, as would the dmesg so far. Sorry! I had posted to alpha initially, but no reply. DEC Alpha 500MHz processor, (digital personal workstation 500a). I will post the dmesg as soon as I can reboot into SRM and get the kernel panic again. ohci_pci_attach(?, ?, ?, ?, ?, fcbfd00) at ohci_pci_attach+0x1a8 disable ohci, then try again. OK, as soon as I figure out how to do that. :) thanks
Re: Difficulty upgrading to 3.7
On Sun, 3 Jul 2005, Aric Gregson wrote: > Hope this is the appropriate list for this. Have tried to upgrade to > 3.7 from 3.6 for a while a now. Tried booting from binary 3.7 -release > on a CD (which I burned), but repeatedly received a hint as to arch would have been appreciated, as would the dmesg so far. > ohci_pci_attach(?, ?, ?, ?, ?, fcbfd00) at ohci_pci_attach+0x1a8 disable ohci, then try again. -- And that's why Miami is Miami.
Re: Difficulty upgrading to 3.7
--On 7/4/05 12:32 AM +0800 Ikmal Ahmad sent: Just refer to this: http://www.openbsd.org.my/faq/upgrade37.html That is exactly what I just finishing doing, which led to the kernel panic at start-up. I cannot now boot into OBSD, neither from the disk, nor from a CD with the 3.7 binaries. aric
Re: Difficulty upgrading to 3.7
Just refer to this: http://www.openbsd.org.my/faq/upgrade37.html On 7/3/05, Aric Gregson <[EMAIL PROTECTED]> wrote: > Hope this is the appropriate list for this. Have tried to upgrade to > 3.7 from 3.6 for a while a now. Tried booting from binary 3.7 -release > on a CD (which I burned), but repeatedly received > > halt code 5 > HALT instruction executed > PC = fc230118 > > 'ps' on this yields: > > >>>ps > IDPBCPRICPU TimeAffinity CPU Program State > 002b 0015dac0 3 000010 ps > running > 0029 0017dec0 5 10400010usbd cb > waiting on > usb callback > 0017 0017a840 3 100010 shell ready > 000f 00173040 5 00rx_ewa0 > waiting on > rx_isr_ewa0 > 0008 00166800 3 000010shell_0 > waiting on > rxq_ready > 0006 000315a0 6 10 tt_control > waiting on > tt_control > 0004 0002cb00 7120 timer > waiting on > timer > 0003 0002b6a0 2 387890 poll ready > 0002 0002a480 6 00 dead_eater > waiting on > dead_beef > 0001 00147ac0 0 6067600010 idle ready > > > I then upgraded to 3.6 -stable (thinking was next best thing) via > source upgrade. This went well after some work. I then tried to reboot > from same CD with 3.7 on it, same error. I next downloaded the 3.7 > -release binaries to the drive and replaced the kernel with the new > kernel and tried to reboot. That did not work and is where I am now. I > have enclosed the results of 'trace' and 'ps' as instructed following > the panic. > > I have no idea where to go from here. Any suggestions on how to get 3.7 > installed and running?? > > thanks > > ddb> trace > Debugger(6, fc757b88, fc8580007aa0, c000, , > 8) at > Debugger+0x4 > panic(fc734b30, fa, fc1f3ad8, fc1f3adc, > fc1f3ae0, fc7bfd00) at panic+0x130 > dec_550_intr_map(?, ?, ?, ?, ?, fc7bfd00) at > dec_550_intr_map+0x190 > ohci_pci_attach(?, ?, ?, ?, ?, fcbfd00) at ohci_pci_attach+0x1a8 > config_attach(?, ?, ?, ?, ?, fcbfd00) at config_attach+0x244 > config_found_sm(?, ?, ?, ?, ?, fcbfd00) at config_found_sm+0x54 > pciattach(?, ?, ?, ?, ?, fcbfd00) at pciattach+0x31c > config_attach(?, ?, ?, ?, ?, fcbfd00) at config_attach+0x244 > config_found_sm(?, ?, ?, ?, ?, fcbfd00) at config_found_sm+0x54 > ciaattach(?, ?, ?, ?, ?, fcbfd00) at ciaattach+0x34c > config_attach(?, ?, ?, ?, ?, fcbfd00) at config_attach+0x244 > config_found_sm(?, ?, ?, ?, ?, fcbfd00) at config_found_sm+0x54 > alpha_XXX_dmamap(?, ?, ?, ?, ?, fcbfd00) at > alpha__XXX_dmamap+0x1c0 > config_attach(?, ?, ?, ?, ?, fcbfd00) at config_attach+0x244 > config_rootfound(?, ?, ?, ?, ?, fcbfd00) at > config_rootfound+0x78 > cpu_configure(?, ?, ?, ?, ?, fcbfd00) at cpu_configure+0x48 > main(?, ?, ?, ?, ?, fcbfd00) at main+0x474 > __start(?, ?, ?, ?, ?, fcbfd00) at __start+0x64 > __start(?, ?, ?, ?, ?, fcbfd00) at __start+0x64 > __start(?, ?, ?, ?, ?, fcbfd00) at __start+0x64 > __start(?, ?, ?, ?, ?, fcbfd00) at __start+0x64 > --db_more-- > > > ps > PIDPPIDPGRPUIDSFLAGSWAITCOMMAND > *0 -1 0 0 7 0x80204 swapper > > -- Thanks & Regards, Ikmal aka EvoIVGSR http://www.leakage.org/ http://root.justdied.com/mylife/ http://www.openbsd.org.my/ http://mirrors.mybsd.org.my/
Difficulty upgrading to 3.7
Hope this is the appropriate list for this. Have tried to upgrade to 3.7 from 3.6 for a while a now. Tried booting from binary 3.7 -release on a CD (which I burned), but repeatedly received halt code 5 HALT instruction executed PC = fc230118 'ps' on this yields: >>>ps IDPBCPRICPU TimeAffinity CPU Program State 002b 0015dac0 3 000010 ps running 0029 0017dec0 5 10400010usbd cb waiting on usb callback 0017 0017a840 3 100010 shell ready 000f 00173040 5 00rx_ewa0 waiting on rx_isr_ewa0 0008 00166800 3 000010shell_0 waiting on rxq_ready 0006 000315a0 6 10 tt_control waiting on tt_control 0004 0002cb00 7120 timer waiting on timer 0003 0002b6a0 2 387890 poll ready 0002 0002a480 6 00 dead_eater waiting on dead_beef 0001 00147ac0 0 6067600010 idle ready I then upgraded to 3.6 -stable (thinking was next best thing) via source upgrade. This went well after some work. I then tried to reboot from same CD with 3.7 on it, same error. I next downloaded the 3.7 -release binaries to the drive and replaced the kernel with the new kernel and tried to reboot. That did not work and is where I am now. I have enclosed the results of 'trace' and 'ps' as instructed following the panic. I have no idea where to go from here. Any suggestions on how to get 3.7 installed and running?? thanks ddb> trace Debugger(6, fc757b88, fc8580007aa0, c000, , 8) at Debugger+0x4 panic(fc734b30, fa, fc1f3ad8, fc1f3adc, fc1f3ae0, fc7bfd00) at panic+0x130 dec_550_intr_map(?, ?, ?, ?, ?, fc7bfd00) at dec_550_intr_map+0x190 ohci_pci_attach(?, ?, ?, ?, ?, fcbfd00) at ohci_pci_attach+0x1a8 config_attach(?, ?, ?, ?, ?, fcbfd00) at config_attach+0x244 config_found_sm(?, ?, ?, ?, ?, fcbfd00) at config_found_sm+0x54 pciattach(?, ?, ?, ?, ?, fcbfd00) at pciattach+0x31c config_attach(?, ?, ?, ?, ?, fcbfd00) at config_attach+0x244 config_found_sm(?, ?, ?, ?, ?, fcbfd00) at config_found_sm+0x54 ciaattach(?, ?, ?, ?, ?, fcbfd00) at ciaattach+0x34c config_attach(?, ?, ?, ?, ?, fcbfd00) at config_attach+0x244 config_found_sm(?, ?, ?, ?, ?, fcbfd00) at config_found_sm+0x54 alpha_XXX_dmamap(?, ?, ?, ?, ?, fcbfd00) at alpha__XXX_dmamap+0x1c0 config_attach(?, ?, ?, ?, ?, fcbfd00) at config_attach+0x244 config_rootfound(?, ?, ?, ?, ?, fcbfd00) at config_rootfound+0x78 cpu_configure(?, ?, ?, ?, ?, fcbfd00) at cpu_configure+0x48 main(?, ?, ?, ?, ?, fcbfd00) at main+0x474 __start(?, ?, ?, ?, ?, fcbfd00) at __start+0x64 __start(?, ?, ?, ?, ?, fcbfd00) at __start+0x64 __start(?, ?, ?, ?, ?, fcbfd00) at __start+0x64 __start(?, ?, ?, ?, ?, fcbfd00) at __start+0x64 --db_more-- > ps PIDPPIDPGRPUIDSFLAGSWAITCOMMAND *0 -1 0 0 7 0x80204 swapper
