Re: problem updating from 4.7 Stable do 5.0 Current

What your server do when it panics? It tries to detect disks?

   Sincerely, Maxim M. Kazachek
       mailto:stranger_at_sberbank.sibnet.ru
       mailto:stranger_at_fpm.ami.nstu.ru


On Mon, 31 Mar 2003, Ventsislav Velkov wrote:

>I could not boot in single user mode with the 5.0 kernel because it brokes.
>Do you mean I should boot in single user with the 4.7 kernel in there installworld and to mergemaster ?
>
>regards,
>Veno
>  ----- Original Message -----
>  From: CARTER Anthony
>  To: freebsd-current_at_freebsd.org
>  Sent: Monday, March 31, 2003 3:15 PM
>  Subject: Re: problem updating from 4.7 Stable do 5.0 Current
>
>
>  Have you installed the world? I don't know if just rebuilding it is
>  sufficient....
>
>  To install the world you have to go to single user mode and run mergemaster to
>  update any changes in configuration files (take a backup of your current
>  files as it overwrites them).
>
>  Anthony
>
>  On Monday 31 March 2003 13:15, Ventsislav Velkov wrote:
>  > Hello all,
>  >
>  > I have a problem updating one of our servers from 4.7Stable to 5.0Current.
>  > It is a Compaq Proliant 7000 Server with 4 Xeons _at_500Mhz with 2MB L2 cache
>  > each. I has a 4200 Compaq Smart Raid Controler with attached 3 U1 Storages.
>  > I update the src rebuild the world from updated src to 5.0Current, build a
>  > GENERIC kernel and installed it. But after I boot it brokes up during the
>  > booting process with the following error:
>  >
>  > //strip
>  >
>  > Fatal trap 12: page fault while in kernel mode cpuid=0; lapic.id= 01000000
>  > fault virtual address = 0x54
>  > fault code = supervisor read, page not present
>  > ....
>  > ....
>  > ....
>  > process eflags = interrupt enabled, resume, IOPL=0
>  > current process = 4(g_down)
>  > kernel: type12trap, code=0
>  > Stopped at ida_construct_qcb+0xe3: movzbl 0x54(%eax),%eax
>  >
>  > //strip
>  >
>  > It may have some punctual mistakes because it is not a copy/paste.
>  >
>  > Will appreciate any advices where could be the problem.
>  >
>  > Best regards,
>  >
>  > Veno
>  > _______________________________________________
>  > freebsd-current_at_freebsd.org mailing list
>  > http://lists.freebsd.org/mailman/listinfo/freebsd-current
>  > To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org"
>  _______________________________________________
>  freebsd-current_at_freebsd.org mailing list
>  http://lists.freebsd.org/mailman/listinfo/freebsd-current
>  To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org"
>_______________________________________________
>freebsd-current_at_freebsd.org mailing list
>http://lists.freebsd.org/mailman/listinfo/freebsd-current
>To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org"
>
>