9:04 a.m.
This has been going on of depending on kernels shipped with FC6-8 I
noticed it...
( HW: Dell inspiron 6000 ) ( yes with the latest kernel FC8 )
Uhhuh. NMI received for unknown reason bX on CPU 0.
You have some hardware problem, likely on the PCI bus.
Dazed and confused, but trying to continue....
Can we fix this messages somehow it's kinda misleading, it
suggest that the hw is failing when in 99% it's a buggy driver..
When I read "You have some hardware problem" I think
my hardware is failing and I need to backup my data
and replace the part that is failing....
Better would be..
Uhhuh. NMI received for unknown reason bX on CPU 0.
I have been feed [ driver X ] buggy driver ...
Dazed and confused, but trying to continue....
Best regards.
Johann B.
10:43 a.m.
On Mon, 2008-03-10 at 14:04 +0000, "Jóhann B. Guðmundsson" wrote:
This has been going on of depending on kernels shipped with FC6-8 I
noticed it...
( HW: Dell inspiron 6000 ) ( yes with the latest kernel FC8 )
Uhhuh. NMI received for unknown reason bX on CPU 0.
You have some hardware problem, likely on the PCI bus.
Dazed and confused, but trying to continue....
Can we fix this messages somehow it's kinda misleading, it
suggest that the hw is failing when in 99% it's a buggy driver..
When I read "You have some hardware problem" I think
my hardware is failing and I need to backup my data
and replace the part that is failing....
Better would be..
Uhhuh. NMI received for unknown reason bX on CPU 0.
I have been feed [ driver X ] buggy driver ...
Dazed and confused, but trying to continue....
Why do you think it is a faulty driver? For me it seems that most
obvious reason for triggering a NMI is a buggy hardware.
--
Lubomir Kundrak (Red Hat Security Response Team)
10:48 a.m.
Am Montag, den 10.03.2008, 16:43 +0100 schrieb Lubomir Kundrak:
On Mon, 2008-03-10 at 14:04 +0000, "Jóhann B. Guðmundsson"
wrote:
> This has been going on of depending on kernels shipped with FC6-8 I
> noticed it...
> ( HW: Dell inspiron 6000 ) ( yes with the latest kernel FC8 )
>
> Uhhuh. NMI received for unknown reason bX on CPU 0.
> You have some hardware problem, likely on the PCI bus.
> Dazed and confused, but trying to continue....
>
> Can we fix this messages somehow it's kinda misleading, it
> suggest that the hw is failing when in 99% it's a buggy driver..
>
> When I read "You have some hardware problem" I think
> my hardware is failing and I need to backup my data
> and replace the part that is failing....
>
> Better would be..
>
> Uhhuh. NMI received for unknown reason bX on CPU 0.
> I have been feed [ driver X ] buggy driver ...
> Dazed and confused, but trying to continue....
Why do you think it is a faulty driver? For me it seems that most
obvious reason for triggering a NMI is a buggy hardware.
--
Lubomir Kundrak (Red Hat Security Response Team)
I know that there are drivers that produce NMI faults. I never saw that
on linux, though.
11:46 a.m.
On Mon, Mar 10, 2008 at 04:48:50PM +0100, Christoph Höger wrote:
> Why do you think it is a faulty driver? For me it seems that
most
> obvious reason for triggering a NMI is a buggy hardware.
I know that there are drivers that produce NMI faults. I never saw that
on linux, though.
NMI is almost always indicating hardware problems and there are very few
software ways to cause them on x86.
1:51 p.m.
Alan Cox wrote:
On Mon, Mar 10, 2008 at 04:48:50PM +0100, Christoph Höger wrote:
>> Why do you think it is a faulty driver? For me it seems that most
>> obvious reason for triggering a NMI is a buggy hardware.
>>
> I know that there are drivers that produce NMI faults. I never saw that
> on linux, though.
>
NMI is almost always indicating hardware problems and there are very few
software ways to cause them on x86.
But there are software ways....
When reporting hardware problems those reports need to be both accurate
and specific
in which hardware parts are failing ( Faulty memory, faulty motherboard
faulty hard drive etc.. )
So when the end user receives the report he knows which components needs
to be replace/fixed..
and is not spending money in something that might not be broken/need fixing.
In my case I have always thought it was something regarding the
Motherboard + DVD drive in the laptop..
Ever since I was trying to get better DVD playback, back in FC-5 and I
received this report
for the first time ( Atleast something I fiddle with caused the error to
appear :) ).
BTW I did end up with smoother DVD playback .
To make things worse this is an Dell Inspiron 6000 with the special
burst into flames integration. ( Manage to remove the battery
in time, had the laptop in the freezer for 3 hours and then I could
started it again thou my hard drive got fried and possibly something else)
That along with the great part of Dells engineering putting the air
intake underneath the laptop ( HP engineers are this smart also :s ,
this actually
makes one wonder who stole the design from who.. ) which can cause the
laptop to run hot! that might cause weird behavior in hardware,
is not ruling out that this is not an actually hardware problem.. Far
from it actually :)
But what has always puzzle me was the fact that I don't get this report
with every kernel, which suggest that
there might be something else causing these reports.
I have finally order an IBM/Lenovo T61p 2.6 Penryn fully spec from USA
just waiting for it to be delivered to replace the Dell Inspiron 6000.
The Dell Inspiron 6000 machine will remain the reminder of it's life an
FC rawhide testing machine...
Why did I order it from USA?
Prize.. ca $3000 in USA, ca $6000 in Iceland.
Only IBM/Lenovo products are this expensive in Iceland, you would get a
similar Dell hardware spec.
laptop for around $3000 and they might even throw the burst into flames
feature for free..
Why IBM/Lenovo Thinkpad?
In case I have the both the laptops running side by side I need A laptop
that can handle it if the Dell
laptop decides to go Supernova...
Best regards.
Johann B.
2:08 p.m.
On Mon, Mar 10, 2008 at 5:46 PM, Alan Cox <alan(a)redhat.com> wrote:
On Mon, Mar 10, 2008 at 04:48:50PM +0100, Christoph Höger wrote:
> > Why do you think it is a faulty driver? For me it seems that most
> > obvious reason for triggering a NMI is a buggy hardware.
> I know that there are drivers that produce NMI faults. I never saw that
> on linux, though.
NMI is almost always indicating hardware problems and there are very few
software ways to cause them on x86.
Is a corrupt /var/lib/random-seed one of them?
I remember seeing this once in the past (x86_64) ...
12:12 p.m.
Lubomir Kundrak wrote:
On Mon, 2008-03-10 at 14:04 +0000, "Jóhann B. Guðmundsson"
wrote:
> This has been going on of depending on kernels shipped with FC6-8 I
> noticed it...
> ( HW: Dell inspiron 6000 ) ( yes with the latest kernel FC8 )
>
> Uhhuh. NMI received for unknown reason bX on CPU 0.
> You have some hardware problem, likely on the PCI bus.
> Dazed and confused, but trying to continue....
>
> Can we fix this messages somehow it's kinda misleading, it
> suggest that the hw is failing when in 99% it's a buggy driver..
>
> When I read "You have some hardware problem" I think
> my hardware is failing and I need to backup my data
> and replace the part that is failing....
>
> Better would be..
>
> Uhhuh. NMI received for unknown reason bX on CPU 0.
> I have been feed [ driver X ] buggy driver ...
> Dazed and confused, but trying to continue....
>
Why do you think it is a faulty driver? For me it seems that most
obvious reason for triggering a NMI is a buggy hardware.
I think it's a faulty driver because it varies on which kernel
i'm running whether I see this in my logs or not FC-6 - FC-8.....
Hence logic says that something that is being change between kernels
are causing this otherwise the kernel would ALWAYS being reporting
this...
The first time I saw it was when I made some custom kernel with hacks
to get better dvd playing experince in FC5 ( dvd playback was lagging )
When I ran the stock kernel in FC5 I did not receive the message..
Also see https://bugzilla.redhat.com/show_bug.cgi?id=213227
Follow the Ubuntu links as well..
If this error is accurate, as in a buggy driver/wrong driver being used
( hardware configuration error ) which behaves similar but not exactly
the same
( then the detection process on which driver to use is buggy ) cant
cause this error
( trigger false signals on the NMI circuitry )
then ok I need to replace my hardware..
But if it can the msg needs rewriting...
If anyone can tell me how I can *debug* it further
I'm all ears..
Best regards
Johann B.
1:11 p.m.
Hence logic says that something that is being change between kernels
are causing this otherwise the kernel would ALWAYS being reporting
this...
Unlikely - hardware problems are often dependant on alignment of objects
and other chance happenings. If you've got bad RAM and the faulty bits happen
to land in a location where the faulty bits don't show a fault (its often
combination based) you'll see exactly what is described.
If anyone can tell me how I can *debug* it further
I'm all ears..
memtest86 full night run is what I usually start with for such cases.
4:18 p.m.
On Mon, 2008-03-10 at 14:11 -0400, Alan Cox wrote:
> Hence logic says that something that is being change between
kernels
> are causing this otherwise the kernel would ALWAYS being reporting
> this...
Unlikely - hardware problems are often dependant on alignment of objects
and other chance happenings. If you've got bad RAM and the faulty bits happen
to land in a location where the faulty bits don't show a fault (its often
combination based) you'll see exactly what is described.
> If anyone can tell me how I can *debug* it further
> I'm all ears..
memtest86 full night run is what I usually start with for such cases.
I've seen this problem on a Dell Insprion 6000 as well, its definitely a
machine problem as opposed to a bad RAM case... I've never tracked down
what triggers it though... it may be heat related ...
Dave.
11:53 a.m.
On Mon, Mar 10, 2008 at 2:18 PM, Dave Airlie <airlied(a)redhat.com> wrote:
On Mon, 2008-03-10 at 14:11 -0400, Alan Cox wrote:
> > Hence logic says that something that is being change between kernels
> > are causing this otherwise the kernel would ALWAYS being reporting
> > this...
>
> Unlikely - hardware problems are often dependant on alignment of objects
> and other chance happenings. If you've got bad RAM and the faulty bits happen
> to land in a location where the faulty bits don't show a fault (its often
> combination based) you'll see exactly what is described.
>
> > If anyone can tell me how I can *debug* it further
> > I'm all ears..
>
> memtest86 full night run is what I usually start with for such cases.
>
>
I've seen this problem on a Dell Insprion 6000 as well, its definitely a
machine problem as opposed to a bad RAM case... I've never tracked down
what triggers it though... it may be heat related ...
I have a Dell Inspiron 9300. A few months ago the NMI problem suddenly
appeared and was happening almost daily. I update from Rawhide pretty
much daily and after a week or so the problem disappeared.
After today's kernel update
2.6.25-0.113.rc5.git2.fc9
the problem reappeared (so much for taking pleasure in the misfortune
of others, sigh)
I'm also more inclined to think that it is a driver problem rather
than a hardware problem.
darrell
12:07 p.m.
darrell pfeifer wrote:
On Mon, Mar 10, 2008 at 2:18 PM, Dave Airlie
<airlied(a)redhat.com> wrote:
> On Mon, 2008-03-10 at 14:11 -0400, Alan Cox wrote:
> > > Hence logic says that something that is being change between kernels
> > > are causing this otherwise the kernel would ALWAYS being reporting
> > > this...
> >
> > Unlikely - hardware problems are often dependant on alignment of objects
> > and other chance happenings. If you've got bad RAM and the faulty bits
happen
> > to land in a location where the faulty bits don't show a fault (its often
> > combination based) you'll see exactly what is described.
> >
> > > If anyone can tell me how I can *debug* it further
> > > I'm all ears..
> >
> > memtest86 full night run is what I usually start with for such cases.
> >
> >
>
> I've seen this problem on a Dell Insprion 6000 as well, its definitely a
> machine problem as opposed to a bad RAM case... I've never tracked down
> what triggers it though... it may be heat related ...
>
>
I have a Dell Inspiron 9300. A few months ago the NMI problem suddenly
appeared and was happening almost daily. I update from Rawhide pretty
much daily and after a week or so the problem disappeared.
After today's kernel update
2.6.25-0.113.rc5.git2.fc9
the problem reappeared (so much for taking pleasure in the misfortune
of others, sigh)
I'm also more inclined to think that it is a driver problem rather
than a hardware problem.
darrell
could take a look at the running temperature on the laptop
when it's reporting this..
( confirming or not confirming it could be heat related.. )
Best regards
Johann B.
12:02 p.m.
Dave Airlie wrote:
On Mon, 2008-03-10 at 14:11 -0400, Alan Cox wrote:
>> Hence logic says that something that is being change between kernels
>> are causing this otherwise the kernel would ALWAYS being reporting
>> this...
>>
> Unlikely - hardware problems are often dependant on alignment of objects
> and other chance happenings. If you've got bad RAM and the faulty bits happen
> to land in a location where the faulty bits don't show a fault (its often
> combination based) you'll see exactly what is described.
>
>
>> If anyone can tell me how I can *debug* it further
>> I'm all ears..
>>
> memtest86 full night run is what I usually start with for such cases.
>
>
>
I've seen this problem on a Dell Insprion 6000 as well, its definitely a
machine problem as opposed to a bad RAM case... I've never tracked down
what triggers it though... it may be heat related ...
Dave.
Sorry about late responce it takes time running these tests...
Have done basic motherboard tests everything "passed"....
Have done cpu test ( cpu burn-in ) running time 7hours+ without errors
Have run Memtest86+ for eleven hours now without errors.
Dave not a bad guess, thats it's head related ( matches some of the HP
models reports as well )
and if it's heat related it's very easy to debug it :)
Simply put the laptop on any soft fabric ( since the heat is getting
blown out
at the bottom of the laptop it's air vent gets blocked hence all the
head is circulating inside
the laptop ( I guess you already know this since you own one of the
masterly engineered laptops)
See if the kernel reports it, let the machine cool down and check if the
kernel is still reporting it.
Dave it would be nice if you could confirm it's heat or not heat related
along with me.
( And possible everyone that owns a masterly engineered laptops such as
this or HP models )
If it's heat related I think all bug reports about this can be closed or
at least the bug
reporter can be asked of "make and model and running heat" when the
kernel reports this.
If we can not confirm that it's heat related could you Alan C. take some
of look at this
problem?
Best regards
Johann B.
11 a.m.
On Mon, 2008-03-10 at 14:04 +0000, "Jóhann B. Guðmundsson" wrote:
This has been going on of depending on kernels shipped with FC6-8 I
noticed it...
( HW: Dell inspiron 6000 ) ( yes with the latest kernel FC8 )
Uhhuh. NMI received for unknown reason bX on CPU 0.
You have some hardware problem, likely on the PCI bus.
Dazed and confused, but trying to continue....
Can we fix this messages somehow it's kinda misleading, it
suggest that the hw is failing when in 99% it's a buggy driver..
When I read "You have some hardware problem" I think
my hardware is failing and I need to backup my data
and replace the part that is failing....
Better would be..
Uhhuh. NMI received for unknown reason bX on CPU 0.
I have been feed [ driver X ] buggy driver ...
Dazed and confused, but trying to continue....
I've only seen this happen on linux boxen with buggy hardware,
especially bad ram or bad ram controller.
In fact, when I see that message I just go straight for replacing memory
chips without even thinking...
YMMV,
David
12:19 p.m.
Hi.
On Mon, 10 Mar 2008 12:00:06 -0400, David Mansfield wrote
I've only seen this happen on linux boxen with buggy hardware,
especially bad ram or bad ram controller.
I've seen it on my X60s with a series of e1000 drivers. The root cause
is a buggy hardware controller, I think (buggy as in buggy by design, not
in my special case), but it can be worked around in the driver, which is
why the error suddenly appeared (and was subsequently fixed after people
found out what was going wrong).
10:25 a.m.
2008/3/10 "Jóhann B. Guðmundsson" <johannbg(a)hi.is>:
This has been going on of depending on kernels shipped with FC6-8 I
noticed it...
( HW: Dell inspiron 6000 ) ( yes with the latest kernel FC8 )
Uhhuh. NMI received for unknown reason bX on CPU 0.
You have some hardware problem, likely on the PCI bus.
Dazed and confused, but trying to continue....
Can we fix this messages somehow it's kinda misleading, it
suggest that the hw is failing when in 99% it's a buggy driver..
When I read "You have some hardware problem" I think
my hardware is failing and I need to backup my data
and replace the part that is failing....
Better would be..
Uhhuh. NMI received for unknown reason bX on CPU 0.
I have been feed [ driver X ] buggy driver ...
Dazed and confused, but trying to continue....
I have a Dell Inspiron 9300 with a radeon card, using latest rawhide.
As I mentioned yesterday, I had seen these errors a few months ago but
they went away.
Yesterday I had 3 NMI's in the space of about 4 hours. In each case, I
had just selected a menu or submenu and it had just finished being
drawn to the screen.
I turned off compiz and haven't had an NMI all morning. If you're
using compiz you might want to give that a try.
That does tend to point to a buggy driver.
darrell
10:48 a.m.
darrell pfeifer wrote:
2008/3/10 "Jóhann B. Guðmundsson" <johannbg(a)hi.is>:
> This has been going on of depending on kernels shipped with FC6-8 I
> noticed it...
> ( HW: Dell inspiron 6000 ) ( yes with the latest kernel FC8 )
>
> Uhhuh. NMI received for unknown reason bX on CPU 0.
> You have some hardware problem, likely on the PCI bus.
> Dazed and confused, but trying to continue....
>
> Can we fix this messages somehow it's kinda misleading, it
> suggest that the hw is failing when in 99% it's a buggy driver..
>
> When I read "You have some hardware problem" I think
> my hardware is failing and I need to backup my data
> and replace the part that is failing....
>
> Better would be..
>
> Uhhuh. NMI received for unknown reason bX on CPU 0.
> I have been feed [ driver X ] buggy driver ...
> Dazed and confused, but trying to continue....
>
>
I have a Dell Inspiron 9300 with a radeon card, using latest rawhide.
As I mentioned yesterday, I had seen these errors a few months ago but
they went away.
Yesterday I had 3 NMI's in the space of about 4 hours. In each case, I
had just selected a menu or submenu and it had just finished being
drawn to the screen.
I turned off compiz and haven't had an NMI all morning. If you're
using compiz you might want to give that a try.
That does tend to point to a buggy driver.
darrell
Check what the temperature is showing you next time you receive the
messages..
I'm not using compiz... :)
Best regards..
Johann B.
5:21 p.m.
On Fri, 2008-03-14 at 08:25 -0700, darrell pfeifer wrote:
2008/3/10 "Jóhann B. Guðmundsson" <johannbg(a)hi.is>:
> This has been going on of depending on kernels shipped with FC6-8 I
> noticed it...
> ( HW: Dell inspiron 6000 ) ( yes with the latest kernel FC8 )
>
> Uhhuh. NMI received for unknown reason bX on CPU 0.
> You have some hardware problem, likely on the PCI bus.
> Dazed and confused, but trying to continue....
>
> Can we fix this messages somehow it's kinda misleading, it
> suggest that the hw is failing when in 99% it's a buggy driver..
>
> When I read "You have some hardware problem" I think
> my hardware is failing and I need to backup my data
> and replace the part that is failing....
>
> Better would be..
>
> Uhhuh. NMI received for unknown reason bX on CPU 0.
> I have been feed [ driver X ] buggy driver ...
> Dazed and confused, but trying to continue....
>
I have a Dell Inspiron 9300 with a radeon card, using latest rawhide.
As I mentioned yesterday, I had seen these errors a few months ago but
they went away.
Yesterday I had 3 NMI's in the space of about 4 hours. In each case, I
had just selected a menu or submenu and it had just finished being
drawn to the screen.
I turned off compiz and haven't had an NMI all morning. If you're
using compiz you might want to give that a try.
That does tend to point to a buggy driver.
Could still be heat related, running the 3D engine may cause more heat
to be generated.. I've been running compiz on my Inspiron 6000 for the
last week and not seen any NMIs, but I've also not being using it for
long periods of time, as that machine has been relegated to being the
beside the couch machine...
Dave.
darrell
6:31 p.m.
On Fri, Mar 14, 2008 at 3:21 PM, Dave Airlie <airlied(a)redhat.com> wrote:
Could still be heat related, running the 3D engine may cause more heat
to be generated.. I've been running compiz on my Inspiron 6000 for the
last week and not seen any NMIs, but I've also not being using it for
long periods of time, as that machine has been relegated to being the
beside the couch machine...
My NMI's seem to happen consistently when pulling down menus, often
from something as simple as firefox. The machine is basically idle.
Neither of the fans is even running (and I'm very fan-sensitive) but
the fans do work.
At some point when I'm no longer NMI-shy I'll put up the temperature
monitor and see if it is a temperature shutdown.
darrell
11:26 a.m.
On Fri, Mar 14, 2008 at 3:21 PM, Dave Airlie <airlied(a)redhat.com> wrote:
> Could still be heat related, running the 3D engine may
cause more heat
> to be generated.. I've been running compiz on my Inspiron 6000 for the
> last week and not seen any NMIs, but I've also not being using it for
> long periods of time, as that machine has been relegated to being the
> beside the couch machine...
I turned on compiz this morning. I had two NMI's within an hour. In
both cases the CPU temperature was at 48C, which is the same value as
when the CPU is idle.
With compiz turned off the NMI's have gone away.
darrell
5:27 a.m.
Am Samstag, den 15.03.2008, 09:26 -0700 schrieb darrell pfeifer:
On Fri, Mar 14, 2008 at 3:21 PM, Dave Airlie
<airlied(a)redhat.com> wrote:
>
>
> Could still be heat related, running the 3D engine may cause more heat
> to be generated.. I've been running compiz on my Inspiron 6000 for the
> last week and not seen any NMIs, but I've also not being using it for
> long periods of time, as that machine has been relegated to being the
> beside the couch machine...
>
I turned on compiz this morning. I had two NMI's within an hour. In
both cases the CPU temperature was at 48C, which is the same value as
when the CPU is idle.
With compiz turned off the NMI's have gone away.
darrell
Sounds like a graphic driver error. What are you using?
9:57 a.m.
2008/3/22 Christoph Höger <choeger(a)cs.tu-berlin.de>:
Am Samstag, den 15.03.2008, 09:26 -0700 schrieb darrell pfeifer:
> On Fri, Mar 14, 2008 at 3:21 PM, Dave Airlie <airlied(a)redhat.com> wrote:
> >
>
> >
> > Could still be heat related, running the 3D engine may cause more heat
> > to be generated.. I've been running compiz on my Inspiron 6000 for the
> > last week and not seen any NMIs, but I've also not being using it for
> > long periods of time, as that machine has been relegated to being the
> > beside the couch machine...
> >
>
> I turned on compiz this morning. I had two NMI's within an hour. In
> both cases the CPU temperature was at 48C, which is the same value as
> when the CPU is idle.
>
> With compiz turned off the NMI's have gone away.
>
> darrell
>
Sounds like a graphic driver error. What are you using?
--
It is a Radeon R300 card. It seems to be the most cranky of all the
Radeons. The general sequence of events has been that the card
1) Didn't work with compiz for quite a while when other cards did.
2) Worked flawlessly for quite a few months
3) Turned off compiz when I started getting NMI's for about a month
4) Tried again and compiz worked flawlessly for about 6 months
5) In the very latest incarnation of X (just for the last few weeks)
the problem is back.
There was another thread a few days ago about people with other
drivers/cards experiencing a similar set of symptoms.
darrell
1:18 p.m.
Am Samstag, den 22.03.2008, 07:57 -0700 schrieb darrell pfeifer:
2008/3/22 Christoph Höger <choeger(a)cs.tu-berlin.de>:
>
> Am Samstag, den 15.03.2008, 09:26 -0700 schrieb darrell pfeifer:
>
>
> > On Fri, Mar 14, 2008 at 3:21 PM, Dave Airlie <airlied(a)redhat.com> wrote:
> > >
> >
> > >
> > > Could still be heat related, running the 3D engine may cause more heat
> > > to be generated.. I've been running compiz on my Inspiron 6000 for
the
> > > last week and not seen any NMIs, but I've also not being using it
for
> > > long periods of time, as that machine has been relegated to being the
> > > beside the couch machine...
> > >
> >
> > I turned on compiz this morning. I had two NMI's within an hour. In
> > both cases the CPU temperature was at 48C, which is the same value as
> > when the CPU is idle.
> >
> > With compiz turned off the NMI's have gone away.
> >
> > darrell
> >
>
> Sounds like a graphic driver error. What are you using?
>
> --
It is a Radeon R300 card. It seems to be the most cranky of all the
Radeons. The general sequence of events has been that the card
1) Didn't work with compiz for quite a while when other cards did.
2) Worked flawlessly for quite a few months
3) Turned off compiz when I started getting NMI's for about a month
4) Tried again and compiz worked flawlessly for about 6 months
5) In the very latest incarnation of X (just for the last few weeks)
the problem is back.
There was another thread a few days ago about people with other
drivers/cards experiencing a similar set of symptoms.
darrell
Guess what I've seen on my X1400 today!
5878
days inactive
5890
days old
21 comments
9 participants
participants (9)
-
"Jóhann B. Guðmundsson" -
Alan Cox -
Christoph Höger -
darrell pfeifer -
David Airlie -
David Mansfield -
drago01 -
Lubomir Kundrak -
Ralf Ertzinger