Jonathan Fournier wrote: > Oh but one other thing, what is that: > > Nov 7 16:27:08 localhost kernel: IPMI Watchdog: Unable to register > misc device
Looks like you have another watchdog driver installed. > Nov 7 16:27:08 localhost kernel: IPMI Watchdog: set timeout error: -22 This is somewhat strange. -22 is EINVAL, IIRC. Is ipmi_watchdog.c or ipmi_msghandler.c patched? I don't see a way this can really happen. You may have to trace through i_ipmi_request() in ipmi_msghandler.c to see what's happening here. -corey > Nov 7 16:27:08 localhost kernel: IPMI Watchdog: driver initialized > > On Nov 7, 2007 9:34 AM, Corey Minyard <[EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]>> wrote: > > I'm not really sure here. There was a driver that worked with this > board, but it had a lot of problems. Looking at that driver and this > data, the only thing I can see is that the other driver terminated the > message with a 0x0d, not a 0x0a. It may be best to send both, so I'm > attaching a patch to do that. > > -corey > > Jonathan Fournier wrote: > > I'm getting this with debug: > > > > ipmi message handler version 39.1 > > IPMI Serial System Interface driver > > ipmi_serial: Registering TerminalMode codec > > ipmi_serial(ttyS4): Found a matching serial port > > ipmi_serial(ttyS4): Outgoing data: 5b([) 31(1) 38(8) 30(0) 30(0) > 30(0) > > 31(1) 5d(]) 0a( ) > > ipmi_serial(ttyS4): Outgoing data: 5b([) 31(1) 38(8) 30(0) 30(0) > 30(0) > > 31(1) 5d(]) 0a( ) > > ipmi_serial(ttyS4): Outgoing data: 5b([) 31(1) 38(8) 30(0) 30(0) > 30(0) > > 31(1) 5d(]) 0a( ) > > ipmi_serial(ttyS4): Outgoing data:<7>ipmi_serial(ttyS4): Incoming > > char: 5b '[' > > ipmi_serial(ttyS4): Incoming char: 45 'E' > > ipmi_serial(ttyS4): Incoming char: 52 'R' > > ipmi_serial(ttyS4): Incoming char: 52 'R' > > ipmi_serial(ttyS4): Incoming char: 20 ' ' > > ipmi_serial(ttyS4): Incoming char: 63 'c' > > ipmi_serial(ttyS4): Incoming char: 31 '1' > > ipmi_serial(ttyS4): Incoming char: 5d ']' > > ipmi_serial(ttyS4): Incoming char: 0a ' ' > > ipmi_serial(ttyS4): Incoming char: 0d ' ' > > 5b([) 31(1) 38(8) 30(0) 30(0) 30(0) 31(1) 5d(]) 0a( ) > > ipmi_serial(ttyS4): Outgoing data: 5b([) 31(1) 38(8) 30(0) 30(0) > 30(0) > > 31(1) 5d(]) 0a( ) > > ipmi_serial(ttyS4): Outgoing data: 5b([) 31(1) 38(8) 30(0) 30(0) > 30(0) > > 31(1) 5d(]) 0a( ) > > ipmi_serial(ttyS4): Outgoing data: 5b([) 31(1) 38(8) 30(0) 30(0) > 30(0) > > 31(1) 5d(]) 0a( ) > > ipmi_serial(ttyS4): Outgoing data: 5b([) 31(1) 38(8) 30(0) 30(0) > 30(0) > > 31(1) 5d(]) 0a( ) > > ipmi_serial(ttyS4): Outgoing data: 5b([) 31(1) 38(8) 30(0) 30(0) > 30(0) > > 31(1) 5d(]) 0a( ) > > ipmi_serial(ttyS4): Outgoing data: 5b([) 31(1) 38(8) 30(0) 30(0) > 30(0) > > 31(1) 5d(]) 0a( ) > > ipmi_serial(ttyS4): codec initialization timed out, interface is not > > usable > > > > ------------------------------------------------------------------------- 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/ _______________________________________________ Openipmi-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openipmi-developer
