>I agree that if you give a mentally unbalanced person a firearm, they might
>shoot themselves with it. I am suggesting we take away their firearm. Write
>support for NTFS is useful for migrating from Linux to NT, R/O support is
>useful for migrating NT to Linux. We won't be giving anything
Oh, I forgot to mention: I use a slight modification to your patch: you
left some functions as "__init/__initdata" functions/data even though they
are should definitely be __devinit/__devinitdata for all the hotplug
stuff. So the thing that works for me has had a global search-and-replace
to
On Sat, 9 Dec 2000, Theodore Y. Ts'o wrote:
>
>I didn't have time to do more than just quickly apply the patch and leave
>in a hurry, but my Vaio certainly recognized the serial port on the combo
>cardbus card I have with this patch. Everything looked fine - I got a
>message
On Wed, Oct 04, 2000 at 12:05:32PM -0400, John M. Flinchbaugh wrote:
> basically, when i added ram to my linux-2.4.0-test8 box taking it from
> 96M to 192M of ram. esd over tcpip started popping, hesitating,
> distorting. if i limit the memory at kernel boot to 127M (and no
The popping and
Hi,
I've notices weird compile time failures etc on test12-pre7, especially
running more than 2 simultaneous processes...
but most noticeable is the time it takes to run ldconfig, after the
first time test11 takes less than 1 second, test12-pre7 takes ~40
seconds.
both were run immediately
I'd like to see these patches as well. They may be useful on the iPAQ
(and similar hardware like my Yopy here... ;-)
I wish some hardware vendor out there would build an x86 box that used
memory addressable flash from 0 up and RAM up higher. A simple Linux
kernel boot loader could then replace
Hi,
I got this BUG report after test12-pre7 soft locked on my NFS server,
all nfsd's in D state and I had to reboot and system was rebuilding the
ide RAID1 arrays.
NFS client test12-pre7 was rebooted as well, root logged in, and ran ldconfig
NFS server BUG'd out
Hand copied OOPS hope too much
Peter Berger <[EMAIL PROTECTED]> writes:
>
> Hi. I have the following tiny test program which fails dramatically,
> using pthreads, in a number of fascinating ways on various version of
> linux, using various versions of glibc, under various (current) versions
> of GDB.
It looks like a GDB
I don't remember having the same problem months (6?) ago when
I built my first Kernel with this enabled (well, maybe I never
touched the key).
When built into the Kernel, by only pressing the
PrintScreen/SysRq the current application is terminated (tested
on a console and GNU screen). Is this
> > * We can now write device drivers in perl, and let them run on the iMAC
> > across the hall from you. :)
>
> Why would you *ever* want to write a device driver in perl???
So you can easily facilitate opportunities for viruses ;)
-d
begin:vcard
n:Ford;David
x-mozilla-html:TRUE
Date: Fri, 8 Dec 2000 13:27:51 -0800 (PST)
From: Linus Torvalds <[EMAIL PROTECTED]>
I didn't have time to do more than just quickly apply the patch and leave
in a hurry, but my Vaio certainly recognized the serial port on the combo
cardbus card I have with this patch. Everything
On Sat, 9 Dec 2000, Mohammad A. Haque wrote:
> It was just an example. Basically, you'd be able to do in with just
> about any language that has ORBit bindings.
Yeah... "Infinitely extendable API" and all such. Roughly translated
as "we can't live without API bloat". Frankly, judging by the
David Woodhouse ([EMAIL PROTECTED]) wrote...
> Can you reproduce it with bcrl's patch below:
Did nothing for me. gcc still got a sig11 after a while.
Took three runs of 'make bzImage' before it completed.
I wondered if I'd been unlucky enough to have been sent a
replacement K6-2 which was
Chris Lattner wrote:
> This email is here to announce the availability of a port of ORBit (the
> GNOME ORB) to the Linux kernel. This ORB, named kORBit, is available from
> our sourceforge web site (http://korbit.sourceforge.net/). A kernel ORB
> allows you to write kernel extensions in CORBA
It was just an example. Basically, you'd be able to do in with just
about any language that has ORBit bindings.
Ben Ford wrote:
> Why would you *ever* want to write a device driver in perl???
--
=
Mohammad A. Haque
On Fri, 8 Dec 2000, Linus Torvalds wrote:
> Looking more at this issue, I suspect that the easiest pretty solution
> that everybody can probably agree is reasonable is to either pass down the
> end-of-io callback to ll_rw_block as you suggested, or, preferably by just
> forcing the _caller_ to
Michael Rothwell wrote:
>
> Alan Cox wrote:
> >
> > > Why is 2.2.18 proc_fs.c different than both 2.2.17 and 2.4.0? Cox, would
> > > you accept a patch that makes 2.2.18 define create_proc_info_entry and
> > > related functions the same way that 2.4.0 does?
> >
> > Send me a diff and I'll be
Marc,
if more / other information is needed let me know.
I'll try to go through the points as described in
/usr/src/linux/REPORTING-BUGS:
[1.] Bug reported on system startup.
[2.] no obvious problem detected besides this message
besides apic errors on both CPUs.
[3.] kernel BUG at
Donald Becker <[EMAIL PROTECTED]> said:
[...]
> The best way to check for this buggy chipset was to check for a 486
> processor. There are very few 486 chips on non-buggy motherboards, and the
> performance impact of shorter PCI bursts is minimal given the slow speed of
> the 486.
Enable it
Alan,
The mouse problems have gone away with the 2.2.18-25 pre-patch. I
am not seeing the problems anymore on the affected systems. I am
trying this evening to apply the 2.4 patch sent to me to see if it
helps with the page cache corruption problem with fork().
Jeff
-
To unsubscribe from
Matthew Galgoci wrote:
>
> Hi Folks,
>
> I am running the 2.4.0test12pre7 kernel on my laptop computer, and
> I'm having some rather interesting problems.
>
> For the longest time, usb never worked on this machine. As of the
> happy patch that enabled bus mastering for usb controllers, it
>
I reported this earlier. Now with 2.2.18pre25 and today's CVS is is past
the place where it crashed.
Sorry for the red herring.
--
Horst von Brand [EMAIL PROTECTED]
Casilla 9G, Vin~a del Mar, Chile +56 32 672616
-
To unsubscribe from
On Fri, 8 Dec 2000 16:53:16 -0800,
"David D.W. Downey" <[EMAIL PROTECTED]> wrote:
>When building the kernel things buld fine with no errors other than the
>standard warnings generated by -Wall. Running the make dep bzImage modules
>modules_install command completes. Nothing big there, but when i
Alan Cox wrote:
>
> > Why is 2.2.18 proc_fs.c different than both 2.2.17 and 2.4.0? Cox, would
> > you accept a patch that makes 2.2.18 define create_proc_info_entry and
> > related functions the same way that 2.4.0 does?
>
> Send me a diff and I'll be happy to
Here it is, both inlined and as
On Fri, Dec 08, 2000 at 04:19:45PM -0800, Matthew Jacob wrote:
>
> > >
> > > On Fri, 8 Dec 2000, Alan Cox wrote:
> > >
> > > > > Yes, and I believe that this is what's broken about the SCSI midlayer. The
>the
> > > > > io_request_lock cannot be completely released in a SCSI HBA because the
On Fri, Dec 08, 2000, Johannes Erdfelt <[EMAIL PROTECTED]> wrote:
> On Fri, Dec 08, 2000, David Woodhouse <[EMAIL PROTECTED]> wrote:
> > On Thu, 7 Dec 2000, Johannes Erdfelt wrote:
> >
> > > Could you try the alternate UHCI driver? You may need to disable the
> > > UHCI driver you have
On Fri, Dec 08, 2000, David Woodhouse <[EMAIL PROTECTED]> wrote:
> On Thu, 7 Dec 2000, Johannes Erdfelt wrote:
>
> > Could you try the alternate UHCI driver? You may need to disable the
> > UHCI driver you have configured for the option to become visible.
>
> Differently broken:
> uhci:
Hi guys,
Not sure if this is the right list for this, but I'll spew this forward
too you. Redirects to right place is definitiely welcome. Since I added the
reiserfs kernel patch , I figured I'd mention it.
Problem:
When building the kernel things buld fine with no errors other than the
Alan wrote :
> struct wireless_physical
> struct wireless_80211
> struct wireless_auth
Please do not underestimate 802.11 (and others). Even two
cards based on the same MAC controller can have very different way
In article <[EMAIL PROTECTED]> you wrote:
> This email is here to announce the availability of a port of ORBit (the
> GNOME ORB) to the Linux kernel.
OMG you guys are so cool :)
Hey, this is real craftsmanship (not sure if it useful :)
Does this revamp the Micro Kernel Discussin? ONLY KIDDING
This is a second posting, I just got back onto the
kernel mailing list. The first was sent via dejanews. So If this looks
familiar... It is. Ignore It.
Hi all, I seem to be having some problems
configuring kernels 2.2.16 and 2.2.17 to nfsroot boot. I have two machines at a
friends house I
On Sat, 9 Dec 2000, Alan Cox wrote:
> > Just in case you didn't catch it: this is not a PCI v2.0 vs. v2.1 issue.
> > The older Tulips work great with PCI v2.0 and v2.1. The bug is with longer
> > bursts and a specific i486 chipset/motherboard.
>
> Which chipset. I can then add it to the PCI
Ivan Passos wrote :
> For synchronous network interfaces, besides configuring network parameters
> such as IP address, netmask, MTU, etc., the system should also configure
> parameters specific to these sync i/f's, such as media (e.g V.35, X.21,
> T1, E1), clock (internal or external, and
> > You can drop it with spin_unlock_irq and that is fine. I do that with no
> > problems in the I2O scsi driver for example
>
> I am (like, I think I *finally* got locking sorta right in my QLogic driver),
> but doesn't this still leave ints blocked for this CPU at least?
spin_unlock_irq
> >
> > On Fri, 8 Dec 2000, Alan Cox wrote:
> >
> > > > Yes, and I believe that this is what's broken about the SCSI midlayer. The the
> > > > io_request_lock cannot be completely released in a SCSI HBA because the flags
> > >
> > > You can drop it with spin_unlock_irq and that is fine. I do
>
> I am actually concerned about the following case:
>
> The add_request ON CPU_1 function calls
> spin_lock_irqsave(_request_lock,flags);
>
> Our I/O Function unlocks the spinlock and goes to sleep.
>
> Finally, the add_request function, NOW ON CPU_2 calls
>
> On Fri, 8 Dec 2000, Alan Cox wrote:
>
> > > Is there anything else I can contribute?
> >
> > The latitude and longtitude of the bios writers current position, and
> > a ballistic missile.
>
> ;-)
>
> > Please boot 2.2.18pre24 (not pre25) [...]
>
> Please pardon the naive question: is
With the purpose of having two printers connected to my Linux server I
bought a PCI (single port) parallel port card thinking that installation
would be straightforward.
Parport was already compiled into the kernel (version 2.2.17), and lp is
a module.
After looking at the output from 'lspci
On Fri, Dec 08, 2000 at 04:03:58PM -0800, Matthew Jacob wrote:
>
>
> On Fri, 8 Dec 2000, Alan Cox wrote:
>
> > > Yes, and I believe that this is what's broken about the SCSI midlayer. The the
> > > io_request_lock cannot be completely released in a SCSI HBA because the flags
> >
> > You can
>
>
>
> On Fri, 8 Dec 2000, Alan Cox wrote:
>
> > > Yes, and I believe that this is what's broken about the SCSI midlayer. The the
> > > io_request_lock cannot be completely released in a SCSI HBA because the flags
> >
> > You can drop it with spin_unlock_irq and that is fine. I do that with
> Just in case you didn't catch it: this is not a PCI v2.0 vs. v2.1 issue.
> The older Tulips work great with PCI v2.0 and v2.1. The bug is with longer
> bursts and a specific i486 chipset/motherboard.
Which chipset. I can then add it to the PCI quirks and we can do it nicely
in 2.4 so that
I am running the 2.2.14 linux kernel, and doing
buffered writes to disk. Whenever kupdate runs, I
notice that the I/Os freeze up, sometimes taking 10-20
seconds to complete. Are there any patches to the
kernel to prevent thsi kind of behaviour ? I am using
the standard bdflush parameters. Is this
On Fri, 8 Dec 2000, Alan Cox wrote:
> > Yes, and I believe that this is what's broken about the SCSI midlayer. The the
> > io_request_lock cannot be completely released in a SCSI HBA because the flags
>
> You can drop it with spin_unlock_irq and that is fine. I do that with no
> problems in
> So you're saying that you got this to work? Because I certainly couldn't
> get it working with a higher version either. I would really love a
I read straight down it anf realised you referenced obsolete versions of
tg->created and thus broadcast incorrectly
> I apologize for my ignorance --
I'll try.
Jeff
On Fri, Dec 08, 2000 at 10:24:55PM +, David Woodhouse wrote:
> On Fri, 8 Dec 2000, Jeff V. Merkey wrote:
>
> > I have not seen it on UP systems either. I only see it on SMP systems.
> > After trying very hard last night, I was able to get my 4 x PPro system to
> > do it
> That could even be automated when this little patch (against -test11, but
> -test12pre works too) is applied...
> +# MANPATH specifies where to install the manpages created from
> +# inline documentation
> +#
> +
> +MANDIR := /usr/share/man
> +
End user installed so
>Well, I've found that VM-global patch before, of course. Until now, the
> last version was against pre18. Since I do not know the exact rules for
> including new things into Alan's tree, I thought that VM-global patch was
> already included in pre24. Sorry for my lack of experience. ;-)) I
> > {0x414B4D01, "Asahi Kasei AK4540 rev 1", NULL},
> > + {0x41445303, "Yamaha YMF" , NULL},
>
> Are you sure it's correct? I am almost certain that no YMFxxx
Its definitely wrong
> has on-chip AC97. I'd like to see a document that allows you
> the change quoted above.
4144
On Thu, 7 Dec 2000, Johannes Erdfelt wrote:
> Could you try the alternate UHCI driver? You may need to disable the
> UHCI driver you have configured for the option to become visible.
Differently broken:
uhci: host controller process error. something bad happened
uhci: host
> Loading the module would cause a very loud monotone
> squeal, like some kind of theft detection device. The computer
Thats actually a generic bug in both ALSA and the kernel AC97 driver
(fixed in 2.2 and by Linus in 2.4test). It is feedback between the microphone
and speakers
-
To
> Yes, and I believe that this is what's broken about the SCSI midlayer. The the
> io_request_lock cannot be completely released in a SCSI HBA because the flags
You can drop it with spin_unlock_irq and that is fine. I do that with no problems
in the I2O scsi driver for example
-
To unsubscribe
In article <[EMAIL PROTECTED]> you wrote:
> That could even be automated when this little patch (against -test11, but
> -test12pre works too) is applied...
Ok, I should actually attach the test11-final patch ;)
Christoph
--
Whip me. Beat me. Make me maintain AIX.
diff -uNr
David Woodhouse <[EMAIL PROTECTED]> said:
[...]
> I quote from the X devel list, which perhaps I shouldn't do but this is
> hardly NDA'd stuff:
> On Mon 20 Nov 2000, [EMAIL PROTECTED] said:
> > I have seen random crashes on dual P3 BX boards (Tyan) and dual Xeon
> > GX boards (Intel).
On Fri, 8 Dec 2000 14:14:31 -0500,
"Jean-Francois Nadeau" <[EMAIL PROTECTED]> wrote:
>Dec 7 17:01:54 trinity kernel: EIP:
>0010:[update_vm_cache_conditional+138/328]
You are letting klogd convert the oops, it is broken. Change klogd to
run with "klogd -x", reproduce the oops and get a clean
> * put cable in *
>
> eth0: card reports no RX buffers.
> eth0: card reports no resources.
> eth0: card reports no RX buffers.
> eth0: card reports no resources.
you know, this might be entirely unrelated, but i had the exact same type of
problem with a brand new machine running a not-so-brand
On Fri, Dec 08, 2000 at 11:24:56PM +0200, Matan Ziv-Av wrote:
> I have an IBM drive, DTLA-307075 (75GB), and a bios that hangs with
> large disks. I use a jumper to clip it to 32GB size, so the bios can
> boot into linux. The problem is that WIN_READ_NATIVE_MAX returns 32GB,
> and not the true
On Fri, 8 Dec 2000, Alexander Viro wrote:
>
> I'm quite aware of that fact ;-) However, you said
>
>On the other hand, I have this suspicion that there is an even simpler
>solution: stop using the end_buffer_io_sync version for writes
>altogether.
>
> If that happens (i.e. if
Hi Linus,
Linus Torvalds <[EMAIL PROTECTED]> writes:
> On 8 Dec 2000, Christoph Rohland wrote:
> >
> > here is my first shot for cleaning up the shm handling. It did
> > survive some basic testing but is not ready for inclusion.
>
> The only comment I have right now is that you probably should
On Fri, Dec 08, 2000 at 11:34:51AM -0800, Mark Vojkovich wrote:
>
>
> On Fri, 8 Dec 2000, David Woodhouse wrote:
>
>Some additional data points. It goes away on UP 2.4 kernels.
> Also, I can't recall seeing this problem on IA64. Maybe it's still
> there on IA64 and I just haven't been
On 8 Dec 2000, Christoph Rohland wrote:
>
> Linus Torvalds <[EMAIL PROTECTED]> writes:
> > On 8 Dec 2000, Christoph Rohland wrote:
> > >
> > > here is my first shot for cleaning up the shm handling. It did
> > > survive some basic testing but is not ready for inclusion.
> >
> > The only
Ion Badulescu wrote:
>
> Ok. Can you send me the entire dump? Also, it would be helpful if you
> could try to determine when exactly it happens (upon insmod, upon ifconfig
> up, or upon receiving some packets later).
I have the eepro driver compiled into a monolithic kernel. After rebooting
a
On Fri, 8 Dec 2000 07:58:06 -0500 (EST),
"Richard B. Johnson" <[EMAIL PROTECTED]> wrote:
>Too many people just want to argue without even reading what they
>are arguing against. Again, I implied nothing. I said;
>
> (1) User traps, CPL3, stack for trap is in CPL0.
> (2) CPL0 has stack-fault (bad
Mike Kravetz wrote:
>
> George,
>
> I can't answer your question. However, have you noticed that this
> lock ordering has changed in the test11 kernel. The new sequence is:
>
> read_lock_irq(_lock);
> spin_lock(_lock);
>
> Perhaps the person who made this change could
On Fri, 8 Dec 2000, Jeff V. Merkey wrote:
> I have not seen it on UP systems either. I only see it on SMP systems.
> After trying very hard last night, I was able to get my 4 x PPro system to
> do it with 2.4.0-12. It seems related to loading in some way. If you
> have more than two
On Fri, 8 Dec 2000, Linus Torvalds wrote:
>
>
> On Fri, 8 Dec 2000, Alexander Viro wrote:
> >
> > Erm... So you want to make ->commit_write() page-unlocking? Fine with me,
> > but that will make for somewhat bigger patch. Hey, _you_ are in position
> > to change the locking rules, freeze or
Petr,
It ran fine on my stock Mandrake 7.2 system - linux-2.2.17-21mdk and
glibc-2.2-5mdk. The program ran fine in both environments - command line
and gdb-5.0. Loadavg creeps up slowly as the program continues to run. At
thread #37000, loadavb is 3.65. The ps command indicates 4 threads
Linus Torvalds wrote:
>
> On Fri, 8 Dec 2000, Daniel Phillips wrote:
> >
> > [ flush-buffers taking the page lock ]
> >
> > This is great when you have buffersize==pagesize. When there are
> > multiple buffers per page it means that some of the buffers might have
> > to wait for flushing just
-
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/
Hi,
I was a GlobeCom 2 weeks ago, and I noticed a few articles
relevant to Linux networking that you might be interested in
reading...
On ECN :
--
Archan Misra, John Baras & Teunis Ott. Generalised TCP
Congestion Avoidance and its Effect on Bandwidth Sharing and
Petr,
Thanks for testing this and finding a working counterexample! I am still
professionally interested to know if the difference is that you are
running a 2.4 kernel, or the glibc. Anyone running a 2.2 kernel with
glibc 2.2 want to drop me a line?
-Peter
(gdb) run
...
[New Thread 25452]
On Fri, 8 Dec 2000 11:30:06 -0500 (EST),
"Georg Nikodym" <[EMAIL PROTECTED]> wrote:
>But since you seem to and while we're doing extreme surgery, why have
>klogd at all? Every other unix, kernel messages are handled by the
>syslog system. What problem did klogd solve and does that problem
Resent patch, hope that it will be acknowledged or discussed.
Xuân. :o)
Hello,
I discovered a bug in netfilter and worked the last 4 days to track it
down (I'm not a kernel hacker...):
Symptoms:
"Sometimes" the ip_conntrack module won't unload. rmmod or modprobe -r
would stay unkillably
On Fri, 8 Dec 2000, Alan Cox wrote:
> > Is there anything else I can contribute?
>
> The latitude and longtitude of the bios writers current position, and
> a ballistic missile.
;-)
> Please boot 2.2.18pre24 (not pre25) [...]
Please pardon the naive question: is pre-patch-2.2.18-24 to be
On Fri, Dec 08, 2000 at 01:27:51PM -0800, Linus Torvalds wrote:
>
> (Of course, I use tulip instead of epic100, so maybe there's an epic
> driver bug, but it's definitely hotplug-aware).
There could be a problem in the epic driver; I've never had a card
that uses this driver and have only
On Fri, 8 Dec 2000, Matan Ziv-Av wrote:
>
> Hi,
>
>
> I have an IBM drive, DTLA-307075 (75GB), and a bios that hangs with
> large disks. I use a jumper to clip it to 32GB size, so the bios can
> boot into linux. The problem is that WIN_READ_NATIVE_MAX returns 32GB,
> and not the true size,
I didn't have time to do more than just quickly apply the patch and leave
in a hurry, but my Vaio certainly recognized the serial port on the combo
cardbus card I have with this patch. Everything looked fine - I got a
message saying it found a 16450 on ttyS4 when I plugged the card in.
Ted, I
On Fri, 8 Dec 2000, Daniel Phillips wrote:
>
> [ flush-buffers taking the page lock ]
>
> This is great when you have buffersize==pagesize. When there are
> multiple buffers per page it means that some of the buffers might have
> to wait for flushing just because bdflush started IO on some
Hi,
I have an IBM drive, DTLA-307075 (75GB), and a bios that hangs with
large disks. I use a jumper to clip it to 32GB size, so the bios can
boot into linux. The problem is that WIN_READ_NATIVE_MAX returns 32GB,
and not the true size, and even trying to set the correct size with
WIN_SET_MAX
Date:Fri, 8 Dec 2000 15:36:35 -0500 (EST)
From: Mark Hahn <[EMAIL PROTECTED]>
can't we just change rss to count pages?
This is what it does now.
or are we worried about rss's over ~16 TB?
If we weren't, we could just use an atomic_t for this problem.
We can't.
This patch
> Er... Well, the traditional solution has been "don't build it into your
> kernel if you don't want it", but in the case of stock kernels, that
> isn't always an option, I suppose. Theoretically, the two devices
> shouldn't step on each other, but this is a computer. Theory is so far
> removed
This email is here to announce the availability of a port of ORBit (the
GNOME ORB) to the Linux kernel. This ORB, named kORBit, is available from
our sourceforge web site (http://korbit.sourceforge.net/). A kernel ORB
allows you to write kernel extensions in CORBA and have the kernel call
into
Jeff Garzik wrote:
> Clayton Weaver wrote:
>>>
>> Shouldn't the setting of the CSR0 value for x86 switch between normal
>> (0x01A08000) and cautious (0x01A04800) based on some notion of
>> what generation of pci bus is installed rather than what cpu the kernel
>> is compiled for?
No, you
On Fri, 8 Dec 2000, Udo A. Steinberg wrote:
> > + /* disable advertising the flow-control capability */
> > + sp->advertising &= ~0x0400;
> > + mdio_write(ioaddr, sp->phy[0] & 0x1f, sp->advertising);
>
>
On Fri, 08 Dec 2000, Linus Torvalds wrote:
> Btw, I also think that the dirty buffer flushing should get the page lock.
> Right now it touches the buffer list without holding the lock on the page
> that the buffer is on, which means that there is really nothign that
> prevents it from racing with
Hi.
The following patch makes a 'defined but not used' warning go
away when compiling drivers/net/irda/w83977af_ir.c without
modular support (kernel 240t12p7). It also removes some unneeded
zero initializations.
--- linux-240-t12-pre7-clean/drivers/net/irda/w83977af_ir.c Wed Nov 22
Hi.
This patch makes a 'defined but not used' warning go away when compiling
drivers/net/tokenring/smctr.c without module support (kernel 240t12p3).
(It should apply cleanly.)
--- linux-240-t12-pre3-clean/drivers/net/tokenring/smctr.c Sat Nov 4 23:27:09
2000
+++
Exactly, and you wouldn't set DPL=3 for interrupt 8 since a double-fault
can only occur from ring 0..
Richard Moore - RAS Project Lead - Linux Technology Centre (PISC).
http://oss.software.ibm.com/developerworks/opensource/linux
Office: (+44) (0)1962-817072, Mobile: (+44) (0)7768-298183
IBM
Hi.
(Does anyone know the maintainer of this code?)
When compiling drivers/net/rclanmtl.c (240t12p3) I get a warning about
incompatible pointer assignment. As far as I can tell it has appeared
because PU32 has been changed to __u32* since test9 (where it was an
unsigned long*). The following
Hello!
I just found two serious bugs in the YMF PCI legacy driver (i.e. the
driver that puts it to the Sound Blaster compatible mode).
pci_unregister_driver() was not called from the cleanup routine, which
caused a recoverable oops while running /sbin/lspci.
Also some module parameters were
Hi.
The following patch makes a 'defined but not used' warning go away
when compiling drivers/char/random.c without sysctl support (240t12p3).
(but should apply cleanly). I am aware that there is a sysctl section
of this code, but the function seems to belong where it is. I would be
happy to
Hi.
The following patch makes some 'defined but not used' warnings go
away when compiling drivers/char/mxser.c without CONFIG_PCI (240t12p3).
It should apply cleanly.
--- linux-240-t12-pre3-clean/drivers/char/mxser.c Wed Nov 22 22:41:39 2000
+++ linux/drivers/char/mxser.c Wed Nov 29
Hallo,
at startup of 2.4.0-test12pre7 I receive a bug-message as part of the
following boot.msg. I hope this will be helpfull. If you need more info, let
me know.
kind regards
Norbert
snip --
kernel BUG at buffer.c:827!
> No no. That's that the whole point of a gate. You make a controlled
> transition to ring 0 including stack switching. There are complex
> protection checking rules, however as long as the DPL of the gate
> descriptor is 3 then ring 3 is allowed to make the transition to ring 0. A
> stack fault
Hi.
The following patch makes some 'defined but not used' warnings go away
when compiling drivers/char/moxa.c without CONFIG_PCI (240t12p3). It should
apply cleanly.
--- linux-240-t12-pre3-clean/drivers/char/moxa.cWed May 3 10:45:18 2000
+++ linux/drivers/char/moxa.c Wed Nov 29
> The following patch moves the page_table_lock in mm/* to cover the
> modification of mm->rss in 240-test12-pre7. It was inspired by a
can't we just change rss to count pages?
or are we worried about rss's over ~16 TB?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel"
Ion Badulescu wrote:
> The fact that apparently only the people using 82559 chips are seeing this
> seems to confirm my analysis above.
>
> If you could try the attached patch (and maybe pass it onto the other
> people who are experiencing this problem), that would be great.
> +
Hi.
The following patch moves the page_table_lock in mm/* to cover the
modification of mm->rss in 240-test12-pre7. It was inspired by a
similar patch from davej(?) which covered too much, AFAIR. The item
is on Tytso's ToDo list.
Please comment.
diff -Naur
On 8 Dec 00 at 14:43, Peter Berger wrote:
> > tg->created may be out of date
> ...
> > You can create it, count it, then up tg->created out of order
>
> Well, you're right, but this is picking lint. Making this change (see
> http://peterb.telerama.com/thread-test.c for the corrected
Hi Peter.
On Tue, 5 Dec 2000, H. Peter Anvin wrote:
> Linus Torvalds wrote:
>> Actually, I bet I know what's up.
>>
>> Want to bet $5 USD that suspend/resume saves the keyboard A20 state,
>> but does NOT save the fast-A20 gate information?
>>
>> So anything that enables A20 with only the fast
Hi.
The following patch removes a 'defined but not used' warning from drivers/
new/hp100.c when compiling without CONFIG_PCI (240t12p3). It should apply
cleanly.
--- linux-240-t12-pre3-clean/drivers/net/hp100.cSat Nov 4 23:27:07 2000
+++ linux/drivers/net/hp100.c Sat Dec 2 16:07:27
1 - 100 of 420 matches
Mail list logo
