Using 2.2.17 kernel that is standard other than the bridging firewall
patch, this Oops happened while setting up tripwire - it was scanning
the disk and then locked up. As its purely a remote machine, I am only
able to go off of the logs in syslogd. Below is the ksymoops report. If
im leaving
(Please cc: me directly if you so choose, I am not subscribed to l-k at the
moment. Thanks. Otherwise, I'll follow the thread in a l-k archive.)
All,
I'd like to enlist your help in diagnosing a series of oopsen over the last
eight weeks. I didn't start tracking the problem in detail until a
On Fri, 17 Nov 2000 14:49:38 Rasmus Andersen wrote:
> Hi.
>
> I get an oops reproducably with 2.2.17 and 2.2.18pre21 on a stock RH 6.2
> system. I cannot trigger it with the RH supplied kernel (2.2.14-5.0).
> I also got it with 2.2.17pre10 which prompted me to upgrade the kernel.
> I initially s
On Fri, 17 Nov 2000, Rasmus Andersen wrote:
> Hi.
>
> I get an oops reproducably with 2.2.17 and 2.2.18pre21 on a stock RH 6.2
> system. I cannot trigger it with the RH supplied kernel (2.2.14-5.0).
> I also got it with 2.2.17pre10 which prompted me to upgrade the kernel.
> I initially suspecte
Hi.
I get an oops reproducably with 2.2.17 and 2.2.18pre21 on a stock RH 6.2
system. I cannot trigger it with the RH supplied kernel (2.2.14-5.0).
I also got it with 2.2.17pre10 which prompted me to upgrade the kernel.
I initially suspected bad RAM but have exchanged the RAM with memtest86'ed
RAM
>
> OK, I tried with 2.2.16 and 2.2.18pre21 compiled with egcs-2.91.66
> (the kernels reported yesterday were compiled with 2.95.2).
>
> 2.2.16 oopsed faithfully (I could not get hold of the oops as several
> scrolled by and none made it to the log). 2.2.18pre21 does not oops.
> Bzip2 core dumps
> I get this also with 2.2.17pre10 (which was what I was running before
> encountering this) but not with the stock RH 6.2 kernel (2.2.14-5.0).
> Unless I get other suggestions I'm going to try with the latest 2.2.18pre
> and 2.2.16 tomorrow.
>
OK, I tried with 2.2.16 and 2.2.18pre21 compiled wi
Hi.
When running 'tar cvIf /' or 'tar cvzf /' (but sometimes not
with 'plain' tar, i.e., without compression) I get an oops after some
time. This is reproducible. The oops below is from a 'tar cvIf' run.
I get this also with 2.2.17pre10 (which was what I was running before
encountering this)
Today I've found the following in my /var/log/messages:
Oct 28 20:14:36 some_host kernel: kmem_free: Bad obj addr (objp=c2b381e0,
name=size-64)
Oct 28 20:14:36 some_host kernel: Unable to handle kernel NULL pointer dereference at
virtual address
Oct 28 20:14:36 some_host kernel: cur
I'm running 2.2.17 on Dual SMP system. This appeared on syslog last
night:
Oct 18 03:28:39 trane kernel: Unable to handle kernel paging request
at virtual address 2d4d524d
Oct 18 03:28:39 trane kernel: current->tss.cr3 = 00101000, %cr3 =
00101000
Oct 18 03:28:39 trane kernel: *pde =
O
10 matches
Mail list logo
