Re: Bug#711135: Re: compiling a bootable kernel for ia64 (itanium2, mckinley, rx2620)

[John Paul Adrian Glaubitz]

On 02/25/2018 03:24 PM, Eberhard Heuser wrote:
> dpkg --version
> Debian »dpkg« Paketmanagement-Programm Version 1.16.18 (ia64).
> Dies ist freie Software; lesen Sie die GNU General Public License in der
> Version 2 oder höher für Kopierbedingungen. Es wird KEINE Haftung übernommen.
> 
> I cannot see how to get a newer version.

What's the output of:

# apt-cache policy dpkg

1.16.18 is definitely too old. Need at least 1.17.27.

Fetch it from here: https://people.debian.org/~glaubitz/ia64/

# wget https://people.debian.org/~glaubitz/ia64/dpkg_1.17.27_ia64.deb 
https://people.debian.org/~glaubitz/ia64/libdpkg-dev_1.17.27_ia64.deb
https://people.debian.org/~glaubitz/ia64/libdpkg-perl_1.17.27_all.deb

# dpkg -i *dpkg*deb

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Re: Bug#711135: Re: compiling a bootable kernel for ia64 (itanium2, mckinley, rx2620)

[John Paul Adrian Glaubitz]

On 02/25/2018 03:00 PM, Eberhard Heuser wrote:
> This is what I get, if I add the lines above:
> 
> debconf: apt-extracttemplates schlug fehl: Datei oder Verzeichnis nicht 
> gefunden
> Extrahiere Vorlagen aus Paketen: 100%
> dpkg-deb: Fehler: Archiv »/var/cache/apt/archives/base-files_10.1_ia64.deb« 
> enthält nicht verstandene Datenelemente control.tar.xz, Abbruch
> dpkg: Fehler beim Bearbeiten von 
> /var/cache/apt/archives/base-files_10.1_ia64.deb (--unpack):
>  Unterprozess dpkg-deb --control gab den Fehlerwert 2 zurück
> Fehler traten auf beim Bearbeiten von:
>  /var/cache/apt/archives/base-files_10.1_ia64.deb
> E: Sub-process /usr/bin/dpkg returned an error code (1)
> 
> Any ideas?

You need to upgrade "dpkg" first before you can perform a dist-upgrade:

# apt-get install dpkg

Your current version of dpkg doesn't know how to handle xz compression.

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Re: Bug#711135: Re: compiling a bootable kernel for ia64 (itanium2, mckinley, rx2620)

[Eberhard Heuser]

Am 20.02.2018 um 16:02 schrieb John Paul Adrian Glaubitz:
On 02/20/2018 03:46 PM, Eberhard Heuser wrot> This is the same wrong 
behavior with my zx2000 Itanium machine.

I was able to install the latest debian distribution.
I managed to update the kernel by hand but all the other software
gets no update because Debian stops the IA64 support.


Actually, we recently just re-added ia64 as part of Debian Ports.

You just need to update your sources.list:

# binary default
deb http://ftp.ports.debian.org/debian-ports/ unstable main
deb http://incoming.ports.debian.org/buildd/ unstable main
deb http://ftp.ports.debian.org/debian-ports/ unreleased main

# source
deb-src http://ftp.debian.org/debian/ unstable main
deb-src http://incoming.debian.org/debian-buildd/ buildd-unstable main

And install the debian-ports-archive-keyring package.

Adrian



This is what I get, if I add the lines above:

debconf: apt-extracttemplates schlug fehl: Datei oder Verzeichnis nicht 
gefunden

Extrahiere Vorlagen aus Paketen: 100%
dpkg-deb: Fehler: Archiv 
»/var/cache/apt/archives/base-files_10.1_ia64.deb« enthält nicht 
verstandene Datenelemente control.tar.xz, Abbruch
dpkg: Fehler beim Bearbeiten von 
/var/cache/apt/archives/base-files_10.1_ia64.deb (--unpack):

 Unterprozess dpkg-deb --control gab den Fehlerwert 2 zurück
Fehler traten auf beim Bearbeiten von:
 /var/cache/apt/archives/base-files_10.1_ia64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

Any ideas?
Eberhard

---
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus

Re: Bug#711135: Re: compiling a bootable kernel for ia64 (itanium2, mckinley, rx2620)

[Eberhard Heuser]

Am 14.02.2018 um 14:46 schrieb Jason Duerstock:

Hi Pedro,

Can you try booting this ISO and let us know what happens?
http://distfiles.gentoo.org/releases/ia64/autobuilds/20180201T031003Z/install-ia64-minimal-20180201T031003Z.iso

Thanks,

Jason




On Wed, Feb 14, 2018 at 2:52 AM, Pedro Miguel Teixeira <pm...@texair.net> wrote:


Hi Emeric.



The machine has no iLO card, so it can’t be because of it. As far as I can
tell, either ELILO never gets to pass control to the kernel, or the kernel
never gets to output the 1st message.



_
Pedro



From: Émeric MASCHINO
Sent: Tuesday, February 13, 2018 23:43
To: Pedro Miguel Teixeira
Cc: Jason Duerstock; Gatis Visnevskis; Ivan Zakharyaschev; debian-ia64;
gle...@altlinux.org


Subject: Re: Bug#711135: Re: compiling a bootable kernel for ia64 (itanium2,
mckinley, rx2620)



Well, problem is then likely with iLO card or serial console.
Indeed, I'm daily using a zx6000 workstation for years, being with
Debian for more than a decade, now with Gentoo since Debian has killed
the plug on ia64 in 2013.
I have no problem booting/using it locally (GNOME 3.24 desktop
environment) with kernels 4.9.76 and 4.12.12. Kernels were compiled
either with GCC 4.5.4 (because of a nasty error with GDB that
sometimes segfaults when kernels i compiled with GCC > 4.5) or 6.2.0.

2018-02-14 1:41 GMT+01:00 Pedro Miguel Teixeira <pm...@texair.net>:


Hi Jason.



That was close – I was really about to send the zx6000 onto the tech
recycle.



The following is all I get coming out from the console (Serial A, since
the
zx6000 does not have a management card / iLO). After the initrd line
shows,
a good 5 seconds pass. Then the front panel becomes all red and the
cryptic
modem-style sounds come out. I’ve wondered about the health of both my
ELILO
and Kernel, but my rx2660 boots fine with the exact the same two.





EFI Boot Manager ver 1.10 [14.61]  Firmware ver 2.31 [4411]



Loading device drivers



Loading.: Auxiliary Floating Point Driver

Load of Auxiliary Floating Point Driver failed: Not Found

EFI Boot Manager ver 1.10 [14.61]  Firmware ver 2.31 [4411]



Please select a boot option



 Windows Boot Manager

 Debian

 EFI Shell [Built-in]

 Removable Media

 Boot Option Maintenance Menu

 System Configuration Menu





 Use ^ and v to change option(s). Use Enter to select an option

Loading.: Debian

Starting: Debian

ELILO v3.14 for EFI/IA-64

..

Uncompressing Linux... done

Loading file \EFI\debian\initrd.img...done






This is the same wrong behavior with my zx2000 Itanium machine.
I was able to install the latest debian distribution.
I managed to update the kernel by hand but all the other software
gets no update because Debian stops the IA64 support.

The crash happens on a very early stage where no debug message
been produced by the starting process.

