One option, if there's no bespoke mechanism is to use DPorbes and or Linux
Trace Toolkit to set up a trace of file system apis. You could also start
with strace.
Richard Moore - RAS Project Lead - Linux Technology Centre (PISC).
http://oss.software.ibm.com/developerworks/opensource/linux
Off
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 in user
Chris Meadors wrote:
>
> On 6 Dec 2000, H. Peter Anvin wrote:
>
> >
> > Please don't use the path /var/shm... it was a really bad precedent
> > set when someone suggested it. Use /dev/shm.
> >
>
> And I'll ask again... If this is now the recommend mount point, can we
> have devfs create this d
[EMAIL PROTECTED] said:
> Can you test some more? In particular, I'd love to hear if this
> happens with vfat even without loopback, or with loopback even without
> vfat (make an ext2 filesystem or similar instead). That woul dnarrow
> down the bug further.
Loopback-mounted iso9660 does it too
Hello guys,
Configuring a new box based on ASUS CUR-DLS dual Pentium III, 1GB RAM and
using
the new LSI SYM53C896 SCSI interface.
Question: How to get sym53c8xx and eepro100 activated at start-up
procedure ?
Thanks for your help.
[EMAIL PROTECTED]
Description:
Version used is Linux 2.2.17
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?
That's one thing that bothered me about the method that the .90 driver
used
[EMAIL PROTECTED] said:
> Sounds like a X Server bug. You should probably contact XFree86, not
> linux-kernel
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 bo
> I asked people to explain why it was needed. I am still waiting. It is a
> patch that does nothing. I will not put random deep magic into the
> kernel.
Alan, I replied to you a few weeks ago (pre20 times) when you asked me why
I was sending you this patch. (perhaps you didn't receive my email).
Okay gang, here is the skinny and it is fat and ugly!
Sometime ago some braindead engineers, at an unamed company that developed
the first DMA engine, thought it was a good idea to wack and stop the DMA
engine if there was a transaction delay of 1 micro-second or more;
regardless if the transfer
On Friday 08 December 2000 05:11, Daniel Quinlan wrote:
> Here's a patch for the cramfs filesystem. Lots of improvements and a
> new cramfsck program, see below for the full list of changes.
>
> It only modifies cramfs code (aside from adding cramfs to struct
> super_block) and aims to be complet
I'm doing some massive grepping (basically, audit of page locking),
but nothing relevant so far. There was some catch (aside of documenting
the thing and finding several completely unrelated buglets):
* ramfs_writepage() doesn't UnlockPage(). Deadlock.
* udf_adinicb_writepa
On Thu, Dec 07, 2000 at 09:59:18PM -0500, Alexander Viro wrote:
> On Fri, 8 Dec 2000 [EMAIL PROTECTED] wrote:
> > > BTW, could we finally lose mpx(2)?
> >
> > Maybe we lost it - I find sys_mpx only in a comment in arch/arm/kernel/calls.S
>
> Sure, but man2/mpx.2 is alive and well...
manpages-de
Hi,
one of my friends uses 2.2.18-pre21 (packaged by Debian...) and
when he run tripwire, he got:
iput: device 08:07 inode 47215 still has aliases!
iput: device 08:07 inode 47592 still has aliases!
iput: device 08:07 inode 110279 still has aliases!
iput: device 08:02 inode 62928 still has alias
On Thu, 7 Dec 2000 [EMAIL PROTECTED] wrote:
> Which surely we can on today's x86 systems. Even back in the days of OS/2
> 2.0 running on a 386 with 4Mb RAM we used a taskgate for both NMI and
> Double Fault. You need only a minimal stack - 1K, sufficient to save state
> and restore ESP to a known
On Thu, 7 Dec 2000, Richard B. Johnson wrote:
> I am not denying the possibility of "warm-booting", i.e.,
> reloate some code to where there is a 1:1 physical to virtual
> translation, jump to the relocated code, disable paging, restart kernel
> code, and possibly examine what happened. You just
On Mon, Dec 04, 2000 at 08:50:04PM +, Stephen C. Tweedie wrote:
> I have pushed another set of raw IO patches out, this time to fix a
This fix is missing:
--- rawio-sct/mm/memory.c.~1~ Fri Dec 8 03:05:01 2000
+++ rawio-sct/mm/memory.c Fri Dec 8 03:57:48 2000
@@ -455,7 +455,7 @@
Hi Linus,
I have just found and fixed another bug in the driver -- the
->ioctl() method would print "freed 0 bytes" when it actually freed >0, if
the update has failed previously.
The patch is cumulative, i.e. contains all the previous fixes I have sent
to you in the last few days.
Tested thoro
Summary:
SO_DETACH_FILTER does not accept any parameter, but code in sock.c check for it.
Problem description:
Trying to remove attached filter i got EINVAL (and the filter was left
attached).
The code setsockopt(fd, SOL_SOCKET, SO_DETACH_FILTER, 0, 0) is correct,
but does work.
Looking in sock.c
On Thu, Dec 07, 2000 at 10:46:08PM +, Russell King wrote:
> It appears to be caused by the pci_read_bridge_bases code copying the
> pointer to the resources instead of making a copy of the resources
> themselves.
No, pci_read_bridge_bases() is obsoleted by new pci setup code. ;-)
You have to
Hello,
I am new to linux world and currently learning to write device drivers and
modules. This question might have been
repeated many times on the list but I havent found any satisfactory answer
in the archives hence I am posting this question
again. While loading the module, the insmod compla
On Fri, 8 Dec 2000 [EMAIL PROTECTED] wrote:
>
>
> 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
Hi Linus,
here is my first shot for cleaning up the shm handling. It did survive
some basic testing but is not ready for inclusion.
The smp locking needs some review, shmem_file_setup needs cleanup, we
probably want to have triple indirect blocks... But the basic concept
seems to work.
Oh, and
> Can you reproduce this without strace?
>
> I only see this problem when I run with 'strace -f' and java wants to
> exit (apart from that java works correctly). I don't see the dependency
> on the heap size here.
Yes, I only started using strace when the problem became apperent. Java 1.3.0
does
At 11:54 PM 12/7/00, Jeff V. Merkey wrote:
>Linux today monitors this list. Some public education may be the best
>route. How do we post a security advisory warning people that will get
>posted? I'm sure folks see the DANGEROUS comments, but they don't seem
>to stick in their heads. Then the
> spin_lock_irq(&io_request_lock);
> we finish the request and return to the add_request function which calls
> spin_unlock_irqrestore(&io_request_lock,flags);
> and restores the flags.
>
> Isn't it possible now that the flags which we restore are out of date now?
> Is this idiom
On Fri, Dec 08, 2000 at 08:19:46AM -0500, David Relson wrote:
> At 11:54 PM 12/7/00, Jeff V. Merkey wrote:
>
>
> >Linux today monitors this list. Some public education may be the best
> >route. How do we post a security advisory warning people that will get
> >posted? I'm sure folks see the D
> My question then is, is there a (monitoring) tool that can tell me who is
> writing to disk? Or how I configure the kernel to know that?
Monitoring tool - none that I know of. FInd can do a search and find all very
new files.
Most likely it's a combination of cruddy CD-ROM drives and magicdev
> Various processes have been getting random signals after heavy CPU usage.
> Playing an MPEG movie, kernel compile, or even just some small apps
> compiling sometimes. Just for the record, this isn't an OOM situation,
> I've watched this box with half its memory free or in buffers left
> unattend
> somewhere in the thousands. Is NTFS write stable enough now in 2.4 to
> fix these problems, if so, can we DISABLE by REMOVING write code in the
It says DANGEROUS in big letters on the configuration option. We are now
down to the level of people who don't understand 'smoking kills you' in big
l
> Is there a project underway that documents how things like the VM, the Memory
> Manger, what a a specific driver needs to do, what it needs to return, how it is
> called, what do all those files in arch/whatever do? Are there bits and pieces
For the kernel stuff there is a project to put docum
> I compiled the Debian distribution of 2.2.18pre21 source on and for a
> AcerNote-950, with APM enabled.
>
> All is fine except that I can reliably "oops" it simply by trying to read
> from /proc/apm (e.g. cat /proc/apm).
>
> oops output and ksymoops-2.3.4 output is attached.
>
> Is there anyt
> Agree. We need to disable it, since folks do not read the docs
> (obviously). Of course, we could leave it on, and I could start
> charging money for these tools -- there's little doubt it would be a
> lucrative business. Perhaps this is what I'll do if the numbers of
> copies keeps growing.
> > wrong with it. I've only seen this under 2.3.x/2.4 SMP kernels. I
> > would say that this is definitely a kernel problem.=20
>
> XFree86 3.9 and XFree86 4 were rock solid for a _long_ time on 2.[34]
> kernels - even on my BP6=B9. The random crashes started to happen when =
> I
> upgraded my
> my server currently works with that patch, but I'm sure it won't boot anymore
> if I apply this 2.2.18pre25 alone.
Some days I don't know why I bother
> just in case, here it is again.
It doesnt even apply
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the
Hi Jens,
I have tested your latest stuff (cd-2) with the CD that was
causing problems before. The problems still occur.
The CD plays fine, but I get the following errors in
my /var/log/messages:
Dec 8 06:05:29 agate kernel: hdc: packet command error: status=0x51 {
DriveReady SeekComplete Erro
On Fri, 8 Dec 2000, Alan Cox wrote:
> I am very firmly against removing something because people do
> not read manuals, what is next fdisk , mkfs ?.
I must say I like the CONFIG_MORON though. By setting that the
(l)user exposes his true identity and leaves little for us to
doubt ;)
Added to the
>
>No, pci_read_bridge_bases() is obsoleted by new pci setup code. ;-)
>You have to set up bus resources properly in pcibios_fixup_bus().
>For a single root bus configuration, you don't need to do anything
>with the root bus itself - its resources already point to ioport_resource
>and iomem_resour
On Fri, Dec 08, 2000 at 02:43:42PM +0100, David Weinehall wrote:
> On Fri, Dec 08, 2000 at 08:19:46AM -0500, David Relson wrote:
> > At 11:54 PM 12/7/00, Jeff V. Merkey wrote:
> No amount of warnings can prevent morons from f**king up. Unix gives
> you enough rope et al. I'm not arguing for remov
Bought myself this new CPU that is mainly available for laptops.
I have Tyan S1590 board which BIOS won't POST if I set cpu speed (it's
500Mhz chip) >300Mhz. This won't matter much in windows since I can there
use graphical utility which allows one to set whe CPU clock multiplier in
flight as 2.0
Hello all
I posted on this subject before, but this time I just would like to
receive an answer to the question - BIOS or kernel - who rules?
So, the question: is it either
1) there ARE situations when BIOS's inability to support DMA for IDE
cannot be fixed by the software or
2) it IS always pos
On Fri, Dec 08 2000, Miles Lane wrote:
> Hi Jens,
>
> I have tested your latest stuff (cd-2) with the CD that was
> causing problems before. The problems still occur.
> The CD plays fine, but I get the following errors in
> my /var/log/messages:
>
> Dec 8 06:05:29 agate kernel: hdc: packet com
You know, couldn't we do something like prompting the (l)user with an
disclaimer/agreement or something when selecting the option or maybe
even when doing a make dep?
They'd prolly blast through it without reading (You don't think they
read teh MS agreement when istalling windows do you?) but I b
Peter Samuelson wrote:
>
> [Jeff Merkey]
> > Please consider the attached patch to make it a little bit harder for
> > folks to enable NTFS Write Support under Linux until it can get fixed
> > properly.
>
> Hey! It was a joke! A better way would be just to comment out the
> CONFIG_NTFS_RW line
Hi all,
Looking at Linux kernel sources, I've found RFC1122 status splitted in
each file. Is there a complete document showing RFC1122 status as a
whole for a given kernel version ?
Thanks, Fabien
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message
On Fri, 8 Dec 2000, Rik van Riel wrote:
> On Fri, 8 Dec 2000, Alan Cox wrote:
>
> > I am very firmly against removing something because people do
> > not read manuals, what is next fdisk , mkfs ?.
>
> I must say I like the CONFIG_MORON though. By setting that the
> (l)user exposes his true iden
Peter Horton wrote:
>
> On Wed, Dec 06, 2000 at 07:44:02PM -0500, Mike A. Harris wrote:
> > Which ethernet module works with this card? 2.2.17 kernel
> >
>
> If the PCI device ID is 3065 then it's via-rhine, but not supported by the
> driver in the kernel. Get updated via-rhine from Donald Beck
> Dec 8 06:05:29 agate kernel: hdc: packet command error: status=0x51 {
> DriveReady SeekComplete Error }
> Dec 8 06:05:29 agate kernel: hdc: packet command error: error=0x50
> Dec 8 06:05:29 agate kernel: ATAPI device hdc:
> Dec 8 06:05:29 agate kernel: Error: Illegal request -- (Sense key
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?
>
> That's one thing that bothered me abou
[EMAIL PROTECTED] said:
> They'd prolly blast through it without reading (You don't think they
> read teh MS agreement when istalling windows do you?) but I bet we
> could argue that they accepted the agreement to protect us.
tristate 'NTFS file system support (read only)' CONFIG_NTFS_FS
dep_
> here is my first shot for cleaning up the shm handling. It did survive
> some basic testing but is not ready for inclusion.
Can you help me with an SHM related problem?
I'm currently writing a Win32 emulation kernel module to help speed Wine up,
and I'm writing the file mapping support stuff
> It doesnt even apply
sorry Alan, I think it's because I had to copy/paste
it
with my mouse under X into my browser (I don't have
smtp access here at work), and it applies here with a
-12 lines offset...
Here it is attached for 2.2.18pre25, but since the
raid
server is running now (under 2.2.18
Is there a development kernel with DRI for the ati rage 128 mobility m/p
processor?
DRI is available for the rage 128, but it is not working on this chipset.
This seems to be the only way to get hardware acceleration working on
XFree86 4.0, without reverting back to 3
The attempted compile of this
Date:Fri, 08 Dec 2000 15:46:59 +0100
From: Fabien Ribes <[EMAIL PROTECTED]>
Looking at Linux kernel sources, I've found RFC1122 status splitted in
each file. Is there a complete document showing RFC1122 status as a
whole for a given kernel version ?
No, unfortunately nobod
On Fri, 08 Dec 2000, Alan Cox wrote:
> > Is there a project underway that documents how things like the VM, the Memory
> > Manger, what a a specific driver needs to do, what it needs to return, how it is
> > called, what do all those files in arch/whatever do? Are there bits and pieces
Of course
Daniel Phillips wrote:
> On Fri, 08 Dec 2000, Alan Cox wrote:
> > For the kernel stuff there is a project to put documentation about functions
> > and what they do inline into the kernel. Its slow progress. Trying to do
> > anything formal and structured isnt going to be productive until the
> > d
easiest way I can think of is to compile them into the kernel, not as
modules. Thus as soon as the kernel boots, they are active in memory.
-- Dan Egli
-- Network Administrator / President
-- Frankenstein Computers
-- 801-671-7875
- Original Message -
From: "Edouard Soriano" <[EMAIL PROTE
On Fri, Dec 08, 2000 at 03:34:09PM +0100, Jan-Benedict Glaw wrote:
[...]
> Maybe that can prevent pupils^H^H^H^H^Heople from shooting their
> foots...
Nothing can "prevent" them from shooting themselves in the foot,
even taking away their guns and ammunition (removing it from th
According to Alan Cox:
> > my server currently works with that patch, but I'm sure it won't boot anymore
> > if I apply this 2.2.18pre25 alone.
>
> Some days I don't know why I bother
Bad day, Alan? ;)
> > just in case, here it is again.
> It doesnt even apply
Hmm, it did apply for me. Do new
On Fri, 8 Dec 2000, Daniel Phillips wrote:
> Tigran Aivazian has been preparing 'Linux Kernel Internals' which is
> *highly recommended* and 100% free.
in case he is curious where to find it:
http://www.moses.uklinux.net/patches/lki.html
(or .sgml for master source).
Interestingly, the main
"Barry Smoke" <[EMAIL PROTECTED]> writes:
> DRI is available for the rage 128, but it is not working on this chipset.
[...]
> Windows reports the chip as a rage mobility-p agp 1x, agp2x
That's not a Rage Mobility 128, I believe. That's a Mach-64-based
chip. Check /var/log/XFree86.0.log for a
Linus, Alan,
I am resubmitting this patch for inclusion in the 2.2.x tree because I
received no response to my initial submission. This patch has been
tested this on 2.2.14-2.2.17. At Usenix last summer, Stephen Tweedie
and Ted T'so looked at it and saw no problems with it (which is why I
have
> "KO" == Keith Owens <[EMAIL PROTECTED]> writes:
KO> You only removed the module symbol handling. The problem is that
KO> the entire klogd oops handling is out of date and broken. I
KO> recommend removing all oops processing from klogd, which means
KO> that klogd does not need any symb
Peter Samuelson wrote:
>
> [Dick Johnson]
> > Do:
> >
> > char main[]={0xff,0xff,0xff,0xff};
>
> Oh come on, at least pick an *interesting* invalid opcode:
>
> char main[]={0xf0,0x0f,0xc0,0xc8};/* try also on NT (: */
>
me2v@reliant DRFDecoder $ ./op
Illegal instruction (core dumped)
I
Actually what you are pointing out here is the differing needs for
differing uses. Real-time, embedded systems etc have different requirements
or at lest different priorities to enterprise usage. I'm coming from the
enterprise server angle - the Linux/390 type of use and high end IA32
Server.
I
Hello!
> Kill it ;)
Great day! Nobody will cry that information sort of this:
* MUST NOT send ICMP errors in reply to:
* ICMP errors (OK)
* Broadcast/multicast datagrams (OK)
* MAC broadcasts (OK)
* Non-initial fragments (OK)
* Datagram with a source address that is
Hello!
Description of the changes:
Changed logic in drivers/sound/Config.in so that both drivers for YMF PCI
can be compiled as modules, but neither of them is enabled if the other
one is linked into the kernel (just like the UHCI drivers).
Don't use ENOTTY in the ioctl routine in drivers/sound
[EMAIL PROTECTED] wrote:
>
> On Thu, 7 Dec 2000, Jeff V. Merkey wrote:
>
> > I think there may be a case when a process forks, that the MMU or some
> > other subsystem is either not setting the page bits correctly, or
> > mapping in a bad page. It's a LEVEL I bug in 2.4 is this is the case,
> >
I have noticed that Linux 2.4.0-test12-pre7 still comes with .8final. Is
there a plan to have .9 incorporated at some future time into the stock
2.4 kernels? Will this happen before 2.4 comes out?
Also is there a transition path between .8final and .9? (short of save
everything to tape and restor
On Fri, Dec 08, 2000 at 07:41:22PM +0300, [EMAIL PROTECTED] wrote:
> /**
> *kfree_skb - free an sk_buff
> *@skb: buffer to free
> *
> *Drop a reference to the buffer and free it if the usage count has
> *hit zero.
> */
>
> People, who need _literal_ translation from C to Eng
On Fri, 8 Dec 2000, Matthew Vanecek wrote:
> Peter Samuelson wrote:
> >
> > [Dick Johnson]
> > > Do:
> > >
> > > char main[]={0xff,0xff,0xff,0xff};
> >
> > Oh come on, at least pick an *interesting* invalid opcode:
> >
> > char main[]={0xf0,0x0f,0xc0,0xc8};/* try also on NT (: */
> >
>
On Fri, 8 Dec 2000 [EMAIL PROTECTED] wrote:
>
>
> Actually what you are pointing out here is the differing needs for
> differing uses. Real-time, embedded systems etc have different requirements
> or at lest different priorities to enterprise usage. I'm coming from the
> enterprise server angle
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. I am honestly not sure if this is a linux bug, a glibc bug, or a
gdb bug,
Hello,
running raid-1 on Mylex 170 2x18Go we have lot of problem
like this:
EXT2-fs error (device rd(48,3)): ext2_readdir: directory #181 contains a hole at
offset 827392
EXT2-fs error (device rd(48,3)): ext2_readdir: directory #181 contains a hole at
offset 831488
EXT2-fs error (device rd(48,3
On Thu, 7 Dec 2000, Alan Cox wrote:
# Ok we believe the VM crash looping printing error messages is now fixed.
# Marcelo finally figured it out and my 8Mb 486 has been running 2.2.18pre
# with that fix and stably[1].
Unfortunately, I don't think it is fixed. We maintain a heavy loaded
FTP/Sam
Quite a few functions in the 2.3 kernels and up are marked as __exit.
This puts the functions in the .text.exit section that is marked as
DISCARD
in vmlinux.lds.
It turns out that if the function is static, ld never puts it into the
symbol
table of vmlinux; however, if the function is global, ld
Hi,
On Wed, Dec 06, 2000 at 05:29:14PM -0800, Linus Torvalds wrote:
> - test7:
> - Kai Germaschewski: ymfpci cleanups and resource leak fixes
> - pre5:
> - Jaroslav Kysela: ymfpci driver
Just tried this out on my laptop and it played and didn't give strange
messages that Pete's driver
> as soon as I can reboot it, I promise I will test the
> kernel with and without the patch to be really sure.
> but before that, if people who have problems with
> megaraid/netraid could give it a try, that would be
> cool. Also, it would be nice if people for which the
> normal megaraid driver w
> > Some days I don't know why I bother
> Bad day, Alan? ;)
Umm no but having people _keep_ sending you do nothing patches gets
annoying after a while ;)
> reading the patch, it makes sense. It probably does about the same
> as Willy's patch, but the "right" way by using pci_resource_start()
> w
> BTW what is this? It is just a question, I missed even the moment, when these
> things appeared:
It allows us to generate man9 sets for that part of the kernel and other
documentation sets
> Well, I am a fossil, of course, and like to read sources printed on paper
> and all these pretentions t
> > Well, I am a fossil, of course, and like to read sources printed on paper
> > and all these pretentions to convert readbale text to hypertext irritate me.
> > But such deep thoughts eat even more expensive space on screen!
>
> So write a 4 line perl script to filter them out before printing ?
Andi Kleen a écrit :
>
> On Fri, Dec 08, 2000 at 06:54:28AM -0800, David S. Miller wrote:
> >Date: Fri, 08 Dec 2000 15:46:59 +0100
> >From: Fabien Ribes <[EMAIL PROTECTED]>
> >
> >Looking at Linux kernel sources, I've found RFC1122 status splitted in
> >each file. Is there a
On Fri, Dec 08, 2000 at 05:19:30PM +0100, Fabien Ribes wrote:
> Andi Kleen a écrit :
> >
> > On Fri, Dec 08, 2000 at 06:54:28AM -0800, David S. Miller wrote:
> > >Date: Fri, 08 Dec 2000 15:46:59 +0100
> > >From: Fabien Ribes <[EMAIL PROTECTED]>
> > >
> > >Looking at Linux kernel
On Fri, Dec 08, 2000 at 06:54:28AM -0800, David S. Miller wrote:
>Date: Fri, 08 Dec 2000 15:46:59 +0100
>From: Fabien Ribes <[EMAIL PROTECTED]>
>
>Looking at Linux kernel sources, I've found RFC1122 status splitted in
>each file. Is there a complete document showing RFC1122 s
Date: Fri, 8 Dec 2000 16:31:54 +0100
From: Andi Kleen <[EMAIL PROTECTED]>
On Fri, Dec 08, 2000 at 06:54:28AM -0800, David S. Miller wrote:
> No, unfortunately nobody has the time to do this.
The RFC evaluation is also out of date and should be either redone
or removed.
I agree
> I have seen two failure modes: on my machine (linux 2.2.5-22, glibc
> 2.1.1), when run under gdb 5.0, the created pthreads stick around as
glibc 2.1.1 definitely has problems with several bits of pthreads. You
want 2.1.3 or higher I believe.
> zombies until the machine runs out of resources.
>We aplied 2.2.18pre25 patch yesterday hoping it could solve it. The
> only difference is that the server reached several hours uptime instead of
> 40 minutes (with pre24). After two hours of load between 6.00 and 15.00
> the console was flooded with those unpopular messages ("VM: ..."). The
>
> However when I then suspended the machine and resumed it sound no longer
> worked. In fact the mpg123 that I used to test it after the resume is
> now just sitting there.
The driver does not currently support power management. In fact whoever
hacked on the include files went and put __init in
I see we have a new "call_usermodehelper" routine now. It looks like the
end result is similer to exec_usermodehelper, except that you no longer
need to mess with creating kernel threads yourself.
Is call_usermodehelper now the officially blessed way for kernel code to
run something in user spac
On Fri, Dec 08, 2000 at 01:55:43PM +, Alan Cox wrote:
> > somewhere in the thousands. Is NTFS write stable enough now in 2.4 to
> > fix these problems, if so, can we DISABLE by REMOVING write code in the
>
> It says DANGEROUS in big letters on the configuration option. We are now
> down to t
On Fri, 8 Dec 2000, Alan Cox wrote:
# >Is there any chance to get rid of these VMM failures?
# By finding them.
:-) I am not so familiar with MM in Linux. :^(
And do not have enough time for intensive study...
Although I would probably like that work...
# Are you confident you are
[Dick Johnson]
> > > char main[]={0xf0,0x0f,0xc0,0xc8};/* try also on NT (: */
> > me2v@reliant DRFDecoder $ ./op
> > Illegal instruction (core dumped)
>
> Yep. And on early Pentinums, the ones with the "f00f" bug, it would
> lock the machine tighter than a witches crotch. Ooops, not
> pol
"Jeff V. Merkey" wrote:
>
> On Fri, Dec 08, 2000 at 02:00:29PM +, Alan Cox wrote:
> > > Agree. We need to disable it, since folks do not read the docs
> > > (obviously). Of course, we could leave it on, and I could start
> > > charging money for these tools -- there's little doubt it would
On Fri, Dec 08, 2000 at 02:00:29PM +, Alan Cox wrote:
> > Agree. We need to disable it, since folks do not read the docs
> > (obviously). Of course, we could leave it on, and I could start
> > charging money for these tools -- there's little doubt it would be a
> > lucrative business. Perha
On Fri, Dec 08, 2000 at 03:34:09PM +0100, Jan-Benedict Glaw wrote:
> On Fri, Dec 08, 2000 at 02:43:42PM +0100, David Weinehall wrote:
> > On Fri, Dec 08, 2000 at 08:19:46AM -0500, David Relson wrote:
> > > At 11:54 PM 12/7/00, Jeff V. Merkey wrote:
>
> > No amount of warnings can prevent morons f
On Fri, Dec 08, 2000 at 12:42:45PM -0500, Jeff Garzik wrote:
> "Jeff V. Merkey" wrote:
>
> We don't need any messages. If (DANGEROUS) is not sufficient, then
> disable the feature unconditionally. Someone hacking on the code will
> be smart enough to enable the stuff while they are debugging.
>
This ALSA-based Yamaha PCI driver does not have the changes
from ALSA that were necessary to make it run on the Transmeta-based
Sony PictureBooks, right? I tried the driver in 2.4.0-test12pre7,
and that driver with Pavel's patch, and that driver with Pavel's
patch with "#include , #undef
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
magically started working. I am really happ
I haven't been able to get PCMCIA working under Linux 2.4 with any kind
of serial devices (Cardbus or normal ISA), at least not reliably, on my
Vaio 505TX. I've tried both yenta_socket and i82365. It works about
one time in ten, but I've never figured out what causes it to work or
not work. Wh
On Fri, Dec 08, 2000 at 07:37:55AM +, Anton Altaparmakov wrote:
> Hearing how many people trash their partition I would agree to comment out
> the NTFS write option altogether. I will make a patch for both 2.4.0-testX
> and 2.2.18latest and send them off to Linus/Alan over the weekend if no
On Fri, Dec 08, 2000 at 06:02:57PM +0100, Martin Kacer wrote:
>Is there any chance to get rid of these VMM failures?
You should apply this patch on top of 2.2.18pre25:
ftp://ftp.us.kernel.org/pub/linux/kernel/people/andrea/patches/v2.2/2.2.18pre25/VM-global-2.2.18pre25-7.bz2
>I
1 - 100 of 227 matches
Mail list logo
