Messages in this thread | | | From | Tim Connors <> | Subject | Re: 2.5.67: ppa driver & preempt == oops | Date | Mon, 14 Apr 2003 14:17:46 +1000 |
| |
In linux.kernel, you wrote: > Andrew Morton wrote: >> Gert Vervoort <gert.vervoort@hccnet.nl> wrote: >> >>>ppa: Version 2.07 (for Linux 2.4.x) >>>ppa: Found device at ID 6, Attempting to use EPP 16 bit >>>ppa: Communication established with ID 6 using EPP 16 bit >>>scsi0 : Iomega VPI0 (ppa) interface >>>bad: scheduling while atomic! >> >> >> This patch should make the warnings go away. >> >> I've been sitting on it for a while, waiting for someone to tell me if the >> ppa driver actually works. Perhaps that person is you? > > I've responded to your questions more than once but evidently you > haven't seen or been able to parse my responses. > > To recap: I see a non-fatal kernel-oops and modprobe segfaults after > successfully loading the ppa module. Once the ppa module is loaded the > ppa driver actually does work with 2.5.x for at least x>50 (I haven't > tried x<50). > > I am using preemptable kernel and devfs and I do NOT see any of the > warnings that Geert is seeing. The only problems I see with Linus's > 2.5.x kernels is the segfault by modprobe, not with the function of > ppa itself.
I'm using both devfs and preempt. The first time I booted (I think it was actually 2.5.66), I tried to mount /zip, and it hung, with 100% cpu usage after that (I can't rememebr what process), and several traces in syslog (lsmod showed the modules as loaded, I think one or two of them "unsafe"). Next time I booted (2.5.67+V4L patches), I modprobed ppa manually, this time, it segfaulted (with traces in syslog), but the modules were listed in lsmod correcly. I then mounted, and it was fine.
Sorry I don't have the logs with me, one of the drawbacks of being too cheap to afford a home innernet connection :(
-- TimC -- http://astronomy.swin.edu.au/staff/tconnors/
Press any key to continue, any other key to abort -- thrillbert's code - 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/
| |