Followup-For: Bug #738575
X-Debbugs-Cc: raykinsell...@gmail.com
On Thu, 16 Nov 2023 12:47:40 +, James wrote:
> I've been thinking more about how to improve the chances that the
> package could be accepted into Debian -- my suggestion would be to
> rebuild it and upload it to
On Thu, 16 Nov 2023 at 09:57, Ray Kinsella wrote:
>
> On Wed, 15 Nov 2023 at 22:30, James Addison wrote:
>>
>> On Wed, 15 Nov 2023 at 21:57, Ray Kinsella wrote:
> [...]
> I spent a not insignificant amount of time devising this solution, to get
> "Debian Support"
> After a few false starts and
hering dust in
Frys and Maplin.
So I couldn't say how many are in the wild being used.
It was the
> energy-efficiency focus of them that gathered my interest in the first
> place, FWIW.
>
>
Boards like the Up-board (https://up-board.org/) and its successors really
filled this g
how widely-adopted they were. It was the
energy-efficiency focus of them that gathered my interest in the first
place, FWIW.
> On Wed, 15 Nov 2023 at 12:27, James Addison wrote:
>>
>> Followup-For: Bug #738575
>> X-Debbugs-Cc: raykinsell...@gmail.com
>>
>>
12:27, James Addison wrote:
> Followup-For: Bug #738575
> X-Debbugs-Cc: raykinsell...@gmail.com
>
> If I understand correctly, then Ray's libx1000 library[1] provides a way to
> work around this in software. It uses some LD_PRELOAD magic, and from
> what I
> remember
Followup-For: Bug #738575
X-Debbugs-Cc: raykinsell...@gmail.com
If I understand correctly, then Ray's libx1000 library[1] provides a way to
work around this in software. It uses some LD_PRELOAD magic, and from what I
remember, it's worth being careful when using that approach.
I opene
Hälsningar!
Mitt namn är barrister Fatma Karatas, jag är en juridisk utövare som
arbetar inom alla områden av familjens jurisdiktion. Jag kontaktade dig för
att hjälpa mig med anspråket och överföringen av pengar ($6 450 000) som
lämnats kvar av min bortgångna klient som miste livet med sin famil
for all lovers of t-shirt ideas to offer or to wear on Valentine's Day
click on the amazon link below
https://amzn.to/2CdX642
for all lovers of t-shirt ideas to offer or to wear on Valentine's Day
click on the amazon link below
https://amzn.to/2CdX642
best regards
Good day my good friend,
Let me start by introducing myself. I am James Musa, an accounts
officer with Bank of Africa here in Burkina Faso West Africa.
I am writing you this letter based on the latest development at my
bank whichI will like to bring to your personal edification.
($9million) tran
Hi all,
I have done some investigation here and it seems that the CPU microcode
cannot be updated on these platforms, which brings us back to fixing the
issue in software. ( I am part of the Intel BSP team for Quark platforms ).
In order to support Quark/Galileo the most straight forward approach
What version of glibc are you compiling? Can you offer some more
assistance as to how you compiled it? Are you cross-compiling or do have
a working set of tools on your galileo to compile natively?
I am attempting to compile from my Ubuntu 14.04 (64-bit) machine with
../glibc-2.20/configure
Aurélien you are correct - some logic is required to use the
-momit-lock-prefix flag for Quark and not for all other CPUs. This is
possible in embedded, cross-compilation environments which build
everything from source (e.g. Yocto) but more difficult elsewhere.
2014-10-21 11:25 GMT+01:00 Aurelien
control: tag -1 + wontfix
On Sun, Oct 19, 2014 at 11:44:02PM +0100, Marc Herbert wrote:
> See the new "-momit-lock-prefix" option added to binutils (gas) in
> order to solve this issue:
>
> https://sourceware.org/ml/binutils/2014-08/msg00093.html
It might solve this issue for Intel Quark, but it
See the new "-momit-lock-prefix" option added to binutils (gas) in
order to solve this issue:
https://sourceware.org/ml/binutils/2014-08/msg00093.html
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.
Hi,
On 08/05/14 22:11, Aurelien Jarno wrote:
On Thu, May 08, 2014 at 04:45:00PM +0200, Jan Just Keijser wrote:
Hi,
FWIW: I've got a Galileo board and am running into similar issuse
(while running CentOS 5 on it ;))
Exact same error at the exact same location; it's not the
instruction that is
On Thu, May 08, 2014 at 04:45:00PM +0200, Jan Just Keijser wrote:
> Hi,
>
> FWIW: I've got a Galileo board and am running into similar issuse
> (while running CentOS 5 on it ;))
>
> Exact same error at the exact same location; it's not the
> instruction that is not supported , a very small piece
Hi,
FWIW: I've got a Galileo board and am running into similar issuse (while
running CentOS 5 on it ;))
Exact same error at the exact same location; it's not the instruction
that is not supported , a very small piece of test code that does
lock cmpxchgl %edx, (%eax)
works just fine - and
FYI, http://en.wikipedia.org/wiki/Pentium_F00F_bug
On Wed, Mar 12, 2014 at 10:07:43PM +0100, Thomas Karmann wrote:
> On 12.03.2014 (21:20), Aurelien Jarno wrote:
> > While it shows that the problem is at the CPU level, it's not really a
> > fix, as the bus is not locked anymore, so it might results in issues in
> > multithreaded solution.
> >
> >
On 12.03.2014 (21:20), Aurelien Jarno wrote:
> While it shows that the problem is at the CPU level, it's not really a
> fix, as the bus is not locked anymore, so it might results in issues in
> multithreaded solution.
>
> The correct solution would be to apply the solution from Intel, that is
> ad
On Wed, Mar 12, 2014 at 03:31:57PM +0100, Thomas Karmann wrote:
> Hi,
>
> I patched out the lock instruction via hexedit and the segfaults are gone!
>
> before:
>
> => 507b: f0 0f b1 8b 94 21 00lock cmpxchg %ecx,0x2194(%ebx)
>
> after:
>
> 507b: 90 nop
On Wed, Mar 12, 2014 at 04:33:45PM +0100, Thomas Karmann wrote:
> Intel knows about this, see the errata (page 15):
> http://downloadmirror.intel.com/23197/eng/Quark_SW_RelNotes_330232_001.pdf
Thanks for digging on this issue, that indeed explains a lot.
It's probably something we can fix in glib
Intel knows about this, see the errata (page 15):
http://downloadmirror.intel.com/23197/eng/Quark_SW_RelNotes_330232_001.pdf
With kind regards
Thomas
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.
Hi,
I patched out the lock instruction via hexedit and the segfaults are gone!
before:
=> 507b: f0 0f b1 8b 94 21 00lock cmpxchg %ecx,0x2194(%ebx)
after:
507b: 90 nop
507c: 0f b1 8b 94 21 00 00cmpxchg %ecx,0x2194(%ebx)
Might be a bug in
I think that it's a race condition as it doesn't happen every time
--
Matteo Croce
OpenWrt Developer
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
On Sun, 2 Mar 2014, Aurelien Jarno wrote:
The test would be to run one of the affected program under gdb, add a
breakpoint on __nptl_setxid, and understand why the memory access fail.
With gdb attached, the crash does not happen. I've got some more things
to try though.
On Fri, Feb 28, 2014 at 10:43:07AM -0500, Stuart Anderson wrote:
>
> I have access to a couple of these boards. I'll be glad to run some tests if
> needed.
>
The test would be to run one of the affected program under gdb, add a
breakpoint on __nptl_setxid, and understand why the memory access f
I have access to a couple of these boards. I'll be glad to run some tests if
needed.
Stuart
Stuart R. Anderson ander...@netsweng.com
Network & Software Engineering http://www.netsweng.com/
1024D/37A79149:
On Mon, Jan 01, 2001 at 12:23:05AM +, Thomas Faust wrote:
> Package: libc6
> Version: 2.13-38
> Severity: normal
> File: pthread
>
> Dear Maintainer,
>
> I bootstrapped a Debian base system via "debootstrap --arch i386 wheezy
> ./newfiles http://http.debian.net/debian/"; and put it on a Gali
> The default toolchain (and thus libc) in Debian has been targetting
> i586 for quite a while now. If this CPU doesn't provide *all* the
> i586 instructions, I'd be pretty surprised if anything worked.
I was first trending in the same direction, but this is a different issue.
I compiled code with
On Mon, Jan 01, 2001 at 12:23:05AM +, Thomas Faust wrote:
>
> which is basically a 486 with some instructions extensions from Pentium.
The default toolchain (and thus libc) in Debian has been targetting
i586 for quite a while now. If this CPU doesn't provide *all* the
i586 instructions, I'd
Package: libc6
Version: 2.13-38
Severity: normal
File: pthread
Dear Maintainer,
I bootstrapped a Debian base system via "debootstrap --arch i386 wheezy
./newfiles http://http.debian.net/debian/"; and put it on a Galileo board. On
the Galileo board there new Intel Quark IA processor - which is b
33 matches
Mail list logo
