Re: Missing serial port after enabling serial console in loader.conf
On Monday, April 25, 2011 5:38:30 pm Przemyslaw Frasunek wrote: > > I don't think so. You can try swapping the hints for sio0 and sio1 and > > seeing if > > sio1 suddenly shows up as working and valid. If so, then the changes in 8 > > to bind > > unit numbers using hints might work for you to get COM1 back as sio0. > > Few days ago I decided to upgrade to 8.2-STABLE, partially due to some > long-standing Netgraph issues (which I discussed on freebsd-net). To my > surprise, sio0 (well, now uart0) had become detectable even in spite of > enabled SOL: > > uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 > uart0: [FILTER] > uart0: console (9600,n,8,1) > uart1: <16550 or compatible> port 0x2f8-0x2ff irq 3 on acpi0 > uart1: [FILTER] > > Eventually I'm able to use comconsole in loader.conf and getty simultaneously. > > BTW. I looked at the BIOS setup on my box - it has "Legacy OS" knob, allowing > to > hide serial port occupied by SOL from non ACPI aware OS. It was disabled for > all > the time, so my problem was probably related to sio(4) and fixed in uart(4). No, this was almost certainly due to the hints logic in 8. :) Probably what happened before is that ACPI was not listing COM1 at all, but then COM2 probed as sio0. Then there was no device for the I/O port resources for COM1. The hint changes in 8 would work around that issue by recognizing that case and keeping COM2 at sio1. That would then have allowed sio0 to probe at isa0. -- John Baldwin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Missing serial port after enabling serial console in loader.conf
> I don't think so. You can try swapping the hints for sio0 and sio1 and > seeing if > sio1 suddenly shows up as working and valid. If so, then the changes in 8 to > bind > unit numbers using hints might work for you to get COM1 back as sio0. Few days ago I decided to upgrade to 8.2-STABLE, partially due to some long-standing Netgraph issues (which I discussed on freebsd-net). To my surprise, sio0 (well, now uart0) had become detectable even in spite of enabled SOL: uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 uart0: [FILTER] uart0: console (9600,n,8,1) uart1: <16550 or compatible> port 0x2f8-0x2ff irq 3 on acpi0 uart1: [FILTER] Eventually I'm able to use comconsole in loader.conf and getty simultaneously. BTW. I looked at the BIOS setup on my box - it has "Legacy OS" knob, allowing to hide serial port occupied by SOL from non ACPI aware OS. It was disabled for all the time, so my problem was probably related to sio(4) and fixed in uart(4). -- * Fido: 2:480/124 ** WWW: http://www.frasunek.com ** NICHDL: PMF9-RIPE * * Jabber ID: veng...@nette.pl ** PGP ID: 2578FCAD ** HAM-RADIO: SQ5JIV * ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Missing serial port after enabling serial console in loader.conf
On Tuesday, April 19, 2011 7:05:34 pm Przemyslaw Frasunek wrote: > > The _STA method is used to query a device's status, and a status of 0 means > > that the device is disabled. I believe that this means that when you have > > SOL enabled (SOLE?) that COM1 is marked inactive so the OS ignores the > > device. > > Good catch, thanks! I had a feeling, that it must be caused by firmware. Is > there any way to override above checks and make SIO detectable even with > enabled > SOL? I don't think so. You can try swapping the hints for sio0 and sio1 and seeing if sio1 suddenly shows up as working and valid. If so, then the changes in 8 to bind unit numbers using hints might work for you to get COM1 back as sio0. -- John Baldwin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Missing serial port after enabling serial console in loader.conf
> The _STA method is used to query a device's status, and a status of 0 means > that the device is disabled. I believe that this means that when you have > SOL enabled (SOLE?) that COM1 is marked inactive so the OS ignores the device. Good catch, thanks! I had a feeling, that it must be caused by firmware. Is there any way to override above checks and make SIO detectable even with enabled SOL? -- * Fido: 2:480/124 ** WWW: http://www.frasunek.com ** NICHDL: PMF9-RIPE * * Jabber ID: veng...@nette.pl ** PGP ID: 2578FCAD ** HAM-RADIO: SQ5JIV * ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Missing serial port after enabling serial console in loader.conf
On Monday, April 18, 2011 1:22:59 pm Przemyslaw Frasunek wrote:
> > 1) Add a printf to sioprobe() in sys/dev/sio/sio.c to output an error
> > message
> > when it fails to allocate a SYS_RES_IOPORT device at the very beginning.
>
> Done. I'll need to wait until next reboot - it's a production box, so it has
> to
> be done in night hours.
>
> > 2) Capture 'acpidump -d' output and post it somewhere?
>
> http://www.frasunek.com/tmp/acpidump.txt
Hmm, I think we have the answer:
Device (UAR1)
{
Name (_HID, EisaId ("PNP0501"))
Name (_UID, 0x01)
Method (_STA, 0, NotSerialized)
{
If (SOLE)
{
Return (0x00)
}
The _STA method is used to query a device's status, and a status of 0 means
that the device is disabled. I believe that this means that when you have
SOL enabled (SOLE?) that COM1 is marked inactive so the OS ignores the device.
--
John Baldwin
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Missing serial port after enabling serial console in loader.conf
> 1) Add a printf to sioprobe() in sys/dev/sio/sio.c to output an error message > when it fails to allocate a SYS_RES_IOPORT device at the very beginning. Done. I'll need to wait until next reboot - it's a production box, so it has to be done in night hours. > 2) Capture 'acpidump -d' output and post it somewhere? http://www.frasunek.com/tmp/acpidump.txt -- * Fido: 2:480/124 ** WWW: http://www.frasunek.com ** NICHDL: PMF9-RIPE * * Jabber ID: veng...@nette.pl ** PGP ID: 2578FCAD ** HAM-RADIO: SQ5JIV * ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Missing serial port after enabling serial console in loader.conf
On Saturday, April 16, 2011 7:13:16 pm Przemyslaw Frasunek wrote: > > Hmm, I don't see it even trying to probe the COM1 device. I'll have to wait > > until you get a verbose dmesg to investigate further I'm afraid. :( > > I've got verbose dmesg now: http://www.frasunek.com/tmp/dmesg-verb.txt Hummm. Can you do a few things: 1) Add a printf to sioprobe() in sys/dev/sio/sio.c to output an error message when it fails to allocate a SYS_RES_IOPORT device at the very beginning. 2) Capture 'acpidump -d' output and post it somewhere? -- John Baldwin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Missing serial port after enabling serial console in loader.conf
> Hmm, I don't see it even trying to probe the COM1 device. I'll have to wait > until you get a verbose dmesg to investigate further I'm afraid. :( I've got verbose dmesg now: http://www.frasunek.com/tmp/dmesg-verb.txt ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Missing serial port after enabling serial console in loader.conf
On Friday, April 15, 2011 3:04:49 pm Przemyslaw Frasunek wrote: > > Hmm, that unknown device is your COM1. Do you have a copy of your current > > dmesg available? I'm curious if sio0 failed to probe the UAR1 device and > > then > > later attached to UAR2. > > Sure, this is my non-verbose dmesg: http://www.frasunek.com/tmp/dmesg.txt > > It's from 7.3-RELEASE, but on 7.4 I get the same behaviour. Hmm, I don't see it even trying to probe the COM1 device. I'll have to wait until you get a verbose dmesg to investigate further I'm afraid. :( -- John Baldwin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Missing serial port after enabling serial console in loader.conf
> Hmm, that unknown device is your COM1. Do you have a copy of your current > dmesg available? I'm curious if sio0 failed to probe the UAR1 device and > then > later attached to UAR2. Sure, this is my non-verbose dmesg: http://www.frasunek.com/tmp/dmesg.txt It's from 7.3-RELEASE, but on 7.4 I get the same behaviour. -- * Fido: 2:480/124 ** WWW: http://www.frasunek.com ** NICHDL: PMF9-RIPE * * Jabber ID: veng...@nette.pl ** PGP ID: 2578FCAD ** HAM-RADIO: SQ5JIV * ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Missing serial port after enabling serial console in loader.conf
On Friday, April 15, 2011 2:31:20 pm Przemyslaw Frasunek wrote: > > Hmm, can you post the output of 'devinfo -vr' and a verbose dmesg at a URL? > > Devinfo output is here: http://www.frasunek.com/tmp/devinfo.txt > > I'll post verbose dmesg after next reboot, which is already scheduled on sunday > morning. unknown pnpinfo _HID=PNP0501 _UID=1 at handle=\_SB_.PCI0.LPC0.UAR1 sio0 pnpinfo _HID=PNP0501 _UID=2 at handle=\_SB_.PCI0.LPC0.UAR2 Interrupt request lines: 3 I/O ports: 0x2f8-0x2ff Hmm, that unknown device is your COM1. Do you have a copy of your current dmesg available? I'm curious if sio0 failed to probe the UAR1 device and then later attached to UAR2. -- John Baldwin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Missing serial port after enabling serial console in loader.conf
> Hmm, can you post the output of 'devinfo -vr' and a verbose dmesg at a URL? Devinfo output is here: http://www.frasunek.com/tmp/devinfo.txt I'll post verbose dmesg after next reboot, which is already scheduled on sunday morning. -- * Fido: 2:480/124 ** WWW: http://www.frasunek.com ** NICHDL: PMF9-RIPE * * Jabber ID: veng...@nette.pl ** PGP ID: 2578FCAD ** HAM-RADIO: SQ5JIV * ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Missing serial port after enabling serial console in loader.conf
On Friday, April 15, 2011 1:03:03 pm Przemyslaw Frasunek wrote: > >> sio0: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 flags 0x10 on > >> acpi0 > >> sio0: type 16550A, console > >> sio0: [FILTER] > > Do you have any hints for sio* in /boot/device.hints? > > My /boot/device.hints are unmodified: > > [root@kalina-gw ~]# grep sio /boot/device.hints > hint.sio.0.at="isa" > hint.sio.0.port="0x3F8" > hint.sio.0.flags="0x10" > hint.sio.0.irq="4" > hint.sio.1.at="isa" > hint.sio.1.port="0x2F8" > hint.sio.1.irq="3" > hint.sio.2.at="isa" > hint.sio.2.disabled="1" > hint.sio.2.port="0x3E8" > hint.sio.2.irq="5" > hint.sio.3.at="isa" > hint.sio.3.disabled="1" > hint.sio.3.port="0x2E8" > hint.sio.3.irq="9" Hmm, can you post the output of 'devinfo -vr' and a verbose dmesg at a URL? -- John Baldwin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Missing serial port after enabling serial console in loader.conf
>> sio0: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 flags 0x10 on >> acpi0 >> sio0: type 16550A, console >> sio0: [FILTER] > Do you have any hints for sio* in /boot/device.hints? My /boot/device.hints are unmodified: [root@kalina-gw ~]# grep sio /boot/device.hints hint.sio.0.at="isa" hint.sio.0.port="0x3F8" hint.sio.0.flags="0x10" hint.sio.0.irq="4" hint.sio.1.at="isa" hint.sio.1.port="0x2F8" hint.sio.1.irq="3" hint.sio.2.at="isa" hint.sio.2.disabled="1" hint.sio.2.port="0x3E8" hint.sio.2.irq="5" hint.sio.3.at="isa" hint.sio.3.disabled="1" hint.sio.3.port="0x2E8" hint.sio.3.irq="9" -- * Fido: 2:480/124 ** WWW: http://www.frasunek.com ** NICHDL: PMF9-RIPE * * Jabber ID: veng...@nette.pl ** PGP ID: 2578FCAD ** HAM-RADIO: SQ5JIV * ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Missing serial port after enabling serial console in loader.conf
On Tuesday, April 12, 2011 7:08:22 pm Jeremy Chadwick wrote: > On Tue, Apr 12, 2011 at 11:13:06PM +0200, Pawel Tyll wrote: > > >> P.S. -- What's "BMC" stand for? > > > Baseband Management Controller. It's the separate NIC (sometimes it's > > > piggy-backed on a NIC) used for remote management of motherboards. > > > Usually includes IPMI support. Depending on the motherboard, it may > > > even include support for keyboard/video/mouse redirection and > > > serial-over-lan and all that other remote management stuff. > > > > Actually, the board in reference has built-in BMC; it's IPMI managed > > and when properly configured it allows user to ssh to its IP and > > access things like SOL, chassis power control and other IPMI things > > without any IPMI clients. As to video redirection, there's addon for > > that, built-in BMC doesn't have anything that fancy. And on point, I > > was having similar problems with these boards some time ago, but it > > seems it has been fixed somewhere between 8.1 and 8.2. > > If I remember correctly from following commits, there were changes to > the boot loader pertaining to serial port initialisation. I think I > remember something about certain control bits being set/reset when they > should have been masked out (left alone). > > As I understand it, the serial console capabilities on FreeBSD are > tested predominantly with motherboards that have on-board serial ports. > That is to say, systems with classic/legacy DB9 ports on the board > itself and not via IPMI or out-of-band management modules (re: BMC). > So, one should not be too surprised that there may be "oddities" seen > with those. > > I imagine that UART enumeration/initialisation might differ on such > modules, so this sort of problem doesn't surprise me much. Marcel > Moolenaar (author of uart(4)) probably has better insights. It may be the issue with ACPI enumerating the ports backwards which 8 handles by matching hinted devices based on resources. That has nothing to do with either sio(4) or uart(4) if so. The BMC port usually uses the resources from COM2 by default which our default hints assign to sio1/uart1. -- John Baldwin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Missing serial port after enabling serial console in loader.conf
On Tuesday, April 12, 2011 3:35:11 pm Przemyslaw Frasunek wrote: > Hello, > > I'm struggling with enabling serial console on Intel SR1630GP server > platform and FreeBSD 7.4. > > In default configuration, my serial ports are detected correctly: > > sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on > acpi0 > sio0: type 16550A > sio0: [FILTER] > sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 > sio1: type 16550A > sio1: [FILTER] > > Both serial ports are usable - sio0 is redirected to BMC and sio1 is a > physical port. I can use getty on both ports. > > If I put following statements in /boot/loader.conf: > > boot_multicons="YES" > boot_serial="YES" > console="comconsole,vidconsole" You should just need the one 'console=' line. I tend to put '-Dh' in /boot.config myself to get the boot2 prompt as well. > I have correct output on serial console from loader and booting kernel, > however after kernel is booted, the port is missing. Dmesg shows, that > only one port is being detected, which formerly was sio1: > > sio0: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 flags 0x10 on > acpi0 > sio0: type 16550A, console > sio0: [FILTER] > > Thus, I'm unable to run getty. > > I belive that this issue might be related to ACPI, as similar problem > was already reported in http://markmail.org/message/chu6ilwhsxtarkfm > > Is there any solution to this problem? Do you have any hints for sio* in /boot/device.hints? -- John Baldwin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Missing serial port after enabling serial console in loader.conf
On Tue, Apr 12, 2011 at 11:13:06PM +0200, Pawel Tyll wrote: > >> P.S. -- What's "BMC" stand for? > > Baseband Management Controller. It's the separate NIC (sometimes it's > > piggy-backed on a NIC) used for remote management of motherboards. > > Usually includes IPMI support. Depending on the motherboard, it may > > even include support for keyboard/video/mouse redirection and > > serial-over-lan and all that other remote management stuff. > > Actually, the board in reference has built-in BMC; it's IPMI managed > and when properly configured it allows user to ssh to its IP and > access things like SOL, chassis power control and other IPMI things > without any IPMI clients. As to video redirection, there's addon for > that, built-in BMC doesn't have anything that fancy. And on point, I > was having similar problems with these boards some time ago, but it > seems it has been fixed somewhere between 8.1 and 8.2. If I remember correctly from following commits, there were changes to the boot loader pertaining to serial port initialisation. I think I remember something about certain control bits being set/reset when they should have been masked out (left alone). As I understand it, the serial console capabilities on FreeBSD are tested predominantly with motherboards that have on-board serial ports. That is to say, systems with classic/legacy DB9 ports on the board itself and not via IPMI or out-of-band management modules (re: BMC). So, one should not be too surprised that there may be "oddities" seen with those. I imagine that UART enumeration/initialisation might differ on such modules, so this sort of problem doesn't surprise me much. Marcel Moolenaar (author of uart(4)) probably has better insights. -- | Jeremy Chadwick j...@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Missing serial port after enabling serial console in loader.conf
Hi, >> P.S. -- What's "BMC" stand for? > Baseband Management Controller. It's the separate NIC (sometimes it's > piggy-backed on a NIC) used for remote management of motherboards. > Usually includes IPMI support. Depending on the motherboard, it may > even include support for keyboard/video/mouse redirection and > serial-over-lan and all that other remote management stuff. Actually, the board in reference has built-in BMC; it's IPMI managed and when properly configured it allows user to ssh to its IP and access things like SOL, chassis power control and other IPMI things without any IPMI clients. As to video redirection, there's addon for that, built-in BMC doesn't have anything that fancy. And on point, I was having similar problems with these boards some time ago, but it seems it has been fixed somewhere between 8.1 and 8.2. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Missing serial port after enabling serial console in loader.conf
On Tue, Apr 12, 2011 at 1:49 PM, Jeremy Chadwick wrote: > P.S. -- What's "BMC" stand for? Baseband Management Controller. It's the separate NIC (sometimes it's piggy-backed on a NIC) used for remote management of motherboards. Usually includes IPMI support. Depending on the motherboard, it may even include support for keyboard/video/mouse redirection and serial-over-lan and all that other remote management stuff. -- Freddie Cash fjwc...@gmail.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Missing serial port after enabling serial console in loader.conf
On Tue, Apr 12, 2011 at 09:35:11PM +0200, Przemyslaw Frasunek wrote: > Hello, > > I'm struggling with enabling serial console on Intel SR1630GP server > platform and FreeBSD 7.4. > > In default configuration, my serial ports are detected correctly: > > sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on > acpi0 > sio0: type 16550A > sio0: [FILTER] > sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 > sio1: type 16550A > sio1: [FILTER] > > Both serial ports are usable - sio0 is redirected to BMC and sio1 is a > physical port. I can use getty on both ports. > > If I put following statements in /boot/loader.conf: > > boot_multicons="YES" > boot_serial="YES" > console="comconsole,vidconsole" > > I have correct output on serial console from loader and booting kernel, > however after kernel is booted, the port is missing. Dmesg shows, that > only one port is being detected, which formerly was sio1: > > sio0: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 flags 0x10 on > acpi0 > sio0: type 16550A, console > sio0: [FILTER] > > Thus, I'm unable to run getty. > > I belive that this issue might be related to ACPI, as similar problem > was already reported in http://markmail.org/message/chu6ilwhsxtarkfm > > Is there any solution to this problem? Does the same problem happen on an 8.x branch? sio(4) was deprecated on 8.x with the default becoming uart(4), which "plays nicer" with ACPI. You should be able to download a LiveFS CD image and enter the above 3 commands at the loader prompt manually before doing "boot" to see if it exhibits the same behaviour. P.S. -- What's "BMC" stand for? -- | Jeremy Chadwick j...@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
