lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 10 Apr 2007 11:39:21 -0400
From:	"Dmitry Torokhov" <dmitry.torokhov@...il.com>
To:	"Helge Hafting" <helge.hafting@...el.hist.no>
Cc:	"Helge Hafting" <helgehaf@...el.hist.no>,
	linux-kernel@...r.kernel.org, linux-usb-devel@...ts.sourceforge.net
Subject: Re: usb touchscreen breakage in 2.6.21-rc5-mm4 ?

On 4/10/07, Helge Hafting <helge.hafting@...el.hist.no> wrote:
> Dmitry Torokhov wrote:
> > Hmm, I am concerned because not only you don't have an input device created,
> > you don't even see the driver being registered with usbcore. Could you please
> > try booting with debug_initcall to see with what error code usbtouchscreen
> > initialization fails?
> >
> Here is the dmesg from a boot with debug_initcall.
> I can't see any messages from usbtouchscreen.
> For me, it looks like the touchscreen is discovered and then
> nothing happens to it.
>

*sigh* When will I learn to spell names of kernel parameters
correctly? It is initcall_debug, not debug_initcall :( Could you try
again, please?

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