Skip to contentSkip to conversation

Serial driver 8250 hangs the kernel with the VIA Nehemiah...

DISCUSSION Chris Pringle 2 participants 3 messages Aug 11, 2006

lore
Share & tools
lore
#0 lore raw
Quoted 8 lines · Alan Cox

Ar Gwe, 2006-08-11 am 09:52 +0100, ysgrifennodd Chris Pringle:

Quoted 3 lines

on it. However, when the port is receiving a lot of data, it has the tendency to either get corrupted data, or to crash the kernel.

What do the crash traces look like

Sorry - the kernel hangs, not crashes. There is no output whatsoever after the hang - SysRq doesn't work, but Numlock does.

Quoted 10 lines
Quoted 6 lines

The "inb" as it is will sometimes return bad data - I'm guessing this is due to ISA bus instability... Anyway I changed it to "inb_p" which cured the corruption problem, but has introduced another issue - it hangs the kernel.

Maybe you need to have a chat with your hardware guys. Certainly if inb_p makes a difference you've got hardware not software side problems.

Perhaps - I'm in discussion with them at the moment, but neither our, nor their department have managed to come up with an answer yet.

Quoted 10 lines
Quoted 5 lines

Interestingly, it only hangs on systems with a VIA Nehemiah CPU, the Intel Celerons seem to work fine. Could this be a problem with writing to that dreaded port 0x080 within inb_p?

Unlikely as it would affect both. More likely would be that the ISA bus clock is generated off the PCI bus clock and you have one of the multipliers wrong or too high for the board.

Thats interesting, but wouldn't this produce strange side affects for the 2.4 kernel as well? 2.4 works fine on both VIAs and Celerons.

Quoted 10 lines
Quoted 5 lines

it only occur on the VIA chip and not the Celeron? I don't think the problem is there when the low latency patches are not applied - so I'm thinking it's probably a timing problem of some sort.

That bit is interesting. Something really off the wall to try - disable interrupts around the inb_p(), especially if you are using pre-emption and let me know what happens.

Quoted 8 lines

Alan

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

I'll give the interrupt disabling a go...

Thanks Alan.
Chris.

Signature · 13 lines
______________________________
Chris Pringle
Software Engineer

Miranda Technologies Ltd.
Hithercroft Road
Wallingford
Oxfordshire OX10 9DG
UK

Tel. +44 1491 820206
Fax. +44 1491 820001
www.miranda.com
#1 lore raw

Ar Gwe, 2006-08-11 am 12:08 +0100, ysgrifennodd Chris Pringle:

Quoted 6 lines
Quoted 4 lines

Unlikely as it would affect both. More likely would be that the ISA bus clock is generated off the PCI bus clock and you have one of the multipliers wrong or too high for the board.

Thats interesting, but wouldn't this produce strange side affects for the 2.4 kernel as well? 2.4 works fine on both VIAs and Celerons.

That I wonder about. The power management stuff and some other things that matter for timing are different however.

Quoted 1 line

I'll give the interrupt disabling a go...

Its just a guess but if you have low latency stuff, you have pre-empt enabled and you actually depend upon the semantics of inb_p/outb_p giving delays reliably then I'm not convinced are guarantees are strong enough

Specifically we don't have any pre-empt protection between the I/O delay and the I/O so we could violate it as we don't have pre-empt disables in inb_p/outb_p and if your CPU context switch is quick enough it could trigger a problem.

Alan

#2 lore raw
Quoted 7 lines · Alan Cox

Ar Gwe, 2006-08-11 am 12:08 +0100, ysgrifennodd Chris Pringle:

Quoted 5 lines
Quoted 5 lines

Unlikely as it would affect both. More likely would be that the ISA bus clock is generated off the PCI bus clock and you have one of the multipliers wrong or too high for the board.

Quoted 6 lines
Quoted 2 lines

Thats interesting, but wouldn't this produce strange side affects for the 2.4 kernel as well? 2.4 works fine on both VIAs and Celerons.

That I wonder about. The power management stuff and some other things that matter for timing are different however.

We don't use any kind of power management (not compiled in) as our systems are always on... Is there any timing related options in the kernel config you'd recommend I look at?

Quoted 14 lines
Quoted 3 lines

I'll give the interrupt disabling a go...

Its just a guess but if you have low latency stuff, you have pre-empt enabled and you actually depend upon the semantics of inb_p/outb_p giving delays reliably then I'm not convinced are guarantees are strong enough

Specifically we don't have any pre-empt protection between the I/O delay and the I/O so we could violate it as we don't have pre-empt disables in inb_p/outb_p and if your CPU context switch is quick enough it could trigger a problem.

Quoted 8 lines

Alan

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Okay, I've tried disabling both preemption and interrupts (separately, and together) and its still hanging...

I've had the Celeron systems being thrashed for well over 4 days now, and they are working fine... Why would the VIA system be any different? They have a slightly different CPU speed (the VIAs are 1000MHz, whereas the Celerons are 850MHz), but I would expect them to be fully compatible otherwise... unless its a microcode bug?

Any more ideas? Do you think writing to port 0x80 could be causing issues?

Thanks,
Chris

Signature · 13 lines
______________________________
Chris Pringle
Software Engineer

Miranda Technologies Ltd.
Hithercroft Road
Wallingford
Oxfordshire OX10 9DG
UK

Tel. +44 1491 820206
Fax. +44 1491 820001
www.miranda.com