Can't turn off SSB (CONFIG_SSB)?

DISCUSSION Philip A. Prindeville 5 participants 17 messages Dec 21, 2009

lore

Share & tools

lore

Philip A. Prindeville

author

2009-12-21 01:16 UTC #0 lore raw

I'm building images for an EMBEDDED platform, and forcing CONFIG_SSB_POSSIBLE=n, but I'm still seeing:

*
* Sonics Silicon Backplane
*
Sonics Silicon Backplane support (SSB) [M/y/?] (NEW) n

Support for the Sonics Silicon Backplane bus. You only need to enable this option, if you are configuring a kernel for an embedded system with this bus.
It will be auto-selected if needed in other environments.

The module will be called ssb.

If unsure, say N.

Sonics Silicon Backplane support (SSB) [M/y/?] (NEW) n

The module will be called ssb.

If unsure, say N.

Sonics Silicon Backplane support (SSB) [M/y/?] (NEW)

And why does arch/x86/configs/i386_defconfig nail up CONFIG_SSB_POSSIBLE?

This is with 2.6.27.38.

And what are the steps to figuring out the dependency that keeps forcing it on? Something must be doing a "select SSB" but I'm not sure what.

Randy Dunlap

2009-12-21 01:51 UTC #1 lore raw

Quoted 1 line · On Sun, 20 Dec 2009 17:16:34 -0800 Philip A. Prindeville wrote:

I'm building images for an EMBEDDED platform, and forcing CONFIG_SSB_POSSIBLE=n, but I'm still seeing:

What $ARCH ?

Quoted 27 lines

*
* Sonics Silicon Backplane
*
Sonics Silicon Backplane support (SSB) [M/y/?] (NEW) n
Support for the Sonics Silicon Backplane bus. You only need to enable this option, if you are configuring a kernel for an embedded system with this bus.
It will be auto-selected if needed in other environments.
The module will be called ssb.
If unsure, say N.
Sonics Silicon Backplane support (SSB) [M/y/?] (NEW) n
Support for the Sonics Silicon Backplane bus. You only need to enable this option, if you are configuring a kernel for an embedded system with this bus.
It will be auto-selected if needed in other environments.
The module will be called ssb.

Quoted 7 lines

If unsure, say N.
Sonics Silicon Backplane support (SSB) [M/y/?] (NEW)
And why does arch/x86/configs/i386_defconfig nail up CONFIG_SSB_POSSIBLE?

That just means that SSB support is possible:

config SSB_POSSIBLE

	bool
	depends on HAS_IOMEM && HAS_DMA
	default y

Shouldn't be a problem.

Quoted 3 lines

This is with 2.6.27.38.
And what are the steps to figuring out the dependency that keeps forcing it on? Something must be doing a "select SSB" but I'm not sure what.

Are you using b43 or b44 network drivers?

---
~Randy

Philip A. Prindeville

author

2009-12-21 04:22 UTC #2 lore raw

Quoted 5 lines · Randy Dunlap

Quoted 1 line · On Sun, 20 Dec 2009 17:16:34 -0800 Philip A. Prindeville wrote:
I'm building images for an EMBEDDED platform, and forcing CONFIG_SSB_POSSIBLE=n, but I'm still seeing:
What $ARCH ?

i586.

Quoted 43 lines

Quoted 28 lines
*
* Sonics Silicon Backplane
*
Sonics Silicon Backplane support (SSB) [M/y/?] (NEW) n
Support for the Sonics Silicon Backplane bus. You only need to enable this option, if you are configuring a kernel for an embedded system with this bus.
It will be auto-selected if needed in other environments.
The module will be called ssb.
If unsure, say N.
Sonics Silicon Backplane support (SSB) [M/y/?] (NEW) n
Support for the Sonics Silicon Backplane bus. You only need to enable this option, if you are configuring a kernel for an embedded system with this bus.
It will be auto-selected if needed in other environments.
The module will be called ssb.
Quoted 7 lines
If unsure, say N.
Sonics Silicon Backplane support (SSB) [M/y/?] (NEW)
And why does arch/x86/configs/i386_defconfig nail up CONFIG_SSB_POSSIBLE?
That just means that SSB support is possible:
config SSB_POSSIBLE
	bool
	depends on HAS_IOMEM && HAS_DMA
	default y

Quoted 7 lines

