On Sun, 15 Apr 2001, Arthur Pedyczak wrote:
> On Sat, 14 Apr 2001, Jeff Garzik wrote:
>
> > Can you try 2.4.4-pre3?
> > ftp://ftp.us.kernel.org/pub/linux/kernel/testing/
> >
...the same thing happens in 2.4.3...
> I am testing loop behaviour in 2.4.3 and 3.4.4p
On Sat, 14 Apr 2001, Jeff Garzik wrote:
> Can you try 2.4.4-pre3?
> ftp://ftp.us.kernel.org/pub/linux/kernel/testing/
>
I am testing loop behaviour in 2.4.3 and 3.4.4p3. I have noticed something
disturbing:
I can mount the same file on the same mountpoint more than once. If I
mount a file twice
came
from
> If you're intent on making it oops why not write a script to
mount/unmount
> it repeatedly?
>
>
> Regards,
> Aaron
>
>
> -Original Message-
> From: Arthur Pedyczak <[EMAIL PROTECTED]>
> To: Jens Axboe <[EMAIL PROTECTED]>
&
On Sat, 14 Apr 2001, Jens Axboe wrote:
[ SNIP..]
> > =
> > Apr 13 20:50:03 cs865114-a kernel: Unable to handle kernel paging request at
>virtual address 7e92bfd7
>
> Please disable syslog decoding (it sucks) and feed it through ksymoops
> instead.
>
> In other
Hi all,
here are my $0.02 regarding loop in 2.4.3.
1. mounted file
mount -t iso9660 -o loop file.img /mnt/cdrom
worked o.k.
2. unmounted
umount /mnt/cdrom
worked o.k.
3. mounted file
mount -t iso9660 -o loop file.img /mnt/cdrom
worked o.k.
4. tried to unmount
umount /mnt/cdrom
got
Hi all,
After running 2.4.3 for 9 days my system froze when copying a cd
(dd if=/dev/cdrom of=file)
After rebooting I found the following in the syslog:
===
Apr 12 22:05:28 cs865114-a kernel: Unable to handle kernel paging request at virtual
a
The subject says it all. The bug got trigerred under _Heavy_ load
(bootstraping gcc ang building Xfree at the same time).
My hardware:
Motherboard: Asus P2B
CPU: P-III 600 (no overclocking)
RAM: 384 MB
IDE: PIIX4: IDE controller on PCI bus 00 dev 21
PIIX4: c
My personal experience strongly suggests that the NVdriver is the
culprit.
Try geting rid of it.
Arthur
On Sun, 4 Mar 2001, Romain Chantereau wrote:
> Hi,
>
> I didn't know where send this bug report, so I send it here as writen in
> the Doc... Sorry if I mistake...
>
> Ok, I have a Debian sid
On Wed, 7 Feb 2001, Alan Cox wrote:
> > report got ignored). After running for 4 days I got many, many oopses.
> > They were trigerred by xscreensaver, and some other X-related apps.
> > After dopping to runlevel 3, the system seemed O.K. Nothing unusual in
> > graphics: Riva TNT2
>
> That makes
On Wed, 7 Feb 2001, Alan Cox wrote:
> > am not sure how to eliminate or confirm this. Recently I added some RAM
> > (256->384) and decided to get rid of swap. This seemed to have destabilized
> > the system, although nothing is obvious. I can try to stress the system by
>
> Get a copy of memtest8
On Wed, 7 Feb 2001, Alan Cox wrote:
> > report got ignored). After running for 4 days I got many, many oopses.
> > They were trigerred by xscreensaver, and some other X-related apps.
> > After dopping to runlevel 3, the system seemed O.K. Nothing unusual in
> > graphics: Riva TNT2
>
> That makes
Hi all,
I have a misfortune of reporting yet another Oops in 2.4.1 (my previous
report got ignored). After running for 4 days I got many, many oopses.
They were trigerred by xscreensaver, and some other X-related apps.
After dopping to runlevel 3, the system seemed O.K. Nothing unusual in
proces
Hi all,
After 1 day of running, 2.4.1 produced 'kernel BUG at dcache.c:134!' and
Oops
during regular RedHat cron job
(tmpwatch + slocate):
Feb 1 04:27:21 cs865114-a kernel: kernel BUG at dcache.c:134!
Feb 1 04:27:21 cs865114-a kernel: invalid operand:
Feb 1 04:27:21 cs865114-a kernel: CP
Hi all,
I have been running 2.4.0 for 8 days with no problem. Then standard
RedHat cron job (slocate.cron) generated an oops:
ksymoops 2.3.4 on i686 2.4.0. Options used
-v /usr/src/linux/vmlinux (specified)
Hi all,
I had been running 2.4.0-test12 for 7 days. Worked great. Then the
system just froze. No oopses,
no log entries, no telneting to the box, no SysRq. Hard reboot. Some 12
hrs. later I got the following Oops in xfs. At that time I was
installing Corel Photopaint and the install was going thro
Hi All,
I have just gotten the following Oops.
The system was working under significant load (CPU intensive computation
+ verification of a freshly burned CD).
ksymoops 2.3.4 on i686 2.4.0-test9. Opti
16 matches
Mail list logo
