Thomas Meyer wrote:
So i did a "make clean" and a "make" (not a make -j3 as i use to do)
and recompiled 2.6.25-rc3 and now it works again. Case closed under
strange error.
2.6.24 works with the same config, i.e. both drivers are build as
modules.
BTW, of course "make -j..." is supposed to
Thomas Meyer wrote:
So i did a "make clean" and a "make" (not a make
-j3 as i use to do) and recompiled 2.6.25-rc3 and now it works again.
Case closed under strange error.
2.6.24 works with the same config, i.e. both drivers are build as
modules.
What a relief. :-) Thanks for retesting.
--
Stefan Richter schrieb:
My conclusion so far: There is something wrong with your system which
is below/ before the control of the ieee1394 or firewire stack.
Yes. I agree with you. So i did a "make clean" and a "make" (not a make
-j3 as i use to do) and recompiled 2.6.25-rc3 and now it works
Stefan Richter schrieb:
My conclusion so far: There is something wrong with your system which
is below/ before the control of the ieee1394 or firewire stack.
Yes. I agree with you. So i did a make clean and a make (not a make
-j3 as i use to do) and recompiled 2.6.25-rc3 and now it works
Thomas Meyer wrote:
So i did a make clean and a make (not a make
-j3 as i use to do) and recompiled 2.6.25-rc3 and now it works again.
Case closed under strange error.
2.6.24 works with the same config, i.e. both drivers are build as
modules.
What a relief. :-) Thanks for retesting.
--
Thomas Meyer wrote:
So i did a make clean and a make (not a make -j3 as i use to do)
and recompiled 2.6.25-rc3 and now it works again. Case closed under
strange error.
2.6.24 works with the same config, i.e. both drivers are build as
modules.
BTW, of course make -j... is supposed to work. I
Thomas Meyer wrote:
[...]
[ 847.320251] ohci1394: Unknown symbol hpsb_iso_packet_sent
[ 847.320328] ohci1394: Unknown symbol hpsb_packet_sent
[ 847.320406] ohci1394: Unknown symbol dma_region_sync_for_cpu
[ 847.320513] ohci1394: Unknown symbol hpsb_selfid_received
[ 847.320586] ohci1394:
Stefan Richter schrieb:
I wrote:
Thomas Meyer wrote at LKML:
With 2.6.25-rc2 my kernel log consists mainly of:
"ohci1394: fw-host0: Unhandled interrupt(s) 0xfc7cfe0c
There are junk interrupt events sent to ohci1394's IRQ handler.
PS, do you still have the log
Stefan Richter schrieb:
I wrote:
Thomas Meyer wrote at LKML:
With 2.6.25-rc2 my kernel log consists mainly of:
ohci1394: fw-host0: Unhandled interrupt(s) 0xfc7cfe0c
There are junk interrupt events sent to ohci1394's IRQ handler.
PS, do you still have the log
Thomas Meyer wrote:
[...]
[ 847.320251] ohci1394: Unknown symbol hpsb_iso_packet_sent
[ 847.320328] ohci1394: Unknown symbol hpsb_packet_sent
[ 847.320406] ohci1394: Unknown symbol dma_region_sync_for_cpu
[ 847.320513] ohci1394: Unknown symbol hpsb_selfid_received
[ 847.320586] ohci1394:
I wrote:
>>> Thomas Meyer wrote at LKML:
With 2.6.25-rc2 my kernel log consists mainly of:
"ohci1394: fw-host0: Unhandled interrupt(s) 0xfc7cfe0c
>
> There are junk interrupt events sent to ohci1394's IRQ handler.
PS, do you still have the log lines which come from ohci1394's
Thomas Meyer wrote:
> Stefan Richter schrieb:
>> Thomas Meyer wrote at LKML:
>>> With 2.6.25-rc2 my kernel log consists mainly of:
>>>
>>> "ohci1394: fw-host0: Unhandled interrupt(s) 0xfc7cfe0c
There are junk interrupt events sent to ohci1394's IRQ handler.
...
>> Do you have any hardware
Stefan Richter schrieb:
Thomas Meyer wrote at LKML:
Hi.
With 2.6.25-rc2 my kernel log consists mainly of:
"ohci1394: fw-host0: Unhandled interrupt(s) 0xfc7cfe0c
ohci1394: fw-host0: Unrecoverable error!
ohci1394: fw-host0: Async Rsp Tx Context died: ctrl[f0002a00]
cmdptr[f0002a00]
Thomas Meyer wrote at LKML:
> Hi.
>
> With 2.6.25-rc2 my kernel log consists mainly of:
>
> "ohci1394: fw-host0: Unhandled interrupt(s) 0xfc7cfe0c
> ohci1394: fw-host0: Unrecoverable error!
> ohci1394: fw-host0: Async Rsp Tx Context died: ctrl[f0002a00]
> cmdptr[f0002a00]
> ohci1394: fw-host0:
Thomas Meyer wrote at LKML:
Hi.
With 2.6.25-rc2 my kernel log consists mainly of:
ohci1394: fw-host0: Unhandled interrupt(s) 0xfc7cfe0c
ohci1394: fw-host0: Unrecoverable error!
ohci1394: fw-host0: Async Rsp Tx Context died: ctrl[f0002a00]
cmdptr[f0002a00]
ohci1394: fw-host0: Iso Recv 3
Stefan Richter schrieb:
Thomas Meyer wrote at LKML:
Hi.
With 2.6.25-rc2 my kernel log consists mainly of:
ohci1394: fw-host0: Unhandled interrupt(s) 0xfc7cfe0c
ohci1394: fw-host0: Unrecoverable error!
ohci1394: fw-host0: Async Rsp Tx Context died: ctrl[f0002a00]
cmdptr[f0002a00]
ohci1394:
Thomas Meyer wrote:
Stefan Richter schrieb:
Thomas Meyer wrote at LKML:
With 2.6.25-rc2 my kernel log consists mainly of:
ohci1394: fw-host0: Unhandled interrupt(s) 0xfc7cfe0c
There are junk interrupt events sent to ohci1394's IRQ handler.
...
Do you have any hardware attached to the
I wrote:
Thomas Meyer wrote at LKML:
With 2.6.25-rc2 my kernel log consists mainly of:
ohci1394: fw-host0: Unhandled interrupt(s) 0xfc7cfe0c
There are junk interrupt events sent to ohci1394's IRQ handler.
PS, do you still have the log lines which come from ohci1394's
initialization?
--
Hi.
With 2.6.25-rc2 my kernel log consists mainly of:
"ohci1394: fw-host0: Unhandled interrupt(s) 0xfc7cfe0c
ohci1394: fw-host0: Unrecoverable error!
ohci1394: fw-host0: Async Rsp Tx Context died: ctrl[f0002a00]
cmdptr[f0002a00]
ohci1394: fw-host0: Iso Recv 3 Context died: ctrl[d4000d0e]
Hi.
With 2.6.25-rc2 my kernel log consists mainly of:
ohci1394: fw-host0: Unhandled interrupt(s) 0xfc7cfe0c
ohci1394: fw-host0: Unrecoverable error!
ohci1394: fw-host0: Async Rsp Tx Context died: ctrl[f0002a00]
cmdptr[f0002a00]
ohci1394: fw-host0: Iso Recv 3 Context died: ctrl[d4000d0e]
20 matches
Mail list logo
