Re: Repeatable Oops in 2.4t13p4ac2

2000-12-28 Thread Alan Cox
> I am fairly confident something in ac2 is fishy. I can repeatable get > ac2 to fail with PCMCIA and also reiserfs under load, I absolutely > cannot get these failures without ac2. The PCMCIA thing is unlikely to be related (there are no changes on any PCMCIA that actually worked on 13pre4).

Re: Repeatable Oops in 2.4t13p4ac2

2000-12-28 Thread Marcelo Tosatti
On Thu, 28 Dec 2000 [EMAIL PROTECTED] wrote: > > > > > > > > > > Do you remember if the reports you've got always oopsed the same > > > > > address (004) ? > > > > > > Hi - Here's another Oops from the same machine. It looks to be in a totally > different place in the code which

Re: Repeatable Oops in 2.4t13p4ac2

2000-12-28 Thread chris
> > > > > > > > Do you remember if the reports you've got always oopsed the same > > > > address (004) ? > > > Hi - Here's another Oops from the same machine. It looks to be in a totally different place in the code which probably means it's a memory problem? I'll try installing on

Re: Repeatable Oops in 2.4t13p4ac2

2000-12-28 Thread Alan Cox
> > > Alan, > > > > > > Do you remember if the reports you've got always oopsed the same > > > address (004) ? > > > > They vary in report > > Doesn't it sounds like memory problems? For -ac Im working on the assumption I introduced a bug into the mm code - To unsubscribe from this

Re: Repeatable Oops in 2.4t13p4ac2

2000-12-28 Thread Marcelo Tosatti
On Thu, 28 Dec 2000, Alan Cox wrote: > > Alan, > > > > Do you remember if the reports you've got always oopsed the same > > address (004) ? > > They vary in report Doesn't it sounds like memory problems? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

Re: Repeatable Oops in 2.4t13p4ac2

2000-12-28 Thread Alan Cox
> Alan, > > Do you remember if the reports you've got always oopsed the same > address (004) ? They vary in report - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/

Re: Repeatable Oops in 2.4t13p4ac2

2000-12-28 Thread Marcelo Tosatti
On Thu, 28 Dec 2000, Alan Cox wrote: > > Hi - we are seeing the following repeatable Oops in 2.4t13p4ac2 compiled using > > gcc 2.95.2 for PIII running on IDE disks. Occurs whilst copying lots of files > > to/from remote filesystems. > > I've had a couple of reports

Re: Repeatable Oops in 2.4t13p4ac2

2000-12-28 Thread Alan Cox
> Hi - we are seeing the following repeatable Oops in 2.4t13p4ac2 compiled using > gcc 2.95.2 for PIII running on IDE disks. Occurs whilst copying lots of files > to/from remote filesystems. I've had a couple of reports like this. Can you test 2.4t13p4 without the -ac changes. I

Re: Repeatable Oops in 2.4t13p4ac2

2000-12-28 Thread Marcelo Tosatti
On Thu, 28 Dec 2000 [EMAIL PROTECTED] wrote: > Hi - we are seeing the following repeatable Oops in 2.4t13p4ac2 compiled using > gcc 2.95.2 for PIII running on IDE disks. Occurs whilst copying lots of files > to/from remote filesystems. > > Thank you > > Chris > &

Repeatable Oops in 2.4t13p4ac2

2000-12-28 Thread chris
Hi - we are seeing the following repeatable Oops in 2.4t13p4ac2 compiled using gcc 2.95.2 for PIII running on IDE disks. Occurs whilst copying lots of files to/from remote filesystems. Thank you Chris Unable to handle kernel paging request at virtual address 0004 c0131891 *pde =

Repeatable Oops in 2.4t13p4ac2

2000-12-28 Thread chris
Hi - we are seeing the following repeatable Oops in 2.4t13p4ac2 compiled using gcc 2.95.2 for PIII running on IDE disks. Occurs whilst copying lots of files to/from remote filesystems. Thank you Chris Unable to handle kernel paging request at virtual address 0004 c0131891 *pde =

Re: Repeatable Oops in 2.4t13p4ac2

2000-12-28 Thread Marcelo Tosatti
On Thu, 28 Dec 2000 [EMAIL PROTECTED] wrote: Hi - we are seeing the following repeatable Oops in 2.4t13p4ac2 compiled using gcc 2.95.2 for PIII running on IDE disks. Occurs whilst copying lots of files to/from remote filesystems. Thank you Chris Unable to handle kernel paging

Re: Repeatable Oops in 2.4t13p4ac2

2000-12-28 Thread Alan Cox
Hi - we are seeing the following repeatable Oops in 2.4t13p4ac2 compiled using gcc 2.95.2 for PIII running on IDE disks. Occurs whilst copying lots of files to/from remote filesystems. I've had a couple of reports like this. Can you test 2.4t13p4 without the -ac changes. If the -ac changes

Re: Repeatable Oops in 2.4t13p4ac2

2000-12-28 Thread Marcelo Tosatti
On Thu, 28 Dec 2000, Alan Cox wrote: Hi - we are seeing the following repeatable Oops in 2.4t13p4ac2 compiled using gcc 2.95.2 for PIII running on IDE disks. Occurs whilst copying lots of files to/from remote filesystems. I've had a couple of reports like this. Can you test 2.4t13p4

Re: Repeatable Oops in 2.4t13p4ac2

2000-12-28 Thread Alan Cox
Alan, Do you remember if the reports you've got always oopsed the same address (004) ? They vary in report - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/

Re: Repeatable Oops in 2.4t13p4ac2

2000-12-28 Thread Marcelo Tosatti
On Thu, 28 Dec 2000, Alan Cox wrote: Alan, Do you remember if the reports you've got always oopsed the same address (004) ? They vary in report Doesn't it sounds like memory problems? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of

Re: Repeatable Oops in 2.4t13p4ac2

2000-12-28 Thread Alan Cox
Alan, Do you remember if the reports you've got always oopsed the same address (004) ? They vary in report Doesn't it sounds like memory problems? For -ac Im working on the assumption I introduced a bug into the mm code - To unsubscribe from this list: send the line

Re: Repeatable Oops in 2.4t13p4ac2

2000-12-28 Thread chris
Do you remember if the reports you've got always oopsed the same address (004) ? Hi - Here's another Oops from the same machine. It looks to be in a totally different place in the code which probably means it's a memory problem? I'll try installing on another box to

Re: Repeatable Oops in 2.4t13p4ac2

2000-12-28 Thread Marcelo Tosatti
On Thu, 28 Dec 2000 [EMAIL PROTECTED] wrote: Do you remember if the reports you've got always oopsed the same address (004) ? Hi - Here's another Oops from the same machine. It looks to be in a totally different place in the code which probably means it's a

Re: Repeatable Oops in 2.4t13p4ac2

2000-12-28 Thread Alan Cox
I am fairly confident something in ac2 is fishy. I can repeatable get ac2 to fail with PCMCIA and also reiserfs under load, I absolutely cannot get these failures without ac2. The PCMCIA thing is unlikely to be related (there are no changes on any PCMCIA that actually worked on 13pre4).