On Wed, Oct 11, 2000 at 10:52:08AM -0700, Emmanuel STAPF wrote:
> Hi,
>
> I find out that doing the following command:
>cp toto titi/toto
> where toto is a file and titi is a directory do not change the date stamp of
> `titi'.
>
> Doing the same on Solaris 2.4 or 2.5 does it?
>
> Could
hi,
once i have got the pci_dev structure( by calling pci_find*), do i
explicitly need to call ioremap for remapping mmio.
i think pci_enable_device does this. correct me if i am wrong..
thanks,
anil
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a
I thought I read on the TODO list that the problems regarding lilo configs
such as:
append="ether=5,0x300,,,eth1"
had been resolved. On my machine that is not true (dual ppro with
supermicro mobo). I have a 3c509 and a netgear fa 310tx. With the above
line in my lilo.conf the 3com should get
You can find the download, and other information at:
http://scry.wanfear.com/~greear/vlan.html
This release seems to work, at least in the limited fashion that
I can test it. However, don't consider it production code (use 0.0.12
if that is what you want...)
Please try it out, and let me know
On Wed, Oct 11, 2000 at 09:59:10PM -0700, Thomas Zimmerman wrote:
> safemode wrote:
> >
> > The only reason I'm asking this is because nobody has mentioned it and it
> > seems to have gotten put on the back-burner .. i have heard a lot about
> > 2.2.x ide-scsi fixes but nothing about 2.4.0 ...
the last one i used was in 2.4.0-test2. then it's gone.
in test9 i have to enable pci and cardbus (which both i don't
have) and manually add CONFIG_I82365 in autoconf.h.
i don't know why it's gone, but that works for me. and i got
aieee, killing interrupt
safemode wrote:
>
> The only reason I'm asking this is because nobody has mentioned it and it
> seems to have gotten put on the back-burner .. i have heard a lot about
> 2.2.x ide-scsi fixes but nothing about 2.4.0 ... what's the status of this?
It works here with a Acer CD-RW drive...but
>I find out that doing the following command:
>cp toto titi/toto
>where toto is a file and titi is a directory do >not change the date stamp
of
>`titi'.
i checked this out with 2.4-0test9.
timestmap of directory is getting modified. you must be using very old
kernel
-
To unsubscribe from
An update of the Via audio driver for Linux 2.4.x kernels has been
posted at
http://gtf.org/garzik/drivers/via82cxxx/
In addition to bug fixes, this update features increased playback
performance and new features: recording, full duplex, realtime, and
trigger support.
The core driver
On Wed, 11 Oct 2000, David S. Miller wrote:
>It's safe because of how x86s hardware works
>
> What about other platforms?
If atomic ops don't work, then software dirty bits are still an option
(read as: it shouldn't break RISC CPUs).
-ben
-
To unsubscribe from this list:
}Date: Thu, 12 Oct 2000 00:03:31 -0400 (EDT)
}From: "Benjamin C.R. LaHaise" <[EMAIL PROTECTED]>
}
}It's safe because of how x86s hardware works
}
} What about other platforms?
On the PPC's that don't do a hardware walk we do a normal write to the
hash table (with a spinlock).
Date:Thu, 12 Oct 2000 00:03:31 -0400 (EDT)
From: "Benjamin C.R. LaHaise" <[EMAIL PROTECTED]>
It's safe because of how x86s hardware works
What about other platforms?
Later,
David S. Miller
[EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe
Hello Linus,
On Wed, 11 Oct 2000, Linus Torvalds wrote:
> I much prefered the dirty fault version.
> What does "quite noticeable" mean? Does it mean that you can see page
> faults (no big deal), or does it mean that you can actually measure the
> performance degradation objectively?
It's a
} Andrea Arcangeli <[EMAIL PROTECTED]> said:
} > On Wed, Oct 11, 2000 at 06:19:23PM -0700, David S. Miller wrote:
} > > I honestly see nothing wrong with it. There are different parts of
} > > the compiler stressed by the kernel build as opposed to most userland
} > > compilation, and
Date: Thu, 12 Oct 2000 04:18:23 +0200
From: Andrea Arcangeli <[EMAIL PROTECTED]>
I disagree the stability/feature ratio needs are different between
kernel and userspace (at least excluding the FPU handling that of
course doesn't matter for kernel :).
Tell that to people who want
On Wed, Oct 11, 2000 at 11:21:06PM -0400, Horst von Brand wrote:
> also moves forward a lot faster than glibc, and grows a lot. A bug in glibc
> means an application goes down or screws up, a bug in the kernel can mean
> masive data loss in no time at all.
Foolhardy as it may be, people do _use_
Andrea Arcangeli <[EMAIL PROTECTED]> said:
> On Wed, Oct 11, 2000 at 06:19:23PM -0700, David S. Miller wrote:
> > I honestly see nothing wrong with it. There are different parts of
> > the compiler stressed by the kernel build as opposed to most userland
> > compilation, and furthermore the
On 2000-10-11 19:53:50 -0700, [EMAIL PROTECTED] wrote:
> On other machines I'd set RLIMIT_DATA and my OOM problems went away,
> but on linux this didn't work
RLIMIT_DATA appears to only be checked for aout format executables.
Looking at the 2.4.0-test10pre1 sources for fs/binfmt_aout.c and
I managed to follow, with a number of debug statements, a problem that
appears to be in parport_pc that causes the following lockup on a dual
P3 500 with modprobe:
NMI Watchdog detected LOCKUP on CPU0, registers:
CPU:0
EIP:0010:[]
EFLAGS: 0086
eax: 0301 ebx: 0216 ecx:
I've had to support an app running as a back-end to a webserver that would
malloc() different amounts of memory depending on user input, up to
multiple gigabytes of memory which vastly exceeded the 512k the machine
had as main memory. The app was a program that would scan genetic
sequence
> Somewhere floating around there is a perl version of rpm2cpio.
This is what I wrote one day a long time ago:
#!/usr/bin/perl -w
use strict;
my ($buffer, $pos, $gzmagic);
$gzmagic = "\037\213";
open OUT, "| gunzip" or die "cannot find gunzip; $!\n";
while(1) {
exit 1 unless defined($pos =
I have adaptec 20160 scsi adapter and plextor 32x cdrom.
I played audio cd with gtcd(gnome app) and eject cdrom with gtcd(eject button)
, gtcd died and dmesg out...
--
kernel BUG at /usr/src/linux-2.4.0-test10/include/asm/pci.h:61!
invalid operand:
CPU:0
EIP:0010:[]
EFLAGS:
On Wed, Oct 11, 2000 at 06:19:23PM -0700, David S. Miller wrote:
> I honestly see nothing wrong with it. There are different parts of
> the compiler stressed by the kernel build as opposed to most userland
> compilation, and furthermore the desired compiler stability/feature
> ratio is different
Hi there,
I am trying to find out more information on large memory support (> 4 GB)
for Linux IA32. Is there a document that elaborates on what is supported
and what isn't and how this scheme actually works in the kernel?
My primary concern is whether a process can allocate more than 4 GB of
}Date: Wed, 11 Oct 2000 19:36:15 -0600
}From: Cort Dougan <[EMAIL PROTECTED]>
}
}I don't think "it's been done in UNIX before" is a
}strong argument for something being done now :)
}
} True, but I think that "different things have different requirements"
} is a strong argument.
On Wed, 11 Oct 2000, Nathan Paul Simons wrote:
> On Wed, Oct 11, 2000 at 10:55:17PM +0100, Alan Cox wrote:
> > Hardly. In fact the idea of distributing a different compiler for kernels
> > comes from debian and the kgcc naming convention from Conectiva.
>
> What different compiler? If
Hiren,
The gcc-2.96 released with RedHat 7.0 is a development snapshot of the
compiler, not an offical gcc release. It has some changes which makes it
impossible to build a kernel. RedHat 7.0 also includes a rpm with kgcc (
"Kernel GCC" ) which provides the compile you should use for this
Date: Wed, 11 Oct 2000 19:36:15 -0600
From: Cort Dougan <[EMAIL PROTECTED]>
I don't think "it's been done in UNIX before" is a
strong argument for something being done now :)
True, but I think that "different things have different requirements"
is a strong argument. I merely
Booting test9 gives me:
PCI: failed to allocate resource 0 for: Q Logic ISP1020
PCI: failed to allocate resource 0 for:
PCI: failed to allocate resource 0 for: <3com card>
Then it gets to:
Net4: Unix domain sockets 1.0/SMP for Linux NET4.0.
and hard locks
this is an alphaserver 1000a
On 2000-10-11 11:45:06 -0400, Bruce A. Locke wrote:
> This manpage shows me functions and structs.
What were you expecting from the system call section of the Linux
Programmer's Manual? Dancing girls?
(h...)
> I'm assuming you want these used by the offending program or the shell
> under
}Date: Wed, 11 Oct 2000 19:15:24 -0600
}From: Cort Dougan <[EMAIL PROTECTED]>
}
}It's not a new idea but that doesn't make it a good one. The idea
}of distributing the _same_ compiler but different versions is
}nutty.
}
} Actually, this is common practice even in the
Date:Wed, 11 Oct 2000 19:15:24 -0600
From: Cort Dougan <[EMAIL PROTECTED]>
It's not a new idea but that doesn't make it a good one. The idea
of distributing the _same_ compiler but different versions is
nutty.
Actually, this is common practice even in the commercial UNIX
On 2000-10-11 12:48:54 -0400, Andrew Pimlott wrote:
> No way should a desktop user be responsible for micro-managing the
> resource usage of his applications.
That's right. The systems administrator should, and will set
appropriate limits for users on his/her system that apply from login.
This
I'm running linux-2.4.0-test9-pre7-riel on a 386 netstation, using
etherboot and rootfs. Rootfs works fine. But ...
Normally I mount /bin, /var, /etc, /lib (minimal) via rootfs, where they
are required for booting, and operation of the box, and once booting
has started, I mount /usr, /sbin and
David Wragg writes:
> Tigran Aivazian <[EMAIL PROTECTED]> writes:
> > b) it detects all memory correctly but creates a write-back mtrr only for
> > the first 2G, is this normal?
>
> mtrr.c is broken for machines with >=4GB of memory (or less than 4GB,
> if the chipset reserves an addresses range
> Hardly. In fact the idea of distributing a different compiler for kernels
> comes from debian and the kgcc naming convention from Conectiva.
It's not a new idea but that doesn't make it a good one. The idea of
distributing the _same_ compiler but different versions is nutty.
-
To unsubscribe
On Wed, Oct 11, 2000 at 10:55:17PM +0100, Alan Cox wrote:
> Hardly. In fact the idea of distributing a different compiler for kernels
> comes from debian and the kgcc naming convention from Conectiva.
What different compiler? If you're talking about the kernel-package
package of
On Thu, 12 Oct 2000, Tom Holroyd wrote:
> Alpha DP264 (UP), SCSI, floppy
>
> If I do a dd if=/dev/zero of=/tmp/moo count=10, I don't see any
> increase in buffers, as reported by vmstat. Furthermore, if I read from
> /dev/fd0, it used to buffer the whole thing, so a second read would be
Hi!
Here is a update to my work that I posted earlier. The new vga.c file
contains common vga routines. Both share a common struct that contains the
hardware state.
TODO:
Merge font handling code. Font code is broken in vga16fb for text
modes. Attempting to make a universal function for
On Wed, Oct 11, 2000 at 03:35:40PM -0200, Marcelo Tosatti wrote:
> Now I'm not sure if this can be caused by a memory problem.
It can.
Andrea
-
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
Alpha DP264 (UP), SCSI, floppy
If I do a dd if=/dev/zero of=/tmp/moo count=10, I don't see any
increase in buffers, as reported by vmstat. Furthermore, if I read from
/dev/fd0, it used to buffer the whole thing, so a second read would be
fast -- now it hits the floppy again.
I ran some
On Thu, 12 Oct 2000 02:20:15 +0200,
Jan Niehusmann <[EMAIL PROTECTED]> wrote:
>> argued that critical routines should always be compiled with -i386,
>> unfortunately that includes all of printk and all console handling
>> (both serial and screen), not really an option.
>
>Neither printk nor
> argued that critical routines should always be compiled with -i386,
> unfortunately that includes all of printk and all console handling
> (both serial and screen), not really an option.
Neither printk nor console handling should be too performance
critical, and the performance of console i/o
The only reason I'm asking this is because nobody has mentioned it and it
seems to have gotten put on the back-burner .. i have heard a lot about
2.2.x ide-scsi fixes but nothing about 2.4.0 ... what's the status of this?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel"
On Wed, 11 Oct 2000, Ben LaHaise wrote:
>
> Here's an updated version of the patch that doesn't do the funky RISC like
> dirty bit updates. It doesn't incur the additional overhead of page
> faults on dirty, which actually happens a lot on SHM attaches
> (during Oracle runs this is quite
On Wed, 11 Oct 2000 18:10:40 -0400,
[EMAIL PROTECTED] wrote:
>Are you sure it was compiled with the correct CPU? If you configure the
>CPU incorrectly (686 when you only have a 586, etc.) the kernel *will*
>refuse to boot.
>
>Maybe we should have the kernel print the CPU information it was
On Wed, 11 Oct 2000 [EMAIL PROTECTED] wrote:
>> 2. Capable Of Corrupting Your FS/data
>>
>> * Non-atomic page-map operations can cause loss of dirty bit on
>>pages (sct, alan)
>
>Is anybody looking into fixing this bug ?
>
> According to sct (who's sitting
Dear.
I use pre-patch-2.0.39final ( I use pre-patch-2.0.39final.gz ),
and work fine.
My PC is
Asus cubx motherboad
Celeron-566
Memory 64 MB
Ethercard chip RTL8139
Disk IBM ATA 30GB ( I use 1GB partition )
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body
> The bug report said that it was verified under both SCSI and ATAPI MO,
> and that uses a different driver than the SCSI CD-ROM code, I think
ATAPI Magneto Optical is SCSI disk. The same thing applies to disk and CD,
it isnt just a CD-ROM path item. Both work in 2.2
-
To unsubscribe from
I just got two separate crashes using 2.2.17 and reiserfs.
H/W:
FIC-SD11 with K7-700, 384MB of RAM
Dlink Quad Ethernet card (tulip)
The first one:
find . -print | cpio -C 4096 -pumd /newplace
i.e., copying a rather large directory tree from one disk to another
From: "Eric Bresie" <[EMAIL PROTECTED]>
Date:Mon, 9 Oct 2000 15:31:56 -0500
The existing TODO type list I refer to are those produced by Kenneth C.
Arnold ( http://kena.8k.com/linux-kernel/ ) (who is doing a fine job I might
add) and formerly by Alan Cox.
I've taken a
Hello !
I think that you should wait a bit before writing a config in /proc for the
bonding driver.
I have rewritten quite a part of it to support link detection and make it a bit
fail safe.
Moreover, I had to rewrite partly ifenslave.c (which is included in the same
patch). Everything
*seems*
On Wed, Oct 11 2000, [EMAIL PROTECTED] wrote:
>Date: Mon, 9 Oct 2000 16:24:24 +0100 (BST)
>From: Alan Cox <[EMAIL PROTECTED]>
>
>> * FAT filesystem doesn't support 2kb sector sizes (did under 2.2.16,
>>doesn't under 2.4.0test7. Kazu Makashima, alan)
>
>[Same as
Date: Sun, 8 Oct 2000 23:24:49 -0700
From: Mitchell Blank Jr <[EMAIL PROTECTED]>
> * IBM Thinkpad 390 won't boot since 2.3.11 (See Decklin Foster for
>more info)
I _highly_ suspect that this is not a 2.4 bug but is instead user error.
I've seen it several times.
Date: Mon, 9 Oct 2000 16:24:24 +0100 (BST)
From: Alan Cox <[EMAIL PROTECTED]>
> * FAT filesystem doesn't support 2kb sector sizes (did under 2.2.16,
>doesn't under 2.4.0test7. Kazu Makashima, alan)
[Same as the CDROM bug listed earlier I think]
The bug report said
> If the problem only impacts User-mode Linux, it's hard for me to justify
> hanging the "critical" label on it. However I'm willing to look at the
> patch, bless it, and send it on to Linus (who as you know sometimes is a
> softy about such things. :-)
>
> I'm pretty sure that we'd be able
On Wed, 11 Oct 2000 09:56:46 -0400, Horst von Brand blurted forth:
> - RH 7 ships a gcc patched from CVS sources in order to take advantage of
>better (on ix86 mainly) optimizations on userland
> - RH 7 ships kgcc for compiling the kernel, as the 2.2 kernels are known to
>be broken
On Wed, Oct 11, 2000 at 05:11:39PM -0400, Richard B. Johnson wrote:
> Linux version 2.2.17
> I tried to add a new Hard disk. It's s Seagate ST39102LW 8.1 Gb.
Hmm. Your C/H/S multiplies out to 9.1 GB.
On the other hand, Seagate ST39102LW has 9105018880 bytes,
so probably the 8 was a typo (and
Just experienced the following Oops: It's reproducible, the offender
being netscape 4.75. Reverting back to 2.4.0-test9 fixes the
problem. Both kernels were compiled with the same config.
I'm not on the list, so please CC me.
ksymoops 2.3.4 on i686 2.4.0-test10p1. Options used
-V
On Wed, Oct 11, 2000 at 12:13:48PM +0200, Benjamin Herrenschmidt wrote:
> >Well, at first, I wanted to implement it the same way on PPC. However, it
> >dies on all occurences where udelay is called with a non-constant expression.
> >
> >I spotted this case in a few PPC specific stuffs (fixable),
On Wed, 11 Oct 2000, Dag B wrote:
>
> > drivers/pcmcia/yenta.c to allocate more than 4MB of PCI memory window.
> [snip]
>
> > align = size = 32*1024*1024;
> Done.
> Didn't work. But it certainly made a difference.
>
> lspci -v now says:
>
> 06:00.0 Ethernet controller: Xircom
Hi All,
Just 2 days back I bought RedHat Linux7. And I was trying to build
the kernel (make bzImage). But the build failed. It looks like
the compiler issue. But I am not sure and hence, I have posted this
on this list.
Well, I tried one more thing. The RedHat Linux7 came with gcc package
Hi,
On Wed, Oct 11, 2000 at 09:28:57PM +0100, Chris Evans wrote:
>
> The problem is best described with a little sequence. After using raw i/o
> facilities, streamed block device reads from the same underlying device
> exhibit much poorer performance than before the raw i/o.
>
> Anyone know
Date: Mon, 09 Oct 2000 20:13:35 +0200
From: Thomas Sailer <[EMAIL PROTECTED]>
Alan Cox wrote:
>
> > 4. Boot Time Failures
> >
> > * IBM Thinkpad 390 won't boot since 2.3.11 (See Decklin Foster for
> >more info)
>
> Add Palmax PD1100 hangs during boot
This came up on the FreeS/WAN list and seemed to me worth raising on
the kernel list...
Original Message
Subject: Re: linux-ipsec: trying to build on RHL7.0
Date: Wed, 11 Oct 2000 14:54:50 -0400 (EDT)
From: "D. Hugh Redelmeier" <[EMAIL PROTECTED]>
[snip discussion of various
On Wed, 11 Oct 2000 [EMAIL PROTECTED] wrote:
>Date: Wed, 11 Oct 2000 16:33:09 +0100 (BST)
>From: Tigran Aivazian <[EMAIL PROTECTED]>
>
>Maybe this is because I called this machine - hilbert, so now it gives me
>nothing but very interesting and exciting Problems... in fact
> 2.2.18-pre with good results on Thinkpad 600x. No adverse consequencies
> (memory is reported correctly, suspend/hibernate work fine). I also had
> a chance to use it on several big SMP and UP servers (where e801 memory
> reporting works fine) Intel, Compaqs and IBM. No adverse consequencies
>
On Wed, 11 Oct 2000, Rik van Riel wrote:
> On Wed, 11 Oct 2000, Tigran Aivazian wrote:
> > > On Wed, 11 Oct 2000, Rik van Riel wrote:
> > > > Could you send me the backtrace of one of the cases where
> > > > you hit the bug ?
> >
> > just to add -- I was following Alan Cox's suggestion of
> >
Would someone please look at this and see what might be going wrong?
Please tell me if additional information is needed.
Thanks,
Miles
Miles Lane wrote:
>
> ksymoops 0.7c on i686 2.4.0-test10. Options used
> -V (default)
> -k /proc/ksyms (default)
> -l /proc/modules
Date:Wed, 11 Oct 2000 16:33:09 +0100 (BST)
From: Tigran Aivazian <[EMAIL PROTECTED]>
Maybe this is because I called this machine - hilbert, so now it gives me
nothing but very interesting and exciting Problems... in fact too many of
them :)
There was a similar problem
> Wouldn't it be better to use an #error directive? I'm sure this could turn
> into a FAQ, even though the symbol is called "__bad_udelay()".
You cant do that trick since #error is pre-processor, otherwise - yes
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> > On Red Hat 7.0, use "kgcc" for kernel compilation. This is
> > really an FAQ... Instead of changing distributions, try reading
> > manuals.
>
> What manuals ?
The ones on the CD that come with it
> The kgcc story looks to me like a lie from RedHat. In my opinion, they
> just don't want
On Wed, 11 Oct 2000, Alan Cox wrote:
> > > have the rules for testing if the driver/host/device register and report
> > > that all signals are valid and stable.
> >
> > Yes, I had some "interesting" modifications to a lot of my /usr when I
> > tried to activate UDMA4 under RH7.0 (I don't
Date: Fri, 06 Oct 2000 16:22:11 -0500
From: Jeff Dike <[EMAIL PROTECTED]>
[EMAIL PROTECTED] said:
> And it's allocating a tty_struct for a really dumb reason, too. It's
> just using it so it cna call tty_name.
> Just replace the call to tty_name with something like this:
I tried to add a new Hard disk. It's s Seagate ST39102LW 8.1 Gb.
In the BIOS setup of the BusLogic adapter, I was able to format
and verify the disk with no problems whatsoever.
fdisk seemed to work okay. I made partitions.
mke2fs would fail (hang the system) while writing inodes.
The BusLogic
On Wed, 11 Oct 2000, Tigran Aivazian wrote:
> it works fine then. Kernel compiles in 68 seconds as it should. Shall I
> keep incrementing mem= to see what happens next...
I suspect fixing the mtrrs on the machine will fix this problem, as a
38-40 times slowdown on a machine that isn't swapping
>
>Yep. This is a huge release patch anyway so resynching the stuff is fine.
>What I wont take is stuff touching core code
I do have a 2 lines patch to the common ide code that fix a problem when
revalidating a CD-ROM after sleep, but it was ack'ed by Andre Hedrick. I
also have a two-liners to
Dear list,
I run a Compaq Proliant 1500 (dual Pentium 75.200) with hardware raid
(Smart2) with two ethernet cards 3com905 (b or c, I can't tell you right
now) as a firewall and web/mail virus scanner which (needless to say)
needs to be up 7d/24h.
Recently, during a pretty fast download the
Alan, can we integrate e820 memory detection into 2.2.18 / 2.2.19? The
backport (from 2.4) patch is available at
http://www.pell.portland.or.us/~orc/Memory/2214.fancy.diff .
It applies cleanly to 2.2.14-2.2.18pre. I have been using it with
2.2.18-pre with good results on Thinkpad 600x. No
Linus Torvalds wrote:
>
> On Wed, 11 Oct 2000, Dag B wrote:
> > 2.4.0-test9/10p1
>
> Can you do another test with this (ie in-kernel pcmcia), AND enable
> debugging in both drivers/pci/pci.c and in arch/i386/kernel/pci-i386.h (in
[snip]
> drivers/pcmcia/yenta.c to allocate more than 4MB of PCI
On Wed, 11 Oct 2000, Tigran Aivazian wrote:
> > On Wed, 11 Oct 2000, Rik van Riel wrote:
> > > Could you send me the backtrace of one of the cases where
> > > you hit the bug ?
>
> just to add -- I was following Alan Cox's suggestion of
> incrementing "mem=N" and finding the value where the
Hi,
Here's a very strange (and repeatable) result. Affects 2.2.x + raw device
patches (i.e. RH7.0). Also had a similar effect on 2.4.0test9!
The problem is best described with a little sequence. After using raw i/o
facilities, streamed block device reads from the same underlying device
exhibit
Tigran Aivazian <[EMAIL PROTECTED]> writes:
> b) it detects all memory correctly but creates a write-back mtrr only for
> the first 2G, is this normal?
mtrr.c is broken for machines with >=4GB of memory (or less than 4GB,
if the chipset reserves an addresses range below 4GB for PCI).
The patch
On Wed, 11 Oct 2000, Tigran Aivazian wrote:
> On Wed, 11 Oct 2000, Rik van Riel wrote:
> > Could you send me the backtrace of one of the cases where
> > you hit the bug ?
>
> here you are:
> Oct 11 16:05:26 hilbert36 kernel: kernel BUG at page_alloc.c:221!
> Oct 11 16:05:27 hilbert36 kernel:
On Wed, 11 Oct 2000 07:32:30 -0400, Jakub Jelinek blurted forth:
> The fact that we recommend using kgcc (especially for 2.2 kernels) does not
> mean that the default gcc is broken, but simply that using it for kernels
> has not been tested yet too much and there can be e.g. bugs in the way
On Thu, 12 Oct 2000, Matthew Hawkins wrote:
> On 2000-10-11 09:45:30 -0500, Jesse Pollard wrote:
> > Until user memory resource quotas are included in the kernel, there will be
> > nothing else that can be done. Even with resource quotas, if the total of
> > active users exceeds the resource then
> On Wed, 11 Oct 2000, Rik van Riel wrote:
> > Could you send me the backtrace of one of the cases where
> > you hit the bug ?
just to add -- I was following Alan Cox's suggestion of incrementing
"mem=N" and finding the value where the system stops working normally. It
was ok as high as
On Wed, 11 Oct 2000, Rik van Riel wrote:
> Could you send me the backtrace of one of the cases where
> you hit the bug ?
here you are:
Oct 11 16:05:26 hilbert36 kernel: kernel BUG at page_alloc.c:221!
Oct 11 16:05:26 hilbert36 kernel: invalid operand:
Oct 11 16:05:26 hilbert36 kernel: CPU:
On Wed, 11 Oct 2000, Tigran Aivazian wrote:
> On Wed, 11 Oct 2000, Rik van Riel wrote:
> > On Wed, 11 Oct 2000, Tigran Aivazian wrote:
> > > On Wed, 11 Oct 2000, Mark Hemment wrote:
> > > > On Wed, 11 Oct 2000, Tigran Aivazian wrote:
> > > >
> > > > > a) one of the eepro100 interfaces (the
"Chris Swiedler" <[EMAIL PROTECTED]> writes:
|> > > 2.2.18pre15 defines udelay as (in file include/asm-i386/delay.h) :
|> > > extern void __bad_udelay(void);
|> > >
|> > > #define udelay(n) (__builtin_constant_p(n) ? \
|> > > ((n) > 2 ? __bad_udelay() : __const_udelay((n) *
|> > >
On Wed, 11 Oct 2000, Rik van Riel wrote:
> On Wed, 11 Oct 2000, Tigran Aivazian wrote:
> > On Wed, 11 Oct 2000, Mark Hemment wrote:
> > > On Wed, 11 Oct 2000, Tigran Aivazian wrote:
> > >
> > > > a) one of the eepro100 interfaces (the onboard one on the S2QR6 mb) is
> > > > malfunctioning,
Use a serial console trace to redirect the output to another thing to
recorded the barf.
Oct 11 12:20:07 sis620 kernel: hda: TF.0=0x00 TF.1=0x00 TF.2=0x01 TF.3=0x00 TF.4=0x00
TF.5=0x00 TF.6=0x00 TF.7=0xec size=540
Oct 11 12:20:07 sis620 kernel: hda: ide_ioctl_cmd HDIO_DRIVE_TASKFILE:
On Wed, 11 Oct 2000, Tigran Aivazian wrote:
> On Wed, 11 Oct 2000, Mark Hemment wrote:
> > On Wed, 11 Oct 2000, Tigran Aivazian wrote:
> >
> > > a) one of the eepro100 interfaces (the onboard one on the S2QR6 mb) is
> > > malfunctioning, interrupts are generated but no traffic gets through
Title: FW: Unable to handle kernel NULL pointer dereference
There was no output, just the logon prompt and below that
"Unable to handle kernel NULL pointer dereference"
-Original Message-
From: Andre Hedrick
To: Gomez, Bob
Cc: '[EMAIL PROTECTED]'
Sent: 10/11/00 2:15 PM
Subject:
Bob, it does help if you send the output ... my ESP is down today.
Cheers,
Andre Hedrick
The Linux ATA/IDE guy
-
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/
Ralf Sinoradzki wrote:
>
> Hi,
>
> I noticed, that the use count of module lp is increased
> when a cron job is done but never decreased.
> Same with restarting lprng.
> So I tested this with a c-program, that opened /dev/lp,
> closed /dev/lp and exited. After this, I started 'lsmod'
> and the
Title: Unable to handle kernel NULL pointer dereference
I received a "Unable to handle kernel NULL pointer dereference" on a Compaq 1850R running 2.4-Test 10-pre1, after running for about 2 hours. I had to hard reboot the system in order to restart the system, there are no log entries for
On Wed, 11 Oct 2000, Mike A. Harris wrote:
> On 10 Oct 2000, Gnea wrote:
>
> >> Please add this to your list. Linux is unusable in these machines.
> >> I have cc'ed Martin and Linus because they play in that PCI area.
> >
> >erm, looking at your list it says that you're using Redhat 7.0,
On Thu, 12 Oct 2000, Matthew Hawkins wrote:
> eax: ebx: c780f3c0 ecx: 0002 edx: 417df660
> esi: c780f421 edi: c17dff2d ebp: c32956e0 esp: d15f3efc
Most likely a fscked memory - bit 31 in the pointer
(to alan)
Alan Cox wrote:
> > I am interested in this too because a) I am the bad guy that did the 2.4 port
> > and therefor may be the one to blame for it and b) if a) is true I'll have to go
> > and fix it.
>
> No its something I've not yet fixed...
>
> cs_ac97_set needs to check nore than
1 - 100 of 375 matches
Mail list logo
