public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: torvalds@transmeta.com (Linus Torvalds)
To: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.2-ac12
Date: 5 Mar 2001 20:21:54 -0800	[thread overview]
Message-ID: <981ol2$rp$1@penguin.transmeta.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0103052124250.1132-100000@groveland.analogic.com> <Pine.LNX.4.32.0103052121180.1029-100000@nic-31-c31-100.mn.mediaone.net>

In article <Pine.LNX.4.32.0103052121180.1029-100000@nic-31-c31-100.mn.mediaone.net>,
Scott M. Hoffman <scott1021@mediaone.net> wrote:
>
> It may not be related, but out of five boot attempts, only one got past
>the IDE driver stage(ie, below from 2.4.2 :
>  VP_IDE: IDE controller on PCI bus 00 dev 39
>  VP_IDE: chipset revision 16
>  VP_IDE: not 100% native mode: will probe irqs later
>  ide: Assuming 33MHz system bus speed for PIO modes; override with
>  idebus=xx
>  VP_IDE: VIA vt82c596b (rev 23) IDE UDMA66 controller on pci00:07.1
>      ide0: BM-DMA at 0xe000-0xe007, BIOS settings: hda:DMA, hdb:DMA
>      ide1: BM-DMA at 0xe008-0xe00f, BIOS settings: hdc:DMA, hdd:DMA)
>
>  I've had 2.4.2 running great for the past 10 days. Need any more info?

I'd love to hear anything you can come up with. What's the next step in
your boot process, ie what's the part that normally shows up but doesn't
with 2.4.2-ac12? Is this using IDE-SCSI, for example?

One thing that both 2.4.3-pre3 and -ac12 do is to not have allocate a
result buffer for TEST_UNIT_READY. I don't see why that should matter,
but can you try un-doing the patch to "scsi_error.c" and see if that
makes a difference. I'm worried about this report, and the buslogic
corruption thing.. 

Justin: there's another "2.4.3-pre2 corrupts all disks on a buslogic
controller" report. The interesting part is that 2.4.3-pre2 doesn't
actually contain any buslogic changes. The only generic-scsi changes
were yours. Ideas?

		Linus

  reply	other threads:[~2001-03-06  4:22 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-06  2:35 Linux 2.4.3 Richard B. Johnson
2001-03-06  3:02 ` Mike Fedyk
2001-03-06  3:33 ` Linux 2.4.2-ac12 Scott M. Hoffman
2001-03-06  4:21   ` Linus Torvalds [this message]
2001-03-06 10:34   ` God
2001-03-06 13:17     ` Scott M. Hoffman
2001-03-06 13:30       ` Alan Cox
2001-03-06 13:56         ` Scott M. Hoffman
2001-03-06 14:09           ` Alan Cox
2001-03-06 18:07         ` Wayne Whitney
2001-03-06 18:10         ` Linux 2.4.2-ac12, ac11 no good either Scott M. Hoffman
2001-03-07  3:31         ` Linux 2.4.2-ac12 God
2001-03-06 23:43       ` God
2001-03-06  3:42 ` Linux 2.4.3 Linus Torvalds
2001-03-08  0:16 ` Krzysztof Halasa
2001-03-08 15:44 ` David Weinehall
2001-03-08 16:09   ` Richard B. Johnson
     [not found] <200103060421.UAA00897@penguin.transmeta.com>
2001-03-06 21:44 ` Linux 2.4.2-ac12 Scott M. Hoffman
2001-03-06 22:22   ` Alan Cox
2001-03-06 22:44     ` Andre Hedrick

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='981ol2$rp$1@penguin.transmeta.com' \
    --to=torvalds@transmeta.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox