On Fri, 22 Jun 2007 11:22:09 +0200
"Marco Berizzi" <[EMAIL PROTECTED]> wrote:
> With the same kernel or should I compile with
> some other options?
With the same kernel. No additional options are needed.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a m
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
st
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;
> > > BTW whats with t
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?
>
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 cle
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, does xfs_repair repor
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 linu
> 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 to explain. With all de
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
Hi,
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, and does this occur
reproducibly? Also, could you please send the dmesg,
stack trace, etc for whe
David Chinner wrote:
> > Jun 6 09:47:09 Pleiadi kernel: ===
> > Jun 6 09:47:09 Pleiadi kernel: 0x0: 28 f1 45 d4 22 53 35 11 09 80
37 5a
> > 47 8a 22 ee
> > Jun 6 09:47:09 Pleiadi kernel: Filesystem "sda8": XFS internal
error
> > xfs_da_do_buf(2) at line 2086 of file fs/xfs/
On Thu, Jun 07, 2007 at 09:44:51AM +0200, Marco Berizzi wrote:
> Hi David.
> Three months ago I wrote the message below.
> I had built various 2.6.20.x and 2.6.21.x
> vanilla kernel with all the debug options
> enabled and linux had never crashed.
> On june 4, I have builded linux 2.6.21.3 without
Hi David.
Three months ago I wrote the message below.
I had built various 2.6.20.x and 2.6.21.x
vanilla kernel with all the debug options
enabled and linux had never crashed.
On june 4, I have builded linux 2.6.21.3 without
any debugging options and after 2 days linux
has starting print these error
On Mon, Mar 19, 2007 at 11:32:27AM +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
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
On Fri, Mar 16, 2007 at 12:05:33PM +0100, Marco Berizzi wrote:
> David Chinner wrote:
>
> > can
> > you post a url to the commit?
>
> http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.19.y.git;a=commit;h=7fbbb01dca7704d52ace6f45a805c98a5b0362f9
Ok, so an ipsec change. And I see from the
ookup_int+0x98/0x10e
> xfs_lookup+0x5a/0x90
> xfs_vn_lookup+0x52/0x93
Curious - never seen this before - possibly a corrupted inode
number in the directory has led to this.
> ba 4e 8b cd
> Mar 12 14:35:21 Pleiadi kernel: Filesystem "sda8": XFS internal error
> xfs_da_do_buf
leiadi kernel: 0x0: e0 61 ed 62 b6 ff f3 a4 7b d6 0c 75
ba 4e 8b cd
Mar 12 14:35:21 Pleiadi kernel: Filesystem "sda8": XFS internal error
xfs_da_do_buf(2) at line 2087 of file fs/xfs/xfs_da_btree.c. Caller
0xc01b00bd
Mar 12 14:35:21 Pleiadi kernel: [] xfs_da_do_buf+0x70
18 matches
Mail list logo
