All of lore.kernel.org
 help / color / mirror / Atom feed
From: "b.gunreben" <b.gunreben@web.de>
To: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] /dev/loop0 problems in 2.5.x?
Date: Wed, 19 Feb 2003 20:58:23 +0100	[thread overview]
Message-ID: <3E53E1DF.5AACBABA@web.de> (raw)
In-Reply-To: 20030218041653.GI15855@systemhalted

Carlos O'Donell wrote:
> 
> parisc,
> 
> Works in 2.4.x, thinking of moving part of the cluster to 2.5, but I like
> to play with swap over NFS.
> 
> root@node01:/etc# /sbin/losetup /dev/loop0 /swapfile
> ioctl: LOOP_SET_FD: Inappropriate ioctl for device
> root@node01:/etc# uname -a
> Linux node01 2.5.59-pa2 #2 Thu Jan 23 00:49:22 EST 2003 parisc unknown
> unknown GNU/Linux
> 
> Do I need newer tools for playing with 2.5.x on HPPA?
> Loopback is compiled into the kernel, no modules, and I can produce the
> .config if you would like to look :)

I recently started to play around with 2.5.60 kernels. Up to now, I was not
successful in building a working kernel. Especially if the loop device was
compiled in, the kernel panicked in the following device driver (first the
network device, after removing the network device it panicked when
initializing SCSI). Without the loop device, the kernel came up to init, and
panicked then.

I was using gcc (GCC) 3.3-hammer 20030123 from CVS, and this is probably the
reason why my kernels fail. Maybe, you should try several different
compilers to build the kernel. 

If someone has a working for .config for 2.5.60, I would like to try this
configuration with a slightly newer compiler (gcc (GCC) 3.3-hammer 20030205)


Berthold

      reply	other threads:[~2003-02-19 20:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-18  4:16 [parisc-linux] /dev/loop0 problems in 2.5.x? Carlos O'Donell
2003-02-19 19:58 ` b.gunreben [this message]

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=3E53E1DF.5AACBABA@web.de \
    --to=b.gunreben@web.de \
    --cc=parisc-linux@lists.parisc-linux.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.