On Thu, Mar 24, 2005 at 04:10:39PM -0500, Dmitry Torokhov wrote: > If you do "ls /sys/bus/serio/devices" and see more than 3 ports you > have MUX mode active.
Just serio0 and serio1. On Thu, Mar 24, 2005 at 04:14:52PM -0500, Dmitry Torokhov wrote: > On Thu, 24 Mar 2005 12:20:40 -0800, Andy Isaacson <[EMAIL PROTECTED]> wrote: > > (How can I verify that "nomux" was accepted? It shows up on the "Kernel > > command line" but there's no other mention of it in dmesg.) > > Ignore my babbling, I just noticed in your dmesg that your KBC does > not support MUX mode to begin with. OK, anything else I should try? Why does it only fail when I have *both* intel_agp and i8042 aux? In the SysRq-T trace I see one interesting process: most things are in D state in refrigerator(), but sh shows the following traceback: wait_for_completion call_usermodehelper kobject_hotplug kobject_del class_device_del class_device_unregister mousedev_disconnect input_unregister_device alps_disconnect psmouse_disconnect serio_driver_remove device_release_driver serio_release_driver serio_resume resume_device dpm_resume device_resume swsusp_write pm_suspend_disk enter_state state_store subsys_attr_store flush_write_buffer sysfs_write_file ... That seems odd to me... Also, khelper has the following trace: io_schedule sync_buffer __wait_on_bit out_of_line_wait_on_bit ext3_find_entry ext3_lookup real_lookup do_lookup __link_path_walk link_path_walk path_lookup open_exec do_execve ... -andy - 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/
