[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Kernel Divide error trap

From: Marcus Brinkmann
Subject: Re: Kernel Divide error trap
Date: Wed, 26 Sep 2001 13:35:38 +0200
User-agent: Mutt/1.3.22i

On Tue, Sep 25, 2001 at 09:57:23PM +0200, Piotr Krukowiecki wrote:
> >         byte = inb(pitctr0_port);       /* least siginifcant */
> here
> >         leftover = inb(pitctr0_port);   /* most significant */
> here

Those two printk's will indeed change the value of leftover completely, if I
am not completely off track what's happening here.  Please remove those.

> >         leftover = (leftover<<8) + byte ;
> and here i have added printk's

After leftover is calculated, it is definitely safe to print that value.

> Anyway, first leftover is f3, second f3ff, so i'ts close to ffff

Just print the final calculation.
> Now, should i left that printk or maybe better would be to add sth. like 
> if (leftover == 0xffff) leftover -= 1;

The last printk should be ok.  BTW, oskit-mach does not use that code, so
the problem will go away in the future.  However, we might be able to just
ditch this code in gnumach in favour of the Linux BogoMIPS calculation (we do
that already, we just need to make use of it for mach, too, not only for the
linux drivers).

> And another bug, maybe know already:
> [...]
> cleaning up left over files...panic: choose_pset_thread
> Kernel Breakpoint trap, eip 0x10d3d8
> Stopped ad 0x10d3d8:    int     $3

Never seen this!  Seems your destiny is to be a kernel hacker ;)
It also should not happen... mmh.


`Rhubarb is no Egyptian god.' Debian http://www.debian.org brinkmd@debian.org
Marcus Brinkmann              GNU    http://www.gnu.org    marcus@gnu.org

reply via email to

[Prev in Thread] Current Thread [Next in Thread]