search for: serial8250

...re a ribon cable to the external DB9 connectors in the case. I tested 5 cables, but none works. whereas I'm not sure if it is a cable problem. this is what dmesg says when booting (with 2 onboard ports). OS is Centos 5.3: Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A 00:03: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A 00:04: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A Linux helios 2.6.18-128.2.1.el5 #1 SMP Tue Jul 14 06:39:56 EDT 2009 i686 i686 i386 GNU/Linux - the dealer...

...550A ACPI: PCI Interrupt 0000:01:0a.1[A] -> GSI 16 (level, low) -> IRQ 233 ttyS6 at I/O 0xcc00 (irq = 233) is a 16550A ttyS7 at I/O 0xc880 (irq = 233) is a 16550A With the 64-bit kernel (2.6.18-164.el5 [x86_64]) I get: Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A 00:0a: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 19 ACPI: PCI Interrupt 0000:01:0a.0[A] -> Link [LNKC] -> GSI 19 (level, low) -> IRQ 177 0000:01:0a....

I recently bought a new UPS, and I''m attempting to use nut to monitor it. Following setup instructions everything seemed to go well until it came to testing the connection, which failed. There is just one serial connector on the computer, so I set it to monitor /dev/ttyS0. Either that is wrong, or communication is failing. I''ve been told to try minicom to monitor it,

...sg reports ttyS0 as the active port: [root at zabackup01 ~]# dmesg |grep tty Bootdata ok (command line is ro root=/dev/System/root rhgb quiet xencons=tty6) Kernel command line: ro root=/dev/System/root rhgb quiet xencons=tty6 WARNING: Failed to register Xen virtual console driver as 'tty1' serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A 00:06: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A ttyS0: 1 input overrun(s) ttyS0: 1 input overrun(s) running screen /dev/ttyS0 doesn't show up anything, and I should at least get the switch's login prompt. -- Kind Regards Rudi Ahlers

...1407 2006-05-15 20:26 upsd.conf -rw-r----- 1 root nut 2391 2006-05-15 20:34 upsd.users jason@ubuntu:~$ sudo cat /etc/nut/ups.conf [...] user = nut [mge] driver = mge-shut port = /dev/ttyS1 desc = "MGE Pulsar Ellipse UPS" jason@ubuntu:~$ dmesg | grep -i ttyS [42949378.240000] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A [42949378.240000] serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A [42949378.250000] 00:09: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A [42949378.250000] 00:0a: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A I have also tried/used "port = /dev/ttyS0"...

I installed CentOS 6 on a Dell Optiplex 790 with a StarTech.com dual serial port card, and the serial ports aren't being recognized. According to dmesg, only the built-in serial port is being recognized: # dmesg | fgrep ttyS serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A 00:08: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A And lspci -v doesn't show that any drivers are loaded for it: # lspci -v [snip] 03:00.0 Serial controller: NetMos Technology PCIe 9922 Multi-I/O Controller (prog-if 02 [16550]) Subsystem: Device...

Hello, I just discovered a strange bug with serial passthrough in xen 4.1 on Debian Wheezy. The Dom0 has a GSM modem connected to serial port. The serial port is passed through to a DomU with options 'irq = [ 4 ]' and 'ioports = [ '3f8-3ff ]'. This worked as expected on Debian Squeeze with Xen 4.0 and Linux kernel 2.6.32 (both for Dom0 and DomU). On Debian Wheezy with Xen

Hello, I just discovered a strange bug with serial passthrough in xen 4.1 on Debian Wheezy. The Dom0 has a GSM modem connected to serial port. The serial port is passed through to a DomU with options 'irq = [ 4 ]' and 'ioports = [ '3f8-3ff ]'. This worked as expected on Debian Squeeze with Xen 4.0 and Linux kernel 2.6.32 (both for Dom0 and DomU). On Debian Wheezy with Xen

..._mode Found MSI capability Allocate Port Service[0000:00:0f.0:pcie00] pci_hotplug: PCI Hot Plug PCI Core version: 0.5 Real Time Clock Driver v1.12ac Non-volatile memory driver v1.2 Linux agpgart interface v0.101 (c) Dave Jones Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A 00:05: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A 00:06: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize Uniform Multi-Platform E-IDE driver R...

...9;ttyS0': device_add [ 268.629209] bus: 'acpi': add driver battery [ 268.679377] driver: '00:05': driver_bound: bound to device 'serial' [ 268.689946] bus: 'pnp': really_probe: bound device 00:05 to driver serial [ 268.703123] Registering platform device 'serial8250'. Parent at platform [ 268.710751] device: 'serial8250': device_add [ 268.712216] bus: 'platform': add device serial8250 [ 268.743291] device: 'ttyS1': device_add [ 268.809001] device: 'ttyS2': device_add [ 268.858752] device: 'ttyS3': device_add [...

