John Baldwin <[EMAIL PROTECTED]> writes:
> On 24-Nov-01 Martin Blapp wrote:
> > - realitexpire, td);
> > + realitexpire, td->td_proc);
> >
> > Fixes the panic 100%.
> Ouch, something this simple definitely caused a warning, it looks
> like warnings are being ig
On 26-Nov-01 Garrett Wollman wrote:
> <
> said:
>
>>> - realitexpire, td);
>>> + realitexpire, td->td_proc);
>
>> Ouch, something this simple definitely caused a warning, it looks like
>> warnings
>> are being ignored. :(
>
> Nope. Look at the prototype for
< said:
>> - realitexpire, td);
>> + realitexpire, td->td_proc);
> Ouch, something this simple definitely caused a warning, it looks like warnings
> are being ignored. :(
Nope. Look at the prototype for callout_reset() and then think about
why the last two p
On 24-Nov-01 Martin Blapp wrote:
>
> Hi DES,
>
> - realitexpire, td);
> + realitexpire, td->td_proc);
>
> Fixes the panic 100%.
>
> Thanks a lot !
>
> Martin
Ouch, something this simple definitely caused a warning, it looks like warnings
are being ignored
Hi DES,
- realitexpire, td);
+ realitexpire, td->td_proc);
Fixes the panic 100%.
Thanks a lot !
Martin
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Martin Blapp <[EMAIL PROTECTED]> writes:
> kernel trap 12 with interrupts disabled
>
> Fatal trap 12: page fault while in kernel mode
> fault virtual address = 0x123423bd
> fault code = supervisor read, page not present
> instruction pointer = 0x8:0xc024d74a
> stack pointer
Hi DES, John,
It does not lock the box completly, but it still panics. Sorry.
DDB over serial connection:
#./unilockd
lock order reversal
1st 0xc04a8e80 sched lock @ /usr/src/sys/kern/kern_mutex.c:319
2nd 0xc049d8a0 sio @ /usr/src/sys/dev/sio/sio.c:2958
kernel trap 12 with interrupts disabl
