ize mean? Is there still obsolete work in the queue as well
or does every item have the same value? (There's no way right now it can
catch up with that many items in the queue. Although that again depends
on the unit...)
Kind regards
Philipp Kern
[1]
https://c
you have an idea how many packages the s390x manages to process
per day and how that compares to the other workers? PubSub queues are
not the easiest to introspect and I'd like to know how far we are off in
intake into the queue per day vs. what we can process.
Kind regards and thanks
Philipp Kern
bbitmq.debci.debian.net:12345"
failed: Connection refused
Kind regards
Philipp Kern
, I'm backholed) - so I would not be surprised if there
is some weirdness there.
Kind regards
Philipp Kern
think
that there is much value in the CD images in the first place. There's a
theoretical possibility to use them but I'm not even sure if they would
work properly at this point - it's definitely untested.
Kind regards
Philipp Kern
4.19.194-3 (2021-07-18) s390x
GNU/Linux
Linux zani 5.10.0-8-s390x #1 SMP Debian 5.10.46-4 (2021-08-03) s390x GNU/Linux
Linux zelenka 4.19.0-17-s390x #1 SMP Debian 4.19.194-3 (2021-07-18) s390x
GNU/Linux
(zani is the only machine of the three on Debian 11)
Kind regards
Philipp Kern
that in the kernel and got told
off. Maybe the answer is to bring this to linux-390 but I don't actually
know.
I think technically what we want is "just" for /proc/consoles to do the
right thing or have a way to map console name to tty name.
Kind regards
Philipp Kern
[1] https://
interested.
Given that ~no-one works on Debian s390x, people will need to step up
and fix things in Debian.
Kind regards and thanks
Philipp Kern
is still true.
Kind regards
Philipp Kern
Package: wnpp
Severity: normal
I intend to orphan the hercules package. It's an s390(x) emulator and
the package itself is in fairly good shape overall. It's mostly that I
have no use for it for several years now. (And mostly I do not want to
feel responsible for it anymore.)
Upstream has been tr
makes it worse.
You don't need to be a DD or DM to step up, although it helps. Aurelien
mentioned that he'd happily sponsor fixes if necessary.
Kind regards and thanks for listening
Philipp Kern
signature.asc
Description: OpenPGP digital signature
a way to get normal z/VM access to a
LinuxONE VM to reinstall the OS and a way to make them permanent, that'd
likely be fine, too.
Kind regards
Philipp Kern
signature.asc
Description: OpenPGP digital signature
es the IBMISV instance where DSA
and myself have a few instances. If we knew the actual requirements it
shouldn't be hard to get some more. Disk has traditionally been annoying
(because it's delivered in the form of small MDISKs in z/VM rather than
large blobs of block storage).
On 14.06.20 17:20, Philipp Kern wrote:
> On 11.05.20 11:53, Winfried Münch wrote:
>> package: s390-tools
>>
>> Version: current Installer from 04.05.2020 21:14
>> http://ftp.halifax.rwth-aachen.de/debian/dists/buster/main/installer-s390x/current/images/generic/
>>
s
> Description: Set of fundamental utilities for Linux on S/390
> The package contains:
My assumption is that this is not fixable through -updates but requires
a point release to be properly fixed.
Kind regards and thanks
Philipp Kern
diff -Nru s390-tools-2.3.0/debian/changelog s390-
ackages to install. It
tries to fetch "perl:any" instead of "perl". See [1].
At the same time bug #960265 is actually of priority serious (breaks
bootstrapping), rather than normal.
Kind regards
Philipp Kern
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960265#20
sign
self
given how hard it is to integrate with existing Debian infrastructure to
test it properly - unless you are an admin there already. Even a qemu
setup would have spotted this particular bug. But without any users who
care I also don't think it is worth spending much time on this.
Kind regards and sorry
Philipp Kern
considering the rotation/expiry of subkeys
and buildd keys. In this case the files already come from a trusted
source and should be ingested as-is, I guess? (Not that I particularly
like the fact that it's only a point in time validation.)
Kind regards
Philipp Kern
7;
I'd say you don't have internet connectivity from within the emulated
machine. At least DNS seems to be not working, hence wget complaining
about the hostnames.
Kind regards
Philipp Kern
pEpkey.asc
Description: application/pgp-keys
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sun, 04 Feb 2018 13:29:22 -0500
Source: s390-tools
Binary: s390-tools s390-tools-udeb ziomon
Architecture: source s390x
Version: 2.3.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian S/390 Team
Changed-By: Philipp Kern
with older machines. I'll try to restart
the discussion again.
What's the venue to have this discussion in? :)
Kind regards and thanks
Philipp Kern
we're mostly at the point where there isn't an
advantage to keeping the baseline low except a lot of churn on our side
in which no-one else is interested in. People on older platforms could
still use stable for a while.
Does anyone happen to know what the story with Hercules is[1]? I don
here some other place I should take a look at?
> Or will posting /var/syslog be enough?
/var/log/installer is present in the installed system (i.e. it is
preserved after the installation). If taken from the installer, a tar of
/var/log should be sufficient.
Kind regards and thanks
Philipp Kern
gt; kernel issue.
>
> I got a more complete log on this.
Please file a bug against debian-installer (reportbug has a template)
and attach the installer's syslog (or optimally all of /var/log/installer).
Kind regards and thanks
Philipp Kern
signature.asc
Description: OpenPGP digital signature
t needs to be a separate arch-all package).
Note that the arch:all autobuilders are amd64. gcc-*-s390x-linux-gnu
exists in Debian, although only on i386 and amd64. I don't think there's
a policy today that precludes you from forcing users to build arch:all
on amd64 for technical reaso
erstand it correctly, this is now obsoleted by the fact that
qemu dropped s390-virtio and runs with their own s390-ccw rom now that's
built from the qemu source. Is that correct? Can we close the s390-tools
bug at least? And I suppose arrange for s390-ccw.rom to be shipped from
the qemu package?
Kind regards and thanks
Philipp Kern
signature.asc
Description: OpenPGP digital signature
On 08/19/2017 09:34 PM, Philipp Kern wrote:
>> So it's not kernel issue or anything else. It must be something wrong
>> with installer itself. Should I report a problem somewhere? or we are
>> only ones who can't do fresh install on hercules?
>
> I'm
must be something wrong
> with installer itself. Should I report a problem somewhere? or we are
> only ones who can't do fresh install on hercules?
I'm happy to retest if you can give me the hercules.cnf you used.
Kind regards
Philipp Kern
kfully, the majority of Debian's
> s390x machines (buildd and porterbox), 3 out of 4, support the newer
> instructions. :-)
What's the current ISA requirement for golang? zEC12? z13?
I suppose popcon (as misleading as it is) likely doesn't have h/w stats?
(And I know that the current count of actual submissions is... 12.)
Kind regards and thanks
Philipp Kern
ure where you look for it and you included no details
whatsoever. Jessie aka oldstable is still on the mirrors for s390x (s390
has been unsupported for a long time now).
Kind regards
Philipp kern
signature.asc
Description: OpenPGP digital signature
. We can also negotiate uploads to
experimental for s390-tools if needed.
Now if something like Viktor's suggestion would've worked, I think we
could've fixed stretch using that as well. But then it's true that
chzdev should be the way forward. And there's too little man po
an't really judge whether this could be annoying in d-i,
> it seems to me that's just fixing a move which hadn't happened with the
> net.ifnames transition, for specific hardware?
FWIW, I have tested this on an installation and haven't seen any problems.
Kind regards
Philipp Kern
signature.asc
Description: OpenPGP digital signature
er you need. On the other
hand the major reason there was such an investment on Go on s390x is
that you can run docker and modern tools.
So personally I'd go and bite the bullet and document that Go is
available but won't work on anything less than a z196/z114 (released in
2010). :(
Kind regards
Philipp Kern
t; on other arch but I don't even know where to get them neither.
https://anonscm.debian.org/cgit/d-i/debian-installer.git/tree/ has the
code. I suppose for ISOs you need
https://anonscm.debian.org/cgit/debian-cd/debian-cd.git/tree/
Kind regards
Philipp Kern
signature.asc
Description: OpenPGP digital signature
arting with CHPID 2a.
> From my point of view, it should be:
> 11: 0.0.00c0-0.0.00c1-0.0.00c2
>
> Ignoring the unusable addresses 0.0.00be and 0.0.00bf.
What's the output of "ls -l /sys/bus/ccw/devices/0.0.00c0/driver"?
Kind regards and thanks
Philipp Kern
signature.asc
Description: OpenPGP digital signature
Package: zipl-installer
Version: 0.0.33
Severity: serious
zipl-installer 0.0.33 breaks installation for normal non-btrfs root
filesystems.
(initramfs) cat /proc/cmdline
root=/dev/mapper/vg-root rootflags=subvol= BOOT_IMAGE=0
The empty subvol= makes mount barf as it's not a valid ext4 flag.
ifferent piece of
software that seems to be unmaintained. For us it's much easier to just
ship the IBM-provided and -maintained cmsfs-fuse that's part of
s390-tools. I'd expect that all your use cases can also be mapped to
that and I'd expect other distributions to carry that a
e hw support.
Debian already makes use of Marist's resources. The challenge was/is to
get redundancy as DSA very sensibly insists on.
Kind regards
Philipp Kern
On Mon, Jun 13, 2016 at 07:33:56PM +, Niels Thykier wrote:
> Philipp Kern:
> > On 2016-06-05 12:01, Niels Thykier wrote:
> >> * amd64, i386, armel, armhf, arm64, mips, mipsel, powerpc, ppc64el,
> >>s390x
> >>- *No* blockers at this time from
and thanks
Philipp Kern
on improving debian-installer. That's just
immensely appreciated.
Kind regards and thanks
Philipp Kern
[*] The only thing that does not go down well is a single untested on
Debian patch that increases the maintenance burden.
acceptable.
I'll need to look at the diff, but it'd be helpful to have a
confirmation that this is all that's needed. (E.g. by rebuilding
jessie's d-i with just this one udeb built for jessie.)
Kind regards and thanks
Philipp Kern
0 machine on *Debian*?
I'm a bit surprised about the explicit addition of the hardening flags,
given that none of the binaries is suid nor a network daemon. So we
could just follow the distro-default here. But I'm not too bothered by
it.
Kind regards and thanks
Philipp Kern
Maintainer field?
In general this is fine with me as long as you add yourself as an
uploader. Where are updates to this package published?
Kind regards
Philipp Kern
Control: tag -1 + pending
On Mon, Dec 21, 2015 at 02:26:51PM +0100, Viktor Mihajlovski wrote:
> On Fri, 18 Dec 2015 23:59:21 +0100 Philipp Kern wrote:
> ...
> >
> > Is there a way I could test FCP installation? As far as I understand
> > there is no emulation of a zFCP-l
tch. Thanks!
Kind regards
Philipp Kern
signature.asc
Description: Digital signature
cycle
> using build profiles: you need to do an initial build with the "stage1"
> profile (e.g. sbuild --profiles=stage1), install the resulting .deb,
> then do a normal build.
I uploaded it. Thanks. :)
Kind regards
Philipp Kern
signature.asc
Description: Digital signature
re harder to partition/segment than DASD-based storage…)
Kind regards
Philipp Kern
n, given that it's user
invoked and not usually scripted, should this be in /usr/sbin
instead?
Kind regards and thanks
Philipp Kern
signature.asc
Description: Digital signature
right thing.
Then I'll see a console, followed by some complaints about missing
/sys/bus/ccw/devices/virtio/cutype (sysfs not populating info on the
CCW
bus?)
Can you transcribe the actual failure you see?
Kind regards
Philipp Kern
bugs that you encounter.
Kind regards
Philipp Kern
[1] http://d-i.debian.org/daily-images/s390x/daily/generic/
signature.asc
Description: Digital signature
ine: -5), so that's a bit of a dead end.
Yeah, I had the same issue back in August. With current qemu and current
kernel (4.1 worked, but also 4.2) it worked for me.
Kind regards
Philipp Kern
[1]
http://lists.nongnu.org/archive/html/qemu-devel/2015-11/msg7.html
[2]
http://lists.nong
On Sun, Nov 01, 2015 at 11:54:27AM +0100, Philipp Kern wrote:
> I wonder how you got into the disk partitioner in the first place. All
> my tries caused fatal errors in the DASD configuration part and it
> wouldn't let me proceed. So s390-dasd will need a fix to detect this
> s
redibly fiddly,
especially at HEAD.) What version?
Kind regards
Philipp Kern
signature.asc
Description: Digital signature
t
> Maybe wb could do a “dak ls” and whatever the equivalent for dpo mini-dak is.
Unfortunately it is not being run on the same host as dak either.
Kind regards
Philipp Kern
signature.asc
Description: Digital signature
to
make it work, but I have and tested that part already. (Essentially
taken from lilo-installer.)
Kind regards and thanks
Philipp Kern
signature.asc
Description: Digital signature
oute SUSE
went with running grub2 from a kernel image booted by zipl and then
kexec()ing into the right kernel and initrd is a bit too much, though.
(OTOH, if someone wants to implement that for Debian that'd be great.)
Kind regards
Philipp Kern
signature.asc
Description: Digital signature
On Wed, Aug 26, 2015 at 09:56:32PM -0400, Stephen Powell wrote:
> On Tue, 25 Aug 2015 19:17:27 -0400 (EDT), Philipp Kern wrote:
> > ...
> > Technically using Hercules is probably your best bet[*]. It should be able
> > to do MIPS similar to your existing z800 on contemp
ilar to your existing z800 on contemporary x86-64 hardware.
(You'll certainly know for how many MIPS your existing machine was
sized and Hercules does display them.) You might need to be careful with
relation to I/O, of course.
Kind regards
Philipp Kern
[*] There's also z/PDT. But well, that one really need discussions with IBM
and all.
the chroot during installation and load that up, but the correct
way is to get zipl to install.
Kind regards and thanks
Philipp Kern
process.
> > I found the culprit: The tree-isolate-paths pass in gcc 4.9. If I
> > disable this pass I get:
> And -fno-delete-null-pointer-checks seems to be the correct option.
Thanks! I uploaded that to replace the gcc-4.8 build dependency.
Kind regards
Philipp Kern
signature.asc
Description: Digital signature
turn 0;
3344: a7 28 00 00 lhi %r2,0
3348: a7 f4 00 04 j 3350
That does look much better for 3338, 3340, not really for 3348 (to 3350). It
does fix the issue at hand, but it's a band-aid at most. I installed the
package on wheezy (co
try to run the python3.4
testsuite.
I won't have time to handle this until late September.
Understood. Thanks.
Kind regards
Philipp Kern
--
To UNSUBSCRIBE, email to debian-s390-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@l
1073740750258176.0
Sadly python3-minimal fails to configure because of this, which in turn
lets other packages being upgraded fail to fully install.
int to float casts are working with python2, but are completely broken
with python3:
float(1)
1073741824.0
float(-1)
-1073741824.0
On Fri, Aug 15, 2014 at 10:46:54AM +0200, Michael Holzheu wrote:
> On Thu, 14 Aug 2014 21:45:53 -0400 (EDT)
> Stephen Powell wrote:
> > On Thu, 14 Aug 2014 10:32:42 -0400 (EDT), Philipp Kern wrote:
> > > Hrm. Odd. It shouldn't be because the brokeness relates to the C
self and zipl does not use the C
library. That being said, I had to recompile s390-tools on sid,
and I do not run sid due to the C breakage. It worked before the
recompilation, hence there might be a change in sid vs. wheezy
that caused this.
You are talking about Hercules, right?
Kind regards
Phil
file a bug against s390-tools in Debian so that it's
not forgotten.
Kind regards and thanks
Philipp Kern
signature.asc
Description: Digital signature
sues.
Will it necessarily explode if both libcs are loaded into the same
address space or only if the broken functionality is used? Would
setjmp/longjmp only break if used across libc6/6.1 boundaries? Passing
around an incompatible pthread struct seems bad, though.
If this would work, a re-bootstrap w
#x27;t
know where. Some of it might belong into the installation manual, but most
of it is just how Debian network configuration works on the mainframe
and I'm not sure if we have good enduser docs where this would fit…
(Thanks for writing it up!)
Kind regards
Philipp Kern
--
T
is a question for the package maintainer. Philipp, are you
> listening?
Is znetconf solely doing runtime configuration or does it also try to persist
it?
Kind regards
Philipp Kern
signature.asc
Description: Digital signature
t happen for Qt for quite some time.)
Kind regards
Philipp Kern
signature.asc
Description: Digital signature
;load normal".) I hope this helps someone.
Maybe you could check out the debian-installer manual from SVN and create a
patch? I'd be happy to commit it.
Thanks
Philipp Kern
--
To UNSUBSCRIBE, email to debian-s390-requ...@lists.debian.org
with a subject of "unsubscribe
On Thu, Jul 04, 2013 at 03:01:14PM -0400, David Prévot wrote:
> No one answer yet to the following question, can you please share your
> thoughts?
Please setup /s390x/ -> /s390/ for now.
Thanks
Philipp Kern
--
To UNSUBSCRIBE, email to debian-s390-requ...@lists.debian.org
with a s
o working on the port
both wrt buildd maintenance and debugging. He is listed on [1], too.
But obviously that does not imply GCC maintainance for s390*.
And indeed, we should've copied Bastian on this. I apologize.
Kind regards
Philipp Kern
[1] http://release.debian.org/wheezy/arch_qualify.h
On Sun, Jun 30, 2013 at 01:45:19PM +, Jeremy Stanley wrote:
> On 2013-06-30 13:58:35 +0200 (+0200), Philipp Kern wrote:
> [...]
> > convmv helps if you're dealing with wrongly encoded files.
> Wrongly encoded fileNAMEs perhaps, but for wrongly encoded file
> CONTENT
ow system (or a substitute
> application for xterm, such as Gnome Terminal) and the other for virtual
> terminals (vt1-vt6).
UTF-8 has been the default on Debian for ages now and there really is no reason
to run it with a different charset. (convmv helps if you're dealing with
wrongly
Package: crash
Version: 6.0.6-1
Severity: normal
crash contains support for s390x, please build it on this architectures.
It can confirm that it builds and that the result works.
Thanks
Philipp Kern
--
To UNSUBSCRIBE, email to debian-s390-requ...@lists.debian.org
with a subject of
Package: makedumpfile
Version: 1.4.3-1
Severity: normal
makedumpfile contains support for s390x, please build it on this
architecture. I can confirm that it builds and that the result works.
Thanks
Philipp Kern
--
To UNSUBSCRIBE, email to debian-s390-requ...@lists.debian.org
with a subject of
there are several options in this scenario.
my personal guess is that there's probably nothing s390x-specific to it,
it's probably broken with 64bit big endian. The d-ports build for
sparc64 fails as well.
Kind regards
Philipp Kern
signature.asc
Description: Digital signature
PIV, so I'm a bit at a loss. The WWPNs of the peers
should turn up in /sys/bus/ccw/drivers/zfcp/0.0.3400 in any case, if it's
properly configured. Maybe somebody on LINUX-390 knows more about it.
Kind regards
Philipp Kern
signature.asc
Description: Digital signature
rt_rescan.
Apart from that the output of dmesg would be helpful to see why no port
has been detected.
Kind regards
Philipp Kern
signature.asc
Description: Digital signature
disk
already. The alternative is passing »dasd=240« (among with the other DASDs you
need) on the kernel command-line.
Kind regards
Philipp Kern
signature.asc
Description: Digital signature
t out and then abandoning their posts.
True. KVM (which is basically »-enable-kvm« passed to qemu) on s390x
itself works, it's just plain qemu-system-s390x on non-System z hardware
that doesn't. Hence you could also use hercules to get started.
Kind regards
Philipp Kern
signature.asc
Description: Digital signature
On Wed, Dec 26, 2012 at 12:24:35PM +0100, Christian PERRIER wrote:
> Is anyone among s390 porters able to build and upload these two packages.
Done.
Kind regards
Philipp Kern
signature.asc
Description: Digital signature
t should
invoke Xtightvnc with the right options. Still it's of course possible
that there's a bug in the software.
Kind regards
Philipp Kern
signature.asc
Description: Digital signature
. Maybe one would have the best
chance with pdl to debug that. 0x80c28d80 is on the heap in any case
(i.e. not an anonymous mmap), my assumption is still that something in the
allocator or the kernel's fishy.
In any case feel free to give back builds failing with this reason. That's
what I did so far.
Kind regards
Philipp Kern
signature.asc
Description: Digital signature
D_BUS}-$env{ID_UID}"
KERNEL=="dasd*[0-9]", ENV{ID_UID}=="?*",
SYMLINK+="disk/by-id/$env{ID_BUS}-$env{ID_UID}-part%n"
Could you please drop the above two lines, preferably for wheezy?
Currently it produces spurious warnings during the boot process about
dasd_id
bian,a=unstable
Pin-Priority: 300
Package: *
Pin: release o=Debian
Pin-Priority: -1
Then you can do »sudo apt-get install s390-tools=1.16.0-2«.
In eight days it will probably enter wheezy, but obviously more eyes
are appreciated.
Kind regards
Philipp Kern
signature.asc
Description: Digital signature
) unstable; urgency=low
+
+ * Drop the now non-existent vol_id from the shipped udev ruleset
+and use blkid instead.
+
+ -- Philipp Kern Fri, 30 Nov 2012 22:10:43 +
+
s390-tools (1.16.0-1) unstable; urgency=low
* New upstream release.
diff -Nru s390-tools-1.16.0/debian/s390
ignore=all,!0.0.1150,!0.0.fd00-0.0.fd02
|
|
| Please note that all devices numbers' hex digits need to be specified in
| lower case. To be considered during the installer's boot process the
| above option needs to be added to parmfile.debian.
But I'm neither an English native
try to get a solution.
Both don't cause any harm, though.
Kind regards
Philipp Kern
signature.asc
Description: Digital signature
k. That's the -4- in
3.2.0-4-s390x. This is increased when symbols are incompatible and
modules need to be rebuilt.
It might work to comment out the following line in »debian/rules.real«:
python debian/bin/buildcheck.py $(DIR) $(ARCH) $(FEATURESET) $(FLAVOUR)
Then probably rules.gen nee
g might be a
better fit for support.)
Kind regards
Philipp Kern
signature.asc
Description: Digital signature
or KDE and
run it via X forwarding or xdmcp or VNC. But that's all not s390-specific.
Kind regards
Philipp Kern
signature.asc
Description: Digital signature
open /dev/tty0 (No such file or directory).
On what graphical console would you expect X to appear? z doesn't have any.
All you can do is using some kind of remote desktop, but not through startx.
Kind regards
Philipp Kern
signature.asc
Description: Digital signature
for the s390 architecture and not the s390x one.
What does «dpkg-architecture -qDEB_HOST_ARCH» say?
> 4) Why is the kernel build process for s390x different than the one
> documented in the Handbook?
«Because the handbook is outdated» would be my guess.
Kind regards
Philipp Kern
signatu
etc. of the new IBM EC12 systems, and I'd
> like to try building Debian in that environment.
>
> What's involved in doing a complete Debian build on the s390x architecture?
It would be highly unusual to rebuild Debian completely. So you might want to
clarify what you try to acc
ver to /etc/modules. In theory the last script to
execute during the boot process would be /etc/rc.local, but you should try to
be idempotent there. Obviously that wouldn't help you if you need it ready for
any earlier script to run properly.
Kind regards
Philipp Kern
--
To UNSUBSCRIBE
And I fear
that the additional bits cannot be discarded at runtime neither, but I cannot
test this right now.
Interestingly enough the kernel is already in its plain form 2.23 times bigger
than an amd64 build of vmlinuz-3.2.0-3-amd64.
Kind regards
Philipp Kern
> [1] http://www.vm.ibm.com
find any package in there for wheezy. (Except that there actually is exactly
one, I wonder why that is because we still update wheezy proper directly. I'll
followup on that.)
Kind regards
Philipp Kern
--
To UNSUBSCRIBE, email to debian-s390-requ...@lists.debian.org
with a subject
1 - 100 of 168 matches
Mail list logo
