Unsolved
This post is more than 5 years old
10 Posts
0
614717
October 19th, 2006 14:00
Linux USB Problems on Dimension E521 AMD 64 X2
Hi,
Anyone else try running Linux (in my case Ubuntu 6.06) on the E521 with the AMD 64 X2 processor? I am having a problem when using xorg where my USB devices, more often my mouse, but my keyboard has had the problem as well stops working. It is almost like the interrupts start getting masked, but it isn't that. Because when the mouse stops working I am usually able to still use the keyboard.
It happens after a while, and usually in times of heavy use. I guess really instead of heavy I would say normal. But it has never happened that it will be working and then I let it lay idle for a while and then reach for it again and it be frozen.
This started happening under the amd64 version of Ubuntu but I have tried several different versions by now and the problem continues to happen.
As far as troubleshooting it has been a real pain. There is never a message in the kernel log or shown by running dmesg. Actually once or twice I have seen the irq status -71 received, but I am pretty sure that is not the cause, becuase it has only happened about twice out of maybe 40 occurances. And there is no message in the Xorg log either.
I have tried the default amd64-generic kernel the latest amd64-generic, the latest amd64-k8 kernel (I think 2.6.15-27.48) I have tried running the i386 uniprocessor kernel and the latest k7-smp kernel. All of them have the same problem.
In an effort to get to the bottom of it I have re-compiled the kernel according to the directions here: http://doc.gwos.org/index.php/Kernel_Compilation_Dapper and turned on debugfs and collected data, but there doesn't seem to be anything of interest. It seems I get hundreds of thousands of lines of -115 status (Which I believe is the controller just telling the device that yeah, I hear ya and I am going to do something EINPROGRESS) and then nothing. The mouse appears to continue to function at least the circuit which senses movement and turns the LED into bright mode. And under Windows I have had no problems at all.
The only solution that always works is to disconnect the USB cable and then reconnect it, which grabs a new device file /dev/input/event7 and probably does some other magic registers with the USB controller, and a bunch of other stuff and then the mouse starts working again.
The only other consistent problem I have noted is the IOAPIC stuff complains about a bug, and sometimes it won't boot and panics, other times it figures out a way to get by and does so. Because of this I have tried booting with noapic and other than changing the way /proc/interrupts looks there seems to be no change in the problem. Eventually under usage the mouse stops responding entirely. Even looking at cat /dev/input/mice there is nothing getting there.
I have upgraded the BIOS to 1.0.3 that had no effect. And also turned off the Cool and Quiet support in the bios.
Any thoughts, recommendations of how to proceed, or any other suggestions are appreciated.
Thank you,
Kevin
Anyone else try running Linux (in my case Ubuntu 6.06) on the E521 with the AMD 64 X2 processor? I am having a problem when using xorg where my USB devices, more often my mouse, but my keyboard has had the problem as well stops working. It is almost like the interrupts start getting masked, but it isn't that. Because when the mouse stops working I am usually able to still use the keyboard.
It happens after a while, and usually in times of heavy use. I guess really instead of heavy I would say normal. But it has never happened that it will be working and then I let it lay idle for a while and then reach for it again and it be frozen.
This started happening under the amd64 version of Ubuntu but I have tried several different versions by now and the problem continues to happen.
As far as troubleshooting it has been a real pain. There is never a message in the kernel log or shown by running dmesg. Actually once or twice I have seen the irq status -71 received, but I am pretty sure that is not the cause, becuase it has only happened about twice out of maybe 40 occurances. And there is no message in the Xorg log either.
I have tried the default amd64-generic kernel the latest amd64-generic, the latest amd64-k8 kernel (I think 2.6.15-27.48) I have tried running the i386 uniprocessor kernel and the latest k7-smp kernel. All of them have the same problem.
In an effort to get to the bottom of it I have re-compiled the kernel according to the directions here: http://doc.gwos.org/index.php/Kernel_Compilation_Dapper and turned on debugfs and collected data, but there doesn't seem to be anything of interest. It seems I get hundreds of thousands of lines of -115 status (Which I believe is the controller just telling the device that yeah, I hear ya and I am going to do something EINPROGRESS) and then nothing. The mouse appears to continue to function at least the circuit which senses movement and turns the LED into bright mode. And under Windows I have had no problems at all.
The only solution that always works is to disconnect the USB cable and then reconnect it, which grabs a new device file /dev/input/event7 and probably does some other magic registers with the USB controller, and a bunch of other stuff and then the mouse starts working again.
The only other consistent problem I have noted is the IOAPIC stuff complains about a bug, and sometimes it won't boot and panics, other times it figures out a way to get by and does so. Because of this I have tried booting with noapic and other than changing the way /proc/interrupts looks there seems to be no change in the problem. Eventually under usage the mouse stops responding entirely. Even looking at cat /dev/input/mice there is nothing getting there.
I have upgraded the BIOS to 1.0.3 that had no effect. And also turned off the Cool and Quiet support in the bios.
Any thoughts, recommendations of how to proceed, or any other suggestions are appreciated.
Thank you,
Kevin
0 events found
No Events found!


ethelle
1 Message
0
January 7th, 2007 17:00
But I got some kernel panic and freeze now, DELL really s, I'm sure I will never buy another PC from them.
someone23
1 Message
0
January 8th, 2007 18:00
vincecate
11 Posts
0
January 9th, 2007 11:00
The mount does not work for me.
I tried mount /dev/sdb1 /mnt/usb
mount -t msdos /dev/sdb1 /mnt/usb
mount -t vfat /dev/sdb1 /mnt/usb
The first says I must specify the type. The others say wrong type. What type should it be?
Thanks,
-- Vince
batsy
6 Posts
0
January 9th, 2007 12:00
# wget http://www.offenders.org/freedos.img
# mkfs.msdos -I /dev/sdb
# dd if=freedos.img of=/dev/sdb (your pendrive device)
# mkdir /mnt/usb
# mount /dev/sdb /mnt/usb
# cp DME521-010104.EXE /mnt/usb
# umount /mnt/usb
Message Edited by batsy on 01-09-200708:16 AM
vincecate
11 Posts
0
January 10th, 2007 06:00
I think the dd wipes out what the mkfs does. I am on an Ubuntu AMD64 system.
fiestachickens
3 Posts
0
January 10th, 2007 12:00
mwette
38 Posts
0
January 10th, 2007 12:00
careful about using "sdb" versus "sdb1". I played with this
a bit. There are two ways to set up a USB card to boot. One
makes it look like a floppy, the other makes it look like a
real disk, with MBR and partition table. I believe the Dell
boxes want to see the filesystem version. Try the "dd" command
on /dev/sdb and then see if you can mount /dev/sdb1. I'm not
sure this freedos.img is workable.
Duli
31 Posts
0
January 10th, 2007 13:00
UNOmar
3 Posts
0
January 10th, 2007 14:00
-UNOmar
fiestachickens
3 Posts
0
January 10th, 2007 15:00
Have you tried a USB hub that has an external power source?
UNOmar
3 Posts
0
January 10th, 2007 17:00
jrminter
10 Posts
0
January 10th, 2007 19:00
jrminter
10 Posts
0
January 10th, 2007 19:00
donnyr3
5 Posts
0
January 11th, 2007 14:00
ajsoft
3 Posts
0
January 11th, 2007 14:00
I have the same but using Mandriva 2007 32 bit and all works fine with BIOS 1.1.4. This, of course, is consistent with what the SuSE users have reported. 32 bit works fine with BIOS 1.1.4. 64 bit still doesnt