Now that it seems that George Bush has won the presidency, I am wondering
whether Linus and other members of the free software community intend to
leave the U.S. and go to more friendly places. Imagine what G.W. Bush is
going to do to export controls, free software, copyright law, patent law,
On Wed, 8 Nov 2000, Michael Rothwell wrote:
>
> Like what? I'm not sure what you're saying here. It seems that the pople
> writing the IrDA code have gotten no feedback from you as to why their
> patch is never accepted -- could you clarify?
Just to clarify.
The ONLY message from the IrDA
Many apologies, it's late and I ran the default ksymoops (0.7c) instead of
./ksymoops
However, after running the real ksymoops against it, it gives nothing
new; I suppose since 'ls' is dying and the stack is from 'ls', that's why.
Is there anything else I should do before booting back to a
"Gregory S. Youngblood" <[EMAIL PROTECTED]> writes:
> The problem occurs with Mandrake 7.0 and 7.1 with kernels 2.2.14, 2.2.16,
> and 2.2.17. These are the secure kernels that Mandrake provides.
can you try with a 2.2.17 kernel rpm standard (no smp no secure) ?
--
MandrakeSoft Inc
On Tue, Nov 07, 2000 at 10:09:34AM -0800, Reto Baettig wrote:
> I have a problem whith Alpha SMP's which seems to be kernel-related. I
> discussed this on the bug-glibc list but everybody seems to agree that
> it cannot be a libc problem.
Indeed it does seem to be some sort of tlb flushing
I've got a problem with inodes which spans three kernels when used
as a gateway/firewall.
The problem occurs with Mandrake 7.0 and 7.1 with kernels 2.2.14, 2.2.16,
and 2.2.17. These are the secure kernels that Mandrake provides.
The catch is, it only affects one machine - the machine I set up
On Wed, 8 Nov 2000 00:38:33 -0600 (CST),
Matthew Hanselman <[EMAIL PROTECTED]> wrote:
>I can poke around tomorrow morning without a reboot, but then I'll have to
>reboot (so please respond via email if I can do anything). I tried
>grinding the message through ksymoops-2.3.5, and it complains
Hi,
Could somebody tell me why inode->i_atomic_write is used in 2.2.x?
And also why this is absent in 2.4.x (actually replaced by ->i_zombie)?
Thanks,
Naren
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the
hi i am writing a video kernel driver for linux lexos and have got
stuck
this is how NVIDIA do their regs
#define NV_PFIFO_RAMHT
0x2210 /* RW-4R */
#define NV_PFIFO_RAMHT_BASE_ADDRESS
8:4 /* RWIUF */
#define
Hi Linus,
This patch fixes a place where we could return with a read/write
lock held. Also update MAINTAINERS and CREDITS files.
Cheers,
Stephen
--
Stephen Rothwell, Open Source Researcher, Linuxcare, Inc.
+61-2-62628990 tel, +61-2-62628991 fax
[EMAIL PROTECTED], http://www.linuxcare.com/
On Tue, Nov 07, 2000 at 06:18:09PM -0800, H. Peter Anvin wrote:
> Jeff Garzik wrote:
> >
> > "Jeff V. Merkey" wrote:
> > > We need a format that allow multiple executable segments to be combined
> > > in a single executable and the loader have enough smarts to grab the
> > > right one based on
I have a directory on my local filesystem that I cannot access on
2.4.0-test10. It happens when I try to "ls" in this bad directory, and ls
segfaults.
I can poke around tomorrow morning without a reboot, but then I'll have to
reboot (so please respond via email if I can do anything). I tried
Here's the Configure.help patch for Alpha against the 2.2.18pre
series. Alan, if you can find time to include this one, I'd appreciate it
:-)
diff -ur linux-2.2.18pre19/Documentation/Configure.help
linux/Documentation/Configure.help
--- linux-2.2.18pre19/Documentation/Configure.help Fri
Rich Payne (API) and I have made a patch for Documentation/Configure.help
to add some more systems to the list of Alphas. Since the original list
was compiled, some of the newer system types were added, but not
all. Also, the list wasn't as inclusive as it should've been (we've been
getting
On Wed, 8 Nov 2000, Michael Rothwell wrote:
> Linus Torvalds wrote:
> >
> > Also, I've never seen much in the form of explanation, and at least the
> > last patch I saw just the first screenful was so off-putting that I just
> > went "Ok, I have real bugs to fix, I don't need this crap".
>
>
Linus Torvalds wrote:
>
> On Tue, 7 Nov 2000, Michael Rothwell wrote:
> >
> > Linus, can you post reasons why you keep ignoring^W rejecting the IrDA
> > patch?
>
> Basically, whatever Alan rants, I've not seen the patches all that many
> times at all.
>
> Also, I've never seen much in the form
Ivan Passos wrote:
>
> Hello,
>
> I was just checking the driver changes needed to comply with the new PCI
> architecture in 2.4.x, and then I got into a problem. I noticed that all
> drivers that use this architecture (or at least the ones I found, such as
> the Tulip, EEPro100, 3c59x ...)
Hello,
I was just checking the driver changes needed to comply with the new PCI
architecture in 2.4.x, and then I got into a problem. I noticed that all
drivers that use this architecture (or at least the ones I found, such as
the Tulip, EEPro100, 3c59x ...) support boards with only one
On Tue, 7 Nov 2000, Gary E. Miller wrote:
>
> I see this patch did not make it into test11-pre1. Without it
> raid1 and SMP do not work together. Please consider for test11-pre2.
You must have a different test11-pre1 than the one I have.
It's already there in -pre1, as far as I can see.
On Tue, 7 Nov 2000 21:48:59 -0500 (EST),
"Mike A. Harris" <[EMAIL PROTECTED]> wrote:
>On Tue, 7 Nov 2000, Alan Cox wrote:
>>Actually they do. I agree that it wants sorting. Im just wondering what the
>>best approach is - maybe check modutils rev and only add the link if its high
>>enough ?
>
On Tue, 7 Nov 2000, Jeff V. Merkey wrote:
> Your way out in the weeds. What started this thread was a customer who
> ended up loading the wrong arch on a system and hanging. I have to
> post a kernel RPM for our release, and it's onerous to make customers
> recompile kernels all the time and
On Tue, 7 Nov 2000, Jeff V. Merkey wrote:
> What makes more sense is to pack multiple segments for different
> processor architecures into a single executable package, and have the
> loader pick the right one (the NT model). It could be used for
> SMP and non-SMP images, though, as well as
On Tue, 7 Nov 2000, Alan Cox wrote:
>Date: Tue, 7 Nov 2000 12:11:57 + (GMT)
>From: Alan Cox <[EMAIL PROTECTED]>
>To: Keith Owens <[EMAIL PROTECTED]>
>Cc: Tomasz Motylewski <[EMAIL PROTECTED]>,
> Alan Cox <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
>Content-Type: text/plain; charset=us-ascii
On Wed, Nov 08, 2000 at 03:39:39AM +, [EMAIL PROTECTED] wrote:
> On Tue, 7 Nov 2000, Jeff V. Merkey wrote:
>
> > > remember it's not just the start of the file that varies based on cachline
> > > size, it's the positioning of code and data thoughout the kernel image.
> > Understood. I will
On Tue, 7 Nov 2000, Marty Fouts wrote:
> There's been a bunch of related work done at the Oregon Graduate Institute
> by Calton Pu and others. See
> http://www.cse.ogi.edu/DISC/projects/synthetix/publications.html for a list
> of papers.
The only paper that immediately caught my eye of
On Wed, Nov 08, 2000 at 03:25:56AM +, [EMAIL PROTECTED] wrote:
> On Tue, 7 Nov 2000, Jeff V. Merkey wrote:
>
> > If the compiler always aligned all functions and data on 16 byte
> > boundries (NetWare) for all i386 code, it would run a lot faster.
>
> Except on architectures where 16 byte
On Tue, 7 Nov 2000, Jeff V. Merkey wrote:
> > remember it's not just the start of the file that varies based on cachline
> > size, it's the positioning of code and data thoughout the kernel image.
> Understood. I will go off and give some thought and study and respond
> later after I have a
Sean Middleditch <[EMAIL PROTECTED]> writes:
> I've installed the Linux-Mandrake 7.2 distro (which uses kernel version
> 2.2.17) on a PIII system (Asus motherboard, Award Medallion v6.0 BIOS).
> For some reason, neither LILO nor Grub were able to boot off of the
> second hard-drive (where Linux
On Tue, 7 Nov 2000, Jeff V. Merkey wrote:
(Please forgive this snippage making Jeff look less literate
than he is, even after several beers.)
> We need a format that allow
[..]
> the right one based on architecture.
Oh, we already have that. It's called source code.
Matthew.
-
To
On Tue, 7 Nov 2000, Jeff V. Merkey wrote:
> > > Detecting the CPU isn't the issue (we already do all this), it's what to
> > > do when you've figured out what the CPU is. Show me code that can
> > > dynamically adjust the alignment of the routines/variables/structs
> > > dependant upon cacheline
On Tue, 7 Nov 2000, Jeff V. Merkey wrote:
> If the compiler always aligned all functions and data on 16 byte
> boundries (NetWare) for all i386 code, it would run a lot faster.
Except on architectures where 16 byte alignment isn't optimal.
> Cache line alignment could be an option in the
> imel96 wrote:
> >
> > hi all,
> >
> > just a few reports:
> >
> > 1. zImage in test10 somehow isn't working
properly. i have a
> > zImage sized a bit more than 500kb on my
harddrive which hangs at
> > the loading process (the one showing dots).
> >
From: "octave klaba" <[EMAIL PROTECTED]>
> > Oct 24 00:07:39 gimme kernel: VM: do_try_to_free_pages failed for
> > postmaster...
>
> 2.2.18pre19 should fix this problem if andrea's patch is inside.
> if not, you have to patch pre18 with VM-global-2.2.18pre18-7.bz2
> if you are from europe you can
There's been a bunch of related work done at the Oregon Graduate Institute
by Calton Pu and others. See
http://www.cse.ogi.edu/DISC/projects/synthetix/publications.html for a list
of papers.
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday,
Igmar Palsenberg wrote:
>
> > > I'm missing ptmx. You NEED a writable /dev/pts dir.
> > >
> >
> > Actually, what you need is the devpts filesystem mounted onto
> > /dev/pts.
>
> Agree. I had a shitload of probs when 2.2.0 came out and I switched.. Was
> due that /dev was readonly here. Bit
There is a variation of #2 that is often good enough, based on some research
work done at (among other places) the Oregon Graduate Center. I don't have
the references handy, but you might want to look for papers on "sandboxing"
authored there.
The basic idea is similar to the one used by many
Jeff Garzik wrote:
>
> "Jeff V. Merkey" wrote:
> > We need a format that allow multiple executable segments to be combined
> > in a single executable and the loader have enough smarts to grab the
> > right one based on architecture. two options:
> >
> > 1. extend gcc to support this or
Alan Cox wrote:
>
> > On Tue, Nov 07, 2000 at 09:02:36PM -0500, Michael Rothwell wrote:
> > > 64-bit printk.
> >
> > Please consider this one Alan, if not for v2.2.18, then at least for
> > v2.2.19pre1.
>
> Nobody has explained why we even need it.
Alan Cox wrote:
>
> Why do we need it ?
To
> On Tue, Nov 07, 2000 at 09:02:36PM -0500, Michael Rothwell wrote:
> > 64-bit printk.
>
> Please consider this one Alan, if not for v2.2.18, then at least for
> v2.2.19pre1.
Nobody has explained why we even need it.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
On Tue, Nov 07, 2000 at 09:02:36PM -0500, Michael Rothwell wrote:
> 64-bit printk.
Please consider this one Alan, if not for v2.2.18, then at least for
v2.2.19pre1.
/David
_ _
// David Weinehall <[EMAIL PROTECTED]> /> Northern
64-bit printk.
-M
Alan Cox wrote:
>
> Ok last call for 2.2.18. The PS/2 cases I've looked at all appear to be
> ghost PS/2 interfaces created due to the USB support fooling programs.
diff -B --unidirectional-new-file --exclude-from=DiffExcludeList --recursive --unified
Ok last call for 2.2.18. The PS/2 cases I've looked at all appear to be
ghost PS/2 interfaces created due to the USB support fooling programs.
Break it if you can 8)
Alan
[S/390 stuff isnt trivial to merge so will have to wait]
2.2.18pre20
o Fix ide-probe SMP build error
On Tue, Nov 07, 2000 at 08:24:38PM -0500, Jeff Garzik wrote:
>
> Take a look at
> http://www.uwsg.iu.edu/hypermail/linux/kernel/9908.0/0669.html This
> happened with ISDN. Slightly different situation, but similar.
I'm familiar with that. The *BIG* difference is that Dag has
always
On Wed, Nov 08, 2000 at 01:41:40AM +0100, Igmar Palsenberg wrote:
> malloc(0) is bogus in this case. malloc(0) == free();
No, you're thinking of realloc.
Tim.
*/
PGP signature
In message <[EMAIL PROTECTED]> you write:
> Paul Gortmaker wrote:
> > - extern void ether_setup(struct net_device *dev);
> > + extern void __ether_setup(struct net_device *dev);
> > + static inline void ether_setup(struct net_device *dev){
> > + dev->owner = THIS_MODULE;
> > +
Alan Cox wrote:
>
> > I'll grab the code in linux and port.
>
> You are welcome
>
> Make sure you get a pretty current 2.2.x tree however. The ultra deep magic
> for detecting NexGen processors is recent. It took a long time before I found
> someone who knew how it worked 8)
I'll get on it.
> We need a format that allow multiple executable segments to be combined
> in a single executable and the loader have enough smarts to grab the
> right one based on architecture. two options:
ELF can do that just fine
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel"
> I'll grab the code in linux and port.
You are welcome
Make sure you get a pretty current 2.2.x tree however. The ultra deep magic
for detecting NexGen processors is recent. It took a long time before I found
someone who knew how it worked 8)
-
To unsubscribe from this list: send the line
Jeff Garzik wrote:
>
> Jeff Merkey wrote:
> > The PE model uses flags to identify CPU type and capbilities
>
> So does ELF.
Jeff,
Can we also combine mutiple segments from different processors or is it
a one-sy two-sy king of affair? If so, we're there, it just becomes a
linking option.
I
Alan Cox wrote:
>
> > There are tests for all this in the feature flags for intel and
> > non-intel CPUs like AMD -- including MTRR settings. All of this could
> > be dynamic. Here's some code that does this, and it's similiar to
> > NetWare. It detexts CPU type, feature flags, special
Jeff Merkey wrote:
> The PE model uses flags to identify CPU type and capbilities
So does ELF.
--
Jeff Garzik | "When I do this, my computer freezes."
Building 1024 | -user
MandrakeSoft| "Don't do that."
| -level 1
-
> There are tests for all this in the feature flags for intel and
> non-intel CPUs like AMD -- including MTRR settings. All of this could
> be dynamic. Here's some code that does this, and it's similiar to
> NetWare. It detexts CPU type, feature flags, special instructions,
> etc. All of this
Yo All!
I see this patch did not make it into test11-pre1. Without it
raid1 and SMP do not work together. Please consider for test11-pre2.
RGDS
GARY
---
Gary E. Miller Rellim 20340 Empire Ave, Suite E-3, Bend, OR 97701
> As for the 2.2.18 patch for correctly determining 2GHz and above, can
> it be easily merged into the 2.4.x kernel, and if so, what's the maximum
> clock speed that can be detected?
It should be easy yes. Its good to 100Ghz or so now ;)
-
To unsubscribe from this list: send the line
> This way all should work. However someone mentioned that the returns
> from "malloc" should be unique. Why would that be? That would prohibit
> my "1" trick. The statement implies you want to go about checking
> pointers for equality. If for example you have a memcmp (a, b) that
> has "if (a
Matti Aarnio wrote:
> needed size is bound to get user burned. malloc(0) is insane thing
> (IMO), but at least glibc supports it for some reason. Likely just due
> to padding and minimum size issues.
Part of the desing of the C language and the library is intended to
make boundary conditions
David Relson wrote:
>
> It seems to me that kernel/cpu matching can be broken into two relatively
> simple parts.
>
> 1 - Put a cpu "signature" in the kernel image indicating cpu requirements; and
> 2 - Have the bootloader (lilo) detect cpu type and match it against the cpu
> "signature".
>
It seems to me that kernel/cpu matching can be broken into two relatively
simple parts.
1 - Put a cpu "signature" in the kernel image indicating cpu requirements; and
2 - Have the bootloader (lilo) detect cpu type and match it against the cpu
"signature".
The bootloader would then load the
Jeff Garzik wrote:
>
> "Jeff V. Merkey" wrote:
> > We need a format that allow multiple executable segments to be combined
> > in a single executable and the loader have enough smarts to grab the
> > right one based on architecture. two options:
> >
> > 1. extend gcc to support this or
David Lang wrote:
>
> Jeff, the kernel image is already pretty large. if you try and take what
> are basicly independant kernel images and put them in one file you will
> very quickly endup with something that is to large to use.
>
> As an example a kenel for a boot floppy needs to be <1.4MB
"Jeff V. Merkey" wrote:
> We need a format that allow multiple executable segments to be combined
> in a single executable and the loader have enough smarts to grab the
> right one based on architecture. two options:
>
> 1. extend gcc to support this or rearragne linux into segments based on
>
Code is. Data isn't. Gcc packs data into the segment like sardines in
a can (NT code does to). 16 byte align this as well. NetWare 16 byte
aligns everythin with an align 16 directive in the data segments of
assembler modules.
Jeff
Jeff Garzik wrote:
>
> "Jeff V. Merkey" wrote:
> > If the
Jeff, the kernel image is already pretty large. if you try and take what
are basicly independant kernel images and put them in one file you will
very quickly endup with something that is to large to use.
As an example a kenel for a boot floppy needs to be <1.4MB compressed,
it's not uncommon for
Jeff Garzik wrote:
>
> Jeff Merkey wrote:
> > here are tests for all this in the feature flags for intel and
> > non-intel CPUs like AMD -- including MTRR settings. All of this could
> > be dynamic. Here's some code that does this, and it's similiar to
> > NetWare. It detexts CPU type,
"Jeff V. Merkey" wrote:
> If the compiler always aligned all functions and data on 16 byte
> boundries (NetWare)
> for all i386 code, it would run a lot faster.
Are you saying that it isn't? Have you look at gcc-generated assembly
from a recent 2.2.x or 2.4.x kernel?
2.2.x build command line,
Sven Koch wrote:
>
> On Tue, 7 Nov 2000, David Lang wrote:
>
> > depending on what CPU you have the kernel (and compiler) can use different
> > commands/opmizations/etc, if you want to do this on boot you have two
> > options.
>
> Wouldn't it be possible to compile the parts of the kernel
Jeff Merkey wrote:
> here are tests for all this in the feature flags for intel and
> non-intel CPUs like AMD -- including MTRR settings. All of this could
> be dynamic. Here's some code that does this, and it's similiar to
> NetWare. It detexts CPU type, feature flags, special instructions,
>
On Tue, 7 Nov 2000, David Lang wrote:
> depending on what CPU you have the kernel (and compiler) can use different
> commands/opmizations/etc, if you want to do this on boot you have two
> options.
Wouldn't it be possible to compile the parts of the kernel needed to
uncompress and to detect the
"Jeff V. Merkey" wrote:
>
> [EMAIL PROTECTED] wrote:
> >
> > > There are tests for all this in the feature flags for intel and
> > > non-intel CPUs like AMD -- including MTRR settings. All of this could
> > > be dynamic. Here's some code that does this, and it's similiar to
> > > NetWare.
Update: I just tested it on Alpha UP and everything's fine. It really
seems to be a SMP problem...
Reto Baettig wrote:
>
> Hi
>
> I have a problem whith Alpha SMP's which seems to be kernel-related. I
> discussed this on the bug-glibc list but everybody seems to agree that
> it cannot be a
On Tue, 7 Nov 2000, Lyle Coder wrote:
> When a program does a malloc... the glibc gets atleast on page (brk)
> [actually, glibs determins of it needs to brk more memory from the kernel...
> because it maintains it;s own pool].. so if you malloc 4 byts, you can copy
> to that pointer more than 4
> The program does not work. A program works if it does what it's supposed to
> do. If you want to argue that this program is supposed to print "ff"
> then explain to me why the 'malloc' contains a zero in parenthesis.
>
> The program can't possibly work because it invokes
David Lang wrote:
>
> Jeff, the problem is not detecting the CPU type at runtime, the problem is
> trying to re-compile the code to take advantage of that CPU at runtime.
>
> depending on what CPU you have the kernel (and compiler) can use different
> commands/opmizations/etc, if you want to
[EMAIL PROTECTED] wrote:
>
> > There are tests for all this in the feature flags for intel and
> > non-intel CPUs like AMD -- including MTRR settings. All of this could
> > be dynamic. Here's some code that does this, and it's similiar to
> > NetWare. It detexts CPU type, feature flags,
You must upgrade to the latest release: 4.0.1e
The fix for this problem went into 4.0.1d, but since you
need to upgrade, you might as well get the latest code.
Miles
On Wed, 8 Nov 2000, David Luyer wrote:
>
> I'm having problems with X 4.0.1 and 2.4.0-test kernels on a Toshiba
> I'm not sure that is fully responsive, Dan. Why doesn't the
> strcpy throw a hissyfit and coredump?
Because he's a lucky guy and doesn't cross a page boundary. If the
"" thing is the entire Wind95 source code it will dump :-)
> {^_^}
Igmar
-
To unsubscribe from this list: send
On Tue, 7 Nov 2000, Su Hwan Hwang wrote:
> I'm interested in linux-kernel but I'm beginner.
>
> So I don't know how to study linux-kernel.
http://kernelnewbies.org/
Rik
--
The Internet is not a network of computers. It is a network
of people. That is its real strength.
On Mon, 6 Nov 2000, RAJESH BALAN wrote:
> hi,
> why does this program works. when executed, it doesnt
> give a segmentation fault. when the program requests
> memory, is a standard chunk is allocated irrespective
> of the what the user specifies. please explain.
>
> main()
> {
>char *s;
>
Yeach... I'm a bit sleepy...
first [PATCH]: kmalloc/kfree bugs hit 1
second [PATCH]: ide modules and /proc fs
--
bkz
-
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/
I'm having problems with X 4.0.1 and 2.4.0-test kernels on a Toshiba Libretto
110CT. Is this likely to be related to a known problem or can someone
recommend some random intermediate kernel versions to try (binary elimination
avoiding known-bad kernel versions...)?
H/w: Toshiba Libretto 110CT
On Mon, Nov 06, 2000 at 02:48:27PM -0700, Jeff V. Merkey wrote:
> Yann Dirson wrote:
> > Nov 5 22:36:17 bylbo nscd: 925: while accepting connection: Cannot allocate memory
> >
> > They usually appear at cron.daily time, although it looks like I kinda can
> > reproduce them. I'm still
Jeff, the problem is not detecting the CPU type at runtime, the problem is
trying to re-compile the code to take advantage of that CPU at runtime.
depending on what CPU you have the kernel (and compiler) can use different
commands/opmizations/etc, if you want to do this on boot you have two
> There are tests for all this in the feature flags for intel and
> non-intel CPUs like AMD -- including MTRR settings. All of this could
> be dynamic. Here's some code that does this, and it's similiar to
> NetWare. It detexts CPU type, feature flags, special instructions,
> etc. All of
> > I'm missing ptmx. You NEED a writable /dev/pts dir.
> >
>
> Actually, what you need is the devpts filesystem mounted onto
> /dev/pts.
Agree. I had a shitload of probs when 2.2.0 came out and I switched.. Was
due that /dev was readonly here. Bit strange if I think of it.
>
> -hpa
Patch fixes ide-disk/ide-floppy/ide-probe modules interaction
with /proc fs. Last chunk is needed to compile ide-probe as
module without /proc support.
--
Bartlomiej Zolnierkiewicz
<[EMAIL PROTECTED]>
--- linux-240t10p6/drivers/ide/ide-disk.c Thu Oct 19 22:05:01 2000
+++
> I'm interested in linux-kernel but I'm beginner.
> So I don't know how to study linux-kernel.
> Please tell me.
http://www.kernelnewbies.org
regards,
Davej.
--
| Dave Jones <[EMAIL PROTECTED]> http://www.suse.de/~davej
| SuSE Labs
-
To unsubscribe from this list: send the line
There are tests for all this in the feature flags for intel and
non-intel CPUs like AMD -- including MTRR settings. All of this could
be dynamic. Here's some code that does this, and it's similiar to
NetWare. It detexts CPU type, feature flags, special instructions,
etc. All of this on x86
Hi
I have a problem whith Alpha SMP's which seems to be kernel-related. I
discussed this on the bug-glibc list but everybody seems to agree that
it cannot be a libc problem.
I attached a little testprogram which reproduces the bug in < 1Minute.
BUT: IT MUST BE STARTED AT LEAST TWICE!
The
I hitted few items from Dawson Engler's list of potential kmalloc/kfree
bugs...
--
Bartlomiej Zolnierkiewicz
<[EMAIL PROTECTED]>
--- linux-240t10/drivers/ide/ide-probe.cTue Oct 3 00:16:51 2000
+++ linux/drivers/ide/ide-probe.c Tue Nov 7 00:25:35 2000
@@ -652,6 +653,10 @@
Marc Lehman verified that PII systems will generate tons of AGIs with
gcc. Perhaps this is the cause of this problem. You could run EMON and
see if there is something obvious in the numbers ...
Jeff
"Richard B. Johnson" wrote:
>
> On Wed, 8 Nov 2000, Keith Owens wrote:
>
> > On Tue, 7 Nov
On Mon, 6 Nov 2000, Jeff Garzik wrote:
> The address_space::writepage callback is called from try_to_swap_out()
> path, and also from the filemap_sync_pte() path. There appears to be no
> way to tell the difference between the two callers. This is not good
> because the semantics are very
Alan,
As for 'rep nop', couldn't we add in the code, as an example:
#ifdef Pentium_4
rep nop
#endif
As for the 2.2.18 patch for correctly determining 2GHz and above, can
it be easily merged into the 2.4.x kernel, and if so, what's the maximum
clock speed that can be detected?
Regards,
Su Hwan Hwang wrote:
>
> I'm interested in linux-kernel but I'm beginner.
>
> So I don't know how to study linux-kernel.
1. Go to www.linuxdoc.org and read the HOWTOs on the Linux kernel.
2. Buy a coffee maker and 3000 lbs. of coffee beans. You will also
need a coffee grinder to grind the
On Wed, 8 Nov 2000, Keith Owens wrote:
> On Tue, 7 Nov 2000 17:31:19 -0500 (EST),
> "Richard B. Johnson" <[EMAIL PROTECTED]> wrote:
> >Also, I get some CPU watchdog timeout that I didn't ask for Grrr...
> >
> >Nov 7 17:17:54 chaos nmbd[115]: Samba server CHAOS is now a domain master
"Jeff V. Merkey" wrote:
> So how come NetWare and NT can detect this at run time, and we have to
> use a .config option to specifiy it? Come on guys.
Linux detects this as well -
However this is not about detection, but optimizations.
Optimizations e.g. for xeon could keep a K6/2 from
On Tue, 7 Nov 2000, Jeff V. Merkey wrote:
> So how come NetWare and NT can detect this at run time, and we have to
> use a .config option to specifiy it? Come on guys.
Then run a kernel compiled for i386 and suffer the poorer code quality
that comes with not using newer instructions and
I don't know about you, but I like having the option to cut out code from
my kernel that will never get used for a particular cpu arch.;o)
Or was that just a troll ;o)
- Forwarded by Bruce Holzrichter/US/Infinium Software on 11/07/2000
05:46 PM -
On Tue, 7 Nov 2000 16:30:22 -0600 (CST),
Jesse Pollard <[EMAIL PROTECTED]> wrote:
> From: Keith Owens <[EMAIL PROTECTED]>
>> No need for a separate size field. Note that MODULE_PARM is built at
>> compile time so all persistent data must have a fixed compile time
>> size.
>
>I'll buy that -
On Tue, 07 Nov 2000 23:32:46 Jeff V. Merkey wrote:
>
> So how come NetWare and NT can detect this at run time, and we have to
> use a .config option to specifiy it? Come on guys.
>
If you can get NT to boot on a 486, perhaps that shows that NT does not use
any optimization...so does not
On Tue, 07 Nov 2000 23:31:19 Richard B. Johnson wrote:
> On Tue, 7 Nov 2000, Dr. Kelsey Hudson wrote:
..
> > 15:111130 IO-APIC-level bttv
> > NMI: 190856196 190856196
> > LOC: 190858464 190858463
> > ERR: 0
> >
..
>
>CPU0 CPU1
> 0:
1 - 100 of 441 matches
Mail list logo
