From: "Oliver Pinter (Pintér Olivér)" <oliver.pntr@gmail.com>
To: "Al Boldi" <a1426z@gawab.com>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
mingo@elte.hu
Subject: Re: konqueror deadlocks on 2.6.22
Date: Sat, 19 Jan 2008 23:17:14 +0100 [thread overview]
Message-ID: <6101e8c40801191417k7906422chf657895152b61a2d@mail.gmail.com> (raw)
In-Reply-To: <200801192357.13774.a1426z@gawab.com>
add cc (ingo)
and then please update to CFS-v24.1
http://people.redhat.com/~mingo/cfs-scheduler/sched-cfs-v2.6.22.15-v24.1.patch
--------------------
On 1/19/08, Al Boldi <a1426z@gawab.com> wrote:
> Oliver Pinter (Pintér Olivér) wrote:
> > This kernel is vanilla 2.6.22.y or with CFS?
>
> Yes with CFSv20.4, as in the log.
>
> It also hangs on 2.6.23.13
>
> > On 1/19/08, Al Boldi <a1426z@gawab.com> wrote:
> > > I was just attacked by some deadlock issue involving sqlite3 and
> > > konqueror. While sqlite3 continues to slowly fill a 7M-record db in
> > > transaction mode, konqueror hangs for a few minutes, then continues only
> > > to hang again and again.
> > >
> > > Looks like an fs/blockIO issue involving fsync.
> > >
> > > As a workaround, is there a way to make fsync soft?
>
>
> Thanks!
>
> --
> Al
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
--
Thanks,
Oliver
next prev parent reply other threads:[~2008-01-19 22:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-19 18:14 konqueror deadlocks on 2.6.22 Al Boldi
2008-01-19 18:53 ` Oliver Pinter (Pintér Olivér)
2008-01-19 20:57 ` Al Boldi
2008-01-19 22:17 ` Oliver Pinter (Pintér Olivér) [this message]
2008-01-22 10:10 ` Ingo Molnar
2008-01-22 13:23 ` Al Boldi
2008-01-22 14:25 ` Chris Mason
2008-01-22 18:54 ` Al Boldi
2008-01-22 19:13 ` Chris Mason
[not found] ` <1200802290.4166.2.camel@homer.simson.net>
2008-01-20 5:41 ` Al Boldi
2008-01-20 7:23 ` Mike Galbraith
2008-01-20 7:30 ` Mike Galbraith
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=6101e8c40801191417k7906422chf657895152b61a2d@mail.gmail.com \
--to=oliver.pntr@gmail.com \
--cc=a1426z@gawab.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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).