Bug#919825: systemd: local filesystems other than '/' and '/usr' not checked and mounted -- emergency mode
On Tue, Mar 12, 2019 at 12:37:27PM +0100, Michael Biebl wrote:
> I can't really trawl through the complete config file.
> What I noticed from the journal are errors like this
>
> Feb 14 04:12:20 smirkin systemd-udevd[435]: sr0: Failed to apply ACL:
> Operation not supported
> Feb 14 04:12:31 smirkin systemd-udevd[440]: sg1: Failed to apply ACL:
> Operation not supported
> ...
>
> You probably want to enable
> CONFIG_TMPFS_XATTR
> CONFIG_{TMPFS,EXT4_FS,XFS,BTRFS_FS,...}_POSIX_ACL
>
> If that makes a difference, I dunno.
Those kernel config parameters are currently designated "optional" in
the systemd README file, and I'd be really annoyed to find out they
aren't. I have no use for the extended attribute and ACL support in a
non-SELINUX context, but it would not surprise me in the least to find
out that systemd has some kind of dependency on it. I'll enable those
options for my next build.
> You could try running udev in debug mode (see /etc/udev/udev.conf) and
> check if you can spot any errors.
Worth a try.
Bug#919825: systemd: local filesystems other than '/' and '/usr' not checked and mounted -- emergency mode
On Thu, Mar 07, 2019 at 10:52:13AM +0100, Michael Biebl wrote: > Sounds a bit like > https://github.com/systemd/systemd/issues/3446#issuecomment-224046140 > > Please check that your kernel has all options enabled that are listed in > /usr/share/doc/systemd/README.gz > > Are you currently missing any of those options? I'll admit to getting bitten by CONFIG_FHANDLE not being set a long time ago. Back then, I was directed toward the systemd "README" file to see if there were any other kernel config options that I hadn't set correctly. I'm pretty sure none of the required options are missing, but an extra set of eyes looking at it couldn't hurt. My ".config" file for 5.0.0 is attached. Do please note at least one fundamental difference (philosophical?) between my hand-built kernels and the usual distro-provided kernels. I like to build-in the drivers that are needed at boot time, *including* any required firmware. I don't know if "systemd/udev" would (or should) be affected by the disk device drivers being built-in instead of modules, but it might be interesting to see if the Debian generic kernel for alpha configures the qlogic SCSI driver as built-in or modular (because it requires firmware that loads at driver initialization). I heard back concerning availability of a fixed generic kernel for Alpha. The latest upload of linux failed to build on a number of architectures, including Alpha. alpha_config.gz Description: application/gunzip
Bug#919825: systemd: local filesystems other than '/' and '/usr' not checked and mounted -- emergency mode
On Thu, Mar 07, 2019 at 10:17:05AM +0100, Michael Biebl wrote: > Could you attach > systemctl list-units --type device Had to specify additional "--all" flag, as all units of type "device" are "inactive" "dead". List attached. UNITLOAD ACTIVE SUB DESCRIPTION dev-sda2.device loaded inactive dead /dev/sda2 dev-sda5.device loaded inactive dead /dev/sda5 dev-sda7.device loaded inactive dead /dev/sda7 LOAD = Reflects whether the unit definition was properly loaded. ACTIVE = The high-level unit activation state, i.e. generalization of SUB. SUB= The low-level unit activation state, values depend on unit type. 3 loaded units listed. To show all installed unit files use 'systemctl list-unit-files'.
Bug#919825: systemd: local filesystems other than '/' and '/usr' not checked and mounted -- emergency mode
On Thu, Mar 07, 2019 at 10:09:10AM +0100, Michael Biebl wrote: > https://github.com/systemd/systemd/blob/master/src/fstab-generator/fstab-generator.c#L109 > https://github.com/systemd/systemd/blob/master/src/basic/virt.c#L430 > > There are various tests used to determine if the system runs in a > container environment. > What does systemd-detect-virt say? "none", now that the system is up and running. No idea what it would have said while the machine was in "emergency mode". From reading the manual page for "systemd-detect-virt", the message about running in a container could be because the virtualization detection logic was triggered by running in a chroot() environment (initrd). (I didn't look at the fstab-generator code, so this is pure speculation.)
Bug#919825: systemd: local filesystems other than '/' and '/usr' not checked and mounted -- emergency mode
On Thu, Mar 07, 2019 at 10:00:23AM +0100, Michael Biebl wrote: > Since alpha is not an officially supported architecture, I was not aware > that there is no Debian provided kernel for it. > > My main point was to test a kernel which has the same set of features / > config options enabled as the Debian one, to rule out obvious problems > like mission kernel features. An entirely reasonable request/approach to solving the problem, and one I'm willing to try :-). I've been bitten by differences in kernel configuration options on previous occasions. It may be a few days, but I'm confident I'll have a Debian-provided kernel within a reasonable time frame.
Bug#919825: systemd: local filesystems other than '/' and '/usr' not checked and mounted -- emergency mode
On Thu, Mar 07, 2019 at 09:00:24AM +0100, Michael Biebl wrote: > Am 20.01.2019 um 00:11 schrieb Bob Tracy: > > > Architecture: alpha > > > > Kernel: Linux 4.16.0 > > Could you test with a Debian provided kernel? Ben Hutchings grabbed the fix referenced here (https://salsa.debian.org/kernel-team/linux/merge_requests/79) for inclusion in sid, and the corresponding issue was closed approximately four weeks ago. A quick check of the kernels available over at "http://ftp.ports.debian.org/debian-ports/pool-alpha/main/l/linux/; doesn't show anything with a late enough date stamp to include the fix. If I'm mistaken as to the availability of a working generic kernel for alpha (single processor Miata variant), kindly point me to it and I'll be happy to give it a try. The generic kernel for single-processor alpha systems has been broken since version 3.18. Let me check with a few people over at the debian-alpha list and see what the status is. Thanks!
Bug#919825: systemd: local filesystems other than '/' and '/usr' not checked and mounted -- emergency mode
On Thu, Feb 28, 2019 at 07:36:37PM +0100, Michael Biebl wrote:
> Control: tags -1 + moreinfo
>
> Please attach the full output "journalctl -alb" output of such a failed
> boot.
>
> I'd also be interested in the output of
> udevadm info /sys/class/block/sda2
Apologies for the delay in responding. Wanted to wait for 5.0.0-final
to be released, and then I had to wait another 48 hours for the build to
finish.
Requested command output attached. I ran "journalctl -alb" in emergency
mode prior to performing any of the manual workaround steps I normally do
to bring the system up multi-user. Only the first of the "failed to start"
local file systems ("/dev/sda5", corresponding to "/tmp") showed up in the
output.
Several packages updated since original bug report. No change in symptoms.
Current kernel is 5.0.0, systemd and udev are 241-1, and initramfs-tools*
are 0.133. Curiously, I've been seeing syslog messages from
"syslogd-fstab-generator" to the effect of "Running in a container, ignoring
fstab device entry for /dev/sda4" (where "/dev/sda4" is my swap partition).
Same log entry for the cdrom device (/dev/hda). No virtualization support
of any kind has consciously been installed/configured, so where is this
notion of running in a container coming from? Probably *not* coincidentally,
swap is no longer automatically enabled by systemd.
-- Logs begin at Thu 2019-02-14 04:12:08 CST, end at Thu 2019-02-14 04:12:38
CST. --
Feb 14 04:12:08 smirkin systemd-journald[400]: Missed 164 kernel messages
Feb 14 04:12:08 smirkin kernel: [drm] radeon: 512M of GTT memory ready.
Feb 14 04:12:08 smirkin kernel: [drm] GART: num cpu pages 65536, num gpu pages
131072
Feb 14 04:12:08 smirkin kernel: [drm] PCI GART of 512M enabled (table at
0xDF28).
Feb 14 04:12:08 smirkin kernel: radeon :00:0b.0: WB disabled
Feb 14 04:12:08 smirkin kernel: radeon :00:0b.0: fence driver on ring 0 use
gpu addr 0x2000 and cpu addr 0x(ptrval)
Feb 14 04:12:08 smirkin kernel: [drm] Supports vblank timestamp caching Rev 2
(21.10.2013).
Feb 14 04:12:08 smirkin kernel: [drm] Driver supports precise vblank timestamp
query.
Feb 14 04:12:08 smirkin kernel: [drm] radeon: irq initialized.
Feb 14 04:12:08 smirkin kernel: [drm] Loading R100 Microcode
Feb 14 04:12:08 smirkin kernel: [drm] radeon: ring at 0x20002000
Feb 14 04:12:08 smirkin kernel: [drm] ring test succeeded in 0 usecs
Feb 14 04:12:08 smirkin kernel: [drm] ib test succeeded in 0 usecs
Feb 14 04:12:08 smirkin kernel: [drm] No TV DAC info found in BIOS
Feb 14 04:12:08 smirkin kernel: [drm] Radeon Display Connectors
Feb 14 04:12:08 smirkin kernel: [drm] Connector 0:
Feb 14 04:12:08 smirkin kernel: [drm] VGA-1
Feb 14 04:12:08 smirkin kernel: [drm] DDC: 0x60 0x60 0x60 0x60 0x60 0x60 0x60
0x60
Feb 14 04:12:08 smirkin kernel: [drm] Encoders:
Feb 14 04:12:08 smirkin kernel: [drm] CRT1: INTERNAL_DAC1
Feb 14 04:12:08 smirkin kernel: [drm] Connector 1:
Feb 14 04:12:08 smirkin kernel: [drm] DVI-I-1
Feb 14 04:12:08 smirkin kernel: [drm] HPD1
Feb 14 04:12:08 smirkin kernel: [drm] DDC: 0x64 0x64 0x64 0x64 0x64 0x64 0x64
0x64
Feb 14 04:12:08 smirkin kernel: [drm] Encoders:
Feb 14 04:12:08 smirkin kernel: [drm] CRT2: INTERNAL_DAC2
Feb 14 04:12:08 smirkin kernel: [drm] DFP1: INTERNAL_TMDS1
Feb 14 04:12:08 smirkin kernel: [drm] fb mappable at 0x1004
Feb 14 04:12:08 smirkin kernel: [drm] vram apper at 0x1000
Feb 14 04:12:08 smirkin kernel: [drm] size 5242880
Feb 14 04:12:08 smirkin kernel: [drm] fb depth is 24
Feb 14 04:12:08 smirkin kernel: [drm]pitch is 5120
Feb 14 04:12:08 smirkin kernel: Console: switching to colour frame buffer
device 160x64
Feb 14 04:12:08 smirkin kernel: radeon :00:0b.0: fb0: radeondrmfb frame
buffer device
Feb 14 04:12:08 smirkin kernel: [drm] Initialized radeon 2.50.0 20080528 for
:00:0b.0 on minor 0
Feb 14 04:12:08 smirkin kernel: qla1280: QLA1040 found on PCI bus 1, dev 9
Feb 14 04:12:08 smirkin kernel: random: crng init done
Feb 14 04:12:08 smirkin kernel: scsi(0:0): Resetting SCSI BUS
Feb 14 04:12:08 smirkin kernel: scsi host0: QLogic QLA1040 PCI to SCSI Host
Adapter
Firmware version: 7.65.06, Driver
version 3.27.1
Feb 14 04:12:08 smirkin kernel: scsi 0:0:0:0: Direct-Access IBM
DXHS36D 0252 PQ: 0 ANSI: 3
Feb 14 04:12:08 smirkin kernel: scsi(0:0:0:0):
Feb 14 04:12:08 smirkin kernel: Sync: period 10, offset 12
Feb 14 04:12:08 smirkin kernel: , Wide
Feb 14 04:12:08 smirkin kernel: , Tagged queuing: depth 31
Feb 14 04:12:08 smirkin kernel:
Feb 14 04:12:08 smirkin kernel: scsi 0:0:0:0: Power-on or device reset occurred
Feb 14 04:12:08 smirkin kernel: scsi host1: pata_cmd64x
Feb 14 04:12:08 smirkin kernel: sd 0:0:0:0: [sda] 71132960 512-byte logical
blocks: (36.4 GB/33.9 GiB)
Feb 14 04:12:08 smirkin kernel: scsi host2: pata_cmd64x
Feb 14 04:12:08 smirkin kernel: ata1: PATA max MWDMA2 cmd 0x1f0 ctl 0x3f6 bmdma
0x9480 irq
Bug#883089: udev: on alpha architecture, /dev/disk/by-XXX nodes not created
On Fri, Dec 01, 2017 at 06:13:01PM -0600, Bob Tracy wrote: > Not ignoring you... PWS 433au takes overnight to build a kernel these > days. > > Rebuilt 4.14 with the few changes noted in my previous message. Will > try it tomorrow when I've got a couple of free hours to collect data and > deal with the consequences if it doesn't work. Report to follow... Request closure of this bug. Effective with the 4.14 kernel, firmware (if applicable) for built-in drivers must be included as part of the kernel build, and my qlogic SCSI card had been relying on the firmware being loaded from disk at boot time. This kernel configuration change, and possibly a few other minor configuration changes as suggested by the "systemd" README file, got me back on track. Particular thanks to Michael Cree for letting me know about the probable firmware issue. --Bob
Bug#883089: udev: on alpha architecture, /dev/disk/by-XXX nodes not created
On Wed, Nov 29, 2017 at 11:10:41PM -0600, Bob Tracy wrote: > On Wed, Nov 29, 2017 at 05:12:58PM +0100, Michael Biebl wrote: > > Please test the kernel that is provided by Debian and report back if it > > works with that one. Not ignoring you... PWS 433au takes overnight to build a kernel these days. Rebuilt 4.14 with the few changes noted in my previous message. Will try it tomorrow when I've got a couple of free hours to collect data and deal with the consequences if it doesn't work. Report to follow... --Bob
Bug#883089: udev: on alpha architecture, /dev/disk/by-XXX nodes not created
On Wed, Nov 29, 2017 at 05:12:58PM +0100, Michael Biebl wrote: > Please check all other kernel config options as well that are listed in > /usr/share/doc/systemd/README.gz A few of the listed config options do not exist, at least in 4.14: CONFIG_DMIID CONFIG_DEVPTS_MULTIPLE_INSTANCES There were a few namespace and crypto config settings that were configured as modules rather than built-in, so I fixed those and am in the process of rebuilding the 4.14 kernel. > Please test the kernel that is provided by Debian and report back if it > works with that one. The Debian-supplied kernels for alpha have been problematic in the past, to the point I've been building my own from the mainline kernel.org source tree for several years now. On a possibly related note, three years ago bug #652459 was opened because systemd and udev failed to work properly with "/usr" being a separate partition from "/". Has anything happened with systemd and/or initramfs development that broke the resolution of that bug? Thanks for the assist! I *do* appreciate your time and trouble. --Bob
Bug#883089: udev: on alpha architecture, /dev/disk/by-XXX nodes not created
Package: udev Version: 235-3 Severity: important Dear Maintainer, With kernel version 4.13, udev worked correctly at least two releases ago. The current release (and maybe the prior one) fails to detect/enumerate SCSI disk partitions (both real filesystems and swap partitions) except for "/" and "/usr" which are mounted immediately upon boot by the initial ramdisk. "journalctl -xb" has multiple messages of the form dev-sdaX.device: Job dev-sdaX.device/start timed out. Timed out waiting for device dev-sdaX.device. When this problem appeared nearly three years ago, the issue was CONFIG_FHANDLE not being set in the kernel configuration: it is currently set, and has been for every kernel build since that time. Possibly related issue: the USB subsystem failed to initialize as well. In systemd's emergency mode, all the various filesystems and swap partitions can be mounted or enabled as appropriate. After doing this and exiting the emergency shell with a cntl-d, the system comes up in a mostly usable state. Networking can be manually started, as can the USB subsystem. The situation is *much* worse with the 4.14 kernel. "cat /proc/scsi/scsi" in the resulting emergency shell shows only the libata-mapped IDE cdrom device, i.e., the real SCSI host adapter and attached disk aren't seen at all. -- Package-specific info: -- System Information: Debian Release: buster/sid APT prefers unreleased APT policy: (500, 'unreleased'), (500, 'unstable') Architecture: alpha Kernel: Linux 4.13.0 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) Versions of packages udev depends on: ii adduser 3.116 ii libacl1 2.2.52-3 ii libblkid12.30.2-0.1 ii libc6.1 2.25-1 ii libkmod2 24-1 ii libselinux1 2.7-2 ii libudev1 235-3 ii lsb-base 9.20170808 ii procps 2:3.3.12-3 ii util-linux 2.30.2-0.1 udev recommends no packages. udev suggests no packages. Versions of packages udev is related to: ii systemd 235-3 -- debconf information: udev/title/upgrade: udev/sysfs_deprecated_incompatibility: udev/reboot_needed: udev/new_kernel_needed: false P: /devices/parport0 E: DEVPATH=/devices/parport0 E: DEVTYPE=parport E: SUBSYSTEM=parport P: /devices/pci:00/:00:03.0 E: DEVPATH=/devices/pci:00/:00:03.0 E: DRIVER=tulip E: MODALIAS=pci:v1011d0019svsdbc02sc00i00 E: PCI_CLASS=2 E: PCI_ID=1011:0019 E: PCI_SLOT_NAME=:00:03.0 E: PCI_SUBSYS_ID=: E: SUBSYSTEM=pci P: /devices/pci:00/:00:03.0/net/eth0 E: DEVPATH=/devices/pci:00/:00:03.0/net/eth0 E: IFINDEX=2 E: INTERFACE=eth0 E: SUBSYSTEM=net P: /devices/pci:00/:00:04.0 E: DEVPATH=/devices/pci:00/:00:04.0 E: DRIVER=pata_cmd64x E: MODALIAS=pci:v1095d0646svsdbc01sc01i80 E: PCI_CLASS=10180 E: PCI_ID=1095:0646 E: PCI_SLOT_NAME=:00:04.0 E: PCI_SUBSYS_ID=: E: SUBSYSTEM=pci P: /devices/pci:00/:00:04.0/ata1/ata_port/ata1 E: DEVPATH=/devices/pci:00/:00:04.0/ata1/ata_port/ata1 E: SUBSYSTEM=ata_port P: /devices/pci:00/:00:04.0/ata1/host1 E: DEVPATH=/devices/pci:00/:00:04.0/ata1/host1 E: DEVTYPE=scsi_host E: SUBSYSTEM=scsi P: /devices/pci:00/:00:04.0/ata1/host1/scsi_host/host1 E: DEVPATH=/devices/pci:00/:00:04.0/ata1/host1/scsi_host/host1 E: SUBSYSTEM=scsi_host P: /devices/pci:00/:00:04.0/ata1/host1/target1:0:0 E: DEVPATH=/devices/pci:00/:00:04.0/ata1/host1/target1:0:0 E: DEVTYPE=scsi_target E: SUBSYSTEM=scsi P: /devices/pci:00/:00:04.0/ata1/host1/target1:0:0/1:0:0:0 E: DEVPATH=/devices/pci:00/:00:04.0/ata1/host1/target1:0:0/1:0:0:0 E: DEVTYPE=scsi_device E: MODALIAS=scsi:t-0x05 E: SUBSYSTEM=scsi P: /devices/pci:00/:00:04.0/ata1/host1/target1:0:0/1:0:0:0/bsg/1:0:0:0 N: bsg/1:0:0:0 E: DEVNAME=/dev/bsg/1:0:0:0 E: DEVPATH=/devices/pci:00/:00:04.0/ata1/host1/target1:0:0/1:0:0:0/bsg/1:0:0:0 E: MAJOR=254 E: MINOR=1 E: SUBSYSTEM=bsg P: /devices/pci:00/:00:04.0/ata1/host1/target1:0:0/1:0:0:0/scsi_device/1:0:0:0 E: DEVPATH=/devices/pci:00/:00:04.0/ata1/host1/target1:0:0/1:0:0:0/scsi_device/1:0:0:0 E: SUBSYSTEM=scsi_device P: /devices/pci:00/:00:04.0/ata1/link1/ata_link/link1 E: DEVPATH=/devices/pci:00/:00:04.0/ata1/link1/ata_link/link1 E: SUBSYSTEM=ata_link P: /devices/pci:00/:00:04.0/ata1/link1/dev1.0/ata_device/dev1.0 E: DEVPATH=/devices/pci:00/:00:04.0/ata1/link1/dev1.0/ata_device/dev1.0 E: SUBSYSTEM=ata_device P: /devices/pci:00/:00:04.0/ata1/link1/dev1.1/ata_device/dev1.1 E: DEVPATH=/devices/pci:00/:00:04.0/ata1/link1/dev1.1/ata_device/dev1.1 E: SUBSYSTEM=ata_device P: /devices/pci:00/:00:04.0/ata2/ata_port/ata2 E: DEVPATH=/devices/pci:00/:00:04.0/ata2/ata_port/ata2 E: SUBSYSTEM=ata_port P:
Bug#855486: libkf5purpose-bin: inappropriate install dependency on nodejs for some architectures
Package: libkf5purpose-bin Version: 1.1-4 Severity: important Dear Maintainer, For several architectures, including at least alpha and hppa, there is no "nodejs" package available. For those architectures, "libkf5purpose-bin" has an installation dependency on "nodejs" that needs to be removed. The above action has supposedly already been taken for "armel", which also does not have "nodejs" built. Respectfully, --Bob -- System Information: Debian Release: 9.0 APT prefers unreleased APT policy: (500, 'unreleased'), (500, 'unstable') Architecture: alpha Kernel: Linux 4.9.0 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system)
Bug#855259: nodejs: FTBFS on alpha architecture
Request bug closure with probable status of "won't fix". Did not realize what I was *really* asking for was a port of a Javascript JIT compiler, which isn't going to happen for the alpha architecture (nor any of several others represented in the Debian ports archive). Original reason for filing this bug report is an inappropriate dependency on this package by another. A more appropriately targeted bug report will be sent to the maintainer(s) of that package requesting removal of the dependency on "nodejs". Apologies for the noise. --Bob
Bug#855259: nodejs: FTBFS on alpha architecture
Source: nodejs Version: 4.7.2~dfsg-2 Severity: serious Justification: fails to build from source Dear Maintainer, The subject package fails to build on alpha systems due to an inappropriate selection of compiler flags during configuration. In particular "-m32" is not valid on alpha. My guess is that a solution might look something like the current patch for "s390". Installed gcc version is 6.3.0 20170205 (Debian 6.3.0-6). Installed binutils version is 2.27.90.20170205 -- System Information: Debian Release: 9.0 APT prefers unreleased APT policy: (500, 'unreleased'), (500, 'unstable') Architecture: alpha Kernel: Linux 4.9.0 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system)
Bug#548096: hangs after doing its job
Package: bind9-host
Version: 1:9.9.5.dfsg-12.1
Followup-For: Bug #548096
Dear Maintainer,
An earlier respondent mentioned the hang occuring with the "host" command as
well.
I have an Alpha PWS-433au running 4.5.0-rc4 (compiled from the stock
"kernel.org"
source tree). Libraries and userspace are fully up-to-date "sid". I've noticed
the hang issue since approximately the beginning of February of this year.
Locally, running "strace host gherkin.frus.com" (gherkin is my local nameserver)
runs to completion about half the time. The rest of the time, I see this:
(...)
futex(0x20002e6fad4, FUTEX_WAKE_OP_PRIVATE, 1, 1, 0x20002e6fad0, {FUTEX_OP_SET,
0, FUTEX_OP_CMP_GT, 1}) = 1
futex(0x20002e6fa58, FUTEX_WAKE_PRIVATE, 1) = 1
rt_sigaction(SIGHUP, {0x277b100, ~[RTMIN RT_1], 0}, NULL, 8, 0x27ff0c0)
= 0
sigsuspend([FPE]gherkin.frus.com has address 192.158.254.49
gherkin.frus.com has IPv6 address 2001:5c0:1500:a800:222:4dff:fe51:6246
gherkin.frus.com mail is handled by 10 merkin.frus.com.
gherkin.frus.com mail is handled by 15 gherkin.frus.com.
gherkin.frus.com mail is handled by 21 mx-b.cirr.com.
gherkin.frus.com mail is handled by 20 mx-a.cirr.com.
A successful run looks like this:
(...)
futex(0x20002e6fad4, FUTEX_WAKE_OP_PRIVATE, 1, 1, 0x20002e6fad0, {FUTEX_OP_SET,
0, FUTEX_OP_CMP_GT, 1}) = 1
futex(0x20002e6fa58, FUTEX_WAKE_PRIVATE, 1) = 1
rt_sigaction(SIGHUP, {0x277b100, ~[RTMIN RT_1], 0}, NULL, 8, 0x27ff0c0)
= 0
sigsuspend([FPE]gherkin.frus.com has address 192.158.254.49
gherkin.frus.com has IPv6 address 2001:5c0:1500:a800:222:4dff:fe51:6246
gherkin.frus.com mail is handled by 20 mx-a.cirr.com.
gherkin.frus.com mail is handled by 10 merkin.frus.com.
gherkin.frus.com mail is handled by 21 mx-b.cirr.com.
gherkin.frus.com mail is handled by 15 gherkin.frus.com.
) = ? ERESTARTNOHAND (To be restarted if no handler)
--- SIGTERM {si_signo=SIGTERM, si_code=SI_TKILL, si_pid=4925, si_uid=1000} ---
sigreturn({mask=[HUP INT TERM]})= -1 EINTR (Interrupted system call)
futex(0x2000102f9c0, FUTEX_WAIT_PRIVATE, 2, NULL) = 0
futex(0x2000102f9c0, FUTEX_WAKE_PRIVATE, 1) = 0
futex(0x20002e6fad4, FUTEX_WAKE_OP_PRIVATE, 1, 1, 0x20002e6fad0, {FUTEX_OP_SET,
0, FUTEX_OP_CMP_GT, 1}) = 1
futex(0x20002e6fa58, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0x20002e6fad4, FUTEX_CMP_REQUEUE_PRIVATE, 1, 2147483647, 0x20002e6fa58,
12) = 1
futex(0x20002e6fa58, FUTEX_WAKE_PRIVATE, 1) = 1
write(4, "\0\0\0\0\377\377\377\377", 8) = 8
epoll_ctl(5, EPOLL_CTL_DEL, 3, 11fb63430) = 0
close(5)= 0
close(3)= 0
close(4)= 0
futex(0x20002e71aac, FUTEX_WAKE_OP_PRIVATE, 1, 1, 0x20002e71aa8, {FUTEX_OP_SET,
0, FUTEX_OP_CMP_GT, 1}) = 1
futex(0x20002e71a58, FUTEX_WAKE_PRIVATE, 1) = 1
open("/proc/sys/vm/overcommit_memory", O_RDONLY|O_CLOEXEC) = 3
read(3, "0", 1) = 1
close(3)= 0
madvise(0x20008022000, 196608, MADV_DONTNEED) = 0
munmap(0x2038000, 177304) = 0
exit_group(0) = ?
+++ exited with 0 +++
This "smells" like a race condition of some kind, but I have no idea where
the issue really lies. Could be something changed in one of the recent 4.X
kernels, or could be a library update that triggered this. The "bind9" packages
have been fairly stable, and I don't recall an update to them prior to this
issue appearing.
Respectfully,
--Bob
-- System Information:
Debian Release: stretch/sid
APT prefers unreleased
APT policy: (500, 'unreleased'), (500, 'unstable')
Architecture: alpha
Kernel: Linux 4.5.0-rc4
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
Versions of packages bind9-host depends on:
ii libbind9-90 1:9.9.5.dfsg-12.1
ii libc6.1 2.22-3
ii libcap2 1:2.24-12
ii libcomerr21.42.13-1
ii libdns100 1:9.9.5.dfsg-12.1
ii libgssapi-krb5-2 1.13.2+dfsg-5
ii libisc95 1:9.9.5.dfsg-12.1
ii libisccfg90 1:9.9.5.dfsg-12.1
ii libk5crypto3 1.13.2+dfsg-5
ii libkrb5-3 1.13.2+dfsg-5
ii liblwres901:9.9.5.dfsg-12.1
ii libssl1.0.2 1.0.2g-1
ii libxml2 2.9.3+dfsg1-1
bind9-host recommends no packages.
bind9-host suggests no packages.
-- no debconf information
Bug#789807: [alpha] cmake: testsuite failure: compiler feature "c_function_prototypes" is not known to C compiler
I think I may have found the issue. Not sure if other architectures
could be affected.
Looking at the cmake build artifacts under the "Build" directory, there
are several instances of "feature_tests.c" and "feature_tests.cxx" with
"const char features[]" initialized to '{ "" ... }' where I'm reasonably
certain the intent is for the first byte of the "features" array to be a
NULL. When "strings" is run on the resulting ".bin" file to extract the
tokens of interest, there's no leading NULL byte in front of what is
supposed to be the first non-NULL character in "features": that's where
the mysterious leading "k" is coming from, and why only the first token
in the array is "corrupted" in that manner. In other words, whichever
feature appears first in the "const char features[]" array is going to
be the one flagged as not supported.
Replacing "" with "\0" correctly produces the intended NULL byte at the
start of the array, and ultimately allows a working "cmake" to be built
on Alpha.
The question then is whether "" is supposed to compile to a NULL byte in
the context of the "const char features[]" array, and whether this
compiler behavior applies to other architectures. My fear is that we're
simply getting lucky on x86, and any NULL in front of the array is there
by accident.
Not sure where/how to apply a proper fix.
--Bob
Bug#660960: tight loop attempting to madvise(..., MADV_DONTNEED) locked memory
On Fri, Apr 27, 2012 at 08:12:51AM +0200, Mike Hommey wrote: Let me guess... alpha has non-4K page size. Page size was 8K the last time I checked, which was admittedly a long time ago. --Bob -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#660960: tight loop attempting to madvise(..., MADV_DONTNEED) locked memory
Earlier messages in this bug-report thread indicated use of Flash would also trigger the madvise() madness. I'm happy (?) to report that visiting Flash-enabled web sites reliably triggers this condition on the Alpha platform for *all* releases of firefox/iceweasel after 9.0.1. Michael Cree gets the nod for noting his backtraces ending in madvise() while we Alpha users were trying to figure out what was going on. Mike H. -- Thanks in advance for any fix/workaround you can come up with. --Bob -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#649641: pulseaudio mutex issue on Alpha architecture
Verified that the previously-mentioned workaround is applicable to Alpha, and that it works: no more mutex failures. The specific implementation of the workaround for the 1.1-1 source package is to patch m4/ax_pthread.m4 line 266ff to read as follows: AC_CACHE_CHECK([for PTHREAD_PRIO_INHERIT], ax_cv_PTHREAD_PRIO_INHERIT, [ AC_LINK_IFELSE( AC_LANG_PROGRAM([[#include pthread.h]], [[int i = PTHREAD_PRIO_INHERIT;]]), [ax_cv_PTHREAD_PRIO_INHERIT=no], [ax_cv_PTHREAD_PRIO_INHERIT=no]) ]) i.e., ax_cv_PTHREAD_PRIO_INHERIT gets set to no regardless of whether the test program compiles successfully (which it does on Alpha). -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#649641: pulseaudio mutex issue on Alpha architecture
Package: pulseaudio Version: 1.1-1 Severity: important Iceweasel and firefox browsers crash with the following error: Assertion 'pthread_mutex_unlock(m-mutex) == 0' failed at pulsecore/mutex-posix.c:106, function pa_mutex_unlock(). Aborting. Always reproducible by starting either firefox or iceweasel, then clicking on the drop-down main menu in the upper-left corner of the browser window. The application immediately aborts with the above error message. See https://bugs.meego.com/show_bug.cgi?id=13567 for a similar bug report on the ARM platform. A workaround suggested there is to disable the PTHREAD priority inheritance feature (in the source package) by adding pulseaudio_cv_PTHREAD_PRIO_INHERIT=no in configure.ac before AS_IF([test $pulseaudio_cv_PTHREAD_PRIO_INHERIT = yes], [ AC_DEFINE([HAVE_PTHREAD_PRIO_INHERIT], 1, [Have PTHREAD_PRIO_INHERIT.]) ]) I have no idea whether this is applicable to Alpha. -- System Information: Debian Release: wheezy/sid APT prefers unreleased APT policy: (500, 'unreleased'), (500, 'unstable') Architecture: alpha Kernel: Linux 3.2.0-rc2 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages pulseaudio depends on: ii adduser 3.113 ii consolekit 0.4.5-1 ii libasound2 1.0.24.1-4 ii libasound2-plugins 1.0.24-3 ii libc6.1 2.13-21 ii libcap2 1:2.22-1 ii libdbus-1-3 1.4.16-1 ii libfftw3-3 3.2.2-1 ii libice6 2:1.0.7-2 ii libltdl72.4.2-1 ii liborc-0.4-01:0.4.16-1 ii libpulse0 1.1-1 ii libsamplerate0 0.1.8-1 ii libsm6 2:1.2.0-2 ii libsndfile1 1.0.25-3 ii libspeexdsp11.2~rc1-1 ii libtdb1 1.2.9-4 ii libudev0172-1 ii libx11-62:1.4.4-4 ii libx11-xcb1 2:1.4.4-4 ii libxcb1 1.7-4 ii libxtst62:1.2.0-4 ii lsb-base3.2-28 ii udev172-1 Versions of packages pulseaudio recommends: ii gstreamer0.10-pulseaudio 0.10.30-2 ii pulseaudio-esound-compat 1.1-1 ii pulseaudio-module-x11 1.1-1 ii rtkit 0.10-2 Versions of packages pulseaudio suggests: ii paman none ii paprefs none ii pavucontrol none ii pavumeter none ii pulseaudio-utils 1.1-1 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#648994: qt4-x11: g++-4.4 optimizer broken on Alpha
Source: qt4-x11 Version: 4:4.7.3-8 Severity: important Tags: patch Dear Maintainer, Due to a bug in the g++-4.4 optimizer, the normal -O2 build of qt4-x11 binary packages results in segfaults on the alpha architecture when apps are run that use the qt4 libraries. This includes kdm and the KDE4 plasma-desktop at a minimum (bad behavior verified and easy to reproduce). A verified workaround is to build with -O0. Note that DEB_BUILD_OPTIONS=noopt is ignored by the QT build system: I ended up editing the appropriate files under mkspecs directly to test the workaround. Unknown whether use of gcc/g++-4.6 fixes the issue. -- System Information: Debian Release: wheezy/sid APT prefers unreleased APT policy: (500, 'unreleased'), (500, 'unstable') Architecture: alpha Kernel: Linux 3.2.0-rc1 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#648761: webkit: FTBFS on Alpha: arch missing from 01_double-conversion.patch
Source: webkit Version: 1.6.1-5 Severity: serious Tags: patch Justification: fails to build from source (but built successfully in the past) Dear Maintainer, This actually applies to 1.6.1-4 as well. The Alpha architecture passes the test mentioned in webkit-1.6.1/Source/JavaScriptCore/wtf/dtoa/utils.h, so a verified fix for the FTBFS condition is to simply append || CPU(ALPHA) to the system list in webkit-1.6.1/debian/patches/01_double-conversion.patch. The logfile for the last failed build: http://buildd.debian-ports.org/status/fetch.php?pkg=webkitarch=alphaver=1.6.1-5stamp=1320307055 -- System Information: Debian Release: wheezy/sid APT prefers unreleased APT policy: (500, 'unreleased'), (500, 'unstable') Architecture: alpha Kernel: Linux 3.1.0 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#556948: gnome-volume-control-applet: Connection failed, reconnecting...
Package: gnome-media Version: 2.28.1-1 Severity: normal My .xsession-errors file is full of lines like the following: ** (gnome-volume-control-applet:19774): WARNING **: Connection failed, reconnecting... If gnome-volume-control-applet is allowed to continue to run, say, overnight, the session eventually hangs due to some kind of resource exhaustion. At that point, a system reboot is required to restore graphical console access, because the keyboard and mouse are no longer seen even if the X11 session is killed and/or restarted. Killing the gnome-volume-control-applet process is a workaround. Other items of note: (1) The speaker icon in the tray disappeared shortly after a gnome package upgrade, probably due the connection failure noted above (although I didn't notice or look for the error messages until a long-running session hung and got my attention). With a freshly-started gnome session, after killing the non-functional gnome-volume-control-applet, I added an instance to the tray and it seems to work ok, i.e., I can pull up the mixer and everything works the way it is supposed to as far as I can tell. (2) /usr/share/gnome/autostart/gnome-volume-control-applet.desktop (presumably the instance that can't connect) has TryExec=/usr/bin/pulseaudio. The instance I added says it's using gstreamer. (3) Give the above two items, this report may be related to #541320. I have not tried reconfiguring my gnome session per the procedure noted there. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: alpha Kernel: Linux 2.6.32-rc7 Locale: LANG=C, LC_CTYPE=en_US (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages gnome-media depends on: ii gnome-media-common 2.28.1-1 GNOME media utilities - common fil ii gstreamer0.10-alsa [gs 0.10.25-6 GStreamer plugin for ALSA ii gstreamer0.10-esd [gst 0.10.16-5 GStreamer plugin for ESD ii gstreamer0.10-plugins- 0.10.16-1 GStreamer plugins from the bad s ii gstreamer0.10-plugins- 0.10.25-6 GStreamer plugins from the base ii gstreamer0.10-plugins- 0.10.16-5 GStreamer plugins from the good ii gstreamer0.10-pulseaud 0.10.16-5 GStreamer plugin for PulseAudio ii libatk1.0-01.28.0-1 The ATK accessibility toolkit ii libc6.12.10.1-7 GNU C Library: Shared libraries ii libcairo2 1.8.8-2 The Cairo 2D vector graphics libra ii libcanberra-gtk0 0.22-1Gtk+ helper for playing widget eve ii libcanberra0 0.22-1a simple abstract interface for pl ii libfontconfig1 2.6.0-4 generic font configuration library ii libfreetype6 2.3.11-1 FreeType 2 font engine, shared lib ii libgconf2-42.28.0-1 GNOME configuration database syste ii libglade2-01:2.6.4-1 library to load .glade files at ru ii libglib2.0-0 2.22.2-2 The GLib library of C routines ii libgnome-media02.28.1-1 runtime libraries for the GNOME me ii libgstreamer-plugins-b 0.10.25-6 GStreamer libraries from the base ii libgstreamer0.10-0 0.10.25-3 Core GStreamer libraries and eleme ii libgtk2.0-02.18.3-1 The GTK+ graphical user interface ii libpango1.0-0 1.26.0-1 Layout and rendering of internatio ii libpulse-mainloop-glib 0.9.20-1 PulseAudio client libraries (glib ii libpulse0 0.9.20-1 PulseAudio client libraries ii libunique-1.0-01.1.6-1 Library for writing single instanc ii libxml22.7.6.dfsg-1 GNOME XML library ii x11-utils 7.4+1 X11 utilities ii zlib1g 1:1.2.3.3.dfsg-15 compression library - runtime gnome-media recommends no packages. Versions of packages gnome-media suggests: ii pulseaudio0.9.20-1 PulseAudio sound server -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#548792: gnumeric: WARNING **: NULL sheet in gnm_sheet_get_size! and segfault
Package: gnumeric Version: 1.9.12-2 Severity: normal Me too, I guess. I haven't checked the original bug report, but the subject indicates I'm not the first to see this. Note that I'm on an Alpha, not x86. Doesn't matter whether gnumeric is invoked with a spreadsheet argument: I get the same error either way. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: alpha Kernel: Linux 2.6.31 Locale: LANG=C, LC_CTYPE=en_US (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages gnumeric depends on: ii debconf [debc 1.5.27 Debian configuration management sy ii gconf22.26.2-3 GNOME configuration database syste ii gnumeric-comm 1.9.12-2 spreadsheet application for GNOME ii gsfonts 1:8.11+urwcyr1.0.7~pre44-4 Fonts for the Ghostscript interpre ii libatk1.0-0 1.26.0-1 The ATK accessibility toolkit ii libc6.1 2.9-25 GNU C Library: Shared libraries ii libcairo2 1.8.8-2The Cairo 2D vector graphics libra ii libglade2-0 1:2.6.4-1 library to load .glade files at ru ii libglib2.0-0 2.22.0-1 The GLib library of C routines ii libgoffice-0- 0.7.13-1 Document centric objects library - ii libgsf-1-114 1.14.15-1 Structured File Library - runtime ii libgtk2.0-0 2.16.6-1 The GTK+ graphical user interface ii libpango1.0-0 1.24.5-1 Layout and rendering of internatio ii libxml2 2.7.4.dfsg-2 GNOME XML library ii procps1:3.2.8-1.1/proc file system utilities ii zlib1g1:1.2.3.3.dfsg-15 compression library - runtime Versions of packages gnumeric recommends: ii evince2.26.2-2 Document (postscript, pdf) viewer Versions of packages gnumeric suggests: ii epiphany-browser 2.26.3-2 Intuitive web browser - dummy pack pn gnumeric-doc none (no description available) pn gnumeric-plugins-extranone (no description available) ii ttf-liberation1.04.93-1 Free fonts with the same metrics a -- debconf information: gnumeric/existing-process: false -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#546675: another library issue with unstable version
I installed the updated gnumeric and gnumeric-common packages from unstable (which fixed the undefined symbol error), but am now getting gnumeric: /usr/lib/libxml2.so.2: no version information available (required by /usr/lib/libspreadsheet-1.9.12.so) This appears to be a warning, as gnumeric seems to function well otherwise. libxml2.so.2 -- libxml2.so.2.7.3 on my alpha. --Bob -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#546846: libspreadsheet-1.9.10.so: undefined symbol error
Package: gnumeric Version: 1.9.10-2 Severity: grave Justification: renders package unusable Invoking gnumeric generates an undefined symbol error for libspreadsheet-1.9.10.so: foo_canvas_item_request_update This error showed up after several squeeze updates were applied over the weekend. Relevant package information as automatically included by reportbug below... -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: alpha Kernel: Linux 2.6.31 Locale: LANG=C, LC_CTYPE=en_US (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages gnumeric depends on: ii debconf [debc 1.5.27 Debian configuration management sy ii gconf22.26.2-3 GNOME configuration database syste ii gnumeric-comm 1.9.10-2 spreadsheet application for GNOME ii gsfonts 1:8.11+urwcyr1.0.7~pre44-4 Fonts for the Ghostscript interpre ii libatk1.0-0 1.26.0-1 The ATK accessibility toolkit ii libc6.1 2.9-25 GNU C Library: Shared libraries ii libcairo2 1.8.8-2The Cairo 2D vector graphics libra ii libglade2-0 1:2.6.4-1 library to load .glade files at ru ii libglib2.0-0 2.20.5-1 The GLib library of C routines ii libgoffice-0- 0.7.12-1 Document centric objects library - ii libgsf-1-114 1.14.15-1 Structured File Library - runtime ii libgtk2.0-0 2.16.6-1 The GTK+ graphical user interface ii libpango1.0-0 1.24.5-1 Layout and rendering of internatio ii libxml2 2.7.3.dfsg-2.1 GNOME XML library ii procps1:3.2.8-1 /proc file system utilities ii zlib1g1:1.2.3.3.dfsg-15 compression library - runtime Versions of packages gnumeric recommends: ii evince2.26.2-2 Document (postscript, pdf) viewer Versions of packages gnumeric suggests: ii epiphany-browser 2.26.3-2 Intuitive web browser - dummy pack pn gnumeric-doc none (no description available) pn gnumeric-plugins-extranone (no description available) ii ttf-liberation1.04.93-1 Free fonts with the same metrics a -- debconf information: gnumeric/existing-process: false -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#541402: alpha: plasma segfault on kde4 startup
ACK on the below indicated packages. I won't have any free time to devote to this until this coming Thursday, but I *will* do what I can to help. Thanks! --Bob On Mon, Aug 31, 2009 at 12:55:35AM +0200, Sune Vuorela wrote: tag 541402 +help thanks On Thursday 13 August 2009 23:24:38 Bob Tracy wrote: Package: kdebase-workspace-bin Version: 4:4.2.4-1 Severity: grave Justification: renders package unusable Hi Currently, the debian-qt-kde team is out of alpha machines, so we kind of need help from the alpha people. This backtrace appears to be of no use. And it is. PLease install at least kdebase-workspace-bin and kde4libs-dbg and try again. We do probably need someone of the alpha people to do some actual debugging here. /Sune -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#541402: alpha: plasma segfault on kde4 startup
Package: kdebase-workspace-bin Version: 4:4.2.4-1 Severity: grave Justification: renders package unusable Since the upgrade from KDE3 to KDE4 on the Alpha platform, KDE has been unusable. /usr/bin/plasma consistently segfaults on startup. This may or may not be related to #519518: the reporter was using an i686 platform. The following diagnostic output was captured (was not given the opportunity to save it directly -- save button grayed-out): This backtrace appears to be of no use. This is probably because your packages are built in a way which prevents creation of proper backtraces, or the stack frame was seriously corrupted in the crash. (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0x20004bad580 (LWP 9690)] 0x021bd638 in nanosleep () from /lib/libc.so.6.1 [Current thread is 0 (process 9690)] Thread 1 (Thread 0x20004bad580 (LWP 9690)): #0 0x021bd638 in nanosleep () from /lib/libc.so.6.1 #1 0x021bd428 in sleep () from /lib/libc.so.6.1 #2 0x02bbef60 in ?? () from /usr/lib/libkdeui.so.5 #3 0x02bbfedc in KCrash::defaultCrashHandler () from /usr/lib/libkdeui.so.5 #4 0x02140db0 in ?? () from /lib/libc.so.6.1 #5 0x0200020c6e80 in ?? () from /usr/lib/libQtCore.so.4 #6 0x0200020c8508 in QObject::QObject () from /usr/lib/libQtCore.so.4 #7 0x020001316cb8 in QAction::QAction () from /usr/lib/libQtGui.so.4 #8 0x0200013a916c in QWidgetAction::QWidgetAction () from /usr/lib/libQtGui.so.4 #9 0x020001ba33f8 in ?? () from /usr/lib/libQtGui.so.4 #10 0x020001ba61a8 in ?? () from /usr/lib/libQtGui.so.4 #11 0x020001ba6de4 in ?? () from /usr/lib/libQtGui.so.4 #12 0x020001b90898 in QGraphicsLinearLayout::sizeHint () from /usr/lib/libQtGui.so.4 #13 0x020001b8e88c in ?? () from /usr/lib/libQtGui.so.4 #14 0x020001b8ef80 in QGraphicsLayoutItem::effectiveSizeHint () from /usr/lib/libQtGui.so.4 #15 0x020001b940f8 in QGraphicsWidget::sizeHint () from /usr/lib/libQtGui.so.4 #16 0x020001b8e88c in ?? () from /usr/lib/libQtGui.so.4 #17 0x020001b8ef80 in QGraphicsLayoutItem::effectiveSizeHint () from /usr/lib/libQtGui.so.4 #18 0x020001b96bc0 in QGraphicsWidget::setGeometry () from /usr/lib/libQtGui.so.4 #19 0x020015cf16c8 in ?? () from /usr/lib/kde4/plasma_applet_systemtray.so #20 0x020001b939f4 in QGraphicsWidget::resize () from /usr/lib/libQtGui.so.4 #21 0x020001b94690 in QGraphicsWidget::updateGeometry () from /usr/lib/libQtGui.so.4 #22 0x020001b8fc24 in QGraphicsLayoutItem::setMinimumSize () from /usr/lib/libQtGui.so.4 #23 0x0233f37c in Plasma::Applet::setBackgroundHints () from /usr/lib/libplasma.so.3 #24 0x020015cf41c8 in ?? () from /usr/lib/kde4/plasma_applet_systemtray.so #25 0x020015cf56cc in KPluginFactory::createInstanceSystemTray::Applet, QObject () from /usr/lib/kde4/plasma_applet_systemtray.so #26 0x02000109eab0 in KPluginFactory::create () from /usr/lib/libkdecore.so.5 #27 0x0234a8c8 in Plasma::Applet::load () from /usr/lib/libplasma.so.3 #28 0x0208d5e0 in ?? () from /usr/lib/libkdeinit4_plasma.so #29 0x0208fb38 in ?? () from /usr/lib/libkdeinit4_plasma.so #30 0x0236f110 in Plasma::Corona::initializeLayout () from /usr/lib/libplasma.so.3 #31 0x020b141c in ?? () from /usr/lib/libkdeinit4_plasma.so #32 0x020b1e00 in ?? () from /usr/lib/libkdeinit4_plasma.so #33 0x020b6e78 in ?? () from /usr/lib/libkdeinit4_plasma.so #34 0x0200020d0d64 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #35 0x0200020d1f78 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #36 0x0200020d9db8 in ?? () from /usr/lib/libQtCore.so.4 #37 0x0200020d9f30 in ?? () from /usr/lib/libQtCore.so.4 #38 0x0200020c925c in QObject::event () from /usr/lib/libQtCore.so.4 #39
Bug#492488: Reproduction of the Iceweasel crashes.
On Sun, Oct 26, 2008 at 12:26:52PM +1300, Michael Cree wrote: I've CCed this to Bob Tracy since he has done quite a bit of work trying to track down the problem,, that is reported in the debian-alpha mail list. He may wish to comment further. Bob compiled vanilla 3.0.3 firefox sources, and I compiled 3.0.3-g1 icecat sources for testing (mainly because iceweasel was still back at 3.0.1 at the time). These also crash. For me the symptom is that the browser window opens on the screen and then immediately disappears again with the crash. That is the symptom I'm seeing as well. Significantly, this occurs both with Iceweasel and with firefox executables built from the vanilla firefox-3.x sources. The main browser window with two tabs appears: the two tabs correspond to the you've upgraded web page and the normal home page. As soon as the two pages start to load, the browser crashes with a segfault. For a vanilla firefox-3.0.3 build, disabling optimization took care of the segfaults, while adding -Wl,--no-relax to DSO_LDOPTS allowed libxul.so to be built. The build process was aborting during the final link-edit of libxul.so with GPREL16 relocation errors, and a 2007 bugzilla report I found implicated the relax code in binutils. The same workarounds allow firefox-3.1b1 to build and work properly. My alpha is a PWS 433au (miata), currently running a kernel.org 2.6.27 kernel. gcc/g++ is version 4.2.4-3, and binutils is version 2.18.0.20080103. -- Bob Tracy | I was a beta tester for dirt. They never did [EMAIL PROTECTED] | get all the bugs out. - Steve McGrew on /. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#503164: more complete list of missing items
As best I can determine, here's what's missing from the binary .deb: /usr/bin/cacao /usr/lib/cacao/* /usr/share/cacao/* /usr/share/man/man1/cacao.1.gz. At least the first two components, and probably the third, are necessary to allow gcjwebplugin to run. I retrieved the Debian source package and attempted to roll my own. The resulting binary package was missing the same components noted above, but they were found in package_dir/debian/tmp following the build. After copying those files to the proper locations, everything seems to work ok within the limits of the tests I can run. -- Bob Tracy | I was a beta tester for dirt. They never did [EMAIL PROTECTED] | get all the bugs out. - Steve McGrew on /. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#503051: gcc-4.2: optimizer produces code that segfaults on Alpha
Package: gcc-4.2 Version: 4.2.4-3 Severity: important firefox-3.0.3 builds from the mozilla.org source tree using gcc/g++-4.2.4 with optimization enabled result in an executable that segfaults on invocation. Adding ac_add_options --disable-optimize to the .mozconfig file and rebuilding produces an executable that behaves properly. Similar bug reports have been filed against the compiler optimizer for other application builds on 64-bit architectures. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: alpha Kernel: Linux 2.6.27 Locale: LANG=C, LC_CTYPE=en_US (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages gcc-4.2 depends on: ii binutils2.18.1~cvs20080103-7 The GNU assembler, linker and bina ii cpp-4.2 4.2.4-3 The GNU C preprocessor ii gcc-4.2-base4.2.4-3 The GNU Compiler Collection (base ii libc6.1 2.7-14 GNU C Library: Shared libraries ii libgcc1 1:4.3.2-1GCC support library Versions of packages gcc-4.2 recommends: ii libc6.1-dev 2.7-14 GNU C Library: Development Librari Versions of packages gcc-4.2 suggests: pn gcc-4.2-doc none (no description available) pn gcc-4.2-locales none (no description available) pn libgcc1-dbg none (no description available) pn libgomp1-dbg none (no description available) pn libmudflap0-4.2-dev none (no description available) pn libmudflap0-dbg none (no description available) -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#503052: binutils: ld default relax option causes relocation errors on Alpha
Package: binutils Version: 2.18.1~cvs20080103-7 Severity: important Attempts to build firefox-3.0.3 from the mozilla.org source tree fail with GPREL16 relocation errors on the Alpha at the point where libxul.so is built. Adding -Wl,--no-relax to DSO_LDOPTS results in a successful build. This bug has been reported elsewhere in different contexts, and has existed since at least version 2.17 back in 2007. It has been suggested in various forums that the relax option is unreliable and should not be enabled by default. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: alpha Kernel: Linux 2.6.27 Locale: LANG=C, LC_CTYPE=en_US (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages binutils depends on: ii libc6.1 2.7-14 GNU C Library: Shared libraries binutils recommends no packages. Versions of packages binutils suggests: pn binutils-doc none (no description available) -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#503164: /usr/bin/cacao not included in alpha package
Package: cacao Version: 0.99.4~20081012-2 Severity: grave Justification: renders package unusable Packaging error: many files missing from alpha architecture version of the .deb file. /usr/bin/cacao is an obvious omission. The included man pages are symbolic links to non-existent files. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: alpha Kernel: Linux 2.6.27 Locale: LANG=C, LC_CTYPE=en_US (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages cacao depends on: ii classpath 2:0.97.2-1 clean room standard Java libraries ii classpath-common 2:0.97.2-1 clean room standard Java libraries cacao recommends no packages. cacao suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#456205: radvd: unaligned traps on Alpha platform
Package: radvd Version: 1:1.0-1 Severity: normal Running radvd on an Alpha PWS 433au causes alignment traps with error messages appearing on both the console and in syslog. The reported address is consistent, and I was able to track down the cause. The workaround below is not a proper fix, but will serve to illustrate the problem. The trap occurs in the vicinity of line 299 in send.c:send_ra(): cmsg-cmsg_len = CMSG_LEN(sizeof(struct in6_pktinfo)); and the workaround on the Alpha is to force 8-byte alignment (sizeof(size_t), which is the size of the cmsg_len structure member) where chdr is declared near the beginning of send_ra(): /* char chdr[CMSG_SPACE(sizeof(struct in6_pktinfo))]; */ char __attribute__((aligned(8))) chdr[CMSG_SPACE(sizeof(struct in6_pktinfo))]; Note that it's possible this is really a compiler quirk of some kind, because a quick reading of the CMSG_SPACE() macro implies that some attention is being paid to possible alignment issues. Compiler version locally is gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21). -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: alpha Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.24-rc5 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages radvd depends on: ii adduser 3.102 Add and remove users and groups ii libc6.1 2.6-2 GNU C Library: Shared libraries radvd recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#439733: gnumeric: abort on startup: Failed to generate NaN.
Package: gnumeric Version: 1.6.3-5 Severity: important gnumeric aborts on startup since upgrading libc6.1 package on Alpha PWS 433au. Error message is Failed to generate NaN, which comes from libgoffice. -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: alpha Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.23-rc3 Locale: LANG=C, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages gnumeric depends on: ii debconf [debc 1.5.11 Debian configuration management sy ii gconf22.16.1-1 GNOME configuration database syste ii gnumeric-comm 1.6.3-5common files for Gnumeric, the GNO ii gsfonts 1:8.11+urwcyr1.0.7~pre41-1 Fonts for the Ghostscript interpre ii libart-2.0-2 2.3.17-1 Library of functions for 2D graphi ii libatk1.0-0 1.12.4-3 The ATK accessibility toolkit ii libbonobo2-0 2.14.0-3 Bonobo CORBA interfaces library ii libbonoboui2- 2.14.0-5 The Bonobo UI library ii libc6.1 2.6-2 GNU C Library: Shared libraries ii libcairo2 1.2.4-4The Cairo 2D vector graphics libra ii libfontconfig 2.4.2-1.2 generic font configuration library ii libgconf2-4 2.16.1-1 GNOME configuration database syste ii libglade2-0 1:2.6.0-4 library to load .glade files at ru ii libglib2.0-0 2.12.4-2 The GLib library of C routines ii libgnome-keyr 0.6.0-3GNOME keyring services library ii libgnome2-0 2.16.0-2 The GNOME 2 library - runtime file ii libgnomecanva 2.14.0-2 A powerful object-oriented display ii libgnomeprint 2.12.1-7 The GNOME 2.2 print architecture - ii libgnomeprint 2.12.1-4 GNOME 2.2 print architecture User ii libgnomeui-0 2.14.1-2 The GNOME 2 libraries (User Interf ii libgnomevfs2- 1:2.14.2-7 GNOME virtual file-system (runtime ii libgoffice-1- 0.2.1-4Document centric objects library - ii libgsf-1-114 1.14.3-1 Structured File Library - runtime ii libgsf-gnome- 1.14.3-1 Structured File Library - runtime ii libgtk2.0-0 2.8.20-7 The GTK+ graphical user interface ii libice6 1:1.0.1-2 X11 Inter-Client Exchange library ii liborbit2 1:2.14.3-0.2 libraries for ORBit2 - a CORBA ORB ii libpango1.0-0 1.14.8-5 Layout and rendering of internatio ii libpopt0 1.10-3 lib for parsing cmdline parameters ii libsm61:1.0.1-3 X11 Session Management library ii libx11-6 2:1.0.3-7 X11 client-side library ii libxcursor1 1.1.7-4X cursor management library ii libxext6 1:1.0.1-2 X11 miscellaneous extension librar ii libxfixes31:4.0.1-5 X11 miscellaneous 'fixes' extensio ii libxi61:1.0.1-4 X11 Input extension library ii libxinerama1 1:1.0.1-4.1X11 Xinerama extension library ii libxml2 2.6.27.dfsg-1 GNOME XML library ii libxrandr22:1.1.0.2-5X11 RandR extension library ii libxrender1 1:0.9.1-3 X Rendering Extension client libra ii zlib1g1:1.2.3-13 compression library - runtime gnumeric recommends no packages. -- debconf information: gnumeric/existing-process: false -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#438431: aboot will not load 2.6.23-rc1 and later kernels
Package: aboot Version: 0.9b-3 Severity: important Richard Henderson reports in a linux-kernel posting dated 14 Aug 2007: Recent build changes have added a PT_NOTE entry to the kernel's ELF header. A perfectly valid change, but Alpha's aboot loader is none too bright about examining these headers. The same posting (http://lkml.org/lkml/2007/8/14/259) includes a patch against aboot-1.0_pre20040408 (available at SourceForge). Note that lib/isolib.c still requires a patch to replace #include linux/config.h with #include linux/autoconf.h for use with 2.6.X kernels. The severity level is actually critical if a kernel more recent than 2.6.22 is required, but the current aboot package works fine for everything = 2.6.22. -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: alpha Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.22 Locale: LANG=C, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages aboot depends on: ii aboot-base0.9b-3 base files required for bootable m ii libc6.1 2.6-2 GNU C Library: Shared libraries aboot recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#368863: hald generates unaligned trap errors on Alpha
Sjoerd Simons wrote: Unfortunately I don't have an alpha lying around, so i can't reproduce this :). Afaik an unaligned trap doesn't do any harm, it's just a performance hit. That's pretty much my observation as well: no real harm being done that I can tell, just the warning messages that aren't really flagged as such. I can fix this for you, but i need you to pinpoint what exactly causes these traps. Which requires some debugging on your part. I confess to being not much good with a debugger, but I do just fine with diagnostic printf()'s (assuming the compiler doesn't help too much by moving things around). I'll retrieve a copy of the source package and start playing around with it. If I find out anything useful, I'll let you know. On the assumption (most certainly valid) that you know more about this than I do, what am I looking for? Suboptimally chosen pointer/variable sizes? Weird structure layouts? Questionable (implicit) typecasts? Thanks for your help!! -- --- Bob Tracy WTO + WIPO = DMCA? http://www.anti-dmca.org [EMAIL PROTECTED] --- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#368863: hald generates unaligned trap errors on Alpha
Package: hal Version: 0.5.7-1 At boot time, and whenever I load/unload a hardware module, hald generates unaligned trap error messages on my Alpha system. For the boot time case, here is the corresponding syslog output with a few lines on each side of the error for context: ... May 24 08:07:45 smirkin kernel: parport0: PC-style at 0x3bc [PCSPP,TRISTATE] May 24 08:07:45 smirkin kernel: lp0: using parport0 (polling). May 24 08:07:45 smirkin kernel: eth0: no IPv6 routers present May 24 08:07:49 smirkin kernel: hald-runner(2760): unaligned trap at 021ca7bc: 00011f57d8d1 28 4 May 24 08:07:49 smirkin kernel: hald-runner(2760): unaligned trap at 021ca7e0: 00011f57d8d1 2c 1 May 24 08:07:49 smirkin kernel: hald-runner(2760): unaligned trap at 021ca7bc: 00011f57d8d1 28 4 May 24 08:07:49 smirkin kernel: hald-runner(2760): unaligned trap at 021ca7e0: 00011f57d8d1 2c 1 May 24 08:07:54 smirkin kernel: NET: Registered protocol family 5 May 24 08:07:54 smirkin atalkd[2852]: restart (2.0.3) ... uname -a: Linux smirkin 2.6.17-rc4 #1 Mon May 15 11:28:37 CDT 2006 alpha GNU/Linux C library: libc6.1 package version 2.3.6-7 System: 433au (miata) -- --- Bob Tracy WTO + WIPO = DMCA? http://www.anti-dmca.org [EMAIL PROTECTED] --- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#344328: installation-reports: Debian Sarge installation on Alpha (PWS 433au)
Package: installation-reports Severity: normal INSTALL REPORT Debian-installer-version: http://cdimage.debian.org/debian-cd/3.1_r0a/alpha/bt-cd/ downloaded in Sept. 2005. uname -a: Linux smirkin 2.4.27-2-generic #1 Tue Nov 22 17:12:59 UTC 2005 alpha GNU/Linux Date: 18 Dec 2005, 18:00 CST Method: booted and installed from CD set Machine: DEC Personal Workstation 433au Processor: Alpha EV56, var. 7, rev. 0 Memory: 576 MB (six slots: 2x64, 4x128) Root Device: SCSI - Model: RZ1CC-BA (C) DEC Rev: 883F at ID 0 Root Size/partition table: Disk /dev/sda: 4290 MB, 4290600960 bytes 255 heads, 63 sectors/track, 521 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes 8 partitions: # start end size fstype [fsize bsize cpg] a:1*1*0* ext2 b:1* 10*9* ext2 /boot c: 10* 41* 30* ext2 / d: 41* 72* 31* swap e: 72* 193* 121* ext2 /tmp f: 193* 376* 182* ext2 /var g: 376* 522* 146* ext2 /home Disk /dev/sdb: 18.2 GB, 18210037760 bytes 255 heads, 63 sectors/track, 2213 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes 3 partitions: # start end size fstype [fsize bsize cpg] a:1* 1241* 1240* ext2 /usr b: 1241* 2214* 973* ext2 /opt Output of lspci and lspci -n: :00:03.0 Ethernet controller: Digital Equipment Corporation DECchip 21142/43 (rev 30) :00:04.0 IDE interface: Silicon Image, Inc. (formerly CMD Technology Inc) PCI0646 (rev 01) :00:07.0 Non-VGA unclassified device: Intel Corp. 82378ZB/IB, 82379AB (SIO, SIO.A) PCI to ISA Bridge (rev 43) :00:0c.0 VGA compatible controller: Digital Equipment Corporation PBXGB [TGA2] (rev 22) :00:14.0 PCI bridge: Digital Equipment Corporation DECchip 21152 (rev 02) :01:09.0 SCSI storage controller: QLogic Corp. ISP1020 Fast-wide SCSI (rev 05) :00:03.0 0200: 1011:0019 (rev 30) :00:04.0 0101: 1095:0646 (rev 01) :00:07.0 : 8086:0484 (rev 43) :00:0c.0 0300: 1011:000d (rev 22) :00:14.0 0604: 1011:0024 (rev 02) :01:09.0 0100: 1077:1020 (rev 05) Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot worked:[O] Configure network HW: [O] Config network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Create file systems:[O] Mount partitions: [O] Install base system:[O] Install boot loader:[O] Reboot: [E] Comments/Problems: First reboot following base system install failed because SRM attempted to boot from previous boot device by default (the CD-ROM drive). Was able to interrupt SRM boot (cntl-C) and perform default boot from first hard disk, after which everything went smoothly. Partitioning process was OK, but cumbersome. Although the needed information is probably in the release notes and/or installation manual, it would have been useful to have the partitioning application provide minimum and suggested partition sizes based on configured mount points. Since this was my first Debian installation, I assumed Debian couldn't possibly be any more bloated than RedHat/Fedora and/or Mandriva, and everything worked out fine :-). With the benefit of hindsight, I would have made my / partition slightly bigger so as to support additional kernel module directories and such in /lib. Installation process should suggest far more strongly that people use the task-based package selection process. Aptitude's interface is hardly intuitive, and there should be a way to back up and correct the mistake of thinking selecting individual packages is the way to go. Having made that mistake, hitting ctlaltdel was the closest thing to a soft recovery I could have hoped for: the machine rebooted and the installation continued at the appropriate point. Instructions at bottom of template on how to submit installation report resulted in report going to Debian's junk in-box. Now trying reportbug. -- System Information: Debian Release: 3.1 Architecture: alpha Kernel: Linux 2.4.27-2-generic Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#344328: installation-reports: Debian Sarge installation on Alpha (PWS 433au)
Frans Pop wrote: Hmm, didn't you use the guided partitioning feature. This should set sane default sizes for different partitioning schemes [1] The guided partitioning feature completely ignored the second hard disk other than to acknowledge its existence :-). The primary drive is only 4 GB (sheesh... I remember when I would have *killed* for a drive that size), which makes for a very cramped environment for other than fairly basic installations. To be fair, the suggested partitions and corresponding sizes were pretty close to optimal if I had been limited to that one drive. Also to be fair, I haven't seen an installation partitioning program that actively encourages the use of other than the primary hard disk for required partitions (e.g., /usr if everything isn't in /) since working with ATT 3B2 computers back in the '80's. Thanks for your installation report. T'was an enjoyable experience. Debian appeared to be the best- supported option as far as Linux on Alpha, and I'd say appearances were *not* deceiving :-). That's not to slam other distros, but rather, to confirm that Debian has its act together. -- --- Bob Tracy WTO + WIPO = DMCA? http://www.anti-dmca.org [EMAIL PROTECTED] --- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
