pseudo-device error in messages

pseudo-device error in messages

Post by Casper H.S. Dik - Network Security Engine » Sat, 18 Nov 1995 04:00:00




>I've got a SS 20 running Sol 2.4 (101945-32), and have found many
>Nov 17 01:12:27 billy unix: pseudo-device: vol0

>Nov 17 02:28:25 billy unix: pseudo-device: vol0

>errors in the messages file. What are these errors? Is it something
>to worry about?

These are not errors.  Simply an indication that the volume manager
device drivers was unloaded and reloaded, probably because of lack
of kernel memory.

Unloading/loading the vol0 driver leaks kernel memory, except
when you install patch 101907-05

Casper

--
Expressed in this posting are my opinions.  They are in no way related
to opinions held by my employer, Sun Microsystems.

 
 
 

pseudo-device error in messages

Post by Koon Ta » Sat, 18 Nov 1995 04:00:00


Hello all,

I've got a SS 20 running Sol 2.4 (101945-32), and have found many

Nov 17 01:12:27 billy unix: pseudo-device: vol0

Nov 17 02:28:25 billy unix: pseudo-device: vol0

errors in the messages file. What are these errors? Is it something
to worry about?

Thanks in advance.
--

Nuclear Physics Research Group,            fax: +44 (0)1273 642405
Department of Mathematical Sciences,
Univesity of Brighton, UK.

 
 
 

1. STREAMS message from pseudo-device to pseudo-device

Hi everybody,

I have a kernel device driver programming related question for Solaris
2.6.

We have a packet classifier which sits between the IP pseudo-driver
and the network interface driver.

We need to send an unacknowledged message from the IP driver to our
classifier so as to pass on connection setup information. The classifier
is implemented as a pseudo device driver. We have plumbed the classifier
beneath IP, and now need a way to send M_PROTO messages from the IP driver
to the classifier. We have saved up the address of the device write queue
of our classifier in a global variable, but a putnext of a message from IP
onto the classifier's device write queue causes the machine to crash.

(1) In short, is there a way for M_PROTO messages to be transmitted from
IP to our classifier beneath it.

(2) Is there a way to set up a STREAM between two kernel pseudo device
drivers?

Thanks a bunch in advance.

Regards,
ravi

2. Kernel panic? What does this mean?

3. May 23 10:50:05 mwsbit04 pseudo: [ID 129642 kern.info] pseudo-device: devinfo0

4. thegreatkarthik@yahoo.co.in

5. Network Pseudo-device question

6. compile Xautolock

7. undefined pseudo-device abcd

8. Subject: Confusion re. "find -perm ..."

9. HELP: configuring tun0 pseudo-device

10. Pseudo-Device Driver in Solaris 2.x

11. Pseudo-device Qns

12. Help developing a pseudo-device driver ?

13. SUMMARY: Is this a job for a pseudo-device driver?