On Fri, Dec 22, 2006 at 11:30:05AM +0100, Ard -kwaak- van Breemen wrote:
> Anyway: on to the ide_setup tracking....
> (I've noticed that the notifier of this problem als has idebus=66
> or something similar, so that explains in his case the
> early call to ide_setup.)
Aaarrgh...
Somewhere between the call to ide_setup and ide_init_hwif_ports
the interrupts get enabled. But I haven't got to the point where
exactly...
include/linux/ide.h:
266 /*
267 * ide_init_hwif_ports() is OBSOLETE and will be removed in 2.7 series.
268 * New ports shouldn't define IDE_ARCH_OBSOLETE_INIT in <asm/ide.h>.
269 */
270 #ifdef IDE_ARCH_OBSOLETE_INIT
271 static inline void ide_init_hwif_ports(hw_regs_t *hw,
272 unsigned long io_addr,
273 unsigned long ctl_addr,
274 int *irq)
275 {
276 if (!irqs_disabled()) printk(__FILE__ "%s(): blaat: interrupts
were enabled [EMAIL PROTECTED]",__FUNCTION__,__LINE__);
277 if (!ctl_addr) {
278 ide_std_init_ports(hw, io_addr,
ide_default_io_ctl(io_addr));
drivers/ide/ide.c:
256 static void init_hwif_default(ide_hwif_t *hwif, unsigned int index)
257 {
258 hw_regs_t hw;
259
260 if (!irqs_disabled()) printk(__FILE__ "%s(): blaat: interrupts
were enabled [EMAIL PROTECTED]",__FUNCTION__,__LINE__);
261 memset(&hw, 0, sizeof(hw_regs_t));
262 if (!irqs_disabled()) printk(__FILE__ "%s(): blaat: interrupts
were enabled [EMAIL PROTECTED]",__FUNCTION__,__LINE__);
263
264 ide_init_hwif_ports(&hw, ide_default_io_base(index), 0,
&hwif->irq);
265 if (!irqs_disabled()) printk(__FILE__ " %s(): blaat: interrupts
were enabled [EMAIL PROTECTED]",__FUNCTION__,__LINE__);
266
dmesg:
BLAAT20Parsing ARGS: console=tty0 console=ttyS0,115200 hdb=noprobe hdc=noprobe
hdd=noprobe root=/dev/md0 ro panic
=30 earlyprintk=serial,ttyS0,115200
Unknown argument: calling ffffffff80643380
Unknown argument: calling ffffffff80643380
Unknown argument: calling ffffffff80643380
ide_setup: hdb=noprobeinclude/linux/ide.hide_init_hwif_ports(): blaat:
interrupts were enabled [EMAIL PROTECTED]
include/linux/ide.hide_init_hwif_ports(): blaat: interrupts were enabled [EMAIL
PROTECTED]
include/linux/ide.hide_init_hwif_ports(): blaat: interrupts were enabled [EMAIL
PROTECTED]
include/linux/ide.hide_init_hwif_ports(): blaat: interrupts were enabled [EMAIL
PROTECTED]
drivers/ide/ide.c init_hwif_default(): blaat: interrupts were enabled [EMAIL
PROTECTED]
drivers/ide/ide.cinit_hwif_default(): blaat: interrupts were enabled [EMAIL
PROTECTED]
drivers/ide/ide.cinit_ide_data(): blaat: interrupts were enabled [EMAIL
PROTECTED]
So as I read it: init_hwif_default calls ide_init_hwif_ports with irq's
disabled, but upon entrance, the irq's are enabled.
That really makes no sense to me.
So I will continue digging this code (there must be something recursive going
on).
--
program signature;
begin { telegraaf.com
} writeln("<[EMAIL PROTECTED]> TEM2");
end
.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
