Bug#1004255: linux-image-5.14.0-1-sparc64-smp: Debian kernels > 5.14.3-1~exp1 fail to boot on SPARC T4-1 with Fast Data Access MMU Miss

Package: src:linux Version: 5.14.6-2 Severity: important X-Debbugs-Cc: debian-sparc@lists.debian.org Dear Maintainer, Debian kernels > 5.14.3-1~exp1 consistently fail to boot on SPARC T4-1: SPARC T4-1, No Keyboard Copyright (c) 1998, 2014, Oracle and/or its affiliates. All rights reserved.

Bug#956624: qemu: FTBFS on sparc64 due to libseccomp-dev dependency

Source: qemu Severity: normal User: debian-sparc@lists.debian.org Usertags: sparc64 Hello, Commit 63f51933 resolved bug #900055 by enabling seccomp on linux-any. Since version 1:2.12+dfsg-2 qemu FTBFS due to this dependency, while it was building successfully before:

RE: Stretch bootstrap for sparc64 and sparc, optimized for ultrasparc3

Hello Adrian, On Thu, Sep 7, 2017, at 07:22 PM, John Paul Adrian Glaubitz wrote: > We are actually planning on implementing Britney for Debian Ports which > means that Debian Ports would also get a testing release. That would be great! > You can just easily cross-compile a native gcc compiler

Stretch bootstrap for sparc64 and sparc, optimized for ultrasparc3

Hi, On Thu, Sep 7, 2017, at 11:19 AM, John Paul Adrian Glaubitz wrote: > On 09/07/2017 10:30 AM, Tom Turelinckx wrote: >> Not all of those may be necessary anymore, but I've been doing it like >> that since squeeze and up to the current sid on dozens of machines, and >> it

Re: Re: mdadm /boot mirror and sun disklabel corruption

Hi Fedor, > For example I make partitions on two disks like the following: > > 1. 500MB for /boot - boot partition > 2. 2GB for swap - swap > 3. Whole disk - sun's whole disk > 4. 31,6GB for / - rest for the root fs > > Then I create metadevices (mirrors) for partitions 1,2 and 4. I'm using a

Re: sparc64 as a release architecture

Hello Adrian, Meanwhile, we have been testing the current sparc64 port on several development machines, both sun4v and sun4u, and the results are really quite promising: the major packages which we're using are all there, they are functional and up-to-date, and on identical hardware, performance

sparc64 as a release architecture

Hi, Now that Stretch has been released as Stable, and Buster has become Testing, what is the planning for turning sparc64 into a release architecture rather than a ports architecture? Thanks, Tom

Re: Debian Sparc 7.10.0 Install Problems

> on a V210, with gui which is stable. Problem is that none of the > repositories for Squeeze work any more and it's not clear if they > are available somewhere else, or have just been deleted ?. Squeeze has been moved to the debian archive. This sources.list snippet should work: deb