Interesting. They should be the same code for the VIA driver.
I remember hearing something about Red Hat disabling UDMA on VIA chips
across the board. Maybe that has something to do with it?
The RH 7.1 kernel disables VIA UDMA if the board has a DMI string indiciating
its a KT7 or
Gerhard Mack wrote:
On Thu, 28 Jun 2001, Jeff Garzik wrote:
Linus Torvalds wrote:
Things like version strings etc sound useful, but the fact is that the
only _real_ problem it has ever solved for anybody is when somebody thinks
they install a new kernel, and forgets to run lilo or
On Thu, 28 Jun 2001, Jeff Garzik wrote:
Linus Torvalds wrote:
Things like version strings etc sound useful, but the fact is that the
only _real_ problem it has ever solved for anybody is when somebody thinks
they install a new kernel, and forgets to run lilo or something. But
even that
On Thu, 28 Jun 2001, Jeff Garzik wrote:
As Alan said, driver versions are incredibly useful. People use update
their drivers over top of kernel drivers all the time. Vendors do it
too. Run dmesg and e-mail me the output is 1000 times more simple for
end users.
Fair enough. Especially as
Linus Torvalds wrote:
Especially as dmesg will output even the debugging messages
that do not actually end up being printed on the screen unless explicitly
asked for.
Nifty, I did not know that. Makes all kinds of sense, though. Silly
me...
I'd also like to acknowledge the fact that at
Intel specifically state that you cannot use CMOV without checking
for it. Its actually a gcc/binutils tool bug. The CPU is right.
How is that a gcc bug? You tell the compiler to generate cmov, you run
it on a CPU that doesn't have it, you get what you deserve. There's
really nothing
i've compiled the kernel 2.4.4 , once i finish and boot the first time on
2.4.4 everything goses ok ,
only too problemes
1st- klogd takes 100% CPU time
Old old versions of klogd had bugs where they would do that. If there is
a continuous problem it may also do so - does 'dmesg' show
1 After a 'shutdown -h now', I get a kernel bug at page_alloc.c:81
2 After being in X (only happens after being in X), I get out of X, and as root
I do a 'shutdown -h now'. It goes through the shutdown process normally, and then
after it prints Syncing hardware clock to system time [
On Thu, 28 Jun 2001 20:42:09 +0100 (BST), Alan Cox wrote:
Intel specifically state that you cannot use CMOV without checking
for it. Its actually a gcc/binutils tool bug. The CPU is right.
How is that a gcc bug? You tell the compiler to generate cmov, you run
it on a CPU that doesn't
Here I have to disagree with you Alan. When you pass -march=i686 to
gcc, you are _not_ saying generate code for a CPUID family 6 CPU.
-march=i686 actually means target an Intel P6 family chip, given
what we currently know about them. The gcc info pages don't talk
Which is fine. The Pentium
4002b000-4002c000 rw-s ec681000 03:01 181386 /dev/mem
4002c000-4002d000 rw-s 4000 03:01 185562 /dev/nvidia0
I'd suggest you talk to your proprietary driver and application provider. Who
knows what their driver does
-
To unsubscribe from this list: send the line unsubscribe
On Wed, Jun 27, 2001 at 05:27:11PM +0100, Alan Cox wrote:
I'm fairly sure it is the file buffers as the apache is already
reniced to 20, it is got max 50 processes and each of processes is
limited to like 1.5mb of size via ulimit.
nice wont help you, it controls scheduling
Hello...
Am Donnerstag, 28. Juni 2001 00:16 schrieb Linus Torvalds:
I don't _have_ any instances of my name being printed out to annoy the
user, so that's a very theoretical argument.
Err Just nitpicking...
dreker@wintermute:~ dmesg | grep -C Linus
hub.c: 2 ports detected
uhci.c: Linus
http://www.viahardware.com/686bfaq.shtm
Couldn't find a mention of this in the archives, but those interested in
the VIA chipset issues should check this out. The page contains the
following officail statement from VIA:
Yeah I've seen it, but they won't tell people what is in it which is
Can we please also drop annoying static informational printk's?
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
The later line is not something of interest to most people, and if it
happens to be they can research it rather than being force-fed
Updatedb is a bit odd in that it mostly sucks in metadata and the buffer to
page cache balancing is a bit suspect IMHO.
In 2.4.6-pre, the buffer cache is no longer used for metata, right?
For ext2 directory blocks the page cache is now used
-
To unsubscribe from this list: send the line
Now the system runs fine for about 1 Week. After than, it oftens crashes.
crashes is not realy the thing ... diffrent things happen :
Unfortunately you dont give enough information to even take a wild guess
The system is running on 2.4.4-ac18
Do try ac13 as well, there are some glitches in
On Thu, 28 Jun 2001, Alan Cox wrote:
This would be extremely useful. My laptop has 256mb of ram, but every day
it runs the updatedb for locate. This fills the memory with the file
cache. Interactivity is then terrible, and swap is unnecessarily used. On
the laptop all this hard drive
[EMAIL PROTECTED] said:
PCI memory (and sometimes I/O) writes are posted, Since x86 memory
writes are also parallelisable instructions and since the CPU merely
has to retire the writes in order your stall basically doesnt exist.
True. I can envisage a situation where the overhead of the
On Thu, 28 Jun 2001, Alan Cox wrote:
That isnt really down to labelling pages, what you are talking qbout is what
you get for free when page aging works right (eg 2.0.39) but don't get in
2.2 - and don't yet (although its coming) quite get right in 2.4.6pre.
Correct, but all pages
That isnt really down to labelling pages, what you are talking qbout is what
you get for free when page aging works right (eg 2.0.39) but don't get in
2.2 - and don't yet (although its coming) quite get right in 2.4.6pre.
Correct, but all pages are not equal.
That is the whole point of
This would be extremely useful. My laptop has 256mb of ram, but every day
it runs the updatedb for locate. This fills the memory with the file
cache. Interactivity is then terrible, and swap is unnecessarily used. On
the laptop all this hard drive thrashing is bad news for battery life
On Thursday 28 June 2001 09:33, Alan Cox wrote:
With CONFIG_SOUND_FUSION=m, I get the following error for 2.4.6-pre6
during make modules:
I've got a number of older 2.4.[3,4,5] kernels, so I'll go back and try
to figure out when the change occured, but this is the first time I've
seen
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...
Leave the copyright messages alone is all I can say. And as to your flag,
well we've got one. Try the 'quiet' boot option
On Thu, 28 Jun 2001, Patrick Dreker wrote:
Am Donnerstag, 28. Juni 2001 00:16 schrieb Linus Torvalds:
I don't _have_ any instances of my name being printed out to annoy the
user, so that's a very theoretical argument.
Err Just nitpicking...
dreker@wintermute:~ dmesg | grep -C Linus
On Thu, 28 Jun 2001, Alan Cox wrote:
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...
Leave the copyright messages alone is all I can say. And as to your flag,
Alan Cox wrote:
This is the initial merge with 2.4.6pre - treat this one with care, it may
not be the most reliable 2.4.5ac release ever made
make[3]: Entering directory `/usr/src/linux-2.4.5-ac/drivers/pnp'
gcc -D__KERNEL__ -I/usr/src/linux-2.4.5-ac/include -Wall -Wstrict-prototypes
[EMAIL PROTECTED] said:
Things like version strings etc sound useful, but the fact is that the
only _real_ problem it has ever solved for anybody is when somebody
thinks they install a new kernel, and forgets to run lilo or
something.
I can give counter-examples of times when it's been
Things like version strings etc sound useful, but the fact is that the
only _real_ problem it has ever solved for anybody is when somebody thinks
they install a new kernel, and forgets to run lilo or something. But
even that information you really get from a simple uname -a.
For device
As to the credit argument: put your copyright at the top of the source
file. The people who care and matter will see it. And do NOT hide the
copyright with reams of changelog information. Put that in a separate file
if you must.
Managers at places like Cisco see boot messages and it gets
Also consider the question What was the last thing you see on screen
before it reboots?
You need that info in case it doesn't. Its much like the watchdog tells you
it fired in case someone didn't wire it right. So in a sense its an error
message
-
To unsubscribe from this list: send the line
On Thu, 28 Jun 2001, Alan Cox wrote:
As to the credit argument: put your copyright at the top of the source
file. The people who care and matter will see it. And do NOT hide the
copyright with reams of changelog information. Put that in a separate file
if you must.
Managers at places
David == David Woodhouse [EMAIL PROTECTED] writes:
David Having per-resource I/O methods would help us to remove some of
David the cruft which is accumulating in various non-x86 code. Note
David that the below is the _core_ routines for _one_ board - I'm not
David even including the extra
I got this familiar error with make xconfig and 2.4.5-ac20 (same as 2.4.6-pre6)
drivers/net/Config.in: 149: can't handle dep_bool/dep_mbool/dep_tristate condition
make[1]: *** [kconfig.tk] Error 1
make[1]: Leaving directory `/usr/src/linux-2.4.5-ac20/scripts'
make: *** [xconfig] Error 2
I
admit that UNIX has a crappy event model, and implement something like Win32
GetMessage =)...
Thats a subset of the real time signal model already in Linux. Just block the
signal and wait for it..
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message
This is the initial merge with 2.4.6pre - treat this one with care, it may
not be the most reliable 2.4.5ac release ever made
Yeah I borked that. The good news is it'll be fixed in ac21 _and_ that
it'll do hotplug notification for dock/undock ;)
-
To unsubscribe from this list: send the
On Thu, Jun 28, 2001 at 10:29:11AM -0700, [EMAIL PROTECTED] wrote:
Taking that one step further, isn't it a developer's right to toot their
own horn in their code?
Right. In the code. Not in the Linux boot diagnostic information.
-
To unsubscribe from this list: send the line unsubscribe
With CONFIG_SOUND_FUSION=m, I get the following error for 2.4.6-pre6 during
make modules:
I've got a number of older 2.4.[3,4,5] kernels, so I'll go back and try to
figure out when the change occured, but this is the first time I've seen
this particular build error.
I've fixed the build
Hi,
The cciss driver in 2.4.5-ac19 is missing the terminating {0,}.
Ciao, Marcus
Index: drivers/block/cciss.c
===
RCS file: /build/mm/work/repository/linux-mm/drivers/block/cciss.c,v
retrieving revision 1.23
diff -u -r1.23 cciss.c
[EMAIL PROTECTED] said:
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
--
dwmw2
-
To unsubscribe from this list: send the line unsubscribe
401 - 440 of 440 matches
Mail list logo
