BTTV.c - who maintains it ? (fwd)

2000-09-24 Thread Oren Held

Hello!

Do you have an idea who maintains the bttv driver (or: who changed it in
2.2.18pre) ?
It has a bug, and I donno who to tell about it to.

(MAINTAINERS file has nothing about bttv, just mentions that Alan
maintains the video4linux)

Thanks,
Oren.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/



[BUG?] test11 - oops on loading some modules

2000-11-25 Thread Oren Held

Hello !

I patched my test10 directly to test11 (I didn't use the PREs, so I
can't
say which exact version caused my problem, though if it's
important I can check that). Anyway, after I saw the problem, I
downloaded the whole kernel tree to see if it's not just some patching
problem, but it still happens:

Some of the modules I load (bttv.o , eepro.o , ide-scsi.o), return a
kernel oops, and since then I see them in lsmod stuck in that position:
bttv   55460   1  (initializing)

It seems to me like a problem with modules loading (some of these
modules weren't changed since test10)..
Here's an example of the oops that bttv.o returns:


bttv0: model: BT848A(Fly Video II) [insmod option]
Unable to handle kernel paging request at virtual address 0001
printing eip:
c8852050
*pde = 
Oops: 0002
CPU:0
EIP:0010:[]
EFLAGS: 00010202
eax: 0001   ebx: c8868748   ecx: fffb   edx: c886b110
esi: c88683bc   edi: c8868660   ebp: c8868748   esp: c7455e88
ds: 0018   es: 0018   ss: 0018
Process insmod (pid: 403, stackpage=c7455000)
Stack: c8858169 c8868660 c8868748 c88683bc c8868666 c8868660 c885c2b7
c8868660
   c8868500 0001 c8868500 0001 c8868665 c88648e5 
0282
   c8868500 c887d000 d8a4 c8861e5b c8868500  c8868500
c12ed400
Call Trace: [] [] [] []
[] [] []
[] [] [] [] []
[] [] []
[] [] [] [] []
[] [] []
[] [] [] [] []
[] [] []
[]
Code: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f0 ff 09 0f



Bye,
Oren.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/