Skip to contentSkip to conversation

No serial since kernel 3.8

DISCUSSION Stephan von Krawczynski 6 participants 12 messages Apr 16, 2013 – Apr 20, 2013 ACPI

lore
Share & tools
lore

Stephan von Krawczynski

author
#0 lore raw

Hello,

can some kind soul please explain how I can get my serial port back under kernel 3.8.X. Earlier kernels showed:

Jan 10 13:57:18 mybox kernel: [    0.712829] serial8250: ttyS0 at I/O 0x3f8

(irq = 4) is a 16550A

But 3.8.4:

Mar 26 10:39:14 admin kernel: [    0.603647] serial 00:0a: disabled

Only kernel is replaced, no change in distro
Is there some kernel boot parameter needed now?
I tried 3.4.X and it works, even 3.7.X works...

Signature · 2 lines
Regards,
Stephan
#1 lore raw
Quoted 8 lines · Stephan von Krawczynski

Hello,

can some kind soul please explain how I can get my serial port back under kernel 3.8.X. Earlier kernels showed:

Jan 10 13:57:18 mybox kernel: [    0.712829] serial8250: ttyS0 at I/O 0x3f8

(irq = 4) is a 16550A

Quoted 7 lines

But 3.8.4:

Mar 26 10:39:14 admin kernel: [    0.603647] serial 00:0a: disabled

Only kernel is replaced, no change in distro
Is there some kernel boot parameter needed now?
I tried 3.4.X and it works, even 3.7.X works...

So, 3.8.3 worked and 3.8.4 introduced a regression? If so please confirm.

CC'ing gregkh, just in case...

--
Thanks,
//richard

#2 lore raw
Quoted 14 lines · richard -rw- weinberger
Quoted 12 lines · Stephan von Krawczynski

Hello,

can some kind soul please explain how I can get my serial port back under kernel 3.8.X. Earlier kernels showed:

Jan 10 13:57:18 mybox kernel: [    0.712829] serial8250: ttyS0 at I/O 0x3f8

(irq = 4) is a 16550A

But 3.8.4:

Mar 26 10:39:14 admin kernel: [    0.603647] serial 00:0a: disabled
Quoted 8 lines
Quoted 3 lines

Only kernel is replaced, no change in distro
Is there some kernel boot parameter needed now?
I tried 3.4.X and it works, even 3.7.X works...

So, 3.8.3 worked and 3.8.4 introduced a regression? If so please confirm.

CC'ing gregkh, just in case...

We had a report of this in Fedora that was fixed with 3.8.7. An upstream change had been brought back to the 3.8.x series, and it was subsequently reverted. 3.8.7 picked up the revert.

josh

author
#3 lore raw
Quoted 22 lines · On Tue, 16 Apr 2013 10:59:53 -0400 Josh Boyer <[email protected]> wrote:
Quoted 21 lines · richard -rw- weinberger
Quoted 8 lines · Stephan von Krawczynski

Hello,

can some kind soul please explain how I can get my serial port back under kernel 3.8.X. Earlier kernels showed:

Jan 10 13:57:18 mybox kernel: [    0.712829] serial8250: ttyS0 at I/O 0x3f8

(irq = 4) is a 16550A

Quoted 7 lines

But 3.8.4:

Mar 26 10:39:14 admin kernel: [    0.603647] serial 00:0a: disabled

Only kernel is replaced, no change in distro
Is there some kernel boot parameter needed now?
I tried 3.4.X and it works, even 3.7.X works...

So, 3.8.3 worked and 3.8.4 introduced a regression? If so please confirm.

Quoted 7 lines
Quoted 1 line

CC'ing gregkh, just in case...

We had a report of this in Fedora that was fixed with 3.8.7. An upstream change had been brought back to the 3.8.x series, and it was subsequently reverted. 3.8.7 picked up the revert.

josh

3.8.7 does not work either. I just checked it. I tried shared and not shared IRQ:

