[Top] [All Lists]

Re: Kernel-oops with devfsd on 2.4.17-SMP

To: Richard Gooch <rgooch@xxxxxxxxxxxxxxx>
Subject: Re: Kernel-oops with devfsd on 2.4.17-SMP
From: Raoul Borenius <borenius@xxxxxxxxxx>
Date: Fri, 11 Jan 2002 09:14:07 +0100
Cc: devfs@xxxxxxxxxxx
In-reply-to: <200201101743.g0AHh2025828@xxxxxxxxxxxxxxxxxxxxxxxx>
References: <20020107093548.GA763@xxxxxxxxxxxxxxxx> <200201090606.g0966HZ29892@xxxxxxxxxxxxxxxxxxxxxxxx> <20020109105953.GA1565@xxxxxxxxxxxxxxxx> <200201101743.g0AHh2025828@xxxxxxxxxxxxxxxxxxxxxxxx>
Sender: owner-devfs@xxxxxxxxxxx
User-agent: Mutt/1.3.25i
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 for debugging?



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