From: s864@ii.uib.no (Ronny V. Vindenes)
To: Linus Torvalds <torvalds@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.6.13-rc1
Date: 29 Jun 2005 16:23:11 +0200 [thread overview]
Message-ID: <m37jgd9r8w.fsf@localhost.localdomain> (raw)
In-Reply-To: <4kEoS-Am-3@gated-at.bofh.it>
Linus Torvalds <torvalds@osdl.org> writes:
> ARM, x86[-64], ppc, sparc updates, networking, sound, infiniband, input
> layer, ISDN, MD, DVB, V4L, network drivers, pcmcia, isofs, jfs, nfs,
> xfs, knfsd.. You name it.
>
> Git trees and traditional patches/tar-balls are out there, or at least
> slowly mirroring out. Go wild,
>
> Linus
On x86_64 with reiserfs and ext3 on dm (using cfq scheduler) the log
is full of this:
Badness in blk_remove_plug at drivers/block/ll_rw_blk.c:1424
Call Trace:<ffffffff8022e9a2>{blk_remove_plug+49} <ffffffff8022f093>{__generic_unplug_device+21}
<ffffffff80230da3>{get_request_wait+155} <ffffffff8013e6d0>{autoremove_wake_function+0}
<ffffffff80231252>{__make_request+789} <ffffffff8022f3e9>{generic_make_request+502}
<ffffffff8013e6d0>{autoremove_wake_function+0} <ffffffff8016a378>{bio_clone+130}
<ffffffff8803cadc>{:dm_mod:clone_bio+37} <ffffffff8803cdf5>{:dm_mod:__split_bio+327}
<ffffffff8803d11e>{:dm_mod:dm_request+171} <ffffffff8022f3e9>{generic_make_request+502}
<ffffffff8013e6d0>{autoremove_wake_function+0} <ffffffff8014d81c>{mempool_alloc+49}
<ffffffff8022f4ba>{submit_bio+188} <ffffffff80169dd0>{bio_alloc_bioset+232}
<ffffffff801674fd>{submit_bh+254} <ffffffff80169158>{__block_write_full_page+419}
<ffffffff8016c0e1>{blkdev_get_block+0} <ffffffff8018308f>{mpage_writepages+418}
<ffffffff8016b39b>{blkdev_writepage+0} <ffffffff8013afe6>{worker_thread+0}
<ffffffff8014ac31>{__filemap_fdatawrite_range+81} <ffffffff881c6752>{:reiserfs:flush_async_commits+103}
<ffffffff881c66eb>{:reiserfs:flush_async_commits+0}
<ffffffff8013b13f>{worker_thread+345} <ffffffff8012aef0>{default_wake_function+0}
<ffffffff8013afe6>{worker_thread+0} <ffffffff8013e533>{kthread+191}
<ffffffff8013afe6>{worker_thread+0} <ffffffff8010eee7>{child_rip+8}
<ffffffff8013afe6>{worker_thread+0} <ffffffff8013e358>{keventd_create_kthread+0}
<ffffffff8013e474>{kthread+0} <ffffffff8010eedf>{child_rip+0}
--
Ronny V. Vindenes <s864@ii.uib.no>
next parent reply other threads:[~2005-06-29 14:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4kEoS-Am-3@gated-at.bofh.it>
2005-06-29 14:23 ` Ronny V. Vindenes [this message]
2005-06-29 14:58 ` Linux 2.6.13-rc1 Tomasz Torcz
2005-06-29 15:07 ` Hugh Dickins
2005-06-29 15:20 ` Ronny V. Vindenes
2005-06-29 6:30 Linus Torvalds
2005-06-29 7:46 ` Brice Goglin
2005-06-29 9:02 ` Brice Goglin
2005-06-29 9:29 ` William Lee Irwin III
2005-06-29 19:31 ` Jesper Juhl
2005-06-29 21:00 ` David Weinehall
2005-06-29 22:34 ` Bill Davidsen
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=m37jgd9r8w.fsf@localhost.localdomain \
--to=s864@ii.uib.no \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox