Ticket #2999 (closed bug: duplicate)

Opened 2 months ago

Last modified 2 months ago

System deadlock when connecting USB devices with ipro100 driver

Reported by: RandomInsano Owned by: axeld
Priority: normal Milestone: R1
Component: Drivers/Network Version: R1 development
Cc: edwinguy+haiku@… Blocked By: #2048
Platform: x86 Blocking:

Description

When I plug in any device into my Compaq Armada M700s USB port the system gets stuck in the fpx interrupt handler during boot (I can see this by getting into the KDL with F12) and the system completely locks up if I do this once the system is booted.

Unplugging the device again doesn't bring the system back into a usable state and it doesn't matter what class of device I use (Several Mass Storage devices, Mouse, Keyboard, Ethernet have been tested).

If I delete the ipro100 device driver the system no longer has this problem, though there are further problems with trying to mount USB mass storage as writable, but that's another story.

The problem also exists on an old Compaq Deskpro. I've tested with many revisions up to 28350 and have never had luck with using USB devices on either system.

Attachments

DSCN2404.JPG (145.5 KB) - added by RandomInsano 2 months ago.
Sticking Point
DSCN2405.JPG (151.7 KB) - added by RandomInsano 2 months ago.
KDL Launched
DSCN2406.JPG (164.4 KB) - added by RandomInsano 2 months ago.
KDL Threads

Change History

Changed 2 months ago by RandomInsano

Sticking Point

Changed 2 months ago by RandomInsano

KDL Launched

Changed 2 months ago by RandomInsano

KDL Threads

Changed 2 months ago by axeld

  • component changed from Drivers to Drivers/Network

It's the ipro100 driver with each system? Also, the "ints" KDL command would be helpful, too.

Changed 2 months ago by umccullough

At least the ipro100 problem is already reported in #2084 for reference.

Changed 2 months ago by RandomInsano

It is the ipro100 driver in both. The issue is only when USB devices are attached however, so perhaps I'll just add my information to bug #2084 instead

Changed 2 months ago by RandomInsano

This does appear to be a duplicate bug. I'm copying my information over to bug #2084

Changed 2 months ago by axeld

  • status changed from new to closed
  • resolution set to duplicate
  • blockedby set to 2048

No need to, I just mark this as a duplicate.

Note: See TracTickets for help on using tickets.