We had a horrific electrical storm on the 28th, and a lightning strike
took out my home air-conditioning units, my cable modem, my Wifi router,
a 16-port switch, my Ooma Telo, my main computer, my printer, and... my
PWS-433au :-(.
The Alpha isn't worth repairing, and I'm not going to go to the tr
On Mon, Apr 25, 2022 at 10:26:46AM +0100, John Garry wrote:
> Please try v5.18-rc2 as it should have a fix in commit eaba83b5b850
Up and running on v5.18-rc5 as I type this. Fix confirmed. Thanks!
--Bob
(Adding linux-scsi and linux-kernel, now that bisection is complete.)
On Wed, Apr 06, 2022 at 05:44:01PM -0500, Bob Tracy wrote:
> v5.17-rc2 ok. v5.17-rc3 I get the disk sector errors and hang that I
> reported in the first message in this thread.
This is on an Alpha Miata platform (PWS
On Wed, Apr 06, 2022 at 05:44:01PM -0500, Bob Tracy wrote:
> v5.17-rc2 ok. v5.17-rc3 I get the disk sector errors and hang that I
> reported in the first message in this thread.
>
> I'm going to try a native build of '-rc3' just to rule out any
> cross-comp
On Tue, Apr 05, 2022 at 08:22:48PM +0200, Helge Deller wrote:
> You don't need to enable it, but for alpha it's probably beneficial to enable
> it.
> When enabled, you will see a big speed improvement when logging in to a
> graphics text
> console and printing info. E.g. try "time dmesg" with an
On Tue, Apr 05, 2022 at 05:01:25PM +1200, Michael Cree wrote:
> On Mon, Apr 04, 2022 at 08:42:38PM -0500, Bob Tracy wrote:
> > On Sun, Mar 27, 2022 at 11:21:57AM +1300, Michael Cree wrote:
> > > On Thu, Mar 24, 2022 at 09:54:15PM -0500, Bob Tracy wrote:
> > > > W
On Sun, Mar 27, 2022 at 11:21:57AM +1300, Michael Cree wrote:
> On Thu, Mar 24, 2022 at 09:54:15PM -0500, Bob Tracy wrote:
> > When I attempt to boot a 5.17.0 kernel built from the kernel.org
> > sources, I see disk sector errors on my "sda" device, and the boot
>
When I attempt to boot a 5.17.0 kernel built from the kernel.org
sources, I see disk sector errors on my "sda" device, and the boot
process hangs at the point where "systemd-udevd.service" starts.
Rebooting on 5.16.0 works with no disk I/O errors of any kind.
Assuming the 5.17.0 kernel or its ass
On Mon, Sep 06, 2021 at 11:00:27AM +1200, Michael Cree wrote:
> I had intended to assist in testing with real hardware but there
> are other issues due to the 5.10 kernel on Alpha that need fixing
> first and I am working on that. I am hoping to come back to this
> and can run some tests in the ne
k properly alongside all the user space changes in "sid" that
have happened since late last year.
Respectfully,
--Bob
On Fri, Jun 04, 2021 at 12:37:14AM -0500, Bob Tracy wrote:
> On Fri, Jun 04, 2021 at 12:18:58AM -0500, Bob Tracy wrote:
> > On Thu, Jun 03, 2021 at 03:15:05PM +
On Fri, Jun 04, 2021 at 12:18:58AM -0500, Bob Tracy wrote:
> On Thu, Jun 03, 2021 at 03:15:05PM +0200, Maciej W. Rozycki wrote:
> > I have lost track about this issue, so please fill me in as to whether
> > the offending commit causing the regression has been bisected or n
On Thu, Jun 03, 2021 at 03:15:05PM +0200, Maciej W. Rozycki wrote:
> I have lost track about this issue, so please fill me in as to whether
> the offending commit causing the regression has been bisected or not.
It has. Michael Cree reported the following back on April 5th:
And the first bad c
On Tue, Apr 06, 2021 at 12:19:29PM +0200, John Paul Adrian Glaubitz wrote:
> We're also supporting everything else that most commercial vendors consider
> obsolete
> such as PA-RISC, M68k, big-endian PowerPC (32 and 64 bits) SPARC and so on,
> in case
> you need testing there.
(Mostly including
On Wed, Mar 31, 2021 at 11:04:42AM +0200, Maciej W. Rozycki wrote:
> I think the only feasible way of determining what has happened here is
> that you track the offending change down by bisecting the upstream kernel
> repository with `git bisect'.
That would normally be what I would do, and it
On Wed, Mar 24, 2021 at 09:48:46AM -0500, Bob Tracy wrote:
> (...)
> Everything worked as well as it's going to for kernel versions up
> through v5.10.0. When I boot on v5.11.0, "lightdm" starts, the screen
> goes blank as usual, I get a mouse pointer as usual, an
All,
First an apology for being "dark" for so long. There are still a few of
us out here using Alpha computers...
Another apology for the crappy "bug report" that follows, but first, a
little background information. I'm not in the habit of running X11 on
my PWS 433au these days, except for peri
On Sun, Apr 19, 2020 at 01:01:17AM +0200, Matthias Ferdinand wrote:
> On Sat, Apr 18, 2020 at 07:48:27AM -0500, Bob Tracy wrote:
> > > If the rules had changed, it should not succeed even without
> > > O_CREAT. A bug?
> >
> > That's *my* take on the matter
On Sat, Apr 18, 2020 at 12:25:11PM +0200, Matthias Ferdinand wrote:
> On Fri, Apr 17, 2020 at 02:17:46PM -0500, Bob Tracy wrote:
> > (directory sticky bit handling strangeness)
>
> it seems the difference lies in handling of O_CREAT.
>
> (...)
>
> not Alpha specif
All,
This likely isn't unique to Debian, much less the alpha platform, but
I first encountered this strangeness on my alpha running Debian unstable.
Best way to explain what I'm seeing is by example. A fairly common
thing to do is create temporary or download directories with octal mode
1777 tha
"apt-get upgrade" is failing on "cmake_3.16.3-1_alpha.deb" with the
following errors for the past day:
Get:1 http://ftp.ports.debian.org/debian-ports unstable/main alpha cmake alpha
3.16.3-1 [3,531 kB]
Err:1 http://ftp.ports.debian.org/debian-ports unstable/main alpha cmake alpha
3.16.3-1
File
On Sat, Jan 18, 2020 at 05:33:31PM +, Witold Baryluk wrote:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932381
At first glance, that certainly appears to be the issue. The
conversation seems to have stalled-out as of July 2019.
memcpy() looks to be a good way of handling the problem,
On my alpha, the system logs are getting spammed with unaligned trap
errors as follows:
[34656.586748] dbus-daemon(700): unaligned trap at 020a9720:
d68c7222 28 18
[34656.599443] dbus-daemon(700): unaligned trap at 020a9720:
d68c7222 28 18
[34656.612138] dbus-daem
Tried to install the latest libc6.1 this evening, and ran into an issue
with the "libcrypt1" installation. Specifically, "perl" is looking for
"libcrypt.so.1.1", and after the new "libcrypt1" package gets
installed, the following library and symlinks exist under
"/usr/lib/alpha-linux-gnu":
libcry
On Sat, Nov 30, 2019 at 05:51:45PM +0100, John Paul Adrian Glaubitz wrote:
> > On Nov 30, 2019, at 4:54 PM, Skye wrote:
> >
> > Bob, that is excellent information. Thank you for sharing!
>
> I suggest turning this into a patch. Fixing guile-2.0 and guile-2.2 on alpha
> is dearly needed, so p
On Sat, Nov 30, 2019 at 01:59:36PM +1300, Michael Cree wrote:
> (...) It passes more often than not and
> only fails occasionally. I see that there is a patch in the
> debian/patches directory to avoid a race condition in this test.
> But I don't know guile so don't understand the code.
There are
On Sat, Nov 30, 2019 at 12:10:28PM +1300, Michael Cree wrote:
> ERROR: 00-repl-server.test: repl-server: HTTP inter-protocol attack -
> arguments: ((system-error "fport_write" "~A" ("Broken pipe") (32)))
>
> Bob: how did you get past this test or did it pass on your build?
It passed on mine. I
(This is a separate copy to the list, just to keep everyone informed.
No attachment included.)
On Tue, Nov 26, 2019 at 04:49:15PM +1300, Michael Cree wrote:
> I don't seem to have received that message.
I'll try sending again just to you... The attached "packages" file was
on the order of 500k,
On Tue, Nov 26, 2019 at 12:00:59PM +1300, Michael Cree wrote:
> Did you build with latest toolchain? I suspect the issue has
> appeared with toolchain changes (hard to pin down when because there
> was quite a period in which a new version of guile-2.0 was not
> uploaded).
>
> And the bug (a segf
On Sat, Nov 23, 2019 at 07:36:11AM +1300, Michael Cree wrote:
> That's not going to help at the moment because vim is bd-uninstallable.
>
> The real problem is guile-2.0 and guile-2.2, both of which FTBFS, and
> are blocking the building of many other packages.
I downloaded the Debian source for
On Fri, Nov 22, 2019 at 11:23:10AM +0100, John Paul Adrian Glaubitz wrote:
> (...)
> The images for alpha and ia64 could have issues because of the missing
> vim package [3]. Someone needs to have a look at vim on these two
> architectures.
>
> (...)
> > [3] https://buildd.debian.org/status/packag
On Sat, Sep 28, 2019 at 04:15:17PM -0600, Skye wrote:
> Congrats! Can you tell us how you got to that point? I need to bring up a
> series of servers next week and dreading my ignorance. They are currently
> running an old release of Red Hat.
Short answer: up-to-date Debian "sid" (unstable) on
Seriously. I just experienced the first "flawless" boot of my Alpha in
over two years. All devices initialized and came up perfectly,
including in particular the network interfaces, the X11 graphical login
screen, all configured file systems, and even the hardware clock.
The latter has been an i
Using gcc 9.2 to build current 5.X kernel.org source trees, I'm seeing
several warnings like the following during the linking of "vmlinux.o":
WARNING: vmlinux.o(__ex_table+0x11d0): Section mismatch in reference from the
(unknown reference) (unknown) to the (unknown reference) .alphalib:(unknown)
On Thu, Sep 19, 2019 at 09:10:20AM +0200, John Paul Adrian Glaubitz wrote:
> (...)
> So, can you please type "ip a" and check what device name is actually assigned
> to your wired card and if it differs from "eth0", adjust your /etc/network/
> interfaces file?
>
> If your wired card is actually na
On Wed, Sep 18, 2019 at 11:46:06AM +0200, John Paul Adrian Glaubitz wrote:
> Your permanent bashing of systemd makes answering your mails stressful
> for me.
Adrian -- please accept my apology for my rantings... They contribute
nothing to the conversation, and as you note, irritate the very peopl
On Mon, Sep 16, 2019 at 09:38:55PM -0500, Bob Tracy wrote:
> I say "almost clean", because a recent update managed to break my
> resolver configuration: "/etc/resolv.conf" came up completely empty, in
> spite of "/etc/network/interfaces" having the requis
On Mon, Sep 09, 2019 at 10:49:25PM +0200, Aurelien Jarno wrote:
> > ...
> >
> > You are in emergency mode. After logging in, type "journalctl -xb" to view
> > system logs, "systemctl reboot" to reboot, "systemctl default" or "exit"
> > to boot into default mode.
> > Give root password for maintena
On Wed, Jul 17, 2019 at 01:45:21PM +, Witold Baryluk wrote:
> Hey John,
>
> > The gist is: A lot of projects don't test their code on systems with
> separate
> > /usr partitions anymore, so things get silently broken.
>
> I don't have separate /usr, just single / (ext4) partition, and just
>
On Wed, Jul 17, 2019 at 03:16:09PM +0200, Frank Scheiner wrote:
> To sum things up: what Adrian intends to do for Alpha - pre-include the
> firmware on the installer discs - seems to be the only way to get this
> problem fixed w/o manual intervention during installation.
Many other things to comme
On Thu, Jul 11, 2019 at 09:48:14PM +0900, John Blake wrote:
> (...)
> I have a DS10L 617mhz and I can't figure out which version is the best to
> attempt to install on it.?? I'd rather avoid things like this issue with
> systemd where they obviously haven't tried to actually test it on an alpha
> p
Greetings. It has been a while since I last checked in. Thought I'd
let the rest of the Alpha community know I'm still around :-).
I'm up and running on kernel version 5.2.0, built from the kernel.org
source tree as is my usual pattern. The previous kernel running on my
system was 5.1.0-rc7. B
I'm finally starting to get a bit of traction on Debian bug #919825, but
Michael Biebl would really like to see me testing with a Debian-provided
kernel instead of my hand-built kernel.org versions (now running 5.0.0).
I saw where Ben Hutchings grabbed the fix referenced here
(https://salsa.debian.
On Wed, Jan 30, 2019 at 04:42:23PM -0500, Alex Winbow wrote:
> I've heard word that /usr destined to be going away, but frankly I'm
> very
> surprised that multiple local filesystems is a rarity these days. The debian
> installer even creates these semi-automatically. It is seriously the cas
On Sun, Jan 27, 2019 at 12:25:52PM -0800, Alex Winbow wrote:
> I'm seeing this also, after installing using the Debian 8.0 installer
> and dist-upgrade'ing to unstable (using the SMP kernel trick to get past the
> GENERIC issue). My understanding is that it's not initramfs-tools that
> mounts all t
. As mentioned there, this patch applies cleanly to at least
all mainline kernel source trees >= version 4.18.
Further apologies for including the patch as an attachment, but I don't
trust my mailer not to impose unintended formatting.
--Bob
Signed-off-by: Bob Tracy
Tested-by: Bob Trac
July 30, 2018 I reported the following to linux-kernel, linux-alpha, etc.:
On an alpha system, got the following build error on the 4.18-rc7
mainline kernel source tree:
HOSTCC net/bpfilter/main.o
In file included from tools/include/uapi/asm/bitsperlong.h:17,
from /usr/include
On Sun, Jan 20, 2019 at 03:32:10PM +0100, John Paul Adrian Glaubitz wrote:
> Hello!
>
> I have created updated installation images for Debian Ports,
> please find the updated images below and test them [1].
>
> Feedback welcome.
>
> Adrian
>
> > [1] https://cdimage.debian.org/cdimage/ports/2019
On Fri, Jan 18, 2019 at 12:19:52AM +, Maciej W. Rozycki wrote:
> (much useful information set in the appropriate historical context)
Thank you for your thoughts.
The earlier reported problem with "/lib/systemd/systemd-udevd" evidently
requiring AF_UNIX socket support to be built-in rather tha
On Wed, Jan 16, 2019 at 01:10:14AM -0600, Bob Tracy wrote:
> (initramfs / systemd / udevd issue)
I think I may have this one painted into a corner...
CONFIG_UNIX (at least) needs to be "y" instead of "m". This is a
relatively new dependency.
For userland applications u
Gentlemen,
Figured it was past time for an update, now that I actually have the
Alpha back on-line and functioning in its pre-meltdown capacity as my
IPv6 router and Linux kernel git repository. The following narrative is
going to necessarily be somewhat long-winded, seeing as it's intended to
be
On Sun, Jan 06, 2019 at 02:46:54PM -0800, Matt Turner wrote:
> On Sun, Jan 6, 2019 at 2:31 PM Bob Tracy wrote:
> >
> > Has anyone reading this used a recent version of "fdisk" to create a BSD
> > disklabel and disk slices from scratch on an Alpha? If so, wo
Has anyone reading this used a recent version of "fdisk" to create a BSD
disklabel and disk slices from scratch on an Alpha? If so, would you
please describe the procedure in enough detail that relevant Linux
installation documentation could be updated? It would seem to be anything
*but* intuitiv
On Sat, Dec 08, 2018 at 07:41:15PM +0100, Frank Scheiner wrote:
> On 12/8/18 15:05, Bob Tracy wrote:
> > From the "image.squashfs" file on the Gentoo "install-alpha-minimal"
> > image, attached is "etc/kernels/kernel-config-alpha-4.14.65-gentoo"
On Sat, Dec 08, 2018 at 11:15:21AM +0100, Frank Scheiner wrote:
> Is this Gentoo generic installer kernel SMP capable? I believe these Gentoo
> kernels have the config included in the kernel image, so available as
> `/proc/config.gz` during runtime, I think.
>From the "image.squashfs" file on the
On Sat, Dec 08, 2018 at 10:06:25AM +1300, Michael Cree wrote:
> On Tue, Dec 04, 2018 at 05:38:51PM +0100, Frank Scheiner wrote:
> > As per [1] and our recent discussions the generic 4.x kernels seem to no
> > longer work on Alpha machines which also renders any installer images using
> > the generi
On Tue, Dec 04, 2018 at 07:37:13PM +0100, Frank Scheiner wrote:
> On 12/4/18 17:45, John Paul Adrian Glaubitz wrote:
> > > ## Patches ##
> > >
> > > 1.
> > > https://salsa.debian.org/frank-scheiner-guest/linux/commit/865cacfd7722b346629082ab3094b6ad93964095
> > >
> > > 2.
> > > https://salsa.de
On Sat, Nov 24, 2018 at 09:07:09AM +1300, Michael Cree wrote:
> On Fri, Nov 23, 2018 at 01:41:17PM -0600, Bob Tracy wrote:
> > Trying the 20181120 minimal installation CD fails due to the firmware
> > for the Qlogic ISP1020 (1040.bin) SCSI adapter not being present, either
> &g
Just a quick update, and hopefully there's a Gentoo advocate/developer
reading this...
Trying the 20181120 minimal installation CD fails due to the firmware
for the Qlogic ISP1020 (1040.bin) SCSI adapter not being present, either
as built-in to the kernel or as a standalone file. No firmware mean
On Wed, Nov 07, 2018 at 04:12:27PM +0100, John Paul Adrian Glaubitz wrote:
> I can unfortunately not build updated installer images for Alpha since I
> don't have an Alpha porterbox available where I can build the debian-installer
> package for Alpha.
>
> I do have two AlphaStation 233 sitting in
On Tue, Nov 06, 2018 at 01:36:45PM +0100, Frank Scheiner wrote:
> sorry, looks like I missed your mails to the debian-alpha list until now.
Not a problem. As a temporary workaround, I've got an "amd64" "testing"
distro loaded on a spare i5-based system. We have time to explore
options and possib
(Dyslexia-related failure on original copy to Michael)
On Fri, Nov 02, 2018 at 01:41:51PM -0500, Bob Tracy wrote:
> Quick background info: I'm having to do a "from scratch" install on my
> PWS 433au (miata) due to a SCSI disk failure.
>
> The Debian 9.0
Quick background info: I'm having to do a "from scratch" install on my
PWS 433au (miata) due to a SCSI disk failure.
The Debian 9.0 NETINST image (from
"http://cdimage.debian.org/cdimage/ports/9.0/alpha/iso-cd/";) seems to
boot ok from SRM (>>> b dka[device_spec]) and takes me to the usual
"aboot"
On Wed, Oct 24, 2018 at 09:46:29AM -0500, Bob Tracy wrote:
> Back in January of 2017, a patch set was created for the 4.9.0 kernel and
> *hopefully* sent upstream to address the subject issue.
> (...).
> Am currently attempting a native 4.19.0 build with an up-to-date debian
> "
Back in January of 2017, a patch set was created for the 4.9.0 kernel and
*hopefully* sent upstream to address the subject issue. The patch
implemented a workaround: defining a new "alphalib" section for all the
Alpha-specific library functions to be linked into the final vmlinux.
The patch was de
It had been an *extremely* long time since I dared try to run a graphical
console on my PWS 433au, so I screwed-up my courage and gave it a try...
"sddm" is extremely slow to initialize, and even slower to respond to
both keyboard and mouse input. Usually, this means something screwy
going on wit
On Wed, Oct 03, 2018 at 07:58:27AM +1300, Michael Cree wrote:
> Hope you don't mind me CCing the debian-alpha list as it would be good
> to get other eyes seeing the problems.
Not a problem. The second of the two issues you mention would seem to
be the long pole in the tent, as it were.
> There
On an alpha system, got the following build error on the 4.18-rc7
mainline kernel source tree:
HOSTCC net/bpfilter/main.o
In file included from tools/include/uapi/asm/bitsperlong.h:17,
from /usr/include/asm-generic/int-ll64.h:12,
from /usr/include/alpha-linux-g
Yes. Just in case you don't regularly check for updates to the Debian
"unstable/sid" distribution, the long wait for a modern version of
Firefox on the Alpha is over. For now...
No idea how much longer Michael and I can keep resurrecting Lazarus.
At some point in the near future, it will no long
On Tue, Jan 16, 2018 at 12:44:03PM -0600, Bob Tracy wrote:
> Pretty well called it :-(. One of the build dependencies for
> "qtwebengine-opensource-src" is a javascript optimizing compiler. I
> suspect it's time to abandon "akregator" on "alpha".
&quo
Following the buildd log chain, the hold-up seems to be build
dependencies that cannot be installed. At the base of the list of
dependencies is "qtwebengine-opensource-src" for which "alpha" is no
longer an architecture listed by the maintainer(s).
Here's the high-level dependency chain:
"akrega
On Tue, Jan 16, 2018 at 12:36:03PM -0600, Bob Tracy wrote:
> Following the buildd log chain, the hold-up seems to be build
> dependencies that cannot be installed. At the base of the list of
> dependencies is "qtwebengine-opensource-src" for which "alpha" is no
>
On Fri, Dec 01, 2017 at 06:22:50PM -0600, Bob Tracy wrote:
> On Sat, Dec 02, 2017 at 10:16:28AM +1300, Michael Cree wrote:
> > Just got a chance to try out 4.14 on an Alpha and look like firmware
> > for built-in drivers are being treated differently. I presume you
> > have
On Sat, Dec 02, 2017 at 10:16:28AM +1300, Michael Cree wrote:
> On Tue, Nov 28, 2017 at 11:49:55PM -0600, Bob Tracy wrote:
> > On Thu, Nov 23, 2017 at 11:10:10PM -0600, Bob Tracy wrote:
> > > Perhaps the subject isn't entirely accurate, but that's what seems to be
&g
Debian bug #883089 opened for this issue.
Assuming there's a 4.13 or later Debian kernel for alpha available and
anyone reading this is brave enough to try it, I'd be interested in
knowing if it boots properly. Without a "yes, it works" from someone,
I'm extremely reluctant to give it a try mysel
On Tue, Nov 28, 2017 at 11:49:55PM -0600, Bob Tracy wrote:
> (...)
>
> Upon trying to reboot on my 4.13 kernel, I discovered *it's* now broken
> as well, thanks to a recent udev update :-(. Now I get a bunch of
> timeouts for all the filesystems (including the swap part
On Thu, Nov 23, 2017 at 11:10:10PM -0600, Bob Tracy wrote:
> Perhaps the subject isn't entirely accurate, but that's what seems to be
> the case. After loading the initial ramdisk, the boot process stalls
> (loops indefinitely) with "mdadm" complaining about not be
Perhaps the subject isn't entirely accurate, but that's what seems to be
the case. After loading the initial ramdisk, the boot process stalls
(loops indefinitely) with "mdadm" complaining about not being able to scan
the disks defined in its configuration file, which is bone-stock. What
makes th
Yesterday, I thought what I wanted to do was the ".c" file equivalent of
the '.section .alphalib,"ax"' substitution we made to the ".S" files.
I'm getting a good kernel build with the following patch:
--CUT HERE--
--- linux/arch/alpha/lib/memcpy.c.orig 2016-10-20 01:11:37.0 -0500
On Sun, Sep 10, 2017 at 10:16:41PM -0500, Bob Tracy wrote:
> On Sun, Sep 10, 2017 at 07:59:40PM -0700, Matt Turner wrote:
> > On Sun, Sep 10, 2017 at 3:34 PM, Bob Tracy wrote:
> > > Here we go again :-(. Tool versions as follows:
> > > (...)
> > >
> > &
On Sun, Sep 10, 2017 at 07:59:40PM -0700, Matt Turner wrote:
> On Sun, Sep 10, 2017 at 3:34 PM, Bob Tracy wrote:
> > Here we go again :-(. Tool versions as follows:
> >
> > gcc version 7.2.0 (Debian 7.2.0-3)
> > GNU ld (GNU Binutils for Debian) 2.29 (binutils 2.29-9)
&
Here we go again :-(. Tool versions as follows:
gcc version 7.2.0 (Debian 7.2.0-3)
GNU ld (GNU Binutils for Debian) 2.29 (binutils 2.29-9)
Note evidence of the ".alphalib" section patch first tried with the 4.9
kernel source. It has worked well up through 4.12. I didn't try
building any of the
No idea how long this has been broken. Noticed it this morning. The
NTP daemon appears to start normally based on entries in "syslog", but
dies almost immediately afterward with the following message:
Apr 13 08:34:09 smirkin ntpd[6676]: Cannot find user ID 110
The appropriate user and group ent
On Wed, Apr 12, 2017 at 07:36:36PM +1200, Michael Cree wrote:
> On Wed, Apr 12, 2017 at 07:57:52AM +0200, Helge Deller wrote:
> > On 12.04.2017 04:59, Bob Tracy wrote:
> > > Bottom line is, no kernel I've built since 4.9 can load a module. All
> > > attempts to l
(Adding linux-kernel to the distribution. The issue seems to be
architecture-specific, but I'm trying to understand what broke.)
The 4.10-rc1 patch set made fairly extensive modifications to
"a/kernel/module.c" (I'm leaving the "a" there so there's no doubt I
mean the top-level "kernel/module.c"
On Tue, Apr 11, 2017 at 06:12:32PM +1200, Michael Cree wrote:
> > > commit e811f8794673153858eac86448d827002e50ac0a
> > > Author: Michael Cree
> > > Date: Wed Feb 8 13:49:02 2017 +1300
> > >
> > > alpha: fix link errors in user_copy().
> >
> > Missed both the above.
>
> This one attached.
On Mon, Apr 10, 2017 at 09:42:50PM +1200, Michael Cree wrote:
> On Sun, Apr 09, 2017 at 07:47:55PM -0500, Bob Tracy wrote:
> > Both my 4.10 and recent 4.11-rc5 builds fail to boot/run properly.
>
> Just built 4.10.9 for DP264 and that boots fine on the XP1000.
>
> I ha
On Sun, Apr 09, 2017 at 07:47:55PM -0500, Bob Tracy wrote:
> (...)
> Both my 4.10 and recent 4.11-rc5 builds fail to boot/run properly. The
> console spews an endless stream of "unix: Unknown relocation: 1" errors
> on each attempt to load any module. I think I saw sev
Well, maybe the subject line is a bit over the top, but there's either
an element of truth to it, or the kernel developers have seriously
screwed things up in a fundamental way for kernels on Alpha after 4.9.
Both my 4.10 and recent 4.11-rc5 builds fail to boot/run properly. The
console spews an
On Sun, Feb 19, 2017 at 05:21:33PM +1300, Michael Cree wrote:
> Thanks for doing that. If there is no action on that by the
> maintainer in the near future, which is likely to be the case since
> Debian is in hard freeze, I could upload a rebuilt libkf5purpose-bin
> with the nodejs dependency remo
On Sat, Feb 18, 2017 at 11:49:06AM -0600, Bob Tracy wrote:
> On Fri, Feb 17, 2017 at 09:13:51AM +0100, Helge Deller wrote:
> > On hppa we will not support jnode short-term (and I assume it's true for
> > most other ports too).
> > So, if you open a bug, please inclu
On Fri, Feb 17, 2017 at 09:13:51AM +0100, Helge Deller wrote:
> On 17.02.2017 06:56, Michael Cree wrote:
> > On Thu, Feb 16, 2017 at 08:43:28PM -0600, Bob Tracy wrote:
> >> On Thu, Feb 16, 2017 at 08:23:05AM +1300, Michael Cree wrote:
> >>> On Wed, Feb 15, 2017 at 03:
On Fri, Feb 17, 2017 at 06:58:02PM +1300, Michael Cree wrote:
> On Thu, Feb 16, 2017 at 09:19:09PM -0600, Bob Tracy wrote:
> > On Thu, Feb 16, 2017 at 08:23:05AM +1300, Michael Cree wrote:
> > > I've got bigger fish to fry at the moment. In particular a
> > > bi
On Thu, Feb 16, 2017 at 08:23:05AM +1300, Michael Cree wrote:
> I've got bigger fish to fry at the moment. In particular a
> binutils/glibc bug that is causing segfaults in the dynamic symbol
> resolver. Try this: write a simple "Hello world" program in C.
> Compile with "-Wl,-z,now" linker optio
On Thu, Feb 16, 2017 at 08:23:05AM +1300, Michael Cree wrote:
> On Wed, Feb 15, 2017 at 03:43:02AM -0600, Bob Tracy wrote:
> (...)
> > Next issue is the "-m32" argument getting passed to the compiler. Not
> > appropriate for Alpha.
>
> That's a bug
On Tue, Jan 24, 2017 at 12:03:37AM -0700, Alan Young wrote:
> (...)
> And should the day ever come, heavens forbid, that a card has passed into
> the silicon beyond, remember that SRM can boot headless and has a serial
> port console on COM1.
> (...)
Hmmm... As long as it is possible to do the Al
I *knew* there was a reason I hung onto my old TGA video card :-).
The batteries in the UPS to which my Alpha was attached required
replacing. No way to do that with the machine plugged in and running,
so I shut it down and got to work.
Upon rebooting, it was obvious that my CMOS settings were g
er" relocation errors reported elsewhere.
Tested-by: Bob Tracy
--- a/arch/alpha/include/asm/uaccess.h 2016-11-19 08:26:53.0 -0600
+++ b/arch/alpha/include/asm/uaccess.h 2016-12-31 15:01:41.621694846 -0600
@@ -344,7 +344,7 @@
/* This little bit of silliness is to get the GP loaded
On Sat, Dec 31, 2016 at 09:32:58PM -0600, Bob Tracy wrote:
> On Sun, Jan 01, 2017 at 01:23:06AM +, Maciej W. Rozycki wrote:
> > You need to *replace* any `.text' pseudo-ops throughout with the said
> > `.section' pseudo-op for this to have any effect.
>
> Tha
On Sun, Jan 01, 2017 at 01:23:06AM +, Maciej W. Rozycki wrote:
> You need to *replace* any `.text' pseudo-ops throughout with the said
> `.section' pseudo-op for this to have any effect.
That makes sense, especially given the fact the *original* error
messages didn't change. Sorry for being
On Sun, Jan 01, 2017 at 08:38:51AM +1300, Michael Cree wrote:
> On Sat, Dec 31, 2016 at 09:20:37AM -0600, Bob Tracy wrote:
> > With '.section .alphalib,"ax"' added to the top of "arch/alpha/lib/*.S"
> > (below opening comment block, if present, but p
1 - 100 of 402 matches
Mail list logo