Eberhard

---
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus

Re: Bug#711135: Re: compiling a bootable kernel for ia64 (itanium2, mckinley, rx2620)

[John Paul Adrian Glaubitz]

On 02/20/2018 03:46 PM, Eberhard Heuser wrot> This is the same wrong behavior 
with my zx2000 Itanium machine.

I was able to install the latest debian distribution.
I managed to update the kernel by hand but all the other software
gets no update because Debian stops the IA64 support.


Actually, we recently just re-added ia64 as part of Debian Ports.

You just need to update your sources.list:

# binary default
deb http://ftp.ports.debian.org/debian-ports/ unstable main
deb http://incoming.ports.debian.org/buildd/ unstable main
deb http://ftp.ports.debian.org/debian-ports/ unreleased main

# source
deb-src http://ftp.debian.org/debian/ unstable main
deb-src http://incoming.debian.org/debian-buildd/ buildd-unstable main

And install the debian-ports-archive-keyring package.

Adrian

--
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Re: Bug#711135: Re: compiling a bootable kernel for ia64 (itanium2, mckinley, rx2620)

[James Clarke]

On 14 Feb 2018, at 07:52, Pedro Miguel Teixeira <pm...@texair.net> wrote:
> 
>  
> Hi Emeric.
>  
> The machine has no iLO card, so it can’t be because of it. As far as I can 
> tell, either ELILO never gets to pass control to the kernel, or the kernel 
> never gets to output the 1st message.

Apologies if you've already tried this or it doesn't apply in your case, but
have you tried the advice in [1]?

James

[1] https://lists.debian.org/debian-ia64/2004/05/msg00051.html

> _
> Pedro
>  
> From: Émeric MASCHINO
> Sent: Tuesday, February 13, 2018 23:43
> To: Pedro Miguel Teixeira
> Cc: Jason Duerstock; Gatis Visnevskis; Ivan Zakharyaschev; debian-ia64; 
> gle...@altlinux.org
> Subject: Re: Bug#711135: Re: compiling a bootable kernel for ia64 (itanium2, 
> mckinley, rx2620)
>  
> Well, problem is then likely with iLO card or serial console.
> Indeed, I'm daily using a zx6000 workstation for years, being with
> Debian for more than a decade, now with Gentoo since Debian has killed
> the plug on ia64 in 2013.
> I have no problem booting/using it locally (GNOME 3.24 desktop
> environment) with kernels 4.9.76 and 4.12.12. Kernels were compiled
> either with GCC 4.5.4 (because of a nasty error with GDB that
> sometimes segfaults when kernels i compiled with GCC > 4.5) or 6.2.0.
> 
> 2018-02-14 1:41 GMT+01:00 Pedro Miguel Teixeira <pm...@texair.net>:
> >
> >
> > Hi Jason.
> >
> >
> >
> > That was close – I was really about to send the zx6000 onto the tech
> > recycle.
> >
> >
> >
> > The following is all I get coming out from the console (Serial A, since the
> > zx6000 does not have a management card / iLO). After the initrd line shows,
> > a good 5 seconds pass. Then the front panel becomes all red and the cryptic
> > modem-style sounds come out. I’ve wondered about the health of both my ELILO
> > and Kernel, but my rx2660 boots fine with the exact the same two.
> >
> >
> >
> >
> >
> > EFI Boot Manager ver 1.10 [14.61]  Firmware ver 2.31 [4411]
> >
> >
> >
> > Loading device drivers
> >
> >
> >
> > Loading.: Auxiliary Floating Point Driver
> >
> > Load of Auxiliary Floating Point Driver failed: Not Found
> >
> > EFI Boot Manager ver 1.10 [14.61]  Firmware ver 2.31 [4411]
> >
> >
> >
> > Please select a boot option
> >
> >
> >
> > Windows Boot Manager
> >
> > Debian
> >
> > EFI Shell [Built-in]
> >
> > Removable Media
> >
> > Boot Option Maintenance Menu
> >
> > System Configuration Menu
> >
> >
> >
> >
> >
> > Use ^ and v to change option(s). Use Enter to select an option
> >
> > Loading.: Debian
> >
> > Starting: Debian
> >
> > ELILO v3.14 for EFI/IA-64
> >
> > ..
> >
> > Uncompressing Linux... done
> >
> > Loading file \EFI\debian\initrd.img...done
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > _
> > Pedro
> >
> >
> >
> > From: Jason Duerstock
> > Sent: Friday, February 9, 2018 04:01
> > To: Pedro Miguel Teixeira
> > Cc: Gatis Visnevskis; Ivan Zakharyaschev; debian-ia64; gle...@altlinux.org
> >
> >
> > Subject: Re: Bug#711135: Re: compiling a bootable kernel for ia64 (itanium2,
> > mckinley, rx2620)
> >
> >
> >
> > Hi Pedro,
> >
> > Can you file a separate bug for this, and include a boot log?
> >
> > Thanks,
> >
> > Jason
> >
> >
> > On Fri, Feb 9, 2018 at 6:24 AM, Pedro Miguel Teixeira <pm...@texair.net>
> > wrote:
> >>
> >>
> >> The latest kernel available from Debian does work fine on my Montvale
> >> rx2660. However, I cannot boot my McKinley zx6000 with it. It will MCA
> >> really early in the boot process.
> >>
> >>
> >>
> >> Linux b777 3.2.0-4-mckinley #1 SMP Debian 3.2.78-1 ia64 GNU/Linux
> >>
> >>
> >>
> >>
> >>
> >> _
> >> Pedro
> >>
> >>
> >>
> >> From: Gatis Visnevskis
> >> Sent: Friday, February 9, 2018 03:13
> >> To: Ivan Zakharyaschev
> >> Cc: Jason Duerstock; debian-ia64; gle...@altlinux.org
> >> Subject: Re: Bug#711135: Re: compiling a bootable kernel for ia64
> >> (itanium2,
> >> mckinley, rx2620)
> >>
> >>
> >>
> >> Hi all
> >>
> >> I got wor

Re: Bug#711135: Re: compiling a bootable kernel for ia64 (itanium2, mckinley, rx2620)

[Jason Duerstock]

Hi Pedro,

Can you try booting this ISO and let us know what happens?
http://distfiles.gentoo.org/releases/ia64/autobuilds/20180201T031003Z/install-ia64-minimal-20180201T031003Z.iso

Thanks,

Jason




