mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Borislav Petkov <petkovbb@googlemail.com>
To: Jonathan Woithe <jwoithe@physics.adelaide.edu.au>
Cc: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
	linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org,
	Tejun Heo <tj@kernel.org>
Subject: Re: 2.9.29.2: ide-tape: panic when probing device at boot
Date: Mon, 18 May 2009 08:30:07 +0200	[thread overview]
Message-ID: <20090518063007.GA7818@liondog.tnic> (raw)
In-Reply-To: <200905180532.n4I5Wxa1031243@turbo.physics.adelaide.edu.au>

Hi,

On Mon, May 18, 2009 at 03:02:59PM +0930, Jonathan Woithe wrote:
> > On Sat, May 09, 2009 at 05:57:49PM +0200, Bartlomiej Zolnierkiewicz wrote:
> > > 
> > > [ cc:ing linux-ide and knowledgeable people ]
> > > 
> > > Borislav/Tejun:
> > > Is the 2.6.29 problem the same thing that was fixed recently?
> > 
> > I'll let Tejun answer that one since I don't get an oops. However, now
> > that I have an ide-tape hardware here, I do get something DMA-related
> > failing during boot ...
> > :
> > and more specifically the bad DMA info in identify block thing above. I
> > haven't looked into it yet but its next on my TODO.
> 
> Cool.
> 
> > > Should I just push commit 1e75540ec5202cae63cd238c86bd880e3d496546
> > > ("ide-tape: remove back-to-back REQUEST_SENSE detection") to Linus
> > > or there is more needed to bring ide-tape to the world of living?
> >
> > The oops will probably fixed the above commit.  I don't have much idea
> > about the DMA problem on 2.6.24 tho.  But even with the above commit
> > fixed, I doubt it would work.  The buffer allocation code is broken
> > and reliably triggered OOM on my test machine.  While trying to locate
> > the bug, I realized the complex code didn't do much good to begin with
> > and just stripped it down, so I didn't actually tracked down the
> > actual bug && the patch to simplify buffer management is way too large
> > for 2.6.29, so unless someone is willing to hunt down the bug just for
> > 2.6.29, we're kind of stuck.  :-(
> 
> So I take it that 2.6.30 (or one of the RCs) is worth trying (at least in so
> far as preventing the oops on boot)?

You could try 30-rc6 which runs pretty stable on my machines. It has the
patch mentioned above in it. At least one user confirmed that it fixes
ide-tape in his case. In case you still catch any OOPSes/warnings etc
please send me the whole dmesg output along with how you trigger them.

> > ... and I'm afraid we'll have to do some serious bugfixing since this
> > driver is behaving really funny :). Stay tuned, I'm on it.
> 
> Ok, I'll keep an eye out for updates.  Presumedly we're talking 2.6.31 or
> .32 here.

Already in .31-rc1 there's will more patches cleaning up ide-tape so if you
could try that and send us bug reports will be simply swell :).

Thanks.

-- 
Regards/Gruss,
    Boris.

  reply	other threads:[~2009-05-18  6:30 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-08  7:00 Jonathan Woithe
2009-05-09 15:57 ` Bartlomiej Zolnierkiewicz
2009-05-09 16:18   ` Borislav Petkov
2009-05-10  0:59     ` Tejun Heo
2010-01-04  1:15       ` Jonathan Woithe
2010-01-04  5:47         ` Borislav Petkov
2010-01-05  5:38           ` Jonathan Woithe
2010-03-12  1:31             ` Jonathan Woithe
2010-01-04  5:52         ` Robert Hancock
2009-05-18  5:32     ` Jonathan Woithe
2009-05-18  6:30       ` Borislav Petkov [this message]
2009-05-18 13:18         ` Borislav Petkov
2009-05-10  0:58   ` Tejun Heo

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=20090518063007.GA7818@liondog.tnic \
    --to=petkovbb@googlemail.com \
    --cc=bzolnier@gmail.com \
    --cc=jwoithe@physics.adelaide.edu.au \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tj@kernel.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

all inboxes | Powered by JetHome®