Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

New sparc64 installation images - 2016-02-24

0 views
Skip to first unread message

John Paul Adrian Glaubitz

unread,
Feb 24, 2016, 2:40:02 PM2/24/16
to
Hi!

I just created fresh sparc64 installation images [1].

Summary of changes:

* kernel has been updated to 4.4.2
* lvm segfaults should be fixed now
* debian-installer and all of its components have been updated
to the current git revision as of 2016-02-24
* all packages shipped on the ISO have been updated to the
current versions in unstable

Note: These images are completely untested. If you need the old images,
look at the images generated on 2016-02-12 [2].

Enjoy,

Adrian

> [1] https://people.debian.org/~glaubitz/debian-cd/2016-02-24/
> [2] https://people.debian.org/~glaubitz/debian-cd/2016-02-12/

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

John Paul Adrian Glaubitz

unread,
Feb 25, 2016, 3:40:03 AM2/25/16
to
On 02/24/2016 08:37 PM, John Paul Adrian Glaubitz wrote:
> I just created fresh sparc64 installation images [1].

There have been issues reported with missing sunvdc/sunvnet modules.

However, I need more detailed feedback in order to investigate into
this. Thus, it would be great that anyone who has actually tested
the images could provide some detailed feedback on this thread.

The more information I have, the easier it becomes to address
these issues.

Thanks,
Adrian

waz0wski

unread,
Feb 25, 2016, 11:30:03 AM2/25/16
to
> There have been issues reported with missing sunvdc/sunvnet modules.

I tested in an LDOM via Solaris 11.3 on a T5220 and had this issue.

The sunvdc/sunvnet modules are not probed/loaded from the installer, nor in the installed system.
workaround: load modules from installer shell, post-install chroot into the installed system, add modules to /etc/initramfs-tools/modules and run update-initramfs -uv
The Debian wiki mentions adding custom modules to the installer is possible[1], and it seems that the modules used to be there[2]


No other issues with the installer, auto-partitioning (EXT4), etc were encountered
Post-install, I see few other issues

- no login presented on ldom console -- I see init messages[3], but no login prompt. workaround: install openssh-server from chroot before reboot
- device initialization / fdisk logic issue[4] (line 13)
- n2_crypto failures[5] (possibly due to my LDOM config, debugging)
- /etc/resolv.conf being populated only with IPv6 nameservers despite having DHCP+DHCPv6 available (possibly due to my network/vnet config, debugging)


let me know if any additional info is needed.


[1] https://wiki.debian.org/DebianInstaller/Modify/CustomKernel
[2] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=504702
[3] http://paste.debian.net/403612
[4] http://paste.debian.net/403282
[5] http://paste.debian.net/403616

Bryce

unread,
Feb 25, 2016, 12:20:03 PM2/25/16
to
Oh, I remember hitting this. I wrote this to get around it.
[root@ca-qasparc10 rules.d]# pwd
/lib/udev/rules.d
[root@ca-qasparc10 rules.d]# cat 10-sunv.rules
# Theory
# Linux under solaris's ldm exposes a pile of /devices/channel-devices/v*
# devices. The drivers should not be reloaded as that would likely
# crash the system.
# If the vio subsystem exists, we check for an environment var (sunv_ran)
# if it doesn't exist or does not have the value '1' then we look for
# a glob match for each driver,.. should we find one we set sunv_ran to
# '1' permently using ':=' and load the associated module
#

SUBSYSTEM!="vio", ENV{sunv_ran}!="1", GOTO="vio_end"
DEVPATH=="/devices/channel-devices/vnet-*", ENV{sunv_ran}:="1", RUN+="/sbin/modprobe -b sunvnet"
DEVPATH=="/devices/channel-devices/vdc-*", ENV{sunv_ran}:="1", RUN+="/sbin/modprobe -b sunvdc"
LABEL="vio_end"

Anatoly Pugachev

unread,
Feb 25, 2016, 4:00:03 PM2/25/16
to
On Thu, Feb 25, 2016 at 8:18 PM, Bryce <philip....@oracle.com> wrote:
> Oh, I remember hitting this. I wrote this to get around it.
>
> [root@ca-qasparc10 rules.d]# pwd
> /lib/udev/rules.d
> [root@ca-qasparc10 rules.d]# cat 10-sunv.rules
> # Theory
> # Linux under solaris's ldm exposes a pile of /devices/channel-devices/v*
> # devices. The drivers should not be reloaded as that would likely
> # crash the system.
> # If the vio subsystem exists, we check for an environment var (sunv_ran)
> # if it doesn't exist or does not have the value '1' then we look for
> # a glob match for each driver,.. should we find one we set sunv_ran to
> # '1' permently using ':=' and load the associated module
> #
>
> SUBSYSTEM!="vio", ENV{sunv_ran}!="1", GOTO="vio_end"
> DEVPATH=="/devices/channel-devices/vnet-*", ENV{sunv_ran}:="1",
> RUN+="/sbin/modprobe -b sunvnet"
> DEVPATH=="/devices/channel-devices/vdc-*", ENV{sunv_ran}:="1",
> RUN+="/sbin/modprobe -b sunvdc"
> LABEL="vio_end"

