Your message dated Tue, 13 Mar 2007 00:02:23 +0000 with message-id <E1HQuT9-0006sx-Oq@ries.debian.org> and subject line Bug#414490: fixed in s390-dasd 0.0.21 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database)
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: doesn't work at high priority and crashes at medium priority in hercules
- From: Joey Hess <joeyh@debian.org>
- Date: Sun, 11 Mar 2007 22:56:05 -0400
- Message-id: <[🔎] 20070312025605.GA1135@kitenet.net>
Package: s390-dasd Version: 0.0.20 Severity: important Not setting this RC since there are ugly and horrible (respectively) workarounds, but this is errata-level trouble at best, and should be fixed if possible. ret = my_debconf_input ("medium", TEMPLATE_PREFIX "format", &ptr); As noted on irc, this question needs to be asked at at least high priority. Currently it's not possible to format a dasd in a default install, which is not good. Even less good is this crash that I get when running at medium priority in hercules. s390-dasd lists one available disk, 0.0.0120, and I select it. It asks if I want to format it, I say yes and it then crashes: 3888 read(7, "rootfs / rootfs rw 0 0\nnone /pro"..., 1024) = 171 3888 close(7) = 0 3888 munmap(0x77e91000, 4096) = 0 3888 lstat64("/sys/bus/ccw/drivers/dasd-fba", 0x7fa61258) = -1 ENOENT (No such file or directory) 3888 write(3, "SUBST s390-dasd/choose_select ch"..., 47) = 47 3888 read(0, "0\n", 4096) = 2 3888 write(3, "INPUT high s390-dasd/choose_sele"..., 35) = 35 3888 read(0, "0 question will be asked\n", 4096) = 25 3888 write(3, "GO\n", 3) = 3 3888 read(0, "0 ok\n", 4096) = 5 3888 write(3, "GET s390-dasd/choose_select\n", 28) = 28 3888 read(0, "0 0.0.0120\n", 4096) = 11 3888 write(3, "SUBST s390-dasd/format device 0."..., 39) = 39 3888 read(0, "0\n", 4096) = 2 3888 write(3, "SET s390-dasd/format false\n", 27) = 27 3888 read(0, "0 value set\n", 4096) = 12 3888 write(3, "INPUT medium s390-dasd/format\n", 30) = 30 3888 read(0, "0 question will be asked\n", 4096) = 25 3888 write(3, "GO\n", 3) = 3 3888 read(0, "0 ok\n", 4096) = 5 3888 write(3, "GET s390-dasd/format\n", 21) = 21 3888 read(0, "0 true\n", 4096) = 7 3888 open("/dev/disk/by-path/ccw-0.0.0120", O_RDONLY) = -1 ENOENT (No such file or directory) 3888 munmap(0x77e93000, 4096) = 0 3888 exit_group(1) = ? There is no /dev/disk/ at that point. If I start partman (which fails with the disk unformatted), /dev/disk does get created. Not sure how; I tried running update-dev but that does not do it. I can then go back to s390-dasd and it sucessfully formats the disk this time. FWIW, the hercules disk image was freshly created before this install using "dasdinit hercules-hercules-web-server-d-i.img 3390-1 root 1200" and my hercules config is as follows: CPUSERIAL 002623 CPUMODEL 3090 MAINSIZE 256 CODEPAGE default XPNDSIZE 0 #CNSLPORT 3270 #HTTPPORT 8081 noauth userid password #HTTPROOT /usr/share/hercules/ NUMCPU 2 LOADPARM 0120.... OSTAILOR LINUX PANRATE SLOW ARCHMODE ESA/390 000C 3505 hercules-hercules-web-server-d-i.kernel hercules-hercules-web-server-d-i.parmfile hercules-hercules-web-server-d-i.initrd autopad eof 0120 3390 /home/joey/tmp/digress-state/hercules-hercules-web-server-d-i.img 0A00 3088 CTCI /dev/net/tun 1500 192.168.2.2 192.168.2.1 255.255.255.255 0A01 3088 CTCI /dev/net/tun 1500 192.168.2.2 192.168.2.1 255.255.255.255 -- see shy joAttachment: signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
- To: 414490-close@bugs.debian.org
- Subject: Bug#414490: fixed in s390-dasd 0.0.21
- From: Frans Pop <fjp@debian.org>
- Date: Tue, 13 Mar 2007 00:02:23 +0000
- Message-id: <E1HQuT9-0006sx-Oq@ries.debian.org>
Source: s390-dasd Source-Version: 0.0.21 We believe that the bug you reported is fixed in the latest version of s390-dasd, which is due to be installed in the Debian FTP archive: s390-dasd_0.0.21.dsc to pool/main/s/s390-dasd/s390-dasd_0.0.21.dsc s390-dasd_0.0.21.tar.gz to pool/main/s/s390-dasd/s390-dasd_0.0.21.tar.gz s390-dasd_0.0.21_s390.udeb to pool/main/s/s390-dasd/s390-dasd_0.0.21_s390.udeb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 414490@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Frans Pop <fjp@debian.org> (supplier of updated s390-dasd package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmaster@debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Format: 1.7 Date: Tue, 13 Mar 2007 00:51:01 +0100 Source: s390-dasd Binary: s390-dasd Architecture: source s390 Version: 0.0.21 Distribution: unstable Urgency: low Maintainer: Debian Install System Team <debian-boot@lists.debian.org> Changed-By: Frans Pop <fjp@debian.org> Description: s390-dasd - Configure DASD (udeb) Closes: 414490 Changes: s390-dasd (0.0.21) unstable; urgency=low . [ Bastian Blank ] * Fix eckd format. (closes: #414490) * Make all templates critical. Files: 146836153e6fd081144e6138b2f60b90 736 debian-installer standard s390-dasd_0.0.21.dsc 5f22c70215a358cd8d5d6384ccada1db 47046 debian-installer standard s390-dasd_0.0.21.tar.gz 619e124b837b95f7df56cb814f5365b2 30902 debian-installer standard s390-dasd_0.0.21_s390.udeb Package-Type: udeb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFF9eiGgm/Kwh6ICoQRAlAIAKDR0jCitIeGsmPG+UCLN/pc55ygZgCgrBLt VJOwXiINp5qrkuWbJpwRhdU= =LBVl -----END PGP SIGNATURE-----
--- End Message ---