Aaron Sethman <[EMAIL PROTECTED]> writes:
> You might want to take a look at using reiserfs on the 130GB partition, as
> its is journalled and doesn't need to be fsck'ed.
No.
All journaling filesystems need to be fsck'ed.
A correctly operating one simply doesn't need to be fsck'ed because
of
"Stephen Gutknecht (linux-kernel)" <[EMAIL PROTECTED]> writes:
> A Linux Kernel compile test does a really good job of testing the hard disk,
> RAM, and CPU... as it executes all types of instructions and the final
> output depends on all prior steps completing correctly. On a really fast
>
[first off, thanks for kicking this stuff into gear Adam. I'm way too
lazy to do this stuff of my own volition :)]
> >was to serialize access to the mixer, there are surely better ways to do
> >it. Why are interrupts disabled?
the maestro has crappy register indirection that you must use to
> Unrelated to your change: the maestro reboot notifier shouldn't need to
> unregister all that stuff. Who cares if the sound devices are freed,
> since we are rebooting. free_irq+maestro_power seems sufficient. or
> maybe stop_dma+free_irq+poweroff.
its only the power stuff that matters.
Keith Owens wrote:
>
> On Tue, 21 Nov 2000 20:17:47 -0700,
> "Jeff V. Merkey" <[EMAIL PROTECTED]> wrote:
> >Was there a reason we removed the -i and -m options from newer modutils
> >and broke backwards caompatibility? I'm re-writing our module build
> >scripts for the installer, and I
Hi all,
How do i lock user mode memmory pages from kernel mode driver.. so that i
can access it whenever i need to from the driver I am using linux kernel
2.2.14.. can this be done in this kernel version... or is it supported in
some other newer versions.. like 2.4..
TIA
azad
-
To
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
Please reply to me directly, since I am not getting messages from
the list. Perhaps something is wedged with my ISP.
Miles
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at
On Tue, Nov 21, 2000 at 10:26:24PM -0500, Joseph Gooch wrote:
> My RaptorNT 6.5 firewall rejects all connections from my linux box when ECN
> is enabled. The error is attached. Perhaps this feature should be disabled
> by default? Or is there already an option of the sort that i'm missing? I
On Tue, 21 Nov 2000 20:17:47 -0700,
"Jeff V. Merkey" <[EMAIL PROTECTED]> wrote:
>Was there a reason we removed the -i and -m options from newer modutils
>and broke backwards caompatibility? I'm re-writing our module build
>scripts for the installer, and I discovered after upgrading to 2.3.20,
On Tue, Nov 21, 2000 at 06:17:48PM -0500, David Riley wrote:
> Richard Torkar wrote:
> >
> > Well David, there is such a "manual".
> >
> > http://ftp.sunet.se/LDP/FAQ/faqs/GCC-SIG11-FAQ
>
> Yes. And if you ask the average new Linux user if they've read it, I
> doubt you'll get a "yes". My
My RaptorNT 6.5 firewall rejects all connections from my linux box when ECN
is enabled. The error is attached. Perhaps this feature should be disabled
by default? Or is there already an option of the sort that i'm missing? I
only got the idea to disable it after a search of linux-kernel.
Plz
Keith,
Was there a reason we removed the -i and -m options from newer modutils
and broke backwards caompatibility? I'm re-writing our module build
scripts for the installer, and I discovered after upgrading to 2.3.20,
that all the build scripts (about 10MB worth) are now busted and I have
been
JE's UHCI driver (drivers/usb/uhci.[hc]) uses
nested_lock() and nested_unlock() for this.
Maybe it could help.
~Randy
___
|randy.dunlap_at_intel.com503-677-5408|
|NOTE: Any views presented here are mine alone|
|& may not represent the views of
I forgot to mention that I have tested the updated maestro.c
patch that I just submitted by loading the module on a
notebook computer, playing some sound, and unloading it.
Adam J. Richter __ __ 4880 Stevens Creek Blvd, Suite 104
[EMAIL PROTECTED] \ /
Jeff Garzik critiqued my patch for linux-2.4.0-test11/drivers/sound/maestro.c:
>[...] if the intention
>was to serialize access to the mixer, there are surely better ways to do
>it. Why are interrupts disabled?
As far as I can tell, I agree with you, but I do not think
that is related
[Alan Cox]
> You got it. The module is doing an overlarge delay
Perhaps people would stop asking this question if the symbol were
renamed from __bad_udelay() to, say, __use_mdelay_instead_please().
Sort of like the DNS zone (somewhere at UCLA was it?) where they had
something like 'quit 86400
On Tue, Nov 21, 2000 at 10:44:30PM -0300, Horst von Brand wrote:
>
> If you have a laptop with an assortment of cards, you might want to have
> the generic builtin and the cards themselves as modules.
No, that's ok, and that's supported with the current config scripts.
The original question
David Hinds <[EMAIL PROTECTED]> said:
[...]
> Is there a technical reason for this? Not that I know of; but then I
> also cannot think of a good reason for wanting, say, the generic code
> built in but the controller support as modules. I do see reasonable
> arguments for all-builtin or
SMP Dual celeron, 128MB ram, 3.6GB part newly created, untar'ing 1GB
newsspool, gave kreiserfsd priority -19, got not very easily reproducible
lockup.
Sysreq showd kreiserfsd running in state L-TLB or something.
elmer.
-
To unsubscribe from this list: send the line "unsubscribe
A few days ago, and again half an hour ago, X stopped working.
Both times this happened in a period of heavy and continuous
IDE disk access (copying a 12 GB tree from one disk to another,
and doing a diff between two 5 GB trees on different disks).
No mouse movement, no reaction to
On Tue, Nov 21, 2000 at 08:10:38PM -0500, Albert D. Cahalan wrote:
>
> Hmmm, I'm not the only one who doesn't like modules depending
> on other modules. I suppose this is part paranoia about extra
> complexity leading to problems, and part desire to avoid the
> module overhead for common code
On Tue, 21 Nov 2000, Jeff Garzik wrote:
>
> A caveat to this whole scheme is that usb-uhci -already- calls
> pci_enable_device before checking dev->irq, and yet cannot get around
> the "assign IRQ to USB: no" setting in BIOS. I hope that is an
> exception rather than the rule.
Do we have a
Alan Cox wrote:
>
>> I tried to compile 2.4.0-test11-ac1, and here is where the compile bombed
out:
>>
>> /usr/bin/kgcc -D__KERNEL__ -I/usr/src/linux/include -Wall
-Wstrict-prototypes
>> -O2 -fomit-frame-pointer -fno-strict-aliasing -pipe -march=i686-c -o
>> sched.o sched.c
>>
Oh well mistakes in Config are okay and not fatal.
Thanks for the find Bart.
Cheers,
On Tue, 21 Nov 2000, Bartlomiej Zolnierkiewicz wrote:
>
> Hi
>
> In drivers/Config.in CONFIG_BLK_DEV_OSB4 depends on itself...
>
> --
> Bartlomiej Zolnierkiewicz
> <[EMAIL PROTECTED]>
>
> ---
[I wrote]
> > > void foo (void)
> > > {
> > > if (0)
> > > printk(KERN_INFO "bar");
> > > }
> > >
[J . A . Magallon]
> Is it related to opt level ? -O3 does auto-inlining and -O2 does not
> (discovered that here, auto inlining in kernel trashes the cache...)
See for
On Tue, 21 Nov 2000, David Woodhouse wrote:
> On Tue, 21 Nov 2000, Andre Hedrick wrote:
>
> > No, if it doesn not hang and we get iCRC errors it will down grade
> > automatically, but it is a transfer rate issue than it must be hard coded
> > to force an upper threshold limit.
>
> Do we
On Tue, Nov 21, 2000 at 08:14:51AM +0300, Eugene Crosser wrote:
> zero entries on the mounted CD, and each "ls" attempt causes this
> kernel message:
>
> _isofs_bmap: block < 0
Same here, except that once showed
_isofs_bmap: block >= EOF (1633681408, 4096)
--
/| Ragnar Højland
>> The subject says it all. Is there any particular (technical) reason
>> why I must have both the generic pcmcia code and the controller
>> support built-in, or build all of them as modules?
>
> Is there a technical reason for this? Not that I know of; but then I
> also cannot think of a good
I was playing around with Kurt Garloff's rescan-scsi-bus.sh, more
precisely, I moved an entire bus from my Tekram DC-390U (with sym53c8xx
driver) to my Tekram DC-390 (with tmscsim driver). Then, I ran that
script which effectively sends a lot of stuff to /proc/scsi/scsi (scsi
add-single-device).
William K. Josephson <[EMAIL PROTECTED]>
wrote on Sun, 8 Oct 2000:
> While writing some user-space code recently, I ran across two bugs
> in the Rock Ridge support code. First, a bogus return value and
> second links on the cd of the form foo->/bar are returned
> as foo->//bar. This should fix
Followup to: <[EMAIL PROTECTED]>
By author:Alan Cox <[EMAIL PROTECTED]>
In newsgroup: linux.dev.kernel
> >
> > Nononono... the 82489DX is an *external* APIC, which should be usable
> > on any Socket 5/7 CPU...
>
> I know of no socket 7 board with an 82489DX, and no board on the planet
Hi all,
Running a 2.4.0-text 10 + XFS + CONFIG_HIGHMEM4GB kernel on a
2p ia32 SMP box with 1Gb of memory, our XFS QA locks up the kernel
fairly repeatably.
It takes quite a while to happen and doesn't appear to be related
to XFS. It also only happens when CONFIG_HIGHMEM4GB is enabled,
which
Alan Cox wrote:
>
> > It's as though the disk drivers are optimized for this case (1024). I
>
> The disk drivers are not, and they normally see merged runs of blocks so they
> will see big chunks rather than 1K then 1K then 1K etc.
>
> > behavior, but there is clearly some optimization
On Tue, Nov 21, 2000 at 05:06:20PM -0700, Jeff V. Merkey wrote:
>
>
> Alan Cox wrote:
> >
> > > Sirs,
> > > performing extensive tests on linux platform performance, optimized as
> > > database server, I got IMHO confusing results:
> > > in particular e2fs initialized to use 1024
"Stephen Gutknecht (linux-kernel)" wrote:
> Part of the issue is that there exists no "easy to use" standardized test
> software. Full 32-bit concurrent use of many devices can reveal problems
> that users do not often see in normal applications.
>
> One major hardware review site found
> > Intel stuff appears to always be happy poking in APIC space. I don't know
> > if this is related to the chip internals on the non APIC capable chips.
>
> Nononono... the 82489DX is an *external* APIC, which should be usable
> on any Socket 5/7 CPU...
I know of no socket 7 board with an
> It's as though the disk drivers are optimized for this case (1024). I
The disk drivers are not, and they normally see merged runs of blocks so they
will see big chunks rather than 1K then 1K then 1K etc.
> behavior, but there is clearly some optimization relative to this size
> inherent in
I guess we can soon expect patch from Linus adding LINUX_REBOOT_MAGIC2C
to Linux kernel.
--
Adam
http://www.eax.com The Supreme Headquarters of the 32 bit registers
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Alan Cox wrote:
>
> > Sirs,
> > performing extensive tests on linux platform performance, optimized as
> > database server, I got IMHO confusing results:
> > in particular e2fs initialized to use 1024 block/fragment size showed
> > significant I/O gains over 4096 block/fragment size, while I
"J . A . Magallon" wrote:
> On Tue, 21 Nov 2000 22:25:01 Bartlomiej Zolnierkiewicz wrote:
> > -static int dataPort = 0; /* port for register data */
> > +static int dataPort; /* port for register data */
>
> That is not too much confidence on the ANSI-ness of the compiler ???
There is
Followup to: <[EMAIL PROTECTED]>
By author:Alan Cox <[EMAIL PROTECTED]>
In newsgroup: linux.dev.kernel
>
> > > making any assumptions about APIC availability on a processor.
> >
> > OK, but how does it handle the 82489DX? There are valid configurations
> > using this kind of APIC,
On Tue, Nov 21, 2000 at 11:34:45PM +0100, Tobias Ringstrom wrote:
> The subject says it all. Is there any particular (technical) reason why I
> must have both the generic pcmcia code and the controller support
> built-in, or build all of them as modules?
Is there a technical reason for this?
Alan,
I have an Oops with 2.2.18-22 that only shows up on a Linux server
that's configured as a pppd dial in server with dynamic address
assignment (no DHCP). Host IP addresses are configured in an
options.ttyS0(192.168.0.1) and options.ttyS1(192.168.0.2) files in
/etc/ppp.
We caused the
> module that is pulling the definition of udelay() from asm/delay.h, it's
> referencing __bad_udelay(). However, I can't seem to find the __bad_udelay()
> function actually defined anyplace. (Although it could be somewhere in the
> kernel source that my grep missed.)
Its intentionally missing
Hello,
Possibly an issue with an external module that I'm using, but when I compile a
module that is pulling the definition of udelay() from asm/delay.h, it's
referencing __bad_udelay(). However, I can't seem to find the __bad_udelay()
function actually defined anyplace. (Although it could be
Umm what worked for me was to do the following :
change the following line in os-interface.c (Part of NVIDIA_kernel package):
symbol_value = get_module_symbol(NV_MODULE_NAME, symbol_name);
to :
symbol_value = inter_module_get_request(NV_MODULE_NAME, symbol_name);
and then remove the
> 53c400a non-PNP still lock this system hard. It starts barking about a
> busy SCSI bus, and then I can fsck again.
>
> To Alan : How hard is it to get thing beast (53c400 and family) to be SMP
> safe ?? Or is it better to start over again ?
The problem is that the code takes spinlocks
On Mon, Nov 20, 2000 at 03:03:03AM +0100, Malte Cornils wrote:
> my Dawicontrol 2974 SCSI-adapter fails with kernel 2.4.0-test10
> with pre-11 and reiserfs for kernel test-10 patched in:
>
> --
> Nov 20 01:30:23 wh36-b407 kernel: scsi : aborting command due to timeout : pid 0,
>scsi0, channel
"Adam J. Richter" wrote:
>
> Here is a patch which ports drivers/sound/maestro.c to the new PCI
> interface, which Zach Brown asked me to post here for comments.
> This patch includes Zach's changes eliminating the ioctl lockups which
> he posted separately, just to make it easier to generate
> Sirs,
> performing extensive tests on linux platform performance, optimized as
> database server, I got IMHO confusing results:
> in particular e2fs initialized to use 1024 block/fragment size showed
> significant I/O gains over 4096 block/fragment size, while I expected t=
> he
> opposite. I
> > MP table regardless of the capabilities of the CPU installed. Its apparently
> > legal to do so. There is an apic capability flag that should be tested before
> It's not legal -- the MPS is very explicit the MP-table must reflect a
> real configuration.
Intel tell me otherwise. The real
On Wed, 22 Nov 2000 00:26:23 Tigran Aivazian wrote:
> On Wed, 22 Nov 2000, J . A . Magallon wrote:
>
> In the case of kernel, we have to do many things manually, can't rely on
> some compiler (sometimes :). So, the code I pointed you at
> arch/i386/kernel/head.S (look for "Clear BSS") is in
> I tried to compile 2.4.0-test11-ac1, and here is where the compile bombed out:
>
> /usr/bin/kgcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes
> -O2 -fomit-frame-pointer -fno-strict-aliasing -pipe -march=i686-c -o
> sched.o sched.c
> irq.c:182: conflicting types for
On Wed, 22 Nov 2000, J . A . Magallon wrote:
>
> On Wed, 22 Nov 2000 00:04:53 Tigran Aivazian wrote:
> > On Tue, 21 Nov 2000, J . A . Magallon wrote:
> >
> > Quite the contrary. The patch seems correct and useful to me. What do you
> > think is wrong with it? (Linus accepted megabytes worth of
> > o Cleanup console_verbose() dunplication
> include/linux/kernel.h: if we are adding new inlines to kernel headers,
> they should be 'static inline'..
Agreed
> > o Epic100 update
>
> dhinds seemed to question the epic100 fix which is enclosed in
> CONFIG_CARDBUS... also I have
On Tue, 21 Nov 2000, Tigran Aivazian wrote:
> Hi Linus,
>
> In arch/i386/mm/init.c:show_mem() we calculate the number of free pages
> but don't printk it out. Therefore, we must either a) remove the variable
> and the calculation or b) make use of it. I think b) is obviously better.
>
> The
On Wed, 22 Nov 2000 00:04:53 Tigran Aivazian wrote:
> On Tue, 21 Nov 2000, J . A . Magallon wrote:
>
> Quite the contrary. The patch seems correct and useful to me. What do you
> think is wrong with it? (Linus accepted megabytes worth of the above in
> the past...)
>
Sorry, i should look at
Richard Torkar wrote:
>
> Well David, there is such a "manual".
>
> http://ftp.sunet.se/LDP/FAQ/faqs/GCC-SIG11-FAQ
Yes. And if you ask the average new Linux user if they've read it, I
doubt you'll get a "yes". My question boils down to this, and this I
suppose is a personal/informational
On 21 Nov, [EMAIL PROTECTED] wrote:
> Hm, there is no stable xinput driver available for XFree 4.0 and
> xinput does not support the wheel, too :-(
Actually XInput supports that sort of information but probably the
XInput driver doesn't. Unfortunately I don't have a Graphire, just
a Intuos
I noticed something odd with the entropy pool in 2.4.0-test11. If a normal
user does a 'sysctl -A', the entropy pool empties. I'm not sure why, but it
sounds like this isn't a good thing from a security standpoint.
DS
-
To unsubscribe from this list: send the line "unsubscribe
On Tue, 21 Nov 2000, J . A . Magallon wrote:
>
> On Tue, 21 Nov 2000 22:25:01 Bartlomiej Zolnierkiewicz wrote:
> >
> > Quick removal of unnecessary initialization to 0.
> >
> >
> > -static int basePort = 0; /* base port address */
> > -static int regPort = 0;/* port for
Here is a patch which ports drivers/sound/maestro.c to the new PCI
interface, which Zach Brown asked me to post here for comments.
This patch includes Zach's changes eliminating the ioctl lockups which
he posted separately, just to make it easier to generate the final
product from pristine
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
On Tue, 21 Nov 2000 22:25:01 Bartlomiej Zolnierkiewicz wrote:
>
> Quick removal of unnecessary initialization to 0.
>
>
> -static int basePort = 0; /* base port address */
> -static int regPort = 0; /* port for register number */
> -static int dataPort = 0; /* port for
On Tuesday November 21, [EMAIL PROTECTED] wrote:
> Hi,
> I want to know , how to Benchmark the performance of
> RAID.Is there any tool for benchmarking?
>
It all depends on what you want to measure.
If you want to measure "how well will this work for me", then you need
a tool that generates a
On Tue, Nov 21, 2000 at 10:47:20AM -0800, Richard Henderson wrote:
> On Tue, Nov 21, 2000 at 06:46:09PM +0300, Ivan Kokshaysky wrote:
> >Interesting, other pyxis machines do not seem to be so sensitive,
> >so I guess some design problems with ux164 motherboard - all this
> >looks
Hi
I think I have a possible explanation for your observations:
1) 1024B Block size:
> User time (seconds): 69.32
> System time (seconds): 25.15
> Percent of CPU this job got: 54%
> Elapsed (wall clock) time (h:mm:ss or m:ss): 2:54.14
> Major (requiring
The subject says it all. Is there any particular (technical) reason why I
must have both the generic pcmcia code and the controller support
built-in, or build all of them as modules?
/Tobias
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Ok, I'm sure this isn't any sort of show stopper for the 2.4.0 series
(or any other series for that matter, and they probably all have it),
but when mapping memory to page 0 in the program header of an ELF,
linux completely ignores the ph_memsz field.. I've attached a program
to demonstrate..
Roy Sigurd Karlsbakk wrote:
>
> Hi
>
> With some years of practice with Novell NetWare, I've been wandering why
> the (unused?) file system compression mechanism in ext2 is based on
> doing realtime compression. To make compression efficient, it can't be
> made this simple. Let's look at the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David Riley wrote:
> Jeff Epler wrote:
> >
> > On Tue, Nov 21, 2000 at 04:08:26PM -0500, David Riley wrote:
> > > Windoze is not the only OS to handle bad hardware better than Linux. On
> > > my Mac, I had a bad DIMM that worked fine on the MacOS
Jeff Epler wrote:
>
> On Tue, Nov 21, 2000 at 04:08:26PM -0500, David Riley wrote:
> > Windoze is not the only OS to handle bad hardware better than Linux. On
> > my Mac, I had a bad DIMM that worked fine on the MacOS side, but kept
> > causing random bus-type errors in Linux. Same as when I
Hi!
Someone overzealously added too many KERN_INFOs to pcnet32, so that they
appear not only at the beginning of each line, but also many times in
between words. This is wrong.
This patch removes the extraneous KERN_* from pcnet32. It leaves all
those that should be there in place. It does not
> > This is true. What I suppose would be the solution is that if faulty
> > hardware is found, a reduction in performance should be made.
>
> Finding out if you've got bad RAM might take a few hours running mem86. Not
> exactly what I have in mind to do each boot...
Even if memtest doesn't
Hi,
Support for some 53c400 cards is still bad (the non-PnP), so I'll start
fixing this.
I'll be my fist kernel job, so please spare me :))
Issues :
53c400a non-PNP still lock this system hard. It starts barking about a
busy SCSI bus, and then I can fsck again.
To Alan : How hard is it to
On Tue, 21 Nov 2000, Jeff Garzik wrote:
> Tobias Ringstrom wrote:
> > When saying yes to "Plug-and-play OS" in the BIOS, my 3Com 905C adapter
> > stops working, since the driver tries to use IRQ 0, since the BIOS does
> > not assign an IRQ to it. The driver seems to read the IRQ from the card
> >
On Tue, 21 Nov 2000, Horst von Brand wrote:
> David Riley <[EMAIL PROTECTED]> said:
> > This is true. What I suppose would be the solution is that if faulty
> > hardware is found, a reduction in performance should be made.
> Finding out if you've got bad RAM might take a few hours running mem86.
Hi Linus,
In arch/i386/mm/init.c:show_mem() we calculate the number of free pages
but don't printk it out. Therefore, we must either a) remove the variable
and the calculation or b) make use of it. I think b) is obviously better.
The patch below was tested under 2.4.0-test11.
Regards,
Tigran
David Riley <[EMAIL PROTECTED]> said:
[...]
> This is true. What I suppose would be the solution is that if faulty
> hardware is found, a reduction in performance should be made.
Finding out if you've got bad RAM might take a few hours running mem86. Not
exactly what I have in mind to do each
Bartlomiej Zolnierkiewicz wrote:
> --- linux-240t11/drivers/ide/Config.in Wed Nov 15 22:02:11 2000
> +++ linux/drivers/ide/Config.in Tue Nov 21 14:52:07 2000
> @@ -68,7 +68,7 @@
> dep_bool 'OPTi 82C621 chipset enhanced support (EXPERIMENTAL)'
>CONFIG_BLK_DEV_OPTI621
David Riley <[EMAIL PROTECTED]> said:
> Horst von Brand wrote:
> > So what? My former machine ran fine with Win95/WinNT. Linux wouldn't even
> > end booting the kernel. Reason: P/100 was running at 120Mhz. Fixed that, no
> > trouble for years. Not the only case of WinXX running (apparently?) fine
Hi James
this is a newer cleaning patch for vgacon.c against test11.
It includes the one I sent a couple of days ago.Could you check this too
and if OK send it to Linus?Unless of course it violates the code-freeze
policy :-)
Thanks,
Jani.
It does the following
1)Removes
On Tue, Nov 21, 2000 at 04:08:26PM -0500, David Riley wrote:
> Windoze is not the only OS to handle bad hardware better than Linux. On
> my Mac, I had a bad DIMM that worked fine on the MacOS side, but kept
> causing random bus-type errors in Linux. Same as when I accidentally
> (long story)
On Tue, 21 Nov 2000, Stephen Gutknecht (linux-kernel) wrote:
> What a Linux kernel compile DOESN'T test is the network interfaces and video
> cards.
Kernel compile over NFS while playing unreal tournament in X ;)
-Dan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
On Tue, 21 Nov 2000, David Riley wrote:
> Horst von Brand wrote:
>
> Windoze is not the only OS to handle bad hardware better than Linux. On
> my Mac, I had a bad DIMM that worked fine on the MacOS side, but kept
> causing random bus-type errors in Linux. Same as when I accidentally
I
On Tue, 21 Nov 2000, David Riley wrote:
> Horst von Brand wrote:
> >
> > So what? My former machine ran fine with Win95/WinNT. Linux wouldn't even
> > end booting the kernel. Reason: P/100 was running at 120Mhz. Fixed that, no
> > trouble for years. Not the only case of WinXX running
Part of the issue is that there exists no "easy to use" standardized test
software. Full 32-bit concurrent use of many devices can reveal problems
that users do not often see in normal applications.
One major hardware review site found stability problems with the Intel
Pentium 3 1130Mhz
the problem is that unless you tecompile the kernel to add timing delays,
you cannot change the timing like this (if you put the tests in all your
fast paths to add delays you have just destroyed your performance in the
case where the hardware is good)
also you don't know the hardware is really
In message <[EMAIL PROTECTED]>, "Mohammad A. Haque" writes:
> I read somewhere that hpt366 bios 1.26 will fix the problem with this
> particular drive. I'll try and dig up the reference.
From the 1.26beta bios redame-file (at http://www.highpoint-tech.com)
1.26.0 08Aug00
. Fix
David Lang wrote:
>
> David, usually when it turns out that Linux finds hardware problems the
> underlying cause is that linux makes more effective use of the component,
> and as such something that was marginal under windows fails under linux as
> the correct timing is used.
This is true.
Hi
Quick removal of unnecessary initialization to 0.
--
Bartlomiej Zolnierkiewicz
<[EMAIL PROTECTED]>
diff -uNr linux-240t11/drivers/ide/ali14xx.c linux/drivers/ide/ali14xx.c
--- linux-240t11/drivers/ide/ali14xx.c Tue Jun 13 20:32:00 2000
+++ linux/drivers/ide/ali14xx.c Tue Nov 21 14:35:59
Hi
In drivers/Config.in CONFIG_BLK_DEV_OSB4 depends on itself...
--
Bartlomiej Zolnierkiewicz
<[EMAIL PROTECTED]>
--- linux-240t11/drivers/ide/Config.in Wed Nov 15 22:02:11 2000
+++ linux/drivers/ide/Config.in Tue Nov 21 14:52:07 2000
@@ -68,7 +68,7 @@
dep_bool 'OPTi 82C621
Hi
- OSB4 isn't marked (EXPERIMENTAL) in drivers/ide/Config.in so it
shouldn't be marked so in Configure.help.
- PDC202XX driver also supports PDC20265.
- new VIA82CXXX driver removed kernel command line option (FIFO
setting) and CONFIG_VIA82CXX_TUNING
--
Bartlomiej Zolnierkiewicz
<[EMAIL
David, usually when it turns out that Linux finds hardware problems the
underlying cause is that linux makes more effective use of the component,
and as such something that was marginal under windows fails under linux as
the correct timing is used.
David Lang
On Tue, 21 Nov 2000, David Riley
Here is a patch to fix a compile error which I previously reported on
the 2.4.0test11-ac1 thread.
I tried to compile 2.4.0-test11-ac1, and here is where the compile bombed
out:
/usr/bin/kgcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes
-O2 -fomit-frame-pointer
Horst von Brand wrote:
>
> So what? My former machine ran fine with Win95/WinNT. Linux wouldn't even
> end booting the kernel. Reason: P/100 was running at 120Mhz. Fixed that, no
> trouble for years. Not the only case of WinXX running (apparently?) fine
> on broken/misconfigured hardware I've
I read somewhere that hpt366 bios 1.26 will fix the problem with this
particular drive. I'll try and dig up the reference.
David Woodhouse wrote:
>
> WorksForMe(tm)
>
> Grrr. I specifically went and read the HPT366 blacklist before buying my
> shiny new hard drive.
>
--
On Tue, 21 Nov 2000, Andre Hedrick wrote:
>
> Does that fix it?
WorksForMe(tm)
Grrr. I specifically went and read the HPT366 blacklist before buying my
shiny new hard drive.
> On Tue, 21 Nov 2000, David Woodhouse wrote:
> > Index: drivers/ide/hpt366.c
> >
On Tue, 21 Nov 2000 13:13:27 Jakub Jelinek wrote:
> On Tue, Nov 21, 2000 at 06:02:35AM -0600, Peter Samuelson wrote:
> >
> > While trying to clean up some code recently (CONFIG_MCA, hi Jeff), I
> > discovered that gcc 2.95.2 (i386) does not remove dead string
> > constants:
> >
> > void foo
1 - 100 of 404 matches
Mail list logo
