Hi,
Please have a look at upstream bug report:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61799
I was asked to test GCC 4.8 and found this issue go away with
locally-recompiled GCC 4.8.2 (upstream source, as ia64 is no more
supported by Debian).
Whether this was expected or not, I don't know.
This has nothing to do with kernel version, but with gcc version, as
alluded to nearly two years ago by Stephan Schreiber [1]...
Upstream bug report: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61799
Émeric
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691576#10
--
To UNSUBSCRIB
Émeric
2014-01-19 20:55 GMT+01:00 Kurt Roeckx :
> On Sun, Jan 19, 2014 at 08:40:27PM +0100, Émeric MASCHINO wrote:
>>
>> [1] https://lists.debian.org/debian-68k/2013/05/msg00065.html <===
>> BTW, why is it archived on debian-68k?
>
> Because it was send to debian-port
2014/1/12 Ben Hutchings :
>
> If you have space to install wheezy on a separate partition, please can
> you try that.
>
> (Of course, that crash ought to be fixed in 3.2.y. But I don't know
> that anyone will have the time and knowledge to do so. And it's not
> part of this bug.)
No more empty p
2014/1/12 Ben Hutchings :
>
> Sorry, I'm being silly. udev is built as part of systemd now, so this
> is independent of whether you use systemd as init. And systemd doesn't
> currently run as init in the initramfs.
Uh, OK.
How can I help further?
Emeric
--
To UNSUBSCRIBE, email to debi
2014/1/12 Ben Hutchings :
>
> You can have sysvinit and systemd installed in parallel and then use the
> 'init' kernel parameter to switch between them. Only systemd-sysv
> conflicts/replaces sysvinit.
So, I've reinstalled sysvinit and sysvinit-core that purged
systemd-sysv. I can't however remov
2014/1/12 Ben Hutchings :
>
> So this is a crash, not an incompatibility with the newer systemd.
[...]
> Can you test the 3.2 kernel with sysvinit, in case this is a bug that's
> specifically provoked by systemd?
That's why I was saying "too old for my current Debian install" on Jan 6th.
Since
2014/1/7 Ben Hutchings :
> On Mon, 2014-01-06 at 10:15 +0100, Émeric MASCHINO wrote:
>
> I don't understand that - I still have 3.2 installed on this unstable
> (i386) system and can still boot it. How does it go wrong?
It seems to crash with something wrong with systemd.
You&#
Hi,
And happy new year!
2013/12/20 Ben Hutchings :
>> > I actually tried building the kernel like that, so you could try the
>> > packages in:
>> >
>> > http://people.debian.org/~benh/packages/wheezy-ia64-kernel-O1/
>>
>> Was your O1-compiled kernel working fine?
>
> I have no idea as no-one has
2013/12/12 Ben Hutchings :
> So far as I know, there is no longer any commercial development of
> Linux on Itanium. Some old 'enterprise' distributions might
> continue to be supported for a few years but mainline isn't
> supported.
It seems that Intel must provide hp with Itanium CPUs till 2017
finitely working fine then or just being lucky because of a
working kernel configuration?
Émeric
[1] http://marc.info/?l=linux-ia64&m=134858659916369&w=2
[2] http://marc.info/?l=linux-ia64&m=133124040906499&w=2
[3] http://lists.debian.org/debian-ia64/2013/09/msg00024.html
2013/12/11 Ben
FYI, linux-image-3.11-2-mckinley 3.11.10-1 in today's Jessie updates
didn't change anything w.r.t. gdb problem.
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/CAA9x
FYI, linux-image-3.11-2-mckinley 3.11.8-1 in today's Jessie updates
breaks gdb again.
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/CAA9xbM62AZ4+r9amXZ3Qyu=cwdfte_
FYI, linux-image-3.10-3-mckinley 3.10.11-1 in today's Jessie updates
brought back gdb to life.
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/CAA9xbM7A--Hj6uQ0bmCFw
Hi,
Just to let you know that linux-image-mckinley 3.10+52 in today's
Jessie updates once again brought back gdb to life.
Go figure...
Émeric
2013/9/21 Émeric MASCHINO :
> Hi,
>
> I don't know what kind of information this can provide, if any, but here's it.
>
r feature, like auditing support or cgroups support, or
PPP module, gdb doesn't work anymore.
I've also tested the working configuration for kernels 3.5.7,
3.5.7-r1, 3.7.10, 3.7.10-r1 and 3.8.13 without a success.
Any ideas/suggestions to go further?
Émeric
2013/8/15 Émeric M
Hi,
Just to let you know that, while kernel 3.9.8-1 was working fine, the
"gdb stops with SIGTRAP at 0" bug is back with kernel 3.10.5-1 in
today's "Jessie" Testing updates :-(
Émeric
2013/8/8 Ben Hutchings :
> On Wed, 2013-08-07 at 16:54 -0400, Camm Maguire wrote:
>> Greetings!
>>
>> Steph
Hello,
To pass parameters to kernel, add an append= line in your elilo.conf
file, just below the initrd= line. In the present case:
append="debug=vc"
Please find attached the log that I've just recorded on a serial
console passing debug=vc to kernel.
Well, I don't see anything useful or dif
Emeric
2012/4/15 Émeric Maschino :
> Hi,
>
> Patch proposed by Tony Luck in
> https://bugzilla.kernel.org/show_bug.cgi?id=42757 works for me :-)
>
> Bug report updated accordingly.
>
> Emeric
>
>
> Le 11 février 2012 16:54, Émeric Maschino a écrit
&g
Hi,
Patch proposed by Tony Luck in
https://bugzilla.kernel.org/show_bug.cgi?id=42757 works for me :-)
Bug report updated accordingly.
Emeric
Le 11 février 2012 16:54, Émeric Maschino a écrit :
> Hi,
>
> Time to track this issue:
> http://bugs.debian.org/cgi-bin/bugreport.cg
Hi,
Tony Luck proposed a patch to fix this issue in
https://bugzilla.kernel.org/show_bug.cgi?id=42757.
Current Debian Testing kernel 3.2-14 locally rebuilt including this
patch works as expected :-)
Many thanks,
Emeric
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
or not, and the return value is certainly used by
> the callers.
>
> Patrick
>
> On Sat, Jan 28, 2012 at 6:43 AM, Émeric Maschino
> wrote:
>>
>> Hi,
>>
>> Just to let you know that I've bisected this issue to commit
>> 37a9d912b24f96a0591773e6e6c3
Package: linux-image-3.2.0-1-mckinley
Version: 3.2.4-1
Severity: important
As reported first in
http://lists.debian.org/debian-ia64/2012/01/msg00016.html, I'm getting
stability issues with kernel > 2.6.38.
I've bisected the problem to commit
37a9d912b24f96a0591773e6e6c3642991ae5a70 (futex: Saniti
tex change and
that renders IA-64 barely usable at this time.
Émeric
Le 4 février 2012 19:32, Émeric Maschino a écrit :
> Hi,
>
> Just to let you know that, as could have been guessed from my initial
> post (http://lists.debian.org/debian-ia64/2012/01/msg00016.html),
> PulseAu
7;t appear in the
> inputs/outputs list). From looking at the x86 version (agh, inline asm is
> hard to parse), it does modify the return value based on whether the
> comparison was a success or not, and the return value is certainly used by
> the callers.
>
> Patrick
>
> O
Hi,
Just to let you know that I've bisected this issue to commit
37a9d912b24f96a0591773e6e6c3642991ae5a70
(futex: Sanitize cmpxchg_futex_value_locked API).
Émeric
Le 17 janvier 2012 23:11, Émeric Maschino a écrit :
> Hi,
>
> Since there's a workaround allowing us to
Hi,
Since there's a workaround allowing us to go kernel > 2.6.38
(http://lists.debian.org/debian-ia64/2012/01/msg00013.html), I
obviously updated my Testing system to current
linux-image-3.1.0-1-mckinley_3.1.8-2_ia64.deb.
Well, graphical desktop experience is _unstable_. When I say "desktop
exper
Le 15 janvier 2012 19:08, maximilian attems a écrit :
>> Nice detective work. So the next question is: why does klibc-utils on
>> ia64 provide /usr/lib/klibc/bin/sh instead of sh.shared like other
>> architectures?
>
> #439181 ia64 works only static
Thanks for pointing this out.
>> I'd also be
Hi,
I've identified the root cause of this issue: busybox hook is called
_before_ klibc one. This ends up with /bin/sh binary in the generated
initrd.img being a copy of (or a symlink to) system
/usr/lib/klibc/bin/sh binary whereas it is expected to be a copy of
(or a symlink to) system /bin/busyb
From: Émeric Maschino
Subject: ia64: Add accept4() syscall
While debugging udev > 170 failure on Debian Wheezy
(http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=648325), it appears
that the issue was in fact due to missing accept4() in ia64.
This patch simply adds accept4() to ia64. The
a
Hi,
Any progress on this? How can I help further?
It's still impossible to either install Wheezy on ia64 from Debian
netinst CD or upgrade from a running Lenny system as kernel > 2.6.38
need initramfs-tools 0.99 that produces unbootable initrd images.
Best regards,
Émeric
--
To UNSUBSCR
Hi,
> does initramfs-tools boot with BUSYBOX=no in initramfs.conf?
Well, I don't know! Indeed, with BUSYBOX=no in initramfs.conf,
initrd.img generation fails:
root@longspeak:/# dpkg-reconfigure linux-image-3.0.0-1-mckinley
Running depmod.
Examining /etc/kernel/postinst.d.
run-parts: executing /et
Package: initramfs-tools
Version: 0.99
Severity: grave
As stated in this thread
http://lists.debian.org/debian-ia64/2011/08/msg1.html, Debian
"Wheezy" Testing cannot be booted at all on IA-64 (current
linux-image-3.0.0-1-mckinley in Testing depends on initramfs-tools
0.99, so initramfs-tools c
2010/2/2 maximilian attems :
>> I've bisected this problem to commit
>> f1a2a9b6189f9f5c27672d4d32fec9492c6486b2 (drm: Preserve SHMLBA bits in
>> hash key for _DRM_SHM mappings), during kernel 2.6.30 development cycle.
>
> please report upstream on bugzilla.kernel.org and let us know
> the bug nr s
34 matches
Mail list logo