Shouldn't be a problem.
Quoted 3 lines
This is with 2.6.27.38.
And what are the steps to figuring out the dependency that keeps forcing it on? Something must be doing a "select SSB" but I'm not sure what.
Are you using b43 or b44 network drivers?

Neither.

I can attach the .config we're using, if you want...

-Philip

Quoted 2 lines

---
~Randy

Randy Dunlap

2009-12-21 16:09 UTC #3 lore raw

Quoted 57 lines · On Sun, 20 Dec 2009 20:22:19 -0800 Philip A. Prindeville wrote:

Quoted 5 lines · Randy Dunlap
Quoted 1 line · On Sun, 20 Dec 2009 17:16:34 -0800 Philip A. Prindeville wrote:
I'm building images for an EMBEDDED platform, and forcing CONFIG_SSB_POSSIBLE=n, but I'm still seeing:
What $ARCH ?
i586.
Quoted 47 lines
Quoted 28 lines
*
* Sonics Silicon Backplane
*
Sonics Silicon Backplane support (SSB) [M/y/?] (NEW) n
Support for the Sonics Silicon Backplane bus. You only need to enable this option, if you are configuring a kernel for an embedded system with this bus.
It will be auto-selected if needed in other environments.
The module will be called ssb.
If unsure, say N.
Sonics Silicon Backplane support (SSB) [M/y/?] (NEW) n
Support for the Sonics Silicon Backplane bus. You only need to enable this option, if you are configuring a kernel for an embedded system with this bus.
It will be auto-selected if needed in other environments.
The module will be called ssb.
Quoted 7 lines
If unsure, say N.
Sonics Silicon Backplane support (SSB) [M/y/?] (NEW)
And why does arch/x86/configs/i386_defconfig nail up CONFIG_SSB_POSSIBLE?
That just means that SSB support is possible:
config SSB_POSSIBLE
	bool
	depends on HAS_IOMEM && HAS_DMA
	default y
Shouldn't be a problem.
Quoted 2 lines
This is with 2.6.27.38.

Quoted 7 lines

Quoted 3 lines
Quoted 1 line
And what are the steps to figuring out the dependency that keeps forcing it on? Something must be doing a "select SSB" but I'm not sure what.
Are you using b43 or b44 network drivers?
Neither.
I can attach the .config we're using, if you want...

Sure, if you are still having problems with it.

---
~Randy

Philip A. Prindeville

author

2009-12-21 18:31 UTC #4 lore raw

Quoted 63 lines · Randy Dunlap

Quoted 61 lines · On Sun, 20 Dec 2009 20:22:19 -0800 Philip A. Prindeville wrote:
Quoted 5 lines · Randy Dunlap
Quoted 1 line · On Sun, 20 Dec 2009 17:16:34 -0800 Philip A. Prindeville wrote:
I'm building images for an EMBEDDED platform, and forcing CONFIG_SSB_POSSIBLE=n, but I'm still seeing:
What $ARCH ?
i586.
Quoted 50 lines
Quoted 28 lines
*
* Sonics Silicon Backplane
*
Sonics Silicon Backplane support (SSB) [M/y/?] (NEW) n
Support for the Sonics Silicon Backplane bus. You only need to enable this option, if you are configuring a kernel for an embedded system with this bus.
It will be auto-selected if needed in other environments.
The module will be called ssb.
If unsure, say N.
Sonics Silicon Backplane support (SSB) [M/y/?] (NEW) n
Support for the Sonics Silicon Backplane bus. You only need to enable this option, if you are configuring a kernel for an embedded system with this bus.
It will be auto-selected if needed in other environments.
The module will be called ssb.
Quoted 7 lines
If unsure, say N.
Sonics Silicon Backplane support (SSB) [M/y/?] (NEW)
And why does arch/x86/configs/i386_defconfig nail up CONFIG_SSB_POSSIBLE?
That just means that SSB support is possible:
config SSB_POSSIBLE
	bool
	depends on HAS_IOMEM && HAS_DMA
	default y
Shouldn't be a problem.
Quoted 3 lines
This is with 2.6.27.38.
And what are the steps to figuring out the dependency that keeps forcing it on? Something must be doing a "select SSB" but I'm not sure what.
Are you using b43 or b44 network drivers?

Quoted 8 lines

