In message <[EMAIL PROTECTED]>, Mike Smith writes:
>>
>> Ahh, Ok.
>>
>> Bruce (a little hasty in my mind) removed a compat shim we had,
>> please change the 'rda' to 'da' again and all should be fine.
>
>Actually, I did the dirty work because I agreed with Bruce. What I don't
>understand is wh
:> Bruce (a little hasty in my mind) removed a compat shim we had,
:> please change the 'rda' to 'da' again and all should be fine.
:
:Actually, I did the dirty work because I agreed with Bruce. What I don't
:understand is why the system explodes when it can't find /, rather than
:giving up cle
>
> Ahh, Ok.
>
> Bruce (a little hasty in my mind) removed a compat shim we had,
> please change the 'rda' to 'da' again and all should be fine.
Actually, I did the dirty work because I agreed with Bruce. What I don't
understand is why the system explodes when it can't find /, rather than
gi
At 10:23 PM 11/29/99 +0100, Poul-Henning Kamp wrote:
>Ahh, Ok.
>
>Bruce (a little hasty in my mind) removed a compat shim we had,
>please change the 'rda' to 'da' again and all should be fine.
>
>Poul-Henning
Done
Thanks
Manfred
=
||[EMAIL PROTECTED] ||
||Ph. (4
Ahh, Ok.
Bruce (a little hasty in my mind) removed a compat shim we had,
please change the 'rda' to 'da' again and all should be fine.
Poul-Henning
In message <[EMAIL PROTECTED]>, Manfred Antar writes:
>At 09:55 PM 11/29/99 +0100, Poul-Henning Kamp wrote:
>
>>Do you have /dev/sd* in your /etc/
At 09:55 PM 11/29/99 +0100, Poul-Henning Kamp wrote:
>Do you have /dev/sd* in your /etc/fstab ?
>
>It should be changed to /dev/da*
This is what I have
# DeviceMountpoint FStype Options DumpPass#
/dev/rda0s1bnoneswapsw 0 0
/dev/rda
Manfred,
Could you send the 10 lines surrounding the address 0xc014a79a
from the output of "nm -n /this_kernel" ?
In message <[EMAIL PROTECTED]>, Manfred Antar writes:
>Mike
>I get a panic on current smp-kernel with the new version
>of vfs_conf.c .
>The system is current as of this morning
>If
At 09:29 PM 11/29/99 +0100, Poul-Henning Kamp wrote:
>Manfred,
>
>Could you send the 10 lines surrounding the address 0xc014a79a
>from the output of "nm -n /this_kernel" ?
OK
This kernel was striped -g
do you need a debug compiled kernel ?
Here is what i get
c014a1c8 T set_timecounter
c014a234 t
:Mike
:I get a panic on current smp-kernel with the new version
:of vfs_conf.c .
:The system is current as of this morning
:If I back out to version 1.44 it boots fine.
:It seems to panic at the swapon part of the boot process.
:I get :
:Fatal trap 12: page fault while in kernel mode
:mp_lock = 0
At 12:26 PM 11/29/99 -0800, Matthew Dillon wrote:
>:Mike
>:I get a panic on current smp-kernel with the new version
>:of vfs_conf.c .
>:The system is current as of this morning
>:If I back out to version 1.44 it boots fine.
>:It seems to panic at the swapon part of the boot process.
>:I get :
>:F
Do you have /dev/sd* in your /etc/fstab ?
It should be changed to /dev/da*
In message <[EMAIL PROTECTED]>, Manfred Antar writes:
>At 09:29 PM 11/29/99 +0100, Poul-Henning Kamp wrote:
>
>>Manfred,
>>
>>Could you send the 10 lines surrounding the address 0xc014a79a
>>from the output of "nm -n /th
:c014a794 T devsw
:c014a7b0 T cdevsw_add
c014a79a --- sounds like the same or a similar bug to the one I
fixed, where devsw() was being called with rootdev == NODEV (-1)
and doing a NULL (well -1) pointer dereference.
In my case it was related to an assumption at line 203 of v
Mike
I get a panic on current smp-kernel with the new version
of vfs_conf.c .
The system is current as of this morning
If I back out to version 1.44 it boots fine.
It seems to panic at the swapon part of the boot process.
I get :
Fatal trap 12: page fault while in kernel mode
mp_lock = 0102;
13 matches
Mail list logo
