public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: |TEcHNO| <techno@punkt.pl>
Cc: linux-scsi@vger.kernel.org
Subject: Re: [SCSI] Driver broken in 2.6.x?
Date: Sun, 29 May 2005 18:07:47 -0700	[thread overview]
Message-ID: <20050529180747.18b7fd9e.akpm@osdl.org> (raw)
In-Reply-To: <4298FD42.10608@punkt.pl>

|TEcHNO| <techno@punkt.pl> wrote:
>
> Hi,
> 
> > Is this crash still repeatable in 2.6.12-rc5?
> > 
> > If so, can you please verify that it still occurs if the nvidia driver was
> > never loaded?
> 
> No, it works now as if it was 2.4.x series.
> Now it just randomly hangs the system, ie. somewhere at the end of 
> scanning or suchm no nothing in logs or similar. Simply hangs. My guess 
> is that It shoudln't, no matter what, I always thought Linux was stable 
> but the current problems (CDburning problems around 2.6.9, scanner/SCSI 
> hanging the system) seem to  contradict this. That's bad.

You cunningly removed linux-scsi from cc and replaced it with linux-kernel.
Please don't do that.

As things have changed we'd need a new bug description please.

Please provide more details about the "hang".

Under what circumstances? 

Does it oops?

What hardware and which driver?

After it has "hung" is any information available from sysrq-P or sysrq-T?

Thanks.

  parent reply	other threads:[~2005-05-30  1:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <424EB65A.8010600@punkt.pl>
     [not found] ` <Pine.LNX.4.62.0504022301430.2525@dragon.hyggekrogen.localhost>
     [not found]   ` <424F0BFF.6020402@punkt.pl>
     [not found]     ` <Pine.LNX.4.62.0504022322150.2525@dragon.hyggekrogen.localhost>
2005-04-03 18:03       ` [Fw linux-kernel:] Re: [SCSI] Driver broken in 2.6.x? |TEcHNO|
2005-05-26  4:40 ` Andrew Morton
     [not found]   ` <4298FD42.10608@punkt.pl>
2005-05-30  1:07     ` Andrew Morton [this message]
2005-05-30  8:19       ` |TEcHNO|

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=20050529180747.18b7fd9e.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=techno@punkt.pl \
    /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