I am surprised the importance of this bug is only medium. A lot of
important devices stopped working for us - contactless card readers
(ACR120), USB scanners (Canon LIDE models)... Thankfully, kernel 3.16
really does fix the issue.
For us, the bug manifested in kernels 3.2, 3.11, 3.13 using Intel
I've since upgraded to Ubuntu Gnome 14.10 running kernel 3.16 and the
bug is no longer present so somewhere between 3.13.0.40 and 3.16 the
module was fixed.
** Changed in: linux (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of
@apw
Can someone explain to me or point me to a guide that shows how to take
the change that apw presented in post #40 and apply it to the latest
ubuntu kernel release?
Thanks,
Hans
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Tested with kernel
linux-image-3.13.0-25-generic_3.13.0-25.47lp1313981v201405131449_amd64.deb
and real serial gadget connected to /dev/ttyS0. The serial line works OK.
Had to use PS2 keyboard. The test kernel did not recognize USB mouse and
keyboard.
dmesg.txt attached
** Attachment added: dmesg
The serial io still disabled in 3.13.0.-29 ubuntu.
Works OK on old hardware with old BIOS, same kernel.
See attached dmesg
Any comments will be welcomed
** Attachment added: dmesg.txt
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1313981/+attachment/4128823/+files/dmesg.txt
--
You
Jun 9 18:07:33 ASUS kernel: [0.771626] Serial: 8250/16550 driver, 32
ports, IRQ sharing enabled
Jun 9 18:07:33 ASUS kernel: [0.771793] serial 00:0a: disabled
14.04
jardag@ASUS:/var/log$ uname -r
3.13.0-29-generic
--
You received this bug notification because you are a member of Kernel
Jun 9 16:58:39 OldBox kernel: [0.694048] Serial: 8250/16550 driver, 32
ports, IRQ sharing enabled
Jun 9 16:58:39 OldBox kernel: [0.714453] 00:05: ttyS0 at I/O 0x3f8 (irq =
4, base_baud = 115200) is a 16550A
jardag@OldBox:/var/log$ uname -r
3.13.0-29-generic
jardag@OldBox:/var/log$
--
Is this enough testing for the kernel team to get a fix commited in a
future release?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1313981
Title:
Kernel disabling serial port ttyS0 on
Ok, yet another test kernel based on the debug in the previous one. If
you could do the do and report back here please:
http://people.canonical.com/~apw/lp1313981-trusty/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Bingo!
I have an enabled serial port with this kernel! dmesg attached.
** Attachment added: dmesggood.txt
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1313981/+attachment/4111810/+files/dmesggood.txt
--
You received this bug notification because you are a member of Kernel
So, there was a massive config shuffle between -19 and -20, but this is
a complete diff of the amd64-generic kernel's configs between those
versions, and nothing obvious jumps out at me.
** Patch added: config.19-20.diff
@Hans109h -- in that range was one interesting looking commit, i have
reverted that for testing and also added some more targetted debugging.
Could you test the latest kernel at the URL below and get a dmesg as
before:
http://people.canonical.com/~apw/lp1313981-trusty/
Please report any
@apw this test was bad, dmesg below:
** Attachment added: 3.13.0-25dmesg.txt
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1313981/+attachment/4110632/+files/3.13.0-25dmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
@apw forgot to mention this last kernel again killed my mouse and
keyboard upon boot.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1313981
Title:
Kernel disabling serial port ttyS0 on
@apw nevermind about mouse and keyboard. I forgot to install header and
once I did that they worked. Still no serial port in this test, but
below is an updated dmesg.
** Attachment added: 051214dmesg.txt
I am unable to compile the kernels to do further bisecting. :-(
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1313981
Title:
Kernel disabling serial port ttyS0 on boot
Status in
@apw
Any ideas on the no device error?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1313981
Title:
Kernel disabling serial port ttyS0 on boot
Status in “linux” package in Ubuntu:
** Tags added: latest-bios-2104 regression-release
** Tags added: needs-bisect
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1313981
Title:
Kernel disabling serial port ttyS0 on boot
I am in the process of trying to bisect the kernel, however what I load
any kernel prior to 3.13.0-24 I lose my mouse and keyboard (and I think
all USB functionality) halfway through the boot.
If anyone can point me in the right direction.
--
You received this bug notification because you
The problem is between 3.13.0-19.40 and 3.13.0-20.41.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1313981
Title:
Kernel disabling serial port ttyS0 on boot
Status in “linux”
@Hans109h -- ok so that shows this was a probe failure:
[0.596333] APW: pnp_device_probe: serial serial 00:0a
[0.596352] APW: pnp_device_probe: serial serial 00:0a probe failed
Nothing seems to have changed since saucy in the driver in question!?
So, I've added additional debug
[0.310505] APW: pnp_device_probe: system system 00:00
[0.310631] APW: pnp_device_probe: system system 00:04
[0.310693] APW: pnp_device_probe: system system 00:06
[0.310750] APW: pnp_device_probe: system system 00:07
[0.310790] APW: pnp_device_probe: system system 00:08
[
Ok that does not really tell us anything more. So, debug time. Could
you test the kernel below, you can run it in the 13.10 userspace no
problem. Could you boot this kernel and get a dmesg output from it
(which should contain additional info on why it fails). Kernels are at
the URL below:
Here it is.
Thanks for looking into this.
** Attachment added: dmesg for 3.13 kernel
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1313981/+attachment/4103727/+files/dmesg3-13.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
** Description changed:
On boot in 13.10 kern.log would state:
- Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
- 00:0a: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
+ Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
+ 00:0a: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
@Hans109h -- had a poke about and the message I am looking for is too
short to find trivially, without knowledge of which device you have
here. So could we get a boot dmesg and /proc/modules output from the
machine running 13.10 which does attach the driver properly to the
serial device.
--
You
Ok this disabled message very likely is coming from pnp_stop_dev(),
and most probabally coming from a probe failure in pnp_device_probe().
This implies we can either not match the device to any driver, or the
probe itself failed for some reason, the lack of any error between the
two quoted lines
** Attachment added: boot dmesg
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1313981/+attachment/4102321/+files/dmesg
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1313981
** Attachment added: /proc/modules
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1313981/+attachment/4102322/+files/proc_modules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Attachment added: lspci -nnvv output
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1313981/+attachment/4102323/+files/lspci.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Attachment added: lsmod
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1313981/+attachment/4102324/+files/lsmod.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1313981
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.15 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix
Because I require the serial port in production I downgraded to 13.10
and all testing I do will be through a live usb boot. Assuming I can
figure out how to customize the live usb to use the mainstream kernel I
will test it.
Thanks,
Hans
--
You received this bug notification because you are a
kernel-unable-to-test-upstream
system froze at loading initial ramdisk on boot
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
For what it's worth, I was able to boot with mainline v3.14.1-trusty
kernel: bug still existed.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1313981
Title:
Kernel disabling serial
35 matches
Mail list logo
