All console-related activity curently happens under spin_lock_irqsave(_lock).
This causes interrutps to be blocked for 1-2 milliseconds with vgacon, and for
hundreds of milliseconds with fbdevs. This results in network overruns, audio
dropouts, dropped characters on serial ports and other such
On Sat, 3 Mar 2001, Curtis Stevens wrote:
> ** This is the quasi-official and semi-temporary T13 email list server. **
>
> Andre
>
> I think We've gone out-of-bounds on this one. None of us are
> lawyers, and nobody can predict what is happening. Personally, I do not see
> the
This, along with the previous ac fixes finally get the smc-mca driver working
for me on my quirky MCA box.
James Bottomley
Index: smc-mca.c
===
RCS file: /home/jejb/CVSROOT/linux/2.4/drivers/net/smc-mca.c,v
retrieving revision
Keith,
I do builds in /usr/src/linux, which is a symlink
to /usr/src/linux-akpm. The recent `mkdep' changes
have broken this practice most horridly. When searching
.hdepend, `make' doesn't recognise that nested headers
have changed. This is because .hdepend has things like
Correction. I can umount the partitions, but I get the
following message:
"can't link lock file /etc/mtab~: No such file or
directory (use -n flag to override)"
And /etc/mtab isn't updated.
__
Do You Yahoo!?
Get email at your own domain with
And Kevin Buhr writes:
-
- > What Linux does presently on x86 is as right as right can be on
- > this platform.
-
- I'm not so sure.
Let me rephrase: According to a designer of the x87 and one
of the IEEE 754 authors, the behavior currently in Linux and
glibc is reasonable on x86.
Andre Tomt wrote:
>
> >'lba32' extensions Copyright (C) 1999,2000 John Coffman
> ^^
>
> Add lba32 as the top line in lilo.conf. Re-run lilo.
>
> > Fatal: geo_comp_addr: Cylinder number is too big (1274 > 1023)
>
> Before 2.4.3pre1, your kernel just happened to toss itself below
diff -urNX dontdiff linux-2.4.2/Documentation/DocBook/Makefile
linux-willy/Documentation/DocBook/Makefile
--- linux-2.4.2/Documentation/DocBook/Makefile Sat Feb 3 13:43:55 2001
+++ linux-willy/Documentation/DocBook/Makefile Sat Mar 3 18:01:07 2001
@@ -82,6 +82,8 @@
>'lba32' extensions Copyright (C) 1999,2000 John Coffman
^^
Add lba32 as the top line in lilo.conf. Re-run lilo.
> Fatal: geo_comp_addr: Cylinder number is too big (1274 > 1023)
Before 2.4.3pre1, your kernel just happened to toss itself below cylinder
1024.
> Go ahead, call me
- Original Message -
From: "Keith Owens" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Saturday, March 03, 2001 8:39 PM
Subject: Re: LILO error with 2.4.3-pre1...
> On Sat, 03 Mar 2001 19:19:28 -0600,
> "Steven J. Hill" <[EMAIL PROTECTED]> wrote:
> >I have
On Sat, 3 Mar 2001 23:35:34 + (GMT), Alan Cox wrote:
>> Well, from reading the source, I don't see how this can break APM... What=
>> am I
>> missing?
>
>If you've stopped kapm-idled from using cpu then you've stopped it from going
>into the bios suspend one presumes.
Maybe, maybe not.
Em Sat, Mar 03, 2001 at 10:45:17PM -0300, Rogerio Brito escreveu:
> On Mar 03 2001, Alan Cox wrote:
> > 2.4.2-ac11
> > o Resync with Linux 2.4.3pre1
> What exactly does these resyncs mean? Do they mean that the
> entire Linus's tree is merged in the -ac patches (unless
>
On Mar 03 2001, Alan Cox wrote:
> 2.4.2-ac11
> o Resync with Linux 2.4.3pre1
What exactly does these resyncs mean? Do they mean that the
entire Linus's tree is merged in the -ac patches (unless
explicitly noted)? And when things eventually get accepted by
On Sat, 03 Mar 2001 19:19:28 -0600,
"Steven J. Hill" <[EMAIL PROTECTED]> wrote:
>I have no idea why the 1023 limit is coming up considering 2.4.2 and
>LILO were working just fine together and I have a newer BIOS that has
>not problems detecting the driver properly. Go ahead, call me idiot :).
Hmm, needed 2.4.3-pre1 and went to install with LILO using
'lilo -v' and got this:
LILO version 21.4-4, Copyright (C) 1992-1998 Werner Almesberger
'lba32' extensions Copyright (C) 1999,2000 John Coffman
Reading boot sector from /dev/hda
Merging with /boot/boot.b
Boot image:
[EMAIL PROTECTED] (Kevin Buhr) writes:
> > You want peoples existing applications to suddenely and magically change
> > their results. Umm problem.
>
> So, how would you feel about a mechanism whereby the kernel could be
> passed a default FPU control word by the binary (with old binaries, by
>
Alan Cox <[EMAIL PROTECTED]> writes:
>
> You want peoples existing applications to suddenely and magically change
> their results. Umm problem.
So, how would you feel about a mechanism whereby the kernel could be
passed a default FPU control word by the binary (with old binaries, by
default,
Andre
I think We've gone out-of-bounds on this one. None of us are
lawyers, and nobody can predict what is happening. Personally, I do not see
the difference between placing a GUID in the vendor specific are or placing
a GUID in the E0112r1 area. Both places are set aside for people
On Sat, 3 Mar 2001, Philipp Rumpf wrote:
> > Well, from reading the source, I don't see how this can break APM... What am I
> > missing?
>
> apm_bios_call must not be called with two identical pointers for
> two different registers.
>
OK, my bad... By replacing the call I made with this:
i have compaq presario 1245 and kernel 2.4.2 does not do power off on
shutdown although all necessary kernel options are compiled in..
lynx
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
> with GCC's 64-bit doubles (and its 64-bit clean but 80-bit dirty
> floating point optimizations), so I'm proposing adding an instruction
> to "init_fpu()" to change the default hardware control word.
You want peoples existing applications to suddenely and magically change
their results. Umm
> Well, from reading the source, I don't see how this can break APM... What=
> am I
> missing?
If you've stopped kapm-idled from using cpu then you've stopped it from going
into the bios suspend one presumes.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body
> "Noah" == Noah Romer <[EMAIL PROTECTED]> writes:
Noah> In my experience, Tx interrupt mitigation is of little
Noah> benefit. I actually saw a performance increase of ~20% when I
Noah> turned off Tx interrupt mitigation in my driver (could have been
Noah> poor implementation on my part).
"Adam J. Richter" <[EMAIL PROTECTED]> writes:
>
> IEEE-754 floating point is available under glibc-based systems,
> including most current GNU/Linux distributions, by linking with -lieee.
> Your example program produces the "9 10" result you wanted when linked
> this way, even when
On Sun, Mar 04, 2001 at 12:19:07AM +0100, Francis Galiegue wrote:
> Well, from reading the source, I don't see how this can break APM... What am I
> missing?
apm_bios_call must not be called with two identical pointers for
two different registers.
-
To unsubscribe from this list: send the line
On Sat, 3 Mar 2001, Alan Cox wrote:
>
> > As attachment. Don't ask me why it works. Rather, if you see why it works, I'd
> > like to know why :)
>
> Why are you breaking kapm-idled. It is supposed to take all that cpu time. You
> just broke all the power saving
>
Well, from reading the
Hi,
and sorry, no patch.
cantaloupe:~/kernel/linuxppc_2_4 # depmod -Vae
depmod version 2.4.2
depmod: *** Unresolved symbols in /lib/modules/2.4.3-pre1-SMP/kernel/drivers/md/md.o
depmod: md_autodetect_dev
cantaloupe:~/kernel/linuxppc_2_4 # cat /proc/version
Linux version 2.4.3-pre1-SMP
Jason Riedy <[EMAIL PROTECTED]> writes:
>
> Note that getting what some people want to call `true' IEEE 754
> arithmetic on an x86 is frightfully tricky. Changing the precision
> does not shorten the exponent field, and that can have, um, fun
> effects on and around under/overflow.
Whoops.
On Sun, 4 Mar 2001, Francis Galiegue wrote:
>
> As attachment. Don't ask me why it works. Rather, if you see why it works, I'd
> like to know why :)
>
BTW, in case this matters, this is with gcc 2.95.3 compiler...
--
Francis Galiegue, [EMAIL PROTECTED] - Normand et fier de l'être
> As attachment. Don't ask me why it works. Rather, if you see why it works, I'd
> like to know why :)
Why are you breaking kapm-idled. It is supposed to take all that cpu time. You
just broke all the power saving
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the
Here's the Changelog that can be found at
ftp.*.kernel.org/pub/linux/kernel/testing/ChangeLog
I think Linus forgot to send it.
-pre1:
- Chris Mason: reiserfs, another null bytes bug
- Andrea Arkangeli: make SMP Athlon build
- Alexander Zarochentcev: reiserfs directory fsync SMP locking
On Sun, 04 Mar 2001 05:16:37 +1100,
Andrew Morton <[EMAIL PROTECTED]> wrote:
>mkdep has got itself a new feature, but the makefiles haven't
>been updated.
Linus took the change to mkdep.c but missed the associated Makefile and
Rules.Make changes. This patch brings 2.4.3-pre1 up to date with my
As attachment. Don't ask me why it works. Rather, if you see why it works, I'd
like to know why :)
Patch also applies cleanly over 2.4.2-ac10.
--
Francis Galiegue, [EMAIL PROTECTED] - Normand et fier de l'être
"Programming is a race between programmers, who try and make more and more
On Fri, 2 Mar 2001, Richard B. Johnson wrote:
> Note that two subsequent calls to gettimeofday() must not return the
> same time even if your CPU runs infinitely fast. I haven't seen any
> kernel in the past few years that fails this test.
i don't see any requirement for this in SuS.
"Albert D. Cahalan" <[EMAIL PROTECTED]> writes:
> >
> > Well, yes, but I'll try not to cry myself to sleep over it. I'm
> > tempted to say that someone who chooses to use "float"s has given up
> > all pretense of caring about the answers they get. And, if they
> > really want to do predictable
> Is it possible to selectively bridge broadcast traffic in the way I have
> described?
Take a look at how your router handles broadcast dhcp requests cisco at
least have a dhcp helper functionality which is essentially just what
you're asking for (selective forwarding of broadcast traffic.
if
On Sat, Mar 03, 2001 at 10:20:02PM +, Alan Cox wrote:
> > > Also try the techtalk mailing list on linuxchix - www.linuxchix.org, IIRC.
> > > A good place to ask "newbie" questions without being told to RTFM!
> >
> > You might even score!
>
> Of course its attitudes like that which leads
> able to get into kdb from a serial console (an then lost the log - murphy can
> be a real PITA). I figure a ps, bt and bta should be enough to point out
> the problem task? Its there anything else I should do (sr t maybe?)?
That should give you most of the info
-
To unsubscribe from this
> > Also try the techtalk mailing list on linuxchix - www.linuxchix.org, IIRC.
> > A good place to ask "newbie" questions without being told to RTFM!
>
> You might even score!
Of course its attitudes like that which leads them to have to set up their
own mailing lists, and contribute to the
Hi. I was using 2.4.2 without any problems until a
flood of warnings
from multilog (daemontools) appeared at my console.
What I first thought
to be a log problem seems to be serious. For some
reason applications
and daemons (not all) can't find files.
Mutt doesn't recognize ~/Mail/postponed if I
NOTICE to all on LKML: DO NOT REPLY, THIS IS AN FYI-HEADS-UP!
On Sat, 3 Mar 2001, Curtis Stevens wrote:
> ** This is the quasi-official and semi-temporary T13 email list server. **
>
> Andre
>
> One of the things that my proposal attempts to do is remove the
> legal issues
I have forwarded my response to the CPRM people about their lawlessness.
Please do not reply to the T13 Reflector.
Regards,
Andre Hedrick
Linux ATA Development
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More
I tried it but no change. I don't have ACPI messages during the boot... I
don't understand why there is this trouble...
-Message d'origine-
De : [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]De la part de Jason Madden
Envoyé : samedi 3 mars 2001 20:44
À : [EMAIL PROTECTED]
Objet : Re:
} > I don't have a simple way on PPC to cause the interrupt to happen again,
} > as you can imagine this is rather controller-specific. However, looking
} > at the code closely, I couldn't figure out a case where having
} > IRQ_PENDING in enable_irq() makes sense.
}
} It only makes sense for
On Friday 02 March 2001 19:20, you wrote:
> > Should an X crash really freeze my box like a block of ice? Would be
> > nice if linux could just detect an X crash an recover... Is this too
> > much to ask from PC harware?
>
> X pokes hardware, so X is kind of a device driver in part. One slip
On Sat, Mar 03, 2001 at 08:59:27PM +, James A. Sutherland wrote:
> > Another great place to ask questions is on irc, see
> > http://www.kernelnewbies.org
>
> Also try the techtalk mailing list on linuxchix - www.linuxchix.org, IIRC.
> A good place to ask "newbie" questions without being
And "Albert D. Cahalan" writes:
-
- 2. Extra precision when it comes free. The precision control is set
-to 80-bit and the compiler tries to keep values in registers.
-This is usually the more useful behavior, and it performs better.
Even better is for gcc to spill intermediate
On Sat, 3 Mar 2001, bert hubert wrote:
> On Sat, Mar 03, 2001 at 11:52:22AM -0800, Peter Jay Salzman wrote:
>
> > is there a more suitable mailing list for me to sign up for? debian has a
> > mailing list both for package maintainers and those who are trying to learn
> > how to be package
[EMAIL PROTECTED] (Hugh Dickins) wrote on 02.03.01 in
<[EMAIL PROTECTED]>:
> The SuSv2 quotations, above and in other mail, are just weasly.
The next version is less weasly. Right now it's still a draft; what it
says in draft 5 is this (note the markers which show what's optional to
which
On Sat, Mar 03, 2001 at 07:32:13PM +, Alan Cox wrote:
>
> 2.4.2-ac11
> o Add ALi15x3 to the list of isa dma hangs(Angelo Di Filippo)
What does this mean?
Kurt
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL
physmem= `head -10 /var/log/dmesg | grep Memory: | cut -d" " -f2 | cut
-d "/" -f1 | cut -d"k" -f1`
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please
On Sat, 3 Mar 2001, Jon Masters wrote:
> e.g. on desktop a broadcast udp packet (with a specified port) needs to
> go not only to itself and the router but also the "REST OF LAN" part
> too - and vice versa. Removing the router is not an option.
Write an application that creates 2 sockets
On Sat, Mar 03, 2001 at 02:14:18PM -0500, Albert D. Cahalan wrote:
> David G\363mez writes:
>
> > Hi, i've got a newbie question about patches:
> > Are the pre* patches ( and i guess also the ac* ones) applied against the
> > last release of the kernel or against the previous patch? I mean, when
On Sat, 3 Mar 2001, Jens Axboe wrote:
> On Sat, Mar 03 2001, Alexander Viro wrote:
> > > Look for the patch I posted yesterday (hint: just remove these two
> > > lines from loop_end_io_transfer)
> > >
> > >if (atomic_dec_and_test(>lo_pending))
> > >
Kevin Buhr writes:
> "Albert D. Cahalan" <[EMAIL PROTECTED]> writes:
>> So you change it to 2... but what about the "float" type? It gets
>> a mixture of 64-bit and 32-bit IEEE arithmetic depending rather
>> unpredictably on compiler register allocations and optimizations???
>
> Well, yes, but
On Sat, Mar 03, 2001 at 11:52:22AM -0800, Peter Jay Salzman wrote:
> is there a more suitable mailing list for me to sign up for? debian has a
> mailing list both for package maintainers and those who are trying to learn
> how to be package maintainers.
>
> is there a similar thing with the
dear all,
i'm in the process of learning how to write modules. i've read the first 4
chapters of alessandro rubini's o'reilly book "writing linux device drivers".
looking through modern drivers, i see a lot has changed.
for the next few months, i'll prolly have a lot of really newbie
On Sat, Mar 03 2001, Alexander Viro wrote:
> > Look for the patch I posted yesterday (hint: just remove these two
> > lines from loop_end_io_transfer)
> >
> >if (atomic_dec_and_test(>lo_pending))
> >up(>lo_bh_mutex);
>
> Uhh... And what will compensate
> ./drivers/char/i810_rng.c.rej
> ./Makefile.rej
>
> Also, a lot of them suceeded, but with offsets.
Oops it was versus 2.4.3pre1. I'll fix it now
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
Alan Cox wrote:
>
> ftp://ftp.kernel.org/pub/linux/kernel/people/alan/2.4/
>
> 2.4.2-ac11
Doesn't apply cleanly against a 2.4.2 tree...
./mm/slab.c.rej
./net/irda/irnet/irnet.h.rej
./arch/i386/kernel/traps.c.rej
./drivers/net/tulip/tulip.h.rej
./drivers/net/tulip/tulip_core.c.rej
On Fri, 2 Mar 2001, Stéphane GARIN wrote:
> Hi,
>
> I have a kernel panic with the patch 2.2.19pre16 that I test. I use a 2.2.18
> Kernel very well. I used the last patch on this kernel and make my kernel
> with sames parameters without error message. At the boot, I can see this :
>
> ...
>
On Sat, 3 Mar 2001, Jens Axboe wrote:
> On Sat, Mar 03 2001, [EMAIL PROTECTED] wrote:
> >
> > I have an encrypted filesystem mounted over loopback that I created under
> > a 2.2.16 kernel. (Using AES, 128 bit key.) Works fine in 2.2.16. Sort of
> > works under the unpatched 2.4 series.
[cc trimmed]
On Sat, 3 Mar 2001, Alan Cox wrote:
> > Long ago, pre* and ac* patches were rare. Patches went from one
>
> Umm wrong. -ac patches for 2.2 regularly did one a day
>
> > line-by-line before the next one came out. Patches always applied
> > easily with the (pre-POSIX?) patch
On Sat, Mar 03 2001, [EMAIL PROTECTED] wrote:
> take2:~# uname -a
> Linux take2 2.4.2-ac8 #2 Fri Mar 2 14:12:44 EST 2001 i686 unknown
> take2:~# losetup -e aes /dev/loop0 /dev/hda12
> Available keysizes (bits): 128 192 256
> Keysize: 128
> Password :
> take2:~# fsck /dev/loop0
> Parallelizing
ftp://ftp.kernel.org/pub/linux/kernel/people/alan/2.4/
2.4.2-ac11
o Fix NLS Config.in (David Weinehall)
o Sort out one escaped revert from the megaraid (me)
update
o Resync with Linux 2.4.3pre1
| Except tulip the network
On Sat, Mar 03 2001, [EMAIL PROTECTED] wrote:
>
> I have an encrypted filesystem mounted over loopback that I created under
> a 2.2.16 kernel. (Using AES, 128 bit key.) Works fine in 2.2.16. Sort of
> works under the unpatched 2.4 series. (Mounts okay, but hangs the system
> on random blocks.)
>
> Long ago, pre* and ac* patches were rare. Patches went from one
Umm wrong. -ac patches for 2.2 regularly did one a day
> line-by-line before the next one came out. Patches always applied
> easily with the (pre-POSIX?) patch command. Version numbers made
patch is Larry Wall
> Pre-patches go
On 3 Mar 2001, Michael Rothwell wrote:
> pyhsmem = `free | grep Mem | tr -s "/ / /" | cut -f2 -d" "`
% strace free 2>&1 |grep /proc
open("/proc/cpuinfo", O_RDONLY) = 3
open("/proc/uptime", O_RDONLY) = 3
open("/proc/stat", O_RDONLY)= 4
open("/proc/meminfo",
I have an encrypted filesystem mounted over loopback that I created under
a 2.2.16 kernel. (Using AES, 128 bit key.) Works fine in 2.2.16. Sort of
works under the unpatched 2.4 series. (Mounts okay, but hangs the system
on random blocks.)
Under various 2.4 kernels with Jens' patched, the
David G\363mez writes:
> Hi, i've got a newbie question about patches:
> Are the pre* patches ( and i guess also the ac* ones) applied against the
> last release of the kernel or against the previous patch? I mean, when
> 2.4.3pre2 will come out, i need to get also the pre1 patch?
Really, I
On Sat, 3 Mar 2001, Denis Perchine wrote:
> Hello,
>
> actually the question is in subj.
> Problem is that there is a program which needs to know physical memory
> size. This information is used to justify memory consumption as after some
> swapping performance is drops dramatically, and it
Jon Masters wrote:
> Jeremy Jackson wrote:
>
> > try bridging instead if ip forwarding. use netfilter too if you want
>
> I mentioned bridging before - I don't want some kind of transparent
> bridge, really so what I would need is for the router to be contactable
> in the same way as before and
pyhsmem = `free | grep Mem | tr -s "/ / /" | cut -f2 -d" "`
On 03 Mar 2001 13:37:42 -0500, Denis Perchine wrote:
> Hello,
>
> actually the question is in subj.
> Problem is that there is a program which needs to know physical memory
> size. This information is used to justify memory
Marek Michalkiewicz wrote:
>
> > Why is lock_kernel necessary?
>
> Well, it is there in 2.4.2 acquirewdt.c (which this driver is based on -
> really only minimal changes, the hardware is only slightly different).
> I can remove it if you tell me it's really not necessary.
Sounds like it got
On Sat, 3 Mar 2001, David Hinds wrote:
>
> In drivers/pcmcia/cardbus.c in cb_alloc(), PCI_INTERRUPT_LINE and
> dev->irq are not filled in until after calling pci_enable_device().
> The result is a cryptic message like:
>
> > PCI: No IRQ known for interrupt pin A of device 01:00.0. Please try
Hello,
actually the question is in subj.
Problem is that there is a program which needs to know physical memory
size. This information is used to justify memory consumption as after some
swapping performance is drops dramatically, and it is better to finish.
I know that this is not the best
Jeremy Jackson wrote:
> try bridging instead if ip forwarding. use netfilter too if you want
I mentioned bridging before - I don't want some kind of transparent
bridge, really so what I would need is for the router to be contactable
in the same way as before and for regular traffic to pass
mkdep has got itself a new feature, but the makefiles haven't
been updated.
We're getting zero-length .depend files.
I assume something like this was intended:
--- linux-2.4.3-pre1/Makefile Sat Mar 3 20:52:23 2001
+++ linux-akpm/Makefile Sun Mar 4 05:13:01 2001
@@ -440,8 +440,8 @@
Benjamin Herrenschmidt wrote:
...
> The reason why I'm getting this problem on the public place (again ?)
> is that we are now faced with people who want to put video cards in both
> AGP & PCI busses, those cards requiring accesses to some legacy VGA IOs
> on each of their busses.
I don't see
On Sat, 3 Mar 2001, Benjamin Herrenschmidt wrote:
>
> Especially, my question is about the code in enable_irq() which checks
> for IRQ_PENDING, and then
> "replays" the interrupt by asking the APIC to issue it again.
>
> I don't have a simple way on PPC to cause the interrupt to happen
In drivers/pcmcia/cardbus.c in cb_alloc(), PCI_INTERRUPT_LINE and
dev->irq are not filled in until after calling pci_enable_device().
The result is a cryptic message like:
> PCI: No IRQ known for interrupt pin A of device 01:00.0. Please try using
>pci=biosirq.
Unless there is a less obvious
Jon Masters wrote:
> Hello,
> I have a brain-dead application here which relies on broadcast
> traffic for client/server discovery and I have a question with regard
> to forwarding broadcast traffic.
try bridging instead if ip forwarding. use netfilter too if you want
>
>
> A small
Andrew Morton wrote:
>
> 2.4.3-pre1 has been uploaded. The following drivers will
> not work as modules:
>
> ./drivers/net/via-rhine.c
> ./drivers/net/yellowfin.c
> ./drivers/net/epic100.c
> ./drivers/net/8139too.c
> ./drivers/net/rcpci45.c
> ./drivers/net/sundance.c
Bah, life is so much
On Saturday 03 March 2001 12:18 pm, [EMAIL PROTECTED] wrote:
> Hi, i've got a newbie question about patches:
> Are the pre* patches ( and i guess also the ac* ones) applied against the
> last release of the kernel or against the previous patch? I mean, when
> 2.4.3pre2 will come out, i need to
> On Wed, 28 Feb 2001, Alan Cox wrote:
>
> > Umm that sounds like it might be timing. That could be a pain
> Timing-related problems in code using sleep_on(). Film at 11. :)
No
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL
>I/O is not supposed to be fast, that's what MMIO is for. :) Just do
>
>void outb (u8 val, u16 addr)
>{
> void *addr = ioremap (ISA_IO_BASE + addr);
> if (addr) {
> writeb (val, addr);
> iounmap (addr);
> }
>}
>
>You can map and unmap for each call
On Wed, 28 Feb 2001, Alan Cox wrote:
> Umm that sounds like it might be timing. That could be a pain
Timing-related problems in code using sleep_on(). Film at 11. :)
--
dwmw2
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL
> > Looks like you were bitten by either the RAID 1 bugs or the
> > elevator bugs.
> > Try a 2.4.2-pre4 or an 2.4.1-ac18 kernel. Should solve it.
>
> Just installed 2.4.2pre4, seems to be stable for now (testing it
> ATM, running dnetc, several kernel compiles etc.). On 2.4.1 even
> su
On 03 Mar 2001 12:54:36 +0100, Vojtech Pavlik wrote:
> No, they have a separate USB chip, but it has the same PCI ID as the
> builtin silicon in the southbridge.
Ah. I went and looked up that chip ID at via's website, and saw only
southbridge chips, no USB-only chips at all. But, my real
On Sat, Mar 03, 2001 at 12:49:04PM +, Russell King wrote:
> Further more, while do_gettimeofday() is still within the
> read_lock_irqsave, we spin_unlock(_lock) in do_slow_gettimeoffset()
> and _re-enable_ interrupts! This means when we later read xtime, we're
> doing it with interrupts
Hi, i've got a newbie question about patches:
Are the pre* patches ( and i guess also the ac* ones) applied against the
last release of the kernel or against the previous patch? I mean, when
2.4.3pre2 will come out, i need to get also the pre1 patch?
thanks
David Gómez
"The question of
On Fri, 2 Mar 2001 20:32:31 -0300
John R Lenton <[EMAIL PROTECTED]> wrote:
> Is there any particular reason why imsttfb isn't available in the
> i386 arch?
I believe it's because the Twin Turbo was introduced into the kernel via
the PPC kernel port - was there actually a TT board for PCs? I'm
Hello!
> this kernel was compiled with GCC 2.95.2,
This is a hint.
Could you make the following things:
1. to disassemble tcp_poll() (the easiest way is to gdb vmlinux, to
say x/i tcp_poll and to hold enter pressed long enough, copying screen
to file) and to send the result to me.
2.
Em Sat, Mar 03, 2001 at 09:06:30AM -0600, Steven Brooks escreveu:
> When mounting a file using the loopback device, the mount program hangs
> for ever. Other than that, the system is still usable.
>
> Dist: Redhat-7
> Kernel: 2.4.2 (compiled with kgcc, i.e. egcs-2.91.66)
FAQ, try 2.4.2-ac10,
2.4.3-pre1 has been uploaded. The following drivers will
not work as modules:
./drivers/net/via-rhine.c
./drivers/net/yellowfin.c
./drivers/net/epic100.c
./drivers/net/8139too.c
./drivers/net/rcpci45.c
./drivers/net/sundance.c
Two new functions need to be exported:
---
On Sat, Mar 03 2001, Steven Brooks wrote:
> When mounting a file using the loopback device, the mount program hangs
> for ever. Other than that, the system is still usable.
Please read lkml archives before posting, this problem has been
all over the list for the past two weeks.
Use the latest
When mounting a file using the loopback device, the mount program hangs
for ever. Other than that, the system is still usable.
Dist: Redhat-7
Kernel: 2.4.2 (compiled with kgcc, i.e. egcs-2.91.66)
CPU: Pentium II 400
Mem: 128MB RAM + 512MB swap
(More information below)
For me, it is 100%
On Thu, Mar 01, 2001 at 02:38:32PM -0800, Peter J. Braam wrote:
> SnapFS - Snapshot File System
>
> Release: alpha1
> Requires: Linux 2.2.18 or later, Ext3 and EA.
> WWW site: http://www.mountainviewdata.com/technology/snapfs
This sounds really nice!
-
To unsubscribe from this list: send the
> Why is lock_kernel necessary?
Well, it is there in 2.4.2 acquirewdt.c (which this driver is based on -
really only minimal changes, the hardware is only slightly different).
I can remove it if you tell me it's really not necessary.
> > + spin_lock_init(_lock);
> > +
> barn. You will need to request a getnanotimeofday() be created if you
> want to allow two consecutive calls to always return different values
> (modulo SMP systems and ~13 more years of Moore's Law)
Or you use rdtsc instructions for x86. There intel do guarantee that no two
rdtsc's execute in
1 - 100 of 234 matches
Mail list logo
