devfs
[Top] [All Lists]

Re: Kernel-oops with devfsd on 2.4.17-SMP

To: Raoul Borenius <borenius@xxxxxxxxxx>
Subject: Re: Kernel-oops with devfsd on 2.4.17-SMP
From: Richard Gooch <rgooch@xxxxxxxxxxxxxxx>
Date: Sat, 12 Jan 2002 12:03:21 -0700
Cc: devfs@xxxxxxxxxxx
In-reply-to: <20020111081407.GA1040@bunny.shuttle.de>
References: <20020107093548.GA763@bunny.shuttle.de> <200201090606.g0966HZ29892@vindaloo.ras.ucalgary.ca> <20020109105953.GA1565@bunny.shuttle.de> <200201101743.g0AHh2025828@vindaloo.ras.ucalgary.ca> <20020111081407.GA1040@bunny.shuttle.de>
Sender: owner-devfs@xxxxxxxxxxx
Raoul Borenius writes:
> Hi Richard,
> 
> On Thu, Jan 10, 2002 at 10:43:02AM -0700, Richard Gooch wrote:
> >   Hi, Raoul. Another question: when you had the Oops, what kernel
> > patches did you have? In particular, did you have the preempt patch?
> 
> I use the sources from Debian/sid (kernel-source-2.4.17-1). Their
> ChangeLog sais
> 
> kernel-source-2.4.17 (2.4.17-1) unstable; urgency=low
> 
>   * New upstream release (closes: #122168, #123471).
>   * Only set startup to 0 for 21143 (rev 65) in tulip.
>   * Don't clear BMCR_FULLDPLX bit in tulip_find_mii as it breaks some cards
>     (closes: #100624).
>   * Fixed atyfb compilation problem (Tobias Ringstrom).
>   * Removed obsolete vfat patch.
>   * Fixed double cache allocation in mount_devfs_fs.
> 
>  -- Herbert Xu <herbert@xxxxxxxxxx>  Sat, 22 Dec 2001 13:41:46 +1100
> 
> Would it be better to use a tarball from kernel.org for debugging?

Yes! It means I have the same kernel that you do, so I can trace every
code path as the need arises. I don't and won't use any kernel other
than official kernels/pre-patches from kernel.org.

In any case, you can hold off on sending more debugging information
for the moment, as I think I know what the problem is (from someone
else's bug report that was similar). I'm working on a 100% correct
solution (I made a half-baked solution late at night that fixed the
problem (and created other problems)). It's a little nasty, this one.

                                Regards,

                                        Richard....
Permanent: rgooch@xxxxxxxxxxxxx
Current:   rgooch@xxxxxxxxxxxxxxx

<Prev in Thread] Current Thread [Next in Thread>