Apr 16 17:47:05 mybox kernel: [    0.604826] Serial: 8250/16550 driver, 8 ports, IRQ sharing disabled

and another test:

Apr 16 18:07:08 mybox kernel: [    0.601203] Serial: 8250/16550 driver, 8 ports, IRQ sharing enabled

I must say that 3.8.7 does not even tell the "serial 00:0a: disabled" any more. This is no special board, it is a pretty mainstream asus xeon board with onboard serial. Loading 3.4.24 (just an example) makes the port work immediately.
Anything else I can test?

Signature · 2 lines
Regards,
Stephan
#4 lore raw

[+cc Rafael & linux-acpi]

Quoted 37 lines · Stephan von Krawczynski
Quoted 22 lines · On Tue, 16 Apr 2013 10:59:53 -0400 Josh Boyer <[email protected]> wrote:
Quoted 21 lines · richard -rw- weinberger
Quoted 8 lines · Stephan von Krawczynski

Hello,

can some kind soul please explain how I can get my serial port back under kernel 3.8.X. Earlier kernels showed:

Jan 10 13:57:18 mybox kernel: [    0.712829] serial8250: ttyS0 at I/O 0x3f8

(irq = 4) is a 16550A

Quoted 7 lines

But 3.8.4:

Mar 26 10:39:14 admin kernel: [    0.603647] serial 00:0a: disabled

Only kernel is replaced, no change in distro
Is there some kernel boot parameter needed now?
I tried 3.4.X and it works, even 3.7.X works...

So, 3.8.3 worked and 3.8.4 introduced a regression? If so please confirm.

Quoted 7 lines
Quoted 1 line

CC'ing gregkh, just in case...

We had a report of this in Fedora that was fixed with 3.8.7. An upstream change had been brought back to the 3.8.x series, and it was subsequently reverted. 3.8.7 picked up the revert.

josh

3.8.7 does not work either. I just checked it. I tried shared and not shared IRQ:

Apr 16 17:47:05 mybox kernel: [    0.604826] Serial: 8250/16550 driver, 8 ports, IRQ sharing disabled
Quoted 8 lines

and another test:

Apr 16 18:07:08 mybox kernel: [    0.601203] Serial: 8250/16550 driver, 8 ports, IRQ sharing enabled

I must say that 3.8.7 does not even tell the "serial 00:0a: disabled" any more. This is no special board, it is a pretty mainstream asus xeon board with onboard serial. Loading 3.4.24 (just an example) makes the port work immediately.
Anything else I can test?

3.7.6 works, and 3.8.3, 3.8.4, 3.8.7 all fail. So it looks like a regression between 3.7.6 and 3.8.3.

The "serial 00:0a: disabled" message is from PNP, so I added Rafael and linux-acpi. Complete dmesg logs from 3.7.6 and 3.8.4 would be a place to start. Also maybe an acpidump, since the 00:0a PNP device probably came from PNPACPI. You could attach all these to a
https://bugzilla.kernel.org report if you want a place to stash them.

Josh, do you have a pointer (URL) to the Fedora issue so we can rule that in or out?

Bjorn

#5 lore raw
Quoted 53 lines · Bjorn Helgaas

[+cc Rafael & linux-acpi]

Quoted 37 lines · Stephan von Krawczynski
Quoted 22 lines · On Tue, 16 Apr 2013 10:59:53 -0400 Josh Boyer <[email protected]> wrote:
Quoted 21 lines · richard -rw- weinberger
Quoted 8 lines · Stephan von Krawczynski

Hello,

can some kind soul please explain how I can get my serial port back under kernel 3.8.X. Earlier kernels showed:

Jan 10 13:57:18 mybox kernel: [    0.712829] serial8250: ttyS0 at I/O 0x3f8

(irq = 4) is a 16550A

Quoted 7 lines

But 3.8.4:

Mar 26 10:39:14 admin kernel: [    0.603647] serial 00:0a: disabled

