Without any marvel-poll patches, kernel loads fine but when I try to load
the ipmi_serial it says ttyMM1 doesn't exists (which I know does), with the
marvel-poll 2.6.23 patches backported to 2.6.21, I get that error right
after the ttyMM0/ttyMM1 (i.e. ttyMM0 at blah using IRQ(xx)...) init lines
appear in the kernel boot sequence.

On Nov 9, 2007 4:57 PM, Corey Minyard <[EMAIL PROTECTED]> wrote:

> No, that's not it.  It's an internal thing.  You are having trouble with
> the console rework.  I'll try to review the patches to make sure
> everything is there.  But maybe you'll trace it down before then.  I'm
> pretty sure everything is there.
>
> -corey
>
> Jonathan Fournier wrote:
> > Is it coming from that patch?
> >
> > http://osdir.com/ml/linux.kernel.openipmi/2006-06/msg00003.html
> >
> >
> > On Nov 9, 2007 3:58 PM, Corey Minyard < [EMAIL PROTECTED]
> > <mailto:[EMAIL PROTECTED]>> wrote:
> >
> >     I'm not really sure.  That actually hasn't been tested in its
> current
> >     form, the patch was ported from something else.  So it very well
> might
> >     have problems.
> >
> >     -corey
> >
> >     Jonathan Fournier wrote:
> >     > Am I gonna run in any trouble backporting the serial-marvel-poll
> >     stuff
> >     > from 2.6.23 patches?
> >     >
> >     > It's not included with 2.6.21, only the 8250.
> >     >
> >     > It doesn't seem to be fine, I backported all the changes against
> >     > drivers/serial/mpsc.c in 2.6.21, and when the kernel boots,
> >     after the
> >     > ttyMM1 init it just does an infinite loop of:
> >     >
> >     > Total memory = 512MB; using 1024kB for hash table (at <blah>)
> >     >
> >     > Driver in 2.6.21 ipmi_serial doesn't work on the Motorola F101.
> >     >
> >     > Regards,
> >     >
> >     > /jonathan
> >     >
> >     > On Nov 7, 2007 9:34 AM, Corey Minyard <[EMAIL PROTECTED]
> >     <mailto:[EMAIL PROTECTED]>
> >     > <mailto: [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

Reply via email to