On Wed, Feb 14, 2018 at 2:52 AM, Pedro Miguel Teixeira <pm...@texair.net> wrote:
>
>
> Hi Emeric.
>
>
>
> The machine has no iLO card, so it can’t be because of it. As far as I can
> tell, either ELILO never gets to pass control to the kernel, or the kernel
> never gets to output the 1st message.
>
>
>
> _
> Pedro
>
>
>
> From: Émeric MASCHINO
> Sent: Tuesday, February 13, 2018 23:43
> To: Pedro Miguel Teixeira
> Cc: Jason Duerstock; Gatis Visnevskis; Ivan Zakharyaschev; debian-ia64;
> gle...@altlinux.org
>
>
> Subject: Re: Bug#711135: Re: compiling a bootable kernel for ia64 (itanium2,
> mckinley, rx2620)
>
>
>
> Well, problem is then likely with iLO card or serial console.
> Indeed, I'm daily using a zx6000 workstation for years, being with
> Debian for more than a decade, now with Gentoo since Debian has killed
> the plug on ia64 in 2013.
> I have no problem booting/using it locally (GNOME 3.24 desktop
> environment) with kernels 4.9.76 and 4.12.12. Kernels were compiled
> either with GCC 4.5.4 (because of a nasty error with GDB that
> sometimes segfaults when kernels i compiled with GCC > 4.5) or 6.2.0.
>
> 2018-02-14 1:41 GMT+01:00 Pedro Miguel Teixeira <pm...@texair.net>:
>>
>>
>> Hi Jason.
>>
>>
>>
>> That was close – I was really about to send the zx6000 onto the tech
>> recycle.
>>
>>
>>
>> The following is all I get coming out from the console (Serial A, since
>> the
>> zx6000 does not have a management card / iLO). After the initrd line
>> shows,
>> a good 5 seconds pass. Then the front panel becomes all red and the
>> cryptic
>> modem-style sounds come out. I’ve wondered about the health of both my
>> ELILO
>> and Kernel, but my rx2660 boots fine with the exact the same two.
>>
>>
>>
>>
>>
>> EFI Boot Manager ver 1.10 [14.61]  Firmware ver 2.31 [4411]
>>
>>
>>
>> Loading device drivers
>>
>>
>>
>> Loading.: Auxiliary Floating Point Driver
>>
>> Load of Auxiliary Floating Point Driver failed: Not Found
>>
>> EFI Boot Manager ver 1.10 [14.61]  Firmware ver 2.31 [4411]
>>
>>
>>
>> Please select a boot option
>>
>>
>>
>> Windows Boot Manager
>>
>> Debian
>>
>> EFI Shell [Built-in]
>>
>> Removable Media
>>
>> Boot Option Maintenance Menu
>>
>> System Configuration Menu
>>
>>
>>
>>
>>
>> Use ^ and v to change option(s). Use Enter to select an option
>>
>> Loading.: Debian
>>
>> Starting: Debian
>>
>> ELILO v3.14 for EFI/IA-64
>>
>> ..
>>
>> Uncompressing Linux... done
>>
>> Loading file \EFI\debian\initrd.img...done
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> _
>> Pedro
>>
>>
>>
>> From: Jason Duerstock
>> Sent: Friday, February 9, 2018 04:01
>> To: Pedro Miguel Teixeira
>> Cc: Gatis Visnevskis; Ivan Zakharyaschev; debian-ia64; gle...@altlinux.org
>>
>>
>> Subject: Re: Bug#711135: Re: compiling a bootable kernel for ia64
>> (itanium2,
>> mckinley, rx2620)
>>
>>
>>
>> Hi Pedro,
>>
>> Can you file a separate bug for this, and include a boot log?
>>
>> Thanks,
>>
>> Jason
>>
>>
>> On Fri, Feb 9, 2018 at 6:24 AM, Pedro Miguel Teixeira <pm...@texair.net>
>> wrote:
>>>
>>>
>>> The latest kernel available from Debian does work fine on my Montvale
>>> rx2660. However, I cannot boot my McKinley zx6000 with it. It will MCA
>>> really early in the boot process.
>>>
>>>
>>>
>>> Linux b777 3.2.0-4-mckinley #1 SMP Debian 3.2.78-1 ia64 GNU/Linux
>>>
>>>
>>>
>>>
>>>
>>> _
>>> Pedro
>>>
>>>
>>>
>>> From: Gatis Visnevskis
>>> Sent: Friday, February 9, 2018 03:13
>>> To: Ivan Zakharyaschev
>>> Cc: Jason Duerstock; debian-ia64; gle...@altlinux.org
>>> Subject: Re: Bug#711135: Re: compiling a bootable kernel for ia64
>>> (itanium2,
>>> mckinley, rx2620)
>>>
>>>
>>>
>>> Hi all
>>>
>>> I got working 3.2.0 kernel after som

RE: Bug#711135: Re: compiling a bootable kernel for ia64 (itanium2, mckinley, rx2620)

[Pedro Miguel Teixeira]

Hi Emeric.

The machine has no iLO card, so it can’t be because of it. As far as I can 
tell, either ELILO never gets to pass control to the kernel, or the kernel 
never gets to output the 1st message.

_
Pedro

From: Émeric MASCHINO<mailto:emeric.masch...@gmail.com>
Sent: Tuesday, February 13, 2018 23:43
To: Pedro Miguel Teixeira<mailto:pm...@texair.net>
Cc: Jason Duerstock<mailto:jason.duerst...@gmail.com>; Gatis 
Visnevskis<mailto:ga...@pie-dabas.net>; Ivan 
Zakharyaschev<mailto:i...@altlinux.org>; 
debian-ia64<mailto:debian-ia64@lists.debian.org>; 
gle...@altlinux.org<mailto:gle...@altlinux.org>
Subject: Re: Bug#711135: Re: compiling a bootable kernel for ia64 (itanium2, 
mckinley, rx2620)

Well, problem is then likely with iLO card or serial console.
Indeed, I'm daily using a zx6000 workstation for years, being with
Debian for more than a decade, now with Gentoo since Debian has killed
the plug on ia64 in 2013.
I have no problem booting/using it locally (GNOME 3.24 desktop
environment) with kernels 4.9.76 and 4.12.12. Kernels were compiled
either with GCC 4.5.4 (because of a nasty error with GDB that
sometimes segfaults when kernels i compiled with GCC > 4.5) or 6.2.0.