Only kernel is replaced, no change in distro
Is there some kernel boot parameter needed now?
I tried 3.4.X and it works, even 3.7.X works...

So, 3.8.3 worked and 3.8.4 introduced a regression? If so please confirm.

Quoted 7 lines
Quoted 1 line

CC'ing gregkh, just in case...

We had a report of this in Fedora that was fixed with 3.8.7. An upstream change had been brought back to the 3.8.x series, and it was subsequently reverted. 3.8.7 picked up the revert.

josh

3.8.7 does not work either. I just checked it. I tried shared and not shared IRQ:

Apr 16 17:47:05 mybox kernel: [    0.604826] Serial: 8250/16550 driver, 8 ports, IRQ sharing disabled
Quoted 8 lines

and another test:

Apr 16 18:07:08 mybox kernel: [    0.601203] Serial: 8250/16550 driver, 8 ports, IRQ sharing enabled

I must say that 3.8.7 does not even tell the "serial 00:0a: disabled" any more. This is no special board, it is a pretty mainstream asus xeon board with onboard serial. Loading 3.4.24 (just an example) makes the port work immediately.
Anything else I can test?

3.7.6 works, and 3.8.3, 3.8.4, 3.8.7 all fail. So it looks like a regression between 3.7.6 and 3.8.3.

Quoted 8 lines

The "serial 00:0a: disabled" message is from PNP, so I added Rafael and linux-acpi. Complete dmesg logs from 3.7.6 and 3.8.4 would be a place to start. Also maybe an acpidump, since the 00:0a PNP device probably came from PNPACPI. You could attach all these to a
https://bugzilla.kernel.org report if you want a place to stash them.

Josh, do you have a pointer (URL) to the Fedora issue so we can rule that in or out?

https://lkml.org/lkml/2013/4/2/426 is the upstream thread. Seems that was narrowed down to 3.8.4 though, not 3.8.3.

josh

#6 lore raw
In reply to Bjorn Helgaas
Quoted 1 line · Bjorn Helgaas

[+cc Rafael & linux-acpi]

Thanks.

Quoted 51 lines
Quoted 37 lines · Stephan von Krawczynski
Quoted 22 lines · On Tue, 16 Apr 2013 10:59:53 -0400 Josh Boyer <[email protected]> wrote:
Quoted 21 lines · richard -rw- weinberger
Quoted 8 lines · Stephan von Krawczynski

Hello,

can some kind soul please explain how I can get my serial port back under kernel 3.8.X. Earlier kernels showed:

Jan 10 13:57:18 mybox kernel: [    0.712829] serial8250: ttyS0 at I/O 0x3f8

(irq = 4) is a 16550A

Quoted 7 lines

But 3.8.4:

Mar 26 10:39:14 admin kernel: [    0.603647] serial 00:0a: disabled

Only kernel is replaced, no change in distro
Is there some kernel boot parameter needed now?
I tried 3.4.X and it works, even 3.7.X works...

So, 3.8.3 worked and 3.8.4 introduced a regression? If so please confirm.

Quoted 7 lines
Quoted 1 line

CC'ing gregkh, just in case...

We had a report of this in Fedora that was fixed with 3.8.7. An upstream change had been brought back to the 3.8.x series, and it was subsequently reverted. 3.8.7 picked up the revert.

josh

3.8.7 does not work either. I just checked it. I tried shared and not shared IRQ:

Apr 16 17:47:05 mybox kernel: [    0.604826] Serial: 8250/16550 driver, 8 ports, IRQ sharing disabled
Quoted 8 lines

and another test:

Apr 16 18:07:08 mybox kernel: [    0.601203] Serial: 8250/16550 driver, 8 ports, IRQ sharing enabled

I must say that 3.8.7 does not even tell the "serial 00:0a: disabled" any more. This is no special board, it is a pretty mainstream asus xeon board with onboard serial. Loading 3.4.24 (just an example) makes the port work immediately.
Anything else I can test?

