usb_webcam.media_addon and firewire_dv.media_addon makes system freeze on Acer Travelmate 6460

[vegardw]

Summary

I have a Acer Travelmate 6463WLMi that I tried to install Haiku on.

If either usb_webcam.media_addon or firewire_dv.media_addon (or both of the) is included in the image, Haiku freezes/becomes unresponsive. Some times I also get thrown into KDL after a few minutes.

Steps to reproduce

• Compile Haiku GCC2 version and install in real partition on a Travelmate 6460 series notebook.
• Reboot notebook and boot Haiku

Expected results

Haiku boots normal on the notebook

Actual results

Haiku boots, but when starting the media_server the system freezes. Sometimes, after a while you get thrown into KDL

Reproducibility

• Freezing: Always, happens on every boot.
• KDL: Not always

Work around

To get Haiku to boot on the notebook I had to either remove both usb_webcam.media_addon and firewire_dv.media_addon from "build/jam/HaikuImage" or change the bootscript to not start the media_server.

Testet on

• Haiku hrev29362
• GCC2 version, compiled on Ubuntu Linux 8.10
• Installed on real partition, running on real HW

Hardware

Acer Travelmate 6463WLMi notebook, P/N LX.TED06.057 with the following specs:

• Intel Core 2 Duo T5500 CPU
• Intel 945 PM chipset (i945PM)
• 2x1GB PC2-4300 SODIMM
• Ati Mobility Radeon X1300 128MB/256MB Hypermemory
• Notebook has built-in USB webcam
• Notebook has firewire controller/firewire port

Additional

If any of the two addons are enabled, the following is printed constantly to the serial log:

ide: ide_timeout() bus 0x80fb5a5c
ide: ide_timeout_dpc() bus 0x80fb5a5c, device 0x81796e80
ide: reset_device() device 0x81796e80
ide: reset_device() device 0x81796e80 success
More than 99% interrupts of vector 11 are unhandled

and

ide: reset_device() device 0x81796aa0
ide: reset_device() device 0x81796aa0 failed, calling reset_bus
ide: reset_bus() device 0x81796aa0, bus 0x80fb5990
More than 99% interrupts of vector 11 are unhandled
ide: reset_bus() device 0x81796aa0, bus 0x80fb5990 success
More than 99% interrupts of vector 11 are unhandled

along with a bunch of "Last message repeated XX times." messages.

With both addons removed these messages is not printed to the serial log.

Attached

Serial logs from booting with both addons, each addon seperate and without any addons

[vegardw]

with both addons

[vegardw]

with only webcam addon

[vegardw]

with only firewire_dv addon

[vegardw]

with both addons removed

[mmlr]

Can you please check what happens if you remove just the firewire bus_manager (either by removing it from the image or deleting it from /boot/beos/system/add-ons/kernel/bus_managers/firewire).

[vegardw]

With just the firewire bus_manager removed (both addons included) the system boots without problems, no freezes or ide_reset/ide_timeout messages in the serial console

[mmlr]

Then it seems to be an interrupt handling problem with firewire.

[korli]

This seems weird as both firewire controllers is on irq 10, though the unhandled interrupt is on irq 11. Also I don't know if it's well supported with two controllers.

[absabs]

IIRC, the stack support at most 4 controllers by default.

Very strange. As the log said, there is a firewire ohci controller TI TSB43AB22/A. Another is "vendor=1217, device=f7", it must be O2 Micro Inc's OHCI 1394 Controller. But as I google Acer Travelmate 6460 has only one firewire port. It is crazy to integrate two firewire ohci chip in notebook.

vegardw, would you please to check how many firewire chips are there in your notebook under windows or linux?

[korli]

lspci for this Travelmate 6460: ​http://www.linuxquestions.org/questions/linux-newbie-8/acer-travelmate-6460-wireless-problem-664786/

At least there is something wrong with either HDA or USB as they are the sole users of IRQ 11. To me, the "only firewire dv addon" test is weird in this respect.

[vegardw]

attached screenshot of windows xp device manager (sorry for the norwegian windows)

There are two firewire host controllers shown? There are two entries in the device manager under "IEEE 1394 Host Controllers" at least. One is called "OHCI compatible IEEE 1394 host controller", the other is called "Texas Instruments OHCI compatible IEEE 1394 host controller"

Since one of you mentioned something with O2Micro, the SD/MMC etc card reader is shown as "02Micro SmartCardBus Reader"

[vegardw]

dmesg output after booting Ubuntu

[vegardw]

lspci output from ubuntu

[vegardw]

also attached output from dmesg and lspci in Ubuntu

[absabs]

There are 2 firewire controllers. As the log said both use irq 10, but which device use irq 11? why reseting firewire controllers will trigger irq 11. Under linux I know cat /proc/interrupts can tell the detailed information about irq, while under haiku how can I know this?

[vegardw]

output of the "ints" command in the kdl with firewire bus_manager, usb_webcam.media_addon and firewire_dv.media_addon included in the image:

kdebug> ints
int   1, enabled 1, handled        1, unhandled        0, ACTIVE
        ps2:ps2_interrupt (0x80f365d0), data 0x00000000
int   7, enabled 1, handled        0, unhandled        0
        uhci:InterruptHandler__4UHCIPv (0x80749634), data 0x80f937fc
int  10, enabled 5, handled        2, unhandled        0
        firewire:fwohci_intr (0x8357bde4), data 0x81de1000
        firewire:fwohci_intr (0x8357bde4), data 0x81d29000
        uhci:InterruptHandler__4UHCIPv (0x80749634), data 0x80f93920
        uhci:InterruptHandler__4UHCIPv (0x80749634), data 0x80f936d8
        broadcom570x:intr_wrapper (0x807e778c), data 0x81028488
int  11, enabled 3, handled      411, unhandled  1602771
        oss:ossintr (0x848373e0), data 0x80fd67f8
        ehci:InterruptHandler__4EHCIPv (0x805f3ae4), data 0x80fa3550
        uhci:InterruptHandler__4UHCIPv (0x80749634), data 0x80f935b4
int  12, enabled 1, handled       20, unhandled        0
        ps2:ps2_interrupt (0x80f365d0), data 0x00000000
int  14, enabled 1, handled     4291, unhandled        0
        ide_adapter:ide_adapter_inthand (0x80614a74), data 0x80fbb038
int  15, enabled 1, handled       53, unhandled        1
        ide_adapter:ide_adapter_inthand (0x80614a74), data 0x80fbb070
int 219, enabled 1, handled    21462, unhandled        0
        kernel_x86:apic_timer_interrupt (0x800d2634), data 0x00000000
int 221, enabled 1, handled    59116, unhandled        0
        kernel_x86:i386_ici_interrupt (0x800cb978), data 0x00000000
int 222, enabled 1, handled        0, unhandled        0
        kernel_x86:i386_smp_error_interrupt (0x800cb9b0), data 0x00000000
int 223, enabled 1, handled        0, unhandled        0
        kernel_x86:i386_spurious_interrupt (0x800cb9a4), data 0x00000000

[modeenf]

Some changes have bean made to the fw_raw driver. Can you check again..

[vegardw]

Unfortunately I don't have the computer any longer, so I'm unable to re-check.

[modeenf]

Replying to vegardw:

Unfortunately I don't have the computer any longer, so I'm unable to re-check.

Ok I will close it for now. Re open this if the bug still exists.