Re: kern/44144 (ifconfig causes assertion failure in vfs_lookup.c)

[David Holland <dholland-bugs%netbsd.org@localhost>]

The following reply was made to PR kern/44144; it has been noted by GNATS.

From: David Holland <dholland-bugs%netbsd.org@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: 
Subject: Re: kern/44144 (ifconfig causes assertion failure in vfs_lookup.c)
Date: Fri, 26 Nov 2010 21:50:24 +0000

 On Fri, Nov 26, 2010 at 03:10:07PM +0000, Alan Barrett wrote:
  >  On Wed, 24 Nov 2010, dholland%NetBSD.org@localhost wrote:
  >  > please try firmload.c 1.16
  >  
  >  Now I get "ERROR: wpi0: could not read firmware file" on the console
  >  (printed by line 1150 of if_wpi.c), and the system enters ddb.
  >
  >  I have /usr/pkg/libdata/if_wpi/iwlwifi-3945.ucode but, because
  >  this was a new kernel with an old userland, I do not have
  >  /libdata/firmware/if_wpi/iwlwifi-3945.ucode.
 
 That appears to be progress, anyway...
 
  >  Instead of entering ddb, I think the system should return the error in a
  >  way that allows userland to print a sensible message.
 
 Certainly. Where's it entering ddb? The error return chain seems to be
 correct up through wpi_init returning failure, none of the direct
 calls from inside if_wpi check that return at all (which is perhaps
 broken but not likely to land in ddb) and above that it's some
 indirect call through ->if_init from the network stack, and there are
 quite a few possible choices.
 
 -- 
 David A. Holland
 dholland%netbsd.org@localhost