3.7.6 works, and 3.8.3, 3.8.4, 3.8.7 all fail. So it looks like a regression between 3.7.6 and 3.8.3.

Quoted 8 lines

The "serial 00:0a: disabled" message is from PNP, so I added Rafael and linux-acpi. Complete dmesg logs from 3.7.6 and 3.8.4 would be a place to start. Also maybe an acpidump, since the 00:0a PNP device probably came from PNPACPI. You could attach all these to a
https://bugzilla.kernel.org report if you want a place to stash them.

Josh, do you have a pointer (URL) to the Fedora issue so we can rule that in or out?

Stephan, below is a list of commits touching the PNP code between 3.7 and 3.8.

Can you please check if any of them has triggered the problem you're seeing?

Rafael

13cde3b PNP: Handle IORESOURCE_BITS in resource allocation
c937766 PNP: Simplify setting of resources
cdc87c5 pnpacpi: fix incorrect TEST_ALPHA() test
a6b5e88 ACPI / PNP: Do not crash due to stale pointer use during system resume 38de279 pnpbios: remove CONFIG_HOTPLUG ifdefs
2905875 ACPI / PNP: skip ACPI device nodes associated with physical nodes already 046d9ce ACPI: Move device resources interpretation code from PNP to ACPI core

Signature · 2 lines
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
author
#7 lore raw
Quoted 72 lines · On Wed, 17 Apr 2013 20:55:04 +0200 "Rafael J. Wysocki" <[email protected]> wrote:
Quoted 1 line · Bjorn Helgaas

[+cc Rafael & linux-acpi]

Thanks.

Quoted 51 lines
Quoted 37 lines · Stephan von Krawczynski
Quoted 22 lines · On Tue, 16 Apr 2013 10:59:53 -0400 Josh Boyer <[email protected]> wrote:
Quoted 21 lines · richard -rw- weinberger
Quoted 8 lines · Stephan von Krawczynski

Hello,

can some kind soul please explain how I can get my serial port back under kernel 3.8.X. Earlier kernels showed:

Jan 10 13:57:18 mybox kernel: [    0.712829] serial8250: ttyS0 at I/O 0x3f8

(irq = 4) is a 16550A

Quoted 7 lines

But 3.8.4:

Mar 26 10:39:14 admin kernel: [    0.603647] serial 00:0a: disabled

Only kernel is replaced, no change in distro
Is there some kernel boot parameter needed now?
I tried 3.4.X and it works, even 3.7.X works...

So, 3.8.3 worked and 3.8.4 introduced a regression? If so please confirm.

Quoted 7 lines
Quoted 1 line

CC'ing gregkh, just in case...

We had a report of this in Fedora that was fixed with 3.8.7. An upstream change had been brought back to the 3.8.x series, and it was subsequently reverted. 3.8.7 picked up the revert.

josh

3.8.7 does not work either. I just checked it. I tried shared and not shared IRQ:

Apr 16 17:47:05 mybox kernel: [    0.604826] Serial: 8250/16550 driver, 8 ports, IRQ sharing disabled
Quoted 8 lines

and another test:

Apr 16 18:07:08 mybox kernel: [    0.601203] Serial: 8250/16550 driver, 8 ports, IRQ sharing enabled

I must say that 3.8.7 does not even tell the "serial 00:0a: disabled" any more. This is no special board, it is a pretty mainstream asus xeon board with onboard serial. Loading 3.4.24 (just an example) makes the port work immediately.
Anything else I can test?

3.7.6 works, and 3.8.3, 3.8.4, 3.8.7 all fail. So it looks like a regression between 3.7.6 and 3.8.3.

Quoted 8 lines

The "serial 00:0a: disabled" message is from PNP, so I added Rafael and linux-acpi. Complete dmesg logs from 3.7.6 and 3.8.4 would be a place to start. Also maybe an acpidump, since the 00:0a PNP device probably came from PNPACPI. You could attach all these to a
https://bugzilla.kernel.org report if you want a place to stash them.

