All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Osterlund <petero2@telia.com>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: linux-kernel@vger.kernel.org, Jens Axboe <axboe@suse.de>
Subject: Re: [2.6.13] pktcdvd: IO-errors
Date: 26 Sep 2005 21:48:14 +0200	[thread overview]
Message-ID: <m3slvr1ugx.fsf@telia.com> (raw)
In-Reply-To: <Pine.LNX.4.60.0509262122450.4031@poirot.grange>

Guennadi Liakhovetski <g.liakhovetski@gmx.de> writes:

> On Mon, 26 Sep 2005, Peter Osterlund wrote:
> 
> > Guennadi Liakhovetski <g.liakhovetski@gmx.de> writes:
> > 
> > > Besides, it works under 2.6.12-rc5...
> > 
> > What gcc versions were used when compiling the kernels? (Boot both
> > kernels, run "cat /proc/version" to find out.)
> 
> Well, they are somewhat different:
> 
> Linux version 2.6.12-rc5 (lyakh@poirot.grange) (gcc version 3.3.4 (Debian 
> 1:3.3.4-13)) #1 Sun May 29 22:53:31 CEST 2005
> 
> Linux version 2.6.13.1 (lyakh@poirot.grange) (gcc version 3.3.5 (Debian 
> 1:3.3.5-13)) #1 Sat Sep 17 11:57:51 CEST 2005
> 
> ... No gcc-4.0, but still - 3.3.4 and 3.3.5... I could try recompiling 
> 2.6.12 with 3.3.5... Do you REALLY believe it could be the reason?

No, not 3.3.4 vs 3.3.5.

> > I just discovered that the driver doesn't work correctly on my laptop
> > if I use "gcc version 4.0.1 20050727 (Red Hat 4.0.1-5)" from Fedora
> > Core 4. "pktsetup 0 /dev/hdc ; cat /proc/driver/pktcdvd/pktcdvd0"
> > OOPSes. If I use gcc32 it does seem to work though.
> 
> Doesn't Oops for me under 2.6.13.1 compiled with 3.3.5, that's where I get 
> errors.

OK. Another option since you have one good and one bad kernel, is to
try to find the point in time where it broke. If you are a git user,
you can use the "git bisect" method. If not, you can use -rc releases
from ftp.kernel.org.

-- 
Peter Osterlund - petero2@telia.com
http://web.telia.com/~u89404340

  reply	other threads:[~2005-09-26 19:48 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-24 19:32 [2.6.13] pktcdvd: IO-errors Guennadi Liakhovetski
2005-09-25  9:09 ` Peter Osterlund
2005-09-25 21:06   ` Guennadi Liakhovetski
2005-09-26 18:36     ` Peter Osterlund
2005-09-26 19:29       ` Guennadi Liakhovetski
2005-09-26 19:48         ` Peter Osterlund [this message]
2005-09-26 22:06           ` Guennadi Liakhovetski
2005-09-28 21:02             ` Peter Osterlund
2005-09-29 19:18               ` Guennadi Liakhovetski
2005-10-02 12:11                 ` Peter Osterlund
2005-10-08 22:37                   ` Guennadi Liakhovetski
2005-10-09 21:23                   ` Guennadi Liakhovetski
2005-10-09 21:54                     ` Peter Osterlund
2005-10-10  5:05                       ` Guennadi Liakhovetski
2005-10-10 17:48                       ` Guennadi Liakhovetski
2005-10-10 20:48                         ` Guennadi Liakhovetski
2005-10-11 21:31                       ` Guennadi Liakhovetski
2005-10-11 21:58                         ` Peter Osterlund
2005-10-15 15:36                           ` Peter Osterlund
2005-10-17 21:11                             ` Guennadi Liakhovetski

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=m3slvr1ugx.fsf@telia.com \
    --to=petero2@telia.com \
    --cc=axboe@suse.de \
    --cc=g.liakhovetski@gmx.de \
    --cc=linux-kernel@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.