Funny,
I also got 32bits kernels running, and moving to 64bits because that's
more stable what we tested here...
Greetings,
Jim.
> Hi Jim,
>
> On 2008-02-05 13:06:34 +0100, Jim van Wel wrote:
>
>> http://lkml.org/lkml/2007/11/6/44
>
> Oops, I didn't expect the problem t
Hi there,
Welcome to the club,
http://lkml.org/lkml/2007/11/6/44
Got same issue, but somewhat different hardware. I'm really wondering, are
you using a 64bits kernel or a 32bit?
Greetings,
Jim.
> Hi,
>
> I'm currently experiencing strange OOM errors on a machine with 8 GB
RAM, 16 GB swap
Hi there,
Welcome to the club,
http://lkml.org/lkml/2007/11/6/44
Got same issue, but somewhat different hardware. I'm really wondering, are
you using a 64bits kernel or a 32bit?
Greetings,
Jim.
Hi,
I'm currently experiencing strange OOM errors on a machine with 8 GB
RAM, 16 GB swap (Xeon
Funny,
I also got 32bits kernels running, and moving to 64bits because that's
more stable what we tested here...
Greetings,
Jim.
Hi Jim,
On 2008-02-05 13:06:34 +0100, Jim van Wel wrote:
http://lkml.org/lkml/2007/11/6/44
Oops, I didn't expect the problem to be 3 months old. Next time
Hi there,
I have a strange problem with like 10-15 servers right now.
We have here all HP DL380-G5 servers with kernel 2.6.22.6. System all
works normall. But after a uptime of like 15 a 25 days, we get these
messages, and the servers is just crashed.
[1791648.015312] exim4 invoked oom-killer:
Hi there,
I have a strange problem with like 10-15 servers right now.
We have here all HP DL380-G5 servers with kernel 2.6.22.6. System all
works normall. But after a uptime of like 15 a 25 days, we get these
messages, and the servers is just crashed.
[1791648.015312] exim4 invoked oom-killer:
Hi there,
To be honest, I am really are great full that you have posted this hear. I
have read the article and it's really interesting to read. Especially this
part:
So I take the hint, and that night, in my office, I start scouring the
80,496 lines of the Reiser4 source code. Eventually I
Hi there,
To be honest, I am really are great full that you have posted this hear. I
have read the article and it's really interesting to read. Especially this
part:
So I take the hint, and that night, in my office, I start scouring the
80,496 lines of the Reiser4 source code. Eventually I
Hi there,
Please try first a newer kernel of FC6.
2.6.19-1.2911.6.5.fc6
That's 2.6.19.7.
That's the newest one.
Greetings,
Jim,
> Hi,
>
> I just bought a brand new notebook and wanted to install FC6 on it.
Unfornately there are some issues reported by the console during boot.
Here are some
Hi there,
Please try first a newer kernel of FC6.
2.6.19-1.2911.6.5.fc6
That's 2.6.19.7.
That's the newest one.
Greetings,
Jim,
Hi,
I just bought a brand new notebook and wanted to install FC6 on it.
Unfornately there are some issues reported by the console during boot.
Here are some
Hi all,
As promised, I should notify if no problems would happen. Well, no
problems happened. So when I was running kernel version 2.6.19 the
problems of my previous e-mails did happen, with kernel 2.6.18.1 running
right now, just none of the errors are comming up, and is running
smoothly.
Hi all,
As promised, I should notify if no problems would happen. Well, no
problems happened. So when I was running kernel version 2.6.19 the
problems of my previous e-mails did happen, with kernel 2.6.18.1 running
right now, just none of the errors are comming up, and is running
smoothly.
Hi,
Well, I filled in the survey. Was wondering if you also post the results
here at the mailing list. That would be nice.
Greetings,
Jim.
> Hi all,
>
> We would like to ask you few question about Linux Kernel Community. The
> survey consists of 31 multiple choice questions and three text
Hi,
Well, I filled in the survey. Was wondering if you also post the results
here at the mailing list. That would be nice.
Greetings,
Jim.
Hi all,
We would like to ask you few question about Linux Kernel Community. The
survey consists of 31 multiple choice questions and three text boxes.
Hi there,
Well, after I was getting the error again, I now switched back to kernel
2.6.18.1, and going to check if I am getting the same errors. I'll keep
you posted about the progress. If a week have passed and no errors has
shown, I'll e-mail this again.
Thanks!
Jim.
> Hi,
>
>> Well, that's
Hi there,
Well, after I was getting the error again, I now switched back to kernel
2.6.18.1, and going to check if I am getting the same errors. I'll keep
you posted about the progress. If a week have passed and no errors has
shown, I'll e-mail this again.
Thanks!
Jim.
Hi,
Well, that's
Hi,
> Oh, so the machine does not crash or go totally out of memory when this
> happens? At least it seems the filesystem is remounted RO?
Well, that's the most funny thing. It doesn't remount RO, it's still
mounted as RW.
Like here:
/dev/md1 on / type ext3 (rw)
none on /proc type proc (rw)
Hi there,
Well, that's kind of difficult because it looks a little random when he
does it, and a interval of three days, but also is maybe random.
And the most difficult part is it's only for three seconds, and than it's
gone, so making a crontab script every minute might not even notice it?
Or
13313570451 : tunables 54 278
: slabdata 27 27 0
Greetings,
Jim van Wel.
> Hi,
>
>> I have something really strange while running kernel 2.6.19.
>>
>> See the following lines:
>>
>> Dec 5 23:50:49 kernel: do_get_write_acc
Hi all,
I have something really strange while running kernel 2.6.19.
See the following lines:
Dec 5 23:50:49 kernel: do_get_write_access: OOM for frozen_buffer
Dec 5 23:50:49 kernel: ext3_free_blocks_sb: aborting transaction: Out of
memory in __ext3_journal_get_undo_access
Dec 5 23:50:49
Hi all,
I have something really strange while running kernel 2.6.19.
See the following lines:
Dec 5 23:50:49 kernel: do_get_write_access: OOM for frozen_buffer
Dec 5 23:50:49 kernel: ext3_free_blocks_sb: aborting transaction: Out of
memory in __ext3_journal_get_undo_access
Dec 5 23:50:49
14943 15222 64 591 : tunables 120 608
: slabdata258258 0
kmem_cache 13313570451 : tunables 54 278
: slabdata 27 27 0
Greetings,
Jim van Wel.
Hi,
I have something really strange while running kernel 2.6.19.
See
Hi there,
Well, that's kind of difficult because it looks a little random when he
does it, and a interval of three days, but also is maybe random.
And the most difficult part is it's only for three seconds, and than it's
gone, so making a crontab script every minute might not even notice it?
Or
Hi,
Oh, so the machine does not crash or go totally out of memory when this
happens? At least it seems the filesystem is remounted RO?
Well, that's the most funny thing. It doesn't remount RO, it's still
mounted as RW.
Like here:
/dev/md1 on / type ext3 (rw)
none on /proc type proc (rw)
24 matches
Mail list logo
