One of the first things I do in my build file is enable the slogger in
hopes of getting useful messages during my bring-up/port. Here is a
snippet from my build file:
[+script] .script = {
devc-ser8250 -e -c66000000 -b9600 0xfc004500,137 &
reopen
display_msg Welcome to Neutrino on UEI PowerDNA!
slogger &
waitfor /dev/slog
pci-pdna -v &
waitfor /dev/pci
reopen /dev/ser1
[+session] esh
}
The PCI driver is dying, (that’s what I’m debugging/porting) but
producing no messages in the syslogger. Furthermore, when I try to
examine the syslog, by typing:
cat /dev/slog
it hangs, and does not produce any output nor does it return to the
command prompt. Typing Ctl-C returns control to the console. Doing ‘ls
-l /dev/slog’ shows a zero length ‘slog’ file.
Any hints on why the slogger doesn’t appear to be capturing slogf()
calls from the PCI driver? (I have the verbosity set to maximum in the
source code for the pci-pdna module, and it should be producing all
kinds of output.)
One more note: these two lines are in the main() routine of my pci
server.c file:
// process args
printf(“PCI-PDNA Server started\n”);
slogf(_SLOGC_PCI, _SLOG_ERROR, “%s program started\n”, argv[0]);
Notice that the printf() does appear on my console, but still the slog
doesn’t produce anything…
-Chris Hallinan
Try sloginfo utility instead of ‘cat /dev/slog’. /dev/slog records have some
binary data that your tty doesn’t like.
“Chris Hallinan” <clh@net1plus.com> wrote in message
news:3DE25794.5080401@net1plus.com…
One of the first things I do in my build file is enable the slogger in
hopes of getting useful messages during my bring-up/port. Here is a
snippet from my build file:
[+script] .script = {
devc-ser8250 -e -c66000000 -b9600 0xfc004500,137 &
reopen
display_msg Welcome to Neutrino on UEI PowerDNA!
slogger &
waitfor /dev/slog
pci-pdna -v &
waitfor /dev/pci
reopen /dev/ser1
[+session] esh
}
The PCI driver is dying, (that’s what I’m debugging/porting) but
producing no messages in the syslogger. Furthermore, when I try to
examine the syslog, by typing:
cat /dev/slog
it hangs, and does not produce any output nor does it return to the
command prompt. Typing Ctl-C returns control to the console. Doing ‘ls
-l /dev/slog’ shows a zero length ‘slog’ file.
Any hints on why the slogger doesn’t appear to be capturing slogf()
calls from the PCI driver? (I have the verbosity set to maximum in the
source code for the pci-pdna module, and it should be producing all
kinds of output.)
One more note: these two lines are in the main() routine of my pci
server.c file:
// process args
printf(“PCI-PDNA Server started\n”);
slogf(_SLOGC_PCI, _SLOG_ERROR, “%s program started\n”, argv[0]);
Notice that the printf() does appear on my console, but still the slog
doesn’t produce anything…
-Chris Hallinan