Diskless boot problem

2005-05-19 Thread Sławek Żak
Hi,

I have a problem with booting Dell 2850 over network. The machine
reads kernel over net, boots upto mounting / from NFS and then
crashes.

Tcpdump output:

12:15:58.919683 arp who-has 10.158.190.73 tell 10.158.190.74
12:15:58.919702 arp reply 10.158.190.73 is-at 00:11:43:d3:6e:e1
12:15:58.920058 IP 10.158.190.74.475209176 > 10.158.190.73.2049: 92
getattr [|nfs]
12:15:58.920134 IP 10.158.190.73.2049 > 10.158.190.74.475209176: reply
ok 28 getattr ERROR: Stale NFS file handle
12:15:58.920432 arp who-has 10.158.190.73 tell 10.158.190.74
12:15:58.920442 arp reply 10.158.190.73 is-at 00:11:43:d3:6e:e1
12:15:58.920681 IP 10.158.190.74.475209177 > 10.158.190.73.2049: 100
lookup [|nfs]
12:15:58.920707 IP 10.158.190.73.2049 > 10.158.190.74.475209177: reply
ok 28 lookup ERROR: Stale NFS file handle
12:15:58.920932 IP 10.158.190.74.475209178 > 10.158.190.73.2049: 100
lookup [|nfs]
12:15:58.920963 IP 10.158.190.73.2049 > 10.158.190.74.475209178: reply
ok 28 lookup ERROR: Stale NFS file handle
12:15:58.952180 IP 10.158.190.74.475209179 > 10.158.190.73.2049: 100
lookup [|nfs]
12:15:58.952277 IP 10.158.190.73.2049 > 10.158.190.74.475209179: reply
ok 28 lookup ERROR: Stale NFS file handle
12:15:58.984785 IP 10.158.190.74.475209180 > 10.158.190.73.2049: 100
lookup [|nfs]
12:15:58.984866 IP 10.158.190.73.2049 > 10.158.190.74.475209180: reply
ok 28 lookup ERROR: Stale NFS file handle
12:15:59.020500 IP 10.158.190.74.475209181 > 10.158.190.73.2049: 104
lookup [|nfs]
12:15:59.020573 IP 10.158.190.73.2049 > 10.158.190.74.475209181: reply
ok 28 lookup ERROR: Stale NFS file handle
12:15:59.054130 IP 10.158.190.74.475209182 > 10.158.190.73.2049: 104
lookup [|nfs]
12:15:59.054224 IP 10.158.190.73.2049 > 10.158.190.74.475209182: reply
ok 28 lookup ERROR: Stale NFS file handle

