On Wed, 14 Jan 2009 18:34:43 +0100
Xav' wrote:
> On Wed, 14 Jan 2009 08:14:01 -0500, David Relson
> wrote:
> > On Wed, 14 Jan 2009 14:01:28 +0100
> > Daniel Pielmeier wrote:
> >
> >> 2009/1/14 David Relson :
> >> >
> >> > I noticed the "taint" message and don't think that's right. How
> >> > do
On Wed, 14 Jan 2009 08:14:01 -0500, David Relson
wrote:
> On Wed, 14 Jan 2009 14:01:28 +0100
> Daniel Pielmeier wrote:
>
>> 2009/1/14 David Relson :
>> >
>> > I noticed the "taint" message and don't think that's right. How do
>> > I identify the tainted module?
>> >
>>
>> Jan 13 21:35:04 osage
Am Mittwoch, 14. Januar 2009 14:36:11 schrieb Daniel Pielmeier:
> 2009/1/14 David Relson :
> > Can a program, i.e. rrdtool, be tainted? I'd not think so since the
> > program is in user space, not kernel space.
>
> According to LWN [1] tainting the kernel from user space is possible.
>
> [1] http:
2009/1/14 David Relson :
>
> Can a program, i.e. rrdtool, be tainted? I'd not think so since the
> program is in user space, not kernel space.
>
According to LWN [1] tainting the kernel from user space is possible.
[1] http://lwn.net/Articles/184879/
--
Regards,
Daniel
On Mittwoch 14 Januar 2009, David Relson wrote:
> On Wed, 14 Jan 2009 14:01:28 +0100
>
> Daniel Pielmeier wrote:
> > 2009/1/14 David Relson :
> > > I noticed the "taint" message and don't think that's right. How do
> > > I identify the tainted module?
> >
> > Jan 13 21:35:04 osage Pid: 13119, comm
2009/1/14 David Relson :
>
> I noticed the "taint" message and don't think that's right. How do I
> identify the tainted module?
>
Jan 13 21:35:04 osage Pid: 13119, comm: rrdtool Tainted: G D W
2.6.28-gentoo #11
rrdtool?
--
Regards,
Daniel
On Wed, 14 Jan 2009 13:46:47 +0100
Dirk Heinrichs wrote:
> Am Mittwoch, den 14.01.2009, 07:38 -0500 schrieb ext David Relson:
> > I presume it'd be useful to report these upstream.
>
> According to the attached files, your kernel is tainted. Nobody will
> care.
>
> First try without the tainting
Am Mittwoch, den 14.01.2009, 07:38 -0500 schrieb ext David Relson:
> I presume it'd be useful to report these upstream.
According to the attached files, your kernel is tainted. Nobody will
care.
First try without the tainting modules. If the problem remains, _then_
file a bug report (on b.g.o, no
Yesterday evening, I had a series of kernel BUG events logged. They
didn't actually _crash_ my workstation but I rebooted it anyway. Last
night at 02:27:09 another BUG halted the machine. Attached file
BUGS.txt summarizes the BUGs logged. Attached files messages.*.txt
have the full messages.
I
9 matches
Mail list logo