LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: Frank Hartmann <soundart@gmx.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: 2.6.19.1 Oops while doing Disk IO + playing sound, 2.6.20 too
Date: Thu, 15 Feb 2007 10:40:53 +0100	[thread overview]
Message-ID: <20070215094053.GA28205@duck.suse.cz> (raw)
In-Reply-To: <87r6ssl3g4.fsf@fantasio.hh.de>

On Thu 15-02-07 00:33:31, Frank Hartmann wrote:
> Jan Kara <jack@suse.cz> writes:
> 
> >   Yes I see some correlation. Again it seems there is a problem with buffers
> > attached to a page which got truncated but Private flag of the page stayed.
> > It's probably not important but just out of curiosity - do you have
> > CONFIG_LBD (large block device) set? I'd just like to verify that page_bufs
> > was NULL when it was passed to walk_page_buffers().
> 
> fantasio:~/tmp/linux-2.6.20$ fgrep CONFIG_LBD .config
> # CONFIG_LBD is not set
  OK, thanks. Then I'm slightly confused as the offset 0x2d in struct
buffer_head is somewhere in b_assoc_buffers which is never dereferenced.
Can you run gdb on vmlinux from the 2.6.20 kernel and send me the output
of 'disass walk_page_buffers'? Thanks.

> >   You said 2.6.17 worked for you, didn't you? How long does it take to
> > reproduce the problem? If it is reasonably easy (e.g. a few hours), could
> > you trace back when the problem started happening? If you could narrow that
> > problem down to a single patch (using git-bisect), that would be great.
> 
> Yes I said that. At least I did not notice it happen:) 
> Reproduction seems easy. So I will try. 
   Great.

> I have some problem: I am not sufficiently familar with git!
> 
> I found http://www.kernel.org/pub/software/scm/git/docs/howto/isolate-bugs-with-bisect.txt
> Is this the way to do a git-bisect?
  Yes, that's it.

> From where do I get the 'labels' for good(2.6.17) and bad(2.6.20)?
  git bisect bad v2.6.20
  git bisect good v2.6.17

(or maybe you could start with 'git bisect bad v2.6.19' if that was also
failing for you). Git will spit out something like:

Bisecting: 9467 revisions left to test after this
[ebdea46fecae40c4d7effcd33f40918a37a1df4b] Merge branch 'devel' of master.kernel.org:/home/rmk/linux-2.6-arm

After you test kernel from the revision
'ebdea46fecae40c4d7effcd33f40918a37a1df4b', you do
  git bisect good/bad ebdea46fecae40c4d7effcd33f40918a37a1df4
and you'll get next revision to check. I hope it's clearer now.

									Honza
-- 
Jan Kara <jack@suse.cz>
SuSE CR Labs

  reply	other threads:[~2007-02-15  9:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-13 11:55 PROBLEM: 2.6.19.1 Oops while doing Disk IO + playing sound Frank Hartmann
2007-02-07  9:18 ` Jan Kara
2007-02-07 19:45   ` Frank Hartmann
2007-02-08  9:39     ` Jan Kara
2007-02-09  8:28       ` Frank Hartmann
2007-02-11 13:59       ` PROBLEM: 2.6.19.1 Oops while doing Disk IO + playing sound, 2.6.20 too Frank Hartmann
2007-02-14 14:32         ` Jan Kara
2007-02-14 23:33           ` Frank Hartmann
2007-02-15  9:40             ` Jan Kara [this message]
     [not found]               ` <87mz3f9gab.fsf@fantasio.hh.de>
2007-02-16  9:29                 ` Jan Kara
2007-03-04  8:37                   ` PROBLEM: 2.6.19.1 Oops while doing Disk IO + playing sound, 2.6.20 too -> STATUS git-bisect Frank Hartmann
2007-03-08  8:45                     ` Kevin Perros

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=20070215094053.GA28205@duck.suse.cz \
    --to=jack@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=soundart@gmx.net \
    --subject='Re: PROBLEM: 2.6.19.1 Oops while doing Disk IO + playing sound, 2.6.20 too' \
    /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

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).