On Wed, 10 Jan 2001, Christoph Hellwig wrote:
>
> Simple. Because I stated before that I DON'T even want the networking
> to use kiobufs in lower layers. My whole argument is to pass a kiovec
> into the fileop instead of a page, because it makes sense for other
> drivers to use multiple pages
Paul Flinders <[EMAIL PROTECTED]> writes:
> Has anyone got either 2.2.x or 2.4.0 booted on the above motherboard?
I've got an MSI 694D Pro AI mainboard (ie non-raid), and both 2.2.x
and 2.4.0 work flawlessly here. I did manage to build a 2.4.0 kernel
which didn't boot, but it got much further b
On Tue, Jan 09, 2001 at 01:26:44PM -0800, Linus Torvalds wrote:
>
>
> On Tue, 9 Jan 2001, Christoph Hellwig wrote:
> > >
> > > Look at sendfile(). You do NOT have a "bunch" of pages.
> > >
> > > Sendfile() is very much a page-at-a-time thing, and expects the actual IO
> > > layers to do it's o
I've been getting problems all along the pre-2.4 series and 2.4 itself
when I use NFS to play mp3 files with xmms.
The message in the logs is:
tulip.c: outl_CSR6 too many attempts,csr5=0x60208100
After a few times the network stops working and it only recovers with the
following sequence of com
Hi Linus,
Linus Torvalds <[EMAIL PROTECTED]> writes:
> I'd really like an opinion on whether this is truly legal or not? After
> all, it does change the behaviour to mean "pages are locked only if they
> have been mapped into virtual memory". Which is not what it used to mean.
>
> Arguably the
Hi,
I don't know if it's possible to make fd a read-only device if the
inserted media is write-protected, but I had a strange problem:
I had inserted a write protected floppy and accessed it via autofs as
vfat in 2.2.18. It worked. Some time later it had expired (and I'm not
sure whether I ha
Hello,
I have some issues on Linux-2.4.0:
During boot the (slightly modified, see later) kernel says:
<4>Linux version 2.4.0-NANO (root@elf) (gcc version 2.95.2 19991024 (release)) #1 Mon
Jan 8
22:04:48 MET 2001
[...]
<4>PCI: PCI BIOS revision 2.10 entry at 0xfb280, last bus=1
<4>PCI: Using c
On Wed, 10 Jan 2001, Andrea Arcangeli wrote:
> On Tue, Jan 09, 2001 at 01:31:35PM -0800, Linus Torvalds wrote:
> > don't have to worry about undocumented extensions etc.
>
> Infact I don't blame gcc maintainers for that, but the standard. Ok, minor
> issue.
Yeah, and nothing we can do about i
On Wed, 10 Jan 2001, David Woodhouse wrote:
>
> How does this affect embedded systems with no swap space at all?
The no-swap behaviour shoul dactually be pretty much identical, simply
because both 2.2 and 2.4 will do the same thing: just skip dirty pages in
the page tables because they cannot
Anyone tried using these beasts on a x86?
Anyway, what's happening: In BIOS my USB keyboard works really poorly -
it almost seems scancodes get dropped left and right. Ok, so I don't mind
too much, i'm sure BIOS has a very limited driver. After booting
Microsoft's offerring, it would work fin
No oops maybe, BUT if you setup an evil script to make so many that the various kernel
structures got too full (or it filled the whole partition/disk up) then
And at 650Mhz my computer could do that quite easily...
DL
-
To unsubscribe from this list: send the line "unsubscribe linux-kerne
On Wed, Jan 10, 2001 at 12:42:01AM +0100, Marc Lehmann wrote:
>
> Basically, you do:
>
> mkdir "$(perl -e 'print "x" x 768')"
[jaqque@osiris:/tmp/chk]% uname -a
Linux osiris 2.2.18 [classified] Sat Jan 6 11:19:04 PST 2001 i586 unknown
[jaqque@osiris:/tmp/chk]% mkdir "$(perl -e 'prin
On Tue, 9 Jan 2001, Chris Mason wrote:
>
>
> On Wednesday, January 10, 2001 02:32:09 AM +0100 Marc Lehmann <[EMAIL PROTECTED]> wrote:
>
> >>> EIP; c013f911<=
> > Trace; c013f706
> > Trace; c0136e01
>
> The buffer reiserfs is sending to filldir is big enough for
> the huge file nam
Archan Paul rearranged electrons thusly:
> I faced the same problem when I patched 2.4.0test7 with reiserFS
> support. On my further correspondence with Alan Cox, he wrote that he is
> unwilling to listen about any "bug report for 2.4kernel", arising after
> patching kernel with some foreign code
I faced the same problem when I patched 2.4.0test7 with reiserFS
support. On my further correspondence with Alan Cox, he wrote that he is
unwilling to listen about any "bug report for 2.4kernel", arising after
patching kernel with some foreign code...
Any comments?
Archan Paul
[EMAIL PROTECTED]
This is valid that Paul is maintaining that subdriver as GADI is doing a
StartUp in Video stuff.
Cheers,
On Tue, 9 Jan 2001, Paul Bristow wrote:
> Linus, Alan,
>
> Could you please apply this patch to the MAINTAINERS file so that the
> 2.4.x
> IDE-FLOPPY maintainer is correctly identified as
Please name a time or event when you would cal a setfeaturers command
without having a IDENTIFY page filled?
On Tue, 9 Jan 2001, Arnaldo Carvalho de Melo wrote:
> Hi,
>
> Please consider applying.
>
> - Arnaldo
>
> --- linux-2.4.0-ac4/drivers/ide/ide-features.cMon Jan 8 20:3
On Wed, 10 Jan 2001, Alan Cox wrote:
> > The Mesa package in Red Hat 7 won't do DRI with recent XFree86 CVS.
>
> Yep. Its Mesa 3.3/DRI 1.0. XFree86 CVS is Mesa 3.4/DRI 2.0. That has several
> advantages including mostly working on Matrox cards which 1.0 never did (for
> me anyway) and handling
linux-2.4.1-pre1/drivers/md/xor.c calls the macro XOR_TRY_TEMPLATES,
which is defined in include/asm-i386/xor.h to use HAVE_XMM, which is
defined in include/asm-i386/processor.h to reference mmu_cr4_features.
So, to support compilation of raid5 as a module, i386_ksyms.c needs
to export mm
- Begin Hush Signed Message from [EMAIL PROTECTED] -
hello.
i just compiled a 2.4.0 kernel from stable sources from ftp.us.kernel.org,
including reiserfs support from the reiserfs patch (www.namesys.com) .
anyway, i compiled the ramfs (resizeable ramdisk) feature as a module, loaded
the
Why not use the limits from instead?
-d
Chris Mason wrote:
> On Wednesday, January 10, 2001 02:32:09 AM +0100 Marc Lehmann <[EMAIL PROTECTED]> wrote:
>
> >>> EIP; c013f911<=
> > Trace; c013f706
> > Trace; c0136e01
>
> The buffer reiserfs is sending to filldir is big enough for
> the
> The Mesa package in Red Hat 7 won't do DRI with recent XFree86 CVS.
Yep. Its Mesa 3.3/DRI 1.0. XFree86 CVS is Mesa 3.4/DRI 2.0. That has several
advantages including mostly working on Matrox cards which 1.0 never did (for
me anyway) and handling things that Mesa 3.3 tried to allocate the odd g
On Monday January 1, [EMAIL PROTECTED] wrote:
> On Thu, Dec 21, 2000 at 12:05:41PM +1100, Neil Brown wrote:
> > So, I have started putting some patches together and they can be
> > found at
> > http://www.cse.unsw.edu.au/~neilb/patches/knfsd-2.2/
>
> I included the interesting ones in my tr
The Mesa package in Red Hat 7 won't do DRI with recent XFree86 CVS.
Michael is quite right in saying he needed to blow it away. The only
way I could get DRI working until recently was to transplant a copy
of libGL.so from the XFree86 build tree into /usr/lib, delete or rename
the Mesa package ver
I haven't tracked the IP storage group too closely, but was at the San Diego IETF
where there were some interesting debates about this issue.
There is a write-up at http://ips.pdl.cs.cmu.edu/mail/msg02598.html
Now I'm not sure if I agree with some of the assumptions. And I share your concern
a
Rik van Riel wrote:
> On Sun, 7 Jan 2001, John O'Donnell wrote:
>
> > Only on my company's e-mail server. My company typically gets "zero"
> > emails from outside the US. If I get a piece of spam (sorry they are
> > typically from outside the US), I just block the entire .com.br domain.
> > I g
Okay, the sleep situation has not improved. I'll admit that right now.
But it's ABOUT to. G'night...
Rob
On Mon, 8 Jan 2001, Rob Landley wrote:
>
> So fork ramfs already. Copy the snapshot you like as an educational
> tool, call it skeletonfs.c or some such, and let the current code evol
He replied to my bad cc:, so forwarding this here should be okay...
Linus Torvalds wrote:
>
> On Mon, 8 Jan 2001, Rob Landley wrote:
> >
> > So fork ramfs already. Copy the snapshot you like as an educational
> > tool, call it skeletonfs.c or some such, and let the current code evolve
> > into
(Argh! Linus replies to my post and my cc: to the linux-kernel was to
rutgers.edu. Teach me to post on three hours of sleep, it's like
getting a hole-in-one with nobody around...)
Linus said in Re: Patch (repost): cramfs memory corruption fix
> I wonder what to do about this - the limits are o
Robert Kaiser wrote:
>
> Hi list,
>
> I can't seem to get the new 2.4.0 kernel running on a 386 CPU.
> The kernel was built for a 386 Processor, Math emulation has been enabled.
> I tried three different 386 boards. Execution seems to get as far as
> pagetable_init() in arch/i386/mm/init.c, then
On Tue, 09 Jan 2001 19:27:24 -0800,
Allen Unueco <[EMAIL PROTECTED]> wrote:
>Also where did get_module_symbol() and put_module_symbol() go?
http://www.mail-archive.com/linux-kernel@vger.kernel.org/msg08791.html
http://www.mail-archive.com/linux-kernel@vger.kernel.org/msg11497.html
-
To unsubscr
Incompatibility with "Sarotech FHD-352F/U Rev 1.0"
Using an external IDE drive in the Sarotech FireWire enclosure fails, even
though the Sarotech unit works with Win2K and other SBP2 drives work for me
(with Linux).
I'm using 2.4.0 together with sbp2_1394_122300.tar.gz.
ACK code 3 is not even me
Hi,
the new version ,
1. add inherit option when config file acls
2. add exec_domain from lids 0.9.11
3. add configuration support to multi-platform
4. bugfixed from 0.9.11
LIDS is a kernel patch and admin tools to enhance the current linux kernel
security.
For more information, pls visit ww
Date: Tue, 9 Jan 2001 19:18:53 -0800 (PST)
From: dean gaudet <[EMAIL PROTECTED]>
- NIC DMAs packet to memory
- CPU reads headers from memory, figures out it's NFS
- CPU copies data bytes from packet image in memory to pagecache
Yes, this is precisely what happens in the NFS client
Sometime around test10 or test11 unmap left vm_operations_struct. The
comment implies its there but it's gone. Where did it go?
How do I get a call back for a page unmap?
I ran into this while hacking the Nvidia kernel driver to work with
2.4.0. I got the driver working but it's not 100%
Al
On Tue, 9 Jan 2001, David S. Miller wrote:
>Date: Tue, 9 Jan 2001 18:56:33 -0800 (PST)
>From: dean gaudet <[EMAIL PROTECTED]>
>
>is NFS receive single copy today?
>
> With the zerocopy patches, NFS client receive is "single cpu copy" if
> that's what you mean.
yeah sorry, i meant:
-
Date: Tue, 9 Jan 2001 18:56:33 -0800 (PST)
From: dean gaudet <[EMAIL PROTECTED]>
is NFS receive single copy today?
With the zerocopy patches, NFS client receive is "single cpu copy" if
that's what you mean.
Later,
David S. Miller
[EMAIL PROTECTED]
-
To unsubscribe from this list: send
> fixed length headers). i've never investigated the actual protocols
> though so maybe the solution used was to just push a lot of the detail
> down into the controllers.
The stuff I have access to (MPT fusion) pushes the FC handling down onto the
board. Basically you talk scsi and IP to it (Se
On Tue, 9 Jan 2001, Ingo Molnar wrote:
> On Mon, 8 Jan 2001, Rik van Riel wrote:
>
> > Having proper kiobuf support would make it possible to, for example,
> > do zerocopy network->disk data transfers and lots of other things.
>
> i used to think that this is useful, but these days it isnt.
this
On Wednesday, January 10, 2001 02:32:09 AM +0100 Marc Lehmann <[EMAIL PROTECTED]> wrote:
>>> EIP; c013f911<=
> Trace; c013f706
> Trace; c0136e01
>
Here is a patch against our 2.4 code (3.6.25) that does the
same as the patch posted for 3.5.29:
-chris
--- linux/include/linux/reiserf
[Mike van Smoorenburg]
> Also calling kwhich with multiple arguments was actually the idea
> behind the script.
Yes, and that's why my optimization patch (in 2.2.19pre3, since
reverted) broke -- it relied on multiple arguments.
Alan, could you put it back in now?
Peter
--- 2.2.19-7/Makefile~
On Wed, Jan 10, 2001 at 01:45:47AM +, David Woodhouse wrote:
> How does this affect embedded systems with no swap space at all?
If there's no swap the swap-cache dirty-sticky issue can't arise.
Andrea
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a
On Wednesday, January 10, 2001 02:32:09 AM +0100 Marc Lehmann <[EMAIL PROTECTED]> wrote:
>>> EIP; c013f911<=
> Trace; c013f706
> Trace; c0136e01
The buffer reiserfs is sending to filldir is big enough for
the huge file name, so I think the real fix should be done in VFSland.
But, in
On Tue, Jan 09, 2001 at 01:31:35PM -0800, Linus Torvalds wrote:
> don't have to worry about undocumented extensions etc.
Infact I don't blame gcc maintainers for that, but the standard. Ok, minor
issue.
Andrea
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body
On Tue, 9 Jan 2001, David S. Miller wrote:
> Ignore Ingo's comments about the MSG_NOCOPY flag, I've not included
> those parts in the zerocopy patches as they are very controversial
> and require some VM layer support.
Okay, I talked to some kernel engineers where I work and they were (I
think)
On 9 Jan 2001, at 10:51, Linus Torvalds wrote:
>
>
> On Tue, 9 Jan 2001, Albert D. Cahalan wrote:
>
> > [about labels w/o statements after them]
> >
> > >> Is this really a kernel bug? This is common idiom in C, so
gcc
> > >> shouldn't warn about it. If it does, it is a bug in gcc IMHO.
> >
Hi Rob,
Just out of curiosity, did you use a 2.2 series
.config file and then run make oldconfig or did
you build a new .config file from scratch?
I have periodically built kernels that crashed
immediately at the point you mention. Usually this
was due to me choose configuration options that
we
We have two Netfinity (7100 with 4 Xeon and 4500R with two PIII) and we
have noticed a weird behaviour with kernel 2.4.0 test and final.
*On the 7100, the final kernel can't detect two pci card (3C980 and
ForeRunnerLE.
*On the 4500R, the test kernel crash unexpectedly in two or three hours
And w
On Tue, 9 Jan 2001, Linus Torvalds wrote:
> And this _is_ a downside, there's no question about it. There's the worry
> about the potential loss of locality, but there's also the fact that you
> effectively need a bigger swap partition with 2.4.x - never mind that
> large portions of the allocati
"Christopher E. Brown" wrote:
>
> Think VLANing switch clusters. Say 4 switches connected by
> GigE on 4 floors or in 4 separate building. Now, across these
> switches 20 VLANS are running, with the switches enforcing VLAN
> partitioning. The client PCs know nothing about it, as each
On Tue, Jan 09, 2001 at 03:53:02PM -0500, Douglas Gilbert wrote:
> by timeouts ** resulting in scsi bus resets. Anyway the problem
> seems to disappear with the recently released SANE 1.0.4 .
> [The original report was based on SANE 1.0.3 and earlier.]
In fact my report that the problem went awa
On Tue, 9 Jan 2001, Arnaldo Carvalho de Melo wrote:
> --- linux-2.4.0-ac4/drivers/char/n_r3964.cTue Dec 19 11:25:34 2000
> +++ linux-2.4.0-ac4.acme/drivers/char/n_r3964.c Tue Jan 9 14:23:07 2001
> + restore_flags(flags);
/me scratches head...
Err is there any reason
On Wed, Jan 10, 2001 at 02:17:35AM +0100, Ingo Molnar wrote:
> i understand now - well, there is no reliable RAID1/RAID5 support in the
> stock 2.2 kernel indeed, you need the 0.90 patch.
I used raid1 without problems in stock 2.2 kernel. For raid5 I certainly
agree ;).
Andrea
-
To unsubscribe f
Date: Tue, 09 Jan 2001 20:23:17 -0500
From: Jeff Garzik <[EMAIL PROTECTED]>
Is there any value to supporting fragments in a driver which
doesn't do hardware checksumming? IIRC Alexey had a patch to do
such for Tulip, but I don't see it in the above patchset.
I'm actually consider
-
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/
Date:Tue, 9 Jan 2001 17:14:33 -0800 (PST)
From: Dave Zarzycki <[EMAIL PROTECTED]>
On Tue, 9 Jan 2001, Ingo Molnar wrote:
> then you'll love the zerocopy patch :-) Just use sendfile() or specify
> MSG_NOCOPY to sendmsg(), and you'll see effective memory-to-card
> DMA-and
"David S. Miller" wrote:
>
> Nothing interesting or new, just merges up with the latest 2.4.1-pre1
> patch from Linus.
>
> ftp.kernel.org:/pub/linux/kernel/people/davem/zerocopy-2.4.1p1-1.diff.gz
>
> I haven't had any reports from anyone, which must mean that it is
> working perfectly fine and
On Tue, 9 Jan 2001, Dave Zarzycki wrote:
> In user space, how do you know when its safe to reuse the buffer that
> was handed to sendmsg() with the MSG_NOCOPY flag? Or does sendmsg()
> with that flag block until the buffer isn't needed by the kernel any
> more? If it does block, doesn't that def
On Wed, 10 Jan 2001 10:27:44 +1100,
Eyal Lebedinsky <[EMAIL PROTECTED]> wrote:
>My 'make dep' fails in the following way. This is on Debian 2.2, I
>commented
>if [ -n "amigamouse.c atarimouse.c atixlmouse.c baycom.c busmouse.c
>cd1865.h conmakehash.c console.c console_struct.h consolemap.c
>conso
On Wed, 10 Jan 2001, Andrea Arcangeli wrote:
> > [ the only category impacted are people who are still using the
> > RAID1/RAID4,5 code in the stock 2.2 kernel - i do believe the number of
>
> That's the category Hubert was talking about indeed.
i unde
On Tue, 9 Jan 2001, Ingo Molnar wrote:
> then you'll love the zerocopy patch :-) Just use sendfile() or specify
> MSG_NOCOPY to sendmsg(), and you'll see effective memory-to-card
> DMA-and-checksumming on cards that support it.
I'm confused.
In user space, how do you know when its safe to reuse
Nothing interesting or new, just merges up with the latest 2.4.1-pre1
patch from Linus.
ftp.kernel.org:/pub/linux/kernel/people/davem/zerocopy-2.4.1p1-1.diff.gz
I haven't had any reports from anyone, which must mean that it is
working perfectly fine and adds no new bugs, testers are thus in
nir
Hi,
I am the linux developer for this card. This is the problem we have fixed
long back and the version of linux driver that comes with 2.4.0 is way too
old. A new driver will be released in a weeks time.
Thanks
Venkat
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
t
> On Tue, 9 Jan 2001, Hubert Mantel wrote:
> > Right, but now there is a problem: Software RAID. The RAID code of
> > 2.4.0 is not backwards compatible to the one in 2.2.18; if somebody
> > has used 2.4.0 on softraid and discovers some problem, he can not
> > switch back to some official 2.2 kerne
Hi
Marc Lehmann wrote:
> We are still investigating, but there seems to be a major security problem
> in at least some versions of reiserfs. Since reiserfs is shipped with
> newer versions of SuSE Linux and the problem is too easy to reproduce and
> VERY dangerous I think alerting people to this
Hi,
Konqueror behaves really strange with the new kernel (compiled with 2.95.2 as
all my kernels for a very long time)
I have not seen this behaviour (to this extent) with earlier 2.4 kernels.
Included a strace... strange use of brk - or? [included /proc/pid/maps too]
It bugs out like this for
Hi,
On sparc the length of an xor block must be a multiple of 128 bytes.
Bad things happen otherwise.
Anton
Index: xor.c
===
RCS file: /cvs/linux/drivers/md/xor.c,v
retrieving revision 1.3
diff -u -r1.3 xor.c
--- xor.c 2000/
On Wednesday, January 10, 2001 12:42:01 AM +0100 Marc Lehmann
<[EMAIL PROTECTED]> wrote:
> We are still investigating, but there seems to be a major security problem
> in at least some versions of reiserfs. Since reiserfs is shipped with
> newer versions of SuSE Linux and the problem is too eas
I can't reproduce this.
[root@vaio /root]# mkdir "$(perl -e 'print "x" x 768')"
[root@vaio /root]# ls
> is this part of 2.2.19pre7 really a good idea? Even in 2.4.0 the size
> field is still a short.
It needs to change in 2.4 as well. The cast of data to a struct isnt portable
to all architectures.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message
Hi,
is this part of 2.2.19pre7 really a good idea? Even in 2.4.0 the size
field is still a short.
-o)
Hubert Mantel Goodbye, dots... /\\
On Tue, 9 Jan 2001, Tony Sumner wrote:
>I have a problem with ftape. What happened was that I had a backup on
>QIC80 tape that I made from Red Hat 5.2 and I (foolishly?) installed
>SuSE 7.0. I then found I could not read the tape with the newer version
>of ftape.
>...
>Kernel version: was 2.0.36
On Tue, 9 Jan 2001, Hubert Mantel wrote:
> Right, but now there is a problem: Software RAID. The RAID code of
> 2.4.0 is not backwards compatible to the one in 2.2.18; if somebody
> has used 2.4.0 on softraid and discovers some problem, he can not
> switch back to some official 2.2 kernel. [...]
Checking for the return value of I/O allocation is reversed.
Patch against 2.4.0 follows. Definitely 2.4.1 material !!
--- linux/drivers/scsi/megaraid.c.orig Wed Dec 6 14:06:18 2000
+++ linux/drivers/scsi/megaraid.c Tue Jan 9 18:09:34 2001
@@ -1527,7 +1527,7 @@
megaCtlrs[numCtlrs+
On Mon, 8 Jan 2001, Taner Halicioglu wrote:
>I probably missed a message or note or something about this, but when I went
>from 2.2.17 to 2.2.18, my sound card (SB Live!) stopped working. It seems
>that in 2.2.18, it gets detected TWICE:
>
>
>kernel: Linux version
On Wed, Jan 10, 2001 at 01:07:55AM +0100, Sasi Peter wrote:
> I thought it over again. I still have to say it is a nonsense for a kernel
> not to have _anything_ (zero pages) currently unused swapped out under
> such an I/O load!
Could you generate some furhter memory pressure to see what happen
you should also try to access the mem_map variable directly, in some
simple way. Could you print out the value of mem_map btw.? [This should
rule out any compiler interaction.]
Ingo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EM
On Mon, Jan 08, 2001 at 04:37:32PM -0800, J Sloan wrote:
> Ragnar Hojland Espinosa wrote:
> > Well, the real problem is that (at least Voodoo3) DRI didn't work _before_
> > with the "latest" test and pre kernels, and X < 4.0.2 (unless there was some
> > combination I didn't manage to find) even if
On Wed, 10 Jan 2001, Robert Kaiser wrote:
> Sorry, no ext2fs in this kernel (it is for a diskless embedded
> system). I seem to recall though that the problem at one point
> magically went away when I disabled the FPU emulation, but I have not
> been able to reproduce this recently, so I'm not s
On Mon, Jan 08, 2001 at 10:45:09PM +, Michael D. Crawford wrote:
> glxinfo says dri is not available if I remove the library as I did. So I
> rebuilt Mesa and reinstalled it. The full output of glxinfo on my machine
> follows. Note that it says "direct rendering: Yes" but the version string
On Wed, 10 Jan 2001, Robert Kaiser wrote:
> I have put a "halting statement" (i.e. "while(1);") after my printouts
> to make sure execution does not go any further than that point. I
> moved this halting statement ahead in the code line by line until the
> crash would occur again. So, yes, I am p
Compiling kernel/ksyms.c:
ksyms.c:209: warning: type defaults to `int' in declaration of `EXPORT_SYKBOL'
ksyms.c:209: warning: parameter names (without types) in function declaration
ksyms.c:209: warning: data definition has no type or storage class
patch-2.4.0-ac4.gz, line 195029:
EXPORT_SYMB
On Tue, 9 Jan 2001, Sasi Peter wrote:
> On Tue, 9 Jan 2001, Andrea Arcangeli wrote:
> > On Mon, Jan 08, 2001 at 10:46:29PM +0100, Sasi Peter wrote:
> > > What I had w/2.2.18pre19 (+raid+ide):
> > > ~80MB more in cache and ~80MB swapped out (eg. currently unused notes
> > > server and squid) There
"Alan Cox wrote:"
> Doesnt seem very wild to me, but something did go back 3uS which would imply
> the CPU tsc's are not synched. 2.2 doesnt like that, Boot with 'notsc' and
> repeat the experiment
No change with that, as you already know. But I just noticed that the
ekernel was compiled for i38
On Die, 09 Jan 2001 you wrote:
> On Tue, 9 Jan 2001, Robert Kaiser wrote:
>
> > Now comes the amazing (to me) part: I split the above statement up into:
> >
> > temp = mk_pte_phys(__pa(vaddr), PAGE_KERNEL);
> > *pte = temp;
>
> this is almost impossible (except some really weird compiler
On Wed, 10 Jan 2001, Jakob Østergaard wrote:
>
> Besides, most people using Software RAID have been using 0.90 for
> at least two years - so I doubt this would have been much of a problem
> if the 0.90 patches weren't available for 2.2, which they are.
This is probably th eimportant part. Most
On Tue, Jan 09, 2001 at 09:10:24PM +0100, Ingo Molnar wrote:
>
> On Tue, 9 Jan 2001, Andrea Arcangeli wrote:
>
> > BTW, I noticed what is left in blk-13B seems to be my work (Jens's
> > fixes for merging when the I/O queue is full are just been integrated
> > in test1x). [...]
>
> it was Jens'
Hi,
This patch makes the mpu401_synth_operations structure respect
attach_mpu401()'s "owner" parameter. This should prevent more sound
module from being accidentally unloaded.
Cheers,
Chris
--- linux-vanilla/drivers/sound/mpu401.cFri Jan 5 23:14:08 2001
+++ linux-2.4.0-ac3/drivers/sou
On Tue, 9 Jan 2001, Benjamin C.R. LaHaise wrote:
> On Tue, 9 Jan 2001, Linus Torvalds wrote:
>
> > The _lower-level_ stuff (ie TCP and the drivers) want the "array of
> > tuples", and again, they do NOT want an array of pages, because if
> > somebody does two sendfile() calls that fit in one p
On Wed, Jan 10, 2001 at 12:34:35AM +0100, Jens Axboe wrote:
> Ah I see. It would be nice to base the QUEUE_NR_REQUEST on something else
> than a static number. For example, 3000 per queue translates into 281Kb
> of request slots per queue. On a typical system with a floppy, hard drive,
> and CD-RO
On Tue, Jan 09, 2001 at 02:54:44PM +, Alan Cox wrote:
> > some official 2.2 kernel. In order to make it possible to switch between
> > kernel releases, every vendor now really is forced to integrate the new
> > RAID0.90 code to their 2.2 kernel. IMHO this code should be integrated to
> > the n
On Mit, 10 Jan 2001 you wrote:
> How big is the kernel image? Are you making a zImage or bzImage?
>
I'm using bzImage. It's size is 566964 bytes.
According to System.map, Symbol _end is 0xc0252cf0. That would mean
the uncompressed kernel size would be 1387760 bytes (0xc0252cf0-0xc010),
righ
From: Igmar Palsenberg <[EMAIL PROTECTED]>
> > 2.2.18 sometimes sees 61 GB, sometimes 32 GB.
> > I don't call that hard to understand.
>
> The same kernel has varying behaviour?
> Maybe not hard to understand, but rather surprising.
> You are the first to report nonde
What kind of USB host controller is it?
Maybe there are some issues with it.
Maybe 'lspci -vv'...
~Randy
___
|randy.dunlap_at_intel.com503-677-5408|
---
> From: Adam Huffman [mailto:[EMAIL PROTECTED]
We are still investigating, but there seems to be a major security problem
in at least some versions of reiserfs. Since reiserfs is shipped with
newer versions of SuSE Linux and the problem is too easy to reproduce and
VERY dangerous I think alerting people to this problem is in order.
We have te
On Tue, 9 Jan 2001, Szabolcs Szakacsits wrote:
> Wayne, the patch below should fix your barrier problem [1 GB physical
> memory configuration].
First, I just wanted to thank you and everyone else (Linus, Andrea, Dan
Maas, Rik and others) who has responded to my emails. You guys are
wonderful!
Version 6.08BETA of the Adaptec sponsored and supported AIC7XXX
dirver is now available. Patches against 2.4.0 and 2.2.18 are
provided here:
http://people.FreeBSD.org/~gibbs/linux/
If you are using hardware supported by the aic7xxx driver,
I would appreciate feedback on the new driver.
Changel
On Wed, 10 Jan 2001 [EMAIL PROTECTED] wrote:
> >> dd: advancing past 1 blocks in output file `/dev/fd0': Permission denied
>
> > dd bug. It tries to ftruncate() the output file and gets all upset when
> > kernel refuses to truncate a block device (surprise, surprise).
>
> Yes. But EPERM means
On Wed, Jan 10 2001, Andrea Arcangeli wrote:
> On Tue, Jan 09, 2001 at 09:12:04PM +0100, Jens Axboe wrote:
> > I haven't heard anything beyond the raised QUEUE_NR_REQUEST, so I'd like to
> > see what you have pending so we can merge :-). The tiotest seek increase was
> > mainly due to the elevator
System is a KA7-100, sole USB peripheral is a Logitech MouseMan Wheel.
If I use the uhci driver, it doesn't initialise properly (there is a
message along the lines of "something bad happened". If I use the
usb-uhci driver, I frequently get an oops if I move the mouse during
bootup.
If anyone i
1 - 100 of 367 matches
Mail list logo