Josh, do you have a pointer (URL) to the Fedora issue so we can rule that in or out?

Stephan, below is a list of commits touching the PNP code between 3.7 and 3.8.

Can you please check if any of them has triggered the problem you're seeing?

Rafael

Quoted 11 lines

13cde3b PNP: Handle IORESOURCE_BITS in resource allocation
c937766 PNP: Simplify setting of resources
cdc87c5 pnpacpi: fix incorrect TEST_ALPHA() test
a6b5e88 ACPI / PNP: Do not crash due to stale pointer use during system resume 38de279 pnpbios: remove CONFIG_HOTPLUG ifdefs
2905875 ACPI / PNP: skip ACPI device nodes associated with physical nodes already 046d9ce ACPI: Move device resources interpretation code from PNP to ACPI core

Signature · 2 lines
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.

Hello all,

I checked 3.8.8 today and it _does_ work.
Shall we burn some time to find out why?
The only significant output difference between working and not working we could find is:

not working:

Apr  2 17:28:23 mybox kernel: [    0.603270] serial 00:0a: disabled

working (3.8.8):

Apr 18 12:58:50 mybox kernel: [    2.855929] 00:0a: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
Signature · 2 lines
Regards,
Stephan
#8 lore raw
Quoted 93 lines · Stephan von Krawczynski
Quoted 72 lines · On Wed, 17 Apr 2013 20:55:04 +0200 "Rafael J. Wysocki" <[email protected]> wrote:
Quoted 1 line · Bjorn Helgaas

[+cc Rafael & linux-acpi]

Thanks.

Quoted 51 lines
Quoted 37 lines · Stephan von Krawczynski
Quoted 22 lines · On Tue, 16 Apr 2013 10:59:53 -0400 Josh Boyer <[email protected]> wrote:
Quoted 21 lines · richard -rw- weinberger
Quoted 8 lines · Stephan von Krawczynski

Hello,

can some kind soul please explain how I can get my serial port back under kernel 3.8.X. Earlier kernels showed:

Jan 10 13:57:18 mybox kernel: [    0.712829] serial8250: ttyS0 at I/O 0x3f8

(irq = 4) is a 16550A

Quoted 7 lines

But 3.8.4:

Mar 26 10:39:14 admin kernel: [    0.603647] serial 00:0a: disabled

Only kernel is replaced, no change in distro
Is there some kernel boot parameter needed now?
I tried 3.4.X and it works, even 3.7.X works...

So, 3.8.3 worked and 3.8.4 introduced a regression? If so please confirm.

Quoted 7 lines
Quoted 1 line

CC'ing gregkh, just in case...

We had a report of this in Fedora that was fixed with 3.8.7. An upstream change had been brought back to the 3.8.x series, and it was subsequently reverted. 3.8.7 picked up the revert.

josh

3.8.7 does not work either. I just checked it. I tried shared and not shared IRQ:

Apr 16 17:47:05 mybox kernel: [    0.604826] Serial: 8250/16550 driver, 8 ports, IRQ sharing disabled
Quoted 8 lines

and another test:

Apr 16 18:07:08 mybox kernel: [    0.601203] Serial: 8250/16550 driver, 8 ports, IRQ sharing enabled

I must say that 3.8.7 does not even tell the "serial 00:0a: disabled" any more. This is no special board, it is a pretty mainstream asus xeon board with onboard serial. Loading 3.4.24 (just an example) makes the port work immediately.
Anything else I can test?

3.7.6 works, and 3.8.3, 3.8.4, 3.8.7 all fail. So it looks like a regression between 3.7.6 and 3.8.3.

Quoted 8 lines

The "serial 00:0a: disabled" message is from PNP, so I added Rafael and linux-acpi. Complete dmesg logs from 3.7.6 and 3.8.4 would be a place to start. Also maybe an acpidump, since the 00:0a PNP device probably came from PNPACPI. You could attach all these to a
https://bugzilla.kernel.org report if you want a place to stash them.

