Unsolved

This post is more than 5 years old

10 Posts

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

38 Posts

November 22nd, 2006 17:00

Duli, Did you try booting one of the other kernels (from grub)?
You can change boot parameters by typing "a" in the grub boot
menu when you have the kernel highlighted. You can then change
params. Try "nosmp noapic" or "maxcpus=1".

13 Posts

November 23rd, 2006 02:00

It's a shame this has been open for a month now and we're no closer to a resolution. We're about to embark on another round of hardware purchases and I think we'll be looking elsewhere...

31 Posts

November 23rd, 2006 10:00



mwette wrote:
Duli, Did you try booting one of the other kernels (from grub)?
You can change boot parameters by typing "a" in the grub boot
menu when you have the kernel highlighted. You can then change
params. Try "nosmp noapic" or "maxcpus=1".


Hi, mwette. I don´t have other kernels in grub because anaconda has installed the i586 kernel. Then, I did a "hard" replace with the i686, which is the only option now. Yes, I tried to boot with different options, but none is working anymore (which is a clear sign of instability, because previuously it was working with "noapic" ). I´ve tried with apci=off, nolapic, noapic.... No success. It just stops. The machine is not at my home, that´s why it takes so long for me to perform tests. But this weekend I´ll bring it home and I´ll make a fresh install and do a lot of tests and place here the outputs, in the name of the hope someone fixes these problems! Thanks a lot for your help!

Message Edited by Duli on 11-23-200606:00 AM

Message Edited by Duli on 11-23-200606:01 AM

November 23rd, 2006 11:00

I have the same problem after installing Windows 2000 professional NL (dutch) version on it.
Mouse hangs after a while, keyboard is still working then.

31 Posts

November 23rd, 2006 11:00



Eduard_MMI wrote:
I have the same problem after installing Windows 2000 professional NL (dutch) version on it.
Mouse hangs after a while, keyboard is still working then.


Did you install the windows drivers avaiable from dell´s website? I think it solves the problem.

November 23rd, 2006 12:00

Had the same problem under Windows 2000 prof dutch version. Found a workaround by using a PS2 mouse in combination with a PS2/USB converter.

38 Posts

November 23rd, 2006 13:00

Folks,

I found a nVidia forum thread which has a lot of discussion about nforce 430 issues.
In particular, there is a post which addresses my timer issue.

Also, I found this in the current kernel (arch/x86_64/io_apic.c):

/* Temporary Hack. Nvidia and VIA boards currently only work with IO-APIC
off. Check for an Nvidia or VIA PCI bridge and turn it off.
Use pci direct infrastructure because this runs before the PCI subsystem.

Can be overwritten with "apic"

And another hack to disable the IOMMU on VIA chipsets.

... and others. Really should move this somewhere else.

Kludge-O-Rama. */

31 Posts

November 23rd, 2006 13:00

Hi, All.
 
Did you guys consider about returning the computer to dell?
 
I don´t know about your countries, but here in mine (Brazil), people has seven days, from the day one receives the product bought via internet, to ask for return the product, without any justification, as long as it´s done within seven days. And they have to return your money, with proper monetary correction. It´s the law here (Consumer Protection Code). If you have similar legislation, I suggest you do the same.
 
I think that would at least call dell´s attention to the problem.
 
I think it´s unfair the problem was quickly resolved for windows, and for linux they just ignore it.
 
Cheers!
Duli

Message Edited by Duli on 11-23-200610:13 AM

November 23rd, 2006 14:00

In fact I did install the drivers from the Dell website.
However the way Dell presents the drivers for operating systems other then Windows XP is confusing.
For Windows XP everything is there, but for Windows 2000 on the other hand the list of drivers is not complete.
Many of them have to be downloaded from the Windows XP section and then you just have to try if the driver can be installed under Windows 2000.
 

Message Edited by Eduard_MMI on 11-23-200610:09 AM

1 Message

November 24th, 2006 08:00

A bios update should be developed immediatley.
 
Paying all this money for a pc that doesnt work properly is unacceptable. Ive been trying to get gentoo to work, but Ive had many problems with the usb and sound.
 
I'll be writing to dell to complain.

31 Posts

November 24th, 2006 10:00



Ollie7 wrote:
A bios update should be developed immediatley.
 
Paying all this money for a pc that doesnt work properly is unacceptable. Ive been trying to get gentoo to work, but Ive had many problems with the usb and sound.
 
I'll be writing to dell to complain.


Ollie, please, post a copy of the letter here. I´ll use it as a base to do the same here. They hava a huge factory here in Brazil and sure sale a lot here. I´ll write them. 

31 Posts

November 24th, 2006 10:00



Eduard_MMI wrote:
In fact I did install the drivers from the Dell website.
However the way Dell presents the drivers for operating systems other then Windows XP is confusing.
For Windows XP everything is there, but for Windows 2000 on the other hand the list of drivers is not complete.
Many of them have to be downloaded from the Windows XP section and then you just have to try if the driver can be installed under Windows 2000.
 

Message Edited by Eduard_MMI on 11-23-200610:09 AM



Sure. I really don´t understand why Dell and most companies still think everybody uses only windows xp. Okay, it´s a nice OS for most of people who don´t know a bit about computers, but I think they should face the reality and start paying attention tho the consumer demands.
 
Intel, for instance, a great company, has implemented a policy of linux compatibility, as you can see in their site:
 
 
"...

Get Started Now
The Intel Quick Start Kit v2.0 for Linux is a PC platform integration kit that provides a collection of software drivers, documentation, and tools to help Intel channel members design, build and sell Intel-based desktops using the Linux* operating system. Order your Free CD or download your specific Distribution files now from the links below:

It´s about time all computer industries start taking some part on this issue.
 
Cheers,
Duli

31 Posts

November 26th, 2006 18:00


@mwette wrote:
It is interesting that you are using "noapic". Can you list the
output of "cat /proc/interrupts" ? I'm interested to see how INT0
is mapped.


This is what I get booting with default install FC6 boot options (without the "noapic" option):

[root@localhost ~]# uname -rm
2.6.18-1.2798.fc6 i686
[root@localhost ~]# cat /proc/interrupts
CPU0
0: 124302 XT-PIC timer
8: 1 IO-APIC-edge rtc
9: 0 IO-APIC-level acpi
50: 1060 IO-APIC-level eth0
209: 9701 IO-APIC-level ohci_hcd:usb1, HDA Intel
217: 506 IO-APIC-level ehci_hcd:usb2
225: 15354 IO-APIC-level libata
233: 0 IO-APIC-level libata
NMI: 0
LOC: 124241
ERR: 1
MIS: 0

This is what I get when booting with "noapic" option:

[root@localhost ~]# uname -rm
2.6.18-1.2798.fc6 i686
[root@localhost ~]# cat /proc/interrupts
CPU0
0: 24377 XT-PIC timer
2: 0 XT-PIC cascade
5: 686 XT-PIC ohci_hcd:usb1, eth0
8: 1 XT-PIC rtc
9: 0 XT-PIC acpi
10: 0 XT-PIC libata
11: 9188 XT-PIC libata, HDA Intel
15: 504 XT-PIC ehci_hcd:usb2
NMI: 0
LOC: 24546
ERR: 1

In both cases mouse freezes and sound does not work with alsa.

Duli

Message Edited by Duli on 11-26-200602:46 PM

Message Edited by Duli on 11-27-200609:54 AM

38 Posts

November 27th, 2006 18:00

Here is the Ubuntu thread.

31 Posts

November 27th, 2006 18:00

For those using Fedora Core 6, there's a bug report here:
 
 
Duli

0 events found

No Events found!

Top