"Peter Samuelson wrote:"
> [Michael Warfield]
> > This thing is not armed and dangerous due to an act of ommision.
> > It's live and active only through three acts of commision.
>
> We could make it *four* acts of commission. (: (: (:
>
> diff -urk~ fs/Config.in
> --- fs/Config.in~ Mon Nov
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 one
beats me to it.
Considering that people are blatantly ignoring all
Linus Torvalds wrote:
>
> It's not a new bug - it's an old bug that apparently is uncovered by a
> new stricter test.
>
> Apparently loopback unlocks an already unlocked page - which has always
> been a serious offense, but has never been detected before.
>
> test12-pre6+ detects it, and thus
Hi,
I got the following timeout on an SMP system:
3c59x.c:LK1.1.9 2 Sep 2000 Donald Becker and others.
http://www.scyld.com/network/vortex.html $Revision: 1.102.2.38 $
See Documentation/networking/vortex.txt
eth0: 3Com PCI 3c900 Boomerang 10Mbps Combo at 0xa800, 00:60:97:b0:c2:25, IRQ 10
> "Frank" == Frank de Lange <[EMAIL PROTECTED]> writes:
Frank> I saw your remarks on the kernel mailing list
Frank> wrt. 'threaded processes get stuck in
Frank> rt_sigsuspend/fillonedir/exit_notify' dd. 2911-12, and
Frank> thought you might be interested in the fact that
[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 entirely. Actually, I think that
My ISP is having mailserver problems causing messages to be sent out
multiple times. They should have it fixed soon.
--
=
Mohammad A. Haque http://www.haque.net/
Linus/Alan,
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.
Jeff
Peter Samuelson wrote:
>
> [Michael Warfield]
> > This thing is not armed and dangerous due to an act of ommision.
> > It's
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 completely backward-compatible. All old
cramfs images will still work
[Michael Warfield]
> This thing is not armed and dangerous due to an act of ommision.
> It's live and active only through three acts of commision.
We could make it *four* acts of commission. (: (: (:
diff -urk~ fs/Config.in
--- fs/Config.in~ Mon Nov 13 01:43:42 2000
+++ fs/Config.in
"Michael H. Warfield" 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. Perhaps this is what I'll do
On Thu, Dec 07, 2000 at 09:43:24PM -0700, Jeff V. Merkey wrote:
> Peter Samuelson wrote:
> >
> > [Jeff Merkey]
> > > Do folks not know this NTFS driver will trash hard drives? We need
> > > to alert folks DO NOT USE WRITE NTFS MODE in those versions we know
> > > are busted.
> > Here's an
Carl Perry wrote:
>
> I was reading an article today on Slashdot about how poorly documented the
> Windows API was and had this fear that Linux could get the same way. So, cut to
> the point:
Whoever posted this on Slashdot is smoking some killer dope or
something. The Windows API is very
Peter Samuelson wrote:
>
> [Jeff Merkey]
> > Do folks not know this NTFS driver will trash hard drives? We need
> > to alert folks DO NOT USE WRITE NTFS MODE in those versions we know
> > are busted.
>
> Here's an idea: let's make r/w support a separate CONFIG option, and
> label it
I was reading an article today on Slashdot about how poorly documented the
Windows API was and had this fear that Linux could get the same way. So, cut to
the point:
Is there a project underway that documents how things like the VM, the Memory
Manger, what a a specific driver needs to do, what
No, I hadn't forgotten: Time for another poke-the-kernel-list post.
December is, for many people, a time of community and family, and a
time for giving gifts to friends and strangers. In Japan, I am told,
they have a custom of giving away to others the gifts they have
received.
The December
[Jeff Merkey]
> Do folks not know this NTFS driver will trash hard drives? We need
> to alert folks DO NOT USE WRITE NTFS MODE in those versions we know
> are busted.
Here's an idea: let's make r/w support a separate CONFIG option, and
label it "DANGEROUS".
Oh wait, we already do that.
"Jeff V. Merkey" wrote:
>
> > So have you enabled core dumps and actually looked at the core dumps
> > of the programs using gdb to see where they crashed ?
>
> Yes. I can only get the SSH crash when I am running remotely from the
> house over the internet, and it only shows then when
Linux/Linus/Anton/Alan,
I am still sending out the NTFS repair tools for Linux trashed volumes,
and I've lost count now relative to how many I've sent out, but it's
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
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,
> BTW. In core dumps (I've looked at 2
Dave,
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,
BTW. In core dumps (I've looked at 2 of them from SSH) it barfs right
after
Hi Stephen,
I presume this should be going to you, as the person named in
arch/i386/kernel/apm.c - if not please redirect/ignore as appropriate.
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"
On Thu, 07 Dec 2000 17:23:51 -0800,
Joseph Cheek <[EMAIL PROTECTED]> wrote:
>i'll check it out. i'm compiling ksymoops now, is there a way to get it to
>work without a static libbfd? all i've got is a libbfd.so, and i'm going to
>need to recompile binutils if i must have a libbfd.a.
On Fri, 8 Dec 2000 [EMAIL PROTECTED] wrote:
> > BTW, if you still have 1.7, 1.10, 1.13 and 1.14...
>
> See ftp://ftp.cwi.nl/pub/aeb/manpages/ (will soon disappear again).
Got them, thanks.
> > BTW, could we finally lose mpx(2)?
>
> Maybe we lost it - I find sys_mpx only in a comment in
Linus,
I booted without an initrd defined (still have support compiled in
though) and I didn't get an Oops when I booted. So I guess it's related
to initrd. Here's some more that I noticed..
--snip--
VFS: Mounted root (ext2 filesystem).
kernel BUG at buffer.c:827!
.Oops.
Code: 0f 0b 83
[Rajiv Majumdar]
> during an exec it gives the following error message : "Pthread
> internal error : message : __libc__reinit() failed" and creates a
> core dump.
This is libc failing -- please report this through libc channels (see
http://www.gnu.org/software/libc). If it is in fact a kernel
[AC]
> > [EMAIL PROTECTED] is alive and well however.
[Pavel Roskin]
> You cannot imagine how frustrating it was to search for the archive.
> I couldn't find an up-to-date archive, and www.kernel.org keeps
> silence about mailing lists. I cannot afford subscribing to every
> list just to
On Thu, 7 Dec 2000, Jeff V. Merkey wrote:
> It's related to some change in 2.4 vs. 2.2. There are other programs
> affected other than X, SSH also get's spurious signal 11's now and again
> with 2.4 and glibc <= 2.1 and it does not occur on 2.2.
I've begun to get a bit paranoid about my K6-2
Hello,
I found a process constantly writing to disk when I run gnome as desktop
and while the whole system is idle. I don't find anything in the log
file, and I don't see anything updated in my home dir or in /tmp. Does it
sound like bdflush is writing? But I don't hear the disk access when
hi,
comments below.
Linus Torvalds wrote:
> In article <[EMAIL PROTECTED]>,
> Joseph Cheek <[EMAIL PROTECTED]> wrote:
> >copying files off a loopback-mounted vfat filesystem exposes this bug.
> >test11 worked fine.
>
> It's not a new bug - it's an old bug that apparently is uncovered by a
>
Hi all,
Thanks for all the input so far. Regarding this...
> (I'm not sure exactly what cerberos does, do you have a link for it ?).
The official name is "Cerberus Test Control System" aka CTCS. I don't know
the official site but a search for this should reveal something. Anyway it
is
On Fri, 8 Dec 2000, Rainer Mager wrote:
> Hi all,
>
> I've searched around for a answer to this with no real luck yet. If anyone
> has some ideas I'd be very grateful.
Signal 11 just means that you "seg-faulted". This is usually caused
by a coding error. However, if you have tools (like
Andi Kleen wrote:
>
> On Thu, Dec 07, 2000 at 06:24:34PM -0700, Jeff V. Merkey wrote:
> >
> > Andi,
> >
> > It's related to some change in 2.4 vs. 2.2. There are other programs
> > affected other than X, SSH also get's spurious signal 11's now and again
> > with 2.4 and glibc <= 2.1 and it
On Thu, Dec 07, 2000 at 06:24:34PM -0700, Jeff V. Merkey wrote:
>
> Andi,
>
> It's related to some change in 2.4 vs. 2.2. There are other programs
> affected other than X, SSH also get's spurious signal 11's now and again
> with 2.4 and glibc <= 2.1 and it does not occur on 2.2.
So have you
On Thu, 7 Dec 2000, Brian Gerst wrote:
> "Richard B. Johnson" wrote:
> >
> > 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
>
>
> > I looked at the implementation of the nbd which just calls
> >
> > spin_unlock_irq(_request_lock);
> > ... do network io ...
> > spin_lock_irq(_request_lock);
> >
> > This seems to work but it looks very dangerous to me (and ugly, too). Isn't there
>a better way to do this?
Andi,
It's related to some change in 2.4 vs. 2.2. There are other programs
affected other than X, SSH also get's spurious signal 11's now and again
with 2.4 and glibc <= 2.1 and it does not occur on 2.2.
Jeff
Andi Kleen wrote:
>
> On Fri, Dec 08, 2000 at 09:44:29AM +0900, Rainer Mager
In article <[EMAIL PROTECTED]>,
Alan Cox <[EMAIL PROTECTED]> wrote:
>
>Excellent. I've been trying to avoid VM fixes for 2.2.18 to stop stuff getting
>muddled together and hard to debug. Running with page aging convinces me that
>2.2.19 we need to sort some of the vm issues out badly, and make
i'll check it out. i'm compiling ksymoops now, is there a way to get it to
work without a static libbfd? all i've got is a libbfd.so, and i'm going to
need to recompile binutils if i must have a libbfd.a.
Linus Torvalds wrote:
> Your stack trace isn't symbolic (see
On Thu, Dec 07 2000, [EMAIL PROTECTED] wrote:
[deleted]
> int regdevresult;
>
> case MODULE_SCSI_DEV:
> #ifdef CONFIG_KMOD
> if (scsi_hosts == NULL)
> {
> request_module("scsi_hostadapter");
> return scsi_register_device_module((struct
>
Bryan Whitehead wrote:
>
> Is there a way I can disble a part of the kernel that is compiled into the
> kernel? For example I'd like to pass this to lilo: "usb=disable" and then
> the usb code is not loaded even though USB has been built into the kernel.
>
> Is such a feature stupid? Or has
On Fri, Dec 08, 2000 at 09:44:29AM +0900, Rainer Mager wrote:
> I recently upgraded to a new machine. It is running RedHat 6.2 Linux (with
> a SMP 2.4.0test[8-11] kernel) and has a Matrox G400 in it. X is 4.0.1.
> Anyway, about once every 2-3 days X will spontaneously die and the only info
>Is there support for using RAMDISK as the final root file system
>in 2.2.x versions, or is it there in the 2.4.x versions.
Works with 2.2x and up to 2.4.0 test12-pre3.bz2
Make sure you specify the following if you're using loadlin
root=/dev/ram
With anything above test12-pre3.bz2,
On Fri, Dec 08, 2000 at 09:44:29AM +0900, Rainer Mager wrote:
> I've heard that signal 11 can be related to bad hardware, most
> often memory, but I've done a good bit of testing on this and the
> system seems ok. What I did was to run the VA Linux Cerberos(sp?)
> test for 15 hours+ with
I have previously reported this error (about three months ago) on 2.4
with XFree 3.3.6. If you are running RedHat 6.2, then you are running
this X Server. It also shows up on Calders'a 2.4 eDesktop. It appears
to be something with glib 2.1 < versions on 2.4. I also see it with
secure shell
On Thu, 7 Dec 2000, Eric Estabrooks wrote:
> A test probably needs to be added in the centaur_model section to test
> for the cyrixIII in disguise.
2.2.18pre, and 2.4.0test have contained this test for some time now.
However, I've heard no reports of it working or not due to no-one having
the
On Thu, 7 Dec 2000, Linus Torvalds wrote:
> > btw, I'm thinking I could guess the routing from the VLSI config space,
>
> Please do. You might leave them commented out right now, but this is
> actually how most of the pirq router entries have been created: by looking
> at various pirq tables
Hi all,
I've searched around for a answer to this with no real luck yet. If anyone
has some ideas I'd be very grateful.
I recently upgraded to a new machine. It is running RedHat 6.2 Linux (with
a SMP 2.4.0test[8-11] kernel) and has a Matrox G400 in it. X is 4.0.1.
Anyway, about
> (note: the above is outdated so it's not anymore suggested for inclusion of
> course)
>
> I sumbitted most of the not-feature-oriented stuff at pre2 time and I plan to
> re-submit after 2.2.18 is released.
Excellent. I've been trying to avoid VM fixes for 2.2.18 to stop stuff getting
muddled
On Fri, Dec 08, 2000 at 12:27:58AM +, Alan Cox wrote:
> The problem is its hard to know which of your patches depend on what, and
> the complete set is large to say the least.
That's why I use a `proposed' directory that only contains patches that can be
applied to your tree, in this case it
> Such bug can't generate crashes. Did you ever reproduced crashes on your 8Mb
> 486 with 2.2.18pre24?
Yes. Every 20 minutes or so quite reliably. With that change it has yet to
crash (its actually running that + page aging + another minor tweak so it
doesnt return success on page aging until
On Thu, 7 Dec 2000, Christopher Friesen wrote:
> Kotsovinos Vangelis wrote:
> >
> > Is there any way to measure (with microsecond accuracy) the time of a
> > program execution (without using Machine Specific Registers) ?
> > I've already tried getrusage(), times() and clock() but they all have
In article <[EMAIL PROTECTED]>,
Joseph Cheek <[EMAIL PROTECTED]> wrote:
>copying files off a loopback-mounted vfat filesystem exposes this bug.
>test11 worked fine.
It's not a new bug - it's an old bug that apparently is uncovered by a
new stricter test.
Apparently loopback unlocks an already
> I looked at the implementation of the nbd which just calls
>
> spin_unlock_irq(_request_lock);
> ... do network io ...
> spin_lock_irq(_request_lock);
>
> This seems to work but it looks very dangerous to me (and ugly, too). Isn't there a
>better way to do this?
It is
On Thu, Dec 07, 2000 at 08:03:00PM +, Alan Cox wrote:
>
> Ok we believe the VM crash looping printing error messages is now fixed.
Such bug can't generate crashes. Did you ever reproduced crashes on your 8Mb
486 with 2.2.18pre24?
> Marcelo finally figured it out and my 8Mb 486 has been
Ok, I'll check it out...
Thank you very much,
--) Vangelis
On Thu, 7 Dec 2000, Karim Yaghmour wrote:
>
> You might want to try the Linux Trace Toolkit. It'll give you microsecond
> accuracy on program execution time measurement.
>
> Check it out:
> http://www.opersys.com/LTT
>
> Karim
>
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 Becker's site
Hi
I'm trying to write a block device driver which does some network stuff to satisfy the
requests. The problem is, that the network stuff wants to grab the io_request_lock
which does not work because this lock is already locked when I come into the
request_fn of my device.
I looked at the
> The cyrixIII chips by via have the centaur vendor id which causes the
> identify_cpu call in arch/i386/kernel/setup.c to fail. It is probably
> reasonable for it to have the centaur id as via owns centaur as well. I
> just replaced the centaur_model call with the cyrix_model one, but I
> know
I am not a subscriber to this list, but I thought this was important
information (which you might already have).
The cyrixIII chips by via have the centaur vendor id which causes the
identify_cpu call in arch/i386/kernel/setup.c to fail. It is probably
reasonable for it to have the centaur id
> Megaraid still needs fixing. I sent you the patch twice, so have
> other people, but it still isn't fixed. The
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.
I have no reason to believe the
On Thu, Dec 07, 2000 at 05:26:46PM -0500, Alexander Viro wrote:
> That invalidate_buffers() should leave the unhashed ones alone. If it can't
> be found via getblk() - just leave it as is.
>
> IOW, let it skip bh if (bh->b_next == NULL && !destroy_dirty_buffers).
> No warnings needed - it's a
In article <[EMAIL PROTECTED]>,
Alan Cox <[EMAIL PROTECTED]> wrote:
>So I figure this is it for 2.2.18, subject to evidence to the contrary
Megaraid still needs fixing. I sent you the patch twice, so have
other people, but it still isn't fixed. The
megaBase &= PCI_BASE_ADDRESS_MEM_MASK;
...
On Thu, 7 Dec 2000, Tigran Aivazian wrote:
> On Thu, 7 Dec 2000, Andreas Klein wrote:
>
> > hello,
> >
> > I have found a problem in scsi.c which in present in the 2.2 and 2.4
> > series. the scsi error handler thread is created with:
> >
> > kernel_thread((int (*)(void *))
Florian Schmitt <[EMAIL PROTECTED]> wrote:
>I had the following oops while doing a "find -name" and playing mp3s on
If you're running 2.4.0-test12-pre5 or later with reiserfs, you should be
aware that this can be unsafe due to a problem with reiserfs_writepage.
Fortunately, Chris Mason just
On Thu, 07 Dec 2000 14:42:38 -0800,
Joseph Cheek <[EMAIL PROTECTED]> wrote:
>loop.o built as module. this hard crashes the machine, every time
>[PIII-450]. i don't know how to debug this, is there a FAQ?
linux/Documentation/oops-tracing.txt
-
To unsubscribe from this list: send the line
On Thu, 7 Dec 2000, Alan Cox wrote:
> > > > A proper way to release the references to resources is to call daemonize()
> > > > function from within the kernel thread function, which calls
> > > > exit_fs()/exit_files() internally.
> > >
> > > Nearly correct, the daemonize function does NOT call
On Thu, 7 Dec 2000, Tigran Aivazian wrote:
> PS, Here it is, to save you time opening kernel/sched.c. The kernel is, of
> course, test12-pre7.
~~~
Before you tell me "it was not so in the earlier versions!" I am tempted
to quote a famous russian proverb
"whosoever remembereth
Is there a way I can disble a part of the kernel that is compiled into the
kernel? For example I'd like to pass this to lilo: "usb=disable" and then
the usb code is not loaded even though USB has been built into the kernel.
Is such a feature stupid? Or has this already been implemented?
It
> > > A proper way to release the references to resources is to call daemonize()
> > > function from within the kernel thread function, which calls
> > > exit_fs()/exit_files() internally.
> >
> > Nearly correct, the daemonize function does NOT call exit_files.
>
> I do not post messages to
Yes, indeed this is the point - we should at least be able to report the
problem even if we can't recover - and we should do that in the standard
kernel. It doesn't seem right to convert a bad problem into an unfathomable
disaster, which is what a trap gate for double-fault does. If you're
In looking over sched.c I find:
spin_lock_irq(_lock);
read_lock(_lock);
This seems to me to be the wrong order of things. The read lock
unavailable (some one holds a write lock) for relatively long periods of
time, for example, wait holds it in a while loop. On the other hand
On Thu, 7 Dec 2000, Andreas Klein wrote:
> > A proper way to release the references to resources is to call daemonize()
> > function from within the kernel thread function, which calls
> > exit_fs()/exit_files() internally.
>
> Nearly correct, the daemonize function does NOT call exit_files.
I
You seem to be misunderstanding the point of the argument: R3 stack fault -
no problem - handled by trap gate for idt vector 12 - recovery is possible
if one wants to handle it. R0 stack fault - big problem, exception 12 is
converted to a double-fault, which is converted to a triple-fault
Hi.
This patch is blessed by the maintainer and is based on the observation
that the Interphase 5526 card requires PCI to work. Therefore the PCI
dependency is moved into net/Config.in and removed from the .c-file.
The maintainers email address is also updated and a minor code shuffle
is done in
> 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
-
To unsubscribe from this list: send the line "unsubscribe
It uses the via-rhine driver on my system
On Thu, 7 Dec 2000, James Bourne wrote:
> On Wed, 6 Dec 2000, Mike A. Harris wrote:
>
> > Which ethernet module works with this card? 2.2.17 kernel
>
> Should be the rtl8139 driver.
>
> Regards,
> Jim
>
> >
Will do in a few hours. Working on stupid cs project right now.
Linus Torvalds wrote:
> Do you have something special that triggers this? Can you test if it
> only happens with initrd, for example?
--
=
Mohammad A. Haque
On Thu, 7 Dec 2000 12:36:01 -0500 (EST),
"Georg Nikodym" <[EMAIL PROTECTED]> wrote:
>> "KO" == Keith Owens <[EMAIL PROTECTED]> writes:
>
> KO> I would prefer to see the oops decoding completely removed from
> KO> klogd.
>
>Since nobody else has weighed in on this issue, I quickly did the
Hi,
Kernel 2.4.0-test12-pre7
There appears to be a possibility whereby the root resources (ioport_resource
and iomem_resource) can get modified by the PCI code:
Unknown bridge resource 0: assuming transparent
Unknown bridge resource 1: assuming transparent
Unknown bridge resource 2: assuming
Russell King writes:
> I'm seeing an oops while assigning PCI resources on an ARM board. This
> board as a PCI to PCI bridge on board without any devices on the second
> bus.
I've solved this one, sorry for the noise.
_
|_| -
On Thu, 7 Dec 2000 23:36:23 +0100,
Florian Schmitt <[EMAIL PROTECTED]> wrote:
>I had the following oops while doing a "find -name" and playing mp3s on
>my SB live:
>0010:[ne2k-pci:__insmod_ne2k-pci_O/lib/modules/2.4.0-test12/kernel/drivers+-2386971/96]
>It seems strange that the oops occured in
On Thu, 7 Dec 2000 21:09:47 +,
[EMAIL PROTECTED] wrote:
>In summary I'd say the lack of a task gate is at the very least an
>oversight, if not a bug.
>
>If no one else wants to do it I'll see if I can code up the task gates for
>the double-fault and NMI.
If you overflow the kernel stack
copying files off a loopback-mounted vfat filesystem exposes this bug.
test11 worked fine.
loop.o built as module. this hard crashes the machine, every time
[PIII-450]. i don't know how to debug this, is there a FAQ?
[transcribed by hand]:
# mount -o loop /tmp/cdboot.288 /mnt/cd
# cd /mnt/cd
I had the following oops while doing a "find -name" and playing mp3s on
my SB live:
Dec 7 14:16:50 phoenix kernel: Unable to handle kernel paging request at
virtual address 00010f08
Dec 7 14:16:50 phoenix kernel: printing eip:
Dec 7 14:16:50 phoenix kernel: d084a3e5
Dec 7 14:16:50 phoenix
"Richard B. Johnson" wrote:
>
> 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,
On Thu, 7 Dec 2000, Udo A. Steinberg wrote:
> Jan Niehusmann wrote:
> >
> > The following patch actually prevents the corruption I described.
> >
> > I'd like to hear from the people having problems with hdparm, if it helps
> > them, too.
>
> Yes, it prevents the issue.
>
> > Please note
In article <[EMAIL PROTECTED]>,
Mohammad A. Haque <[EMAIL PROTECTED]> wrote:
>
>I'm getting a BUG at boot in buffer.c:827. Oops/ksymoops at teh end of
>this message. I also noticed that the driver for my scsi card isn't
>loading at boot if compiled as a module using initrd. This is what I get
On Thu, 7 Dec 2000, Andries Brouwer wrote:
> On Thu, Dec 07, 2000 at 10:24:31AM -0500, Alexander Viro wrote:
>
> > Al, currently walking through the /usr/share/man/man2 and swearing silently...
>
> Swearing? At the POSIX decisions or at the man page quality?
Mostly at the
Jan Niehusmann wrote:
>
> The following patch actually prevents the corruption I described.
>
> I'd like to hear from the people having problems with hdparm, if it helps
> them, too.
Yes, it prevents the issue.
> Please note that the patch circumvents the problem more than it fixes it.
> The
On 7 Dec 00 at 16:44, Richard B. Johnson wrote:
> 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
Hi
I m sorry if this question doesn't belong to this list. But I couldn't
access the linux-admin list.
Is there support for using RAMDISK as the final root file system
in 2.2.x versions, or is it there in the 2.4.x versions.
I am trying to bring up linux on a diskless server which initially
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
On Thu, Dec 07, 2000 at 08:01:13PM +0100, Kai Germaschewski wrote:
> Maybe I'm stating something which is obvious to everybody, but note
> that pci_assign_unassigned_resources is only called from
Possibly, but I don't know either. :)
> ./arch/alpha/kernel/pci.c:
The following patch actually prevents the corruption I described.
I'd like to hear from the people having problems with hdparm, if it helps
them, too.
Please note that the patch circumvents the problem more than it fixes it.
The true fix would invalidate the mappings, but I don't know how to do
You might want to try the Linux Trace Toolkit. It'll give you microsecond
accuracy on program execution time measurement.
Check it out:
http://www.opersys.com/LTT
Karim
Kotsovinos Vangelis wrote:
>
> Is there any way to measure (with microsecond accuracy) the time of a
> program execution
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 point before switching back to the main TSS to
On Thu, 7 Dec 2000, Hugh Dickins wrote:
> The present situation is inconsistent: "notsc" removes cpuinfo's
> "tsc" flag in the UP case (when cpu_data[0] is boot_cpu_data), but
> not in the SMP case. I don't believe HPA's recent mods affected that
> behaviour, but it is made consistent (cleared
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?
2.2.17:
does not define this
2.2.18:
#define create_proc_info_entry(n, m, b, g) \
{ \
I'm getting a BUG at boot in buffer.c:827. Oops/ksymoops at teh end of
this message. I also noticed that the driver for my scsi card isn't
loading at boot if compiled as a module using initrd. This is what I get
during the boot process.
SCSI subsystem driver Revision: 1.00
1 - 100 of 410 matches
Mail list logo
