From John Jason Jordan <[EMAIL PROTECTED]>:
> Compaq R3240, Ubuntu Edgy amd64

I also have an R3240, but I'm running 32-bit Kubuntu because I sick of 
fighting with browser plugins. :(

> I started with Ubuntu Hoary, then Breezy, then Dapper, and now have
> Edgy, all 64-bit. I have had a problem since the beginning making
> backups to an external USB disk. Whether I use tar, dar or rsync the
> computer will lock up somewhere in the middle of the backup. It will
> also sometimes lock up when doing a lot of file deletions on the USB
> disk, e.g., to delete an old backup set.

I don't use rsync to the flash drives ... it reads the entire file and 
calculates checksums, then updates only the portions that need updating.  
This means 100% of the file must be read and then some X% must be 
written.  I've figured it's probably faster to just write 100% and be 
done with it.  Note that this could hurt the lifetime of the flash 
memory, though (they are write-cycle limited).  I haven't done any 
real-world simulations of this to determine the trade-offs.

> [   42.278295] usbcore: registered new driver ndiswrapper
>
> So it appears that there may be a problem with ACPI. I am wondering if
> the USB driver uses an IRQ that is being shared with something else. I
> haven't tried pci=assign-busses or pci=routeirq yet because I thought
> I'd ask here first if anyone else has encountered similar problems.

I have had the 32-bit Debian kernel (2.6.17) also mention 
the "pci=assign-busses".  The SUSE 10.0 kernel (which I think was 2.6.9, 
IIRC) never produced that message.

I also use an external drive (two, actually; one is 40GB and the other is 
20GB) and have not experienced any lockups.  And I am always sucking 
video from my Series2 TiVo, unlocking the mpeg2 stream, then transcoding 
it to an mpeg4 AVI.  These large files (typically about 1.7GB per 
2-hours) are then moved back and forth to the USB drives.  Long-term 
storage is on the external drive, but before I take a business trip, I'll 
copy a few of them back to the internal drive so that I don't need the 
external hooked up to watch Battlestar Galactica or Heroes or ...

However, I _have_ had lockups using the ndiswrapper module, which I 
noticed you also have installed (it's lucky that you included that 
line!).  I never had a problem under 64-bit SUSE when I grabbed the 
source for ndiswrapper and built it myself, but I have sporadic lockups 
whenever I use the wireless under 32-bit Kubuntu.  I have not looked into 
this in detail yet, since I haven't *needed* the wireless, but I will 
likely start on this problem in the next week or two, as I start 
traveling again (hotels like wireless, since the infrastructure for it is 
easier than wired (sigh)).

> Any suggestions welcome.

Try the "assign-busses" and let us know if that solves the problem.  If it 
doesn't, I'd try leaving out the ndiswrapper and see if that helps.

PS: Have you used ndiswrapper on all of your previous installs as well?  
Has it always been from a binary repository, ie. have you ever built it 
from source?

I wish you the best of luck!
-- 
Frank J. Edwards
Edwards & Edwards Consulting, LLC
Voice: (813) 996-7954
Email: [EMAIL PROTECTED]
Large Attachments To: [EMAIL PROTECTED]

Attachment: pgpgnluBimSbg.pgp
Description: PGP signature

_______________________________________________
LinuxR3000 mailing list
[email protected]
http://lists.pcxperience.com/cgi-bin/mailman/listinfo/linuxr3000
Wiki at http://prinsig.se/weekee/

Reply via email to