On Fri, Dec 01, 2000 at 12:46:18PM +, Alan Cox wrote:
> > I was able to reproduce this oops with a somewhat more reliable ksymoops (I was
>ready for this nasty bug this time). Looks like the problem is in the sockets
> > code.
>
> The traces so far all match one description , this one
> I was able to reproduce this oops with a somewhat more reliable ksymoops (I was
>ready for this nasty bug this time). Looks like the problem is in the sockets
> code.
The traces so far all match one description , this one included. Its the
'something scribbled a while ago and I just walked
I was able to reproduce this oops with a somewhat more reliable ksymoops (I was
ready for this nasty bug this time). Looks like the problem is in the sockets
code.
The traces so far all match one description , this one included. Its the
'something scribbled a while ago and I just walked the
On Fri, Dec 01, 2000 at 12:46:18PM +, Alan Cox wrote:
I was able to reproduce this oops with a somewhat more reliable ksymoops (I was
ready for this nasty bug this time). Looks like the problem is in the sockets
code.
The traces so far all match one description , this one included.
Alan,
I was able to reproduce this oops with a somewhat more reliable ksymoops (I was ready
for this nasty bug this time). Looks like the problem is in the sockets
code.
See attached.
Jeff
ksymoops 0.7c on i686 2.2.18pre21. Options used
EIP: 0010: []
Using defaults from ksymoops -t
Alan,
I was able to reproduce this oops with a somewhat more reliable ksymoops (I was ready
for this nasty bug this time). Looks like the problem is in the sockets
code.
See attached.
Jeff
ksymoops 0.7c on i686 2.2.18pre21. Options used
EIP: 0010: [c013365d]
Using defaults from ksymoops
6 matches
Mail list logo