Quoted 3 lines
Neither.
I can attach the .config we're using, if you want...
Sure, if you are still having problems with it.
---
~Randy

Here's what we have.

-Philip

Michael Buesch

2009-12-21 18:45 UTC #5 lore raw

Quoted 1 line · On Monday 21 December 2009 19:31:06 Philip A. Prindeville wrote:

Here's what we have.

# CONFIG_SSB is not set

Signature · 1 line

Greetings, Michael.

Philip A. Prindeville

author

2009-12-21 19:06 UTC #6 lore raw

Quoted 5 lines · Michael Buesch

Quoted 1 line · On Monday 21 December 2009 19:31:06 Philip A. Prindeville wrote:
Here's what we have.
# CONFIG_SSB is not set

Ok, here's what's happening.

We have a "canned" config that we copy over, per platform.

I'm showing diffs of that config with what results (i.e. what's left in the linux-2.6.27.38 directory after running "make silentoldconfig" and "make prepare1"):

linux-2.6.27.38-astlinux/.config 2009-12-21 11:02:34.000000000 -0800 renamed from device/via-c7/linux.config 2009-12-21 10:55:55.000000000 -0800 +14 -4

@@ -1,7 +1,7 @@
 #
 # Automatically generated make config: don't edit
 # Linux kernel version: 2.6.27.38
-# Tue Nov 10 16:50:01 2009
+# Mon Dec 21 11:02:34 2009
 #
 # CONFIG_64BIT is not set
 CONFIG_X86_32=y

@@ -1446,8 +1446,16 @@
 #
 # Sonics Silicon Backplane
 #
-CONFIG_SSB_POSSIBLE=n
-CONFIG_SSB=n
+CONFIG_SSB_POSSIBLE=y
+CONFIG_SSB=m
+CONFIG_SSB_SPROM=y
+CONFIG_SSB_PCIHOST_POSSIBLE=y
+CONFIG_SSB_PCIHOST=y
+# CONFIG_SSB_B43_PCI_BRIDGE is not set
+# CONFIG_SSB_SILENT is not set
+# CONFIG_SSB_DEBUG is not set
+CONFIG_SSB_DRIVER_PCICORE_POSSIBLE=y
+CONFIG_SSB_DRIVER_PCICORE=y
 
 #
 # Multifunction device drivers

@@ -1621,6 +1629,8 @@
 # CONFIG_USB_DYNAMIC_MINORS is not set
 # CONFIG_USB_SUSPEND is not set
 # CONFIG_USB_OTG is not set
+# CONFIG_USB_OTG_WHITELIST is not set
+# CONFIG_USB_OTG_BLACKLIST_HUB is not set
 # CONFIG_USB_MON is not set
 
 #

@@ -1955,7 +1965,7 @@
 CONFIG_DEBUG_FS=y
 # CONFIG_HEADERS_CHECK is not set
 # CONFIG_DEBUG_KERNEL is not set
-CONFIG_DEBUG_BUGVERBOSE=y
+# CONFIG_DEBUG_BUGVERBOSE is not set
 CONFIG_DEBUG_MEMORY_INIT=y
 # CONFIG_LATENCYTOP is not set
 CONFIG_SYSCTL_SYSCALL_CHECK=y

as you can see, a bunch of things are getting "turned on" that we explicitly turned off.

-Philip

Michael Buesch

2009-12-21 19:09 UTC #7 lore raw

Quoted 63 lines · On Monday 21 December 2009 20:06:13 Philip A. Prindeville wrote:

Quoted 5 lines · Michael Buesch

Quoted 1 line · On Monday 21 December 2009 19:31:06 Philip A. Prindeville wrote:
Here's what we have.
# CONFIG_SSB is not set

Ok, here's what's happening.

We have a "canned" config that we copy over, per platform.

I'm showing diffs of that config with what results (i.e. what's left in the linux-2.6.27.38 directory after running "make silentoldconfig" and "make prepare1"):

linux-2.6.27.38-astlinux/.config 2009-12-21 11:02:34.000000000 -0800 renamed from device/via-c7/linux.config 2009-12-21 10:55:55.000000000 -0800 +14 -4

@@ -1,7 +1,7 @@
 #
 # Automatically generated make config: don't edit
 # Linux kernel version: 2.6.27.38
