All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pedro Ribeiro <pedrib@gmail.com>
To: Dave Chinner <david@fromorbit.com>
Cc: xfs@oss.sgi.com
Subject: Re: Crash with 3.8.3 and TuxOnIce
Date: Wed, 20 Mar 2013 18:01:35 +0000	[thread overview]
Message-ID: <CAEDdjHc139n-FFrW34FLyfKsqFHBy0_LVcVT24aLyCpb4DC9dA@mail.gmail.com> (raw)
In-Reply-To: <20130320004405.GC17758@dastard>


[-- Attachment #1.1: Type: text/plain, Size: 2237 bytes --]

Thanks for the answer Dave.

Yes I would definitely say it's a ToI bug that perhaps has been dormant so
far. Unfortunately the ToI developer is very busy at the moment, so I will
have to debug and fix it myself.
This problem did not occur with 3.7 and the ToI code did not change.

Do you have any idea where I can start looking for the XFS change in 3.8
that triggered this behaviour in ToI? Or maybe it was a VFS change?

PS: the email definitely bounced back, most likely because imageshack is
blocked on the sgi server:

Technical details of permanent failure:
Google tried to deliver your message, but it was rejected by the server for
the recipient domain oss.sgi.com by cuda-allmx.sgi.com. [192.48.176.16].

The error that the other server returned was:
554 rejecting banned content

Regards,
Pedro

On 20 March 2013 00:44, Dave Chinner <david@fromorbit.com> wrote:

> On Tue, Mar 19, 2013 at 11:31:16PM +0000, Pedro Ribeiro wrote:
> > Hi,
> >
> > I'm using a TuxOnIce enabled kernel, and recently moved from 3.7.1 to
> > 3.8.3. The former used to work nicely, but now I get a hard crash when I
> > try to hibernate.
> > This is solely related to TuxOnIce as it does not happen in the default
> > hibernation.
> >
> > I know this is an unsupported out of tree patch, but can you please help
> me
> > debug it or point in the right direction?
> >
> > Unfortunately as this was a kernel crash all I have are crappy photos,
> but
> > they do show a readable stack trace:
> > img18[dot]imageshack[dot]us/img18/395/imag0228hp[dot]jpg
> > img13[dot]imageshack[dot]us/img13/4375/imag0231p[dot]jpg
> >
> > (I removed the HTTP part and the dots off the links else it would bounce
> > back from the list)
>
> The list doesn't bounce URLs. Please make then clicky in future.
>
> As it is, your kernel has oopsed in submit_bio() when writing a log
> buffer writing a dummy log record.
>
> The xfs_log_worker is trying to cover the log, and it seems like the
> IO subsystem below it is doing something wrong. Perhaps Tux-on-Ice
> is killing the IO subsystem without having first stopped all the
> async filesystem processing first?
>
> Looks like a Tux-on-ICE problem to me...
>
> Cheers,
>
> Dave.
> --
> Dave Chinner
> david@fromorbit.com
>

[-- Attachment #1.2: Type: text/html, Size: 4118 bytes --]

[-- Attachment #2: Type: text/plain, Size: 121 bytes --]

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2013-03-20 18:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-19 23:31 Crash with 3.8.3 and TuxOnIce Pedro Ribeiro
2013-03-20  0:44 ` Dave Chinner
2013-03-20 18:01   ` Pedro Ribeiro [this message]
2013-03-21  1:01     ` Dave Chinner
2013-03-21 17:45       ` Pedro Ribeiro
2013-03-27 21:58         ` Pedro Ribeiro
2013-03-28  0:51           ` Dave Chinner
2013-03-27 23:39 ` Ben Myers
2013-03-28  0:51   ` Dave Chinner

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=CAEDdjHc139n-FFrW34FLyfKsqFHBy0_LVcVT24aLyCpb4DC9dA@mail.gmail.com \
    --to=pedrib@gmail.com \
    --cc=david@fromorbit.com \
    --cc=xfs@oss.sgi.com \
    /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.