Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1505230
| From | Sean Young <sean@mess.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: console issue since 3.6, console=ttyS1 hangs |
| Date | 2016-10-20 22:20 +0200 |
| Message-ID | <surYJ-3VP-27@gated-at.bofh.it> (permalink) |
| References | (3 earlier) <stFKq-4lw-11@gated-at.bofh.it> <stGZP-5pH-5@gated-at.bofh.it> <stIff-6f2-3@gated-at.bofh.it> <su0Fd-2Wq-67@gated-at.bofh.it> <su7nj-7o9-7@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Wed, Oct 19, 2016 at 05:13:41PM -0500, Nathan Zimmer wrote: > On 10/19/2016 04:07 AM, Sean Young wrote: > >So with 3.6.0: > > > >>[ 2.079980] Serial: 8250/16550 driver, 8 ports, IRQ sharing disabled > >>[ 2.100887] serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A > >>[ 2.101715] serial 00:04: unable to assign resources > >>[ 2.102174] serial: probe of 00:04 failed with error -16 > >The pnp probe fails for some reason. I don't understand why. > > > >With 3.7.0: > > > >>[ 2.062700] Serial: 8250/16550 driver, 8 ports, IRQ sharing disabled > >>[ 2.063250] serial 00:04: [io 0x02f8-0x02ff] > >>[ 2.063875] serial 00:04: [irq 12] > >>[ 2.064345] serial 00:04: [dma 18446744073709551615 disabled] > >>[ 2.065540] serial 00:04: activated > >>[ 2.086442] 00:04: ttyS1 at I/O 0x2f8 (irq = 12) is a 16550A > >Now the pnp probe succeeds (with broken irq from pnp). > > > >Can you please check if there is a wrong irq configured in the bios setup > >or if there is a bios update available? I don't know why this worked in > >the first place. > > Apparently this is the latest bios available for these nodes. > Also in the bios setup screens I don't see anything for changing irq numbers > for serial console. > But this is a cluster so sometimes thing get hidden to keep everything > uniform as possible. > > If you want to point me to the pnp probe code you would be suspicious of I > can try to debug and see what is going there. That would be great, thanks. A good start would be to boot 3.6.0 with "loglevel=7 pnp.debug=1" and hopefully that will show why the probe used to fail. Also, does the issue still exist with a more contemporary kernel? Sean
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
console issue since 3.6, console=ttyS1 hangs Nathan Zimmer <nzimmer@sgi.com> - 2016-10-17 17:00 +0200
Re: console issue since 3.6, console=ttyS1 hangs Sean Young <sean@mess.org> - 2016-10-17 17:20 +0200
Re: console issue since 3.6, console=ttyS1 hangs Nathan Zimmer <nzimmer@sgi.com> - 2016-10-17 18:50 +0200
Re: console issue since 3.6, console=ttyS1 hangs Nathan Zimmer <nzimmer@sgi.com> - 2016-10-18 18:50 +0200
Re: console issue since 3.6, console=ttyS1 hangs Sean Young <sean@mess.org> - 2016-10-18 20:10 +0200
Re: console issue since 3.6, console=ttyS1 hangs Sean Young <sean@mess.org> - 2016-10-19 17:10 +0200
Re: console issue since 3.6, console=ttyS1 hangs Nathan Zimmer <nzimmer@sgi.com> - 2016-10-20 00:20 +0200
Re: console issue since 3.6, console=ttyS1 hangs Sean Young <sean@mess.org> - 2016-10-20 22:20 +0200
Re: console issue since 3.6, console=ttyS1 hangs Nathan Zimmer <nzimmer@sgi.com> - 2016-10-21 18:00 +0200
Re: console issue since 3.6, console=ttyS1 hangs Sean Young <sean@mess.org> - 2016-10-24 16:00 +0200
Re: console issue since 3.6, console=ttyS1 hangs Sean Young <sean@mess.org> - 2016-10-25 22:50 +0200
Re: console issue since 3.6, console=ttyS1 hangs Nathan Zimmer <nzimmer@sgi.com> - 2016-10-26 20:20 +0200
csiph-web