All of lore.kernel.org
 help / color / mirror / Atom feed
From: Giuliano Pochini <pochini@shiny.it>
To: Olaf Hering <olh@suse.de>
Cc: linux-kernel@vger.kernel.org, linuxppc-dev@lists.linuxppc.org
Subject: RE: 2.4.2 freezes with bad ISOs in IDE cdroms
Date: Wed, 21 Mar 2001 15:19:22 +0100 (CET)	[thread overview]
Message-ID: <XFMail.010321151922.pochini@shiny.it> (raw)
In-Reply-To: <20010320225845.A5763@suse.de>


On 20-Mar-01 Olaf Hering wrote:
> Hi,
> 
> this is a bogus bugreport.
> 
> The 2.4.2 kernel freezes on some machines here when I try to access (or
> mount) a bad self burned ISO image, in this case the boot CD with the
> install system.
> 
> There are different case:
> 
> I have an iBook and a blue&white G3. The G3 has a cmd646 controller. It
> freezes when it tries to access the CD. No output.
> "ide0=nodma ide2=nodma" doesnt lead to a freeze, but endless error messages.
> The installer starts after a while, so it can mount the inst-sys, but it
> doest get very far (no output).
> 
> Uniform Multi-Platform E-IDE driver Revision: 6.31
> ide: Assuming 33MHz system bus speed for PIO modes; override with
> idebus=xx
> CMD646: IDE controller on PCI bus 01 dev 08
> CMD646: chipset revision 7
> CMD646: chipset revision 0x07, UltraDMA Capable
> CMD646: 100% native mode on irq 26
>     ide0: BM-DMA at 0x1800-0x1807, BIOS settings: hda:pio, hdb:pio
>     ide1: BM-DMA at 0x1808-0x180f, BIOS settings: hdc:pio, hdd:pio
> pmac_ide: enabling IDE bus ID 0
> hda: Maxtor 90648D3, ATA DISK drive
> ide: Assuming 33MHz system bus speed for PIO modes; override with
> idebus=xx
> hde: MATSHITADVD-ROM SR-8583, ATAPI CD/DVD-ROM drive
> ide0 at 0x1840-0x1847,0x1832 on irq 26
> ide2 at 0xc8544000-0xc8544007,0xc8544160 on irq 13
> hda: 12656448 sectors (6480 MB) w/512KiB Cache, CHS=12556/16/63,
> UDMA(33)
> hde: Enabling MultiWord DMA 2
> hde: ATAPI 32X DVD-ROM drive, 512kB Cache, DMA
> Uniform CD-ROM driver Revision: 3.12
> Partition check:
>  hda: [mac] hda1 hda2 hda3 hda4 hda5 hda6 hda7 hda8 hda9 hda10
> 
> 
> Today I got another report on a G4/500. It just freezes when it access a
> package on a bad block. Skipping the rpm package were it freezes solves that.
> 
> I tried the same ISOs on a SCSI cdrom to verify the MD5SUMS, no crash,
> just read errors in dmesg. The controller is a "Symbios Logic Inc.
> (formerly NCR) 53c875 (rev 04)".
> 
> However, my machine at home locks the SCSI bus in sometimes. It has a
> mesh SCSI controller, The last message in the syslog is that:
> Device not ready.  Make sure there is a disc in the drive
> I still can switch consoles, but the hard drive is not accessible
> anymore. 
> (this part of the bugreport is maybe not related to the lockups).
> 
> 
> Any ideas where to start here?


This happens on my blue G3 with 2.2.x too. I think it's a bug in the IDE
driver. My old 7300 (mesh) with a SCSI cd just reported a read error on
the same disk.


Bye.
    Giuliano Pochini ->)|(<- Shiny Network {AS6665} ->)|(<-


  reply	other threads:[~2001-03-21 14:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-20 21:58 2.4.2 freezes with bad ISOs in IDE cdroms Olaf Hering
2001-03-21 14:19 ` Giuliano Pochini [this message]
2001-03-21 14:33   ` Olaf Hering

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=XFMail.010321151922.pochini@shiny.it \
    --to=pochini@shiny.it \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=olh@suse.de \
    /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.