Alpha arch development list
 help / color / mirror / Atom feed
From: Bob Tracy <rct@gherkin.frus.com>
To: Uwe Schindler <uwe@thetaphi.de>
Cc: 'Witold Baryluk' <baryluk@smp.if.uj.edu.pl>,
	'Michael Cree' <mcree@orcon.net.nz>,
	debian-alpha@lists.debian.org, mattst88@gmail.com,
	linux-alpha@vger.kernel.org
Subject: Re: recent udev upgrade failure on alpha
Date: Wed, 18 May 2011 13:37:34 -0500	[thread overview]
Message-ID: <20110518183734.GA7244@gherkin.frus.com> (raw)
In-Reply-To: <008e01cc1570$4567c210$d0374630$@thetaphi.de>

On Wed, May 18, 2011 at 05:28:42PM +0200, Uwe Schindler wrote:
> > > I had some time today to try again an upgrade of my AlphaStation 500
> > > to "linux-image-2.6.38-2-alpha-generic". I got again an error on
> > > loading the xfs.ko module from initrd  (I typed it manually from the
> > > boot screen to this mail *g*):
> > >
> > > Module xfs: Relocation (type4) overflow vs _xfs_buf_find
> > > FATAL: Error inserting xfs
> (/lib/modules/2.6.38-2-alpha-generic/.../xfs.ko):
> > > Invalid module format

Another data point...

My PWS 433au with a 2.6.38 kernel built from the standard kernel.org
source has a "xfs.ko" that will load correctly using "modprobe".  I
haven't tried the 2.6.38-2-alpha-generic kernel.

--Bob

  reply	other threads:[~2011-05-18 18:37 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-24  7:02 recent udev upgrade failure on alpha Bob Tracy
2011-02-24  7:51 ` Bob Tracy
2011-02-24 10:09   ` Uwe Schindler
2011-02-24 15:11     ` Matt Turner
2011-02-24 18:55       ` Uwe Schindler
     [not found]       ` <008101cbd454$02036770$060a3650$@thetaphi.de>
     [not found]         ` <005301cc1555$58f92c30$0aeb8490$@thetaphi.de>
     [not found]           ` <20110518145605.GJ3539@smp.if.uj.edu.pl>
2011-05-18 15:28             ` Uwe Schindler
2011-05-18 18:37               ` Bob Tracy [this message]
2011-07-15 14:04   ` Uwe Schindler
2011-07-15 15:17     ` Bob Tracy
2011-07-15 15:46       ` Uwe Schindler
2011-08-15 17:09         ` Uwe Schindler
2011-08-15 17:28           ` Uwe Schindler
2011-02-24  9:54 ` Michael Cree
2011-02-24 10:25   ` Bob Tracy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20110518183734.GA7244@gherkin.frus.com \
    --to=rct@gherkin.frus.com \
    --cc=baryluk@smp.if.uj.edu.pl \
    --cc=debian-alpha@lists.debian.org \
    --cc=linux-alpha@vger.kernel.org \
    --cc=mattst88@gmail.com \
    --cc=mcree@orcon.net.nz \
    --cc=uwe@thetaphi.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox