All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: ext4 on s390?
Date: Fri, 08 Aug 2008 16:31:13 -0500	[thread overview]
Message-ID: <489CBB21.5030801@redhat.com> (raw)
In-Reply-To: <489CA7B8.7090202@redhat.com>

Eric Sandeen wrote:
> Just wondering if anyone has tested ext4 on s390.  I see that some
> assembly bitops got fixed upstream, but even with those in place I'm
> hanging when ext4 tries to init bg's:
> 
> Call Trace:
> ([<0000000000016472>] show_trace+0xb2/0x130)
>  [<00000000001793f4>] showacpu+0x48/0x68
>  [<0000000000024816>] do_ext_call_interrupt+0x8a/0xc4
>  [<000000000001c2b6>] do_extint+0xe2/0xfc
>  [<0000000000020ea8>] ext_no_vtime+0x16/0x1a
>  [<0000000020cd99f2>] ext4_mb_init_cache+0x9fe/0x1020 [ext4dev]
> ([<0000000020cd91a4>] ext4_mb_init_cache+0x1b0/0x1020 [ext4dev])
>  [<0000000020cdba9c>] ext4_mb_load_buddy+0x264/0x36c [ext4dev]
>  [<0000000020cdc446>] ext4_mb_regular_allocator+0x53e/0x1218 [ext4dev]
>  [<0000000020ce0d06>] ext4_mb_new_blocks+0x1a2/0x7e8 [ext4dev]
>  [<0000000020cd6538>] ext4_ext_get_blocks+0xe3c/0x1074 [ext4dev]
>  [<0000000020cc32be>] ext4_get_blocks_wrap+0x132/0x190 [ext4dev]
>  [<0000000020cc40aa>] ext4_getblk+0x8a/0x26c [ext4dev]
>  [<0000000020cc4b12>] ext4_bread+0x26/0xd8 [ext4dev]
>  [<0000000020cc89fa>] ext4_mkdir+0x18e/0x3c8 [ext4dev]
>  [<00000000000be54c>] vfs_mkdir+0x10c/0x1a8
>  [<00000000000c204e>] sys_mkdirat+0xca/0x114
>  [<00000000000208c0>] sysc_tracego+0xe/0x14
>  [<00000200001345e6>] 0x200001345e6
> 
> I'm now struggling to get an s390 booted on an upstream kernel to test
> that, but I know about -><- about s390s.

I managed to boot 2.6.26.2 (stock) on an s390; same problem.  :(

IBM, help? :)

-Eric

      reply	other threads:[~2008-08-08 21:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-08 20:08 ext4 on s390? Eric Sandeen
2008-08-08 21:31 ` Eric Sandeen [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=489CBB21.5030801@redhat.com \
    --to=sandeen@redhat.com \
    --cc=linux-ext4@vger.kernel.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.