* Weird bttv errors and video hangs with 2.4.2-ac21
@ 2001-03-22 19:20 Udo A. Steinberg
2001-03-22 19:57 ` Alan Cox
0 siblings, 1 reply; 3+ messages in thread
From: Udo A. Steinberg @ 2001-03-22 19:20 UTC (permalink / raw)
To: kraxel, Linux Kernel
Hi,
With -ac21 I'm getting occasional long delays in video output with xawtv
or the picture totally freezes until I click with the mouse in the xawtv
window. dmesg shows:
bttv0: PLL: 28636363 => 35468950 ... ok
bttv0: irq: OCERR risc_count=0fb54810
bttv0: irq: OCERR risc_count=0fb54810
bttv0: irq: OCERR risc_count=0fb54810
bttv0: irq: SCERR risc_count=0fb54810
bttv0: irq: SCERR risc_count=0fb54810
bttv0: aiee: error loops
bttv0: resetting chip
bttv0: PLL: 28636363 => 35468950 ... ok
bttv0: irq: OCERR risc_count=0fb54810
bttv0: irq: OCERR risc_count=0fb54820
bttv0: irq: OCERR risc_count=0fb54810
bttv0: irq: OCERR risc_count=0fb54810
bttv0: irq: SCERR risc_count=0fb54810
bttv0: aiee: error loops
bttv0: irq: SCERR risc_count=0c898014
bttv0: aiee: error loops
bttv0: resetting chip
bttv0: PLL: 28636363 => 35468950 ... ok
bttv0: irq: OCERR risc_count=0fb54810
All of this did not happen with -ac20 under the exact same circumstances,
so -ac21 does something which the bttv driver (0.7.57) doesn't quite like.
Regards,
Udo.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Weird bttv errors and video hangs with 2.4.2-ac21
2001-03-22 19:20 Weird bttv errors and video hangs with 2.4.2-ac21 Udo A. Steinberg
@ 2001-03-22 19:57 ` Alan Cox
2001-03-22 20:13 ` Udo A. Steinberg
0 siblings, 1 reply; 3+ messages in thread
From: Alan Cox @ 2001-03-22 19:57 UTC (permalink / raw)
To: Udo A. Steinberg; +Cc: kraxel, Linux Kernel
> With -ac21 I'm getting occasional long delays in video output with xawtv
> or the picture totally freezes until I click with the mouse in the xawtv
> window. dmesg shows:
You have a VIA chipset ?
> bttv0: resetting chip
> bttv0: PLL: 28636363 => 35468950 ... ok
> bttv0: irq: OCERR risc_count=0fb54810
>
> All of this did not happen with -ac20 under the exact same circumstances,
> so -ac21 does something which the bttv driver (0.7.57) doesn't quite like.
The only candidate I can think of is the pci quirk stuff added for the VIA
chipsets
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Weird bttv errors and video hangs with 2.4.2-ac21
2001-03-22 19:57 ` Alan Cox
@ 2001-03-22 20:13 ` Udo A. Steinberg
0 siblings, 0 replies; 3+ messages in thread
From: Udo A. Steinberg @ 2001-03-22 20:13 UTC (permalink / raw)
To: Alan Cox; +Cc: Linux Kernel
Alan Cox wrote:
>
> > With -ac21 I'm getting occasional long delays in video output with xawtv
> > or the picture totally freezes until I click with the mouse in the xawtv
> > window. dmesg shows:
>
> You have a VIA chipset ?
Yes. Via KT133.
lspci output under -ac20:
00:00.0 Host bridge: VIA Technologies, Inc.: Unknown device 0305 (rev 02)
Subsystem: Asustek Computer, Inc.: Unknown device 8033
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: 0
Region 0: Memory at e0000000 (32-bit, prefetchable) [size=128M]
Capabilities: [a0] AGP version 2.0
Status: RQ=31 SBA+ 64bit- FW+ Rate=x1,x2
Command: RQ=0 SBA- AGP- 64bit- FW- Rate=<none>
Capabilities: [c0] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00:01.0 PCI bridge: VIA Technologies, Inc.: Unknown device 8305 (prog-if 00 [Normal decode])
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: 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
I/O behind bridge: 0000e000-0000dfff
Memory behind bridge: d5000000-d65fffff
Prefetchable memory behind bridge: d7f00000-dfffffff
BridgeCtl: Parity- SERR- NoISA- VGA+ MAbort- >Reset- FastB2B-
Capabilities: [80] Power Management version 2
Flags: PMEClk- DSI+ D1+ D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00:04.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super] (rev 22)
Subsystem: Asustek Computer, Inc.: Unknown device 8033
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: 0
00:04.1 IDE interface: VIA Technologies, Inc. VT82C586 IDE [Apollo] (rev 10) (prog-if 8a [Master SecP PriP])
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: 32
Region 4: I/O ports at d800 [size=16]
Capabilities: [c0] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00:04.2 USB Controller: VIA Technologies, Inc. VT82C586B USB (rev 10) (prog-if 00 [UHCI])
Subsystem: Unknown device 0925:1234
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: 32, cache line size 08
Interrupt: pin D routed to IRQ 9
Region 4: I/O ports at d400 [size=32]
Capabilities: [80] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00:04.3 USB Controller: VIA Technologies, Inc. VT82C586B USB (rev 10) (prog-if 00 [UHCI])
Subsystem: Unknown device 0925:1234
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: 32, cache line size 08
Interrupt: pin D routed to IRQ 9
Region 4: I/O ports at d000 [size=32]
Capabilities: [80] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00:04.4 Host bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev 30)
Subsystem: Asustek Computer, Inc.: Unknown device 8033
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 ? routed to IRQ 9
Capabilities: [68] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
> > bttv0: resetting chip
> > bttv0: PLL: 28636363 => 35468950 ... ok
> > bttv0: irq: OCERR risc_count=0fb54810
> >
> > All of this did not happen with -ac20 under the exact same circumstances,
> > so -ac21 does something which the bttv driver (0.7.57) doesn't quite like.
>
> The only candidate I can think of is the pci quirk stuff added for the VIA
> chipsets
That is probably the problem then. If you have a patch, want me to try something or
need more info, just let me know.
Regards,
Udo.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2001-03-22 20:15 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2001-03-22 19:20 Weird bttv errors and video hangs with 2.4.2-ac21 Udo A. Steinberg
2001-03-22 19:57 ` Alan Cox
2001-03-22 20:13 ` Udo A. Steinberg
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®