Re: Panic during boot under current

2000-06-11 Thread 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 kernel 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

2000-06-05 Thread 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

2000-06-05 Thread 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 kernel 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]brian@[uk.]FreeBSD.org
  http://www.Awfulhak.org   brian@[uk.]OpenBSD.org
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

2000-05-25 Thread 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



Re: Panic during boot under current

2000-05-25 Thread 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]brian@[uk.]FreeBSD.org
  http://www.Awfulhak.org   brian@[uk.]OpenBSD.org
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



Panic during boot under current

2000-05-22 Thread Mark Knight

World and kernel of approx 1100 GMT Sunday 21st May:

Console (re-typed):

ad0: 1999MB VMware Virtual IDE Hard Drive [4334/15/63] at ata0-master using UDMA33
ad1: 499MB VMware Virtual IDE Hard Drive [1083/15/63] at ata0-slave using UDMA33
Mounting root from ufs: /dev/ad0s1a

Fatal trap 12: page fault while in kernel mode
fault virtual address   = 0x2a6
fault code  = supervisor read, page not present
instruction pointer = 0x8:0xc017553b
stack pointer   = 0x10:0xc0328f14
frame pointer   = 0x10:0xc0328f30
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1 def32 1, gran 1
processor eflags= interrupt enabled, IOPL = 0
current process = 0 (swapper)
interrupt mask  = none
kernel: type 12 trap, code=0
Stopped at  getdiskbyname+0x9f: pushl   0x20(%eax)
db t
getdiskbyname(c0888c85,c0328f7c,c01751e2,c0888c80,c02a42d0) at getdiskbyname+0x9f
setrootbyname(c0888c80) at setrootbyname+0xb
vfs_mountroot_try(c0313092,c024cedc) at vfs_mountroot_try+0xda
vfs_mountroot(0,326c00,32d000,0,c011b736) at vfs_mountroot+0x5a
mi_startup(c0328fb4,a0202,ffe,32d000,c0158765) at mi_startup+0x70
begin() at begin+0x4b
db

Config:

machine i386
#cpuI386_CPU
#cpuI486_CPU
#cpuI586_CPU
cpu I686_CPU
ident   VMWARE
maxusers32

makeoptions DEBUG=-g#Build kernel with gdb(1) debug symbols

#optionsMATH_EMULATE#Support for x87 emulation
options INET#InterNETworking
#optionsINET6   #IPv6 communications protocols
options FFS #Berkeley Fast Filesystem
options FFS_ROOT#FFS usable as root device [keep this!]
options MFS #Memory Filesystem
options MD_ROOT #MD is a potential root device
options NFS #Network Filesystem
options NFS_ROOT#NFS usable as root device, NFS required
options MSDOSFS #MSDOS Filesystem
options CD9660  #ISO 9660 Filesystem
options CD9660_ROOT #CD-ROM usable as root, CD9660 required
options PROCFS  #Process filesystem
options COMPAT_43   #Compatible with BSD 4.3 [KEEP THIS!]
options SCSI_DELAY=15000#Delay (in ms) before probing SCSI
options UCONSOLE#Allow users to grab the console
options USERCONFIG  #boot -c editor
options VISUAL_USERCONFIG   #visual boot -c editor
options KTRACE  #ktrace(1) support
options SYSVSHM #SYSV-style shared memory
options SYSVMSG #SYSV-style message queues
options SYSVSEM #SYSV-style semaphores
options P1003_1B#Posix P1003_1B real-time extensions
options _KPOSIX_PRIORITY_SCHEDULING
options ICMP_BANDLIM#Rate limit bad replies
options KBD_INSTALL_CDEV# install a CDEV entry in /dev
options DDB

device  isa
#device eisa
device  pci
options COMPAT_OLDISA   # Old ISA driver shims
options COMPAT_OLDPCI   # Old PCI driver shims

# Floppy drives
device  fdc0at isa? port IO_FD1 irq 6 drq 2
device  fd0 at fdc0 drive 0
device  fd1 at fdc0 drive 1

# ATA and ATAPI devices
device  ata0at isa? port IO_WD1 irq 14
device  ata1at isa? port IO_WD2 irq 15
device  ata
device  atadisk # ATA disk drives
device  atapicd # ATAPI CDROM drives
#device atapifd # ATAPI floppy drives
#device atapist # ATAPI tape drives
options ATA_STATIC_ID   #Static device numbering
#optionsATA_ENABLE_ATAPI_DMA#Enable DMA on ATAPI devices

device  atkbdc0 at isa? port IO_KBD
device  atkbd0  at atkbdc? irq 1 flags 0x1
device  psm0at atkbdc? irq 12

device  vga0at isa?

pseudo-device   splash

device  sc0 at isa? flags 0x100

device  npx0at nexus? port IO_NPX irq 13

device  apm0at nexus? flags 0x20 # Advanced Power Management

device  sio0at isa? port IO_COM1 flags 0x10 irq 4
device  sio1at isa? port IO_COM2 irq 3
device  sio2at isa? disable port IO_COM3 irq 5
device  sio3at isa? disable port IO_COM4 irq 9

device  lnc0at isa? port 0x280 irq 10 drq 0

pseudo-device   loop# Network loopback
pseudo-device   ether   # Ethernet support
pseudo-device   sl  1   # Kernel SLIP
pseudo-device   ppp 1   # Kernel PPP
pseudo-device   tun # Packet tunnel.
pseudo-device