In article <[EMAIL PROTECTED]> you wrote:
> Alan,
> I think adding a document about MCE in the kernel would be very useful.
> Or at least a pointer to Intel's documentation about it.
and something like this:
"This means that your CPU indicates that it is defective"
as a printk
Hi,
I can compile and successfully boot test9-pre7 but
/lib/modules/2.4.0-test9/kernel/drivers/sound/sb.o returns:
init_module: No such device.
Works fine under test6, and it oopsed under test7, test8 and test9-pre1
through to pre4.
Cheers,
Sheldon.
-
To unsubscribe from this list: send the
[EMAIL PROTECTED] wrote
I doubt this has any relevance whatsoever, but when I try this on
a 2.2.16
kernel running on top of a Pentium Pro 200 w/96megs of mem w/ a
SCSI 2
disk, I get some funny numbers:
matt@zeus:~/cwork/personal$ ./elv_test 8 30
files created, 240 megs written at 4.32 megs/sec
A few extra notes:
- Several places use long (or unsigned long) formats for the result of
ntohl(), this is a 32-bit quantity. Makes no difference on ia32, but could
bite on Alpha (an int is 32, a long is 64 there)
- There are several headers for NFS:
include/linux/nfs.h
On Tuesday September 19, [EMAIL PROTECTED] wrote:
> Problem:
>
> The md driver doesn't handle large physical blocks in 2.2.x
>
...
>
> A quick look at the 2.4pre code shows that this has been addressed so I
> have taken a crack at adding a few similar lines of code to md.c in
> order to get
Erik Andersen <[EMAIL PROTECTED]> said:
[...]
> Another approach would be to let user space turn off overcommit.
> That way, user space can be assured there will be no surprises...
I'd call emacs consistently not being able to start an ls on a 16Mb machine
much worse than a surprise...
Sep 26 23:17:11 tacorp kernel: invalid operand:
Sep 26 23:17:11 tacorp kernel: CPU:1
Sep 26 23:17:11 tacorp kernel: EIP:0010:[__find_get_page+7/300]
Sep 26 23:17:11 tacorp kernel: EFLAGS: 00010286
Sep 26 23:17:11 tacorp kernel: eax: c148a3a0 ebx: c01273ec
ecx: 0010 edx:
On Sun, Sep 24, 2000 at 08:27:36PM -0400, Shawn Starr wrote:
>
> Unfortunately. I hope some of those key developers see this is a time to
> "Let's fix our security problems". Ie, GNOME, etc...
Think their view is mainly, "This is to be used on a desktop system, let's rely
on security
Hi,
Please apply.
- Arnaldo
--- linux-2.4.0-test9-7/drivers/sound/esssolo1.cMon Sep 25 23:31:33 2000
+++ linux-2.4.0-test9-7.acme/drivers/sound/esssolo1.c Tue Sep 26 22:01:17 2000
@@ -2085,12 +2085,11 @@
return -ERESTARTSYS;
Hi !
Is any arch other than PPC using include/linux/openpic.h ?
I'm doing some cleanup work on various parts of the PPC arch, and it's
now time for the openpic driver to suffer. That file exports to everybody
all the functions & data structures of the driver, which is wrong with
the way the
Hi,
Please apply.
- Arnaldo
--- linux-2.4.0-test9-7/drivers/sound/cmpci.c Mon Sep 25 23:31:31 2000
+++ linux-2.4.0-test9-7.acme/drivers/sound/cmpci.c Tue Sep 26 21:54:13 2000
@@ -2370,28 +2370,25 @@
continue;
s->irq
Riley Williams <[EMAIL PROTECTED]> said:
[...]
> > I've run heaps of CPU intensive stuff with Win 95
> > since then, like Longbow II, with no crashes at all.
I've got a P/100 which works fine with WinNT 4.0 at /120, Linux won't
finish booting on it at that speed...
--
Horst von Brand
Hi,
Please apply.
- Arnaldo
--- linux-2.4.0-test9-7/drivers/sound/aedsp16.c Thu Aug 24 07:40:05 2000
+++ linux-2.4.0-test9-7.acme/drivers/sound/aedsp16.cTue Sep 26 21:46:35 2000
@@ -241,6 +241,9 @@
- Module informations added.
- Removed
Hi Folks,
Sorry if already known.
Here is oops I've got on test9-pre7.
Not sure what triggered this. As usual when I install new test kernel I do
silly simple stress stuff :
hdparm -t /dev/sdaX or /dev/hdaX (couple of times)
memspeed 150(megs) 10(times) (swaper and mem stress)
Andrew McNabb wrote:
> I'm running 2.2.16 and I have the same problem with my Maestro 2e.
> > Every second playback using maestro produces bad quality output. I'm using
> > splay and -test8. Also sound quality degrades _after_ dropout caused by
> > slow disk. Any ideas how to fix that?
Ok, I'll
On Tue, 26 Sep 2000, Alexander Viro wrote:
> On Tue, 26 Sep 2000, Andreas Dilger wrote:
>
> > Al Viro writes:
> > > Folks, give it a try - just keep decent backups. Similar code will
> > > have to go into UFS in 2.4 and that (ext2) variant may be of interest for
> > > 2.4./2.5. timeframe.
>
On Mon, Sep 25, 2000 at 04:00:51PM +0200, Jens Axboe wrote:
> On Mon, Sep 25 2000, Robert Cohen wrote:
> > With kernel version 2.4.0-test9pre6 the results are as follows.
> > The test machine has 128 Megs of memory. The tests accesses 240 Megs of
> > files so that it can't fit in cache.
> >
> >
On Tue, 26 Sep 2000, Andreas Dilger wrote:
> Al Viro writes:
> > Folks, give it a try - just keep decent backups. Similar code will
> > have to go into UFS in 2.4 and that (ext2) variant may be of interest for
> > 2.4./2.5. timeframe.
>
> Haven't tested it yet, but just reading over the
Hi,
Please consider applying. There are more cases of check_region usage in
the sound drivers, as well as some drivers not using request_region at all for
some areas, I'll be sending more patches if you don't see any problems with
doing this now (well, this is one of the things on Ted's
Al Viro writes:
> Folks, give it a try - just keep decent backups. Similar code will
> have to go into UFS in 2.4 and that (ext2) variant may be of interest for
> 2.4./2.5. timeframe.
Haven't tested it yet, but just reading over the patch - in ext2_lookup():
if (dentry->d_name.len
I'm running 2.2.16 and I have the same problem with my Maestro 2e.
On Mon, 25 Sep 2000, Pavel Machek wrote:
> Hi!
>
> Every second playback using maestro produces bad quality output. I'm using
> splay and -test8. Also sound quality degrades _after_ dropout caused by
> slow disk. Any ideas how
On Tue, Sep 26, 2000 at 06:31:04PM -0400, Alexander Viro wrote:
> On Wed, 27 Sep 2000, Marko Kreen wrote:
> > There is something fishy in ext2_empty_dir:
>
> Why?
>
> > + } else if (de->name[2])
>
Sorry, I had a hard day and I should have gone to sleep already...
On Sun, 24 Sep 2000, Constantine Gavrilov wrote:
> Hi, I'd like to use channel bonding driver for high availability.
>
> Currenly the bonding driver does not detect a dead slave link. When a
> slave link dies, it causes lots of network retransmits and the effective
> speed of the bonding device
On Tue, Sep 26, 2000 at 05:29:27PM -0400, Alexander Viro wrote:
> Comments and help in testing are more than welcome.
There is something fishy in ext2_empty_dir:
+ /* check for . and .. */
+ if (de->name[0] != '.')
+
On Tue, Sep 26, 2000 at 09:37:30PM +0200, Christoph Hellwig wrote:
> I'd like to have st_flags added to struct stat64, so adding the actual
> feature in Linux 2.5 (if it has a chance to get in - that's why I'm
> interested in a comment by Linus on this) will not need a new version
> of struct
> If software than provoke your disks to think they have bad blocks, your
> disks a certainly broken. [There may be another error somewhere in linux,
> but theres at least one error in the hw.]
Agree, but still no reason to lock solid. That IS a bug.
>
hello;
This patch does the following:
1) Enhances the kernel-doc script to strip out macros from header files
2) Corrects path to videodev.c in makefile, kernel-api.tmpl and
videobook.tmpl
3) Adds docbook tags to /asm-i386/atomic.h and /linux/init.h
4) Adds atomic and module calls to
On Tue, Sep 26, 2000 at 08:23:04PM +0100, Adam Sampson wrote:
> However, I'm probably not a useful datapoint, as I'm running 2.4.0-test8 +
> reiserfs-3.9.16 + 2.4.0-t8-sched + 2.4.0-t8-vmpatch4.
Just happened again with test9-pre7; looked like it was caused by gcc eating
lots of memory and going
Duh. After fixing two idiotic bugs in ext2_readdir() it seems to
be really working (survives assorted builds, does the right thing on
find-based scripts and obvious local tests, yodda, yodda). It certainly
needs more testing, but I would call it (early) beta.
Folks, give it a try
> I think adding a document about MCE in the kernel would be very useful.
> Or at least a pointer to Intel's documentation about it.
Agreed - and maybe an MCE decoder app
I've been peering over the docs to retrieve POST log entries as well. It means
running some bios calls in vm86 but might
Alan,
I think adding a document about MCE in the kernel would be very useful.
Or at least a pointer to Intel's documentation about it.
On 26 Sep 2000, H. Peter Anvin wrote:
> Followup to: <[EMAIL PROTECTED]>
> By author:"Martin Bene" <[EMAIL PROTECTED]>
> In newsgroup:
> So memory problems seem to be out. (kernel did not panic on machine check
> exception, so machine is still up after reported exception)
MCE is a cpu level check. It generally indicates a processor fault. The actual
code you get you can decode with the intel PII manual
-
To unsubscribe from
Hello,
> > Another approach would be to let user space turn off overcommit.
>
> No. Overcommit only applies to pageable memory. Beancounter is
> really needed for non-pageable resources such as page tables and
> mlock()ed pages.
>
In addition to beancounter, do you think pageable page
Hi Albert,
> See the Signal 11 FAQ... you can start with:
>
> 1. make sure the memory in bank 4 is properly seated
> 2. make sure your case is cool enough inside
> 3. make sure your power supply is good
> 4. try new RAM
> 5. try a new motherboard
Memory: ECC Mem in all banks, status:
Hello Constantine !
I also needed to be able to detect a failed link and to remove the
guilty interface from a trunk between a linux box and an Alteon A708
switch. So I've just written a little patch against 2.2.17 to implement
the BOND_RELEASE ioctl (Thomas Davis cc'd for this). I also quickly
On Tue, 26 Sep 2000, Ingo Molnar wrote:
> On 26 Sep 2000, Juan J. Quintela wrote:
>
> > Ingo, I am very wrong, or vmfixes-B2_deadlock is not included in
> > test9-pre7.
>
> well, the __GFP_IO part is included (in a different way). The slab.c part
> is not included.
Actually the
Followup to: <[EMAIL PROTECTED]>
By author:"Martin Bene" <[EMAIL PROTECTED]>
In newsgroup: linux.dev.kernel
>
> Hi,
>
> just found this in my logs, doesn't look like something I'd want to
> see - anything I should do about it?
>
What causes machine check exceptions? Hardware error.
On Tue, Sep 26, 2000 at 10:00:12PM +0200, Peter Osterlund wrote:
> Therefore, no matter what algorithm you use in elevator_linus() the total
> number of seeks should be the same.
It isn't. There's a big difference between the two algorithms and all your
previous emails was completly correct
On Tue, Sep 26, 2000 at 09:10:16PM +0200, Pavel Machek wrote:
> Hi!
> > > i talked about GFP_KERNEL, not GFP_USER. Even in the case of GFP_USER i
> >
> > My bad, you're right I was talking about GFP_USER indeed.
> >
> > But even GFP_KERNEL allocations like the init of a module or any other
On Tue, 26 Sep 2000, Andrea Arcangeli wrote:
: > smaller with your algorithm? (I later realized that request merging is
: > done before the elevator function kicks in, so your algorithm should
:
: Not sure what you mean. There are two cases: the bh is merged, or
: the bh will be queued in a new
Christoph Hellwig <[EMAIL PROTECTED]> writes:
> I'd like to have st_flags added to struct stat64, so adding the actual
> feature in Linux 2.5 (if it has a chance to get in - that's why I'm
> interested in a comment by Linus on this) will not need a new version
> of struct stat (and a new libc
Hi!
> > i talked about GFP_KERNEL, not GFP_USER. Even in the case of GFP_USER i
>
> My bad, you're right I was talking about GFP_USER indeed.
>
> But even GFP_KERNEL allocations like the init of a module or any other thing
> that is static sized during production just checking the retval
>
Hi!
> > > Sep 21 23:55:44 fs1 kernel: hdb: timeout waiting for DMA
> > > Sep 21 23:55:44 fs1 kernel: hdb: irq timeout: status=0xd0 { Busy }
> > > Sep 21 23:55:44 fs1 kernel: hda: DMA disabled
>
> Perhaps some timeouts are not set correctly or the specs include some errors, but
> it is very
Hi!
Every second playback using maestro produces bad quality output. I'm using
splay and -test8. Also sound quality degrades _after_ dropout caused by
slow disk. Any ideas how to fix that?
Pavel
PS: This has happened before. With
Hi!
> The NIC has an 8 kbyte on-board FIFO, some of which (3-5k) is used for
> buffering incoming data.
>
> An Rx overrun occurs when that on-board FIFO has filled up, and more
> data needs to go into it. It shouldn't fill up. This can be caused by
Well, it certainly can fill up (fbcon
On Tue, Sep 26, 2000 at 12:15:49PM -0700, Ulrich Drepper wrote:
> Christoph Hellwig <[EMAIL PROTECTED]> writes:
>
> > Hehe, that's why I'd like to introduce some additional pad with my
> > patch ;)
>
> There is no reason to introduce now unnecessarily incompatibilities.
> If you want to look
On Tue, Sep 26, 2000 at 03:29:40PM +0200, Helge Hafting wrote:
> Unfortunately it still dies occationally. sysrq-Boot is the only thing
> that work,
> I have no more data as it happened in X and console switching didn't
> work.
>
> Exactly the same behavior as VM crashes in test9-pre5 and
Christoph Hellwig <[EMAIL PROTECTED]> writes:
> Hehe, that's why I'd like to introduce some additional pad with my
> patch ;)
There is no reason to introduce now unnecessarily incompatibilities.
If you want to look forward and add more padding do this when there is
another change necessary.
> So runtime checks don't have to be made. If you don't have DMA, the
> functions just return -EINVAL (so they must return a value). Otherwise,
> they don't return a value because they 'printk' their own diagnostic
> message.
The return value thing is a bug
-
To unsubscribe from this list: send
On Tue, Sep 26, 2000 at 05:42:59PM +0200, Mads Martin Joergensen wrote:
> * Timur Tabi <[EMAIL PROTECTED]> [Sep 26. 2000 17:36]:
> > > Maybe this can be fixed for 2.96, but it breaks badly elsewhere (doesn't
> > > compile; kernel builds but hangs/crashes at boot; kernel appears to work
> > > fine
On Tue, 26 Sep 2000 10:37:01 -0500, Timur Tabi wrote:
> ** Reply to message from Horst von Brand <[EMAIL PROTECTED]> on Tue, 26 Sep
> 2000 10:45:10 -0400
>> Maybe this can be fixed for 2.96, but it breaks badly elsewhere (doesn't
>> compile; kernel builds but hangs/crashes at boot; kernel appears
> "Alan" == Alan Cox <[EMAIL PROTECTED]> writes:
Alan> unsigned is always explicitly integer.
>> And recent gcc's complain over it.
Alan> So file a gcc bug ?
Hmmm and it doesn't seem to moan over it anymore, highly embarrassing
;-( Sorry Aris.
I remember Andreas changed some of these in I
Andrea Arcangeli <[EMAIL PROTECTED]> writes:
> Could you tell me what's wrong in having an app with a 1.5G mapped executable
> (or a tiny executable but with a 1.5G shared/private file mapping if you
> prefer),
O.K. that sound more reasonable. I was reading image as program
text... and a 1.5GB
At 05:23 PM 09/25/2000 -0400, Johathan Earle wrote:
>
> Hi,
>
> I'm running kernel 2.4.0-test9-pre4 on a Dell GX1 (PIII-500) with a Znyx
> 4port 10/100 card (4 tulip 21143 ethernet controllers onboard). With the
> ports locked at 10mbps full duplex, and traffic (64byte UDP packets) from
our
>
> "Alan" == Alan Cox <[EMAIL PROTECTED]> writes:
Alan> unsigned is always explicitly integer.
>> And recent gcc's complain over it.
Alan> So file a gcc bug ?
Ok, I got it now - I confused 'unsigned foo' with 'static foo' the
latter being moaned about.
Sorry about the confusion.
Jes
-
To
On Tue, Sep 26, 2000 at 06:20:47PM +0200, Christoph Rohland wrote:
> O.K. that sound more reasonable. I was reading image as program
> text... and a 1.5GB program text is a something I never have seen (and
> hopefully will never see :-)
:)
>From the shrink_mmap complexity of the algorithm point
On Tue, Sep 26, 2000 at 09:56:55AM +0200, Listuser AVA System wrote:
> Sorry to bother all ya important ones.
> I'm about to disect 2.4, however the little bugger won't boot.
> I suspect the milo. Which is built for 2.2.13.
Use a recent MILO (milo-2.2-17.tar.bz2) or check the 'legacy kernel
On Tue Sep 26, 2000 at 06:08:20PM +0100, Stephen C. Tweedie wrote:
> Hi,
>
> On Tue, Sep 26, 2000 at 11:02:48AM -0600, Erik Andersen wrote:
>
> > Another approach would be to let user space turn off overcommit.
>
> No. Overcommit only applies to pageable memory. Beancounter is
> really
On Tue, Sep 26, 2000 at 10:12:44AM -0700, Linus Torvalds wrote:
> It should probably just be a GFP_USER (ie not the GFP_KERNEL "try very
> hard").
GFP_KERNEL and GFP_USER have to try equally very hard until the machine runs
_truly_ out of memory.
When the machine runs truly out of memory I
Le mar, sep 26, 2000, à 11:05:42 -0500, Jeff Garzik a écrit:
> This driver was merged from 2.2.x and needs some more cleanups. Horst
> von Brand posted a patch on lkml against this driver, too, but his
> cleanups had a bug in it, and weren't as terse with procfs as the
> following patch is...
On Tue, 26 Sep 2000, boria wrote:
> Hi,
>
> First of all, i am new to kernel, so please correct me if i am wrong or
> explain if i don't get something.
> Why does free_dma get declared with different return types in dma.c ?
>
So runtime checks don't have to be made. If you don't have
On Tue, 26 Sep 2000, Alan Cox wrote:
> > Alan> unsigned is always explicitly integer.
> > And recent gcc's complain over it.
>
> So file a gcc bug ?
AFAIK C99 spec requires full type description ("unsigned int"), gcc just
follows the spec.
Zbigniew Chyla
-
To unsubscribe from this list:
> From: Narayan Desai [mailto:[EMAIL PROTECTED]]
>
> > "Randy" == Dunlap, Randy <[EMAIL PROTECTED]> writes:
>
> >> Hi, I have been having problems with the usb audio driver on a set
> >> of Philips DSS330. The driver seemed to work properly up until
> >> 2.3.99-6. The driver included with
On Tue, 26 Sep 2000, Jeff Garzik wrote:
> On Mon, 25 Sep 2000, Linus Torvalds wrote:
> > - pre7:
> > - official Compaq CISS driver.
>
> He may be the maintainer, but he needs a good spanking...
No, the breakage is probably mine.
The problem was that you sent me the forward-port of
On Tue, 26 Sep 2000, Arjan van de Ven wrote:
>
> And the network-stack in net/core/sock.c:sock_alloc_send_skb which sounds
> like a bug in this case, and might even be the cause of too many GFP_BUFFER
> allocations in loads suchs as Ingo's.
Hey, good grepping.
That looks like just complete
> "Randy" == Dunlap, Randy <[EMAIL PROTECTED]> writes:
>> Hi, I have been having problems with the usb audio driver on a set
>> of Philips DSS330. The driver seemed to work properly up until
>> 2.3.99-6. The driver included with 2.3.99-6 worked correctly when
>> included with kernels up to
Hi,
First of all, i am new to kernel, so please correct me if i am wrong or
explain if i don't get something.
Why does free_dma get declared with different return types in dma.c ?
from kernel/dma.c (kernel test9-pre6)
#ifdef MAX_DMA_CHANNELS
...
void free_dma(unsigned int dmanr)
...
Hi,
On Tue, Sep 26, 2000 at 11:02:48AM -0600, Erik Andersen wrote:
> Another approach would be to let user space turn off overcommit.
No. Overcommit only applies to pageable memory. Beancounter is
really needed for non-pageable resources such as page tables and
mlock()ed pages.
Cheers,
On Tue Sep 26, 2000 at 05:04:06PM +0100, Stephen C. Tweedie wrote:
> Hi,
>
> On Tue, Sep 26, 2000 at 09:17:44AM -0600, [EMAIL PROTECTED] wrote:
>
> > Operating systems cannot make more memory appear by magic.
> > The question is really about the best strategy for dealing with low memory. In my
> I have installed my linux, redhat. I do not have boot disk.
> How do i make boot floppy disk from the already installed linux
> on my harddrive?.
Firstly you want the redhat lists not the kernel list ([EMAIL PROTECTED])
Secondly its in the manual
-
To unsubscribe from this list: send the line
> "edsel" == Edsel Adap <[EMAIL PROTECTED]> writes:
Hi
edsel> Hi,
edsel> I'm suffering from the occasional Oops message, and from reading the
edsel> oops-tracing.txt file, it says:
edsel> cd /usr/src/linux/scripts/ksymoops
edsel> make ksymoops
you can got ksymoops package and no need to
Hi,
I have installed my linux, redhat. I do not have boot disk.
How do i make boot floppy disk from the already installed linux
on my harddrive?.
Thanx,
jm
_
Get Your Private, Free E-mail from MSN Hotmail at
Timur Tabi <[EMAIL PROTECTED]> said:
[...]
> Why is 2.96 so screwed up? I mean, the version numbers imply that 2.96 is a
> minor bugfix over 2.95, but your comments make it sound like it's a major
> change.
It's the kernel which is screwed up, not the compiler. The kernel uses
gcc-specific
> Alan> unsigned is always explicitly integer.
> And recent gcc's complain over it.
So file a gcc bug ?
-
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/
Woo hoo, I found some time for kernel hacking :)
This driver was merged from 2.2.x and needs some more cleanups. Horst
von Brand posted a patch on lkml against this driver, too, but his
cleanups had a bug in it, and weren't as terse with procfs as the
following patch is...
Against
On Mon, Sep 25, 2000 at 10:11:37PM +0200, Jasper Spaans wrote:
> A simple solution: update your version of mount, and try
>
> mount --bind /foo /bar
Is there a way to place such a mount in fstab?
Jan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a
Hi,
On Tue, Sep 26, 2000 at 09:17:44AM -0600, [EMAIL PROTECTED] wrote:
> Operating systems cannot make more memory appear by magic.
> The question is really about the best strategy for dealing with low memory. In my
> opinion, the OS should not try to out-think physical limitations. Instead,
> "Alan" == Alan Cox <[EMAIL PROTECTED]> writes:
aris> + unsigned xmt_lower_limit_reg; + unsigned xmt_upper_limit_reg;
aris> + unsigned eeprom_reg; };
>> Please don't use unsigned without specifying the size, use either
>> unsigned int or unsigned long.
Alan> unsigned is always explicitly
[Edsel Adap]
> Where can I get bfd.h?
Debian package 'binutils-dev'.
Peter
-
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/
> aris> + unsigned xmt_lower_limit_reg;
> aris> + unsigned xmt_upper_limit_reg;
> aris> + unsigned eeprom_reg;
> aris> };
>
> Please don't use unsigned without specifying the size, use either
> unsigned int or unsigned long.
unsigned is always explicitly integer.
[Jes Sørensen]
> Please don't use unsigned without specifying the size, use either
> unsigned int or unsigned long.
This is just a stylistic issue, right? I believe 'unsigned' is short
(no pun intended) for 'unsigned int', just as 'long' is short for 'long
int'. I find both forms about
[mec]
> > Peter, your patch fails if CONFIG_BLK_DEV_MD=m and CONFIG_BLK_DEV_LVM=y.
Ewww, you're right. As I believe I already mentioned, this is why I
was originally opposed to mixing lvm and md into one directory. Not
that this was a valid objection, of course.
The easy fix would be to
On Tue, Sep 26, 2000 at 12:14:18AM +0200, Andrea Arcangeli wrote:
> On Mon, Sep 25, 2000 at 10:52:08PM +0200, Peter Osterlund wrote:
> > Do you know why? Is it because the average seek distance becomes
>
> Good question. No I don't know why right now. I'll try again just to be 200%
> sure and
hi,
done, thanks Jes!
On 26 Sep 2000, Jes Sorensen wrote:
> > "aris" == aris <[EMAIL PROTECTED]> writes:
>
> aris> hi, misc fixes on eepro driver, please apply
>
> aris> @@ -212,6 +214,12 @@
> aris>version of the 82595 chip. */
> aris>
* Timur Tabi <[EMAIL PROTECTED]> [Sep 26. 2000 17:36]:
> > Maybe this can be fixed for 2.96, but it breaks badly elsewhere (doesn't
> > compile; kernel builds but hangs/crashes at boot; kernel appears to work
> > fine while it is busy eating your disk; ...)
>
> Why is 2.96 so screwed up? I
> "aris" == aris <[EMAIL PROTECTED]> writes:
aris> hi, misc fixes on eepro driver, please apply
aris> @@ -212,6 +214,12 @@
aris> version of the 82595 chip. */
aris> int stepping;
aris> spinlock_t lock; /* Serializing lock */
aris> +
** Reply to message from Horst von Brand <[EMAIL PROTECTED]> on Tue, 26 Sep
2000 10:45:10 -0400
> Maybe this can be fixed for 2.96, but it breaks badly elsewhere (doesn't
> compile; kernel builds but hangs/crashes at boot; kernel appears to work
> fine while it is busy eating your disk; ...)
On Mon, Sep 25, 2000 at 05:14:11PM -0600, Erik Andersen wrote:
> On Mon Sep 25, 2000 at 02:04:19PM -0600, [EMAIL PROTECTED] wrote:
> >
> > > all of the pending requests just as long as they are serialised, is
> > > this a problem?
> >
> > I think you are solving the wrong problem. On a small
Hi,
I'm suffering from the occasional Oops message, and from reading the
oops-tracing.txt file, it says:
cd /usr/src/linux/scripts/ksymoops
make ksymoops
This fails with the following error message:
trillian:/usr/src/linux/scripts/ksymoops> make ksymoops
gcc -Dlinux -Wall
Jeff Garzik wrote:
>
> On Wed, 27 Sep 2000, Andrew Morton wrote:
> >
> > --- linux-2.4.0-test9-pre7/include/linux/tty_driver.h Sat Aug 5 13:35:24 2000
> > +++ linux-akpm/include/linux/tty_driver.h Wed Sep 27 00:47:24 2000
> > @@ -117,6 +117,15 @@
> >
> > #include
> >
> > +#ifdef
hi,
misc fixes on eepro driver, please apply
--
Aris
---
Aristeu Sergio Rozanski Filho [EMAIL PROTECTED]
Hi,
just found this in my logs, doesn't look like something I'd want to
see - anything I should do about it?
System: Linux 2.2.17, UP-Kernel, Asus P3V133 Motherboard, PIII/800
coppermine (133 FSB), 512MB ECC SDRAM
CPU 0: Machine Check Exception: 0004<0>Bank 4:
[EMAIL PROTECTED] (Michael N. Lipp)
> I can't compile the latest linux kernel with the latest gcc due to a
> strange define in checksum.S. The gcc preprocessor complains about
> the usage of elipses in the macros
linux-2.2.x are strictly egcs-1.1.x or gcc-2.95.x at the latest. 2.96 won't
work,
On Wed, 27 Sep 2000, Andrew Morton wrote:
>
> --- linux-2.4.0-test9-pre7/include/linux/tty_driver.h Sat Aug 5 13:35:24 2000
> +++ linux-akpm/include/linux/tty_driver.h Wed Sep 27 00:47:24 2000
> @@ -117,6 +117,15 @@
>
> #include
>
> +#ifdef CONFIG_MODULES
> +#include
> +struct
On Tue, Sep 26, 2000 at 09:15:33AM -0500, Jeff Garzik wrote:
> On Tue, 26 Sep 2000, Jan-Benedict Glaw wrote:
Hi!
> Take a look at past lkml messages from today... A larger Alpha patch
> was posted. Does that patch fix this problem too?
Oops. Yes, it does;)
MfG, JBG
--
Fehler eingestehen,
Hi, Ted.
The patch applies the industry-standard `struct module *owner' stuff to
tty_driver and tty_ldisc (as per the TODO list!). It also closes the
schedule()-with-zero-module-refcount hole in release_dev().
There is still no explanation for Harley Anderson's crash though.
serial.c and
On Tue, 26 Sep 2000, Jan-Benedict Glaw wrote:
> Hi!
>
> The following patch fixes this compile error:
>
> fcntl.c: In function `do_fcntl':
> fcntl.c:294: `F_LINUX_SPECIFIC_BASE' undeclared (first use in this function)
> fcntl.c:294: (Each undeclared identifier is reported only once
>
On 26 Sep 2000, Juan J. Quintela wrote:
> Ingo, I am very wrong, or vmfixes-B2_deadlock is not included in
> test9-pre7.
well, the __GFP_IO part is included (in a different way). The slab.c part
is not included.
Ingo
-
To unsubscribe from this list: send the line
> "ingo" == Ingo Molnar <[EMAIL PROTECTED]> writes:
Hi
>> Thank You! Seems to be much better now:
>>
>> Test of 2.4.0-t9p6 + vmfixes-2.4.0-test9-B2 + vmfixes-B2-deadlock.patch
ingo> note that this is effectively test8-pre7 (with a couple of more fixes and
ingo> the new multiqueue stuff),
Hi!
The following patch fixes this compile error:
fcntl.c: In function `do_fcntl':
fcntl.c:294: `F_LINUX_SPECIFIC_BASE' undeclared (first use in this function)
fcntl.c:294: (Each undeclared identifier is reported only once
fcntl.c:294: for each function it appears in.)
make[2]: *** [fcntl.o]
1 - 100 of 274 matches
Mail list logo
