public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: k.gavrilenko@arhont.com
Cc: mlists@arhont.com, linux-kernel@vger.kernel.org
Subject: Re: 2.6.5-mm6 reiserfs and hpt366 problems
Date: Fri, 16 Apr 2004 15:53:37 -0700	[thread overview]
Message-ID: <20040416155337.34555e61.akpm@osdl.org> (raw)
In-Reply-To: <408057A5.6010604@arhont.com>

Konstantin Gavrilenko <mlists@arhont.com> wrote:
>
> Anyway, I applied 2.6.5-mm6 patch. The system does not hang anymore, but,
> I get this weird errors filling up syslog:
> 
> 
> Apr 16 22:45:06 filo kernel: Debug: sleeping function called from 
> invalid context at drivers/block/ll_rw_blk.c:1156
> Apr 16 22:45:06 filo kernel: in_atomic():0, irqs_disabled():1
> Apr 16 22:45:06 filo kernel: Call Trace:
> Apr 16 22:45:06 filo kernel:  [<c0117449>] __might_sleep+0x99/0xb0
> Apr 16 22:45:06 filo kernel:  [<c02950bf>] generic_unplug_device+0x1f/0x60
> Apr 16 22:45:06 filo kernel:  [<c02d9fc9>] unplug_slaves+0x69/0x70
> Apr 16 22:45:06 filo kernel:  [<c029511f>] blk_backing_dev_unplug+0x1f/0x30
> Apr 16 22:45:06 filo kernel:  [<c014dc99>] __wait_on_buffer+0xd9/0xe0
> Apr 16 22:45:06 filo kernel:  [<c0117770>] autoremove_wake_function+0x0/0x50
> Apr 16 22:45:06 filo kernel:  [<c013998c>] mark_page_accessed+0x2c/0x40
> Apr 16 22:45:06 filo kernel:  [<c0117770>] autoremove_wake_function+0x0/0x50
> Apr 16 22:45:06 filo kernel:  [<c01a91da>] flush_commit_list+0x29a/0x3a0
> Apr 16 22:45:06 filo kernel:  [<c01adf1a>] do_journal_end+0x85a/0xb60
> Apr 16 22:45:06 filo kernel:  [<c0136b30>] pdflush+0x0/0x30
> Apr 16 22:45:06 filo kernel:  [<c01acc8d>] journal_end_sync+0x4d/0x90
> Apr 16 22:45:06 filo kernel:  [<c019964d>] reiserfs_sync_fs+0x4d/0x60
> Apr 16 22:45:06 filo kernel:  [<c03776b7>] __down_failed_trylock+0x7/0xc
> Apr 16 22:45:06 filo kernel:  [<c0152b81>] sync_supers+0xb1/0xc0
> Apr 16 22:45:06 filo kernel:  [<c01361d6>] wb_kupdate+0x56/0x140
> Apr 16 22:45:06 filo kernel:  [<c0377974>] schedule+0x2a4/0x480
> Apr 16 22:45:06 filo kernel:  [<c0136a54>] __pdflush+0xa4/0x180
> Apr 16 22:45:06 filo kernel:  [<c0136b58>] pdflush+0x28/0x30
> Apr 16 22:45:06 filo kernel:  [<c0136180>] wb_kupdate+0x0/0x140
> Apr 16 22:45:06 filo kernel:  [<c0136b30>] pdflush+0x0/0x30

Someone else saw this, but they had an EVMS patch applied.  Have you
applied any additional patches here?


  reply	other threads:[~2004-04-16 22:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-16 22:01 2.6.5-mm6 reiserfs and hpt366 problems Konstantin Gavrilenko
2004-04-16 22:53 ` Andrew Morton [this message]
2004-04-16 23:37 ` Andrew Morton

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=20040416155337.34555e61.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=k.gavrilenko@arhont.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mlists@arhont.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox