| Author |
 Topic  |
|
adam(at)bostoncoop.net
Just Posting
5 Posts |
 Posted - 07/23/2003 : 4:37:39 PM
|
I know several people have experienced USB-related crashes under Linux. I'm working with a USB developer to try to isolate the bug, whether it's in Linux or in the Neuros device.
If you've experienced this problem (see., e.g., bugs #367), please contact me so we can gather more data.
Thanks! |
Your quick response to this post: (0 total votes)
I agree (0%)
I disagree (0%)
|
|
|
Sean Starkey
Posting Mania
848 Posts |
Posted - 07/23/2003 : 5:29:58 PM
|
This happens to me all the time. 
Most of the time it just locks up the whole system for 30-60 secs, but recovers. Occasionally it locks up completely and I have to do a hardware reset.
Sean Starkey - Project Manager for Neuros Database Manipulator - http://neurosdbm.sourceforge.net |
Your quick response to this post: (1 total votes)
I agree (100%)
I disagree (0%) |
 |
|
|
Craig
Posting is for Closers
82 Posts |
Posted - 07/24/2003 : 08:59:09 AM
|
| I also get constant lockups but I didn't know anyone else was. This is on a 2.4.20 SMP kernel. I've also gotten kernel panics on a number of occasions but running mount in sync mode seems to have helped. Also, I've noticed that lockups for me only occur during long file transfers. |
Your quick response to this post: (0 total votes)
I agree (0%)
I disagree (0%) |
|
|
|
slestak(at)cavtel.net
Posting is for Closers
53 Posts |
Posted - 07/24/2003 : 12:16:54 PM
|
I use gentoo-sources 2.4.20r5 I think (from memory). Just for the record, I have not had any lockups with this machine (its the only machine I use to add software to my neuros, using Positron.
I got one large lockup on a family members computer, but that was under XP Home while transferring a large ISO to disk using windows explorer. I was on battery power, but I had plenty. Note to self, dont copy 650 MB files on battery power.
Edited:
Hopefully with USB2, we'll see less of this since technically, an ISO can be copied much faster, so the overral time the machine is stressing will be shorter. |
Edited by - slestak(at)cavtel.net on 07/24/2003 12:18:55 PM |
Your quick response to this post: (0 total votes)
I agree (0%)
I disagree (0%) |
|
|
|
kgiverson
Just Posting
4 Posts |
Posted - 07/24/2003 : 9:13:23 PM
|
I've used my Neuros on two different Linux boxes with a range of results.
The first is an Athalon SMP machine that was initially running 2.4.18 and has OHCI USB. The Neuros would consistently lock up and cause the machine to lock up. I upgraded to 2.4.21 and after the upgrade the Neuros would still lock up, but it would no longer lock up the machine.
The second is a single processor pentium III with UHCI USB initially running 2.4.9 and using the usb-uhci kernel module. I had a couple of machine lock ups, but mostly just got "file system is read only" errors.
I upgraded to 2.4.21 which took care of the read only issues, but I still had some machine lock ups. I saw another post here about switching from usb-uhci to uhci, tried it and have not had an issue since. |
Your quick response to this post: (0 total votes)
I agree (0%)
I disagree (0%) |
|
|
|
qvack_82
Posting is for Closers
79 Posts |
Posted - 07/24/2003 : 10:22:28 PM
|
Here's My experiences with the Neuros under Linux.
linux-2.4.20, uhci. Neuros locks up, kernel has all sorts of errors that I don't understand.
linux-2.4.21, uhci. No worries at all, IF you wait for 10 seconds after turning off the neuros before plugging my USB cable in. If I don't wait, i get 'attempted access past end of device' errors.
linux-2.6.0-test1, uhci. Neuros goes through the Syncronization thing, with the animated icon, then stops, as normal. Linux hasn't recognised the neuros at all, no 'new usb device detected' or 'mass storage device found' etc. etc.
The most significant thing is to add a sync flag to your mount. ie
mount -t vfat -o sync /dev/sda1 /mnt/neuros
or
/etc/fstab
/dev/sda1 /mnt/neuros vfat user,noauto,sync 0 0
this means that there is no buffering, and writes will be immediatly committed to the neuros disk.
Hope this helps.
Cheers
Paul
ln -s /dev/null ~/.sig |
Your quick response to this post: (2 total votes)
I agree (100%)
I disagree (0%) |
|
|
|
alecm
Posting Profoundly
117 Posts |
Posted - 07/25/2003 : 12:25:41 PM
|
| My experiences are similar. For me, switching from the usb-uhci driver to the uhci driver made a huge difference. The occasional loss of system interactive response (frozen pointer for some seconds) that remained was fixed by mounting with the sync option. I'm running 2.4.21 SMP enabled. |
Your quick response to this post: (0 total votes)
I agree (0%)
I disagree (0%) |
|
|
|
enry
Posting is for Closers
51 Posts |
Posted - 07/28/2003 : 08:07:46 AM
|
| Please be sure your machine has the latest BIOS on it. There are cases where there will be USB firmware changes that can fix the problem. |
Your quick response to this post: (0 total votes)
I agree (0%)
I disagree (0%) |
|
|
|
qvack_82
Posting is for Closers
79 Posts |
Posted - 07/29/2003 : 10:07:10 PM
|
some more luck with 2.6.0-test2
uhci-hcd, usb-storage, sd_mod.
dmesg says that the Neuros is recognised, and assigned to sda, and that's all, no /dev/sda1, no /dev/scsi/*. and then any modprobe/rmmod/lsmod execution locks up that terminal solid, a reboot then segfaults :o)
hooray for development kernels :o)
Cheers
Paul
ln -s /dev/null ~/.sig |
Your quick response to this post: (0 total votes)
I agree (0%)
I disagree (0%) |
|
|
|
adam(at)bostoncoop.net
Just Posting
5 Posts |
Posted - 07/29/2003 : 10:16:22 PM
|
I've had no trouble getting the device recognize with the 2.5/2.6 line of kernels, it's just that the process gets stuck after a while and there's no way of recovering it. I'm not sure why you haven't been able to even mount the device in 2.5/2.6, as that's never been a problem for me.
Here's the kernel configuration I used, in case it is helpful:
http://bostoncoop.net/adam/temp/config-2.6.0
In other news, it seems to work perfectly, or nearly perfectly, in 2.4.22, even though it failed terribly in 2.4.21. The only problem is that sometimes it takes a while to flush the buffer, but I think this is actually normal (and goes away if I mount the device -o sync). |
Your quick response to this post: (0 total votes)
I agree (0%)
I disagree (0%) |
|
|
|
MeatMyDemands
Just Posting
1 Posts |
Posted - 07/30/2003 : 12:35:09 PM
|
This is a big problem for me. I have tried 2.4.21 with both the regular and JE UHCI drivers. I have also tried the 2.6.0-test kernel. In all cases, the USB bus will hang when I try to do a positron rebuild or even just copy a large file (like, for instance, a firmware file). Using the sync option on the mount does not make the problem go away or reduce it notably.
I will mention here that my mainboard is a FIC SD11. I mention it because this mainboard has known chipset/implementation problems. One, for example, is the tendency to misbehave when trying to use UDMA with hard disks. I have not heard of USB problems with this mainboard, though.
My problem consists of a total hang of the USB subsystem. My USB mouse quits working, and does not come back. My system cannot even be shut down properly, because it hangs when trying to umount the neuros. I can reproduce this seemingly at will. |
Your quick response to this post: (0 total votes)
I agree (0%)
I disagree (0%) |
|
|
|
DocWhat
Posting is for Closers
30 Posts |
Posted - 08/02/2003 : 11:39:05 AM
|
I have a question: Does anyone with these locks use a new version ALSA? I discovered reciently that the newer versions of ALSA can cause corruptions of the PCI bus. That'll cause USB to lock up or even the whole machine.
If you do have alsa, try disabling it and preventing it from loading *any* modules. Then reboot and try using the neuros.
Ciao!
Neuros Order #2553 |
Your quick response to this post: (0 total votes)
I agree (0%)
I disagree (0%) |
|
|
|
alecm
Posting Profoundly
117 Posts |
Posted - 08/03/2003 : 1:30:23 PM
|
I'm using ALSA 0.9.2 under 2.4.21 (SMP) with the JE drivers and the sync mount option. I have had no problems whatsoever with this setup.
Alec |
Your quick response to this post: (0 total votes)
I agree (0%)
I disagree (0%) |
|
|
|
bitboy
Posting is for Closers
25 Posts |
Posted - 09/09/2003 : 3:28:52 PM
|
Hi, all,
I don't know if you are still looking for victims^Wvolunteers, but I'm also having the same lockup problems (posted in another thread) with firmware 1.40 and Positron 1.0.
I'll be happy to assist in troubleshooting in any way I can.
Thanks again for all the hard work,
Brian |
Your quick response to this post: (0 total votes)
I agree (0%)
I disagree (0%) |
|
|
|
adam(at)bostoncoop.net
Just Posting
5 Posts |
Posted - 09/09/2003 : 3:59:37 PM
|
quote:
Originally posted by bitboy
I don't know if you are still looking for victims^Wvolunteers, but I'm also having the same lockup problems (posted in another thread) with firmware 1.40 and Positron 1.0.
You might want to try kernel 2.4.22 if you can. My problems were 95% fixed with that kernel, although some of them come back with 2.6.0test*.
Also, I assume you've seen the advice of mounting the device sync (mount -o sync or add sync to mount options in /etc/fstab). |
Your quick response to this post: (0 total votes)
I agree (0%)
I disagree (0%) |
|
|
|
bitboy
Posting is for Closers
25 Posts |
Posted - 09/16/2003 : 08:11:28 AM
|
Greetings, all.
Finally had the time to finish my upgrade to kernel 2.4.22 last night and it did fix the problems I was having with USB timeouts. Thanks for the suggestion.
Brian |
Your quick response to this post: (0 total votes)
I agree (0%)
I disagree (0%) |
|
|
|
Toojays
Just Posting
6 Posts |
Posted - 10/14/2003 : 06:18:02 AM
|
My two cents on this.
I only got my Neuros today, and before that I hadn't tried using any USB devices on this computer. Anyway, it took me a while to get it working consistently. I wasn't getting full system lockups, but the Neuros would freeze, and it seemed as though there was some kind of lockup in the kernel module---I could not rmmod usb-storage or unmount the Neuros. When I tried to umount, the shell I was in would freeze up . . . even "killall -KILL umount" from another shell wouldn't work, nor would a "reboot", even though I could click around KDE and use other programs with no problems.
Anyway, it looks to be working now. The difference (I think) is with the options to the usb-storage module. In the kernel menuconfig, under "USB Mass Storage Support", it has a bunch of sub-options about debugging, CF readers, bridges, etc. On my first try to get things working, it had not selected any of these. After comparing it to my dad's computer, which did seem to work, I selected _all_ of the suboptions. Now it seems to work fine.
This is with a K7S5A motherboard, kernel 2.4.20-gentoo-r7, usb-ohci. |
Your quick response to this post: (0 total votes)
I agree (0%)
I disagree (0%) |
|
|
|
Toojays
Just Posting
6 Posts |
Posted - 10/15/2003 : 05:39:34 AM
|
Grrr,
Scratch that last post . . . it just did it again, so I have not fixed the problem (but perhaps made it less obvious). |
Your quick response to this post: (0 total votes)
I agree (0%)
I disagree (0%) |
|
|
|
ExecutorElassus
Likes to Post
13 Posts |
Posted - 02/10/2004 : 12:56:57 PM
|
So, i'm running 2.4.21-166, on SuSE 9.0, with uhci and ehci-hcd running as modules. neuros firmware is 1.40. i have three VIA usb2 hubs on the motherboard, and SuSE reports that they're working properly (i have a zip drive and a joystick on one hub, and both work perfectly).
when i plug the neuros in, the "synchronization" window pops up, but the animation freezes almost immediately. sometimes the computer beeps (when it detects a new device) and sometimes not. in all cases, once the neuros is frozen, the kernel doesn't see it as a device, and i can't mount it.
any idea why this would freeze? should i install the 2.6 kernel? i could use the neuros perfectly before i upgraded the motherboard (the old one had built-in usb1.1), so i'm guessing this is a kernel problem.
hope someone can help! i haven't been able to use the neuros since november or so.
thanks,
EE |
Your quick response to this post: (0 total votes)
I agree (0%)
I disagree (0%) |
|
|
|
kronin
Posting Mania
1144 Posts |
Posted - 02/10/2004 : 1:05:12 PM
|
quote:
Originally posted by ExecutorElassus
So, i'm running 2.4.21-166, on SuSE 9.0, with uhci and ehci-hcd running as modules. neuros firmware is 1.40. i have three VIA usb2 hubs on the motherboard, and SuSE reports that they're working properly (i have a zip drive and a joystick on one hub, and both work perfectly).
Did you try booting with no other USB devices attached, then try plugging in the Neuros? Also, are you getting any output at all in /var/log/messages? |
Your quick response to this post: (1 total votes)
I agree (100%)
I disagree (0%) |
|
|
|
BuddhaTigger
Likes to Post
15 Posts |
Posted - 02/12/2004 : 10:17:16 AM
|
I'm also experiencing problems with the Neuros and Linux (Fedora 2.4.22-1.2149.nptl). It usually locks up when unmounting. But I think it (the Neuros) locks up after syncing the new songs onto it using NDBM. When it locks up I see something like lost interrupt in dmesg. To make matters worse that USB is sharing the same IRQ with the ethernet (just found that out, btw it also gets a lost interrupt)! I'll remove all the USB devices to limit what I'm seeing. Any suggestions on what to look for or what other info I should get?
[Edited March 8, 2004]
I'm now able to mount and write to the disk with ndbm. Unfortunately I still had problems with my system after I umounted the neuros. I tried to mount it again the neuros and the mount command hung.
Thanks
|
Edited by - BuddhaTigger on 03/08/2004 5:04:50 PM |
Your quick response to this post: (0 total votes)
I agree (0%)
I disagree (0%) |
|
|
|
Topic |
|
Forum Locked
Topic Locked
