Messages in this thread | | | Date | Fri, 7 Jul 2006 10:02:47 -0700 | From | "Bret Towe" <> | Subject | Re: 2.6.18-rc1 bttv modprobe null pointer dereference |
| |
On 7/6/06, Andrew Morton <akpm@osdl.org> wrote: > On Thu, 6 Jul 2006 22:19:09 -0700 > "Bret Towe" <magnade@gmail.com> wrote: > > > > > Code: 4c 8b bf 48 01 00 00 48 8b bf c0 00 00 00 8b 5e 10 48 81 c7 > > > > RIP [<ffffffff802f1f9b>] sysfs_add_file+0x2b/0xb0 > > > > RSP <ffff81002ac71c28> > > > > CR2: 0000000000000149 > > > > > > There don't seem to have been significant changes in bttv-driver.c for some > > > time, and we're seeing a few reports like this. I'm suspecting that either > > > a sysfs/driver-core change was wrong, or previously wrong driver behaviour > > > is now causing oopses. > > > > > > And Mauro is offline until July 12. > > > > > > Can you send the .config please? > > > > of course > > I spent ten minutes and got lost. I suspect videodev's class_device > handling is wrong, but I fail to spot it. > > This might tell us something.
i dont see any new error messages in dmesg looking at the trace it looks like its dieing before it gets to where this patch would be used? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |