http://bugzilla.kernel.org/show_bug.cgi?id=14746
--- Comment #9 from [email protected] 2009-12-09 07:56:00 --- Please help me doing it properly this time. Since capturing those logs are not as easy as i would have liked, involves physically moving a box from one room to the next fooling around with network settings and KVM switch. a. http://bugzilla.kernel.org/attachment.cgi?id=24090 is indeed the log of successful boot b. http://bugzilla.kernel.org/attachment.cgi?id=24090 is intentionally truncated by me, since nothing particularly stellar goes on there c. http://bugzilla.kernel.org/attachment.cgi?id=24068 (the failed one) is truncated because the box just resets, without an oops or any indication of the reset cause Regarding item (b), one of the reasons why i've truncated it is the fact that the box has a video acquisition board with 4 saa7134 chips and v4l is printing a lot of useless "your board is missing EEPROM" messages with long and tedious enumeration of all saa7134 derived grabbers it supports. So, if _really_ needed, i can remove the board (since the problem is always there regardless of the boards presence) and try to recapture the logs, this time attaching the whole, regardless how big, successful log. Is that what i should do? Thanks. -- Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. ------------------------------------------------------------------------------ Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev _______________________________________________ acpi-bugzilla mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
