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
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
(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
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
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
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
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 suspected bad
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
>
> 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
> 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
On Mon, Nov 13, 2000 at 11:10:08PM -0600, Peter Samuelson wrote:
>
> [Rasmus Andersen]
> > I'm getting oopses on a linux 2.2.17 box when I try to do
> > tar cvIf -X /. Reproducably.
>
> Are you excluding /proc? Trying to back up all of /proc is definitely
> asking for trouble, although the
On Mon, Nov 13, 2000 at 11:10:08PM -0600, Peter Samuelson wrote:
[Rasmus Andersen]
I'm getting oopses on a linux 2.2.17 box when I try to do
tar cvIf file -Xfile /. Reproducably.
Are you excluding /proc? Trying to back up all of /proc is definitely
asking for trouble, although the
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 with
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, but
[Rasmus Andersen]
> I'm getting oopses on a linux 2.2.17 box when I try to do
> tar cvIf -X /. Reproducably.
Are you excluding /proc? Trying to back up all of /proc is definitely
asking for trouble, although the oops still indicates a kernel bug.
Peter
-
To unsubscribe from this list: send
On Mon, 13 Nov 2000, Rasmus Andersen wrote:
> Hi.
>
> I'm getting oopses on a linux 2.2.17 box when I try to do
> tar cvIf -X /. Reproducably. This works fine
> for the std. RH 6.2 kernel (2.2.14-5). The resulting file
> is about 20MB.
>
> I would submit the oops, but it is run through
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)
Hi.
I'm getting oopses on a linux 2.2.17 box when I try to do
tar cvIf -X /. Reproducably. This works fine
for the std. RH 6.2 kernel (2.2.14-5). The resulting file
is about 20MB.
I would submit the oops, but it is run through klogd and
I seem to remember people expressing dissatisfaction
Hi.
When running 'tar cvIf file /' or 'tar cvzf file /' (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
On Mon, 13 Nov 2000, Rasmus Andersen wrote:
Hi.
I'm getting oopses on a linux 2.2.17 box when I try to do
tar cvIf file -Xfile /. Reproducably. This works fine
for the std. RH 6.2 kernel (2.2.14-5). The resulting file
is about 20MB.
I would submit the oops, but it is run through
[Rasmus Andersen]
I'm getting oopses on a linux 2.2.17 box when I try to do
tar cvIf file -Xfile /. Reproducably.
Are you excluding /proc? Trying to back up all of /proc is definitely
asking for trouble, although the oops still indicates a kernel bug.
Peter
-
To unsubscribe from this list:
Hello i got me several nasty oopses on my heavily loaded webserver.
[1.] One line summary of the problem:
I get a oops that seems to generate more oops.
My logs are full of them bastards.
I hate them. GRRR.
[2.] Full description of the problem/report:
I recently upgraded my box to 1GB of mem,
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:
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:
Casually browsing through my system logs, I came upon this two oopses
that happened together (logged as same second). I don't really remember
what situation was surrounding, or even if any interruption was
experienced. The system did totally freeze just under 30 minutes later,
however, with no
Casually browsing through my system logs, I came upon this two oopses
that happened together (logged as same second). I don't really remember
what situation was surrounding, or even if any interruption was
experienced. The system did totally freeze just under 30 minutes later,
however, with no
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 =
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 =
On Fri, 29 Sep 2000 23:48:34 -0500 (CDT),
Erik McKee <[EMAIL PROTECTED]> wrote:
>I recieved this oops on boot up. ksymoops claims that the module is from
>2.2.16, but I haven't touched any of the modules after make
>modules_install.
>Warning (compare_Version): Version mismatch. 3c507 says
Hello!
I recieved this oops on boot up. ksymoops claims that the module is from
2.2.16, but I haven't touched any of the modules after make
modules_install. Also, with 2.2.17 my networking freezes up more
frequently then before. I only use ethernet and not ppp, so I don't now
why this module
Hello!
I recieved this oops on boot up. ksymoops claims that the module is from
2.2.16, but I haven't touched any of the modules after make
modules_install. Also, with 2.2.17 my networking freezes up more
frequently then before. I only use ethernet and not ppp, so I don't now
why this module
33 matches
Mail list logo
