From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Tejun Heo <htejun@gmail.com>
Cc: "linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
paul@paulbristow.net, Alan Cox <alan@lxorguk.ukuu.org.uk>,
Stanislav Brabec <sbrabec@novell.com>,
Jeff Garzik <jeff@garzik.org>
Subject: Re: regression: ide-floppy doesn't work with IOMEGA IDE ZIP drive
Date: Mon, 12 Mar 2007 16:27:21 +0300 [thread overview]
Message-ID: <45F55539.7030709@ru.mvista.com> (raw)
In-Reply-To: <45F5465F.6050709@gmail.com>
Hello.
Tejun Heo wrote:
> Stanislav Brabec reported that IOMEGA IDE ZIP drive doesn't work with
> recent kernels. Low level driver is via82cxxx. Relevant part of
> 2.6.20.1 boot message follows.
> VP_IDE: IDE controller at PCI slot 0000:00:11.1
> VP_IDE: chipset revision 6
> VP_IDE: not 100% native mode: will probe irqs later
> VP_IDE: VIA vt8233 (rev 00) IDE UDMA100 controller on pci0000:00:11.1
> ide0: BM-DMA at 0xff00-0xff07, BIOS settings: hda:DMA, hdb:pio
> ide1: BM-DMA at 0xff08-0xff0f, BIOS settings: hdc:DMA, hdd:DMA
> Probing IDE interface ide0...
> hda: ST3160812A, ATA DISK drive
> hdb: IOMEGA ZIP 100 ATAPI, ATAPI FLOPPY drive
> ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
> ...
> hdb: lost interrupt
> hdb: status error: status=0x00 { }
> ide: failed opcode was: unknown
> ide-floppy: Strange, packet command initiated yet DRQ isn't asserted
> ...
> hdb: 98304kB, 96/64/32 CHS, 4096 kBps, 512 sector size, 2941 rpm
> hdb: No disk in drive
> hdb: lost interrupt
> hdb: status error: status=0x00 { }
> ide: failed opcode was: unknown
> ide-floppy: Strange, packet command initiated yet DRQ isn't asserted
> [above repeats several times]
> ...
> hdb: lost interrupt
> hdb: status error: status=0x00 { }
> ide: failed opcode was: unknown
> ide-floppy: Strange, packet command initiated yet DRQ isn't asserted
> hdb: 98304kB, 196608 blocks, 512 sector size
> hdb: unknown partition table
> hdb: unknown partition table
> hdb: unknown partition table
> hdb: unknown partition table
> And the device is inaccessible after boot completed. On suse 10.1
> kernel (2.6.16 based), it works better.
> VP_IDE: IDE controller at PCI slot 0000:00:11.1
> PCI: VIA IRQ fixup for 0000:00:11.1, from 255 to 0
> VP_IDE: chipset revision 6
> VP_IDE: not 100% native mode: will probe irqs later
> VP_IDE: VIA vt8233 (rev 00) IDE UDMA100 controller on pci0000:00:11.1
> ide0: BM-DMA at 0xff00-0xff07, BIOS settings: hda:DMA, hdb:pio
> ide1: BM-DMA at 0xff08-0xff0f, BIOS settings: hdc:DMA, hdd:DMA
> Probing IDE interface ide0...
> hda: ST3160812A, ATA DISK drive
> hdb: IOMEGA ZIP 100 ATAPI, ATAPI FLOPPY drive
> ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
> ...
> hdb: No disk in drive
> hdb: 98304kB, 96/64/32 CHS, 4096 kBps, 512 sector size, 2941 rpm
> ...
> hdb: lost interrupt
> hdb: status error: status=0x00 { }
> ide: failed opcode was: unknown
> ide-floppy: Strange, packet command initiated yet DRQ isn't asserted
> hdb: 98304kB, 196608 blocks, 512 sector size
> hdb: unknown partition table
> There is one lost interrupt message but the drive reportedly works
> fine after that. Stanislav also seems to recall that ide-floppy
> worked without any error message with older kernel.
> I'm attaching full boot log messages for 2.6.20.1 and suse 10.1.
> Any ideas?
BTW... I've looked at that code last spring and found it strange that
ide-floopy is the only driver that still calls dma_start() method *before*
issuing a command *while this is not a right thing to do accoring to spec and
is known to not work with some chips, namely Promise). I was going to send a
patch then but lacking both time and actual hardware, kept deferring it
since... :-)
MBR, Sergei
next prev parent reply other threads:[~2007-03-12 13:27 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-12 12:23 regression: ide-floppy doesn't work with IOMEGA IDE ZIP drive Tejun Heo
2007-03-12 13:27 ` Sergei Shtylyov [this message]
2007-03-13 11:50 ` Bartlomiej Zolnierkiewicz
2007-03-12 14:05 ` Jeff Garzik
2007-03-14 8:03 ` Albert Lee
2007-03-14 8:15 ` Tejun Heo
2007-03-14 9:01 ` Albert Lee
-- strict thread matches above, loose matches on Subject: below --
2007-03-13 11:17 Stanislav Brabec
2007-03-13 12:14 ` Tejun Heo
2007-03-13 13:42 ` Alan Cox
2007-03-13 14:24 ` Tejun Heo
2007-03-14 10:19 Stanislav Brabec
2007-03-14 11:58 ` Tejun Heo
2007-03-14 13:30 ` Mark Lord
2007-03-14 13:48 ` Tejun Heo
2007-03-14 17:42 ` Jeff Garzik
2007-03-14 13:42 ` Bartlomiej Zolnierkiewicz
2007-03-14 13:44 ` Tejun Heo
2007-03-14 18:27 ` Mark Lord
2007-03-15 2:08 ` Tejun Heo
[not found] ` <45F80841.EMEA5.EMEA5-1.100.1396E6E.1.3873.1@1:7.EMEA5.EMEA5-1.100.0.1.0.1@16>
2007-03-14 20:41 ` Stanislav Brabec
2007-03-15 4:29 ` Albert Lee
2007-03-15 19:58 ` Bartlomiej Zolnierkiewicz
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=45F55539.7030709@ru.mvista.com \
--to=sshtylyov@ru.mvista.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bzolnier@gmail.com \
--cc=htejun@gmail.com \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=paul@paulbristow.net \
--cc=sbrabec@novell.com \
/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.