Syquest EZ135 locks up the kernel 2.0.30..

Syquest EZ135 locks up the kernel 2.0.30..

Post by Isma » Tue, 29 Apr 1997 04:00:00



   I just tried using a Syquest EZ135 with Linux
   2.0.30 kernel and the modular ncr53c8xx driver.
   Everything went ok until I started writing to the
   drive:  I did an fdisk /dev/sda and partitioned it
   to a Linux native format, then did an mke2fs -m1
   /dev/sda1 and fsck'ed  it ok afterward. So far so
   good. I then tried to tar a directory on it.  It
   went for a few files and then stopped and
   complained about not finding the superblock.  My
   kernel panicked and  got kind of locked up. I could
   not reboot or halt the system. The commands just
   came back without doing anything. I had to push the
   reset button. I went through the same sequence
   twice..

   What is happening? Could this be a kernel/driver
   bug, or I am missing something?

   ismail

-------------------------------------------------------
Legal Warning: Do NOT send unsolicited commercial
email to me - consider this as an official notice:

    "By US Code Title 47, Sec.227(a)(2)(B), a
    computer/modem/printer meets the definition of a
    telephone fax machine.  By Sec.227(b)(1)(C), it is
    unlawful to send any unsolicited adverti*t to
    such equipment.  By Sec.227(b)(3)(C), a violation of
    the aforementioned Section is punishable by action to
    recover actual monetary loss, or $500, whichever is
    greater, for each violation."

 
 
 

1. Syquest EZ135 locks up the kernel 2.0.30..

   I just tried using a Syquest EZ135 with Linux
   2.0.30 kernel and the modular ncr53c8xx driver.
   Everything went ok until I started writing to the
   drive:  First I did an fdisk /dev/sda and partitioned it
   to a Linux native format, then did an mke2fs -m1
   /dev/sda1, and fsck'ed it ok afterward. So far so good.

   I then tried to tar a directory on it.  It
   went for a few files and then stopped, and
   complained about not finding the superblock.  The
   kernel panicked and  got kind of locked up. I could
   not reboot or halt the system. The commands just
   came back without doing anything. I had to push the
   reset button. I went through the same sequence twice..

   What is happening? Could this be a kernel/driver
   bug, or I am missing something?

   ismail

-------------------------------------------------------
Legal Warning: Do NOT send unsolicited commercial
email to me - consider this as an official notice:

    "By US Code Title 47, Sec.227(a)(2)(B), a
    computer/modem/printer meets the definition of a
    telephone fax machine.  By Sec.227(b)(1)(C), it is
    unlawful to send any unsolicited advertisement to
    such equipment.  By Sec.227(b)(3)(C), a violation of
    the aforementioned Section is punishable by action to
    recover actual monetary loss, or $500, whichever is
    greater, for each violation."

2. ruined my /etc/bashrc. Can I login?

3. Syquest EZ135 with ncr53c810 locks it all up...

4. XIRCOM CARD BUS 56 GLOBAL ACCESS

5. Resolved: Syquest EZ135 with ncr53c810 locks it all up...

6. x86 Solaris disk IO performance

7. UPS for about 30 kVA

8. Upgrading KDE

9. Syquest EZ135

10. Does the SyQuest EZ135 optical drive work w/ Linux?

11. Syquest EZ135 SCSI & Linux

12. Syquest EZ135 IDE and Linux?

13. Syquest EZ135 parport on linux