-# Tue Nov 10 16:50:01 2009
+# Mon Dec 21 11:02:34 2009
 #
 # CONFIG_64BIT is not set
 CONFIG_X86_32=y

@@ -1446,8 +1446,16 @@
 #
 # Sonics Silicon Backplane
 #
-CONFIG_SSB_POSSIBLE=n
-CONFIG_SSB=n
+CONFIG_SSB_POSSIBLE=y
+CONFIG_SSB=m
+CONFIG_SSB_SPROM=y
+CONFIG_SSB_PCIHOST_POSSIBLE=y
+CONFIG_SSB_PCIHOST=y
+# CONFIG_SSB_B43_PCI_BRIDGE is not set
+# CONFIG_SSB_SILENT is not set
+# CONFIG_SSB_DEBUG is not set
+CONFIG_SSB_DRIVER_PCICORE_POSSIBLE=y
+CONFIG_SSB_DRIVER_PCICORE=y
 
 #
 # Multifunction device drivers

@@ -1621,6 +1629,8 @@
 # CONFIG_USB_DYNAMIC_MINORS is not set
 # CONFIG_USB_SUSPEND is not set
 # CONFIG_USB_OTG is not set
+# CONFIG_USB_OTG_WHITELIST is not set
+# CONFIG_USB_OTG_BLACKLIST_HUB is not set
 # CONFIG_USB_MON is not set
 
 #

@@ -1955,7 +1965,7 @@
 CONFIG_DEBUG_FS=y
 # CONFIG_HEADERS_CHECK is not set
 # CONFIG_DEBUG_KERNEL is not set
-CONFIG_DEBUG_BUGVERBOSE=y
+# CONFIG_DEBUG_BUGVERBOSE is not set
 CONFIG_DEBUG_MEMORY_INIT=y
 # CONFIG_LATENCYTOP is not set
 CONFIG_SYSCTL_SYSCALL_CHECK=y

Quoted 6 lines

as you can see, a bunch of things are getting "turned on" that we explicitly turned off.
-Philip

That is expected, because you have
CONFIG_B44=m

Signature · 1 line

Greetings, Michael.

Randy Dunlap

2009-12-21 19:11 UTC #8 lore raw

In reply to Philip A. Prindeville

Quoted 63 lines · On Mon, 21 Dec 2009 11:06:13 -0800 Philip A. Prindeville wrote:

Quoted 5 lines · Michael Buesch

Quoted 1 line · On Monday 21 December 2009 19:31:06 Philip A. Prindeville wrote:
Here's what we have.
# CONFIG_SSB is not set

Ok, here's what's happening.

We have a "canned" config that we copy over, per platform.

I'm showing diffs of that config with what results (i.e. what's left in the linux-2.6.27.38 directory after running "make silentoldconfig" and "make prepare1"):

linux-2.6.27.38-astlinux/.config 2009-12-21 11:02:34.000000000 -0800 renamed from device/via-c7/linux.config 2009-12-21 10:55:55.000000000 -0800 +14 -4

@@ -1,7 +1,7 @@
 #
 # Automatically generated make config: don't edit
 # Linux kernel version: 2.6.27.38
-# Tue Nov 10 16:50:01 2009
+# Mon Dec 21 11:02:34 2009
 #
 # CONFIG_64BIT is not set
 CONFIG_X86_32=y

@@ -1446,8 +1446,16 @@
 #
 # Sonics Silicon Backplane
 #
-CONFIG_SSB_POSSIBLE=n
-CONFIG_SSB=n
+CONFIG_SSB_POSSIBLE=y
+CONFIG_SSB=m
+CONFIG_SSB_SPROM=y
+CONFIG_SSB_PCIHOST_POSSIBLE=y
+CONFIG_SSB_PCIHOST=y
+# CONFIG_SSB_B43_PCI_BRIDGE is not set
+# CONFIG_SSB_SILENT is not set
+# CONFIG_SSB_DEBUG is not set
+CONFIG_SSB_DRIVER_PCICORE_POSSIBLE=y
+CONFIG_SSB_DRIVER_PCICORE=y
 
 #
 # Multifunction device drivers

@@ -1621,6 +1629,8 @@
 # CONFIG_USB_DYNAMIC_MINORS is not set
 # CONFIG_USB_SUSPEND is not set
 # CONFIG_USB_OTG is not set