...9;ttyS0': device_add [ 268.629209] bus: 'acpi': add driver battery [ 268.679377] driver: '00:05': driver_bound: bound to device 'serial' [ 268.689946] bus: 'pnp': really_probe: bound device 00:05 to driver serial [ 268.703123] Registering platform device 'serial8250'. Parent at platform [ 268.710751] device: 'serial8250': device_add [ 268.712216] bus: 'platform': add device serial8250 [ 268.743291] device: 'ttyS1': device_add [ 268.809001] device: 'ttyS2': device_add [ 268.858752] device: 'ttyS3': device_add [...

Hello Can anyone share a known working config for xen which would transfer a serial interface ( add-on card preferably, mine uses e880-e887 : 0000:03:05.0 / ec00-ec07 : 0000:03:05.0 ) to a DomU ? I've been trying with the stock packages from Centos 5.5 ( fully updated) and also with gitco's 3.4.3 but after 2 days of googling and testing we still fail to access the serial

At the risk of angering the crash Gods, my sustem has NOT crashed again since I downgraded the kernel from 2.6.18-1.2239.fc5 to 2.6.18-1.2200.fc5. Given that newfound stability, and my lack of time, I'm going to put on hold any further diagnostics, until the next kernel revision is released. I have submitted a report at bugzilla.redhat.com (bug 218128). (Ah, nuts; accidentally created a

...: 0.5 ACPI: duty_cycle spans bit 4 ACPI: CPU0 (power states: C1[C1] C2[C2] C3[C3]) Real Time Clock Driver v1.12ac hpet_resources: 0xfed00000 is busy Non-volatile memory driver v1.2 Linux agpgart interface v0.101 (c) Dave Jones Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A 00:05: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A 00:06: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A brd: module loaded Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 ide: Assuming 33MHz system bus s...

...Express Hot Plug Controller Driver version: 0.4 acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5 pci-stub: invalid id string "" Non-volatile memory driver v1.3 Linux agpgart interface v0.103 crash memory driver: version 1.0 Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A serial8250: ttyS2 at I/O 0x3e8 (irq = 5) is a 16550A brd: module loaded loop: module loaded input: Macintosh mouse button emulation as /devices/virtual/input/input0 Fixed MDIO Bus: probed ehci_hcd: USB 2....

Maybe that is https://reviews.llvm.org/D30171. On Mon, Feb 20, 2017 at 11:16 PM, Dmitry Golovin <dima at golovin.in> wrote: > Hi, > > I can't build the Linux kernel anymore. With the latest kernel source and > latest LLVM and LLD (with D30163) I can only get this error message when > linking vmlinux: > > ld.lld: error: unable to move location counter backward >

...ACPI: Power Button [PWRB] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1 ACPI: Power Button [PWRF] ACPI: duty_cycle spans bit 4 Real Time Clock Driver v1.12b Non-volatile memory driver v1.3 Linux agpgart interface v0.103 Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A 00:05: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A 00:06: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A brd: module loaded loop: module loaded drbd: initialized. Version: 8.3.7 (api:88/proto:86-92) drbd: built-in...

...isapnp: No Plug & Play device found Non-volatile memory driver v1.3 Linux agpgart interface v0.103 agpgart-intel 0000:00:00.0: Intel i845 Chipset agpgart-intel 0000:00:00.0: AGP aperture is 64M @ 0xf0000000 crash memory driver: version 1.1 Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A 00:07: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A 00:08: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A brd: module loaded loop: module loaded input: Macintosh mouse button emulation as /devices/virtual/input/inp...

...PCI Hot Plug PCI Core version: 0.5 [??? 1.194608] pciehp: PCI Express Hot Plug Controller Driver version: 0.4 [??? 1.208324] isapnp: Scanning for PnP cards... [??? 1.485622] isapnp: No Plug & Play device found [??? 1.495148] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled [??? 1.504771] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A [??? 1.541453] brd: module loaded [??? 1.557973] loop: module loaded [??? 1.578621] scsi0 : ata_piix [??? 1.581302] scsi1 : ata_piix [??? 1.588164] ata1: PATA max MWDMA2 cmd 0x1f0 ctl 0x3f6 bmdma 0xc000 irq 14 [??? 1.590866] ata2: PATA max MWDMA2 cmd 0x170...

Hi there, I''m using the Suse Enterprise 10 RC2 along with Xen 3.0.2 on X86-64 and I''m experiencing a problem with the network. I boot into the Xen kernel and everything works just fine. I can browse the net etc. However after a while the network stops responding completely. I am not sure what causes this to happen or what triggers it. After a few hours, the network just stops