Bjorn Helgaas napisaÅ(a):
>>Version from syskonnect site require only changing usage of
>>pci_dev->slot_name to pci_name(pci_dev) in skge.c and skethtool.c. After
>>that everything should work fine. So I think there is no need to post my
>>path here but if you really whant I may do this. Whole
Bjorn Helgaas napisa(a):
Version from syskonnect site require only changing usage of
pci_dev-slot_name to pci_name(pci_dev) in skge.c and skethtool.c. After
that everything should work fine. So I think there is no need to post my
path here but if you really whant I may do this. Whole path agains
Bjorn Helgaas wrote:
> On Fri, 2005-04-01 at 21:23 +0200, Jacek Luczak wrote:
>
>>Michael Thonke napisał(a):
>>
>>>Hello Jacek,
>>>
>>>I finially got it working :-) my PCI-Express devices working now...
>>>I grabbed the last bk-snapshot fro
Bjorn Helgaas wrote:
On Fri, 2005-04-01 at 21:23 +0200, Jacek Luczak wrote:
Michael Thonke napisa(a):
Hello Jacek,
I finially got it working :-) my PCI-Express devices working now...
I grabbed the last bk-snapshot from kernel.org 2.6.12-rc1-bk3 and et volia
everything except the Marvell Yokon
Natanael Copa napisał(a):
> On Thu, 2005-03-31 at 12:11 -0500, Lee Revell wrote:
>
>
>>Didn't you ever look up what a ulimit is?
>
>
> ofcourse i did. I just think that ulimit (or other userspace tools)
> should be used to *raise* the limit if you need more. Not the reverse.
>
>
>>If you
Natanael Copa napisa(a):
On Thu, 2005-03-31 at 12:11 -0500, Lee Revell wrote:
Didn't you ever look up what a ulimit is?
ofcourse i did. I just think that ulimit (or other userspace tools)
should be used to *raise* the limit if you need more. Not the reverse.
If you consider your
Jacek Luczak napisaÅ(a):
Matan Peled napisaÅ(a):
Jacek Luczak wrote:
Hi
Early morning i made a 2.6.12-rc1 with RT-V0.7.43-05 and this is what I
sow in dmesg after 6 hours of computers work:
Hmm... A lot of that seems to involve ndiswrapper. Is there any way
you could
reproduce this without
Hi
Early morning i made a 2.6.12-rc1 with RT-V0.7.43-05 and this is what I
sow in dmesg after 6 hours of computers work:
BUG: scheduling while atomic: events/0/0x0001/8
caller is schedule+0x40/0x140
[] dump_stack+0x23/0x30 (20)
[] __schedule+0xe53/0xeb0 (124)
[] schedule+0x40/0x140 (36)
Hi
Early morning i made a 2.6.12-rc1 with RT-V0.7.43-05 and this is what I
sow in dmesg after 6 hours of computers work:
BUG: scheduling while atomic: events/0/0x0001/8
caller is schedule+0x40/0x140
[c0104333] dump_stack+0x23/0x30 (20)
[c032ba03] __schedule+0xe53/0xeb0 (124)
[c032baa0]
Jacek Luczak napisa(a):
Matan Peled napisa(a):
Jacek Luczak wrote:
Hi
Early morning i made a 2.6.12-rc1 with RT-V0.7.43-05 and this is what I
sow in dmesg after 6 hours of computers work:
SNIP!
Hmm... A lot of that seems to involve ndiswrapper. Is there any way
you could
reproduce this without
Michael Thonke napisaÅ(a):
Hello Jacek,
I finially got it working :-) my PCI-Express devices working now...
I grabbed the last bk-snapshot from kernel.org 2.6.12-rc1-bk3 and et volia
everything except the Marvell Yokon PCI-E device working.
I hope Andrew will look into the mm-line to find the bug?
hello Michael :)
This message:
ACPI: No ACPI bus support for 00:00
means that acpi_get_bus_type() is unable to determinate
bus type! Mayby someone forgot about PCI-E?
Regards
Jacek
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL
Michael Thonke napisaÅ(a):
Hello,
since the first version of 2.6.12-rc1 and mm[1-4] kernel I can't use any
of my PCI-Express devices that worked with all 2.6.11.[1-6] kernels.
It's a real odd right now.
I have 25 computers with an Intel 925XE Chipset based motherboards and
Intel 6xx CPU on it.
Michael Thonke napisa(a):
Hello,
since the first version of 2.6.12-rc1 and mm[1-4] kernel I can't use any
of my PCI-Express devices that worked with all 2.6.11.[1-6] kernels.
It's a real odd right now.
I have 25 computers with an Intel 925XE Chipset based motherboards and
Intel 6xx CPU on it.
hello Michael :)
This message:
ACPI: No ACPI bus support for 00:00
means that acpi_get_bus_type() is unable to determinate
bus type! Mayby someone forgot about PCI-E?
Regards
Jacek
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL
Michael Thonke napisa(a):
Hello Jacek,
I finially got it working :-) my PCI-Express devices working now...
I grabbed the last bk-snapshot from kernel.org 2.6.12-rc1-bk3 and et volia
everything except the Marvell Yokon PCI-E device working.
I hope Andrew will look into the mm-line to find the bug?
16 matches
Mail list logo
