From: Andrew Morton <akpm@linux-foundation.org>
To: "M" <martin@luminoussheep.net>
Cc: "Jan Kara" <jack@ucw.cz>, linux-fsdevel@vger.kernel.org
Subject: Re: PROBLEM: Regular crashes on 2.6.37 ext3_ordered_writepage?
Date: Fri, 21 Jan 2011 13:45:43 -0800 [thread overview]
Message-ID: <20110121134543.ccb8182d.akpm@linux-foundation.org> (raw)
In-Reply-To: <3e586516bdba94f2fac04d1488135fe9.squirrel@luminoussheep.net>
On Fri, 21 Jan 2011 21:27:58 -0000 (GMT)
"M" <martin@luminoussheep.net> wrote:
> > Do the traces all look like this? If you have other traces, please send
> them.
>
> They seem fairly regular but for some reason more often than not don't end
> up in the log, this is the only one I have so far.
>
> I've tried a serial dongle but I can't seem to get the kernel parameter to
> set the speed.
> I have:
> console=ttyUSB0,9600n8r console=tty
>
> And without it I can use minicom to test and the port works fine with it I
> just get some garbage... Any ideas? I've also built in usb and the usb
> dongle support (i.e. not a module).
hm, capturing oopses over USB is likely to be problematic - there's a
heck of a lot of software involved :( I've never tried it.
> Would it be worth my time typing in a transcript? It looks quite a lot to
> type and would be error prone :( but if another trace would make the
> difference. I'd give it a go.
Cellphone photographs work well.
next prev parent reply other threads:[~2011-01-21 21:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-21 21:27 PROBLEM: Regular crashes on 2.6.37 ext3_ordered_writepage? M
2011-01-21 21:45 ` Andrew Morton [this message]
[not found] <888ef2e56b2ab414fdb72771db8d673f.squirrel@luminoussheep.net>
2011-01-21 21:03 ` Andrew Morton
2011-01-21 21:49 ` Andreas Dilger
2011-01-21 22:06 ` M
2011-01-22 13:38 ` M
2011-02-12 8:01 ` martin
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=20110121134543.ccb8182d.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=jack@ucw.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=martin@luminoussheep.net \
/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;
as well as URLs for NNTP newsgroup(s).