Hi Peter.
I've trying to move some of my servers to 2.4.4 kernel from
2.2.x. Everything goes fine, notable perfomance increase
occures, but the problem is I'm really often touch the following
problem:
__alloc_pages: 1-order allocation failed.
__alloc_pages: 1-order allocation
Hi Nick.
I have a zip disk which I attempted to mount using the following
fstab entry:
/dev/sda4 /zip vfat noauto,nodev,nosuid,user
===8=== CUT ===8===
The Zip is a bit suspect, as when I attempted to transfer stuff
from a Windows machine, it reported the size as a few Mb, and
Hi Tony.
sorry for the cold call - i've been trying to find a statement
about 'kernel governance' and how new code is accepted into the
kernel...
To help anybody else wondering about these issues, I've cc'd my reply
to the Linux-Kernel mailing list for comments. However, please note
that
Hi Nick.
Hi. I just compiled the 2.4.2 Linux Kernel on my machine and
ran into trouble with the linker. I had just installed the
latest build of binutils and apparently they changed the command
line flag from -oformat to --oformat, so the Makefile needed to
be edited in order to get
Hi all.
As a result of private email correspondance I have recently received, I
became aware that the current system of identifying the versions of the
various subsystems required to support any particular kernel version is
inadequate, and decided to do something about it. The enclosed patch is
Hi Andries.
[Yes, I wrote, replying to your mail, just because I happened to
notice the incorrect or debatable lines in your patch. Let me cc
the Changes maintainer - maybe Chris Ricker.]
-o util-linux 2.10o # fdformat --version
+o util-linux #
Hi Andries.
Neither am I - but, according to comments from RedHat a while back,
they repackage mount separately because they provide a NEWER version
of mount than is in the util-linux package. This will ALSO result in
`mount --version` giving the wrong answer...
There
Hi Andries.
{Shrug} Thinking isn't sufficient - check your facts.
Poor Riley,
Probably I should not answer, I think you know all the facts
already. But just to be sure:
(i) There are two different packages, kbd and a forked version,
console-tools. Both contain roughly the same
Hi Albert.
+o Mount # 2.10e# mount --version
Concerning mount: (i) the version mentioned is too old,
Exactly why? Mere missing features don't make for a required
upgrade. Version number inflation should be resisted.
These days you can mount several
Hi Albert.
The rule should be like this:
List the lowest version number required to get
2.2.xx-level features while running a 2.4.xx kernel.
That's a meaningless definition, and can only be taken as such. What
use would such a list be to somebody wishing (like I recently was)
Hi Horst.
Also, part of my plan was to check that the disk is
already in this non-standard format, and refuse to
dump if not. This would ensure that doing so didn't
overwrite somebody's master boot disk by accident, as
such disks will not normally be in this non-standard
format.
Hi Peter.
On Tue, 5 Dec 2000, H. Peter Anvin wrote:
Linus Torvalds wrote:
Actually, I bet I know what's up.
Want to bet $5 USD that suspend/resume saves the keyboard A20 state,
but does NOT save the fast-A20 gate information?
So anything that enables A20 with only the fast A20 gate will
Hi Alan.
I've just done a comparison of the configuration variables listed in
the config.in files against those listed in the Configure.help file.
I have enclosed the bash script I wrote to perform this analysis, and
would like to submit it for inclusion with the kernel as the file...
Hi Alan.
The enclosed patch deals with two problems relating to the Magic SysRq
function, as follows:
1. One of my pet peeves with SysRq as implemented is the apparently
random order theoptions as listed in the SysRq help list. This
patch sorts that list into case-insensitive
Hi Linus.
On Sun, 24 Dec 2000, Linus Torvalds wrote:
On Sun, 24 Dec 2000, Tim Wright wrote:
Which is all fine, but maybe the kernel really ought to detect
that problem and complain at boot time?
Or does that happen already?
There was a similar thread to this recently. The issue is that
Hi Alan.
This patch simply corrects a couple of comments in the said file to
reflect what the code actually does rather than (presumably) what the
code used to do at some time in the distant past.
In my case, I've been working on a patch for the kernel that uses
these facilities, and was
Hi Alan.
You may remember a while back a suggestion that panic messages be
dumped to floppy so they can be read afterwards.
I've been looking into this idea for a while, in between working on my
plans to get married, and looking for a job somewhere, and I think I
have the bones of it laid out
Hi Horst.
Before I go any further with this, I would like to ask a few
questions relating to it:
1. Is there any likelihood of this making it into the official
kernel, or am I just wasting my time?
Depends, I'd say... perhaps after a long shakeout and much use.
Fair enough - I'd
Hi there.
A friend of mine is having a problem with the 2.2.19 kernel on one of
his boxes, and has asked for some advice which is beyond my experience
so I'm asking here: Is this a kernel problem or something else?
First, the hardware, as best we can determine:
Vesa VLB motherboard,
Hi Ivan.
I like to build kernels with a bunch of patches on top to test
new stuff. The problem is that it takes a lot of effort to fix
all the failed hunks during patching that really wouldn't have
to be failed if only patch was a little more inteligent and
could merge several patches
Hi Russell, Adam.
So, I guess something like Keith Owens's patch would be the way
to go, with some additional definitions (CONFIG_AGP, CONFIG_PCI,
CONFIG_ISA, CONFIG_EISA, CONFIG_PCMCIA, and possibly others).
I am not sure which other conditionals might also be incorrectly
ignored by
Hi HPA.
Some time ago I installed Linux (Redhat 6.0) on my pc (Cx486 8M
RAM) and gcc had a lot of signal 11 (a couple every hour) I was
upgrading the kernel every time there was a new kernel and from
2.2.12(or 14) no more signal 11 (very rare) Is this still a
hardware problem ? Was a
Hi Peter.
Wasn't 2.2.12 the kernel that included the `lock halt` bug patch?
Perhaps, but is has absolutely nothing to do with the rest of
this discussion.
The `lock halt` bug patch was specific to the Cyrix processors (not to
be confused with the `lock registers` patch for the Intel
Hi Peter.
Wasn't 2.2.12 the kernel that included the `lock halt` bug patch?
Perhaps, but is has absolutely nothing to do with the rest of
this discussion.
The `lock halt` bug patch was specific to the Cyrix processors
(not to be confused with the `lock registers` patch for the
Hi Alan.
The enclosed patch was originally developed for the ELKS kernel, but
will apply equally well against any Linux kernel as it only adds new
scripts to the scripts subdirectory. The new scripts are as follows:
1. renvar Renames configuration variables in all files
Hi Alan.
Linux 2.2 is now firmly into maintainance state. Patches for
neat new ideas belong in 2.4. Generally new drivers belong in
2.4 (possibly in 2.2 as well after 2.4 shows them stable).
Expect me to be very picky on changes to the core code now.
Can I submit the attached patch for
that actually tells people what they need to know whilst you do so.
Best wishes from Riley.
*
On Fri, 23 Mar 2001, Albert D. Cahalan wrote:
Riley Williams writes:
Hi Albert.
The rule should be like this:
List the lowest
Hi David.
Perhaps even a boot flag of some sort to de-activate the
printing of the /proc/credits during the kernel boot sequence.
Or would the community rather an opt-in scenario...
KERN_BANNER
Where would you put that in the sequence?
Best wishes from Riley.
-
To unsubscribe from
Hi Alan.
What is the Right Way[tm] as of 2.4.6 to allocate 16Mb as 4K
pages and get the pci bus address for each page? Bonus points
is they're virtually contiguous, but that's not necessary.
IIRC, the old vmalloc-then-walk-the-pagetables trick is
considered out-of-bounds nowadays.
Hi Alan.
Brief critique...
Linux 2.4 BIOS usage reference
Boot Sequence
-
Linux is normally loaded either directly as a bootable floppy
image or from hard disk via a boot loader called lilo. The
kernel image is transferred into low memory and a parameter
block above
Hi Peter.
> I've trying to move some of my servers to 2.4.4 kernel from
> 2.2.x. Everything goes fine, notable perfomance increase
> occures, but the problem is I'm really often touch the following
> problem:
> __alloc_pages: 1-order allocation failed.
> __alloc_pages: 1-order allocation
Hi Nick.
> Hi. I just compiled the 2.4.2 Linux Kernel on my machine and
> ran into trouble with the linker. I had just installed the
> latest build of binutils and apparently they changed the command
> line flag from -oformat to --oformat, so the Makefile needed to
> be edited in order to
Hi all.
As a result of private email correspondance I have recently received, I
became aware that the current system of identifying the versions of the
various subsystems required to support any particular kernel version is
inadequate, and decided to do something about it. The enclosed patch is
Hi Andries.
>> -o util-linux 2.10o # fdformat --version
>> +o util-linux # 2.10o# fdformat --version
> Looking at fdformat to get the util-linux version is perhaps not
> the most reliable way - some people have fdformat from fd-utils
> or
Hi Andries.
> [Yes, I wrote, replying to your mail, just because I happened to
> notice the incorrect or debatable lines in your patch. Let me cc
> the Changes maintainer - maybe Chris Ricker.]
-o util-linux 2.10o # fdformat --version
+o util-linux
Hi Andries.
> Neither am I - but, according to comments from RedHat a while back,
> they repackage mount separately because they provide a NEWER version
> of mount than is in the util-linux package. This will ALSO result in
> `mount --version` giving the wrong answer...
>
Hi Andries.
>> {Shrug} Thinking isn't sufficient - check your facts.
> Poor Riley,
>
> Probably I should not answer, I think you know all the facts
> already. But just to be sure:
> (i) There are two different packages, kbd and a forked version,
> console-tools. Both contain roughly the
Hi Albert.
>> +o Mount # 2.10e# mount --version
> Concerning mount: (i) the version mentioned is too old,
>>> Exactly why? Mere missing features don't make for a required
>>> upgrade. Version number inflation should be resisted.
>> These days you can mount
Hi Albert.
>>> The rule should be like this:
>>>
>>>List the lowest version number required to get
>>>2.2.xx-level features while running a 2.4.xx kernel.
>> That's a meaningless definition, and can only be taken as such. What
>> use would such a list be to somebody wishing (like
Hi Nick.
> I have a zip disk which I attempted to mount using the following
> fstab entry:
> /dev/sda4 /zip vfat noauto,nodev,nosuid,user
===8<=== CUT ===>8===
> The Zip is a bit suspect, as when I attempted to transfer stuff
> from a Windows machine, it reported the size as a few
Hi Tony.
> sorry for the cold call - i've been trying to find a statement
> about 'kernel governance' and how new code is accepted into the
> kernel...
To help anybody else wondering about these issues, I've cc'd my reply
to the Linux-Kernel mailing list for comments. However, please note
Hi there.
A friend of mine is having a problem with the 2.2.19 kernel on one of
his boxes, and has asked for some advice which is beyond my experience
so I'm asking here: Is this a kernel problem or something else?
First, the hardware, as best we can determine:
Vesa VLB motherboard,
Hi Ivan.
> I like to build kernels with a bunch of patches on top to test
> new stuff. The problem is that it takes a lot of effort to fix
> all the failed hunks during patching that really wouldn't have
> to be failed if only patch was a little more inteligent and
> could merge several
Hi Ivan.
>>> I like to build kernels with a bunch of patches on top to test
>>> new stuff. The problem is that it takes a lot of effort to fix
>>> all the failed hunks during patching that really wouldn't have
>>> to be failed if only patch was a little more inteligent and
>>> could merge
Hi Russell, Adam.
>> So, I guess something like Keith Owens's patch would be the way
>> to go, with some additional definitions (CONFIG_AGP, CONFIG_PCI,
>> CONFIG_ISA, CONFIG_EISA, CONFIG_PCMCIA, and possibly others).
>> I am not sure which other conditionals might also be incorrectly
>>
Hi HPA.
>> Some time ago I installed Linux (Redhat 6.0) on my pc (Cx486 8M
>> RAM) and gcc had a lot of signal 11 (a couple every hour) I was
>> upgrading the kernel every time there was a new kernel and from
>> 2.2.12(or 14) no more signal 11 (very rare) Is this still a
>> hardware problem
Hi Peter.
>> Wasn't 2.2.12 the kernel that included the `lock halt` bug patch?
> Perhaps, but is has absolutely nothing to do with the rest of
> this discussion.
The `lock halt` bug patch was specific to the Cyrix processors (not to
be confused with the `lock registers` patch for the Intel
Hi Peter.
Wasn't 2.2.12 the kernel that included the `lock halt` bug patch?
>>> Perhaps, but is has absolutely nothing to do with the rest of
>>> this discussion.
>> The `lock halt` bug patch was specific to the Cyrix processors
>> (not to be confused with the `lock registers` patch
Hi Alan.
The enclosed patch was originally developed for the ELKS kernel, but
will apply equally well against any Linux kernel as it only adds new
scripts to the scripts subdirectory. The new scripts are as follows:
1. renvar Renames configuration variables in all files
Hi Alan.
> Linux 2.2 is now firmly into maintainance state. Patches for
> neat new ideas belong in 2.4. Generally new drivers belong in
> 2.4 (possibly in 2.2 as well after 2.4 shows them stable).
> Expect me to be very picky on changes to the core code now.
Can I submit the attached patch
Hi David.
>> Perhaps even a boot flag of some sort to de-activate the
>> printing of the /proc/credits during the kernel boot sequence.
>> Or would the community rather an opt-in scenario...
> KERN_BANNER
Where would you put that in the sequence?
Best wishes from Riley.
-
To
Hi Alan.
>> What is the Right Way[tm] as of 2.4.6 to allocate 16Mb as 4K
>> pages and get the pci bus address for each page? Bonus points
>> is they're virtually contiguous, but that's not necessary.
>> IIRC, the old vmalloc-then-walk-the-pagetables trick is
>> considered out-of-bounds
Hi Alan.
Brief critique...
> Linux 2.4 BIOS usage reference
> Boot Sequence
> -
>
> Linux is normally loaded either directly as a bootable floppy
> image or from hard disk via a boot loader called lilo. The
> kernel image is transferred into low memory and a parameter
>
Hi Horst.
>>> Also, part of my plan was to check that the disk is
>>> already in this non-standard format, and refuse to
>>> dump if not. This would ensure that doing so didn't
>>> overwrite somebody's master boot disk by accident, as
>>> such disks will not normally be in this non-standard
Hi Peter.
On Tue, 5 Dec 2000, H. Peter Anvin wrote:
> Linus Torvalds wrote:
>> Actually, I bet I know what's up.
>>
>> Want to bet $5 USD that suspend/resume saves the keyboard A20 state,
>> but does NOT save the fast-A20 gate information?
>>
>> So anything that enables A20 with only the fast
Hi Alan.
I've just done a comparison of the configuration variables listed in
the config.in files against those listed in the Configure.help file.
I have enclosed the bash script I wrote to perform this analysis, and
would like to submit it for inclusion with the kernel as the file...
Hi Alan.
The enclosed patch deals with two problems relating to the Magic SysRq
function, as follows:
1. One of my pet peeves with SysRq as implemented is the apparently
random order theoptions as listed in the SysRq help list. This
patch sorts that list into case-insensitive
Hi Linus.
On Sun, 24 Dec 2000, Linus Torvalds wrote:
> On Sun, 24 Dec 2000, Tim Wright wrote:
>>> Which is all fine, but maybe the kernel really ought to detect
>>> that problem and complain at boot time?
>>>
>>> Or does that happen already?
>> There was a similar thread to this recently.
Hi Alan.
This patch simply corrects a couple of comments in the said file to
reflect what the code actually does rather than (presumably) what the
code used to do at some time in the distant past.
In my case, I've been working on a patch for the kernel that uses
these facilities, and was
Hi Alan.
You may remember a while back a suggestion that panic messages be
dumped to floppy so they can be read afterwards.
I've been looking into this idea for a while, in between working on my
plans to get married, and looking for a job somewhere, and I think I
have the bones of it laid out
Hi Horst.
>> Before I go any further with this, I would like to ask a few
>> questions relating to it:
>> 1. Is there any likelihood of this making it into the official
>>kernel, or am I just wasting my time?
> Depends, I'd say... perhaps after a long shakeout and much use.
Fair
that actually tells people what they need to know whilst you do so.
Best wishes from Riley.
*
On Fri, 23 Mar 2001, Albert D. Cahalan wrote:
> Riley Williams writes:
> > Hi Albert.
>
> >>>&
62 matches
Mail list logo