+# CONFIG_USB_OTG_WHITELIST is not set
+# CONFIG_USB_OTG_BLACKLIST_HUB is not set
 # CONFIG_USB_MON is not set
 
 #

@@ -1955,7 +1965,7 @@
 CONFIG_DEBUG_FS=y
 # CONFIG_HEADERS_CHECK is not set
 # CONFIG_DEBUG_KERNEL is not set
-CONFIG_DEBUG_BUGVERBOSE=y
+# CONFIG_DEBUG_BUGVERBOSE is not set
 CONFIG_DEBUG_MEMORY_INIT=y
 # CONFIG_LATENCYTOP is not set
 CONFIG_SYSCTL_SYSCALL_CHECK=y

Quoted 1 line

as you can see, a bunch of things are getting "turned on" that we explicitly turned off.

Your custom config seems to enable B44, which selects SSB. Can you disable B44?

---
~Randy

Holger Schurig

2009-12-21 08:24 UTC #9 lore raw

In reply to Philip A. Prindeville

Quoted 3 lines

And what are the steps to figuring out the dependency that keeps forcing it on? Something must be doing a "select SSB" but I'm not sure what.

"make xconfig", and then turn on "Options -> Show Debug Info".

Then you see the reverse dep.

Another thing would be "find -name Kconfig |xargs grep SSB_POSSIBLE" and then carefully check those files.

Signature · 1 line

http://www.holgerschurig.de

Philip A. Prindeville

author

2009-12-21 18:51 UTC #10 lore raw

Quoted 11 lines · Holger Schurig

Quoted 3 lines
And what are the steps to figuring out the dependency that keeps forcing it on? Something must be doing a "select SSB" but I'm not sure what.
"make xconfig", and then turn on "Options -> Show Debug Info".
Then you see the reverse dep.
Another thing would be "find -name Kconfig |xargs grep SSB_POSSIBLE" and then carefully check those files.

Well, as I mentioned, arch/x86/configs/i386_defconfig contains:

CONFIG_SSB_POSSIBLE=y

which I've not been able to understand why. There are lots of x86 configurations where this might *not* be possible, in embedded platforms in particular.

-Philip

John W. Linville

2009-12-21 19:00 UTC #11 lore raw

Quoted 10 lines · Philip A. Prindeville

Quoted 9 lines · Holger Schurig
Quoted 3 lines
And what are the steps to figuring out the dependency that keeps forcing it on? Something must be doing a "select SSB" but I'm not sure what.
"make xconfig", and then turn on "Options -> Show Debug Info".
Then you see the reverse dep.

Quoted 8 lines

Quoted 2 lines
Another thing would be "find -name Kconfig |xargs grep SSB_POSSIBLE" and then carefully check those files.
Well, as I mentioned, arch/x86/configs/i386_defconfig contains:
CONFIG_SSB_POSSIBLE=y
which I've not been able to understand why. There are lots of x86 configurations where this might *not* be possible, in embedded platforms in particular.

config SSB_POSSIBLE

        bool
        depends on HAS_IOMEM && HAS_DMA
        default y

What x86 configurations don't have IOMEM or DMA? And what difference does it make if SSB_POSSIBLE is defined if it doesn't build any code?

John

Signature · 2 lines

John W. Linville		Someday the world will need a hero, and you
[email protected]			might be all we have.  Be ready.

Philip A. Prindeville

author

2009-12-21 19:07 UTC #12 lore raw

Quoted 21 lines · John W. Linville

Quoted 10 lines · Philip A. Prindeville
Quoted 9 lines · Holger Schurig
Quoted 3 lines
And what are the steps to figuring out the dependency that keeps forcing it on? Something must be doing a "select SSB" but I'm not sure what.
"make xconfig", and then turn on "Options -> Show Debug Info".
Then you see the reverse dep.
Quoted 8 lines
Quoted 2 lines
Another thing would be "find -name Kconfig |xargs grep SSB_POSSIBLE" and then carefully check those files.
Well, as I mentioned, arch/x86/configs/i386_defconfig contains:
CONFIG_SSB_POSSIBLE=y
which I've not been able to understand why. There are lots of x86 configurations where this might *not* be possible, in embedded platforms in particular.
config SSB_POSSIBLE

Quoted 8 lines

        bool
        depends on HAS_IOMEM && HAS_DMA
        default y
