Le Thursday 26 April 2007 22:44:59 Jay Vosburgh, vous avez écrit :
> Chris Snook <[EMAIL PROTECTED]> wrote:
> >Vincent ETIENNE wrote:
> >> Hi,
> >>
> >> Summary :
> >>Got this trace when one network interface come down or up in a 2
> >>interfaces bonding. So far, system seems to
Le Thursday 26 April 2007 22:44:59 Jay Vosburgh, vous avez écrit :
Chris Snook [EMAIL PROTECTED] wrote:
Vincent ETIENNE wrote:
Hi,
Summary :
Got this trace when one network interface come down or up in a 2
interfaces bonding. So far, system seems to survive to this problem
Le Sunday 29 April 2007 13:18:31 Jiri Kosina, vous avez écrit :
>
> Hi Vincent,
Hi Jiri,
>
> yes, the device is messed up, but it shouldn't have any consequences for
> you - the HID driver is able to correctly handle that, so as soon as we
> don't need to add any extra quirks for such
On Sat, 28 Apr 2007, Vincent ETIENNE wrote:
> > No, it isn't a problem in the USB core. The device itself is messed up;
> > it really does report idVendor and idProduct both equal to 0.
> So is it just a scary trace but without consequence that i could ignored
> ? May i ask you what is the
On Sat, 28 Apr 2007, Vincent ETIENNE wrote:
No, it isn't a problem in the USB core. The device itself is messed up;
it really does report idVendor and idProduct both equal to 0.
So is it just a scary trace but without consequence that i could ignored
? May i ask you what is the device
Le Sunday 29 April 2007 13:18:31 Jiri Kosina, vous avez écrit :
Hi Vincent,
Hi Jiri,
yes, the device is messed up, but it shouldn't have any consequences for
you - the HID driver is able to correctly handle that, so as soon as we
don't need to add any extra quirks for such device,
Le Saturday 28 April 2007 00:32:37 Andrew Morton, vous avez écrit :
> On Fri, 27 Apr 2007 22:05:28 +0200
>
> because we thought we'd fixed the rtnl_lock() problems in 2.6.21-rc7-mm2.
> Are you sure that log is from 2.6.21-rc7-mm2?
Yes. I have retested it another time ( for adding the small usb
Le Saturday 28 April 2007 21:50:30 Alan Stern, vous avez écrit :
> No, it isn't a problem in the USB core. The device itself is messed up;
> it really does report idVendor and idProduct both equal to 0.
>
> Jiri, don't worry about all those other devices in the listing that also
> have idVendor
On Sat, 28 Apr 2007, Jiri Kosina wrote:
> On Sat, 28 Apr 2007, Vincent ETIENNE wrote:
>
> > > I now don't immediately see how this could happen - the vendor ID
> > > seems to be propagated properly from hid_probe() (nothing has been
> > > changed in this codepath), so this would mean that
On Sat, 28 Apr 2007, Vincent ETIENNE wrote:
> > I now don't immediately see how this could happen - the vendor ID
> > seems to be propagated properly from hid_probe() (nothing has been
> > changed in this codepath), so this would mean that hid_probe() has
> > been passed usb_interface for
On Sat, 28 Apr 2007, Vincent ETIENNE wrote:
With your patch it seems like idVendor passed is 0. You could see it there ;
http://mail1.vetienne.net/linux/dmesg.2.6.21-rc7-mm2+patch-usbhid
I could confirm that the keyboard is working ( yesterday i was just behind the
box due to test on the
Le Saturday 28 April 2007 00:42:45 Jiri Kosina, vous avez écrit :
> On Fri, 27 Apr 2007, Greg KH wrote:
> > > BUG: at drivers/hid/usbhid/hid-quirks.c:480 usbhid_exists_dquirk()
>
> [ .. stacktraces stripped .. ]
>
> > Jiri, any thoughts about this? This looks like it comes from your tree
> > as
Le Saturday 28 April 2007 00:42:45 Jiri Kosina, vous avez écrit :
On Fri, 27 Apr 2007, Greg KH wrote:
BUG: at drivers/hid/usbhid/hid-quirks.c:480 usbhid_exists_dquirk()
[ .. stacktraces stripped .. ]
Jiri, any thoughts about this? This looks like it comes from your tree
as 2.6.21
On Sat, 28 Apr 2007, Vincent ETIENNE wrote:
With your patch it seems like idVendor passed is 0. You could see it there ;
http://mail1.vetienne.net/linux/dmesg.2.6.21-rc7-mm2+patch-usbhid
I could confirm that the keyboard is working ( yesterday i was just behind the
box due to test on the
On Sat, 28 Apr 2007, Vincent ETIENNE wrote:
I now don't immediately see how this could happen - the vendor ID
seems to be propagated properly from hid_probe() (nothing has been
changed in this codepath), so this would mean that hid_probe() has
been passed usb_interface for which
On Sat, 28 Apr 2007, Jiri Kosina wrote:
On Sat, 28 Apr 2007, Vincent ETIENNE wrote:
I now don't immediately see how this could happen - the vendor ID
seems to be propagated properly from hid_probe() (nothing has been
changed in this codepath), so this would mean that hid_probe() has
Le Saturday 28 April 2007 21:50:30 Alan Stern, vous avez écrit :
No, it isn't a problem in the USB core. The device itself is messed up;
it really does report idVendor and idProduct both equal to 0.
Jiri, don't worry about all those other devices in the listing that also
have idVendor and
Le Saturday 28 April 2007 00:32:37 Andrew Morton, vous avez écrit :
On Fri, 27 Apr 2007 22:05:28 +0200
because we thought we'd fixed the rtnl_lock() problems in 2.6.21-rc7-mm2.
Are you sure that log is from 2.6.21-rc7-mm2?
Yes. I have retested it another time ( for adding the small usb
Hi Jiri,
On Sat, 28 Apr 2007, Jiri Kosina wrote:
Paul, do you have any idea? In fact, what was your reason for putting this
WARN_ON() there?
The static quirk list uses idVendor == 0 to mark the end of
hid_blacklist[], so we don't expect any device to have idVendor == 0. If
a device is
On Sat, 28 Apr 2007, Jiri Kosina wrote:
> This BUG (it's in fact a warning) is this one:
>WARN_ON(idVendor == 0);
> I now don't immediately see how this could happen - the vendor ID seems
> to be propagated properly from hid_probe() (nothing has been changed in
> this codepath), so this
lem -
> > > the machine tends to hang after some minutes work in X. That hang is
> > > unusual in that moving the mouse still move the X cursor, but everything
> > > else stops and sysrq fails me. But that is another story.
> > [...]
> > > The (first
On Fri, 27 Apr 2007, Greg KH wrote:
> > BUG: at drivers/hid/usbhid/hid-quirks.c:480 usbhid_exists_dquirk()
[ .. stacktraces stripped .. ]
> Jiri, any thoughts about this? This looks like it comes from your tree
> as 2.6.21 doesn't have the drivers/hid/usbhid/ directory...
Paul (author of the
On Fri, Apr 27, 2007 at 11:25:46AM +0200, VE (HOME) wrote:
> Andrew Morton wrote:
> > On Thu, 26 Apr 2007 20:58:32 +0200 Vincent ETIENNE <[EMAIL PROTECTED]>
> > wrote:
> >
> >
> > This was due to locking bustage in the net tree. It should be fixed
> > in 2.6.21-rc7-mm2.
>
> I have tried this
in that moving the mouse still move the X cursor, but everything
> > else stops and sysrq fails me. But that is another story.
> [...]
> > The (first) "hanging" patch in 2.6.21-rc6-mm1 is: git-acpi.patch
>
> Hi Helge,
>
> thanks for the effort. If you take stock
at separately.
>
> And also a strange problem : dhcp server and dns server was started before
> bond0 was completly up ( eth0 and eth1 was declared down at this time and
> up a few times later : was not the case with later 2.6.21-rc6-mm1 )
>
-
To unsubscribe from this list: send the l
bond0 was completly up ( eth0 and eth1 was declared down at this time and
up a few times later : was not the case with later 2.6.21-rc6-mm1 )
Vincent
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordo
at this time and
up a few times later : was not the case with later 2.6.21-rc6-mm1 )
Vincent
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ
was completly up ( eth0 and eth1 was declared down at this time and
up a few times later : was not the case with later 2.6.21-rc6-mm1 )
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org
the X cursor, but everything
else stops and sysrq fails me. But that is another story.
[...]
The (first) hanging patch in 2.6.21-rc6-mm1 is: git-acpi.patch
Hi Helge,
thanks for the effort. If you take stock rc6-mm1 and revert just
git-acpi.patch, doesn the machine behave correctly
On Fri, Apr 27, 2007 at 11:25:46AM +0200, VE (HOME) wrote:
Andrew Morton wrote:
On Thu, 26 Apr 2007 20:58:32 +0200 Vincent ETIENNE [EMAIL PROTECTED]
wrote:
This was due to locking bustage in the net tree. It should be fixed
in 2.6.21-rc7-mm2.
I have tried this version. Same
On Fri, 27 Apr 2007, Greg KH wrote:
BUG: at drivers/hid/usbhid/hid-quirks.c:480 usbhid_exists_dquirk()
[ .. stacktraces stripped .. ]
Jiri, any thoughts about this? This looks like it comes from your tree
as 2.6.21 doesn't have the drivers/hid/usbhid/ directory...
Paul (author of the
minutes work in X. That hang is
unusual in that moving the mouse still move the X cursor, but everything
else stops and sysrq fails me. But that is another story.
[...]
The (first) hanging patch in 2.6.21-rc6-mm1 is: git-acpi.patch
Hi Helge,
thanks for the effort. If you take
On Sat, 28 Apr 2007, Jiri Kosina wrote:
This BUG (it's in fact a warning) is this one:
WARN_ON(idVendor == 0);
I now don't immediately see how this could happen - the vendor ID seems
to be propagated properly from hid_probe() (nothing has been changed in
this codepath), so this
Hi Jiri,
On Sat, 28 Apr 2007, Jiri Kosina wrote:
Paul, do you have any idea? In fact, what was your reason for putting this
WARN_ON() there?
The static quirk list uses idVendor == 0 to mark the end of
hid_blacklist[], so we don't expect any device to have idVendor == 0. If
a device is
On Thu, 26 Apr 2007 20:58:32 +0200 Vincent ETIENNE <[EMAIL PROTECTED]> wrote:
> Apr 26 11:09:34 jupiter2 RTNL: assertion failed at
> net/ipv4/devinet.c
> (1055) Apr 26 11:09:34 jupiter2
> Apr 26 11:09:34 jupiter2 Call Trace:
> Apr 26
hat hang is
> > unusual in that moving the mouse still move the X cursor, but everything
> > else stops and sysrq fails me. But that is another story.
> [...]
> > The (first) "hanging" patch in 2.6.21-rc6-mm1 is: git-acpi.patch
linux-acpi: we have a problem.
> Hi He
srq fails me. But that is another story.
[...]
> The (first) "hanging" patch in 2.6.21-rc6-mm1 is: git-acpi.patch
Hi Helge,
thanks for the effort. If you take stock rc6-mm1 and revert just
git-acpi.patch, doesn the machine behave correctly?
--
Jiri Kosina
-
To unsubscribe from
calling every hanging kernel "bad" will at least find the first broken
patch.
7: boots up ok!
8,9,10: hangs at the aboce mentioned ACPI message
The (first) "hanging" patch in 2.6.21-rc6-mm1 is: git-acpi.patch
Helge Hafting
-
To unsubscribe from this list: send the lin
Le Thursday 26 April 2007 22:44:59 Jay Vosburgh, vous avez écrit :
> Chris Snook <[EMAIL PROTECTED]> wrote:
> >Vincent ETIENNE wrote:
> >> Hi,
> >>
> >> Summary :
> >>Got this trace when one network interface come down or up in a 2
> >>interfaces bonding. So far, system seems to
Chris Snook <[EMAIL PROTECTED]> wrote:
>Vincent ETIENNE wrote:
>> Hi,
>>
>> Summary :
>> Got this trace when one network interface come down or up in a 2
>> interfaces bonding. So far, system seems to survive to this problem
>> and works fine.
>
>I'm investigating a
attention )
Keywords ; network, bonding
Version : Linux version 2.6.21-rc6-mm1 ([EMAIL PROTECTED]) (gcc version 4.1.1
(Gentoo 4.1.1-r3)) #3 SMP Thu Apr 26 08:45:06 CEST 2007
Output of /var/log/messages
Apr 26 11:09:34 jupiter2 e1000: eth0: e1000_watchdog_task: NIC Link
a 2.6.20 and 2.6.19 vanilla kernel ( identical problem
but in
onecase the system doesn't survive : that the reason the problem catch
my
attention )
Keywords; network, bonding
Version : Linux version 2.6.21-rc6-mm1 ([EMAIL PROTECTED]) (gcc version
4.1.1
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
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
a 2.6.20 and 2.6.19 vanilla kernel ( identical problem
but in
onecase the system doesn't survive : that the reason the problem catch
my
attention )
Keywords; network, bonding
Version : Linux version 2.6.21-rc6-mm1 ([EMAIL PROTECTED]) (gcc version
4.1.1
attention )
Keywords ; network, bonding
Version : Linux version 2.6.21-rc6-mm1 ([EMAIL PROTECTED]) (gcc version 4.1.1
(Gentoo 4.1.1-r3)) #3 SMP Thu Apr 26 08:45:06 CEST 2007
Output of /var/log/messages
Apr 26 11:09:34 jupiter2 e1000: eth0: e1000_watchdog_task: NIC Link
Chris Snook [EMAIL PROTECTED] wrote:
Vincent ETIENNE wrote:
Hi,
Summary :
Got this trace when one network interface come down or up in a 2
interfaces bonding. So far, system seems to survive to this problem
and works fine.
I'm investigating a similar/possibly
Le Thursday 26 April 2007 22:44:59 Jay Vosburgh, vous avez écrit :
Chris Snook [EMAIL PROTECTED] wrote:
Vincent ETIENNE wrote:
Hi,
Summary :
Got this trace when one network interface come down or up in a 2
interfaces bonding. So far, system seems to survive to this problem
will at least find the first broken
patch.
7: boots up ok!
8,9,10: hangs at the aboce mentioned ACPI message
The (first) hanging patch in 2.6.21-rc6-mm1 is: git-acpi.patch
Helge Hafting
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL
. But that is another story.
[...]
The (first) hanging patch in 2.6.21-rc6-mm1 is: git-acpi.patch
Hi Helge,
thanks for the effort. If you take stock rc6-mm1 and revert just
git-acpi.patch, doesn the machine behave correctly?
--
Jiri Kosina
-
To unsubscribe from this list: send the line unsubscribe
the mouse still move the X cursor, but everything
else stops and sysrq fails me. But that is another story.
[...]
The (first) hanging patch in 2.6.21-rc6-mm1 is: git-acpi.patch
linux-acpi: we have a problem.
Hi Helge,
thanks for the effort. If you take stock rc6-mm1 and revert just
git
On Thu, 26 Apr 2007 20:58:32 +0200 Vincent ETIENNE [EMAIL PROTECTED] wrote:
Apr 26 11:09:34 jupiter2 RTNL: assertion failed at
net/ipv4/devinet.c
(1055) Apr 26 11:09:34 jupiter2
Apr 26 11:09:34 jupiter2 Call Trace:
Apr 26 11:09:34
On Wed, 25 Apr 2007 23:39:54 +0200, "J.A. Magallón" <[EMAIL PROTECTED]> wrote:
> On Wed, 25 Apr 2007 22:50:39 +0200, "J.A. Magallón" <[EMAIL PROTECTED]> wrote:
...
>
> But I think I found the problem.
> In short, in /dev/pts is mounted before /dev. I remounted it and ssh worked
> fine again.
>
> >
> > > > > On Sun, 8 Apr 2007 14:35:59 -0700, Andrew Morton <[EMAIL PROTECTED]>
> > > > > wrote:
> > > > >
> > > > > >
> > > > > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.
> > > On Tue, 24 Apr 2007 10:10:41 +0200 "J.A. Magallón" <[EMAIL PROTECTED]>
> > > wrote:
> > >
> > > > On Sun, 8 Apr 2007 14:35:59 -0700, Andrew Morton <[EMAIL PROTECTED]>
> > > > wrote:
> > > >
> > > &g
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 getting hangs at different stages of boot,
depending on your local
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 getting hangs at different stages of boot,
> > depending on your local
Jiri Kosina wrote:
[...]
So I guess you are operating on some broken version of 2.6.21-rc6-mm1
codebase if you are getting rejects on this trivial patch.
Didn't think of that - the codebase might be wrong.
Anyway, based on information you have provided in your later messages, it
seems
Jiri Kosina wrote:
[...]
So I guess you are operating on some broken version of 2.6.21-rc6-mm1
codebase if you are getting rejects on this trivial patch.
Didn't think of that - the codebase might be wrong.
Anyway, based on information you have provided in your later messages, it
seems
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 getting hangs at different stages of boot,
depending on your local
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 getting hangs at different stages of boot,
depending on your local
PROTECTED]
wrote:
On Sun, 8 Apr 2007 14:35:59 -0700, Andrew Morton [EMAIL PROTECTED]
wrote:
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc6/2.6.21-rc6-mm1/
- Lots of x86 updates
Has somthing related with PTY's
PROTECTED]
wrote:
On Tue, 24 Apr 2007 10:10:41 +0200 J.A. Magallón [EMAIL PROTECTED]
wrote:
On Sun, 8 Apr 2007 14:35:59 -0700, Andrew Morton [EMAIL PROTECTED]
wrote:
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc6/2.6.21-rc6
On Wed, 25 Apr 2007 23:39:54 +0200, J.A. Magallón [EMAIL PROTECTED] wrote:
On Wed, 25 Apr 2007 22:50:39 +0200, J.A. Magallón [EMAIL PROTECTED] wrote:
...
But I think I found the problem.
In short, in /dev/pts is mounted before /dev. I remounted it and ssh worked
fine again.
I'll dig
> wrote:
> >
> > > On Sun, 8 Apr 2007 14:35:59 -0700, Andrew Morton <[EMAIL PROTECTED]>
> > > wrote:
> > >
> > > >
> > > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc6/2.6.21-rc6-mm1/
>
> >
> > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc6/2.6.21-rc6-mm1/
> > >
> > >
> > > - Lots of x86 updates
> > >
> >
> > Has somthing related with PTY's changed in this kernel ?
>
> Not
On Tue, 24 Apr 2007 10:10:41 +0200 "J.A. Magallón" <[EMAIL PROTECTED]> wrote:
> On Sun, 8 Apr 2007 14:35:59 -0700, Andrew Morton <[EMAIL PROTECTED]> wrote:
>
> >
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc6/2.6.21-rc6-
On Sun, 8 Apr 2007 14:35:59 -0700, Andrew Morton <[EMAIL PROTECTED]> wrote:
>
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc6/2.6.21-rc6-mm1/
>
>
> - Lots of x86 updates
>
Has somthing related with PTY's changed in this kernel ?
I have to en
On Sun, 8 Apr 2007 14:35:59 -0700, Andrew Morton [EMAIL PROTECTED] wrote:
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc6/2.6.21-rc6-mm1/
- Lots of x86 updates
Has somthing related with PTY's changed in this kernel ?
I have to enable legacy PTY handling
On Tue, 24 Apr 2007 10:10:41 +0200 J.A. Magallón [EMAIL PROTECTED] wrote:
On Sun, 8 Apr 2007 14:35:59 -0700, Andrew Morton [EMAIL PROTECTED] wrote:
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc6/2.6.21-rc6-mm1/
- Lots of x86 updates
Has somthing
/2.6/2.6.21-rc6/2.6.21-rc6-mm1/
- Lots of x86 updates
Has somthing related with PTY's changed in this kernel ?
Not as far as I know, but there were some kobject_uevent changes which
might have caused udev upcalls to break. Perhaps.
I have to enable legacy PTY handling
PROTECTED]
wrote:
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc6/2.6.21-rc6-mm1/
- Lots of x86 updates
Has somthing related with PTY's changed in this kernel ?
Not as far as I know, but there were some kobject_uevent changes which
> "John" == John Stoffel <[EMAIL PROTECTED]> writes:
> "John" == John Stoffel <[EMAIL PROTECTED]> writes:
> Ok, so do I need to do anything special with the next -mm release and
> the next version?
Well, let Alan decide that (2Alan: and I said that HPT code is bogus
> "John" == John Stoffel <[EMAIL PROTECTED]> writes:
>>> > Ok, so do I need to do anything special with the next -mm release and
>>> > the next version?
>>>
>>> Well, let Alan decide that (2Alan: and I said that HPT code is bogus :-).
Alan> Try drivers/ide/pci/hpt366 - if that works grab a
On Wed, 2007-04-18 at 19:00 -0400, Joshua Wise wrote:
> On Tue, 17 Apr 2007, Shaohua Li wrote:
> > Looks there is init order issue of sysfs files. The new refreshed patch
> > should fix your bug.
>
> Yes, that did fix the hang on resume from STR -- that now works fine.
>
> However:
> [EMAIL
On Tue, 17 Apr 2007, Shaohua Li wrote:
Looks there is init order issue of sysfs files. The new refreshed patch
should fix your bug.
Yes, that did fix the hang on resume from STR -- that now works fine.
However:
[EMAIL PROTECTED]:/sys/devices/system/cpu/cpuidle$ cat available_drivers
On Tue, 17 Apr 2007, Shaohua Li wrote:
Looks there is init order issue of sysfs files. The new refreshed patch
should fix your bug.
Yes, that did fix the hang on resume from STR -- that now works fine.
However:
[EMAIL PROTECTED]:/sys/devices/system/cpu/cpuidle$ cat available_drivers
On Wed, 2007-04-18 at 19:00 -0400, Joshua Wise wrote:
On Tue, 17 Apr 2007, Shaohua Li wrote:
Looks there is init order issue of sysfs files. The new refreshed patch
should fix your bug.
Yes, that did fix the hang on resume from STR -- that now works fine.
However:
[EMAIL
John == John Stoffel [EMAIL PROTECTED] writes:
Ok, so do I need to do anything special with the next -mm release and
the next version?
Well, let Alan decide that (2Alan: and I said that HPT code is bogus :-).
Alan Try drivers/ide/pci/hpt366 - if that works grab a dmesg and let
Alan me
John == John Stoffel [EMAIL PROTECTED] writes:
John == John Stoffel [EMAIL PROTECTED] writes:
Ok, so do I need to do anything special with the next -mm release and
the next version?
Well, let Alan decide that (2Alan: and I said that HPT code is bogus :-).
Alan Try drivers/ide/pci/hpt366
Sergei Shtylyov wrote:
HPT chips are surely not a good example of how to do things, more like
an example how *not* to do. :-)
That explains a lot! :)
(guess who's first ATA work was on the Highpoint driver..
.. no need to post the answer here, though)
Cheers
-
To unsubscribe from this
Hello.
John Stoffel wrote:
Ok, so do I need to do anything special with the next -mm release and
the next version?
Well, let Alan decide that (2Alan: and I said that HPT code is bogus :-).
Alan> Try drivers/ide/pci/hpt366 - if that works grab a dmesg and let
Alan> me know. It means that
>> > Ok, so do I need to do anything special with the next -mm release and
>> > the next version?
>>
>> Well, let Alan decide that (2Alan: and I said that HPT code is bogus :-).
Alan> Try drivers/ide/pci/hpt366 - if that works grab a dmesg and let
Alan> me know. It means that Sergei's DPLL
> > Ok, so do I need to do anything special with the next -mm release and
> > the next version?
>
>Well, let Alan decide that (2Alan: and I said that HPT code is bogus :-).
Try drivers/ide/pci/hpt366 - if that works grab a dmesg and let me know.
It means that Sergei's DPLL sync code seems to
John Stoffel wrote:
I was just testing out 2.6.21-rc6-mm1 to test some Cyclades patches
and I noticed that my HPT302 (rev1) controller with a pair of 120gb WD
disks are not longer detected and I get the following in the dmesg
logs:
[ 148.121490] hpt37x: DPLL did not stabilize.
Where
>>>>> "Sergei" == Sergei Shtylyov <[EMAIL PROTECTED]> writes:
Sergei> Hello.
Sergei> John Stoffel wrote:
>> I was just testing out 2.6.21-rc6-mm1 to test some Cyclades patches
>> and I noticed that my HPT302 (rev1) controller with a pair of 12
Hello.
John Stoffel wrote:
I was just testing out 2.6.21-rc6-mm1 to test some Cyclades patches
and I noticed that my HPT302 (rev1) controller with a pair of 120gb WD
disks are not longer detected and I get the following in the dmesg
logs:
[ 148.121490] hpt37x: DPLL did not stabilize
On Mon, 2007-04-16 at 22:50 -0400, Joshua Wise wrote:
> On Mon, 16 Apr 2007, Shaohua Li wrote:
> > On Sat, 2007-04-14 at 01:45 +0200, Mattia Dongili wrote:
> >> ...
> > please check if the patch at
> > http://marc.info/?l=linux-acpi=117523651630038=2 fixed the issue
>
> I have the same system as
On Mon, 2007-04-16 at 22:50 -0400, Joshua Wise wrote:
On Mon, 16 Apr 2007, Shaohua Li wrote:
On Sat, 2007-04-14 at 01:45 +0200, Mattia Dongili wrote:
...
please check if the patch at
http://marc.info/?l=linux-acpim=117523651630038w=2 fixed the issue
I have the same system as Mattia,
Sergei == Sergei Shtylyov [EMAIL PROTECTED] writes:
Sergei Hello.
Sergei John Stoffel wrote:
I was just testing out 2.6.21-rc6-mm1 to test some Cyclades patches
and I noticed that my HPT302 (rev1) controller with a pair of 120gb WD
disks are not longer detected and I get the following
Hello.
John Stoffel wrote:
I was just testing out 2.6.21-rc6-mm1 to test some Cyclades patches
and I noticed that my HPT302 (rev1) controller with a pair of 120gb WD
disks are not longer detected and I get the following in the dmesg
logs:
[ 148.121490] hpt37x: DPLL did not stabilize
John Stoffel wrote:
I was just testing out 2.6.21-rc6-mm1 to test some Cyclades patches
and I noticed that my HPT302 (rev1) controller with a pair of 120gb WD
disks are not longer detected and I get the following in the dmesg
logs:
[ 148.121490] hpt37x: DPLL did not stabilize.
Where
Ok, so do I need to do anything special with the next -mm release and
the next version?
Well, let Alan decide that (2Alan: and I said that HPT code is bogus :-).
Try drivers/ide/pci/hpt366 - if that works grab a dmesg and let me know.
It means that Sergei's DPLL sync code seems to work
Ok, so do I need to do anything special with the next -mm release and
the next version?
Well, let Alan decide that (2Alan: and I said that HPT code is bogus :-).
Alan Try drivers/ide/pci/hpt366 - if that works grab a dmesg and let
Alan me know. It means that Sergei's DPLL sync code seems
Hello.
John Stoffel wrote:
Ok, so do I need to do anything special with the next -mm release and
the next version?
Well, let Alan decide that (2Alan: and I said that HPT code is bogus :-).
Alan Try drivers/ide/pci/hpt366 - if that works grab a dmesg and let
Alan me know. It means that
Sergei Shtylyov wrote:
HPT chips are surely not a good example of how to do things, more like
an example how *not* to do. :-)
That explains a lot! :)
(guess who's first ATA work was on the Highpoint driver..
.. no need to post the answer here, though)
Cheers
-
To unsubscribe from this
On Mon, 16 Apr 2007, Shaohua Li wrote:
On Sat, 2007-04-14 at 01:45 +0200, Mattia Dongili wrote:
...
please check if the patch at
http://marc.info/?l=linux-acpi=117523651630038=2 fixed the issue
I have the same system as Mattia, and when I applied this patch and turned
CPU_IDLE back on, I got
On Mon, 2007-04-16 at 22:50 -0400, Joshua Wise wrote:
> On Mon, 16 Apr 2007, Shaohua Li wrote:
> > On Sat, 2007-04-14 at 01:45 +0200, Mattia Dongili wrote:
> >> ...
> > please check if the patch at
> > http://marc.info/?l=linux-acpi=117523651630038=2 fixed the issue
>
> I have the same system as
Hi Jeff and crew,
I was just testing out 2.6.21-rc6-mm1 to test some Cyclades patches
and I noticed that my HPT302 (rev1) controller with a pair of 120gb WD
disks are not longer detected and I get the following in the dmesg
logs:
[ 148.121490] hpt37x: DPLL did not stabilize.
Where before
Hi Jeff and crew,
I was just testing out 2.6.21-rc6-mm1 to test some Cyclades patches
and I noticed that my HPT302 (rev1) controller with a pair of 120gb WD
disks are not longer detected and I get the following in the dmesg
logs:
[ 148.121490] hpt37x: DPLL did not stabilize.
Where before
1 - 100 of 264 matches
Mail list logo
