[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#368490: linux-image-2.6.16-1-686: ohci1394 module panics and/or halts kernel



Package: linux-image-2.6.16-1-686
Version: 2.6.16-12
Severity: critical
Justification: breaks the whole system


machine: Toshiba tecra A4
AFAIK all tecras A4 and all satellite m40 models have the same hardware/bios
configuration, so this bug affect them all.

If the module ohci1394 is loaded while uhci-hcd and/or sky2 and/or ipw2200 
and/or yenta_socket and/or any module/driver that uses IRQ11, this panic 
occurs:

ieee1394: Current remote IRM is not 1394a-2000 compliant, resetting...
irq 11: nobody cared (try booting with the "irqpoll" option)
 [<b012f0ff>] __report_bad_irq+0x2b/0x69
 [<b012f2b3>] note_interrupt+0x176/0x1a7
 [<b012ed1b>] handle_IRQ_event+0x20/0x4c
 [<b012edac>] __do_IRQ+0x65/0x91
 [<b0104a1b>] do_IRQ+0x1d/0x2a
 [<b010335a>] common_interrupt+0x1a/0x20
 [<b012ed10>] handle_IRQ_event+0x15/0x4c
 [<b012ed9a>] __do_IRQ+0x53/0x91
 [<b0104a1b>] do_IRQ+0x1d/0x2a
 [<b010335a>] common_interrupt+0x1a/0x20
 [<b012ed10>] handle_IRQ_event+0x15/0x4c
 [<b012ed9a>] __do_IRQ+0x53/0x91
 [<b0104a1b>] do_IRQ+0x1d/0x2a
 [<b010335a>] common_interrupt+0x1a/0x20
 [<b0116450>] do_syslog+0x12d/0x2cb
 [<b0123f44>] autoremove_wake_function+0x0/0x3a
 [<b01466bd>] vfs_read+0xa3/0x13a
 [<b014706e>] sys_read+0x3b/0x64
 [<b0102915>] syscall_call+0x7/0xb
handlers:
[<f0947f7b>] (sky2_intr+0x0/0x1fa [sky2])
[<f09c4b5b>] (usb_hcd_irq+0x0/0x54 [usbcore])
[<f09c4b5b>] (usb_hcd_irq+0x0/0x54 [usbcore])
[<f09c4b5b>] (usb_hcd_irq+0x0/0x54 [usbcore])
[<f09e8dee>] (yenta_interrupt+0x0/0xb5 [yenta_socket])
Disabling IRQ #11
ohci1394: fw-host0: AT dma reset ctx=0, aborting transmission

All 2.6 kernels has the same bug, including sarge kernel 2.6.8.
Some times the kernel freezes, others just panic.

So the main problem is that no debian-installer can use network to
install debian because the IRQ11 is disabled when the error pops.
If the module is not loaded (putting the module in blacklist) the
kernel works right, with ACPI working good.

If you disable all drivers/modules that use IRQ11, you can load the
ohci1394 and sbp2 and access your external harddrives without a 
problem(I not have other firewire device to test).
Even after a panic, you can rmmod all modules, load the ohci1396 XOR
the others modules and you can use the hardware with out problems

a workarround to install debian is:
-using a 2.4 kernel
But the problem is that a lot of hardware is not recognized.
Also the kernel do use IDE devices (ich6m) and the kernel 2.6 
use SATA devices, piix in 2.6 does not recognize the harddisk.
-disabling ACPI
But some hardware is useless (no button events, no battery info)

There is no way to tell the installer not to load the ohci1394 (AFAIK)
all hw detection loads the driver.

The BIOS in this machine is not a toshiba BIOS.
Ahh I dont know why, but the ohci1394 does not use IRQ11, only use IRQ6 as
/proc/interrupts shows:
           CPU0       
  0:     963418          XT-PIC  timer
  1:       3214          XT-PIC  i8042
  2:          0          XT-PIC  cascade
  6:        101          XT-PIC  ohci1394
  9:         31          XT-PIC  acpi
 10:          0          XT-PIC  ehci_hcd:usb1, uhci_hcd:usb2
 11:     200000          XT-PIC  sky2, uhci_hcd:usb3, uhci_hcd:usb4, uhci_hcd:usb5, yenta
 14:       5572          XT-PIC  libata
 15:       1294          XT-PIC  libata
NMI:          0 
LOC:     302532 
ERR:          0
MIS:          0


-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16-1-686
Locale: LANG=es_ES@euro, LC_CTYPE=es_ES@euro (charmap=ISO-8859-15)

Versions of packages linux-image-2.6.16-1-686 depends on:
ii  initramfs-tools [linux-initra 0.60       tools for generating an initramfs
ii  module-init-tools             3.2.2-2    tools for managing Linux kernel mo
ii  yaird [linux-initramfs-tool]  0.0.12-9   Yet Another mkInitRD

Versions of packages linux-image-2.6.16-1-686 recommends:
pn  libc6-i686                    <none>     (no description available)

-- debconf information:
  linux-image-2.6.16-1-686/preinst/initrd-2.6.16-1-686:
  linux-image-2.6.16-1-686/postinst/create-kimage-link-2.6.16-1-686: true
  linux-image-2.6.16-1-686/preinst/lilo-has-ramdisk:
  linux-image-2.6.16-1-686/prerm/removing-running-kernel-2.6.16-1-686: true
  linux-image-2.6.16-1-686/postinst/old-dir-initrd-link-2.6.16-1-686: true
  linux-image-2.6.16-1-686/postinst/depmod-error-initrd-2.6.16-1-686: false
  linux-image-2.6.16-1-686/preinst/lilo-initrd-2.6.16-1-686: true
  linux-image-2.6.16-1-686/postinst/old-system-map-link-2.6.16-1-686: true
  linux-image-2.6.16-1-686/postinst/kimage-is-a-directory:
  linux-image-2.6.16-1-686/preinst/bootloader-initrd-2.6.16-1-686: true
* linux-image-2.6.16-1-686/preinst/already-running-this-2.6.16-1-686:
  linux-image-2.6.16-1-686/preinst/overwriting-modules-2.6.16-1-686: true
  linux-image-2.6.16-1-686/postinst/old-initrd-link-2.6.16-1-686: true
  linux-image-2.6.16-1-686/preinst/abort-overwrite-2.6.16-1-686:
  linux-image-2.6.16-1-686/postinst/depmod-error-2.6.16-1-686: false
  linux-image-2.6.16-1-686/preinst/failed-to-move-modules-2.6.16-1-686:
  linux-image-2.6.16-1-686/preinst/elilo-initrd-2.6.16-1-686: true
  linux-image-2.6.16-1-686/prerm/would-invalidate-boot-loader-2.6.16-1-686: true
  linux-image-2.6.16-1-686/postinst/bootloader-error-2.6.16-1-686:
  linux-image-2.6.16-1-686/preinst/abort-install-2.6.16-1-686:
  linux-image-2.6.16-1-686/postinst/bootloader-test-error-2.6.16-1-686:



Reply to: