| View previous topic :: View next topic |
| Author |
Message |
dice
Guru
Joined: 21 Apr 2002
Posts: 577
|
 Posted: Thu May 26, 2005 10:31 am Post subject: |
 |
|
Running on amd64 with FullRT I've found two bugs in my dmesg output, only one of which might be relevant here.
First off, this may or may not be a problem with the nvidia module itself:
| Code: | nvidia: module license 'NVIDIA' taints kernel.
ACPI: PCI Interrupt Link [APC5] enabled at IRQ 16
ACPI: PCI Interrupt 0000:01:00.0[A] -> Link [APC5] -> GSI 16 (level, low) -> IRQ 209
NVRM: loading NVIDIA Linux x86_64 NVIDIA Kernel Module 1.0-7174 Tue Mar 22 06:45:40 PST 2005
BUG: modprobe/4264, lock held at task exit time!
[ffff81003d4e8388] {(struct semaphore *)(&os_sema->wait)}
.. held by: modprobe: 4264 [ffff81003e471800, 119]
... acquired at: os_alloc_sema+0x38/0x67 [nvidia]
it87: Found IT8712F chip at 0x290, revision 5
agpgart: Found an AGP 3.0 compliant device at 0000:00:00.0. |
I didn't get any errors when loading my other modules.
Secondly there's this:
| Code: | ksoftirqd/0/2: BUG in __up_mutex at kernel/rt.c:1332
Call Trace:<ffffffff801492e8>{__up_mutex+616} <ffffffff8014a631>{rt_up+209}
<ffffffff88280811>{:nvidia:os_release_sema+90} <ffffffff88074eca>{:nvidia:_nv001648rm+12}
<ffffffff8807867c>{:nvidia:_nv001198rm+164} <ffffffff8807ba4b>{:nvidia:rm_isr_bh+17}
<ffffffff8827cdc4>{:nvidia:nv_kern_isr_bh+202} <ffffffff80135bf4>{tasklet_action+68}
<ffffffff80135807>{___do_softirq+87} <ffffffff80135d10>{ksoftirqd+0}
<ffffffff8013595b>{_do_softirq+27} <ffffffff80135d10>{ksoftirqd+0}
<ffffffff80135dda>{ksoftirqd+202} <ffffffff80135d10>{ksoftirqd+0}
<ffffffff80145f9d>{kthread+205} <ffffffff8010e05b>{child_rip+8}
<ffffffff80145ed0>{kthread+0} <ffffffff8010e053>{child_rip+0} |
Which, now that I look more closely, also seems to be related to the nvidia module. 3d's working fine though, I haven't played any doom3 but glxgears loads and was doing some reasonable framerate when I checked it. |
|
| Back to top |
|
 |
fallow
Bodhisattva
Joined: 08 Jan 2004
Posts: 2208
Location: Poland
|
| Posted: Thu May 26, 2005 10:52 am Post subject: |
|
|
hmm ok , this release also cannot be stable because of RTP bugs.
but WE OFFICIALY SUPPORTING only x86 , not x86_64
from this point of view, there is no errors on x86.
however , I feel its not enough good .
stable is still rc3-love1..
will be rc5-love1 very soon
cheers 
_________________
"Time is a companion that goes with us on a journey. It reminds us to cherish each moment, because it will never come again. What we leave behind is not as important as how we have lived" J-L. Picard  |
|
| Back to top |
|
|
NiLuJe
Guru
Joined: 06 Nov 2004
Posts: 303
Location: Paris, France
|
| Posted: Thu May 26, 2005 12:13 pm Post subject: |
|
|
fallow > It was in fullRT, and it seems related to the nvidia module ... But apart from the warnings in dmesg, it was running fine (Hmm, except the 'silght overhead' of fullrt, ksoftirq process eating 5% cpu time ^^ ).
I'm back in lld, and it runs fine, no more warnings in kernel logs |
|
| Back to top |
|
|
vipernicus
Veteran
Joined: 17 Jan 2005
Posts: 1462
Location: Your College IT Dept.
|
|
| Back to top |
|
|
predatorfreak
l33t
Joined: 13 Jan 2005
Posts: 708
Location: USA, Michigan.
|
| Posted: Thu May 26, 2005 1:38 pm Post subject: |
|
|
| vipernicus wrote: | | Could RTP work with Staircase? |
People have tried, nothing has worked so far.
_________________
System: predatorbox
Distro: Arch Linux x86_64
Current projects: blackhole, convmedia and anything else I cook up. |
|
| Back to top |
|
|
vipernicus
Veteran
Joined: 17 Jan 2005
Posts: 1462
Location: Your College IT Dept.
|
| Posted: Thu May 26, 2005 2:03 pm Post subject: |
|
|
| predatorfreak wrote: | | vipernicus wrote: | | Could RTP work with Staircase? |
People have tried, nothing has worked so far. |
Do you have any sources with results? I'm curious.
_________________
Viper-Sources Maintainer || nesl247 Projects || vipernicus.org blog |
|
| Back to top |
|
|
fallow
Bodhisattva
Joined: 08 Jan 2004
Posts: 2208
Location: Poland
|
| Posted: Thu May 26, 2005 3:16 pm Post subject: |
|
|
results of logo competition for now :
| Code: |
blutkind-logo-1.png 8.82% [3 votes]
donis-love-logo-x.png 8.82% [3 votes]
drwoland-logo-1.jpg 2.94% [1 vote]
fallow-logo-1.png 32.35% [11 votes]
logo-fallow-deviant1.png 14.71% [5 votes]
fallow-logo-2.png 0% [No votes]
sith_happens-logo1.png 11.76% [4 votes]
sith_happens-logo2.png 20.59% [7 votes]
|
so for next release I will make a choice beetwen mine first logo , and sith_happens second..
voting will be active still
_________________
"Time is a companion that goes with us on a journey. It reminds us to cherish each moment, because it will never come again. What we leave behind is not as important as how we have lived" J-L. Picard |
|
| Back to top |
|
|
dice
Guru
Joined: 21 Apr 2002
Posts: 577
|
| Posted: Thu May 26, 2005 9:30 pm Post subject: |
|
|
| fallow wrote: | but WE OFFICIALY SUPPORTING only x86 , not x86_64
from this point of view, there is no errors on x86.
however , I feel its not enough good . |
What more would you need in order to officialy support x86_64? I can do testing and search LKML for patches then apply and test them. I know C but I've not worked with the kernel and I'm not very familliar with its structure. |
|
| Back to top |
|
|
fallow
Bodhisattva
Joined: 08 Jan 2004
Posts: 2208
Location: Poland
|
| Posted: Fri May 27, 2005 5:50 am Post subject: |
|
|
| dice wrote: | | fallow wrote: | but WE OFFICIALY SUPPORTING only x86 , not x86_64
from this point of view, there is no errors on x86.
however , I feel its not enough good . |
What more would you need in order to officialy support x86_64? I can do testing and search LKML for patches then apply and test them. I know C but I've not worked with the kernel and I'm not very familliar with its structure. |
Needs :
1) X86_64 box for testing [ I have x86 ]
2) X86_64 co-maintainer
one of this 2 things.
for patchseting base of C is enough.
I havent just possibilities to test X86_64 modyfications.
You can try to fix existing x86_64 error reported in rc5-love1 thread if You have intend for the beginning
cheers
_________________
"Time is a companion that goes with us on a journey. It reminds us to cherish each moment, because it will never come again. What we leave behind is not as important as how we have lived" J-L. Picard |
|
| Back to top |
|
|
|
Unsupported Software
