On 18 Sep, this message from Gérard Roudier echoed through cyberspace:
>> > All I wanted was a function that allows the driver to decide that which
>> > needs to be enabled.
>> >
>> > pci_enable_device(struct pci_dev *dev, byte enable_mask)
>> >
>> > This would allow drivers to enable that which
On some motherboards the IRQs are shared by PCI slots, look out for that.
More importantly, if two or more PCI slots share the same Bus Master
Control Signal you are asking for trouble(assuming you are using both
slots)
[EMAIL PROTECTED]
On Mon, 18 Sep 2000, Terence Ang wrote:
> Dear All,
>
kjh63 <[EMAIL PROTECTED]> writes:
> > How Linux Kernel and BPF relate to each other:
> >
> > a) linux has BPF (I don't think so).
It has LSF, the Linux Socket Filter.
> > b) Linux has own equivalent of BPF (part of NAT?)
Yes, the LSF.
> > c) linux does not have anything like BPF
BPF opcodes
Hello,
On Mon, 18 Sep 2000, Andi Kleen wrote:
> > SI_SIGIO is not generated from kernel. The same is for the
> > other SI_ consts < 0 not defined with __SI_CODE.
>
> Ok, then you have already broken binary compatibility between 2.2 and 2.4
Looking in the old kernels, it
On Mon, 18 Sep 2000 21:28:20 -0700,
"Armand" <[EMAIL PROTECTED]> wrote:
>drivers/char/char.o(.text.lock+0x66a): relocation truncated to fit:
>R_386_PC32 text.exit
>make: *** [vmlinux] Error 1
>
>I've upgraded to modutils-2.3.16-1 with Caldera OpenLinux LTP running on
Nothing to do with
Hi Linus,
please, check carefully Rik's VM patch, it definitly contains a
deadlock, which can be seen on low-memory computers. Try mem=8m. I
wasn't able to use any Rik patch since against -test8 (-t8-vmpatch{2,4},
-test9-pre{1,2}). It boots fine(mem=16m), but then stalls begin for some
time and
Hello,
I end up getting this error when I make bzImage:
drivers/char/char.o(.text.lock+0x66a): relocation truncated to fit:
R_386_PC32 text.exit
make: *** [vmlinux] Error 1
I've upgraded to modutils-2.3.16-1 with Caldera OpenLinux LTP running on
a SuperMicro P6DNF with dual Pentium II
> How Linux Kernel and BPF relate to each other:
>
> a) linux has BPF (I don't think so).
> b) Linux has own equivalent of BPF (part of NAT?)
> c) linux does not have anything like BPF
> d) something else (if so, then what?)
a) The Documentation/networking/filters.txt may say so but i dont think
Rusty writes:
> In message <[EMAIL PROTECTED]> you write:
>> * Mark Salisbury <[EMAIL PROTECTED]> [000918 07:32]:
>>> the source file linux/fs/hpfs/super.c
>>>
>>> from kernel version 2.4-test8 causes cscope to core dump during
>>> the database generation phase.
>>>
>>> the problem is the
On Mon, 18 Sep 2000, Olivier Galibert wrote:
> On Mon, Sep 18, 2000 at 05:51:43PM -0700, Linus Torvalds wrote:
> > Why would this not have happened for a module?
> >
> > I agree that the thing looks fishy. But this is not new code, and it has
> > worked previously. What changed?
>
> Maybe
On Mon, Sep 18, 2000 at 05:51:43PM -0700, Linus Torvalds wrote:
> Why would this not have happened for a module?
>
> I agree that the thing looks fishy. But this is not new code, and it has
> worked previously. What changed?
Maybe nobody ever insmod'ed a module for a scsi device they don't
In message <[EMAIL PROTECTED]> you write:
> * Mark Salisbury <[EMAIL PROTECTED]> [000918 07:32]:
> > the source file linux/fs/hpfs/super.c
> >
> > from kernel version 2.4-test8 causes cscope to core dump during the database
> > generation phase.
> >
> > the problem is the extremely long
Tigran Aivazian <[EMAIL PROTECTED]> said:
[...]
> did you try this patch?
>
> --- linux/drivers/pci/pci.c Mon Sep 18 12:35:11 2000
> +++ work/drivers/pci/pci.cMon Sep 18 13:12:20 2000
> @@ -714,7 +714,7 @@
>* We need to blast all three values with a single write.
>
ifconfig sit0 up tunnel ::206.123.31.102
SIOCSIFDSTADDR: No buffer space available
Anyone know why it does this? I can't seem to find any documentation on
that error...
Gerhard
--
Gerhard Mack
[EMAIL PROTECTED]
<>< As a computer I find your faith in technology amusing.
-
To
On Mon, 18 Sep 2000, David S. Miller wrote:
>
> The problem is that regardless of the tpnt->present setting, the
> MOD_DEC_USE_COUNT must occur.
>
>And again, why did this not show up with modules?
>
> I have no idea, I'm just the messenger in this case :-)
Hey, I didn't shoot you, I
On Tue, 19 Sep 2000, Tulika Pradhan wrote:
> can i use change the value of KERNELBASE from 0xc000 to 0x ?
> does this cause any problems ?
I'm pretty sure setting KERNELBASE to 0x000 leaves no room at all for
user space, which would suck.
Unless you plan on hacking a lot of
Jaroslav Kysela wrote:
>
> On Tue, 29 Aug 2000, M.H.VanLeeuwen wrote:
>
> > With default BIOS settings, IRQ 5 is unavailable for ISA yet
> > it is being assigned by the ne.c driver and NFS root system
> > doesn't finish booting.
> >
> > Is this a driver problem or a ISAPNP problem?
>
> It is
can i use change the value of KERNELBASE from 0xc000 to 0x ?
does this cause any problems ?
tulika
_
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.
Share information about yourself,
On Mon, 18 Sep 2000, David S. Miller wrote:
>Date: Mon, 18 Sep 2000 21:31:17 -0400 (EDT)
>From: jamal <[EMAIL PROTECTED]>
>
>My testing with the included scheme (#ifdef RAND_LIE) indicates
>that fairness infact goes up; however, the overall throughput when
>only one
On Sun, Sep 17, 2000 at 06:14:11PM -0700, Christoph Lameter wrote:
> With both version I get the "booting linux" message and then the first
> line of the kernel messages. Then its dead. Have tried to change the kernel
> configuration but to no avail.
The problem was that the cputype was set
2.4 does indeed use 32-bit integers for uid and gid in all places, with
the exception of BSD process accounting (for now). Quota should work fine
with UIDs >65535; however, you can not use the full 32 bits of UID due to
the format of the quota file. (you should be fine with hundreds of
thousands
I seem to be able to reliably reproduce it as well. Let me know if I
can be of any help.
On Mon, Sep 18, 2000 at 03:38:28PM +0200, Udo A. Steinberg wrote:
> This should probably be added to the 2.4.x bug-list. Since Pavel
> seems to be able to constantly reproduce it, it should be possible to
>
I finally had a chance to try it out under 2.2.17... no hint of a
problem there. So presumably it is a 2.4.0-testX kernel issue.
I don't know what apt-move does which triggers it, but it seems to do
it quite reliably.
On Sun, Sep 17, 2000 at 12:13:14PM -0500, Gregory T. Norris wrote:
> Do you
On Mon, 18 Sep 2000, David S. Miller wrote:
>
> Did you try to boot these kernels containing scsi devices you
> don't have? I don't see how it could work (actually I do, see
> below).
Hmm..
Why would this not have happened for a module?
I agree that the thing looks fishy. But this is not
> The reload of the address of `p' isn't necessary and gcc is wrong in
> generating it. p is a constant embedded into the .text section ...
It's perhaps not optimal, however I'm not sure that it's wrong. In
any case if you can supply a small standalone test case (i.e. preprocessed
source code)
I apologize for the over 10K email.. consider this documentation ;->
This is cross-posted to l-k; i would prefer the discussions on netdev
or cc netdev (i am not subscribed to l-k)
This is a port against 2.4.0-test8 based on the OLS presentation i made
"Fast Forwarding the Bird" available at:
In article <[EMAIL PROTECTED]> you wrote:
> How about taking a decaying average (loadavg style) of the peak allocation-free
why? I think it is not a bad thing if you have some kind of setting like
"irq heavy system" <-> "applicaion heavy system" even in NT you hve this
slider. The current
Patches for bluesmoke against 2.4.0-test9-pre3.
arch/i386/kernel/traps.c still contains
asmlinkage void reserved(void);
DO_ERROR(18, SIGSEGV, "reserved", reserved)
With a definition of reserved in entry.S. Vector 18 is now used for
machine check, lines removed.
Most C routines called from
On Mon, Sep 18, 2000 at 07:53:04PM -0400, John Wehle wrote:
> What version of gcc? Recently some work was done to improve the handling of
> constant memory.
I'm using 2.95.2 19991024.
Take this small testcase:
#include
int * p;
spinlock_t lock = SPIN_LOCK_UNLOCKED;
extern void dummy(int,
On Mon, Sep 18, 2000 at 08:04:21PM +0200, Julian Anastasov wrote:
>
> Hello,
>
> Everything looks good after test1 except the extra
> '<< 16' in __SI_CODE.
>
> SI_SIGIO is not generated from kernel. The same is for the
> other SI_ consts < 0 not defined with __SI_CODE.
Ok,
In article <[EMAIL PROTECTED]> you wrote:
> (1) An in-kernel resident lump, providing very basic services:
> * file-change notification
this is interesting for other stuff too, i think irix has an interface for
that, i think its an ioctl?
> * unicode string handling/conversion
Please kill this thread.
Linus has stated he does not want a kernel debugger in the standard
kernel. As the maintainer of kdb I accept that decision and will
maintain kdb outside the kernel. Any other discussion is just noise.
-
To unsubscribe from this list: send the line "unsubscribe
'twas user error, apmd does it. mea culpa.
-d
--
"There is a natural aristocracy among men. The grounds of this are
virtue and talents", Thomas Jefferson [1742-1826], 3rd US President
begin:vcard
n:Ford;David
x-mozilla-html:TRUE
Gene did the instruction set architecture along with some others. I think he
was also involved in the i/o architecture.
-Original Message-
From: Joel Jaeggli [mailto:[EMAIL PROTECTED]]
Sent: Monday, September 18, 2000 4:59 PM
To: Marty Fouts
Cc: 'Malcolm Beattie'; [EMAIL PROTECTED]
Date:Mon, 18 Sep 2000 15:58:02 -0700 (PDT)
From: Linus Torvalds <[EMAIL PROTECTED]>
The SCSI stuff is pretty straightforward, and it works for me (and
I also built a kernel with all regular x86-capable SCSI drivers
included, so the others got at least that level of
Gene Amdahl I think...
On Mon, 18 Sep 2000, Marty Fouts wrote:
> I think that more people quote Brooks than have read him and that more
> people know him from the Mythical Man Month than from the POO.
>
> He wasn't, by the way, the principle architect of OS/360; he was the manager
> of the
On Mon, Sep 18, 2000 at 03:41:11PM -0700, John Byrne wrote:
> 1.) Any decision on what the bigger dev_t will be? 16-bit major and
> 16-bit minor, for example?
My old code does something like this:
major = (dev >> 32);
minor = (dev & 0x);
if (!major) {
> I read the asm produced by some of some of my testcases. The current spinlock
> implementation seems to do exactly the _right_ thing in practice and nothing
> more. "memory" was instead causing reloads of constant addresses into registers
> and stuff that shouldn't be necessary (I was infact
I think that more people quote Brooks than have read him and that more
people know him from the Mythical Man Month than from the POO.
He wasn't, by the way, the principle architect of OS/360; he was the manager
of the 360 development organization. I will email a monster cookie to the
first
On Mon, Sep 18, 2000 at 08:56:58PM +0200, Jamie Lokier wrote:
[...making SI_FROMUSER exclude SI_ASYNCIO and SI_TIMER...]
I haven't checked, but I suspect that would break the glibc user space
implementations.
Overall the concept of kernel reserved numbers doesn't make too much
sense as a API
Then I suggest you skip the one paragraph at the beginning of my comment
that wasn't appropriately diplomatic and read the portion that you snipped.
It contains a wee bit of wisdom.
-Original Message-
From: Tigran Aivazian [mailto:[EMAIL PROTECTED]]
Sent: Monday, September 18, 2000 1:36
This will probaly fix a bunch of scsi problems in tytso's list at
linux24.sourceforge.net.
Could people please verify this and send him a note.
Thanks.
--
Torben Mathiasen <[EMAIL PROTECTED]>
Linux ThunderLAN maintainer
http://tlan.kernel.dk
-
To unsubscribe from this list: send the line
Andreas Dilger wrote:
>
> Daniel writes:
> > Alexander Viro wrote:
> > > On Mon, 18 Sep 2000, Andreas Dilger wrote:
> > > > This may actually be a problem in the future... what about shared access
> > > > block devices like FCAL or a distributed filesystem? It has to be
> > > > possible for
Linus Torvalds wrote:
>
> On Mon, 18 Sep 2000, Alexander Viro wrote:
> > That's what makes me unhappy about the current situation + obvious
> > fixes. It works, but the proof is... well, not pretty.
>
> Oh, agreed. I think we should clean up the code. I looked at it yesterday,
> and it
On Mon, Sep 18, 2000 at 03:39:50PM -0700, Linus Torvalds wrote:
> Have you looked at the code it generates? Quite sad, really.
I read the asm produced by some of some of my testcases. The current spinlock
implementation seems to do exactly the _right_ thing in practice and nothing
more.
"J. Dow" wrote:
>
> Jeff et al who might prefer a kernel debugger,
>
> One should note that when a person or critter is backed into a corner
> and pressured hard enough that he makes an "over my dead body"
> level statement more pressure is likely to solidify the position rather
> than change
Ok, there's a test9-pre3 there now..
The SCSI stuff is pretty straightforward, and it works for me (and I also
built a kernel with all regular x86-capable SCSI drivers included, so the
others got at least that level of testing). But there are some non-x86
scsi drivers out there etc, so give it
Attached, for possible inclusion in the Linux kernel, is a patch for the
Linux-2.4.0-test8 kernel that causes core dumps to output appropriate
information for multithreaded programs for use by gdb. Currently only ELF
files are supported but other formats can easily add their own functions
to
Daniel writes:
> Alexander Viro wrote:
> > On Mon, 18 Sep 2000, Andreas Dilger wrote:
> > > This may actually be a problem in the future... what about shared access
> > > block devices like FCAL or a distributed filesystem? It has to be
> > > possible for pages to become non-uptodate in a sane
"H. Peter Anvin" wrote:
>
> Followup to: <[EMAIL PROTECTED]>
> By author:John Byrne <[EMAIL PROTECTED]>
> In newsgroup: linux.dev.kernel
> >
> > Anyway, one of the things I was hoping to find out by going to
> > linux-kernel was if there was anything other than devfs in the offing:
> > such
From: "Jeff V. Merkey" <[EMAIL PROTECTED]>
>
> Marty,
>
> I think they said they could care less about kernel debuggers. Just go
> write one, use Keith's or ours or whatever, and do what you want with
> your Linux development -- Linus doesn't seem to care if you just make a
> fork of Linux or
On Tue, 19 Sep 2000, Andrea Arcangeli wrote:
>
> I think we can remove all the __dummy stuff and put the "memory" in such asm
> statements.
>
> Comments?
Have you looked at the code it generates? Quite sad, really.
Linus
-
To unsubscribe from this list: send the line
linux:~ # gcc -v
Reading specs from /usr/lib/gcc-lib/i486-linux/2.7.2.3/specs
gcc version 2.7.2.3
But no luck :( still hangs on "Booting Linux...". I've rpmmed -e
gcc 2.95 from a Suse 6.4 and installed the gcc 2.7.3 from suse 6.3
It compiles fine, so I think there's another problem :)
The
On Fri, Sep 08, 2000 at 01:41:05PM +0200, Jamie Lokier wrote:
> Casting via __dummy is there so that the "m" (or "=m") memory constraint
> will make that operand refer to the actual object in memory, and not a
> copy (in a different area of memory).
Are you really sure gcc could pass a copy even
On Mon, Sep 18 2000, Torben Mathiasen wrote:
> It just hit me when I touched the send button (yeah right!). I'm basicly
> compiling the same kernel right now.
> Glad we got that in place, otherwise it would have been a long wasted night 8).
>
And just to follow up on my own mail, this patch
On Mon, 18 Sep 2000, Mr. James W. Laferriere wrote:
> Oh God , I hope this doesn't mean what I think it might ?
> Please tell me I am stil going to be able to 'Statically' compile
> in the drivers of my choosing ? Tia , JimL
This discussion is about using one initialization
On Mon, 18 Sep 2000, Torben Mathiasen wrote:
> On Mon, Sep 18 2000, Linus Torvalds wrote:
> > And think about it - if this part didn't work, then loadable SCSI modules
> > would never have worked. And every single distribution I know of basically
> > depends on SCSI drivers being loadable
On Mon, 18 Sep 2000, Elmer Joandi wrote:
> 1. First - it mounted a ufs but showed nothing long time to find the
> 44bsd senseless
> option.
Sigh... Would you prefer six-seven fs types? You see, 4.4 UFS != Slowlaris
UFS. And no, FreeBSD implementation is not happy with it either.
> 2. ok,
Alexander Viro wrote:
>
> On Mon, 18 Sep 2000, Andreas Dilger wrote:
>
> > Alexander writes:
> > > * uptodate pages should never become non-uptodate.
> > > uptodate .. pages ... never have data _older_ than on disk
> >
> > This may actually be a problem in the future... what about
Alexander Viro wrote:
> Looks like I'm taking care of the UFS for a while. Yes, 2.4 is currently
> broken.
2.2.16, migrated FreeBSD to Linux on production system this weekend.
Dreamed that I just leave ufs there without copying the stuff.
1. First - it mounted a ufs but showed nothing
Andrea Arcangeli <[EMAIL PROTECTED]> writes:
> > The only disadvantage I can see is that the new patch doesn't handle
> > consecutive insertions in O(1) time, but then again, the pre-latency
>
> We can still do that by trivially fixing a bit your code. You should first
> check if the new
On Mon, 18 Sep 2000, Torben Mathiasen wrote:
>
> What about the case when scsi is compiled into the kernel with one or
> more host adapters? We have to initialize those right away.
Actually, we don't. It's really equivalent to just having two or
more modules.
>
Mark Salisbury writes:
> the source file linux/fs/hpfs/super.c
>
> the problem is the extremely long printk() string starting on line 280 in the
> function static inline void hpfs_help(void){}
>
> simply breaking up this printk up into several smaller printk's solves the
> problem.
Looking at
On Mon, 18 Sep 2000, Eric Youngdale wrote:
>
> What is the primary objective here - getting rid of #ifdef MODULE, or is
> it removing redundant code for the two paths? Or both?
Both.
As you probably saw, it really started out from fixing this silly bug that
was introduced by mistake
Date:Mon, 18 Sep 2000 16:11:37 +0200
From: Florian Lohoff <[EMAIL PROTECTED]>
This is all Kernel 2.2.17
ioremap is buggy on sparc64 in 2.2.x, but fixing it would break a lot
of drivers. See drivers/net/sk98lin/skge.c, grep for __sparc__, for
how to deal with this problem.
[NB. following may not be relevant as seen on box with known upper 32MB
of 128MB DIMM faulty and not in use via mem=96MB]
Oops obtained when exiting Staroffice 5.2. Relevant procs left in
unkillable state :-
F S UIDPID PPID CLS PRI ADDR SZ WCHAN STIME TTY TIME CMD
144 Z
* Mark Salisbury <[EMAIL PROTECTED]> [000918 07:32]:
> I use cscope version 13.7 (on solaris 2.6)
There is an open sourced version of cscope released under a BSD license at
http://cscope.sourceforge.net/ ...
> the source file linux/fs/hpfs/super.c
>
> from kernel version 2.4-test8 causes
On Mon, Sep 18 2000, Eric Youngdale wrote:
> What is the primary objective here - getting rid of #ifdef MODULE, or is
> it removing redundant code for the two paths? Or both?
>
> I am just trying to get a handle on what is driving this.
Well the code clean-up came as a pleasent side
On Mon, Sep 18 2000, Linus Torvalds wrote:
> Actually, hold off a moment.
>
> It turns out that the MODULE case does all the right things, for all the
> obvious reasons. I'm running a kernel that has the #ifdef MODULE stuff
> just removed, and it seems to be a rather easy approach. It really
On Mon, Sep 18, 2000 at 11:31:09AM -0500, [EMAIL PROTECTED] wrote:
> This patch prevents scsi_ioctl_send_command() from overwriting the SEND
> DIAGNOSTICS (Drive Self Test) reserved bits in cmd[1], as found in SCSI-3.
> Code provided by Michael Landrus of Dell.
>
> Comments are requested. If
>> Network block device seems broken by block device changes (In sec. 11.
To Check)
FWIW...
I have a set of Pentium Pro machines connected by 100 MBit ethernet. I've
been testing the bonnie I/O benchmark over nbd. Using 2.4 kernels up to
test6, bonnie would hang when using backing files 100MB
What is the primary objective here - getting rid of #ifdef MODULE, or is
it removing redundant code for the two paths? Or both?
I am just trying to get a handle on what is driving this.
-Eric
- Original Message -
From: "Linus Torvalds" <[EMAIL PROTECTED]>
To: "Torben
On Sun, Sep 17, 2000 at 08:40:33PM -0700, Larry McVoy wrote:
> On Sun, Sep 17, 2000 at 02:33:40PM -0700, Marty Fouts wrote:
> I'm sort of in the middle. I know BitKeeper very well, and it's actually
> a larger wad of code than the kernel if you toss out the device drivers.
> About the only thing
On Mon, Sep 18, 2000 at 04:39:36PM -0400, Johannes Erdfelt wrote:
> Are you getting any oops'? I ran into a problem where with some devices,
> it would oops on open.
Nah... It turned out to be something REALLY obvious. I was
missing the joydev module. Someone else already pointed it
lest people start shouting at me...
The philosphy behind this patch is:
There are two ways to turn a "guess" into a "fix":
a) to understand why it works
or
b) to make sure it fixes the problem for everyone on the planet and
doesn't break anything...
This time b) seemed easier :)
Regards,
On Mon, 18 Sep 2000, Torben Mathiasen wrote:
>
> Thanks a lot. I've started to do the basics, like getting all subsystems to work
> with the module_init/exit stuff. This of course leds to some
>rewriteting/restructuring
> of the scsi layer. Nothing major though.
Actually, hold off a moment.
Yes, 2.4 has 32bit uid/gid support. No, 2.2 doesn't, but there is a patch
from http://www.engin.umich.edu/caen/systems/Linux. You'll probably have
to do some work to fit the patches into the latest 2.2 kernels though, as
they're no longer being maintained in leu of 2.4.
In addition to running
On Mon, 18 Sep 2000, Derek Wildstar wrote:
> On 18 Sep 2000, Alex Romosan wrote:
>
> I get the same thing with a Xircon realport 10/100/modem card. Works
> great in test9-pre1 and test8.
>
> -dwild
>
did you try this patch?
--- linux/drivers/pci/pci.c Mon Sep 18 12:35:11 2000
+++
On Mon, Sep 18, 2000, Michael H. Warfield <[EMAIL PROTECTED]> wrote:
> Hello all...
>
> No joy with this joystick and I'm not sure what I'm doing wrong.
>
> I just received a Logitech USB Wingman Force Joystick. I have
> the iforce module compiled and loaded and the it recognizes
> Hello all...
>
> No joy with this joystick and I'm not sure what I'm doing wrong.
>
> I just received a Logitech USB Wingman Force Joystick. I have
> the iforce module compiled and loaded and the it recognizes the USB
> joystick.
>
...
> Trouble is "jstest /dev/js0" says
On Mon, Sep 18 2000, Eric Youngdale wrote:
> Historical. SCSI was made modular very early on when the modules
> technology was pretty primative. As time has gone on, the two
> initialization paths have converged, and now they are essentially redundant.
>
Thats understandable.
> The
On Mon, Sep 18, 2000 at 04:50:55AM -0700, Andre Hedrick wrote:
[ext2 errors and fdisk complaints on 2.4.0test8, patched?]
Andre,
(i) Geometry does not play any role in the functioning of Linux -
it is only a matter to LILO and fdisk. So, if you meet
a strange geometry, then that is surprising,
Hi,
This patch against 2.2.18-pre9 moves the USB input drivers into the same
directory structure that they are in for 2.4.x, and it also updates the
drivers to their latest versions.
This patch was done by Franz Sirl (thanks Franz for doing this!)
I've included it in two forms here:
On 18 Sep 2000, Alex Romosan wrote:
I get the same thing with a Xircon realport 10/100/modem card. Works
great in test9-pre1 and test8.
-dwild
> i have the same problem with the same setup. from the logs, it looks
> like this is due to a PCI resource allocation conflict:
>
> Sep 17 15:56:33
On Sun, Sep 17, 2000 at 10:37:51AM -0700, Linus Torvalds wrote:
>
> Ok. I think we're getting to the point where there are no major known
> bugs. That means that as of the final 2.4.0-test9 I will no longer accept
> any patches that don't have a critical problem (as defined by Teds list)
>
Hi!
While developing the next versions, I found two 'obvious bugs' in the
2.1 version. They are not very harmful. The attached patch fixes them.
--
Vojtech Pavlik
SuSE Labs
--- linux/drivers/ide/via82cxxx.c.old Mon Sep 18 22:10:10 2000
+++ linux/drivers/ide/via82cxxx.c Mon Sep 18
On Mon, 18 Sep 2000, Alan Cox wrote:
> > All I wanted was a function that allows the driver to decide that which
> > needs to be enabled.
> >
> > pci_enable_device(struct pci_dev *dev, byte enable_mask)
> >
> > This would allow drivers to enable that which it needs and not weird out
> > the
On Mon, 18 Sep 2000, Alexander Viro wrote:
> >
> > but should instead be
> >
> > static int make_buffer_uptodate(struct page *page, struct buffer_head * bh)
> > {
> > if (Page_Uptodate(page)) {
> ^^^
> >
> reproduce the exact kernel configuration of my running 2.2.14 system
> and a 2.2.17 kernel. (It would be extremely useful to have a pointer
> to a tool which would duplicate the configs rather than going through
> the manual process of configuring the kernel build).
cp .config new_kernel_dir
That's to fs/buffer.c, generic_file_write() part will go
separately (it's a separate bug actually - if copy_from_user() in
generic_file_write() fails we mark page as not-uptodate; if memory
pressure will drop the buffer_heads attempts to read will blow the page
contents away).
If a process executes an int3 (breakpoint) instruction while
another process is attaching to it, the SIGTRAP can be lost. This bug
is present in 2.4.0-test8 and 2.2.14.
Below is a program that demonstrates this behavior. It forks a
child that repeatedly executes an int3 and handles
On Mon, Sep 18, 2000 at 08:47:55PM +0100, Alan Cox wrote:
> > The drivers/net/wan/comx.c #errors if it is compiled in a kernel
> > without procfs support. The following patch updates the documentation
> > to state this. I have cc'ed the maintainer so he can comment.
>
> It does really need
Hi!
> Ok. I think we're getting to the point where there are no major known
> bugs. That means that as of the final 2.4.0-test9 I will no longer accept
> any patches that don't have a critical problem (as defined by Teds list)
> associated with them.
> So when you send me a patch, either bug
> The drivers/net/wan/comx.c #errors if it is compiled in a kernel
> without procfs support. The following patch updates the documentation
> to state this. I have cc'ed the maintainer so he can comment.
It does really need procfs, but I'd say its better to put them depenancy
in the Config.in if
Hi, I've noticed that there are quite a few hardware performance counter
patches (which allow access to things like the Pentium Model Specific
Registers for gathering profiling info) floating around, including Rabbit
(http://www.scl.ameslab.gov/Projects/Rabbit/), Richard Gooch's patches, and
PAPI
Hello all...
No joy with this joystick and I'm not sure what I'm doing wrong.
I just received a Logitech USB Wingman Force Joystick. I have
the iforce module compiled and loaded and the it recognizes the USB
joystick.
/var/log/message:
Sep 18 15:09:32 alcove kernel: usb.c:
make[4]: Entering directory `/disks/hdb/src/kernel/linux/drivers/char/drm'
gcc -D__KERNEL__ -I/disks/hdb/src/kernel/linux/include -Wall -Wstrict-prototypes -O2
-fomit-frame-pointer -pipe -march=i686 -fno-strict-aliasing-DEXPORT_SYMTAB -c
r128_drv.c
In file included from r128_drv.c:33:
"Dunlap, Randy" <[EMAIL PROTECTED]> said:
[]
> > Good thing I promised Ted to bring another bottle of
> > that Brazillian liquor to the next event we meet ;)
> Rik, does it have to be Brazilian liquor?
> I still have patches for 2.4.0-final also.
You'd have to ask Ted...
BTW folks,
Hi.
The following patch cleans up some minor stuff in mm/filemap.c:
o transmorphs tsk->state=XX -> __set_task_state
o removes the wait argument to filemap_write_page (it is not used)
and cleans up the two places filemap_write_page is called.
o cleans up some comments.
---
On Mon, 18 Sep 2000, Alexander Viro wrote:
> Except that the only reason why check for page being uptodate is correct
> is that for such pages we are guaranteed that buffer ring will not be
> dropped when page contatins data newer than on disk.
Ugh. Translation:
The only reason why the
1 - 100 of 368 matches
Mail list logo
