Hello everybody. Sorry for posting to this list,
but I'm pretty lost.
I'm experimenting this kernel panic on 3 different
slackware linux boxes. The harware is the same, and
also the .config with vanilla 2.6.20
I don't think this is related to buggy hardware
because it is happening on 3 different
Pekka Enberg wrote:
Hi Pekka,
So, can you please repost the original oops?
Here is:
Mar 14 03:42:25 Mimosa kernel: [ cut here ]
Mar 14 03:42:25 Mimosa kernel: kernel BUG at mm/slab.c:610!
Mar 14 03:42:25 Mimosa kernel: invalid opcode: [#1]
Mar 14 03:42:25 Mimosa
Hello everybody.
Since 2.6.19.2 + commit 7fbbb01dca7704d52ace6f45a805c98a5b0362f9
I'm experimenting these errors.
2.6.19.1 has been worked good for more
than 30 days.
I have reverted back to 2.6.19.1 to see if
this problem happens again.
sda8 is a 280GB xfs filesystem which hosts
the squid file
Marco Berizzi wrote:
Pekka Enberg wrote:
Hi Pekka,
So, can you please repost the original oops?
Here is:
Mar 14 03:42:25 Mimosa kernel: [ cut here ]
Mar 14 03:42:25 Mimosa kernel: kernel BUG at mm/slab.c:610!
Mar 14 03:42:25 Mimosa kernel: invalid opcode:
David Chinner wrote:
Ok, so an ipsec change. And I see from the history below it
really has nothing to do with this problem. it seems the problem
has something to do with changes between 2.6.19.1 and 2.6.19.2.
indeed. Yesterday at 13:00 I have switched from 2.6.19.1 to 2.6.19.2
(without the
Hi. Sorry for posting to this list,
but I got this panic with linux
2.6.20
I have also changed the motherboard
of this server and memtest has not
found any error (ram tested for 10
hours)
May anyone tell me if this could
be an hardware problem?
TIA
Linux version 2.6.20 ([EMAIL PROTECTED]) (gcc
Hello everybody.
I'm running oracle 10.2.0.1 on Slackware Linux 10.2
After 50 days uptime, sqlplus was looping forever.
I have killed all oracle processes and cleared all
semaphore and shared memory segment with ipcrm.
I have also unmounted remounted the file system
where the oracle binaries and
Lee Revell wrote:
On 3/28/07, Marco Berizzi [EMAIL PROTECTED] wrote:
Hello everybody.
I'm running oracle 10.2.0.1 on Slackware Linux 10.2
After 50 days uptime, sqlplus was looping forever.
I have killed all oracle processes and cleared all
semaphore and shared memory segment with ipcrm
Christoph Lameter wrote:
Could you try this with the SLUB allocator and then boot with
slub_debug?
Hi Christoph,
I have upgraded to 2.6.22.5 and I have selected
the SLUB. I have also added append=slub_debug to
lilo.conf
After a week uptime I got this error. I hope it
will be useful for you.
Christoph Lameter wrote:
On Tue, 4 Sep 2007, Marco Berizzi wrote:
After a week uptime I got this error. I hope it
will be useful for you.
Yes indeed but this is a different type of failure. Looks like a
higher
allocation failure in the networking code. Someone created objects
Christoph Lameter wrote:
On Wed, 5 Sep 2007, Marco Berizzi wrote:
tcp_collapse? This is due to a network configuration that required
an
order 2 kmalloc block. Jumbo frames?
I don't use jumbo frames. Hardware is
very old (celeron with 3com 3c905).
Something must be doing
Guillaume Chazarain wrote:
Hi, this should be fixed in mainline by
http://git.kernel.org/gitweb.cgi?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=5c127c58ae9bf196d787815b1bd6b0aec5aee816
Thanks everybody.
I was thinking that this fix was included in rc5 (looking at gitweb it
appear
to
Hello.
Linux 2.6.23-rc5 after 30 minutes crash with this
error message (taken from serial console):
BUG: unable to handle kernel NULL pointer dereference at virtual address
0025
printing eip:
*pde =
Oops: [#1]
SMP
Modules linked in: nf_nat_pptp nf_nat_proto_gre
Hello everybody.
I'm running linux 2.6.22 on Slackware.
This box is running openswan 2.4.9
and squid 2.6S13
I get tons of these messages:
Jul 20 01:17:09 Gemini kernel: msnt_auth S 0 8356 819
(NOTLB)
Jul 20 01:17:09 Gemini kernel:c2bd5d54 0086 0001
Hello everybody.
I'm running Slackware 12 with 2.6.23-rc1
and when I start X i get this error:
Jul 24 10:11:16 Calimero kernel: [drm:drm_release] *ERROR*
reclaim_buffers_locked() deadlock. Please rework this
Jul 24 10:11:16 Calimero kernel: driver to use
reclaim_buffers_idlelocked() instead.
Jul
Jesse Barnes wrote:
Looks like a DRM driver problem. Can you file a bug for this at
freedesktop.org if there's not one already?
thanks for the reply. Here is:
https://bugs.freedesktop.org/show_bug.cgi?id=11726
_
Express
Marco Berizzi wrote:
Hello everybody.
I'm running linux 2.6.22 on Slackware.
This box is running openswan 2.4.9
and squid 2.6S13
I get tons of these messages:
Jul 20 01:17:09 Gemini kernel: msnt_auth S 0 8356
819
(NOTLB)
Jul 20 01:17:09 Gemini kernel:c2bd5d54
Marco Berizzi wrote:
Marco Berizzi wrote:
Hello everybody.
I'm running linux 2.6.22 on Slackware.
This box is running openswan 2.4.9
and squid 2.6S13
I get tons of these messages:
Jul 20 01:17:09 Gemini kernel: msnt_auth S 0 8356
819
(NOTLB)
Jul 20 01:17:09
Hello everybody.
This morning isc dhcpd 3.0.5 running on linux 2.6.19.1
(slackware 10.2 glibc 2.3.5 gcc 3.3.6) has been crashed
and this error was logged (I have also noticed that any
kernel message event are written to /var/log/syslog).
Is this a kernel or hardware problem?
[EMAIL
directory.
Chopping out the rest of the top posting (please don't do that)
apologies
we get down to 3 months ago:
On Mon, Mar 19, 2007 at 11:32:27AM +0100, Marco Berizzi wrote:
Marco Berizzi wrote:
Here is the relevant results:
Phase 2 - found root inode chunk
Phase 3
Satyam Sharma wrote:
Hi,
ciao
On 6/8/07, Marco Berizzi [EMAIL PROTECTED] wrote:
After few hours linux has crashed with this message:
BUG: at arch/i386/kernel/smp.c:546 smp_call_function()
Which kernel (exactly) was this
2.6.21.3
and does this occur
reproducibly?
I don't know. I try
Satyam Sharma wrote:
Hi Marco,
Ciao Satyam, thanks for the feedback.
[ Re-adding David, XFS, Andrew and Christoph; this appears to be
some SLAB / fs (?) issue, so I'm a little out of my depth here :-) ]
On 6/8/07, Marco Berizzi [EMAIL PROTECTED] wrote:
After few hours linux has
David Chinner wrote:
On Fri, Jun 08, 2007 at 03:59:39PM +0200, Marco Berizzi wrote:
David Chinner wrote:
Where we saw signs of on disk directory corruption. Have you run
xfs_repair successfully on the filesystem since you reported
this?
yes.
If you did clean up the error
Marco Berizzi wrote:
David Chinner wrote:
On Fri, Jun 08, 2007 at 03:59:39PM +0200, Marco Berizzi wrote:
David Chinner wrote:
Where we saw signs of on disk directory corruption. Have you run
xfs_repair successfully on the filesystem since you reported
this?
yes
Christoph Lameter wrote:
On Thu, 21 Jun 2007, Marco Berizzi wrote:
Some RCU callback (that calls kmem_cache_free()) oopsed and
panic'ed his box. [ Marco had experienced fs issues lately, so
we
could
suspect file_free_rcu() here, but I can't really tell from the
stack
trace
+0100, Marco Berizzi wrote:
Marco Berizzi wrote:
David Chinner wrote:
Ok, so an ipsec change. And I see from the history below it
really has nothing to do with this problem. it seems the problem
has something to do with changes between 2.6.19.1 and 2.6.19.2.
indeed. Yesterday
Hi Folks,
I'm running slackware linux 14 32 bits as a firewall/ipsec
gateway with linux 3.18.0
I got this error just after 12 hours uptime:
WARNING: CPU: 0 PID: 0 at net/sched/sch_generic.c:303 dev_watchdog+0xee/0x174()
NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out
Modules linked in:
Hi Folks,
I'm getting this error with linux-4.10.1 on a very old hp netserver dl360g5
running slackware 14.2
The last working version is linux-4.8.17 (where I don't see this error, and
both cpu0 and cpu1 are enabled.)
[0.00] [ cut here ]
[0.00] WARNING:
Hello everybody.
This morning isc dhcpd 3.0.5 running on linux 2.6.19.1
(slackware 10.2 glibc 2.3.5 gcc 3.3.6) has been crashed
and this error was logged (I have also noticed that any
kernel message event are written to /var/log/syslog).
Is this a kernel or hardware problem?
[EMAIL
Hello everybody. Sorry for posting to this list,
but I'm pretty lost.
I'm experimenting this kernel panic on 3 different
slackware linux boxes. The harware is the same, and
also the .config with vanilla 2.6.20
I don't think this is related to buggy hardware
because it is happening on 3 different
Pekka Enberg wrote:
Hi Pekka,
> So, can you please repost the original oops?
Here is:
Mar 14 03:42:25 Mimosa kernel: [ cut here ]
Mar 14 03:42:25 Mimosa kernel: kernel BUG at mm/slab.c:610!
Mar 14 03:42:25 Mimosa kernel: invalid opcode: [#1]
Mar 14 03:42:25 Mimosa
Hello everybody.
Since 2.6.19.2 + commit 7fbbb01dca7704d52ace6f45a805c98a5b0362f9
I'm experimenting these errors.
2.6.19.1 has been worked good for more
than 30 days.
I have reverted back to 2.6.19.1 to see if
this problem happens again.
sda8 is a 280GB xfs filesystem which hosts
the squid file
Marco Berizzi wrote:
> Pekka Enberg wrote:
>
> Hi Pekka,
>
> > So, can you please repost the original oops?
>
> Here is:
>
> Mar 14 03:42:25 Mimosa kernel: [ cut here ]
> Mar 14 03:42:25 Mimosa kernel: kernel BUG at mm/slab.c:610!
> Ma
David Chinner wrote:
> Ok, so an ipsec change. And I see from the history below it
> really has nothing to do with this problem. it seems the problem
> has something to do with changes between 2.6.19.1 and 2.6.19.2.
indeed. Yesterday at 13:00 I have switched from 2.6.19.1 to 2.6.19.2
(without
Hi. Sorry for posting to this list,
but I got this panic with linux
2.6.20
I have also changed the motherboard
of this server and memtest has not
found any error (ram tested for 10
hours)
May anyone tell me if this could
be an hardware problem?
TIA
Linux version 2.6.20 ([EMAIL PROTECTED]) (gcc
Hello everybody.
I'm running oracle 10.2.0.1 on Slackware Linux 10.2
After 50 days uptime, sqlplus was looping forever.
I have killed all oracle processes and cleared all
semaphore and shared memory segment with ipcrm.
I have also unmounted & remounted the file system
where the oracle binaries and
Lee Revell wrote:
> On 3/28/07, Marco Berizzi <[EMAIL PROTECTED]> wrote:
> > Hello everybody.
> > I'm running oracle 10.2.0.1 on Slackware Linux 10.2
> > After 50 days uptime, sqlplus was looping forever.
> > I have killed all oracle processes and cleared al
Marco Berizzi wrote:
> David Chinner wrote:
>
> > On Fri, Jun 08, 2007 at 03:59:39PM +0200, Marco Berizzi wrote:
> > > David Chinner wrote:
> > > > Where we saw signs of on disk directory corruption. Have you run
> > > > xfs_repair succ
nel: [] vfs_read+0xee/0x141
Jun 6 09:47:09 Pleiadi kernel: [] sys_read+0x41/0x6a
Jun 6 09:47:09 Pleiadi kernel: [] syscall_call+0x7/0xb
Jun 6 09:47:09 Pleiadi kernel: ===
..
David Chinner wrote:
> On Mon, Mar 19, 2007 at 11:32:27AM +0100, Marco Berizzi wr
0x30/0x35
>
> These above stack trace is the sign of a corrupted directory.
>
> Chopping out the rest of the top posting (please don't do that)
apologies
> we get down to 3 months ago:
>
> > > On Mon, Mar 19, 2007 at 11:32:27AM +0100, Marco Berizzi wrote:
> > > >
Satyam Sharma wrote:
> Hi,
ciao
> On 6/8/07, Marco Berizzi <[EMAIL PROTECTED]> wrote:
>> After few hours linux has crashed with this message:
>> BUG: at arch/i386/kernel/smp.c:546 smp_call_function()
>
> Which kernel (exactly) was this
2.6.21.3
> and does th
Satyam Sharma wrote:
> Hi Marco,
Ciao Satyam, thanks for the feedback.
> [ Re-adding David, XFS, Andrew and Christoph; this appears to be
> some SLAB / fs (?) issue, so I'm a little out of my depth here :-) ]
>
> > > On 6/8/07, Marco Berizzi <[EMAIL PROTECTED]> wr
David Chinner wrote:
> On Fri, Jun 08, 2007 at 03:59:39PM +0200, Marco Berizzi wrote:
> > David Chinner wrote:
> > > Where we saw signs of on disk directory corruption. Have you run
> > > xfs_repair successfully on the filesystem since you reported
> > > thi
Christoph Lameter wrote:
> On Thu, 21 Jun 2007, Marco Berizzi wrote:
>
> > > > Some RCU callback (that calls kmem_cache_free()) oopsed and
> > > > panic'ed his box. [ Marco had experienced fs issues lately, so
we
> > > could
> > > > suspect
Christoph Lameter wrote:
> Could you try this with the SLUB allocator and then boot with
> "slub_debug"?
Hi Christoph,
I have upgraded to 2.6.22.5 and I have selected
the SLUB. I have also added append=slub_debug to
lilo.conf
After a week uptime I got this error. I hope it
will be useful for
"Christoph Lameter" wrote:
> On Tue, 4 Sep 2007, Marco Berizzi wrote:
>
> > After a week uptime I got this error. I hope it
> > will be useful for you.
>
> Yes indeed but this is a different type of failure. Looks like a
higher
> allocation failure in the net
Christoph Lameter wrote:
> On Wed, 5 Sep 2007, Marco Berizzi wrote:
>
> > > tcp_collapse? This is due to a network configuration that required
an
> > > order 2 kmalloc block. Jumbo frames?
> >
> > I don't use jumbo frames. Hardware is
> > very old (ce
Hello everybody.
I'm running linux 2.6.22 on Slackware.
This box is running openswan 2.4.9
and squid 2.6S13
I get tons of these messages:
Jul 20 01:17:09 Gemini kernel: msnt_auth S 0 8356 819
(NOTLB)
Jul 20 01:17:09 Gemini kernel:c2bd5d54 0086 0001
Hello everybody.
I'm running Slackware 12 with 2.6.23-rc1
and when I start X i get this error:
Jul 24 10:11:16 Calimero kernel: [drm:drm_release] *ERROR*
reclaim_buffers_locked() deadlock. Please rework this
Jul 24 10:11:16 Calimero kernel: driver to use
reclaim_buffers_idlelocked() instead.
Jul
Jesse Barnes wrote:
Looks like a DRM driver problem. Can you file a bug for this at
freedesktop.org if there's not one already?
thanks for the reply. Here is:
https://bugs.freedesktop.org/show_bug.cgi?id=11726
_
Express
Marco Berizzi wrote:
> Hello everybody.
> I'm running linux 2.6.22 on Slackware.
> This box is running openswan 2.4.9
> and squid 2.6S13
> I get tons of these messages:
>
> Jul 20 01:17:09 Gemini kernel: msnt_auth S 0 8356
819
> (NOTLB)
> Ju
Marco Berizzi wrote:
> Marco Berizzi wrote:
>
> > Hello everybody.
> > I'm running linux 2.6.22 on Slackware.
> > This box is running openswan 2.4.9
> > and squid 2.6S13
> > I get tons of these messages:
> >
> > Jul 20 01:17:09 Gemini kernel: msnt_
Guillaume Chazarain wrote:
> Hi, this should be fixed in mainline by
>
http://git.kernel.org/gitweb.cgi?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=5c127c58ae9bf196d787815b1bd6b0aec5aee816
Thanks everybody.
I was thinking that this fix was included in rc5 (looking at gitweb it
appear
to
Hello.
Linux 2.6.23-rc5 after 30 minutes crash with this
error message (taken from serial console):
BUG: unable to handle kernel NULL pointer dereference at virtual address
0025
printing eip:
*pde =
Oops: [#1]
SMP
Modules linked in: nf_nat_pptp nf_nat_proto_gre
Hi Folks,
I'm running slackware linux 14 32 bits as a firewall/ipsec
gateway with linux 3.18.0
I got this error just after 12 hours uptime:
WARNING: CPU: 0 PID: 0 at net/sched/sch_generic.c:303 dev_watchdog+0xee/0x174()
NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out
Modules linked in:
Hi Folks,
I'm getting this error with linux-4.10.1 on a very old hp netserver dl360g5
running slackware 14.2
The last working version is linux-4.8.17 (where I don't see this error, and
both cpu0 and cpu1 are enabled.)
[0.00] [ cut here ]
[0.00] WARNING:
56 matches
Mail list logo
