Re: USB related commit leads to hung systems if USB-IRQ=Disabled in BIOS

2000-12-06 Thread Mike Smith

 
 In my bios I have PnPOS=NO, USB-IRQ=Disabled.
 
 The commit below results in a PCI interrupt storm and a terminally
 wedged system right after interrupts are enabled.

This would be a bug in the UHCI or OHCI driver then.  You can avoid it by 
not running the driver.

 Poul-Henning
 
 | nsayer  2000/12/03 09:07:24 PST
 | 
 |   Modified files:
 | sys/pci  ohci_pci.c uhci_pci.c
 |   Log:
 |   We now have the ability to assign the correct IRQ when PNP-OS is turned
 |   on. So stop failing the attach if the IRQ is unassigned. With this
 |   patch, I can now boot with PNP-OS YES in my BIOS no differently than
 |   PNP-OS NO (which is a good thing since Windows hangs with PNP-OS NO).
 |  
 |   Obtained from:msmith
 |  
 |   Revision  ChangesPath
 |   1.21  +1 -11 src/sys/pci/ohci_pci.c
 |  1.32  +1 -11 src/sys/pci/uhci_pci.c
 
 --
 Poul-Henning Kamp   | UNIX since Zilog Zeus 3.20
 [EMAIL PROTECTED] | TCP/IP since RFC 956
 FreeBSD committer   | BSD since 4.3-tahoe
 Never attribute to malice what can adequately be explained by incompetence.
 
 
 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with "unsubscribe freebsd-current" in the body of the message
 

-- 
... every activity meets with opposition, everyone who acts has his
rivals and unfortunately opponents also.  But not because people want
to be opponents, rather because the tasks and relationships force
people to take different points of view.  [Dr. Fritz Todt]
   V I C T O R Y   N O T   V E N G E A N C E




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: USB related commit leads to hung systems if USB-IRQ=Disabled in BIOS

2000-12-06 Thread Mike Smith

  
  In my bios I have PnPOS=NO, USB-IRQ=Disabled.
  
  The commit below results in a PCI interrupt storm and a terminally
  wedged system right after interrupts are enabled.
 
 This would be a bug in the UHCI or OHCI driver then.  You can avoid it by 
 not running the driver.

I should have mentioned; you can probably also avoid it by letting your 
BIOS give the USB controller an IRQ, since it'll almost certainly also 
perform whatever initialisation the driver is currently missing out on.

-- 
... every activity meets with opposition, everyone who acts has his
rivals and unfortunately opponents also.  But not because people want
to be opponents, rather because the tasks and relationships force
people to take different points of view.  [Dr. Fritz Todt]
   V I C T O R Y   N O T   V E N G E A N C E




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: USB related commit leads to hung systems if USB-IRQ=Disabled in BIOS

2000-12-06 Thread Poul-Henning Kamp

In message [EMAIL PROTECTED], Mike Smith writes:
  
  In my bios I have PnPOS=NO, USB-IRQ=Disabled.
  
  The commit below results in a PCI interrupt storm and a terminally
  wedged system right after interrupts are enabled.
 
 This would be a bug in the UHCI or OHCI driver then.  You can avoid it by 
 not running the driver.

I should have mentioned; you can probably also avoid it by letting your 
BIOS give the USB controller an IRQ, since it'll almost certainly also 
perform whatever initialisation the driver is currently missing out on.

Right, that is what I did once I realized that this particular commit
was the culprit.

--
Poul-Henning Kamp   | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer   | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: USB related commit leads to hung systems if USB-IRQ=Disabled in BIOS

2000-12-06 Thread Mike Smith

 I should have mentioned; you can probably also avoid it by letting your 
 BIOS give the USB controller an IRQ, since it'll almost certainly also 
 perform whatever initialisation the driver is currently missing out on.
 
 Right, that is what I did once I realized that this particular commit
 was the culprit.

The commit isn't (really) the culprit; it's just exposed a bug in the USB 
chipset driver in question.  (I'm mostly just making this point so that 
other people don't go blaming 'correct' PCI behaviour for their problems 
8).

-- 
... every activity meets with opposition, everyone who acts has his
rivals and unfortunately opponents also.  But not because people want
to be opponents, rather because the tasks and relationships force
people to take different points of view.  [Dr. Fritz Todt]
   V I C T O R Y   N O T   V E N G E A N C E




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message