Josh, do you have a pointer (URL) to the Fedora issue so we can rule that in or out?

Stephan, below is a list of commits touching the PNP code between 3.7 and 3.8.

Can you please check if any of them has triggered the problem you're seeing?

Rafael

Quoted 11 lines

13cde3b PNP: Handle IORESOURCE_BITS in resource allocation
c937766 PNP: Simplify setting of resources
cdc87c5 pnpacpi: fix incorrect TEST_ALPHA() test
a6b5e88 ACPI / PNP: Do not crash due to stale pointer use during system resume 38de279 pnpbios: remove CONFIG_HOTPLUG ifdefs
2905875 ACPI / PNP: skip ACPI device nodes associated with physical nodes already 046d9ce ACPI: Move device resources interpretation code from PNP to ACPI core

Signature · 2 lines
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.

Hello all,

I checked 3.8.8 today and it _does_ work.
Shall we burn some time to find out why?
The only significant output difference between working and not working we could find is:

Quoted 5 lines

not working:

Apr  2 17:28:23 mybox kernel: [    0.603270] serial 00:0a: disabled

working (3.8.8):

Apr 18 12:58:50 mybox kernel: [    2.855929] 00:0a: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A

If you are curious, you can run 'git bisect' to figure out the fix, but if you look at the commits in these 3.8.x releases, I think it will be pretty obvious as to what specific patch fixed it :)

Thanks for letting us know,

greg k-h

#9 lore raw
In reply to Stephan von Krawczynski
Quoted 84 lines · Stephan von Krawczynski
Quoted 72 lines · On Wed, 17 Apr 2013 20:55:04 +0200 "Rafael J. Wysocki" <[email protected]> wrote:
Quoted 1 line · Bjorn Helgaas

[+cc Rafael & linux-acpi]

Thanks.

Quoted 51 lines
Quoted 37 lines · Stephan von Krawczynski
Quoted 22 lines · On Tue, 16 Apr 2013 10:59:53 -0400 Josh Boyer <[email protected]> wrote:
Quoted 21 lines · richard -rw- weinberger
Quoted 8 lines · Stephan von Krawczynski

Hello,

can some kind soul please explain how I can get my serial port back under kernel 3.8.X. Earlier kernels showed:

Jan 10 13:57:18 mybox kernel: [    0.712829] serial8250: ttyS0 at I/O 0x3f8

(irq = 4) is a 16550A

Quoted 7 lines

But 3.8.4:

Mar 26 10:39:14 admin kernel: [    0.603647] serial 00:0a: disabled

Only kernel is replaced, no change in distro
Is there some kernel boot parameter needed now?
I tried 3.4.X and it works, even 3.7.X works...

So, 3.8.3 worked and 3.8.4 introduced a regression? If so please confirm.

Quoted 7 lines
Quoted 1 line

CC'ing gregkh, just in case...

We had a report of this in Fedora that was fixed with 3.8.7. An upstream change had been brought back to the 3.8.x series, and it was subsequently reverted. 3.8.7 picked up the revert.

josh

3.8.7 does not work either. I just checked it. I tried shared and not shared IRQ:

Apr 16 17:47:05 mybox kernel: [    0.604826] Serial: 8250/16550 driver, 8 ports, IRQ sharing disabled
Quoted 8 lines

and another test:

Apr 16 18:07:08 mybox kernel: [    0.601203] Serial: 8250/16550 driver, 8 ports, IRQ sharing enabled

I must say that 3.8.7 does not even tell the "serial 00:0a: disabled" any more. This is no special board, it is a pretty mainstream asus xeon board with onboard serial. Loading 3.4.24 (just an example) makes the port work immediately.
Anything else I can test?

3.7.6 works, and 3.8.3, 3.8.4, 3.8.7 all fail. So it looks like a regression between 3.7.6 and 3.8.3.

Quoted 8 lines

