On Fri, Apr 26, 2002, Dave C. <[EMAIL PROTECTED]> wrote:
> [sorry for the dual send; formatting got hosed up the 1st time]
> 
> PROBLEM: The module usb-uhci consistantly causes Windows 2K
>          booting to fail when doing a warm reboot from Linux into 
>          Windows 2000.  
[snip]
> [2.] Full description of the problem/report:
> 
>         SHORT VERSION
>                 The module usb-uhci consistantly causes Windows 2000
>         booting to fail when doing a warm reboot (aka: 
>         shutdown -r, init 6, ctrl-alt-delete) from Linux into 
>         Windows 2000 in my environment.  During the Windows 2000 boot, 
>         the system hangs.
>                 When the usb-uhci module is removed (rmmod usb-uhci) 
>         prior to the warm reboot, Windows boots fine.
>                 KERNEL: I'm using the most recent stable kernel 
>         (2.4.18) compiled under a fresh install of Red Hat 7.2
>                   ALT DRIVER: I have tried the 'uhci' (alt) module 
>         as well.  The uhci seemed to exhibit the same behavior, but
>         I didn't do the same amount of testing so I'm not including
>         it in the problem description.
>                  See the end of this doc for a workaround.
[snip]
>               (PCI) 11 Intel 82371AB/EB PCI to USB Universal Host Controller
>               (PCI) 11 NeoMagic MagicMedia 256AV Audio Driver(WDM)
[snip]
>         00:07.2 USB Controller: Intel Corporation 82371AB PIIX4 USB (rev 01)
> (prog-if 00 [UHCI])
>                 Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop-
> ParErr- Stepping- SERR- FastB2B-
>                 Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
> <TAbort- <MAbort- >SERR- <PERR-
>                 Latency: 64
>                 Interrupt: pin D routed to IRQ 11
>                 Region 4: I/O ports at fce0 [size=32]
[snip]
>         01:00.1 Multimedia audio controller: Neomagic Corporation [MagicMedia
> 256AV Audio] (rev 12)
>                 Subsystem: Dell Computer Corporation MagicMedia 256AV Audio
> Device on Colorado Inspiron
>                 Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop-
> ParErr- Stepping- SERR- FastB2B+
>                 Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
> <TAbort- <MAbort- >SERR- <PERR-
>                 Interrupt: pin B routed to IRQ 11
>                 Region 0: Memory at fe000000 (32-bit, prefetchable) [size=4M]
>                 Region 1: Memory at fe700000 (32-bit, non-prefetchable) [size=1M]
>                 Capabilities: [dc] Power Management version 1
>                         Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA
> PME(D0-,D1-,D2-,D3hot-,D3cold-)
>                         Status: D0 PME-Enable- DSel=0 DScale=0 PME-

Wow, that's one of the most verbose bug reports I have ever seen.

Well, the only difference between a warm reboot and unloading the
driver, is that we stop the host controller when the driver gets
unloaded.

What I suspect is happening is that we don't stop the HC when Linux
reboots and an event that would trigger an interrupt occurs. When
Windows gets around to booting, it unmasks interrupt 11 and it floods
the system and it won't stop.

Can you try unplugging all of your devices and then rebooting the
system and see if it still hangs?

Anyway, I think the kernel should probably call the remove function
for all of the PCI devices before it reboots.

JE


_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-users

Reply via email to