I believe we need to write a patch for virt-what as well, having sysfs
information from /devices/channel-devices/v*
I just don't know how to implement it better, a simple bash check for
directory " -d /devices/channel-devices/v* " or something
particular...
Any thoughts are welcome.

Thanks.

John Paul Adrian Glaubitz

unread,
Feb 26, 2016, 4:50:03 AM2/26/16
to
On 02/25/2016 05:11 PM, waz0wski wrote:
> The sunvdc/sunvnet modules are not probed/loaded from the installer, nor in the installed system.

I have just reported this as a bug against the kernel package [1].

> The Debian wiki mentions adding custom modules to the installer is possible[1],

Yeah, but we can't use custom kernels for installer images, so this is
not an option. It needs to be fixed properly. Anything else is just
a crude hack.

> and it seems that the modules used to be there[2]

No, that's the kernel package for "sparc", we're on "sparc64".

> No other issues with the installer, auto-partitioning (EXT4), etc were encountered

Great to hear.

> - no login presented on ldom console -- I see init messages[3], but no login prompt. workaround: install openssh-server from chroot before reboot

That's odd. This might be an issue specific to the LDOM installations.
Since I don't have such hardware at hand, Anatoly needs to comment
on this.

> - device initialization / fdisk logic issue[4] (line 13)

That pastebin has already expired. So I cannot comment on this.

> - n2_crypto failures[5] (possibly due to my LDOM config, debugging)

Again, this is something Anatoly needs to comment on. No idea.

> - /etc/resolv.conf being populated only with IPv6 nameservers

Odd. I haven't observed that. Anyone else seen this issue?

Cheers,
Adrian

> [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815977

Anatoly Pugachev

unread,
Feb 26, 2016, 8:40:03 AM2/26/16
to
On Thu, Feb 25, 2016 at 7:11 PM, waz0wski <li...@mass-distortion.net> wrote:
>> There have been issues reported with missing sunvdc/sunvnet modules.
>
> I tested in an LDOM via Solaris 11.3 on a T5220 and had this issue.
>
> The sunvdc/sunvnet modules are not probed/loaded from the installer, nor in the installed system.
> workaround: load modules from installer shell, post-install chroot into the installed system, add modules to /etc/initramfs-tools/modules and run update-initramfs -uv
> The Debian wiki mentions adding custom modules to the installer is possible[1], and it seems that the modules used to be there[2]
>
>
> No other issues with the installer, auto-partitioning (EXT4), etc were encountered
> Post-install, I see few other issues
>
> - no login presented on ldom console -- I see init messages[3], but no login prompt. workaround: install openssh-server from chroot before reboot

enable and start console-getty.service via systemctl

> - device initialization / fdisk logic issue[4] (line 13)
> - n2_crypto failures[5] (possibly due to my LDOM config, debugging)

the only part I touched kernel is n2rng module, and looking at [5] it
is successfully works. I've no idea about n2cp, but we could probably
try to debug...

John Paul Adrian Glaubitz

unread,
Mar 4, 2016, 4:50:03 PM3/4/16
to
On 02/26/2016 01:11 AM, waz0wski wrote:
> - no login presented on ldom console -- I see init messages[3], but no login prompt. workaround: install openssh-server from chroot before reboot

After another user on the list saw the same issue, I now realize your
problem. You need to pass "console=ttyS0,115200,8n1" on the kernel
command line to actually activate login on the serial console.

This affects all versions of Debian, not just sparc64. Maybe we could
change the defaults here.

Anatoly Pugachev

unread,
Mar 5, 2016, 4:10:02 AM3/5/16
to
On Sat, Mar 5, 2016 at 12:44 AM, John Paul Adrian Glaubitz
<glau...@physik.fu-berlin.de> wrote:
> On 02/26/2016 01:11 AM, waz0wski wrote:
>> - no login presented on ldom console -- I see init messages[3], but no login prompt. workaround: install openssh-server from chroot before reboot
>
> After another user on the list saw the same issue, I now realize your
> problem. You need to pass "console=ttyS0,115200,8n1" on the kernel
> command line to actually activate login on the serial console.
>
> This affects all versions of Debian, not just sparc64. Maybe we could
> change the defaults here.

I'm not sure about making it as a system defaults for all the arches,
but we could make it as default on sparc64 somewhere in postinstall
scripts in debian-installer.
0 new messages