Hi,
my system has an Nvidia "nForce 630A MCP" chipset.
(Asrock ALiveNF7G-HDready mainboard)
If it helps, I've uploaded the output of "lspci -vvxxx" to:
http://datenparkplatz.de/DiesUndDas/lspci-vvxxx.output.txt.
Best wishes,
Ulrich
-
To unsubscribe from
o map I/O space 00f0
(XEN) mm.c:833:d2 Non-privileged (2) attempt to map I/O space 00f0
It's not a big issue, but maybe if the RTC cannot be read, it's better to skip
rather tan outputting a wrong date/time.
Regards,
Ulrich
--
To unsubscribe from this list: send the line "
This looks like a merge error, the code is duplicated with the first
copy doing something else as well. Just remove the second block.
Signed-off-by: Ulrich Drepper
Makefile |8
1 file changed, 8 deletions(-)
Index: perf/config/Makefile
On Sun, Oct 6, 2013 at 4:42 PM, Linus Torvalds
wrote:
> I doubt it is intentional, but I also cannot really feel that we care
> deeply. Afaik we don't really honor the size limit exactly anyway, ie
> we tend to check only at page boundaries etc. So do we really care?
I could imagine in the case A
Hey guys,
according the dw_apb_timer I need your statement...
Am 06.07.2013 23:00, schrieb Thomas Gleixner:
> Ulrich,
>
> On Sat, 6 Jul 2013, Ulrich Prinz wrote:
>
>> I got the message. With modifying the existing driver to support more
>> function pointers in its sys
e to process
the dirty buffers.
For reference: The machine in question is at 3.0.74-0.6.10-default with the
latest SLES11 SP2 kernel being 3.0.93-0.5.
I'd like to know what the gurus thing about that. I think with increasing RAM
this issue will become extremely important soon.
Regards,
Ulric
I forgot to mention: CPU power is not the problem: We have 2 * 6 Cores (2
Threads each), making 24 logical CPUs...
>>> Ulrich Windl schrieb am 10.10.2013 um
>>> 10:15
in Nachricht <52566237.478 : 161 : 60728>:
> Hi!
>
> We are running some x86_64 server
: 2
(I know this CPU has some bugs with virtualization; is filesystem corruption
one of them?)
Regards,
Ulrich
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.
in an reliable way.
Being paranoid, the user should at most be able to limit his own processes. I
cannot envision a proper solution with the current interface.
Would anybody share some good ideas with me?
(I'm not subscribed to the kernel list, so please CC:)
Regards,
Ulrich
--
To unsubs
dm-15 HP,HSV200
CBW_DB_BTD-E2 (3600508b4001085dd000115ad) dm-14 HP,HSV200
DP_DB_10k-E1 (3600508b4001085e3f246) dm-20 HP,HSV200
CBW_DB_10k-E2 (3600508b4001085dd000115a5) dm-9 HP,HSV200
CBW_DB_10k-E1 (3600508b4001085e3f35f) dm-13 HP,HSV200
The code is in blkio_policy_parse_and_set() of
openSUSE 12.3...
Regards,
Ulrich
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
isters
rk3188-dw-apb-timer64-osc: will load 64bit variant of 64bit registers
>
>
> Copy and paste is a conveniant thing, right? It just should have a pop
> up window assigned which asks at the second instance of copying the
> same thing whether you really thought about it.
We th
e way you explained in your replies. Just the courage was missing I
guess :)
Regards,
Ulrich
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-i
Re-sent due to "5.7.1 Content-Policy reject msg: The capital Triple-X in
subject is way too often associated with junk email, please rephrase. ":
>>> "Ulrich Windl" schrieb am 16.08.2013 um
10:29 in Nachricht <520e15ef.ed38.00a...@rz.uni-regensburg.de>:
>
know this is the wrong list for
discussing utils).
Regards,
Ulrich Windl
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FA
and a truncate, just in case you wonder...
Regards,
Ulrich
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
>>> Hugh Dickins schrieb am 04.08.2013 um 00:37 in Nachricht
:
> On Thu, 1 Aug 2013, Ulrich Windl wrote:
>> Hi folks!
>>
>> I think I'd let you know (maybe I'm wrong, and the kernel is right):
>>
>> I write a C-program that maps a file into
.
Is this problem fixed in a newer kernel?
For the curious: I tuned queue/max_sectors_kb for the paths in a multipath
device, but didn't tune the multipath device itself...
Regards,
Ulrich
P.S.: Plese keep CC: as I'm not subscribed to the list
--
To unsubscribe from this list: send th
On Mon, Feb 25, 2013 at 2:22 PM, Eric Dumazet wrote:
> I don't understand the issue.
>
> sendfile() returns -EAGAIN only if no bytes were copied to the socket.
There is something wrong/unexpected/...
I have a program which can use either sendfile or send. When using
sendfile to transmit a large
On Sat, Mar 2, 2013 at 10:09 PM, Eric Dumazet wrote:
>
> Using non blocking IO means the sender (and the receiver) must be able
> to perform several operations, as long as the whole transfert is not
> finished.
Certainly, and this is implemented. But the receiver never gets the
rest of the data
originates from read_magic_time() in
/drivers/base/power/trace.c.
I'm running kernel 3.0.74-0.6.8-xen (SLES11 SP2) on x86_64.
Regards,
Ulrich
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo
00 [xfsbufd/dm-12]
5561 ?S 0:00 [xfsaild/dm-12]
5593 ?S 0:00 [xfsbufd/dm-13]
5594 ?S 0:00 [xfsaild/dm-13]
5875 tty1 S+ 0:00 grep xfs
Regards,
Ulrich
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the
please keep me in CC: as I'm not subscribed to the list.
Regards,
Ulrich
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Wouldn't you agree that seeing the microcode revision in /proc/cpuinfo would be
nice?
For those CPUs lacking the feature one could hard-wire the value "none" (which
would be also "kind of true")...
Regards,
Ulrich
(not subscribed, so please CC: you replies to me)
--
To unsubsc
SLES11 SP2.
In openSUSE 12.1 (kernel 3.1.10) it's also still missing.
Anyway, it's nice to see that others also thought this feature is useful.
Thanks & best regards,
Ulrich
>>> Borislav Petkov schrieb am 14.08.2012 um 15:12 in Nachricht
<20120814131211.ga25...@x1.osrc.
On Mon, Jul 23, 2012 at 11:00 AM, Kirill A. Shutemov
wrote:
> The right way to fix it is to switch to XSI-compliant version.
And why exactly would this be "the right way"? Just fix the use of
strerror_r or use strerror_l.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel"
On Mon, Jul 23, 2012 at 4:31 PM, Kirill A. Shutemov
wrote:
> + const char *err = strerror_r(errnum, buf, buflen);
> +
> + if (err != buf && buflen > 0) {
> + size_t len = strlen(err);
> + char *c = mempcpy(buf, err, min(buflen
On Mon, Jul 23, 2012 at 5:06 PM, Kirill A. Shutemov
wrote:
> They are bugs.
>
> Let's fix strerror_r() usage.
>
> Signed-off-by: Kirill A. Shutemov
Acked-by: Ulrich Drepper
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
t
On Tue, Jan 15, 2013 at 8:39 AM, Jiri Olsa wrote:
> $ perf stat -f formula.conf:cpi kill
> usage: kill [ -s signal | -p ] [ -a ] pid ...
> kill -l [ signal ]
I do like this proposal. The only comment I have is that perhaps the
command line syntax isn't ideal. What you use above is
On Wed, Jan 16, 2013 at 9:25 AM, Jiri Olsa wrote:
> I was thinking having config files (global and arch specific)
> comming with perf having predefined formulas.
All the more reason to not mention the file name or really any source
for the definition of the formula in the name,
> 1) -e 'ratio/
>>> Ryan Mallon schrieb am 09.07.2012 um 01:24 in Nachricht
<4ffa16b6.9050...@gmail.com>:
> On 06/07/12 16:27, Ulrich Windl wrote:
> > Hi!
> >
> > Recently I found a problem with the command (kernel 3.0.34-0.7-default from
> SLES 11 SP2, run as r
Hi!
Still the problem seems to be related to the sysfs:
# cd /tmp
# touch testfile
# chmod u=w,go= testfile
# F=/tmp/testfile
# test -r "$F" && cat "$F"
So it seems access(2) works correctly for root and "normal" filesystems. That's
why I came up with
kernel development.
Regards,
Ulrich
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
ely a kernel problem, a
library problem, or a gdb problem?
Naively I thought when exiting the process, all threads would die...
Ulrich
P.S. Not subscribed here
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More ma
nd there is no guarantee that any of
the _SC_* constants are defined as macros. You'll have to add a
configure test.
--
---. ,-. 1325 Chesapeake Terrace
Ulrich Drepper \,---' \ Sunnyvale, CA 94089 USA
Red Hat `--&
time warps).
As any problem, it can be solved with some overhead, but should it be
done?
Replies to me too, as I'm not subscribed, please.
Ulrich
On 9 Apr 2001, at 18:39, Andreas Bussjaeger wrote:
> > from the current CPU. All these values seem highly suspect. However a
> > fe
Ulrich Lauther ph: +49 89 636 48834 fx: ... 636 42284
Siemens CT SE 6 Internet: [EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo
frequently. What has this to do with costs?
Confused,
Ulrich
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
> Hi,
>
> I think that it is the bug of FAT-fs.
> Please try the following patch.
>
thanks a lot, the patch fixes the problem
--
-ulrich lauther
----
Ulrich Lauther ph: +49 89 636 48834 fx
data. It is a programmer problem.
--
---. ,-. 1325 Chesapeake Terrace
Ulrich Drepper \,---' \ Sunnyvale, CA 94089 USA
Red Hat `--' drepper at redhat.com `
-
To unsubscribe from this list: send the line "unsubscribe
rogrammers to not
initialize.
--
---. ,-. 1325 Chesapeake Terrace
Ulrich Drepper \,---' \ Sunnyvale, CA 94089 USA
Red Hat `--' drepper at redhat.com `
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel&qu
people apparently want.
--
---. ,-. 1325 Chesapeake Terrace
Ulrich Drepper \,---' \ Sunnyvale, CA 94089 USA
Red Hat `--' drepper at redhat.com `
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the b
cesses.
The rest seems OK. Thanks,
--
---. ,-. 1325 Chesapeake Terrace
Ulrich Drepper \,---' \ Sunnyvale, CA 94089 USA
Red Hat `--' drepper at redhat.com `
-
To unsubscribe from this l
r dealing with the common case without
syscalls can be applied here as well.
--
---. ,-. 1325 Chesapeake Terrace
Ulrich Drepper \,---' \ Sunnyvale, CA 94089 USA
Red Hat `--' drepper at redhat.com `--
lemented using
fd = open (name)
addr = mmap (..fd..)
close (fd)
sem_syscall (addr)
i.e., it can be mapped to a memory reference again.
--
---. ,-. 1325 Chesapeake Terrace
Ulrich Drepper \,---' \ Sunnyvale, CA
e like the shmfs.
> So you have unix file permissions on them ?
See above. Permissions are only allowed for named semaphores.
--
---. ,-. 1325 Chesapeake Terrace
Ulrich Drepper \,---' \ Sunnyvale, CA 94089 USA
Red Hat
sions to
the file change?
The kernel representation of the mutex must not be disassociated from
the shared memory region.
Even if you all think very little about Solaris, look at the kernel
interface for semaphores.
--
---. ,-. 1
#x27;t really care what the final implementation will be like. For
UP and SMP machines I definitely want to have as much as possible at
user-level. If you need a special libpthread for NUMA machines, so be
it.
--
---. ,-. 1325 Chesapeake
doing this her/himself.
--
---. ,-. 1325 Chesapeake Terrace
Ulrich Drepper \,---' \ Sunnyvale, CA 94089 USA
Red Hat `--' drepper at redhat.com `
-
To unsubscribe from this list: send the line
1 + 1;
i = (int *) (m2 + 1);
while (1)
{
++*i;
pthread_mutex_unlock (m1);
pthread_mutex_lock (m2);
}
return 0;
}
~~~~~~~
--
---. ,-. 1325 Chesapeake Terrace
Ulrich Drepper \,---'
Jens Axboe <[EMAIL PROTECTED]> writes:
> Does attached patch fix it?
Yes.
--
---. ,-. 1325 Chesapeake Terrace
Ulrich Drepper \,---' \ Sunnyvale, CA 94089 USA
Red Hat `--' dr
mplement something else I couldn't care less since it's useless for
me.
--
---. ,-. 1325 Chesapeake Terrace
Ulrich Drepper \,---' \ Sunnyvale, CA 94089 USA
Red Hat `--' drepper at redhat.com `
zes the FPU. This was always the case
and necessary to implement the fast lazy FPU saving/restoring.
Processes which never use the FPU never initialize it.
--
---. ,-. 1325 Chesapeake Terrace
Ulrich Drepper \,---' \ Sunnyva
kernel code and the features of
the processor first. The kernel can detect when the FPU is used for
the first time.
--
---. ,-. 1325 Chesapeake Terrace
Ulrich Drepper \,---' \ Sunnyvale, CA 94089 USA
Red Hat `--'
IMHO the POSIX is doable to comply with POSIX. Probably not what many
of the RT freaks expect, but doable. I'm tuning the nanoseconds for a
while now...
Ulrich
On 17 Apr 2001, at 11:53, george anzinger wrote:
> I was thinking that it might be good to remove the POSIX API for the
>
range
(maybe even more). The patch tries to keep binary compatibility, too.
Opinions?
Regards,
Ulrich
--- kernel/243time.cMon Apr 16 20:14:27 2001
+++ kernel/xxxtime.cMon Apr 16 20:41:15 2001
@@ -100,7 +100,8 @@
write_lock_irq(&xtime_lock);
xtime.tv_se
Hi,
browsing the sources for some problem I wondered why nvram.c uses a
static spinlock named rtc_lock, hiding the global one.
Regards,
Ulrich
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo inf
So either the kernel
corrupts the very same inode every time, or e2fsck does not really fix
it, or the error simply doesn't exist. I think the kernel doesn't
temporarily set the size to non-zero, so this seems strange.
Regards,
Ulrich
-
To unsubscribe from this list: send the lin
nes. In the former it's called "CMOS-RAM", in the
latter
* "NVRAM" (NV stands for non-volatile).
Regards,
Ulrich
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://
On 26 Feb 2001, at 10:48, Andreas Dilger wrote:
> Ulrich Windl writes:
> > I had an interesting effect: Due to NVdriver I had a lot of system
> > freezes, and I had to reboot. Using e2fsck 1.19a (SuSE 7.1) I got the
> > message that one specific "Special (device
pid idea. No kernel and no libc modifications necessary. This is
the end of the story as far as I'm concerned.
--
---. ,-. 1325 Chesapeake Terrace
Ulrich Drepper \,---' \ Sunnyvale, CA 94089 USA
Red Hat
mment typo in asm-i386/pgtable-3level.h.
Ciao,
Uli Kunitz
--
Ulrich Kunitz ([EMAIL PROTECTED])
--- linux-2.4.2/include/asm-i386/pgalloc.h Thu Feb 22 01:09:57 2001
+++ linux/include/asm-i386/pgalloc.hSun Mar 4 20:14:50 2001
@@ -92,9 +92,9 @@
free_page((unsigned lon
David Miller wrote:
>From: Ulrich Weigand <[EMAIL PROTECTED]>
>Date: Mon, 1 Jan 2001 23:15:26 +0100 (MET)
>
> * Is there some reason why ptep_test_and_clear_young should
> *not*, after all, flush the TLB?
>
> Yes, because the accuracy of that s
> +}
This is wrong. You cannot execute libc.so.5. This only works with
glibc.
--
---. ,-. 1325 Chesapeake Terrace
Ulrich Drepper \,---' \ Sunnyvale, CA 94089 USA
Red Hat `--' drepper at redhat.com `-
les
there).
--
---. ,-. 1325 Chesapeake Terrace
Ulrich Drepper \,---' \ Sunnyvale, CA 94089 USA
Red Hat `--' drepper at redhat.com `
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a messag
bc5) => /usr/i486-linux-libc5/lib/libc.so.5
and then look in that directory (/usr/i486-linux-libc5/lib).
--
---. ,-. 1325 Chesapeake Terrace
Ulrich Drepper \,---' \ Sunnyvale, CA 94089 USA
Red Hat `--' drepper at redhat.com `--
fi
> ;;
Why don't you, as the other script suggested, execute libc.so.6?
Symlinks can be missing or can be wrong.
--
---. ,-. 1325 Chesapeake Terrace
Ulrich Drepper \,---' \ Sunnyvale, CA 9408
:
Regards,
Ulrich
-
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/
I thought I'd find a diff between 2.4.0test12 (last test release) to
the final 2.4.0 release, but did not. Wouldn't it be (have been) a good
idea?
Regards,
Ulrich
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMA
On 8 Jan 2001, at 14:16, Andreas Jaeger wrote:
> >>>>> Ulrich Windl writes:
>
> > I thought I'd find a diff between 2.4.0test12 (last test release) to
> > the final 2.4.0 release, but did not. Wouldn't it be (have been) a good
> > idea?
Inspecting some code I found out that in 2.4.0test12
request_irq() is declared in sched.h, and not in interrupt.h,
SA_SHIRQ is declared in asm/signal.h, and not in interrupt.h
Isn't that a bit confusing? Maybe for 2.5 let's re-sort some things to
clean up dependencies...
Regar
01.149
cache size : 128 KB
fdiv_bug: no
hlt_bug : no
sep_bug : no
f00f_bug: no
coma_bug: no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 sep mtrr pge mca cmov pat pse36
I could guess that the disc-
change ore write-protect status was not updated in some case.
Maybe it rings some bell for one of you; if not, never mind.
Regards,
Ulrich
-
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/
page_alloc.c:74!
Jan 10 22:14:54 kernel: invalid operand:
So long.
Ulrich
-
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/
jne2a <_EIP+0x2a> c0126127
Code; c012610e
11: 68 c5 01 00 00push $0x1c5
In /var/log/kernlog, this incident was reported as follows:
Jan 10 22:14:54 kernel: kernel BUG at page_alloc.c:74!
Jan 10 22:14:54 kernel: invalid operand:
So long.
Ulrich
-
On Wed, Jan 10, 2001 at 09:21:57PM -0200, Marcelo Tosatti wrote:
>> kernel BUG at vmscan.c:452!
>> invalid operand:
> Does reiserfs patch changes vmscan.c ?
No, it doesn't.
It's strange that the console reported vmscan.c:452 whilst
kern.log reports page_alloc.c:
ear to obtain the old pte
+ * not possible, use ptep_get_and_clear to obtain the old pte
* value and then use set_pte to update it. -ben
*/
static inline void set_pte(pte_t *ptep, pte_t pte)
--
Ulrich Kunitz ([EMAIL PROTECTED])
-
To unsubscribe from this list: send the line "unsubscribe l
t(pmd)
#define pmd_free_kernelpmd_free
#define pmd_alloc_kernel pmd_alloc
--
Ulrich Kunitz ([EMAIL PROTECTED])
-
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/
not to have a /proc/sys/kernel/time
directory, I'd also suggest to accept the patch for
/usr/src/linux/include/sysctl.h for the standard kernel. Currently I
have allocated "50" for the "time" entry. I'd like to have a sta
onds on network and non-UNIX filesystems? >:-)
You mean to say that a leap second is an implicit time update? I can
Implement it without any trouble, if you all can agree that the idea is
acceptable. BTW: Same applies for RTCs using local time, and we switch
from/to DST: The kernel doesn'
ng...
The driver being used was
Adaptec AHA274x/284x/294x (EISA/VLB/PCI-Fast SCSI) 5.1.31/3.2.4
After that, everything worked fine.
Regards,
Ulrich
-
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/
got a conflict between
and , but it was too late to investigate. (I had done
over 4 hours merging rejected diffs, and I was tired from pressing C-d
C-d C-n in Emacs ;-))
Regards,
Ulrich
-
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/
/pub/linux/daemons/ntp/PPS on most mirrors of quality ;-)
Regards,
Ulrich
-
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/
situations.
What's the correct way to fix this? In mlock and mprotect,
potentially many segments could be freed; do we need to
call lock_vma_mappings on all of them before calling
merge_segments?
Mit freundlichen Gruessen / Best Regards
Ulrich Weigand
--
Dr. Ulrich Weigand
Linux for S/390 D
On 30 Aug 2000, at 8:49, Mike Galbraith wrote:
> On Wed, 30 Aug 2000, Ulrich Windl wrote:
>
> > The syslog (2.5kB) with surrounding messages is attached.
>
> No it's not :)
8-(
It happened because of forwarding the bounced message from
vger.rutgers.edu.
Now it is a
nning that kernel on that machine before without
problems. Only kswapd seemed instable in 2.2.16. My machine, a P100,
has 64MB RAM.
The syslog (2.5kB) with surrounding messages is attached.
Regards,
Ulrich
P.S. The library issue is probably due to SuSE-7.0.
-
To unsubscribe from this list: sen
plementation.
[1] Since Linus says so it must be true.
--
---. ,-. 1325 Chesapeake Terrace
Ulrich Drepper \,---' \ Sunnyvale, CA 94089 USA
Red Hat `--' drepper at redhat.com `
-
To unsubscrib
ase about
just that. And I know that there are many other users with this
problem.
--
---. ,-. 1325 Chesapeake Terrace
Ulrich Drepper \,---' \ Sunnyvale, CA 94089 USA
Red Hat `--' drepper at redhat.com `
problem: you cannot send a signal explicitly to this thread
(to implement pthread_kill). The PID of this initial thread is now
used as the PID of the thread group.
--
---. ,-. 1325 Chesapeake Terrace
Ulrich Drepper \,---' \
ds. That's the
whole purpose of this exercise.
--
---. ,-. 1325 Chesapeake Terrace
Ulrich Drepper \,---' \ Sunnyvale, CA 94089 USA
Red Hat `--' drepper at redhat.com `
-
To unsubscribe from this list: send the line "unsubscribe
e first clone() but this is solvable.
--
---. ,-. 1325 Chesapeake Terrace
Ulrich Drepper \,---' \ Sunnyvale, CA 94089 USA
Red Hat `--' drepper at redhat.com `
-
To unsubscribe from this l
In a second stage where we have m kernel threads and n user-level
threads (the ultimate goal) things might be different. But this is
beyond what is needed in the 2.4 kernel so lets just skip the
SA_NOCLDWAIT stuff for now.
--
---. ,-. 1325
g. You have of course to swap before
the clone since the new thread will use the stack.
--
---. ,-. 1325 Chesapeake Terrace
Ulrich Drepper \,---' \ Sunnyvale, CA 94089 USA
Red Hat `--' drepper at redhat.com `
problems with changing UID/GID
It will require some investigation to see whether we can implement the
restart semantics correctly without a manager thread. If yes, we
should be able to live with the simple loop.
--
---. ,-. 1325 Chesapeake Terrace
Ulrich Dr
#x27;s see what I have next week.
--
---. ,-. 1325 Chesapeake Terrace
Ulrich Drepper \,---' \ Sunnyvale, CA 94089 USA
Red Hat `--' drepper at redhat.com `
-
To unsubscribe from this list: send the line &
rrent modification (based on PPSkit-0.9.3) is "nanofix.diff.gz",
both located on your favourite Linux mirror in
pub/linux/daemons/ntp/PPS (or very similar).
Regards,
Ulrich
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
se it this way.
--
---. ,-. 1325 Chesapeake Terrace
Ulrich Drepper \,---' \ Sunnyvale, CA 94089 USA
Red Hat `--' drepper at redhat.com `
-
To unsubscribe from this list: send the line "
already used CLONE_SIGHAND and is not prepared for thread
groups all hell breaks loose.
I've told Linus several times about this problems but he puts out one
test release after the other without this fixed.
--
---. ,-. 1325 Chesapeake Terra
r is someone already working on this?
"Fixing" alone won't cut it. I've started a rewrite and send Linus
more comments about what is needed but not even got a reply. Seems
the short interest span is already over.
--
---.
tely unrelated. The fix for your problem is to change
the CLONE_SIGHAND flag back to it's original behavior. Changing
linuxthreads to take advantage of the new kernel functionality is on a
different plate.
--
---. ,-. 1325 Chesapea
1 - 100 of 623 matches
Mail list logo