The "serial 00:0a: disabled" message is from PNP, so I added Rafael and linux-acpi. Complete dmesg logs from 3.7.6 and 3.8.4 would be a place to start. Also maybe an acpidump, since the 00:0a PNP device probably came from PNPACPI. You could attach all these to a
https://bugzilla.kernel.org report if you want a place to stash them.

Josh, do you have a pointer (URL) to the Fedora issue so we can rule that in or out?

Stephan, below is a list of commits touching the PNP code between 3.7 and 3.8.

Can you please check if any of them has triggered the problem you're seeing?

Rafael

Quoted 8 lines

13cde3b PNP: Handle IORESOURCE_BITS in resource allocation
c937766 PNP: Simplify setting of resources
cdc87c5 pnpacpi: fix incorrect TEST_ALPHA() test
a6b5e88 ACPI / PNP: Do not crash due to stale pointer use during system resume 38de279 pnpbios: remove CONFIG_HOTPLUG ifdefs
2905875 ACPI / PNP: skip ACPI device nodes associated with physical nodes already 046d9ce ACPI: Move device resources interpretation code from PNP to ACPI core

Quoted 3 lines

Hello all,

I checked 3.8.8 today and it _does_ work.

Great!

Quoted 1 line

Shall we burn some time to find out why?

Only if you want to know. :-)

Quoted 7 lines

The only significant output difference between working and not working we could find is:

not working:

Apr  2 17:28:23 mybox kernel: [    0.603270] serial 00:0a: disabled

working (3.8.8):

Apr 18 12:58:50 mybox kernel: [    2.855929] 00:0a: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A

Thanks for the info
Rafael

Signature · 2 lines
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
author
#10 lore raw
In reply to richard -rw- weinberger
Quoted 14 lines · On Tue, 16 Apr 2013 16:55:25 +0200 richard -rw- weinberger…
Quoted 12 lines · Stephan von Krawczynski

Hello,

can some kind soul please explain how I can get my serial port back under kernel 3.8.X. Earlier kernels showed:

Jan 10 13:57:18 mybox kernel: [    0.712829] serial8250: ttyS0 at I/O 0x3f8

(irq = 4) is a 16550A

But 3.8.4:

Mar 26 10:39:14 admin kernel: [    0.603647] serial 00:0a: disabled
Quoted 8 lines
Quoted 3 lines

Only kernel is replaced, no change in distro
Is there some kernel boot parameter needed now?
I tried 3.4.X and it works, even 3.7.X works...

So, 3.8.3 worked and 3.8.4 introduced a regression? If so please confirm.

CC'ing gregkh, just in case...

No, neither 3.8.4 nor 3.8.3 worked. The last working version I know for sure is 3.7.6
FYI: I don't load serial as a module

Signature · 2 lines
Regards,
Stephan
#11 lore raw
Quoted 21 lines · Stephan von Krawczynski
Quoted 18 lines · On Tue, 16 Apr 2013 16:55:25 +0200 richard -rw- weinberger…
Quoted 15 lines · Stephan von Krawczynski

Hello,

can some kind soul please explain how I can get my serial port back under kernel 3.8.X. Earlier kernels showed:

Jan 10 13:57:18 mybox kernel: [    0.712829] serial8250: ttyS0 at I/O 0x3f8

(irq = 4) is a 16550A

But 3.8.4:

Mar 26 10:39:14 admin kernel: [    0.603647] serial 00:0a: disabled

Only kernel is replaced, no change in distro
Is there some kernel boot parameter needed now?
I tried 3.4.X and it works, even 3.7.X works...

Quoted 7 lines
Quoted 4 lines

So, 3.8.3 worked and 3.8.4 introduced a regression? If so please confirm.

CC'ing gregkh, just in case...

No, neither 3.8.4 nor 3.8.3 worked. The last working version I know for sure is 3.7.6
FYI: I don't load serial as a module

Can you run 'git bisect' between those kernels to track down the offending commit?

thanks,

greg k-h