From: Igor M Podlesny <for.poige+linux@gmail.com>
To: Jarek Poplawski <jarkao2@gmail.com>
Cc: Patrick McHardy <kaber@trash.net>, netdev@vger.kernel.org
Subject: > try a more current kernel (e.g. 2.6.26-rc5).
Date: Fri, 13 Jun 2008 04:21:34 +0800 [thread overview]
Message-ID: <4851854E.7050505@gmail.com> (raw)
In-Reply-To: <20080612201548.GA2472@ami.dom.local>
On 2008-06-13 04:15, Jarek Poplawski wrote:
> On Fri, Jun 13, 2008 at 03:46:36AM +0800, Igor M Podlesny wrote:
>> On 2008-06-13 03:36, Jarek Poplawski wrote:
[...]
> Hm... hard to tell. This shouldn't happen and rebooting isn't a solution.
> Try to eliminate this (is it patched kernel BTW?). Check your hardware
> and maybe try a more current kernel (e.g. 2.6.26-rc5).
2.6.26 has changed something in sensors interface and Nvidia's driver could not be
compiled for it as well. As far as I use TwinView I can afford just switching to not
Nvidia's driver.
--
next prev parent reply other threads:[~2008-06-12 20:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-10 14:36 re-formated /Re: Hi!Couldn't you take a look at kernel stack's trace? (ip_route_input+0x91a/0xcc9)/ Igor Podlesny
2008-06-12 12:07 ` Patrick McHardy
2008-06-12 12:24 ` Igor Podlesny
2008-06-12 12:26 ` Patrick McHardy
2008-06-12 19:36 ` Jarek Poplawski
2008-06-12 19:46 ` > with unpatched kernels, and if you tried other than 2.6.25 versions Igor M Podlesny
2008-06-12 20:15 ` Jarek Poplawski
2008-06-12 20:19 ` > Hm... hard to tell. This shouldn't happen and rebooting isn't a solution Igor M Podlesny
2008-06-12 20:49 ` Jarek Poplawski
2008-06-12 20:51 ` > OK, a reboot after a bug can sometimes prevent further data corruption/loss Igor M Podlesny
2008-06-12 21:04 ` Jarek Poplawski
2008-06-12 20:21 ` Igor M Podlesny [this message]
2008-06-12 20:39 ` > try a more current kernel (e.g. 2.6.26-rc5) Stephen Hemminger
2008-06-12 20:44 ` > And kernel developer's can not afford debugging closed source drivers Igor M Podlesny
2008-06-12 20:23 ` > this message has strange "Subject" Igor M Podlesny
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4851854E.7050505@gmail.com \
--to=for.poige+linux@gmail.com \
--cc=jarkao2@gmail.com \
--cc=kaber@trash.net \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).