At 08:57 12-2-2001 -0600, you wrote:
> On Mon, Feb 12, 2001 at 08:51:21AM +0100, Seth Mos wrote:
> > I attached the file that is produced when I'm trying to dial over the
ISDN
> > device using minicom. I will reproduce the samba oops later and send
that
> > one to the list.
>
> [...]
>
> Very much looks like a Eicon bug. I would suggest to contact the Eicon or
> ISDN maintainers. If XFS would corrupt random memory other subsystems would
> break too.
>
>
> -Andi
I would second Andi's opinion on this - we do not have changes in the kernel
which should affect this. Mind you, nothing in the isdn code appears to have
changed much in 2.4.1 either. 2.4.2-pre3 takes a rather large swipe at isdn.
However, I do notice empty_bad_page in the trace - this is not a function
call, but a special page. I checked in one fix in a swapout path on Friday
which was related to pte corruption with XFS, you need the latest
version of mm/vmscan.c. Are you running with this file?
Steve
I waxed the tree the other day, rebuilt it from scratch and rebuild it.
I can't oops the machine under high long disk and aggresive memory use.
Network speed is also normal. Files of 2.8GB are no problem to put onto the
samba share. So I consider this "fixed".
Bye
--
Seth
Has anybody seen my lightbulb?
I _really_ need some light here.
|