2018-02-14 1:41 GMT+01:00 Pedro Miguel Teixeira <pm...@texair.net>:
>
>
> Hi Jason.
>
>
>
> That was close – I was really about to send the zx6000 onto the tech
> recycle.
>
>
>
> The following is all I get coming out from the console (Serial A, since the
> zx6000 does not have a management card / iLO). After the initrd line shows,
> a good 5 seconds pass. Then the front panel becomes all red and the cryptic
> modem-style sounds come out. I’ve wondered about the health of both my ELILO
> and Kernel, but my rx2660 boots fine with the exact the same two.
>
>
>
>
>
> EFI Boot Manager ver 1.10 [14.61]  Firmware ver 2.31 [4411]
>
>
>
> Loading device drivers
>
>
>
> Loading.: Auxiliary Floating Point Driver
>
> Load of Auxiliary Floating Point Driver failed: Not Found
>
> EFI Boot Manager ver 1.10 [14.61]  Firmware ver 2.31 [4411]
>
>
>
> Please select a boot option
>
>
>
> Windows Boot Manager
>
> Debian
>
> EFI Shell [Built-in]
>
> Removable Media
>
> Boot Option Maintenance Menu
>
> System Configuration Menu
>
>
>
>
>
> Use ^ and v to change option(s). Use Enter to select an option
>
> Loading.: Debian
>
> Starting: Debian
>
> ELILO v3.14 for EFI/IA-64
>
> ..
>
> Uncompressing Linux... done
>
> Loading file \EFI\debian\initrd.img...done
>
>
>
>
>
>
>
>
>
> _
> Pedro
>
>
>
> From: Jason Duerstock
> Sent: Friday, February 9, 2018 04:01
> To: Pedro Miguel Teixeira
> Cc: Gatis Visnevskis; Ivan Zakharyaschev; debian-ia64; gle...@altlinux.org
>
>
> Subject: Re: Bug#711135: Re: compiling a bootable kernel for ia64 (itanium2,
> mckinley, rx2620)
>
>
>
> Hi Pedro,
>
> Can you file a separate bug for this, and include a boot log?
>
> Thanks,
>
> Jason
>
>
> On Fri, Feb 9, 2018 at 6:24 AM, Pedro Miguel Teixeira <pm...@texair.net>
> wrote:
>>
>>
>> The latest kernel available from Debian does work fine on my Montvale
>> rx2660. However, I cannot boot my McKinley zx6000 with it. It will MCA
>> really early in the boot process.
>>
>>
>>
>> Linux b777 3.2.0-4-mckinley #1 SMP Debian 3.2.78-1 ia64 GNU/Linux
>>
>>
>>
>>
>>
>> _
>> Pedro
>>
>>
>>
>> From: Gatis Visnevskis
>> Sent: Friday, February 9, 2018 03:13
>> To: Ivan Zakharyaschev
>> Cc: Jason Duerstock; debian-ia64; gle...@altlinux.org
>> Subject: Re: Bug#711135: Re: compiling a bootable kernel for ia64
>> (itanium2,
>> mckinley, rx2620)
>>
>>
>>
>> Hi all
>>
>> I got working 3.2.0 kernel after some work. Without recompilation.
>> HP rx4640. That was 2 years ago. Server switched off for cost saving :(
>>
>> Started to install toolchain for compilation, but not finished.
>> Internal disks were too small, some 36 gb i think.
>>
>> It seems that i have to boot my server, and try again, as there is some
>> light in end of tunnel. I was hoping to get LXC working on ia64 some
>> day.
>>
>> Gasha
>>
>> On Fri, 9 Feb 2018 11:33:16 +0300 (MSK)
>> Ivan Zakharyaschev <i...@altlinux.org> wrote:
>>
>>> Hi,
>>>
>>> On Wed, 7 Feb 2018, Ivan Zakharyaschev wrote:
>>>
>>> > On Sun, 4 Feb 2018, Jason Duerstock wrote:
>>> >
>>> >>  Does the kernel fro

Re: Bug#711135: Re: compiling a bootable kernel for ia64 (itanium2, mckinley, rx2620)

[Émeric MASCHINO]

Well, problem is then likely with iLO card or serial console.
Indeed, I'm daily using a zx6000 workstation for years, being with
Debian for more than a decade, now with Gentoo since Debian has killed
the plug on ia64 in 2013.
I have no problem booting/using it locally (GNOME 3.24 desktop
environment) with kernels 4.9.76 and 4.12.12. Kernels were compiled
either with GCC 4.5.4 (because of a nasty error with GDB that
sometimes segfaults when kernels i compiled with GCC > 4.5) or 6.2.0.

2018-02-14 1:41 GMT+01:00 Pedro Miguel Teixeira <pm...@texair.net>:
>
>
> Hi Jason.
>
>
>
> That was close – I was really about to send the zx6000 onto the tech
> recycle.
>
>
>
> The following is all I get coming out from the console (Serial A, since the
> zx6000 does not have a management card / iLO). After the initrd line shows,
> a good 5 seconds pass. Then the front panel becomes all red and the cryptic
> modem-style sounds come out. I’ve wondered about the health of both my ELILO
> and Kernel, but my rx2660 boots fine with the exact the same two.
>
>
>
>
>
> EFI Boot Manager ver 1.10 [14.61]  Firmware ver 2.31 [4411]
>
>
>
> Loading device drivers
>
>
>
> Loading.: Auxiliary Floating Point Driver
>
> Load of Auxiliary Floating Point Driver failed: Not Found
>
> EFI Boot Manager ver 1.10 [14.61]  Firmware ver 2.31 [4411]
>
>
>
> Please select a boot option
>
>
>
> Windows Boot Manager
>
> Debian
>
> EFI Shell [Built-in]
>
> Removable Media
>
> Boot Option Maintenance Menu
>
> System Configuration Menu
>
>
>
>
>
> Use ^ and v to change option(s). Use Enter to select an option
>
> Loading.: Debian
>
> Starting: Debian
>
> ELILO v3.14 for EFI/IA-64
>
> ..
>
> Uncompressing Linux... done
>
> Loading file \EFI\debian\initrd.img...done
>
>
>
>
>
>
>
>
>
> _
> Pedro
>
>
>
> From: Jason Duerstock
> Sent: Friday, February 9, 2018 04:01
> To: Pedro Miguel Teixeira
> Cc: Gatis Visnevskis; Ivan Zakharyaschev; debian-ia64; gle...@altlinux.org
>
>
> Subject: Re: Bug#711135: Re: compiling a bootable kernel for ia64 (itanium2,
> mckinley, rx2620)
>
>
>
> Hi Pedro,
>
> Can you file a separate bug for this, and include a boot log?
>
> Thanks,
>
> Jason
>
>
> On Fri, Feb 9, 2018 at 6:24 AM, Pedro Miguel Teixeira <pm...@texair.net>
> wrote:
>>
>>
>> The latest kernel available from Debian does work fine on my Montvale
>> rx2660. However, I cannot boot my McKinley zx6000 with it. It will MCA
>> really early in the boot process.
>>
>>
>>
>> Linux b777 3.2.0-4-mckinley #1 SMP Debian 3.2.78-1 ia64 GNU/Linux
>>
>>
>>
>>
>>
>> _
>> Pedro
>>
>>
>>
>> From: Gatis Visnevskis
>> Sent: Friday, February 9, 2018 03:13
>> To: Ivan Zakharyaschev
>> Cc: Jason Duerstock; debian-ia64; gle...@altlinux.org
>> Subject: Re: Bug#711135: Re: compiling a bootable kernel for ia64
>> (itanium2,
>> mckinley, rx2620)
>>
>>
>>
>> Hi all
>>
>> I got working 3.2.0 kernel after some work. Without recompilation.
>> HP rx4640. That was 2 years ago. Server switched off for cost saving :(
>>
>> Started to install toolchain for compilation, but not finished.
>> Internal disks were too small, some 36 gb i think.
>>
>> It seems that i have to boot my server, and try again, as there is some
>> light in end of tunnel. I was hoping to get LXC working on ia64 some
>> day.
>>
>> Gasha
>>
>> On Fri, 9 Feb 2018 11:33:16 +0300 (MSK)
>> Ivan Zakharyaschev <i...@altlinux.org> wrote:
>>
>>> Hi,
>>>
>>> On Wed, 7 Feb 2018, Ivan Zakharyaschev wrote:
>>>
>>> > On Sun, 4 Feb 2018, Jason Duerstock wrote:
>>> >
>>> >>  Does the kernel from here work for you?:
>>> >>
>>> >>  https://people.debian.org/~jrtc27/wheezy-backports-ia64/
>>> >>
>>> >>  Specifically
>>> >>
>>> >>
>>> >> https://people.debian.org/~jrtc27/wheezy-backports-ia64/linux-image-3.16.0-0.bpo.4-mckinley_3.16.39-1+deb8u1~bpo70+1+gcc4.4_ia64.deb
>>> >
>>> > (As I've already said, this kernel works for our machine.)
>>> >
>>> > How to reproduce this build? Have you published the corresponding
>>> > rules?
>>> >
>>> > I tried:
>>> >
>>> > $ apt-get source linux-image-3.16.0-0.bpo.4-mckinley
>>> &

RE: Bug#711135: Re: compiling a bootable kernel for ia64 (itanium2, mckinley, rx2620)

[Pedro Miguel Teixeira]

Hi Jason.

That was close – I was really about to send the zx6000 onto the tech recycle.

The following is all I get coming out from the console (Serial A, since the 
zx6000 does not have a management card / iLO). After the initrd line shows, a 
good 5 seconds pass. Then the front panel becomes all red and the cryptic 
modem-style sounds come out. I’ve wondered about the health of both my ELILO 
and Kernel, but my rx2660 boots fine with the exact the same two.


EFI Boot Manager ver 1.10 [14.61]  Firmware ver 2.31 [4411]

Loading device drivers

Loading.: Auxiliary Floating Point Driver
Load of Auxiliary Floating Point Driver failed: Not Found
EFI Boot Manager ver 1.10 [14.61]  Firmware ver 2.31 [4411]

Please select a boot option

Windows Boot Manager
Debian
EFI Shell [Built-in]
Removable Media
Boot Option Maintenance Menu
System Configuration Menu


Use ^ and v to change option(s). Use Enter to select an option
Loading.: Debian
Starting: Debian
ELILO v3.14 for EFI/IA-64
..
Uncompressing Linux... done
Loading file \EFI\debian\initrd.img...done




_
Pedro

From: Jason Duerstock<mailto:jason.duerst...@gmail.com>
Sent: Friday, February 9, 2018 04:01
To: Pedro Miguel Teixeira<mailto:pm...@texair.net>
Cc: Gatis Visnevskis<mailto:ga...@pie-dabas.net>; Ivan 
Zakharyaschev<mailto:i...@altlinux.org>; 
debian-ia64<mailto:debian-ia64@lists.debian.org>; 
gle...@altlinux.org<mailto:gle...@altlinux.org>
Subject: Re: Bug#711135: Re: compiling a bootable kernel for ia64 (itanium2, 
mckinley, rx2620)

Hi Pedro,

Can you file a separate bug for this, and include a boot log?

Thanks,

Jason


On Fri, Feb 9, 2018 at 6:24 AM, Pedro Miguel Teixeira <pm...@texair.net> wrote:
>
>
> The latest kernel available from Debian does work fine on my Montvale
> rx2660. However, I cannot boot my McKinley zx6000 with it. It will MCA
> really early in the boot process.
>
>
>
> Linux b777 3.2.0-4-mckinley #1 SMP Debian 3.2.78-1 ia64 GNU/Linux
>
>
>
>
>
> _
> Pedro
>
>
>
> From: Gatis Visnevskis
> Sent: Friday, February 9, 2018 03:13
> To: Ivan Zakharyaschev
> Cc: Jason Duerstock; debian-ia64; gle...@altlinux.org
> Subject: Re: Bug#711135: Re: compiling a bootable kernel for ia64 (itanium2,
> mckinley, rx2620)
>
>
>
> Hi all
>
> I got working 3.2.0 kernel after some work. Without recompilation.
> HP rx4640. That was 2 years ago. Server switched off for cost saving :(
>
> Started to install toolchain for compilation, but not finished.
> Internal disks were too small, some 36 gb i think.
>
> It seems that i have to boot my server, and try again, as there is some
> light in end of tunnel. I was hoping to get LXC working on ia64 some
> day.
>
> Gasha
>
> On Fri, 9 Feb 2018 11:33:16 +0300 (MSK)
> Ivan Zakharyaschev <i...@altlinux.org> wrote:
>
>> Hi,
>>
>> On Wed, 7 Feb 2018, Ivan Zakharyaschev wrote:
>>
>> > On Sun, 4 Feb 2018, Jason Duerstock wrote:
>> >
>> >>  Does the kernel from here work for you?:
>> >>
>> >>  https://people.debian.org/~jrtc27/wheezy-backports-ia64/
>> >>
>> >>  Specifically
>> >>
>> >> https://people.debian.org/~jrtc27/wheezy-backports-ia64/linux-image-3.16.0-0.bpo.4-mckinley_3.16.39-1+deb8u1~bpo70+1+gcc4.4_ia64.deb
>> >
>> > (As I've already said, this kernel works for our machine.)
>> >
>> > How to reproduce this build? Have you published the corresponding
>> > rules?
>> >
>> > I tried:
>> >
>> > $ apt-get source linux-image-3.16.0-0.bpo.4-mckinley
>> > $ cd linux-3.16.39/
>> > $ sed -e 's/gcc-4.6/gcc-4.4/g' debian/config/ia64/defines -i
>> > $ debuild -b -us -uc
>> > $ debuild -j2 -b -us -uc
>> > ...
>> >   Kernel: vmlinux.gz is ready
>> > ERROR: "numa_slit" [drivers/block/nvme.ko] undefined!
>> > make[6]: *** [__modpost] Error 1
>>
>> BTW, has anyone been working on adapting the newest kernel package
>> for ia64? (buildd simply reports that there are no rules for ia64.)
>>
>> As for building 3.16 myself (reproducing Jason's build), I've found
>> an obvious fix for the above build problem at
>>
>> https://kernel.opensuse.org/cgit/kernel-source/commit/patches.arch/ia64-export-numa_slit.patch?h=packaging=bbf39ca510248f9f9cbfc3c65e8514df929a3094
>> :
>>
>> $ cd debian/patches/
>> $ mkdir bugfix/ia64
>> $ wget
>>
>> 'https://kernel.opensuse.org/cgit/kernel-source/plain/patches.arch/ia64-export-numa_slit.patch?h=packaging=bbf39ca510248f9f9cbfc3c65e8514df929a3094'
>> -O bugfix/ia64/ia64-export-numa_slit.patch
>> $ cat bu

Re: Bug#711135: Re: compiling a bootable kernel for ia64 (itanium2, mckinley, rx2620)

[Jason Duerstock]

Hi Pedro,

Can you file a separate bug for this, and include a boot log?

Thanks,

Jason


On Fri, Feb 9, 2018 at 6:24 AM, Pedro Miguel Teixeira <pm...@texair.net> wrote:
>
>
> The latest kernel available from Debian does work fine on my Montvale
> rx2660. However, I cannot boot my McKinley zx6000 with it. It will MCA
> really early in the boot process.
>
>
>
> Linux b777 3.2.0-4-mckinley #1 SMP Debian 3.2.78-1 ia64 GNU/Linux
>
>
>
>
>
> _
> Pedro
>
>
>
> From: Gatis Visnevskis
> Sent: Friday, February 9, 2018 03:13
> To: Ivan Zakharyaschev
> Cc: Jason Duerstock; debian-ia64; gle...@altlinux.org
> Subject: Re: Bug#711135: Re: compiling a bootable kernel for ia64 (itanium2,
> mckinley, rx2620)
>
>
>
> Hi all
>
> I got working 3.2.0 kernel after some work. Without recompilation.
> HP rx4640. That was 2 years ago. Server switched off for cost saving :(
>
> Started to install toolchain for compilation, but not finished.
> Internal disks were too small, some 36 gb i think.
>
> It seems that i have to boot my server, and try again, as there is some
> light in end of tunnel. I was hoping to get LXC working on ia64 some
> day.
>
> Gasha
>
> On Fri, 9 Feb 2018 11:33:16 +0300 (MSK)
> Ivan Zakharyaschev <i...@altlinux.org> wrote:
>
>> Hi,
>>
>> On Wed, 7 Feb 2018, Ivan Zakharyaschev wrote:
>>
>> > On Sun, 4 Feb 2018, Jason Duerstock wrote:
>> >
>> >>  Does the kernel from here work for you?:
>> >>
>> >>  https://people.debian.org/~jrtc27/wheezy-backports-ia64/
>> >>
>> >>  Specifically
>> >>
>> >> https://people.debian.org/~jrtc27/wheezy-backports-ia64/linux-image-3.16.0-0.bpo.4-mckinley_3.16.39-1+deb8u1~bpo70+1+gcc4.4_ia64.deb
>> >
>> > (As I've already said, this kernel works for our machine.)
>> >
>> > How to reproduce this build? Have you published the corresponding
>> > rules?
>> >
>> > I tried:
>> >
>> > $ apt-get source linux-image-3.16.0-0.bpo.4-mckinley
>> > $ cd linux-3.16.39/
>> > $ sed -e 's/gcc-4.6/gcc-4.4/g' debian/config/ia64/defines -i
>> > $ debuild -b -us -uc
>> > $ debuild -j2 -b -us -uc
>> > ...
>> >   Kernel: vmlinux.gz is ready
>> > ERROR: "numa_slit" [drivers/block/nvme.ko] undefined!
>> > make[6]: *** [__modpost] Error 1
>>
>> BTW, has anyone been working on adapting the newest kernel package
>> for ia64? (buildd simply reports that there are no rules for ia64.)
>>
>> As for building 3.16 myself (reproducing Jason's build), I've found
>> an obvious fix for the above build problem at
>>
>> https://kernel.opensuse.org/cgit/kernel-source/commit/patches.arch/ia64-export-numa_slit.patch?h=packaging=bbf39ca510248f9f9cbfc3c65e8514df929a3094
>> :
>>
>> $ cd debian/patches/
>> $ mkdir bugfix/ia64
>> $ wget
>>
>> 'https://kernel.opensuse.org/cgit/kernel-source/plain/patches.arch/ia64-export-numa_slit.patch?h=packaging=bbf39ca510248f9f9cbfc3c65e8514df929a3094'
>> -O bugfix/ia64/ia64-export-numa_slit.patch
>> $ cat bugfix/ia64/ia64-export-numa_slit.patch
>> From: Hannes Reinecke <h...@suse.de>
>> Date: Wed, 14 Jan 2015 15:01:30 +0100
>> Subject: [PATCH] ia64: export numa_slit()
>> Patch-Mainline: not yet
>> References: bnc#913030,FATE#317455
>>
>> nvme triggers a build error with 'numa_slit' being undefined.
>>
>> Signed-off-by: Hannes Reinecke <h...@suse.de>
>> ---
>>   arch/ia64/mm/numa.c | 1 +
>>   1 file changed, 1 insertion(+)
>>
>> diff --git a/arch/ia64/mm/numa.c b/arch/ia64/mm/numa.c
>> index 88f4eeb..23a914c 100644
>> --- a/arch/ia64/mm/numa.c
>> +++ b/arch/ia64/mm/numa.c
>> @@ -35,6 +35,7 @@ struct node_cpuid_s node_cpuid[NR_CPUS] =
>>* proportional to the memory access latency ratios.
>>*/
>>   u8 numa_slit[MAX_NUMNODES * MAX_NUMNODES];
>> +EXPORT_SYMBOL(numa_slit);
>>
>>   /* Identify which cnode a physical address resides on */
>>   int
>
>

RE: Bug#711135: Re: compiling a bootable kernel for ia64 (itanium2, mckinley, rx2620)

[Pedro Miguel Teixeira]

The latest kernel available from Debian does work fine on my Montvale rx2660. 
However, I cannot boot my McKinley zx6000 with it. It will MCA really early in 
the boot process.


  *   Linux b777 3.2.0-4-mckinley #1 SMP Debian 3.2.78-1 ia64 GNU/Linux


_
Pedro

From: Gatis Visnevskis<mailto:ga...@pie-dabas.net>
Sent: Friday, February 9, 2018 03:13
To: Ivan Zakharyaschev<mailto:i...@altlinux.org>
Cc: Jason Duerstock<mailto:jason.duerst...@gmail.com>; 
debian-ia64<mailto:debian-ia64@lists.debian.org>; 
gle...@altlinux.org<mailto:gle...@altlinux.org>
Subject: Re: Bug#711135: Re: compiling a bootable kernel for ia64 (itanium2, 
mckinley, rx2620)

Hi all

I got working 3.2.0 kernel after some work. Without recompilation.
HP rx4640. That was 2 years ago. Server switched off for cost saving :(

Started to install toolchain for compilation, but not finished.
Internal disks were too small, some 36 gb i think.

It seems that i have to boot my server, and try again, as there is some
light in end of tunnel. I was hoping to get LXC working on ia64 some
day.

Gasha

On Fri, 9 Feb 2018 11:33:16 +0300 (MSK)
Ivan Zakharyaschev <i...@altlinux.org> wrote:

> Hi,
>
> On Wed, 7 Feb 2018, Ivan Zakharyaschev wrote:
>
> > On Sun, 4 Feb 2018, Jason Duerstock wrote:
> >
> >>  Does the kernel from here work for you?:
> >>
> >>  https://people.debian.org/~jrtc27/wheezy-backports-ia64/
> >>
> >>  Specifically
> >>  
> >> https://people.debian.org/~jrtc27/wheezy-backports-ia64/linux-image-3.16.0-0.bpo.4-mckinley_3.16.39-1+deb8u1~bpo70+1+gcc4.4_ia64.deb
> >
> > (As I've already said, this kernel works for our machine.)
> >
> > How to reproduce this build? Have you published the corresponding
> > rules?
> >
> > I tried:
> >
> > $ apt-get source linux-image-3.16.0-0.bpo.4-mckinley
> > $ cd linux-3.16.39/
> > $ sed -e 's/gcc-4.6/gcc-4.4/g' debian/config/ia64/defines -i
> > $ debuild -b -us -uc
> > $ debuild -j2 -b -us -uc
> > ...
> >   Kernel: vmlinux.gz is ready
> > ERROR: "numa_slit" [drivers/block/nvme.ko] undefined!
> > make[6]: *** [__modpost] Error 1
>
> BTW, has anyone been working on adapting the newest kernel package
> for ia64? (buildd simply reports that there are no rules for ia64.)
>
> As for building 3.16 myself (reproducing Jason's build), I've found
> an obvious fix for the above build problem at
> https://kernel.opensuse.org/cgit/kernel-source/commit/patches.arch/ia64-export-numa_slit.patch?h=packaging=bbf39ca510248f9f9cbfc3c65e8514df929a3094
> :
>
> $ cd debian/patches/
> $ mkdir bugfix/ia64
> $ wget
> 'https://kernel.opensuse.org/cgit/kernel-source/plain/patches.arch/ia64-export-numa_slit.patch?h=packaging=bbf39ca510248f9f9cbfc3c65e8514df929a3094'
> -O bugfix/ia64/ia64-export-numa_slit.patch
> $ cat bugfix/ia64/ia64-export-numa_slit.patch
> From: Hannes Reinecke <h...@suse.de>
> Date: Wed, 14 Jan 2015 15:01:30 +0100
> Subject: [PATCH] ia64: export numa_slit()
> Patch-Mainline: not yet
> References: bnc#913030,FATE#317455
>
> nvme triggers a build error with 'numa_slit' being undefined.
>
> Signed-off-by: Hannes Reinecke <h...@suse.de>
> ---
>   arch/ia64/mm/numa.c | 1 +
>   1 file changed, 1 insertion(+)
>
> diff --git a/arch/ia64/mm/numa.c b/arch/ia64/mm/numa.c
> index 88f4eeb..23a914c 100644
> --- a/arch/ia64/mm/numa.c
> +++ b/arch/ia64/mm/numa.c
> @@ -35,6 +35,7 @@ struct node_cpuid_s node_cpuid[NR_CPUS] =
>* proportional to the memory access latency ratios.
>*/
>   u8 numa_slit[MAX_NUMNODES * MAX_NUMNODES];
> +EXPORT_SYMBOL(numa_slit);
>
>   /* Identify which cnode a physical address resides on */
>   int

Re: Bug#711135: Re: compiling a bootable kernel for ia64 (itanium2, mckinley, rx2620)

[Gatis Visnevskis]

Hi all

I got working 3.2.0 kernel after some work. Without recompilation.
HP rx4640. That was 2 years ago. Server switched off for cost saving :(

Started to install toolchain for compilation, but not finished.
Internal disks were too small, some 36 gb i think.

It seems that i have to boot my server, and try again, as there is some
light in end of tunnel. I was hoping to get LXC working on ia64 some
day.

Gasha

On Fri, 9 Feb 2018 11:33:16 +0300 (MSK)
Ivan Zakharyaschev  wrote:

> Hi,
> 
> On Wed, 7 Feb 2018, Ivan Zakharyaschev wrote:
> 
> > On Sun, 4 Feb 2018, Jason Duerstock wrote:
> >
> >>  Does the kernel from here work for you?:
> >>
> >>  https://people.debian.org/~jrtc27/wheezy-backports-ia64/
> >>
> >>  Specifically
> >>  
> >> https://people.debian.org/~jrtc27/wheezy-backports-ia64/linux-image-3.16.0-0.bpo.4-mckinley_3.16.39-1+deb8u1~bpo70+1+gcc4.4_ia64.deb
> >
> > (As I've already said, this kernel works for our machine.)
> >
> > How to reproduce this build? Have you published the corresponding
> > rules?
> >
> > I tried:
> >
> > $ apt-get source linux-image-3.16.0-0.bpo.4-mckinley
> > $ cd linux-3.16.39/
> > $ sed -e 's/gcc-4.6/gcc-4.4/g' debian/config/ia64/defines -i
> > $ debuild -b -us -uc
> > $ debuild -j2 -b -us -uc
> > ...
> >   Kernel: vmlinux.gz is ready
> > ERROR: "numa_slit" [drivers/block/nvme.ko] undefined!
> > make[6]: *** [__modpost] Error 1
> 
> BTW, has anyone been working on adapting the newest kernel package
> for ia64? (buildd simply reports that there are no rules for ia64.)
> 
> As for building 3.16 myself (reproducing Jason's build), I've found
> an obvious fix for the above build problem at 
> https://kernel.opensuse.org/cgit/kernel-source/commit/patches.arch/ia64-export-numa_slit.patch?h=packaging=bbf39ca510248f9f9cbfc3c65e8514df929a3094
>  
> :
> 
> $ cd debian/patches/
> $ mkdir bugfix/ia64
> $ wget 
> 'https://kernel.opensuse.org/cgit/kernel-source/plain/patches.arch/ia64-export-numa_slit.patch?h=packaging=bbf39ca510248f9f9cbfc3c65e8514df929a3094'
>  
> -O bugfix/ia64/ia64-export-numa_slit.patch
> $ cat bugfix/ia64/ia64-export-numa_slit.patch
> From: Hannes Reinecke 
> Date: Wed, 14 Jan 2015 15:01:30 +0100
> Subject: [PATCH] ia64: export numa_slit()
> Patch-Mainline: not yet
> References: bnc#913030,FATE#317455
> 
> nvme triggers a build error with 'numa_slit' being undefined.
> 
> Signed-off-by: Hannes Reinecke 
> ---
>   arch/ia64/mm/numa.c | 1 +
>   1 file changed, 1 insertion(+)
> 
> diff --git a/arch/ia64/mm/numa.c b/arch/ia64/mm/numa.c
> index 88f4eeb..23a914c 100644
> --- a/arch/ia64/mm/numa.c
> +++ b/arch/ia64/mm/numa.c
> @@ -35,6 +35,7 @@ struct node_cpuid_s node_cpuid[NR_CPUS] =
>* proportional to the memory access latency ratios.
>*/
>   u8 numa_slit[MAX_NUMNODES * MAX_NUMNODES];
> +EXPORT_SYMBOL(numa_slit);
> 
>   /* Identify which cnode a physical address resides on */
>   int

Re: Bug#711135: Re: compiling a bootable kernel for ia64 (itanium2, mckinley, rx2620)

[Ivan Zakharyaschev]

Hi,

On Wed, 7 Feb 2018, Ivan Zakharyaschev wrote:


On Sun, 4 Feb 2018, Jason Duerstock wrote:


 Does the kernel from here work for you?:

 https://people.debian.org/~jrtc27/wheezy-backports-ia64/

 Specifically
 
https://people.debian.org/~jrtc27/wheezy-backports-ia64/linux-image-3.16.0-0.bpo.4-mckinley_3.16.39-1+deb8u1~bpo70+1+gcc4.4_ia64.deb


(As I've already said, this kernel works for our machine.)

How to reproduce this build? Have you published the corresponding rules?

I tried:

$ apt-get source linux-image-3.16.0-0.bpo.4-mckinley
$ cd linux-3.16.39/
$ sed -e 's/gcc-4.6/gcc-4.4/g' debian/config/ia64/defines -i
$ debuild -b -us -uc
$ debuild -j2 -b -us -uc
...
  Kernel: vmlinux.gz is ready
ERROR: "numa_slit" [drivers/block/nvme.ko] undefined!
make[6]: *** [__modpost] Error 1


BTW, has anyone been working on adapting the newest kernel package for 
ia64? (buildd simply reports that there are no rules for ia64.)


As for building 3.16 myself (reproducing Jason's build), I've found an 
obvious fix for the above build problem at 
https://kernel.opensuse.org/cgit/kernel-source/commit/patches.arch/ia64-export-numa_slit.patch?h=packaging=bbf39ca510248f9f9cbfc3c65e8514df929a3094 
:


$ cd debian/patches/
$ mkdir bugfix/ia64
$ wget 
'https://kernel.opensuse.org/cgit/kernel-source/plain/patches.arch/ia64-export-numa_slit.patch?h=packaging=bbf39ca510248f9f9cbfc3c65e8514df929a3094' 
-O bugfix/ia64/ia64-export-numa_slit.patch

$ cat bugfix/ia64/ia64-export-numa_slit.patch
From: Hannes Reinecke 
Date: Wed, 14 Jan 2015 15:01:30 +0100
Subject: [PATCH] ia64: export numa_slit()
Patch-Mainline: not yet
References: bnc#913030,FATE#317455

nvme triggers a build error with 'numa_slit' being undefined.

Signed-off-by: Hannes Reinecke 
---
 arch/ia64/mm/numa.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/arch/ia64/mm/numa.c b/arch/ia64/mm/numa.c
index 88f4eeb..23a914c 100644
--- a/arch/ia64/mm/numa.c
+++ b/arch/ia64/mm/numa.c
@@ -35,6 +35,7 @@ struct node_cpuid_s node_cpuid[NR_CPUS] =
  * proportional to the memory access latency ratios.
  */
 u8 numa_slit[MAX_NUMNODES * MAX_NUMNODES];
+EXPORT_SYMBOL(numa_slit);

 /* Identify which cnode a physical address resides on */
 int
--
1.8.5.2

Unfortunately, the references lead to secret notes ("bnc" refers to 
bugzilla.novell.com), so I couldn't see whether this is believed to be a 
reasonable fix leading to an actually working code.


And I'm doing:

$ cd ../..
$ echo bugfix/ia64/ia64-export-numa_slit.patch >>series
$ sed -e 's/gcc-4.6/gcc-4.4/g' debian/config/ia64/defines -i
# If one wnats to use gcc-4.5 from the archive snapshots, one should add it to 
debian/config/defines, too
$ debuild -b -uc -us
# stops because the package got updated
$ debuild -j2 -b -uc -us

We'll see whether it compiles successfully.

--
Best regards,
Ivan

Re: Bug#711135: Re: compiling a bootable kernel for ia64 (itanium2, mckinley, rx2620)

[Ivan Zakharyaschev]

Hi Jason,

On Sun, 4 Feb 2018, Jason Duerstock wrote:


Does the kernel from here work for you?:

https://people.debian.org/~jrtc27/wheezy-backports-ia64/

Specifically 
https://people.debian.org/~jrtc27/wheezy-backports-ia64/linux-image-3.16.0-0.bpo.4-mckinley_3.16.39-1+deb8u1~bpo70+1+gcc4.4_ia64.deb


(As I've already said, this kernel works for our machine.)

How to reproduce this build? Have you published the corresponding rules?

I tried:

$ apt-get source linux-image-3.16.0-0.bpo.4-mckinley
Reading package lists... Done
Building dependency tree
Reading state information... Done
Picking 'linux' as source package instead of 
'linux-image-3.16.0-0.bpo.4-mckinley'
NOTICE: 'linux' packaging is maintained in the 'Git' version control 
system at:

https://anonscm.debian.org/git/kernel/linux.git
Need to get 84.2 MB of source archives.
Get:1 http://ftp.ru.debian.org/debian/ wheezy-backports/main linux 
3.16.39-1+deb8u1~bpo70+1 (dsc) [97.4 kB]
Get:2 http://ftp.ru.debian.org/debian/ wheezy-backports/main linux 
3.16.39-1+deb8u1~bpo70+1 (tar) [81.8 MB]
Get:3 http://ftp.ru.debian.org/debian/ wheezy-backports/main linux 
3.16.39-1+deb8u1~bpo70+1 (diff) [2,316 kB]

Fetched 84.2 MB in 9s (9,087 kB/s)
dpkg-source: info: extracting linux in linux-3.16.39
dpkg-source: info: unpacking linux_3.16.39.orig.tar.xz
dpkg-source: info: unpacking linux_3.16.39-1+deb8u1~bpo70+1.debian.tar.xz
dpkg-source: info: applying debian/version.patch
...
$ cd linux-3.16.39/
$ sed -e 's/gcc-4.6/gcc-4.4/g' debian/config/ia64/defines -i
$ debuild -b -us -uc
$ debuild -j2 -b -us -uc
...
  LINKvmlinux
  LD  vmlinux.o
  MODPOST vmlinux.o
  GEN .version
  CHK include/generated/compile.h
  UPD include/generated/compile.h
  CC  init/version.o
  LD  init/built-in.o
  KSYM.tmp_kallsyms1.o
  KSYM.tmp_kallsyms2.o
  LD  vmlinux
  SYSMAP  System.map
  Building modules, stage 2.
  OBJCOPY arch/ia64/hp/sim/boot/vmlinux.bin
  GZIParch/ia64/hp/sim/boot/vmlinux.gz
  MODPOST 2506 modules
  LN  vmlinux.gz
  Kernel: vmlinux.gz is ready
ERROR: "numa_slit" [drivers/block/nvme.ko] undefined!
make[6]: *** [__modpost] Error 1
make[5]: *** [modules] Error 2
make[4]: *** [sub-make] Error 2
make[3]: *** [__sub-make] Error 2
make[3]: Leaving directory 
`/home/imz/with-gcc-4.4.7_wheezy/linux-3.16.39/debian/build/build_ia64_none_itanium'

make[2]: *** [debian/stamps/build_ia64_none_itanium_plain] Error 2
make[2]: Leaving directory `/home/imz/with-gcc-4.4.7_wheezy/linux-3.16.39'
make[1]: *** [build-arch_ia64_none_itanium_real] Error 2
make[1]: Leaving directory `/home/imz/with-gcc-4.4.7_wheezy/linux-3.16.39'
make: *** [build-arch] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
debuild: fatal error at line 1357:
dpkg-buildpackage -rfakeroot -D -us -uc -j2 -b failed

$

(Parallellization, i.e., -j2, doesn't affect the result; I have checked 
that.)



On Sun, Feb 4, 2018 at 7:56 PM, Ivan Zakharyaschev  wrote:



Yes, [this one] doesn't boot on our system. It might even be in our case a
strange/buggy behavior caused by old firmware for an otherwise correct
kernel binary code (or, of course, the code might be not correct). Perhaps,
there is a difference between yours and ours machines:

root@rx2620:~# cat /proc/cpuinfo
processor  : 0
vendor : GenuineIntel
arch   : IA-64
family : 31
model  : 2
model name : Madison up to 9M cache
revision   : 1
archrev: 0
features   : branchlong
cpu number : 0
cpu regs   : 4
cpu MHz: 1600.021
itc MHz: 1600.021752
BogoMIPS   : 2390.01
siblings   : 1
physical id: 0

processor  : 1
vendor : GenuineIntel
arch   : IA-64
family : 31
model  : 2
model name : Madison up to 9M cache
revision   : 1
archrev: 0
features   : branchlong
cpu number : 0
cpu regs   : 4
cpu MHz: 1600.021
itc MHz: 1600.021752
BogoMIPS   : 2390.01
siblings   : 1
physical id: 1

root@rx2620:~#

It looks like ours has 2 Madison CPUs (if we are to trust this cpuinfo),
which are older than your Montecito ones.




 [this one]:
 https://packages.debian.org/wheezy/linux-image-3.2.0-4-mckinley



So far, we've done a number of attempts to compile and boot a kernel (I'm
going to post the details and the kernels soon), and my conclusion so far is
that the only affecting factor is the version of gcc (even not -O1 vs
-Os/-O2).

gcc <= 4.5.3 produces a bootable kernel (as for
linux-image-3.2.0-4-mckinley, gcc 4.4.7 from wheezy and gcc 4.5.3 from
snapshots produced a bootable one in my experiments);
gcc > = 4.6.3 produces a non-bootable kernel.

So this already gives an initial hypothesis about the solution to 1):

To compile a bootable kernel for this machine, use gcc <= 4.5.3.