Re: 2.6.14-rc4-mm1

[Greg KH]

On Mon, Oct 17, 2005 at 04:58:28PM -0500, Dmitry Torokhov wrote:
> On 10/17/05, Greg KH <greg@xxxxxxxxx> wrote:
> > On Mon, Oct 17, 2005 at 04:39:52PM -0500, Dmitry Torokhov wrote:
> > > On 10/17/05, Vojtech Pavlik <vojtech@xxxxxxx> wrote:
> > > > On Mon, Oct 17, 2005 at 01:22:42PM -0700, Andrew Morton wrote:
> > > > > Brice Goglin <Brice.Goglin@xxxxxxxxxxxx> wrote:
> > > > > >
> > > > > > Le 17.10.2005 00:41, Andrew Morton a ?crit :
> > > > > > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.14-rc4/2.6.14-rc4-mm1/
> > > > > > >
> > > > > > > - Lots of i2c, PCI and USB updates
> > > > > > >
> > > > > > > - Large input layer update to convert it all to dynamic input_dev allocation
> > > > > > >
> > > > > > > - Significant x86_64 updates
> > > > > > >
> > > > > > > - MD updates
> > > > > > >
> > > > > > > - Lots of core memory management scalability rework
> > > > > >
> > > > > > Hi Andrew,
> > > > > >
> > > > > > I got the following oops during the boot on my laptop (Compaq Evo N600c).
> > > > > > .config is attached.
> > > > > >
> > > > > > Regards,
> > > > > > Brice
> > > >
> > > > Where did get support for IBM TrackPoints into that kernel? It's
> > > > certainly not in 2.6.14, and it's not in the -mm patch either ...
> > > >
> > >
> > > Yes it is. We merged it at the beginning of 2.6.14.. ;)
> > >
> > > > That's likely the cause here, since the TP patch probably relies on
> > > > non-dynamic allocation semantics.
> > > >
> > >
> > > It was converted but I am aftraid when Greg created sub-class devices
> > > something broke a bit. Do you see the ugly names input core prints?
> >
> > The "//" stuff you mean?  Did I do that?
> >
> 
> Not directly. I was trying to make names look "nice" but when you
> moved stuff around they stopped being nice ;) Although that name in
> front of double "/" - it should not be there... it was supposed to be
> "%s as %s/%s", somehow I screwed that up.
> 
> Hopefully I'll have some time tonight to investigate further.

A simple:
	cat /sys/class/input/input1/event1/name
causes this to happen too.

That's my fault, I'll work on fixing that.

thanks,

greg k-h
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/