On Fri, Dec 29, 2006 at 04:01:32PM +0100, Ard -kwaak- van Breemen wrote: > > - parse-one detection of Yanmin > It doesn't flag it. I am working on that. As said: it was doing a callback to obsolete_... This replaces the patch into not being bloated and still gives enough info. It won't check voor callbacks or whatever, just which parameter b0rked it.
Output of dmesg without the pci-patch applied: [EMAIL PROTECTED]:~$ dmesg|grep -B5 -A1 'interrupts were enabled' Kernel command line: console=tty0 console=ttyS0,115200 hdb=noprobe hdc=noprobe hdd=noprobe root=/dev/md0 ro panic=30 earlyprintk=serial,ttyS0,115200 ide_setup: hdb=noprobe parse_args(): option 'hdb=noprobe' enabled irq's! ide_setup: hdc=noprobe ide_setup: hdd=noprobe start_kernel(): bug: interrupts were enabled *very* early, fixing it Initializing CPU#0 -- program signature; begin { telegraaf.com } writeln("<[EMAIL PROTECTED]> TEM2"); end .
--- linux-2.6.19.vanilla/kernel/params.c 2006-11-29 21:57:37.000000000 +0000 +++ linux-2.6.19/kernel/params.c 2006-12-29 15:14:26.000000000 +0000 @@ -143,9 +143,14 @@ while (*args) { int ret; + int irq_was_disabled; args = next_arg(args, ¶m, &val); + irq_was_disabled=irqs_disabled(); ret = parse_one(param, val, params, num, unknown); + if(irq_was_disabled && !irqs_disabled()) { + printk(KERN_WARNING "parse_args(): option '%s' enabled irq's!\n",param); + } switch (ret) { case -ENOENT: printk(KERN_ERR "%s: Unknown parameter `%s'\n",