YES!
seems like 2.6.32.8 with your patch included finally doesn't
spit any backtraces and peername failed errors!
will You push this upstream + to stable?
thanks a lot for Your help!
have a nice day
with best regards
nik
This seems that we missed checking XPT_DEAD too.
Nikola, does adding
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.31 and 2.6.32.
The following bug entry is on the current list of known regressions
introduced between 2.6.31 and 2.6.32. Please verify if it still should
be listed and let the tracking team
On Mon, Feb 22, 2010 at 5:42 AM, Rafael J. Wysocki r...@sisk.pl wrote:
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.31 and 2.6.32.
The following bug entry is on the current list of known regressions
introduced between 2.6.31 and
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.31 and 2.6.32.
The following bug entry is on the current list of known regressions
introduced between 2.6.31 and 2.6.32. Please verify if it still should
be listed and let the tracking team
Hi Rafael,
Sorry, I haven't had time to test newer kernels lately :(, but according to
changelogs, no related problems were fixed till 2.6.32.7...
I'll update problematic machine on wednesday though...
regards
nik
On Mon, Feb 01, 2010 at 01:43:18AM +0100, Rafael J. Wysocki wrote:
This message
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.31 and 2.6.32.
The following bug entry is on the current list of known regressions
introduced between 2.6.31 and 2.6.32. Please verify if it still should
be listed and let me know (either
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.31 and 2.6.32.
The following bug entry is on the current list of known regressions
introduced between 2.6.31 and 2.6.32. Please verify if it still should
be listed and let me know (either
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.31 and 2.6.32.
The following bug entry is on the current list of known regressions
introduced between 2.6.31 and 2.6.32. Please verify if it still should
be listed and let me know (either
Hello Rafael,
I can confirm the bug is still present. I've also created kernel
bugzilla account so I can track the status and provide further
testing/feedback.
Thanks for Your interest.
best regards
nik
On Tue, Dec 29, 2009 at 04:28:57PM +0100, Rafael J. Wysocki wrote:
This message has been
On Tuesday 29 December 2009, Nikola Ciprich wrote:
Hello Rafael,
I can confirm the bug is still present. I've also created kernel
bugzilla account so I can track the status and provide further
testing/feedback.
Great, thanks for the update.
Rafael
--
To unsubscribe from this list: send the
10 matches
Mail list logo
