Tino Keitel wrote:
On Mon, Mar 26, 2007 at 17:15:53 -0400, Alan Stern wrote:
[...]
The lack of messages from the iPod seems to indicate that the hub isn't
working right. You could try plugging the iPod into a different hub or
directly into the computer. Or maybe into a different port of
Tino Keitel wrote:
On Mon, Mar 26, 2007 at 17:15:53 -0400, Alan Stern wrote:
[...]
The lack of messages from the iPod seems to indicate that the hub isn't
working right. You could try plugging the iPod into a different hub or
directly into the computer. Or maybe into a different port of
On Tue, 27 Mar 2007, Tino Keitel wrote:
> On Tue, Mar 27, 2007 at 00:21:24 +0200, Tino Keitel wrote:
>
> [...]
>
> > this is the bisect result:
> >
> > $ git bisect good
> > 1d619f128ba911cd3e6d6ad3475f146eb92f5c27 is first bad commit
> > commit 1d619f128ba911cd3e6d6ad3475f146eb92f5c27
>
> I
On Tue, 27 Mar 2007, Tino Keitel wrote:
On Tue, Mar 27, 2007 at 00:21:24 +0200, Tino Keitel wrote:
[...]
this is the bisect result:
$ git bisect good
1d619f128ba911cd3e6d6ad3475f146eb92f5c27 is first bad commit
commit 1d619f128ba911cd3e6d6ad3475f146eb92f5c27
I just tested
On Tue, Mar 27, 2007 at 00:21:24 +0200, Tino Keitel wrote:
[...]
> this is the bisect result:
>
> $ git bisect good
> 1d619f128ba911cd3e6d6ad3475f146eb92f5c27 is first bad commit
> commit 1d619f128ba911cd3e6d6ad3475f146eb92f5c27
I just tested 2.6.21-rc5 with this commit reverted and the iPod
On Mon, Mar 26, 2007 at 23:26:14 +0200, Tino Keitel wrote:
> On Mon, Mar 26, 2007 at 17:15:53 -0400, Alan Stern wrote:
>
> [...]
>
> > The lack of messages from the iPod seems to indicate that the hub isn't
> > working right. You could try plugging the iPod into a different hub or
> > directly
On Mon, Mar 26, 2007 at 17:15:53 -0400, Alan Stern wrote:
[...]
> The lack of messages from the iPod seems to indicate that the hub isn't
> working right. You could try plugging the iPod into a different hub or
> directly into the computer. Or maybe into a different port of that hub.
Uh, I
On Mon, Mar 26, 2007 at 17:15:53 -0400, Alan Stern wrote:
[...]
> The lack of messages from the iPod seems to indicate that the hub isn't
> working right. You could try plugging the iPod into a different hub or
> directly into the computer. Or maybe into a different port of that hub.
I
On Mon, 26 Mar 2007, Tino Keitel wrote:
> > > There are no messages from the iPod because, well, nothing happens when
> > > I plug it in. I tried it 3 times.
> >
> > I don't understand. The dmesg log you attached shows the iPod was
> > detected and recognized as scsi5 (sdc). Then some time
On Mon, Mar 26, 2007 at 16:28:34 -0400, Alan Stern wrote:
> On Mon, 26 Mar 2007, Tino Keitel wrote:
>
> > Attached is a dmesg output with CONFIG_USB_DEBUG and CONFIG_USB_SUSPEND
> > enabled.
> >
> > There are no messages from the iPod because, well, nothing happens when
> > I plug it in. I tried
On Mon, 26 Mar 2007, Tino Keitel wrote:
> Attached is a dmesg output with CONFIG_USB_DEBUG and CONFIG_USB_SUSPEND
> enabled.
>
> There are no messages from the iPod because, well, nothing happens when
> I plug it in. I tried it 3 times.
I don't understand. The dmesg log you attached shows the
On Mon, Mar 26, 2007 at 14:12:25 -0400, Alan Stern wrote:
> On Sun, 25 Mar 2007, Tino Keitel wrote:
>
> > > Please recompile
> > > with CONFIG_USB_DEBUG
> > > and without CONFIG_USB_SUSPEND
> >
> > With CONFIG_USB_SUSPEND disabled, the iPod works. The dmesg output is
> > attached.
>
> In fact,
On Sun, 25 Mar 2007, Tino Keitel wrote:
> > Please recompile
> > with CONFIG_USB_DEBUG
> > and without CONFIG_USB_SUSPEND
>
> With CONFIG_USB_SUSPEND disabled, the iPod works. The dmesg output is
> attached.
In fact, both logs (with and without CONFIG_USB_SUSPEND) show the iPod
working. Can
On Sun, 25 Mar 2007, Tino Keitel wrote:
Please recompile
with CONFIG_USB_DEBUG
and without CONFIG_USB_SUSPEND
With CONFIG_USB_SUSPEND disabled, the iPod works. The dmesg output is
attached.
In fact, both logs (with and without CONFIG_USB_SUSPEND) show the iPod
working. Can you post a
On Mon, Mar 26, 2007 at 14:12:25 -0400, Alan Stern wrote:
On Sun, 25 Mar 2007, Tino Keitel wrote:
Please recompile
with CONFIG_USB_DEBUG
and without CONFIG_USB_SUSPEND
With CONFIG_USB_SUSPEND disabled, the iPod works. The dmesg output is
attached.
In fact, both logs (with and
On Mon, 26 Mar 2007, Tino Keitel wrote:
Attached is a dmesg output with CONFIG_USB_DEBUG and CONFIG_USB_SUSPEND
enabled.
There are no messages from the iPod because, well, nothing happens when
I plug it in. I tried it 3 times.
I don't understand. The dmesg log you attached shows the iPod
On Mon, Mar 26, 2007 at 16:28:34 -0400, Alan Stern wrote:
On Mon, 26 Mar 2007, Tino Keitel wrote:
Attached is a dmesg output with CONFIG_USB_DEBUG and CONFIG_USB_SUSPEND
enabled.
There are no messages from the iPod because, well, nothing happens when
I plug it in. I tried it 3 times.
On Mon, 26 Mar 2007, Tino Keitel wrote:
There are no messages from the iPod because, well, nothing happens when
I plug it in. I tried it 3 times.
I don't understand. The dmesg log you attached shows the iPod was
detected and recognized as scsi5 (sdc). Then some time later (can't
On Mon, Mar 26, 2007 at 17:15:53 -0400, Alan Stern wrote:
[...]
The lack of messages from the iPod seems to indicate that the hub isn't
working right. You could try plugging the iPod into a different hub or
directly into the computer. Or maybe into a different port of that hub.
I already
On Mon, Mar 26, 2007 at 17:15:53 -0400, Alan Stern wrote:
[...]
The lack of messages from the iPod seems to indicate that the hub isn't
working right. You could try plugging the iPod into a different hub or
directly into the computer. Or maybe into a different port of that hub.
Uh, I think
On Mon, Mar 26, 2007 at 23:26:14 +0200, Tino Keitel wrote:
On Mon, Mar 26, 2007 at 17:15:53 -0400, Alan Stern wrote:
[...]
The lack of messages from the iPod seems to indicate that the hub isn't
working right. You could try plugging the iPod into a different hub or
directly into the
On Tue, Mar 27, 2007 at 00:21:24 +0200, Tino Keitel wrote:
[...]
this is the bisect result:
$ git bisect good
1d619f128ba911cd3e6d6ad3475f146eb92f5c27 is first bad commit
commit 1d619f128ba911cd3e6d6ad3475f146eb92f5c27
I just tested 2.6.21-rc5 with this commit reverted and the iPod was
On Thu, Mar 22, 2007 at 20:42:44 +0100, Oliver Neukum wrote:
> Am Donnerstag, 22. März 2007 20:17 schrieb Tino Keitel:
> > On Thu, Mar 22, 2007 at 09:50:29 +0100, Oliver Neukum wrote:
> > > Am Mittwoch, 21. März 2007 21:47 schrieb Tino Keitel:
> > >
> > > > along with other USB error messages. I
On Thu, Mar 22, 2007 at 20:42:44 +0100, Oliver Neukum wrote:
Am Donnerstag, 22. März 2007 20:17 schrieb Tino Keitel:
On Thu, Mar 22, 2007 at 09:50:29 +0100, Oliver Neukum wrote:
Am Mittwoch, 21. März 2007 21:47 schrieb Tino Keitel:
along with other USB error messages. I tried a hub
On Thu, Mar 22, 2007 at 10:46:53PM +0100, Tino Keitel wrote:
> On Thu, Mar 22, 2007 at 14:29:11 -0700, David Brownell wrote:
> > On Thursday 22 March 2007 12:54 pm, Tino Keitel wrote:
> > > On Thu, Mar 22, 2007 at 15:40:40 -0400, Alan Stern wrote:
> > > > _Something_ is generating those
On Thu, Mar 22, 2007 at 10:46:53PM +0100, Tino Keitel wrote:
On Thu, Mar 22, 2007 at 14:29:11 -0700, David Brownell wrote:
On Thursday 22 March 2007 12:54 pm, Tino Keitel wrote:
On Thu, Mar 22, 2007 at 15:40:40 -0400, Alan Stern wrote:
_Something_ is generating those
David Brownell wrote:
> On Thursday 22 March 2007 12:54 pm, Tino Keitel wrote:
>> On Thu, Mar 22, 2007 at 15:40:40 -0400, Alan Stern wrote:
>>> _Something_ is generating those overcurrent
>>> warnings, and it sure looks like a hardware malfunction.
>> But it works with 2.6.20.
>
> So can
On Thu, Mar 22, 2007 at 14:29:11 -0700, David Brownell wrote:
> On Thursday 22 March 2007 12:54 pm, Tino Keitel wrote:
> > On Thu, Mar 22, 2007 at 15:40:40 -0400, Alan Stern wrote:
> > > _Something_ is generating those overcurrent
> > > warnings, and it sure looks like a hardware malfunction.
On Thursday 22 March 2007 12:54 pm, Tino Keitel wrote:
> On Thu, Mar 22, 2007 at 15:40:40 -0400, Alan Stern wrote:
> > _Something_ is generating those overcurrent
> > warnings, and it sure looks like a hardware malfunction.
>
> But it works with 2.6.20.
So can you bisect to find what
On Thu, Mar 22, 2007 at 15:40:40 -0400, Alan Stern wrote:
> On Thu, 22 Mar 2007, Tino Keitel wrote:
>
> > On Thu, Mar 22, 2007 at 09:50:29 +0100, Oliver Neukum wrote:
> > > Am Mittwoch, 21. März 2007 21:47 schrieb Tino Keitel:
> > >
> > > > along with other USB error messages. I tried a hub with
Am Donnerstag, 22. März 2007 20:17 schrieb Tino Keitel:
> On Thu, Mar 22, 2007 at 09:50:29 +0100, Oliver Neukum wrote:
> > Am Mittwoch, 21. März 2007 21:47 schrieb Tino Keitel:
> >
> > > along with other USB error messages. I tried a hub with own power
> > > supply and a USB port on the computer.
On Thu, 22 Mar 2007, Tino Keitel wrote:
> On Thu, Mar 22, 2007 at 09:50:29 +0100, Oliver Neukum wrote:
> > Am Mittwoch, 21. März 2007 21:47 schrieb Tino Keitel:
> >
> > > along with other USB error messages. I tried a hub with own power
> > > supply and a USB port on the computer. A full log is
On Thu, Mar 22, 2007 at 09:50:29 +0100, Oliver Neukum wrote:
> Am Mittwoch, 21. März 2007 21:47 schrieb Tino Keitel:
>
> > along with other USB error messages. I tried a hub with own power
> > supply and a USB port on the computer. A full log is attached.
>
> Your log basically shows a hub going
On Thu, Mar 22, 2007 at 09:50:29 +0100, Oliver Neukum wrote:
> Am Mittwoch, 21. März 2007 21:47 schrieb Tino Keitel:
>
> > along with other USB error messages. I tried a hub with own power
> > supply and a USB port on the computer. A full log is attached.
>
> Your log basically shows a hub going
Am Mittwoch, 21. März 2007 21:47 schrieb Tino Keitel:
> along with other USB error messages. I tried a hub with own power
> supply and a USB port on the computer. A full log is attached.
Your log basically shows a hub going berserk. Please post "lsusb -v"
and your .config
Regards
Am Mittwoch, 21. März 2007 21:47 schrieb Tino Keitel:
along with other USB error messages. I tried a hub with own power
supply and a USB port on the computer. A full log is attached.
Your log basically shows a hub going berserk. Please post lsusb -v
and your .config
Regards
On Thu, Mar 22, 2007 at 09:50:29 +0100, Oliver Neukum wrote:
Am Mittwoch, 21. März 2007 21:47 schrieb Tino Keitel:
along with other USB error messages. I tried a hub with own power
supply and a USB port on the computer. A full log is attached.
Your log basically shows a hub going
On Thu, Mar 22, 2007 at 09:50:29 +0100, Oliver Neukum wrote:
Am Mittwoch, 21. März 2007 21:47 schrieb Tino Keitel:
along with other USB error messages. I tried a hub with own power
supply and a USB port on the computer. A full log is attached.
Your log basically shows a hub going
On Thu, 22 Mar 2007, Tino Keitel wrote:
On Thu, Mar 22, 2007 at 09:50:29 +0100, Oliver Neukum wrote:
Am Mittwoch, 21. März 2007 21:47 schrieb Tino Keitel:
along with other USB error messages. I tried a hub with own power
supply and a USB port on the computer. A full log is attached.
Am Donnerstag, 22. März 2007 20:17 schrieb Tino Keitel:
On Thu, Mar 22, 2007 at 09:50:29 +0100, Oliver Neukum wrote:
Am Mittwoch, 21. März 2007 21:47 schrieb Tino Keitel:
along with other USB error messages. I tried a hub with own power
supply and a USB port on the computer. A full log
On Thu, Mar 22, 2007 at 15:40:40 -0400, Alan Stern wrote:
On Thu, 22 Mar 2007, Tino Keitel wrote:
On Thu, Mar 22, 2007 at 09:50:29 +0100, Oliver Neukum wrote:
Am Mittwoch, 21. März 2007 21:47 schrieb Tino Keitel:
along with other USB error messages. I tried a hub with own power
On Thursday 22 March 2007 12:54 pm, Tino Keitel wrote:
On Thu, Mar 22, 2007 at 15:40:40 -0400, Alan Stern wrote:
_Something_ is generating those overcurrent
warnings, and it sure looks like a hardware malfunction.
But it works with 2.6.20.
So can you bisect to find what caused the
On Thu, Mar 22, 2007 at 14:29:11 -0700, David Brownell wrote:
On Thursday 22 March 2007 12:54 pm, Tino Keitel wrote:
On Thu, Mar 22, 2007 at 15:40:40 -0400, Alan Stern wrote:
_Something_ is generating those overcurrent
warnings, and it sure looks like a hardware malfunction.
But
David Brownell wrote:
On Thursday 22 March 2007 12:54 pm, Tino Keitel wrote:
On Thu, Mar 22, 2007 at 15:40:40 -0400, Alan Stern wrote:
_Something_ is generating those overcurrent
warnings, and it sure looks like a hardware malfunction.
But it works with 2.6.20.
So can you bisect to
44 matches
Mail list logo
