https://bugzilla.novell.com/show_bug.cgi?id=423518
User [email protected] added comment https://bugzilla.novell.com/show_bug.cgi?id=423518#c44 --- Comment #44 from Michael Trausch <[email protected]> 2008-12-18 16:12:31 MST --- Well, I am willing to do a kernel bisection to determine when the problem was introduced and by what changeset. Can we keep this bug open in the meantime until I am able to do that and attempt to get something going? This would appear to be categorized as a regression, so probably need to send another message to the LKML (often, a single message *does* get lost in the load) and ensure that the word "regression" is in the bug title. That will get the attention of the kernel's regressions manager, and that will make the problem a little more visible as well. I am willing to take care of that, since I'll also be bisecting the kernel to be looking for the problem, so I can include a [bisected] tag as well to identify the first bad kernel commit. I'd at least like to understand what is going on or what it is that changed within the kernel before this is closed out entirely, though this is of course just a personal opinion. I can attempt to get some work done where I am at (I am out of town for Christmas holiday presently, but do have access to my testing machine at home from here, assuming that I can setup access to the global IPv6 network where I am presently located), but nothing is certain---I won't be back home until around the 5th of January. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
