Hi Christoph,
thanks for your answer!
Any clue on how to help/speed up this? Was there any exchange with them when you
first provided your patch back in 2014? Can it be restarted?
My feeling is that the issue fixed with 045065d8a300a37218c548e9aa7becd581c6a0e8
was in fact the real paper over
Hi Sergio,
On Tue, Aug 18, 2015 at 09:44:28AM +0200, Sergio Callegari wrote:
> Hi,
>
> I have bisected the issue down to
>
> [045065d8a300a37218c548e9aa7becd581c6a0e8] [SCSI] fix qemu boot hang problem
>
> Bisecting has been a painful job due to the fact that the bug may show only
> many hours
Hi,
I have bisected the issue down to
[045065d8a300a37218c548e9aa7becd581c6a0e8] [SCSI] fix qemu boot hang problem
Bisecting has been a painful job due to the fact that the bug may show only many
hours after the system boot.
The commit above in fact is not the culprit, but a fix to an issue
On 02/07/2015 18:11, Ondrej Zary wrote:
You're probably using libata and not the old IDE layer.
Just tested this one:
Model=IOMEGA ZIP 100 ATAPI, FwRev=03.H, SerialNo=
Config={ SpinMotCtl Removeable nonMagnetic }
RawCHS=0/0/0, TrkSize=0, SectSize=0, ECCbytes=0
BuffType=unknown, B
On Thursday 25 June 2015 22:58:58 Sergio Callegari wrote:
> Hi,
>
> I have an Iomega IDE Zip drive as in:
>
> /dev/sda:
>
> Model=IOMEGA ZIP 100 ATAPI Floppy, FwRev=12.A, SerialNo=
> Config={ SpinMotCtl Removeable nonMagnetic }
> RawCHS=0/0/0, TrkSize=0, SectSize=0, ECCbytes=0
> Bu
On Thu, Jun 25, 2015 at 08:58:58PM +, Sergio Callegari wrote:
> What has changed wrt IDE in 3.16->3.17 transition? Why is the issue present
> even when the drive is not used (unmounted)? How can I help diagnosing?
Here's what went into ide in 3.17:
$ git log -p v3.16..v3.17 drivers/ide/
com
On Wed, Jan 02, 2008 at 10:25:05AM +0100, Borislav Petkov wrote:
by the way, i messed up the numbering of the patches: their correct count is not
12 but 10 so you shouldn't be missing any even if it seems so at a first glance.
--
Regards/Gruß,
Boris.
--
To unsubscribe from this list: send th
Denis Vlasenko wrote:
On Friday 02 September 2005 23:47, Ondrej Zary wrote:
Hello,
I've bought "new" LS-120 drive and found that software eject does not
work with 2.6.13 kernel:
[EMAIL PROTECTED]:~# eject /dev/hdc
eject: unable to eject, last error: Invalid argument
The drive spins up and af
>> May 17 05:42:20 m kernel: hdd: lost interrupt
>> May 17 05:42:20 m kernel: ide-floppy: CoD != 0 in idefloppy_pc_intr
>> May 17 05:42:20 m kernel: hdd: ATAPI reset complete
>> May 17 05:43:10 m kernel: hdd: lost interrupt
>> May 17 05:43:10 m kernel: ide-floppy: CoD != 0 in idefloppy_pc_intr
>>
> Whenever I boot (2.4.4-ac6) I get this error message if there is a zip
> disk in the drive.
Does it work with ide-scsi ?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordo
I have HOTSWAP ATA completed, but will release after IDF.
It will be used to blow MircoSoft out of the water at IDF.
On Sun, 25 Feb 2001, Jeremy Jackson wrote:
> Derrik Pates wrote:
>
> > Subject says about all there is to say. I have figured out that IDE drives
> > are enumerated as part of t
Derrik Pates wrote:
> Subject says about all there is to say. I have figured out that IDE drives
> are enumerated as part of the boot-time partition check in
> fs/partitions/check.c, but if I don't have something loaded at boot time
> (IDE SuperDisk in PC at home, IDE Zip 100 in G3 tower at work)
Hello Paul,
(you CC'ed your original post to vger.rutgers.edu, I shamelessly corrected
this for this reply)
> I have (finally) merged your patch in with the ide-floppy driver and
> have it working with devfs here on my laptop for a PCMCIA Clik drive.
Have you merged my patch in literate or in
> One of my concerns is that we don't take the ide-floppy driver in a
> different direction to the other removeable media drives.
In general the others do it raw via scsi commands and sg.
> For Alan Cox, could you back out Sam's patch for now. It will be back
> soon.
When the new one is sorted.
Hi together,
Paul Bristow wrote:
>
> I'll get on it. I just tidied up the previous patch for Clik! support
> and fixed the last bug so that *should* wrap up 2.2.x.
Wonderful, so I can hope for a good solution soon :-)
BTW (for Jens): I noticed some other removable device problems
with devfs
On Tue, 24 Oct 2000, Guest section DW wrote:
> On Tue, Oct 24, 2000 at 01:33:57AM +0200, Andreas Franck wrote:
>
> + printk(KERN_INFO "calling ide_register_module\n");
> ide_register_module(&idefloppy_module);
> + printk(KERN_INFO "ide_register_module finished\n");
>
> You d
On Tue, Oct 24, 2000 at 01:33:57AM +0200, Andreas Franck wrote:
+ printk(KERN_INFO "calling ide_register_module\n");
ide_register_module(&idefloppy_module);
+ printk(KERN_INFO "ide_register_module finished\n");
You do not want debugging code like this in the kernel code.
-
To
I did report this back a month or so ago. Another work around is to have a
device node (22,0 in my case) around to bang on for a sec. After having
the kernel poke the device, the appropriate devfs node appears
automagically.
My 0.02USD.
Josh
On Sun, 22 Oct 2000, Andreas Franck wrote:
> Hi Paul
Hi Paul, hi Richard, hi linux-kernel audience,
Paul Bristow wrote:
> Hi Andreas,
>
> Could you re-send the patch, as it didn't make it with your last
> message?
Sorry, my mailer crashed when I sent this message and I didn't even
notice it got sent :-) So here's what you're waitung for (at least
19 matches
Mail list logo
