Re: Panic during boot under current

[Paul Richards]

Brian Somers wrote:
> 
> > In article <[EMAIL PROTECTED]>, Archie Cobbs
> > <[EMAIL PROTECTED]> writes
> > >Brian Somers writes:
> > >> Also (Mark sits beside me at work), is there anyone else out there
> > >> that actually runs FreeBSD-current under VMWare (irrespective of the
> > >> host OS) ?
> >
> > This problem has now been traced down to a bug in the lnc driver, where
> > multiple instances are installed.
> >
> > This surfaced as a result of changes made on 16th May.
> 
> Specifically, the lnc driver declares NLNC softcs.  Mark has an isa
> style ``device lnc0'' in his config and then uses vmware with two
> configured devices.

Actually, PCI cards allocated their own softc dynamically, only ISA
cards accessed the softc array.
 
> config  produces lnc.h which contains ``#define NLNC 1'' and
> if_lnc_pci.c dives in and starts writing to the second softc.
> 
> I'll look at fixing this at some point if you don't have time Paul :-I

Just got back from the Perl cruise, still catching up with things.
 
> This may have broken because Paul changed the softc decl from static
> to just global (so that the other if_lnc*.c modules can get at it)
> either that or Mark has been ``just lucky'' so far and the lnc driver
> has never worked properly with more than one device.  This would neatly

It was working with more than one device (one PCI and one ISA) the day I
left, which was 19 May. I think the changes to the PCI and ISA
compatibility code modified something relating to unit number allocation
that caused the ISA driver to get a unit number > NLNC whereas before
the ISA instances would come first and the PCI instances would get unit
numbers after the ISA cards, since the PCI part of the driver creates
softc structures dynamically that worked fine.

Paul.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Panic during boot under current

[Brian Somers]

> In article <[EMAIL PROTECTED]>, Archie Cobbs
> <[EMAIL PROTECTED]> writes
> >Brian Somers writes:
> >> Also (Mark sits beside me at work), is there anyone else out there 
> >> that actually runs FreeBSD-current under VMWare (irrespective of the 
> >> host OS) ?
> 
> This problem has now been traced down to a bug in the lnc driver, where
> multiple instances are installed.
> 
> This surfaced as a result of changes made on 16th May.

Specifically, the lnc driver declares NLNC softcs.  Mark has an isa 
style ``device lnc0'' in his config and then uses vmware with two 
configured devices.

config  produces lnc.h which contains ``#define NLNC 1'' and 
if_lnc_pci.c dives in and starts writing to the second softc.

I'll look at fixing this at some point if you don't have time Paul :-I

This may have broken because Paul changed the softc decl from static 
to just global (so that the other if_lnc*.c modules can get at it) 
either that or Mark has been ``just lucky'' so far and the lnc driver 
has never worked properly with more than one device.  This would neatly 
explain why he's seen funny errors in the past - one of them was a 
message to you Garrett saying that your npx.c modification to do no 
more than output a boot-time diagnostic seemed to screw up his 
kernel !!!

> -- 
> Mark Knight   PGP Public Key: finger [EMAIL PROTECTED]

-- 
Brian <[EMAIL PROTECTED]>
     
Don't _EVER_ lose your sense of humour !




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Panic during boot under current

[Mark Knight]

In article <[EMAIL PROTECTED]>, Archie Cobbs
<[EMAIL PROTECTED]> writes
>Brian Somers writes:
>> Also (Mark sits beside me at work), is there anyone else out there 
>> that actually runs FreeBSD-current under VMWare (irrespective of the 
>> host OS) ?

This problem has now been traced down to a bug in the lnc driver, where
multiple instances are installed.

This surfaced as a result of changes made on 16th May.
-- 
Mark Knight   PGP Public Key: finger [EMAIL PROTECTED]


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Panic during boot under current

[Archie Cobbs]

Brian Somers writes:
> Also (Mark sits beside me at work), is there anyone else out there 
> that actually runs FreeBSD-current under VMWare (irrespective of the 
> host OS) ?

Julian has done that I think..

-Archie

___
Archie Cobbs   *   Whistle Communications, Inc.  *   http://www.whistle.com


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Panic during boot under current

[Brian Somers]

> In article <[EMAIL PROTECTED]>, Mark Knight <[EMAIL PROTECTED]>
> writes
> >World and kernel of approx 1100 GMT Sunday 21st May:
> 
> Sorry to reply to my own thread, but new world and kernel/modules of
> 24th May 22:00 GMT still exhibit this behaviour...
> 
> Any ideas appreciated before I start the 'binary chop'.

Also (Mark sits beside me at work), is there anyone else out there 
that actually runs FreeBSD-current under VMWare (irrespective of the 
host OS) ?

> Cheers,
> -- 
> Mark Knight   PGP Public Key: finger [EMAIL PROTECTED]

-- 
Brian <[EMAIL PROTECTED]>
     
Don't _EVER_ lose your sense of humour !




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Panic during boot under current

[Mark Knight]

In article <[EMAIL PROTECTED]>, Mark Knight <[EMAIL PROTECTED]>
writes
>World and kernel of approx 1100 GMT Sunday 21st May:

Sorry to reply to my own thread, but new world and kernel/modules of
24th May 22:00 GMT still exhibit this behaviour...

Any ideas appreciated before I start the 'binary chop'.

Cheers,
-- 
Mark Knight   PGP Public Key: finger [EMAIL PROTECTED]


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message