Thanks for all the tips, guys.
I managed to get the problem to occur on a vanilla kernel with just the
proprietary module loaded. Contacted the vendor, they got me to try out
a new driver, problem appears to be fixed.
Looks like the module wasn't properly tracking refcounts, so it was
being
On Fri, 2 Sep 2005, Christopher Friesen wrote:
>
> I'm debugging a problem. Unfortunately, I have a module loaded that taints
> the kernel.
>
> Now that that's out of the way, if anyone is still willing to help, the oops
> is below, along with the disassembly of filp_close(). One thing I don't
In-Reply-To: <[EMAIL PROTECTED]>
On Fri, 02 Sep 2005 at 22:25:40 -0600, Christopher Friesen wrote:
> One thing I
> don't understand--the function makes calls to other functions including
> printk(), but I don't see those calls listed in the disassembly.
Calls to external functions whose addres
Christopher Friesen napsal(a):
[snip]
EIP is at filp_close+0x64/0xa0
[snip]
0x1a9a : call 0x1a9b
0x1a9f : mov%edi,0x4(%esp,1)
0x1aa3 : mov%ebx,(%esp,1)
[snip]
End of assembler dump.
It seems, that this is disassemble output of something else. The
fun
4 matches
Mail list logo