I wonder where the `Stale NFS handle'  error comes from, as the client
doesn't seem to have mounted the filesystem over NFS from what I can
see. On the console of the diskless I have this:

NFS ROOT: 10.158.190.73:/var/www/FreeBSD-5.4-x86-PXE
em0: Link is up 100 Mbps Half Duplex
exec /sbin/init: error 70
exec /sbin/oinit: error 70
exec /sbin/init.bak: error 70
exec /rescue/init: error 70
exec /stand/sysinstall: error 70
init: not found in path
/sbin/init:/sbin/oinit:/sbin/init.bak:/rescue/init:/stand/sysinstall
panic: no init
Uptime: 55s
Cannot dump. No dump device defined.
Automatic reboot in 15 seconds - press a key on the console to abort

The speed for em0 is obviously wrong. Setting on the switch is 100
full-duplex. Our network wizards can f***kup autonegotiation on Cisco
Catalyst, so it must stay that way. Intel em-s tend to hang for a
couple of seconds before getting on the net so it might be the
problem. On the other hand kernel loads just fine over TFTP.

Any thoughts?

Thanks, /S
-- 
Sławek Żak / UNIX Systems Administrator
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: 5.4-RC2 freezing - ATA related?

2005-05-19 Thread Doug White
On Wed, 18 May 2005, Jamie Heckford wrote:

> Hi Peter,
>
> On Thu, May 19, 2005 at 05:53:12AM +1000, Peter Jeremy wrote:
> > On Wed, 2005-May-18 16:03:16 +0100, Jamie Heckford wrote:
> > >Managed to get a dump on our system for a similar prob we are getting:
> >
> > That traceback looks like a panic, not a deadlock.  What was the panic
> > message?
>
> Only have remote access to the box im afraid, is there anyway I can obtain
> the panic message?

"print msgbuf" should do it

>
> >
> > >#2  0xc0513474 in panic (fmt=0xc06c3da5 "%s") at 
> > >/usr/src/sys/kern/kern_shutdown.c:566
> > ...
> > >#7  0xc0510018 in crcopy () at /usr/src/sys/kern/kern_prot.c:1810
> > >#8  0xc0598c77 in in_pcbdetach (inp=0xc0743a40) at 
> > >/usr/src/sys/netinet/in_pcb.c:720
> > >#9  0xc05b21a6 in tcp_close (tp=0x0) at /usr/src/sys/netinet/tcp_subr.c:783
> >
> > There's something wrong here:  If tcp_close() is passed NULL it will panic
> > at this point when it tries to dereference tp.
>
> Starting to stretch my knowledge a bit now ;)
>
> If I can provide you with further debug output would you be able to give me 
> some
> pointers?
>
> Thanks for your help
>
>

-- 
Doug White|  FreeBSD: The Power to Serve
[EMAIL PROTECTED]  |  www.FreeBSD.org
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


page fault in ugenpoll()

2005-05-19 Thread Dirk Gouders
Hello,

on a machine

FreeBSD karga.hank.home 4.11-STABLE FreeBSD 4.11-STABLE #2: Thu May 19 12:32:50 
CEST 2005 [EMAIL PROTECTED]:/usr/src/sys/compile/KARGA  i386

I am playing with a Cryptoflex e-gate USB token and get kernel
panics when invoking a program openct-control to access it:

Fatal trap 12: page fault while in kernel mode
fault virtual address   = 0x3
fault code  = supervisor read, page not present
instruction pointer = 0x8:0xc027177b
stack pointer   = 0x10:0xccde7d40
frame pointer   = 0x10:0xccde7d50
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 173 (ifdhandler)
interrupt mask  = bio 
trap number = 12
panic: page fault

The IP points to the following line in the function ugenpoll (line
1445 in ugen.c):

switch (sce->edesc->bmAttributes & UE_XFERTYPE)

Examining sce with gdb gives:

(kgdb) print sce
$1 = (struct ugen_endpoint *) 0x68c060
(kgdb) print sce->edesc
Cannot access memory at address 0x68c064.
(kgdb) 

The software that I am trying to use might be erroneous, but I am
wondering that it causes kernel panics by accessing /dev/ugen0.

Dirk
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: page fault in ugenpoll()

2005-05-19 Thread Dirk GOUDERS
Hello,

just for completeness, I want to provide a simple program that causes
a kernel panic when invoked with the argument /dev/ugen0:

#include 
#include 
#include 
#include 
#include 
#include 

int main(int argc, char *argv[])
{
int fd;
int nfd;
char *path = argv[1];
struct pollfd pfd[1];

fd = open(path, O_RDWR);
if ( fd < 0 ) {
fprintf(stderr, "%s: %s\n", path, strerror(errno));
exit(1);
}
pfd[0].fd = fd;
pfd[0].events = POLLHUP;
pfd[0].revents = 0;
nfd = poll(pfd, 1, 10);
if ( nfd < 0 ) {
fprintf(stderr, "poll(2): %s\n", strerror(errno));
exit(1);
}
printf("nfd = %d\n", nfd);
close(fd);
exit(0);
}

 > Hello,
 > 
 > on a machine
 > 
 > FreeBSD karga.hank.home 4.11-STABLE FreeBSD 4.11-STABLE #2: Thu May 19 12:32
 > :50 CEST 2005 [EMAIL PROTECTED]:/usr/src/sys/compile/KARGA  i386
 > 
 > I am playing with a Cryptoflex e-gate USB token and get kernel
 > panics when invoking a program openct-control to access it:
 > 
 > Fatal trap 12: page fault while in kernel mode
 > fault virtual address   = 0x3
 > fault code  = supervisor read, page not present
 > instruction pointer = 0x8:0xc027177b
 > stack pointer   = 0x10:0xccde7d40
 > frame pointer   = 0x10:0xccde7d50
 > code segment= base 0x0, limit 0xf, type 0x1b
 > = DPL 0, pres 1, def32 1, gran 1
 > processor eflags= interrupt enabled, resume, IOPL = 0
 > current process = 173 (ifdhandler)
 > interrupt mask  = bio 
 > trap number = 12
 > panic: page fault
 > 
 > The IP points to the following line in the function ugenpoll (line
 > 1445 in ugen.c):
 > 
 > switch (sce->edesc->bmAttributes & UE_XFERTYPE)
 > 
 > Examining sce with gdb gives:

 > (kgdb) print sce
 > $1 = (struct ugen_endpoint *) 0x68c060
 > (kgdb) print sce->edesc
 > Cannot access memory at address 0x68c064.
 > (kgdb) 
 > 
 > The software that I am trying to use might be erroneous, but I am
 > wondering that it causes kernel panics by accessing /dev/ugen0.
 > 
 > Dirk
 > ___
 > freebsd-hackers@freebsd.org mailing list
 > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
 > To unsubscribe, send any mail to "[EMAIL PROTECTED]"
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


PCI Device Driver

2005-05-19 Thread Luís Vitório Cargnini
Hi i need to write a device driver for a PCI board. I read the
developers book see the exemples and i'm starting to write the device
driver. I'm writeing a device driver for a board with SAA713X TV chipset
from Phillips. I did theskeleton example, but whe i catch the example of
PCI driver from developers book and tried to compilate i receive the
following:
(forgive me for the long paste, but i need some answers and i need to
give the details)


PASTE of ERORS:
@/sys/bus.h:455:23: device_if.h: No such file or directory
@/sys/bus.h:456:20: bus_if.h: No such file or directory
In file included from saa713x.c:23:
@/dev/pci/pcivar.h:170:20: pci_if.h: No such file or directory
In file included from saa713x.c:23:
@/dev/pci/pcivar.h: In function `pci_get_subvendor':
@/dev/pci/pcivar.h:203: warning: implicit declaration of function
`BUS_READ_IVAR'
@/dev/pci/pcivar.h:203: warning: nested extern declaration of
`BUS_READ_IVAR'
@/dev/pci/pcivar.h: In function `pci_set_subvendor':
@/dev/pci/pcivar.h:203: warning: implicit declaration of function
`BUS_WRITE_IVAR'
@/dev/pci/pcivar.h:203: warning: nested extern declaration of
`BUS_WRITE_IVAR'
@/dev/pci/pcivar.h: In function `pci_get_subdevice':
@/dev/pci/pcivar.h:204: warning: nested extern declaration of
`BUS_READ_IVAR'
@/dev/pci/pcivar.h:203: warning: redundant redeclaration of
'BUS_READ_IVAR'
@/dev/pci/pcivar.h:203: warning: previous implicit declaration of
'BUS_READ_IVAR' was here
@/dev/pci/pcivar.h: In function `pci_set_subdevice':
@/dev/pci/pcivar.h:204: warning: nested extern declaration of
`BUS_WRITE_IVAR'
@/dev/pci/pcivar.h:203: warning: redundant redeclaration of
'BUS_WRITE_IVAR'
@/dev/pci/pcivar.h:203: warning: previous implicit declaration of
'BUS_WRITE_IVAR' was here
@/dev/pci/pcivar.h: In function `pci_get_vendor':
@/dev/pci/pcivar.h:205: warning: nested extern declaration of
`BUS_READ_IVAR'
@/dev/pci/pcivar.h:203: warning: redundant redeclaration of
'BUS_READ_IVAR'
@/dev/pci/pcivar.h:203: warning: previous implicit declaration of
'BUS_READ_IVAR' was here
@/dev/pci/pcivar.h: In function `pci_set_vendor':
@/dev/pci/pcivar.h:205: warning: nested extern declaration of
`BUS_WRITE_IVAR'
@/dev/pci/pcivar.h:203: warning: redundant redeclaration of
'BUS_WRITE_IVAR'
@/dev/pci/pcivar.h:203: warning: previous implicit declaration of
'BUS_WRITE_IVAR' was here
@/dev/pci/pcivar.h: In function `pci_get_device':
@/dev/pci/pcivar.h:206: warning: nested extern declaration of
`BUS_READ_IVAR'
@/dev/pci/pcivar.h:203: warning: redundant redeclaration of
'BUS_READ_IVAR'
@/dev/pci/pcivar.h:203: warning: previous implicit declaration of
'BUS_READ_IVAR' was here
@/dev/pci/pcivar.h: In function `pci_set_device':
@/dev/pci/pcivar.h:206: warning: nested extern declaration of
`BUS_WRITE_IVAR'
@/dev/pci/pcivar.h:203: warning: redundant redeclaration of
'BUS_WRITE_IVAR'
@/dev/pci/pcivar.h:203: warning: previous implicit declaration of
'BUS_WRITE_IVAR' was here
@/dev/pci/pcivar.h: In function `pci_get_devid':
@/dev/pci/pcivar.h:207: warning: nested extern declaration of
`BUS_READ_IVAR'
@/dev/pci/pcivar.h:203: warning: redundant redeclaration of
'BUS_READ_IVAR'
@/dev/pci/pcivar.h:203: warning: previous implicit declaration of
'BUS_READ_IVAR' was here
@/dev/pci/pcivar.h: In function `pci_set_devid':
@/dev/pci/pcivar.h:207: warning: nested extern declaration of
`BUS_WRITE_IVAR'
@/dev/pci/pcivar.h:203: warning: redundant redeclaration of
'BUS_WRITE_IVAR'
@/dev/pci/pcivar.h:203: warning: previous implicit declaration of
'BUS_WRITE_IVAR' was here
@/dev/pci/pcivar.h: In function `pci_get_class':
@/dev/pci/pcivar.h:208: warning: nested extern declaration of
`BUS_READ_IVAR'
@/dev/pci/pcivar.h:203: warning: redundant redeclaration of
'BUS_READ_IVAR'
@/dev/pci/pcivar.h:203: warning: previous implicit declaration of
'BUS_READ_IVAR' was here
@/dev/pci/pcivar.h: In function `pci_set_class':
@/dev/pci/pcivar.h:208: warning: nested extern declaration of
`BUS_WRITE_IVAR'
@/dev/pci/pcivar.h:203: warning: redundant redeclaration of
'BUS_WRITE_IVAR'
@/dev/pci/pcivar.h:203: warning: previous implicit declaration of
'BUS_WRITE_IVAR' was here
@/dev/pci/pcivar.h: In function `pci_get_subclass':
@/dev/pci/pcivar.h:209: warning: nested extern declaration of
`BUS_READ_IVAR'
@/dev/pci/pcivar.h:203: warning: redundant redeclaration of
'BUS_READ_IVAR'
@/dev/pci/pcivar.h:203: warning: previous implicit declaration of
'BUS_READ_IVAR' was here
@/dev/pci/pcivar.h: In function `pci_set_subclass':
@/dev/pci/pcivar.h:209: warning: nested extern declaration of
`BUS_WRITE_IVAR'
@/dev/pci/pcivar.h:203: warning: redundant redeclaration of
'BUS_WRITE_IVAR'
@/dev/pci/pcivar.h:203: warning: previous implicit declaration of
'BUS_WRITE_IVAR' was here
@/dev/pci/pcivar.h: In function `pci_get_progif':
@/dev/pci/pcivar.h:210: warning: nested extern declaration of
`BUS_READ_IVAR'
@/dev/pci/pcivar.h:203: warning: redundant redeclaration of
'BUS_READ_IVAR'
@/dev/pci/pcivar.h:203: warning: previous implicit declaration of
'BUS_READ_IVAR' was he

Re: PCI Device Driver

2005-05-19 Thread Scott Long
Luís Vitório Cargnini wrote:
Hi i need to write a device driver for a PCI board. I read the
developers book see the exemples and i'm starting to write the device
driver. I'm writeing a device driver for a board with SAA713X TV chipset
from Phillips. I did theskeleton example, but whe i catch the example of
PCI driver from developers book and tried to compilate i receive the
following:
(forgive me for the long paste, but i need some answers and i need to
give the details)
PASTE of ERORS:
Yes, the skeleton driver is very out of date.  Would anyone object
to me updating it and tossing out the ISA code?
Scott
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: PCI Device Driver

2005-05-19 Thread Ulf Zimmermann
On Thu, May 19, 2005 at 11:27:45PM -0600, Scott Long wrote:
> Lu?s Vit?rio Cargnini wrote:
> 
> >Hi i need to write a device driver for a PCI board. I read the
> >developers book see the exemples and i'm starting to write the device
> >driver. I'm writeing a device driver for a board with SAA713X TV chipset
> >from Phillips. I did theskeleton example, but whe i catch the example of
> >PCI driver from developers book and tried to compilate i receive the
> >following:
> >(forgive me for the long paste, but i need some answers and i need to
> >give the details)
> >
> >
> >PASTE of ERORS:
> 
> Yes, the skeleton driver is very out of date.  Would anyone object
> to me updating it and tossing out the ISA code?
> 
> Scott

PLEASE! :-) I was starting to look at it myself for a driver to the
Digi/Patton 2977 card and got stucked.

___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: PCI Device Driver

2005-05-19 Thread M. Warner Losh
In message: <[EMAIL PROTECTED]>
Scott Long <[EMAIL PROTECTED]> writes:
: Yes, the skeleton driver is very out of date.  Would anyone object
: to me updating it and tossing out the ISA code?

I personally think it should be in dev/skel and in lint build instead
of squirreled away who knows where.  This would let us also make sure
that all the 'supported' busses be in the tree and always available
for copying.  We should then delete the weird things in
/usr/share/examples/drivers.  They are too hard to keep up to date.

Warner
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"