http://bugzilla.kernel.org/show_bug.cgi?id=8562
------- Comment #25 from [EMAIL PROTECTED] 2007-08-10 08:44 ------- Good grief. All that kobject debug crap fills up the logs, obliterating the stuff I'd like to see. If you have CONFIG_DEBUG_KOBJECT=y, can you turn that off, please? It does have this: 00:09: ttyS3 at I/O 0x2e8 (irq = 11) is a 16550A which means ttyS3 must be working with IRQ 11. So maybe there's some interrupt sharing issue that "acpi=noirq" works around. Your first log was from 2.6.21.2, which has different legacy serial detection that 2.6.22.1. So can you get two logs from 2.6.22.1, one with "acpi=noirq" (where ttyS3 should work) and one without (where ttyS3 probably won't work)? Also collect the contents of /proc/interrupts. I want to see exactly what difference "acpi=noirq" makes, with everything else the same. -- Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ acpi-bugzilla mailing list acpi-bugzilla@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
