ns8250: UART FCR is broken duirng boot OS

Antibiotic

@johnpoz Hello, do you know this error

What it mean, how to resolve?

I have put in system tunable hw.puc.msi_disable=1 as suggest on FreeBSD forum but it does not help!

pfSense 24.03 on custom hardware box!

johnpoz

@Antibiotic I am not familiar with that error.. So this happens on an upgrade of pfsense, after power loss, just reboot because you wanted to reboot? It just crashed on its own and has this error?

The go to guy for that sort of stuff is @stephenw10

Antibiotic

@johnpoz No, its going permanently on each OS boot and nothing more. No any crashing or power loss.

johnpoz

@Antibiotic your system still works right, your just seeing that in the dmesg

Antibiotic

@johnpoz Yes sir)))

Antibiotic

@johnpoz and second error as well: atrtc1: Warning: Couldn't map I/O

johnpoz

@Antibiotic so everything you need is working?

I would expect some errors like that on 3rd party hardware and especially on such a new version of freebsd.. But Steve is the go to guy for anything like this.. Lets see if he notices my page out to him and chimes in.

Antibiotic

@johnpoz said in ns8250: UART FCR is broken duirng boot OS:

I would expect some errors like that on 3rd party hardware and especially on such a new version of freebsd.. But Steve is the go to guy for anything like this.. Lets see if he notices my page out to him and chimes in

Ok will wait

tedquade

@Antibiotic Just Google "ns8250: UART FCR is broken" for lots of information on this matter.

Google is handy for those sorts of questions.

Ted

Gertjan

@tedquade

More Google food here.

JKnott

@Antibiotic said in ns8250: UART FCR is broken duirng boot OS:

ns8250: UART FCR is broken duirng boot OS

What it mean, how to resolve?

WOW!!! There's a blast from the past!
The 8250 was the UART in the original IBM PC. I also designed and built an 8 serial port board for my IMSAI 8080 that used them. The NS refers to National Semiconductor, one of the manufacturers of that chip. In building my board, I discovered a bug that NS didn't know about.

Antibiotic

@JKnott Did you resolve this bug?

fireodo

@Antibiotic

From internet research:

"You can safely ignore the message, and it will
disappear once someone adds the required support to bhyve. We should
probably also have the kernel emit the message only once. I've CC'd
Colin for comment."

(freebsd kernel discussion)

PS. seems that message comes with pfsense 2.7.0 for the first time (freebsd 14 current kernel) (not present in 2.5.2, 2.6.0)

JKnott

@Antibiotic said in ns8250: UART FCR is broken duirng boot OS:

@JKnott Did you resolve this bug?

I created a work around. However, I did let NS know about it.

The 8250 has 3 chip select lines which I used with a 3 bit latch to select the 1 chip of 8 that I wanted to communicate with. Turns out, the chip didn't like that. It wanted at least one of the bits to change when writing to it was completed. Because of that bug, it would continually transmit the same character. I just added a bit more logic, to cause one of the 3 select bits to change. Trivial fix.

Antibiotic

@JKnott said in ns8250: UART FCR is broken duirng boot OS:

. I just added a bit more logic,

What did you add?

JKnott

@Antibiotic said in ns8250: UART FCR is broken duirng boot OS:

What did you add?

I just used a 2 spare NAND gates to toggle one bit on board select.

BTW, this is going back over 40 years to when I did that. The IMSAI was an S-100 bus computer. Various makes of S-100 bus computers were popular in the late 70s, until the IBM PC came out. They were generally used to run the CP/M operating system.

BTW, I built that IMSAI from a kit, which was essentially bags of parts that had to be soldered to the circuit boards and then the system assembled.