On Fri, Apr 27, 2007 at 12:39:19AM +0200, Jiri Kosina wrote:
> On Fri, 27 Apr 2007, Helge Hafting wrote:
>
> > 2.6.21-rc6 boots up fine. Both rc6 and rc7 has a different problem -
> > the machine tends to hang after some minutes work in X. That hang is
> > unusual
Jiri Kosina wrote:
> On Wed, 25 Apr 2007, Helge Hafting wrote:
>
>>
>> I don't know about 2.6.21-rc6, but 2.6.21-rc7 (from fresh sources) is
>> good. It boots up without hanging, and my USB devices works too. Should
>> I test rc7-mm1 then?
>>
I recompiled 2.6.21-rc6-mm1 from fresh sources.
It still hangs initializing USBm but this time your
patch applied.
I rebooted with your patch, and got:
Detailed lists of all the USB devices found
(printer,mouse,...)
Then usbcore registered various drivers, such as
usblp, usb-storage, libusual, us
Jiri Kosina wrote:
> On Wed, 25 Apr 2007, Helge Hafting wrote:
>
>
>>> Anyway, based on information you have provided in your later messages,
>>> it seems that it is probably not necessairly related neither to USB
>>> nor HID, as you are getti
gt; offending patch?
>
I don't know about 2.6.21-rc6, but 2.6.21-rc7
(from fresh sources) is good. It boots up without hanging,
and my USB devices works too.
Should I test rc7-mm1 then?
Helge Hafting
-
This SF.
On Thu, Apr 12, 2007 at 08:32:50PM +0200, Jiri Kosina wrote:
> OK, so it hangs somewhere nearby usbhid's hid_init(), and the
> usb_register() has been already invoked. Could you please apply the
> superstupid patch below and send me the output up to the point it hangs? I
> am curious to know whe
dress 0xd0121000,
> slave address 0x0, irq 5
>
> (this was run on 32bit machine)
>
> When I turn IPMI off, I can't reproduce your hang, evetything runs
> smoothly. Could you please try recompiling the kernel with IPMI disabled,
> if it could b
On Thu, Apr 12, 2007 at 09:50:54AM +0200, Jiri Kosina wrote:
> On Thu, 12 Apr 2007, Helge Hafting wrote:
>
> > > OK. If you add initcall_debug to the kernel boot command line, what's the
> > > last thing we call?
> > The last messages (handwritten, somewhat
On Thu, Apr 12, 2007 at 09:47:47AM -0700, Andrew Morton wrote:
> On Thu, 12 Apr 2007 13:42:57 +0200 Helge Hafting <[EMAIL PROTECTED]> wrote:
>
> > Jiri Kosina wrote:
> > > On Thu, 12 Apr 2007, Jiri Kosina wrote:
> > >
> > >
> > >> Coul
On Wed, Apr 11, 2007 at 10:37:11AM -0400, Dmitry Torokhov wrote:
> On 4/11/07, Helge Hafting <[EMAIL PROTECTED]> wrote:
> >Dmitry Torokhov wrote:
> >>
> >> *sigh* When will I learn to spell names of kernel parameters
> >> correctly? It is initcall_
e if it helps?
>>
>
> Do you compile with CONFIG_HIDRAW?
>
No, that one is not set.
I did use the new SLUB thing - could that possibly be the cause?
Going back to SLAB is easy enough.
Helge Hafting
-
_init+0x0/0x50()
usbcore registered new interface driver hiddev
and then it hangs completely.
Helge Hafting
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get
-core.c: v2.6:USB HID core driver
usbcore: registered new interface driver usbserial
This is a x86-64 single processor
Helge Hafting
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay
CONFIG_USB_SERIAL_PL2303=y
Helge Hafting
initcall_debugrc5mm4.gz
Description: application/gzip
initcall_debugrc6.gz
Description: application/gzip
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay
er gets /class/input/input3,
usbcore registers usbtouchscreen, and the
touchscreen works.
Well, it became /dev/input/event3 while
2.6.18 placed it at /dev/input/event1, but I think that
is more of a udev problem...
Helge Hafting
--
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.
Helge Hafting
debug_initcall.gz
Description: a
On Fri, Apr 06, 2007 at 10:37:12PM -0400, Dmitry Torokhov wrote:
> On Friday 06 April 2007 20:54, Helge Hafting wrote:
> > I have an usb touchscreen (egalax variety) that works with
> > the 2.6.18 kernel supplied by debian.
> >
> > It fails when I compile 2.6.21-rc
wrong, or could there be a seemingly unrelated option
that I need to turn on?
Helge Hafting
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to
ed. I have
edited out stuff that isn't usb or scsi.
Helge Hafting
dmesg3.gz
Description: application/gzip
-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-in
to prevent media removal. :-)
> and it returns a phase error in response to a READ
> command. In spite of the fact that it claims to have a 256 MB card
> present.
>
It has slots for several different cards, all t
k's help. I can add more of them too, if needed.
Big transfers seems to bring out the worst - I always get the
crash on the first megabyte now.
During boot I get lots of those "Hardware error, end-of-data detected"
messages, but I've never seen it crash during bootup.
Helge Ha
Alan Stern wrote:
On Wed, 18 Oct 2006, Helge Hafting wrote:
[...]
That's why I asked for the USB debugging logs (which you forgot to include
here).
Attached dmesg.gz with lots of usb messages.
To bring it down:
dd if=/dev/sdc of=sdc.dump bs=1M
This time, it seems to
Alan Stern wrote:
> Verbose usb-storage debugging messages would help more
> (CONFIG_USB_STORAGE_DEBUG and CONFIG_USB_DEBUG). If the kernel hangs very
> badly you might need to use a serial console to capture all the logging
> information.
>
Version information first: This is 2.6.19-rc1, not
Andrew Morton wrote:
We still have some serious bugs, several of which are in 2.6.15 as well:
[...]
- Helge Hafting reports a usb printer regression - I don't know if that's
still live?
I tried printing four pages of graphichs with 2.6.16-rc3-mm1
and it worked fine. When
24 matches
Mail list logo