What x86 configurations don't have IOMEM or DMA? And what difference does it make if SSB_POSSIBLE is defined if it doesn't build any code?
John

The issue is that later on when we build compat-wireless, then my .config file from the linux build directory gets sourced by that and we get a bunch of warnings from the b43, b44, etc. drivers that some ssb_* entry points are missing.

Michael Buesch

2009-12-21 19:11 UTC #13 lore raw

Quoted 1 line · On Monday 21 December 2009 20:07:47 Philip A. Prindeville wrote:

The issue is that later on when we build compat-wireless, then my .config file from the linux build directory gets sourced by that and we get a bunch of warnings from the b43, b44, etc. drivers that some ssb_* entry points are missing.

So, disable these drivers?

Signature · 1 line

Greetings, Michael.

Randy Dunlap

2009-12-21 19:03 UTC #14 lore raw

In reply to Philip A. Prindeville

Quoted 10 lines · On Mon, 21 Dec 2009 10:51:16 -0800 Philip A. Prindeville wrote:

Quoted 9 lines · Holger Schurig
Quoted 3 lines
And what are the steps to figuring out the dependency that keeps forcing it on? Something must be doing a "select SSB" but I'm not sure what.
"make xconfig", and then turn on "Options -> Show Debug Info".
Then you see the reverse dep.

Quoted 6 lines

Quoted 2 lines
Another thing would be "find -name Kconfig |xargs grep SSB_POSSIBLE" and then carefully check those files.
Well, as I mentioned, arch/x86/configs/i386_defconfig contains:
CONFIG_SSB_POSSIBLE=y

That is =y iff:

config SSB_POSSIBLE

	bool
	depends on HAS_IOMEM && HAS_DMA
	default y

HAS_IOMEM=y and HAS_DMA=y. Aren't those both =y on your platform?

Other than being set, it shouldn't be hurting anything.

Quoted 1 line

which I've not been able to understand why. There are lots of x86 configurations where this might *not* be possible, in embedded platforms in particular.

---
~Randy

Michael Buesch

2009-12-21 12:29 UTC #15 lore raw

In reply to Philip A. Prindeville

Quoted 35 lines · On Monday 21 December 2009 02:16:34 Philip A. Prindeville wrote:

I'm building images for an EMBEDDED platform, and forcing CONFIG_SSB_POSSIBLE=n, but I'm still seeing:
*
* Sonics Silicon Backplane
*
Sonics Silicon Backplane support (SSB) [M/y/?] (NEW) n
Support for the Sonics Silicon Backplane bus. You only need to enable this option, if you are configuring a kernel for an embedded system with this bus.
It will be auto-selected if needed in other environments.
The module will be called ssb.
If unsure, say N.
Sonics Silicon Backplane support (SSB) [M/y/?] (NEW) n
Support for the Sonics Silicon Backplane bus. You only need to enable this option, if you are configuring a kernel for an embedded system with this bus.
It will be auto-selected if needed in other environments.
The module will be called ssb.
If unsure, say N.
Sonics Silicon Backplane support (SSB) [M/y/?] (NEW)

Quoted 5 lines

And why does arch/x86/configs/i386_defconfig nail up CONFIG_SSB_POSSIBLE?
This is with 2.6.27.38.
And what are the steps to figuring out the dependency that keeps forcing it on? Something must be doing a "select SSB" but I'm not sure what.

CONFIG_SSB_POSSIBLE is just a management config entry that does not affect compilation. It's just used to get the dependencies right. As long as CONFIG_SSB is n, no SSB code will be built. CONFIG_SSB_POSSIBLE does just indicate whether it's possible to enable SSB. No more and no less. It's just used as a dependency for the other modules that do a "select SSB".

The drivers that automatically select CONFIG_SSB are:

- bcm47xx MIPS platform
- bcm63xx MIPS platform
- b43 driver
- b43legacy driver
- b44 driver

Signature · 1 line

Greetings, Michael.

Michael Buesch

2009-12-21 12:35 UTC #16 lore raw

Philipp, your server is bouncing mail (just in case you read the list archives or whatever :D):

Quoted 4 lines

[email protected]
SMTP error from remote mail server after initial connection:
host mail.redfish-solutions.com [66.232.79.143]:
554 mail.redfish-solutions.com ESMTP not accepting messages

Signature · 1 line

Greetings, Michael.