Search results for query "Linux ./configure"

6358 messages

[Arm-dev] [PATCH] add QDF2432 support

by Christopher Covington

Backport UART and GIC related patches, enabling the CentOS 7.2 AltArch kernel to run on the Qualcomm Technologies QDF2432 server development platform. Signed-off-by: Christopher Covington <cov(a)codeaurora.org> --- ...mba-pl011-add-register-accessor-functions.patch | 718 +++++++++++++++++++++ ...011-convert-accessor-functions-to-take-ua.patch | 709 ++++++++++++++++++++ ...011-add-support-for-32-bit-register-acces.patch | 79 +++ ...011-use-iotype-instead-of-access_32b-to-t.patch | 119 ++++ ...a-pl011-Use-32-bit-accesses-for-SBSA-UART.patch | 29 + ...4006-irqchip-Fully-support-ACPI-GICv3-ITS.patch | 49 ++ ...-add-support-for-extended-IRQ-to-PCI-link.patch | 113 ++++ ...-v3-ACPI-Add-redistributor-support-via-GI.patch | 68 ++ SPECS/kernel-aarch64.spec | 25 +- 9 files changed, 1908 insertions(+), 1 deletion(-) create mode 100644 SOURCES/4001-tty-amba-pl011-add-register-accessor-functions.patch create mode 100644 SOURCES/4002-tty-amba-pl011-convert-accessor-functions-to-take-ua.patch create mode 100644 SOURCES/4003-tty-amba-pl011-add-support-for-32-bit-register-acces.patch create mode 100644 SOURCES/4004-tty-amba-pl011-use-iotype-instead-of-access_32b-to-t.patch create mode 100644 SOURCES/4005-tty-amba-pl011-Use-32-bit-accesses-for-SBSA-UART.patch create mode 100644 SOURCES/4006-irqchip-Fully-support-ACPI-GICv3-ITS.patch create mode 100644 SOURCES/4007-acpi-add-support-for-extended-IRQ-to-PCI-link.patch create mode 100644 SOURCES/4008-irqchip-gic-v3-ACPI-Add-redistributor-support-via-GI.patch diff --git a/SOURCES/4001-tty-amba-pl011-add-register-accessor-functions.patch b/SOURCES/4001-tty-amba-pl011-add-register-accessor-functions.patch new file mode 100644 index 0000000..6fb4d0e --- /dev/null +++ b/SOURCES/4001-tty-amba-pl011-add-register-accessor-functions.patch @@ -0,0 +1,718 @@ +From: Russell King <rmk+kernel(a)arm.linux.org.uk> +Date: Tue, 3 Nov 2015 14:50:58 +0000 +Subject: tty: amba-pl011: add register accessor functions + +Add register accessor functions to amba-pl011. Much of this +transformation was done using the sed expression below, with any +left-overs fixed up manually afterwards, and code formatted to remain +within coding style. + +s/readw($uap->port.membase\|regs\|port->membase$ +/pl011_read(\1,/g +s/writew($.*$ +/pl011_write(\1,/g + +Signed-off-by: Russell King <rmk+kernel(a)arm.linux.org.uk> +Reviewed-by: Peter Hurley <peter(a)hurleysoftware.com> +Signed-off-by: Greg Kroah-Hartman <gregkh(a)linuxfoundation.org> + +Git-commit: 7583633921d54f33e96b65569a0c980ae1d05dba +Git-repo: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git +--- + drivers/tty/serial/amba-pl011.c | 210 +++++++++++++++++++++------------------- + 1 file changed, 112 insertions(+), 98 deletions(-) + +diff --git a/drivers/tty/serial/amba-pl011.c b/drivers/tty/serial/amba-pl011.c +index fd27e98..b75f750 100644 +--- a/drivers/tty/serial/amba-pl011.c ++++ b/drivers/tty/serial/amba-pl011.c +@@ -184,6 +184,16 @@ struct uart_amba_port { + #endif + }; + ++static unsigned int pl011_read(void __iomem *base, unsigned int reg) ++{ ++ return readw(base + reg); ++} ++ ++static void pl011_write(unsigned int val, void __iomem *base, unsigned int reg) ++{ ++ writew(val, base + reg); ++} ++ + /* + * Reads up to 256 characters from the FIFO or until it's empty and + * inserts them into the TTY layer. Returns the number of characters +@@ -196,12 +206,12 @@ static int pl011_fifo_to_tty(struct uart_amba_port *uap) + int fifotaken = 0; + + while (max_count--) { +- status = readw(uap->port.membase + UART01x_FR); ++ status = pl011_read(uap->port.membase, UART01x_FR); + if (status & UART01x_FR_RXFE) + break; + + /* Take chars from the FIFO and update status */ +- ch = readw(uap->port.membase + UART01x_DR) | ++ ch = pl011_read(uap->port.membase, UART01x_DR) | + UART_DUMMY_DR_RX; + flag = TTY_NORMAL; + uap->port.icount.rx++; +@@ -438,7 +448,7 @@ static void pl011_dma_tx_callback(void *data) + + dmacr = uap->dmacr; + uap->dmacr = dmacr & ~UART011_TXDMAE; +- writew(uap->dmacr, uap->port.membase + UART011_DMACR); ++ pl011_write(uap->dmacr, uap->port.membase, UART011_DMACR); + + /* + * If TX DMA was disabled, it means that we've stopped the DMA for +@@ -552,7 +562,7 @@ static int pl011_dma_tx_refill(struct uart_amba_port *uap) + dma_dev->device_issue_pending(chan); + + uap->dmacr |= UART011_TXDMAE; +- writew(uap->dmacr, uap->port.membase + UART011_DMACR); ++ pl011_write(uap->dmacr, uap->port.membase, UART011_DMACR); + uap->dmatx.queued = true; + + /* +@@ -588,9 +598,9 @@ static bool pl011_dma_tx_irq(struct uart_amba_port *uap) + */ + if (uap->dmatx.queued) { + uap->dmacr |= UART011_TXDMAE; +- writew(uap->dmacr, uap->port.membase + UART011_DMACR); ++ pl011_write(uap->dmacr, uap->port.membase, UART011_DMACR); + uap->im &= ~UART011_TXIM; +- writew(uap->im, uap->port.membase + UART011_IMSC); ++ pl011_write(uap->im, uap->port.membase, UART011_IMSC); + return true; + } + +@@ -600,7 +610,7 @@ static bool pl011_dma_tx_irq(struct uart_amba_port *uap) + */ + if (pl011_dma_tx_refill(uap) > 0) { + uap->im &= ~UART011_TXIM; +- writew(uap->im, uap->port.membase + UART011_IMSC); ++ pl011_write(uap->im, uap->port.membase, UART011_IMSC); + return true; + } + return false; +@@ -614,7 +624,7 @@ static inline void pl011_dma_tx_stop(struct uart_amba_port *uap) + { + if (uap->dmatx.queued) { + uap->dmacr &= ~UART011_TXDMAE; +- writew(uap->dmacr, uap->port.membase + UART011_DMACR); ++ pl011_write(uap->dmacr, uap->port.membase, UART011_DMACR); + } + } + +@@ -640,14 +650,14 @@ static inline bool pl011_dma_tx_start(struct uart_amba_port *uap) + if (!uap->dmatx.queued) { + if (pl011_dma_tx_refill(uap) > 0) { + uap->im &= ~UART011_TXIM; +- writew(uap->im, uap->port.membase + +- UART011_IMSC); ++ pl011_write(uap->im, uap->port.membase, ++ UART011_IMSC); + } else + ret = false; + } else if (!(uap->dmacr & UART011_TXDMAE)) { + uap->dmacr |= UART011_TXDMAE; +- writew(uap->dmacr, +- uap->port.membase + UART011_DMACR); ++ pl011_write(uap->dmacr, uap->port.membase, ++ UART011_DMACR); + } + return ret; + } +@@ -658,9 +668,9 @@ static inline bool pl011_dma_tx_start(struct uart_amba_port *uap) + */ + dmacr = uap->dmacr; + uap->dmacr &= ~UART011_TXDMAE; +- writew(uap->dmacr, uap->port.membase + UART011_DMACR); ++ pl011_write(uap->dmacr, uap->port.membase, UART011_DMACR); + +- if (readw(uap->port.membase + UART01x_FR) & UART01x_FR_TXFF) { ++ if (pl011_read(uap->port.membase, UART01x_FR) & UART01x_FR_TXFF) { + /* + * No space in the FIFO, so enable the transmit interrupt + * so we know when there is space. Note that once we've +@@ -669,13 +679,13 @@ static inline bool pl011_dma_tx_start(struct uart_amba_port *uap) + return false; + } + +- writew(uap->port.x_char, uap->port.membase + UART01x_DR); ++ pl011_write(uap->port.x_char, uap->port.membase, UART01x_DR); + uap->port.icount.tx++; + uap->port.x_char = 0; + + /* Success - restore the DMA state */ + uap->dmacr = dmacr; +- writew(dmacr, uap->port.membase + UART011_DMACR); ++ pl011_write(dmacr, uap->port.membase, UART011_DMACR); + + return true; + } +@@ -703,7 +713,7 @@ __acquires(&uap->port.lock) + DMA_TO_DEVICE); + uap->dmatx.queued = false; + uap->dmacr &= ~UART011_TXDMAE; +- writew(uap->dmacr, uap->port.membase + UART011_DMACR); ++ pl011_write(uap->dmacr, uap->port.membase, UART011_DMACR); + } + } + +@@ -743,11 +753,11 @@ static int pl011_dma_rx_trigger_dma(struct uart_amba_port *uap) + dma_async_issue_pending(rxchan); + + uap->dmacr |= UART011_RXDMAE; +- writew(uap->dmacr, uap->port.membase + UART011_DMACR); ++ pl011_write(uap->dmacr, uap->port.membase, UART011_DMACR); + uap->dmarx.running = true; + + uap->im &= ~UART011_RXIM; +- writew(uap->im, uap->port.membase + UART011_IMSC); ++ pl011_write(uap->im, uap->port.membase, UART011_IMSC); + + return 0; + } +@@ -805,8 +815,8 @@ static void pl011_dma_rx_chars(struct uart_amba_port *uap, + */ + if (dma_count == pending && readfifo) { + /* Clear any error flags */ +- writew(UART011_OEIS | UART011_BEIS | UART011_PEIS | UART011_FEIS, +- uap->port.membase + UART011_ICR); ++ pl011_write(UART011_OEIS | UART011_BEIS | UART011_PEIS | ++ UART011_FEIS, uap->port.membase, UART011_ICR); + + /* + * If we read all the DMA'd characters, and we had an +@@ -854,7 +864,7 @@ static void pl011_dma_rx_irq(struct uart_amba_port *uap) + + /* Disable RX DMA - incoming data will wait in the FIFO */ + uap->dmacr &= ~UART011_RXDMAE; +- writew(uap->dmacr, uap->port.membase + UART011_DMACR); ++ pl011_write(uap->dmacr, uap->port.membase, UART011_DMACR); + uap->dmarx.running = false; + + pending = sgbuf->sg.length - state.residue; +@@ -874,7 +884,7 @@ static void pl011_dma_rx_irq(struct uart_amba_port *uap) + dev_dbg(uap->port.dev, "could not retrigger RX DMA job " + "fall back to interrupt mode\n"); + uap->im |= UART011_RXIM; +- writew(uap->im, uap->port.membase + UART011_IMSC); ++ pl011_write(uap->im, uap->port.membase, UART011_IMSC); + } + } + +@@ -922,7 +932,7 @@ static void pl011_dma_rx_callback(void *data) + dev_dbg(uap->port.dev, "could not retrigger RX DMA job " + "fall back to interrupt mode\n"); + uap->im |= UART011_RXIM; +- writew(uap->im, uap->port.membase + UART011_IMSC); ++ pl011_write(uap->im, uap->port.membase, UART011_IMSC); + } + } + +@@ -935,7 +945,7 @@ static inline void pl011_dma_rx_stop(struct uart_amba_port *uap) + { + /* FIXME. Just disable the DMA enable */ + uap->dmacr &= ~UART011_RXDMAE; +- writew(uap->dmacr, uap->port.membase + UART011_DMACR); ++ pl011_write(uap->dmacr, uap->port.membase, UART011_DMACR); + } + + /* +@@ -979,7 +989,7 @@ static void pl011_dma_rx_poll(unsigned long args) + spin_lock_irqsave(&uap->port.lock, flags); + pl011_dma_rx_stop(uap); + uap->im |= UART011_RXIM; +- writew(uap->im, uap->port.membase + UART011_IMSC); ++ pl011_write(uap->im, uap->port.membase, UART011_IMSC); + spin_unlock_irqrestore(&uap->port.lock, flags); + + uap->dmarx.running = false; +@@ -1041,7 +1051,7 @@ static void pl011_dma_startup(struct uart_amba_port *uap) + skip_rx: + /* Turn on DMA error (RX/TX will be enabled on demand) */ + uap->dmacr |= UART011_DMAONERR; +- writew(uap->dmacr, uap->port.membase + UART011_DMACR); ++ pl011_write(uap->dmacr, uap->port.membase, UART011_DMACR); + + /* + * ST Micro variants has some specific dma burst threshold +@@ -1049,8 +1059,8 @@ skip_rx: + * be issued above/below 16 bytes. + */ + if (uap->vendor->dma_threshold) +- writew(ST_UART011_DMAWM_RX_16 | ST_UART011_DMAWM_TX_16, +- uap->port.membase + ST_UART011_DMAWM); ++ pl011_write(ST_UART011_DMAWM_RX_16 | ST_UART011_DMAWM_TX_16, ++ uap->port.membase, ST_UART011_DMAWM); + + if (uap->using_rx_dma) { + if (pl011_dma_rx_trigger_dma(uap)) +@@ -1075,12 +1085,12 @@ static void pl011_dma_shutdown(struct uart_amba_port *uap) + return; + + /* Disable RX and TX DMA */ +- while (readw(uap->port.membase + UART01x_FR) & UART01x_FR_BUSY) ++ while (pl011_read(uap->port.membase, UART01x_FR) & UART01x_FR_BUSY) + barrier(); + + spin_lock_irq(&uap->port.lock); + uap->dmacr &= ~(UART011_DMAONERR | UART011_RXDMAE | UART011_TXDMAE); +- writew(uap->dmacr, uap->port.membase + UART011_DMACR); ++ pl011_write(uap->dmacr, uap->port.membase, UART011_DMACR); + spin_unlock_irq(&uap->port.lock); + + if (uap->using_tx_dma) { +@@ -1181,7 +1191,7 @@ static void pl011_stop_tx(struct uart_port *port) + container_of(port, struct uart_amba_port, port); + + uap->im &= ~UART011_TXIM; +- writew(uap->im, uap->port.membase + UART011_IMSC); ++ pl011_write(uap->im, uap->port.membase, UART011_IMSC); + pl011_dma_tx_stop(uap); + } + +@@ -1191,7 +1201,7 @@ static void pl011_tx_chars(struct uart_amba_port *uap, bool from_irq); + static void pl011_start_tx_pio(struct uart_amba_port *uap) + { + uap->im |= UART011_TXIM; +- writew(uap->im, uap->port.membase + UART011_IMSC); ++ pl011_write(uap->im, uap->port.membase, UART011_IMSC); + pl011_tx_chars(uap, false); + } + +@@ -1211,7 +1221,7 @@ static void pl011_stop_rx(struct uart_port *port) + + uap->im &= ~(UART011_RXIM|UART011_RTIM|UART011_FEIM| + UART011_PEIM|UART011_BEIM|UART011_OEIM); +- writew(uap->im, uap->port.membase + UART011_IMSC); ++ pl011_write(uap->im, uap->port.membase, UART011_IMSC); + + pl011_dma_rx_stop(uap); + } +@@ -1222,7 +1232,7 @@ static void pl011_enable_ms(struct uart_port *port) + container_of(port, struct uart_amba_port, port); + + uap->im |= UART011_RIMIM|UART011_CTSMIM|UART011_DCDMIM|UART011_DSRMIM; +- writew(uap->im, uap->port.membase + UART011_IMSC); ++ pl011_write(uap->im, uap->port.membase, UART011_IMSC); + } + + static void pl011_rx_chars(struct uart_amba_port *uap) +@@ -1242,7 +1252,7 @@ __acquires(&uap->port.lock) + dev_dbg(uap->port.dev, "could not trigger RX DMA job " + "fall back to interrupt mode again\n"); + uap->im |= UART011_RXIM; +- writew(uap->im, uap->port.membase + UART011_IMSC); ++ pl011_write(uap->im, uap->port.membase, UART011_IMSC); + } else { + #ifdef CONFIG_DMA_ENGINE + /* Start Rx DMA poll */ +@@ -1263,10 +1273,10 @@ static bool pl011_tx_char(struct uart_amba_port *uap, unsigned char c, + bool from_irq) + { + if (unlikely(!from_irq) && +- readw(uap->port.membase + UART01x_FR) & UART01x_FR_TXFF) ++ pl011_read(uap->port.membase, UART01x_FR) & UART01x_FR_TXFF) + return false; /* unable to transmit character */ + +- writew(c, uap->port.membase + UART01x_DR); ++ pl011_write(c, uap->port.membase, UART01x_DR); + uap->port.icount.tx++; + + return true; +@@ -1313,7 +1323,8 @@ static void pl011_modem_status(struct uart_amba_port *uap) + { + unsigned int status, delta; + +- status = readw(uap->port.membase + UART01x_FR) & UART01x_FR_MODEM_ANY; ++ status = pl011_read(uap->port.membase, UART01x_FR); ++ status &= UART01x_FR_MODEM_ANY; + + delta = status ^ uap->old_status; + uap->old_status = status; +@@ -1341,15 +1352,15 @@ static void check_apply_cts_event_workaround(struct uart_amba_port *uap) + return; + + /* workaround to make sure that all bits are unlocked.. */ +- writew(0x00, uap->port.membase + UART011_ICR); ++ pl011_write(0x00, uap->port.membase, UART011_ICR); + + /* + * WA: introduce 26ns(1 uart clk) delay before W1C; + * single apb access will incur 2 pclk(133.12Mhz) delay, + * so add 2 dummy reads + */ +- dummy_read = readw(uap->port.membase + UART011_ICR); +- dummy_read = readw(uap->port.membase + UART011_ICR); ++ dummy_read = pl011_read(uap->port.membase, UART011_ICR); ++ dummy_read = pl011_read(uap->port.membase, UART011_ICR); + } + + static irqreturn_t pl011_int(int irq, void *dev_id) +@@ -1361,15 +1372,15 @@ static irqreturn_t pl011_int(int irq, void *dev_id) + int handled = 0; + + spin_lock_irqsave(&uap->port.lock, flags); +- imsc = readw(uap->port.membase + UART011_IMSC); +- status = readw(uap->port.membase + UART011_RIS) & imsc; ++ imsc = pl011_read(uap->port.membase, UART011_IMSC); ++ status = pl011_read(uap->port.membase, UART011_RIS) & imsc; + if (status) { + do { + check_apply_cts_event_workaround(uap); + +- writew(status & ~(UART011_TXIS|UART011_RTIS| +- UART011_RXIS), +- uap->port.membase + UART011_ICR); ++ pl011_write(status & ~(UART011_TXIS|UART011_RTIS| ++ UART011_RXIS), ++ uap->port.membase, UART011_ICR); + + if (status & (UART011_RTIS|UART011_RXIS)) { + if (pl011_dma_rx_running(uap)) +@@ -1386,7 +1397,7 @@ static irqreturn_t pl011_int(int irq, void *dev_id) + if (pass_counter-- == 0) + break; + +- status = readw(uap->port.membase + UART011_RIS) & imsc; ++ status = pl011_read(uap->port.membase, UART011_RIS) & imsc; + } while (status != 0); + handled = 1; + } +@@ -1400,7 +1411,7 @@ static unsigned int pl011_tx_empty(struct uart_port *port) + { + struct uart_amba_port *uap = + container_of(port, struct uart_amba_port, port); +- unsigned int status = readw(uap->port.membase + UART01x_FR); ++ unsigned int status = pl011_read(uap->port.membase, UART01x_FR); + return status & (UART01x_FR_BUSY|UART01x_FR_TXFF) ? 0 : TIOCSER_TEMT; + } + +@@ -1409,7 +1420,7 @@ static unsigned int pl011_get_mctrl(struct uart_port *port) + struct uart_amba_port *uap = + container_of(port, struct uart_amba_port, port); + unsigned int result = 0; +- unsigned int status = readw(uap->port.membase + UART01x_FR); ++ unsigned int status = pl011_read(uap->port.membase, UART01x_FR); + + #define TIOCMBIT(uartbit, tiocmbit) \ + if (status & uartbit) \ +@@ -1429,7 +1440,7 @@ static void pl011_set_mctrl(struct uart_port *port, unsigned int mctrl) + container_of(port, struct uart_amba_port, port); + unsigned int cr; + +- cr = readw(uap->port.membase + UART011_CR); ++ cr = pl011_read(uap->port.membase, UART011_CR); + + #define TIOCMBIT(tiocmbit, uartbit) \ + if (mctrl & tiocmbit) \ +@@ -1449,7 +1460,7 @@ static void pl011_set_mctrl(struct uart_port *port, unsigned int mctrl) + } + #undef TIOCMBIT + +- writew(cr, uap->port.membase + UART011_CR); ++ pl011_write(cr, uap->port.membase, UART011_CR); + } + + static void pl011_break_ctl(struct uart_port *port, int break_state) +@@ -1460,12 +1471,12 @@ static void pl011_break_ctl(struct uart_port *port, int break_state) + unsigned int lcr_h; + + spin_lock_irqsave(&uap->port.lock, flags); +- lcr_h = readw(uap->port.membase + uap->lcrh_tx); ++ lcr_h = pl011_read(uap->port.membase, uap->lcrh_tx); + if (break_state == -1) + lcr_h |= UART01x_LCRH_BRK; + else + lcr_h &= ~UART01x_LCRH_BRK; +- writew(lcr_h, uap->port.membase + uap->lcrh_tx); ++ pl011_write(lcr_h, uap->port.membase, uap->lcrh_tx); + spin_unlock_irqrestore(&uap->port.lock, flags); + } + +@@ -1477,7 +1488,7 @@ static void pl011_quiesce_irqs(struct uart_port *port) + container_of(port, struct uart_amba_port, port); + unsigned char __iomem *regs = uap->port.membase; + +- writew(readw(regs + UART011_MIS), regs + UART011_ICR); ++ pl011_write(pl011_read(regs, UART011_MIS), regs, UART011_ICR); + /* + * There is no way to clear TXIM as this is "ready to transmit IRQ", so + * we simply mask it. start_tx() will unmask it. +@@ -1491,7 +1502,8 @@ static void pl011_quiesce_irqs(struct uart_port *port) + * (including tx queue), so we're also fine with start_tx()'s caller + * side. + */ +- writew(readw(regs + UART011_IMSC) & ~UART011_TXIM, regs + UART011_IMSC); ++ pl011_write(pl011_read(regs, UART011_IMSC) & ~UART011_TXIM, ++ regs, UART011_IMSC); + } + + static int pl011_get_poll_char(struct uart_port *port) +@@ -1506,11 +1518,11 @@ static int pl011_get_poll_char(struct uart_port *port) + */ + pl011_quiesce_irqs(port); + +- status = readw(uap->port.membase + UART01x_FR); ++ status = pl011_read(uap->port.membase, UART01x_FR); + if (status & UART01x_FR_RXFE) + return NO_POLL_CHAR; + +- return readw(uap->port.membase + UART01x_DR); ++ return pl011_read(uap->port.membase, UART01x_DR); + } + + static void pl011_put_poll_char(struct uart_port *port, +@@ -1519,10 +1531,10 @@ static void pl011_put_poll_char(struct uart_port *port, + struct uart_amba_port *uap = + container_of(port, struct uart_amba_port, port); + +- while (readw(uap->port.membase + UART01x_FR) & UART01x_FR_TXFF) ++ while (pl011_read(uap->port.membase, UART01x_FR) & UART01x_FR_TXFF) + barrier(); + +- writew(ch, uap->port.membase + UART01x_DR); ++ pl011_write(ch, uap->port.membase, UART01x_DR); + } + + #endif /* CONFIG_CONSOLE_POLL */ +@@ -1546,15 +1558,17 @@ static int pl011_hwinit(struct uart_port *port) + uap->port.uartclk = clk_get_rate(uap->clk); + + /* Clear pending error and receive interrupts */ +- writew(UART011_OEIS | UART011_BEIS | UART011_PEIS | UART011_FEIS | +- UART011_RTIS | UART011_RXIS, uap->port.membase + UART011_ICR); ++ pl011_write(UART011_OEIS | UART011_BEIS | UART011_PEIS | ++ UART011_FEIS | UART011_RTIS | UART011_RXIS, ++ uap->port.membase, UART011_ICR); + + /* + * Save interrupts enable mask, and enable RX interrupts in case if + * the interrupt is used for NMI entry. + */ +- uap->im = readw(uap->port.membase + UART011_IMSC); +- writew(UART011_RTIM | UART011_RXIM, uap->port.membase + UART011_IMSC); ++ uap->im = pl011_read(uap->port.membase, UART011_IMSC); ++ pl011_write(UART011_RTIM | UART011_RXIM, uap->port.membase, ++ UART011_IMSC); + + if (dev_get_platdata(uap->port.dev)) { + struct amba_pl011_data *plat; +@@ -1568,7 +1582,7 @@ static int pl011_hwinit(struct uart_port *port) + + static void pl011_write_lcr_h(struct uart_amba_port *uap, unsigned int lcr_h) + { +- writew(lcr_h, uap->port.membase + uap->lcrh_rx); ++ pl011_write(lcr_h, uap->port.membase, uap->lcrh_rx); + if (uap->lcrh_rx != uap->lcrh_tx) { + int i; + /* +@@ -1576,14 +1590,14 @@ static void pl011_write_lcr_h(struct uart_amba_port *uap, unsigned int lcr_h) + * to get this delay write read only register 10 times + */ + for (i = 0; i < 10; ++i) +- writew(0xff, uap->port.membase + UART011_MIS); +- writew(lcr_h, uap->port.membase + uap->lcrh_tx); ++ pl011_write(0xff, uap->port.membase, UART011_MIS); ++ pl011_write(lcr_h, uap->port.membase, uap->lcrh_tx); + } + } + + static int pl011_allocate_irq(struct uart_amba_port *uap) + { +- writew(uap->im, uap->port.membase + UART011_IMSC); ++ pl011_write(uap->im, uap->port.membase, UART011_IMSC); + + return request_irq(uap->port.irq, pl011_int, 0, "uart-pl011", uap); + } +@@ -1598,12 +1612,12 @@ static void pl011_enable_interrupts(struct uart_amba_port *uap) + spin_lock_irq(&uap->port.lock); + + /* Clear out any spuriously appearing RX interrupts */ +- writew(UART011_RTIS | UART011_RXIS, +- uap->port.membase + UART011_ICR); ++ pl011_write(UART011_RTIS | UART011_RXIS, uap->port.membase, ++ UART011_ICR); + uap->im = UART011_RTIM; + if (!pl011_dma_rx_running(uap)) + uap->im |= UART011_RXIM; +- writew(uap->im, uap->port.membase + UART011_IMSC); ++ pl011_write(uap->im, uap->port.membase, UART011_IMSC); + spin_unlock_irq(&uap->port.lock); + } + +@@ -1622,21 +1636,21 @@ static int pl011_startup(struct uart_port *port) + if (retval) + goto clk_dis; + +- writew(uap->vendor->ifls, uap->port.membase + UART011_IFLS); ++ pl011_write(uap->vendor->ifls, uap->port.membase, UART011_IFLS); + + spin_lock_irq(&uap->port.lock); + + /* restore RTS and DTR */ + cr = uap->old_cr & (UART011_CR_RTS | UART011_CR_DTR); + cr |= UART01x_CR_UARTEN | UART011_CR_RXE | UART011_CR_TXE; +- writew(cr, uap->port.membase + UART011_CR); ++ pl011_write(cr, uap->port.membase, UART011_CR); + + spin_unlock_irq(&uap->port.lock); + + /* + * initialise the old status of the modem signals + */ +- uap->old_status = readw(uap->port.membase + UART01x_FR) & UART01x_FR_MODEM_ANY; ++ uap->old_status = pl011_read(uap->port.membase, UART01x_FR) & UART01x_FR_MODEM_ANY; + + /* Startup DMA */ + pl011_dma_startup(uap); +@@ -1677,9 +1691,9 @@ static void pl011_shutdown_channel(struct uart_amba_port *uap, + { + unsigned long val; + +- val = readw(uap->port.membase + lcrh); ++ val = pl011_read(uap->port.membase, lcrh); + val &= ~(UART01x_LCRH_BRK | UART01x_LCRH_FEN); +- writew(val, uap->port.membase + lcrh); ++ pl011_write(val, uap->port.membase, lcrh); + } + + /* +@@ -1693,11 +1707,11 @@ static void pl011_disable_uart(struct uart_amba_port *uap) + + uap->autorts = false; + spin_lock_irq(&uap->port.lock); +- cr = readw(uap->port.membase + UART011_CR); ++ cr = pl011_read(uap->port.membase, UART011_CR); + uap->old_cr = cr; + cr &= UART011_CR_RTS | UART011_CR_DTR; + cr |= UART01x_CR_UARTEN | UART011_CR_TXE; +- writew(cr, uap->port.membase + UART011_CR); ++ pl011_write(cr, uap->port.membase, UART011_CR); + spin_unlock_irq(&uap->port.lock); + + /* +@@ -1714,8 +1728,8 @@ static void pl011_disable_interrupts(struct uart_amba_port *uap) + + /* mask all interrupts and clear all pending ones */ + uap->im = 0; +- writew(uap->im, uap->port.membase + UART011_IMSC); +- writew(0xffff, uap->port.membase + UART011_ICR); ++ pl011_write(uap->im, uap->port.membase, UART011_IMSC); ++ pl011_write(0xffff, uap->port.membase, UART011_ICR); + + spin_unlock_irq(&uap->port.lock); + } +@@ -1867,8 +1881,8 @@ pl011_set_termios(struct uart_port *port, struct ktermios *termios, + pl011_enable_ms(port); + + /* first, disable everything */ +- old_cr = readw(port->membase + UART011_CR); +- writew(0, port->membase + UART011_CR); ++ old_cr = pl011_read(port->membase, UART011_CR); ++ pl011_write(0, port->membase, UART011_CR); + + if (termios->c_cflag & CRTSCTS) { + if (old_cr & UART011_CR_RTS) +@@ -1901,8 +1915,8 @@ pl011_set_termios(struct uart_port *port, struct ktermios *termios, + quot -= 2; + } + /* Set baud rate */ +- writew(quot & 0x3f, port->membase + UART011_FBRD); +- writew(quot >> 6, port->membase + UART011_IBRD); ++ pl011_write(quot & 0x3f, port->membase, UART011_FBRD); ++ pl011_write(quot >> 6, port->membase, UART011_IBRD); + + /* + * ----------v----------v----------v----------v----- +@@ -1911,7 +1925,7 @@ pl011_set_termios(struct uart_port *port, struct ktermios *termios, + * ----------^----------^----------^----------^----- + */ + pl011_write_lcr_h(uap, lcr_h); +- writew(old_cr, port->membase + UART011_CR); ++ pl011_write(old_cr, port->membase, UART011_CR); + + spin_unlock_irqrestore(&port->lock, flags); + } +@@ -2052,9 +2066,9 @@ static void pl011_console_putchar(struct uart_port *port, int ch) + struct uart_amba_port *uap = + container_of(port, struct uart_amba_port, port); + +- while (readw(uap->port.membase + UART01x_FR) & UART01x_FR_TXFF) ++ while (pl011_read(uap->port.membase, UART01x_FR) & UART01x_FR_TXFF) + barrier(); +- writew(ch, uap->port.membase + UART01x_DR); ++ pl011_write(ch, uap->port.membase, UART01x_DR); + } + + static void +@@ -2079,10 +2093,10 @@ pl011_console_write(struct console *co, const char *s, unsigned int count) + * First save the CR then disable the interrupts + */ + if (!uap->vendor->always_enabled) { +- old_cr = readw(uap->port.membase + UART011_CR); ++ old_cr = pl011_read(uap->port.membase, UART011_CR); + new_cr = old_cr & ~UART011_CR_CTSEN; + new_cr |= UART01x_CR_UARTEN | UART011_CR_TXE; +- writew(new_cr, uap->port.membase + UART011_CR); ++ pl011_write(new_cr, uap->port.membase, UART011_CR); + } + + uart_console_write(&uap->port, s, count, pl011_console_putchar); +@@ -2092,10 +2106,10 @@ pl011_console_write(struct console *co, const char *s, unsigned int count) + * and restore the TCR + */ + do { +- status = readw(uap->port.membase + UART01x_FR); ++ status = pl011_read(uap->port.membase, UART01x_FR); + } while (status & UART01x_FR_BUSY); + if (!uap->vendor->always_enabled) +- writew(old_cr, uap->port.membase + UART011_CR); ++ pl011_write(old_cr, uap->port.membase, UART011_CR); + + if (locked) + spin_unlock(&uap->port.lock); +@@ -2108,10 +2122,10 @@ static void __init + pl011_console_get_options(struct uart_amba_port *uap, int *baud, + int *parity, int *bits) + { +- if (readw(uap->port.membase + UART011_CR) & UART01x_CR_UARTEN) { ++ if (pl011_read(uap->port.membase, UART011_CR) & UART01x_CR_UARTEN) { + unsigned int lcr_h, ibrd, fbrd; + +- lcr_h = readw(uap->port.membase + uap->lcrh_tx); ++ lcr_h = pl011_read(uap->port.membase, uap->lcrh_tx); + + *parity = 'n'; + if (lcr_h & UART01x_LCRH_PEN) { +@@ -2126,13 +2140,13 @@ pl011_console_get_options(struct uart_amba_port *uap, int *baud, + else + *bits = 8; + +- ibrd = readw(uap->port.membase + UART011_IBRD); +- fbrd = readw(uap->port.membase + UART011_FBRD); ++ ibrd = pl011_read(uap->port.membase, UART011_IBRD); ++ fbrd = pl011_read(uap->port.membase, UART011_FBRD); + + *baud = uap->port.uartclk * 4 / (64 * ibrd + fbrd); + + if (uap->vendor->oversampling) { +- if (readw(uap->port.membase + UART011_CR) ++ if (pl011_read(uap->port.membase, UART011_CR) + & ST_UART011_CR_OVSFACT) + *baud *= 2; + } +@@ -2334,8 +2348,8 @@ static int pl011_register_port(struct uart_amba_port *uap) + int ret; + + /* Ensure interrupts from this UART are masked and cleared */ +- writew(0, uap->port.membase + UART011_IMSC); +- writew(0xffff, uap->port.membase + UART011_ICR); ++ pl011_write(0, uap->port.membase, UART011_IMSC); ++ pl011_write(0xffff, uap->port.membase, UART011_ICR); + + if (!amba_reg.state) { + ret = uart_register_driver(&amba_reg); diff --git a/SOURCES/4002-tty-amba-pl011-convert-accessor-functions-to-take-ua.patch b/SOURCES/4002-tty-amba-pl011-convert-accessor-functions-to-take-ua.patch new file mode 100644 index 0000000..6524bda --- /dev/null +++ b/SOURCES/4002-tty-amba-pl011-convert-accessor-functions-to-take-ua.patch @@ -0,0 +1,709 @@ +From: Russell King <rmk+kernel(a)arm.linux.org.uk> +Date: Tue, 3 Nov 2015 14:51:03 +0000 +Subject: tty: amba-pl011: convert accessor functions to take uart_amba_port + +Convert the new accessor functions to take the uart_amba_port instead +of the port base address. + +Signed-off-by: Russell King <rmk+kernel(a)arm.linux.org.uk> +Reviewed-by: Peter Hurley <peter(a)hurleysoftware.com> +Signed-off-by: Greg Kroah-Hartman <gregkh(a)linuxfoundation.org> + +Git-commit: b2a4e24c2efd76a2c25478836fb35951e00d5b52 +Git-repo: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git +--- + drivers/tty/serial/amba-pl011.c | 199 ++++++++++++++++++++-------------------- + 1 file changed, 97 insertions(+), 102 deletions(-) + +diff --git a/drivers/tty/serial/amba-pl011.c b/drivers/tty/serial/amba-pl011.c +index b75f750..61512af 100644 +--- a/drivers/tty/serial/amba-pl011.c ++++ b/drivers/tty/serial/amba-pl011.c +@@ -184,14 +184,16 @@ struct uart_amba_port { + #endif + }; + +-static unsigned int pl011_read(void __iomem *base, unsigned int reg) ++static unsigned int pl011_read(const struct uart_amba_port *uap, ++ unsigned int reg) + { +- return readw(base + reg); ++ return readw(uap->port.membase + reg); + } + +-static void pl011_write(unsigned int val, void __iomem *base, unsigned int reg) ++static void pl011_write(unsigned int val, const struct uart_amba_port *uap, ++ unsigned int reg) + { +- writew(val, base + reg); ++ writew(val, uap->port.membase + reg); + } + + /* +@@ -206,13 +208,12 @@ static int pl011_fifo_to_tty(struct uart_amba_port *uap) + int fifotaken = 0; + + while (max_count--) { +- status = pl011_read(uap->port.membase, UART01x_FR); ++ status = pl011_read(uap, UART01x_FR); + if (status & UART01x_FR_RXFE) + break; + + /* Take chars from the FIFO and update status */ +- ch = pl011_read(uap->port.membase, UART01x_DR) | +- UART_DUMMY_DR_RX; ++ ch = pl011_read(uap, UART01x_DR) | UART_DUMMY_DR_RX; + flag = TTY_NORMAL; + uap->port.icount.rx++; + fifotaken++; +@@ -448,7 +449,7 @@ static void pl011_dma_tx_callback(void *data) + + dmacr = uap->dmacr; + uap->dmacr = dmacr & ~UART011_TXDMAE; +- pl011_write(uap->dmacr, uap->port.membase, UART011_DMACR); ++ pl011_write(uap->dmacr, uap, UART011_DMACR); + + /* + * If TX DMA was disabled, it means that we've stopped the DMA for +@@ -562,7 +563,7 @@ static int pl011_dma_tx_refill(struct uart_amba_port *uap) + dma_dev->device_issue_pending(chan); + + uap->dmacr |= UART011_TXDMAE; +- pl011_write(uap->dmacr, uap->port.membase, UART011_DMACR); ++ pl011_write(uap->dmacr, uap, UART011_DMACR); + uap->dmatx.queued = true; + + /* +@@ -598,9 +599,9 @@ static bool pl011_dma_tx_irq(struct uart_amba_port *uap) + */ + if (uap->dmatx.queued) { + uap->dmacr |= UART011_TXDMAE; +- pl011_write(uap->dmacr, uap->port.membase, UART011_DMACR); ++ pl011_write(uap->dmacr, uap, UART011_DMACR); + uap->im &= ~UART011_TXIM; +- pl011_write(uap->im, uap->port.membase, UART011_IMSC); ++ pl011_write(uap->im, uap, UART011_IMSC); + return true; + } + +@@ -610,7 +611,7 @@ static bool pl011_dma_tx_irq(struct uart_amba_port *uap) + */ + if (pl011_dma_tx_refill(uap) > 0) { + uap->im &= ~UART011_TXIM; +- pl011_write(uap->im, uap->port.membase, UART011_IMSC); ++ pl011_write(uap->im, uap, UART011_IMSC); + return true; + } + return false; +@@ -624,7 +625,7 @@ static inline void pl011_dma_tx_stop(struct uart_amba_port *uap) + { + if (uap->dmatx.queued) { + uap->dmacr &= ~UART011_TXDMAE; +- pl011_write(uap->dmacr, uap->port.membase, UART011_DMACR); ++ pl011_write(uap->dmacr, uap, UART011_DMACR); + } + } + +@@ -650,14 +651,12 @@ static inline bool pl011_dma_tx_start(struct uart_amba_port *uap) + if (!uap->dmatx.queued) { + if (pl011_dma_tx_refill(uap) > 0) { + uap->im &= ~UART011_TXIM; +- pl011_write(uap->im, uap->port.membase, +- UART011_IMSC); ++ pl011_write(uap->im, uap, UART011_IMSC); + } else + ret = false; + } else if (!(uap->dmacr & UART011_TXDMAE)) { + uap->dmacr |= UART011_TXDMAE; +- pl011_write(uap->dmacr, uap->port.membase, +- UART011_DMACR); ++ pl011_write(uap->dmacr, uap, UART011_DMACR); + } + return ret; + } +@@ -668,9 +667,9 @@ static inline bool pl011_dma_tx_start(struct uart_amba_port *uap) + */ + dmacr = uap->dmacr; + uap->dmacr &= ~UART011_TXDMAE; +- pl011_write(uap->dmacr, uap->port.membase, UART011_DMACR); ++ pl011_write(uap->dmacr, uap, UART011_DMACR); + +- if (pl011_read(uap->port.membase, UART01x_FR) & UART01x_FR_TXFF) { ++ if (pl011_read(uap, UART01x_FR) & UART01x_FR_TXFF) { + /* + * No space in the FIFO, so enable the transmit interrupt + * so we know when there is space. Note that once we've +@@ -679,13 +678,13 @@ static inline bool pl011_dma_tx_start(struct uart_amba_port *uap) + return false; + } + +- pl011_write(uap->port.x_char, uap->port.membase, UART01x_DR); ++ pl011_write(uap->port.x_char, uap, UART01x_DR); + uap->port.icount.tx++; + uap->port.x_char = 0; + + /* Success - restore the DMA state */ + uap->dmacr = dmacr; +- pl011_write(dmacr, uap->port.membase, UART011_DMACR); ++ pl011_write(dmacr, uap, UART011_DMACR); + + return true; + } +@@ -713,7 +712,7 @@ __acquires(&uap->port.lock) + DMA_TO_DEVICE); + uap->dmatx.queued = false; + uap->dmacr &= ~UART011_TXDMAE; +- pl011_write(uap->dmacr, uap->port.membase, UART011_DMACR); ++ pl011_write(uap->dmacr, uap, UART011_DMACR); + } + } + +@@ -753,11 +752,11 @@ static int pl011_dma_rx_trigger_dma(struct uart_amba_port *uap) + dma_async_issue_pending(rxchan); + + uap->dmacr |= UART011_RXDMAE; +- pl011_write(uap->dmacr, uap->port.membase, UART011_DMACR); ++ pl011_write(uap->dmacr, uap, UART011_DMACR); + uap->dmarx.running = true; + + uap->im &= ~UART011_RXIM; +- pl011_write(uap->im, uap->port.membase, UART011_IMSC); ++ pl011_write(uap->im, uap, UART011_IMSC); + + return 0; + } +@@ -816,7 +815,7 @@ static void pl011_dma_rx_chars(struct uart_amba_port *uap, + if (dma_count == pending && readfifo) { + /* Clear any error flags */ + pl011_write(UART011_OEIS | UART011_BEIS | UART011_PEIS | +- UART011_FEIS, uap->port.membase, UART011_ICR); ++ UART011_FEIS, uap, UART011_ICR); + + /* + * If we read all the DMA'd characters, and we had an +@@ -864,7 +863,7 @@ static void pl011_dma_rx_irq(struct uart_amba_port *uap) + + /* Disable RX DMA - incoming data will wait in the FIFO */ + uap->dmacr &= ~UART011_RXDMAE; +- pl011_write(uap->dmacr, uap->port.membase, UART011_DMACR); ++ pl011_write(uap->dmacr, uap, UART011_DMACR); + uap->dmarx.running = false; + + pending = sgbuf->sg.length - state.residue; +@@ -884,7 +883,7 @@ static void pl011_dma_rx_irq(struct uart_amba_port *uap) + dev_dbg(uap->port.dev, "could not retrigger RX DMA job " + "fall back to interrupt mode\n"); + uap->im |= UART011_RXIM; +- pl011_write(uap->im, uap->port.membase, UART011_IMSC); ++ pl011_write(uap->im, uap, UART011_IMSC); + } + } + +@@ -932,7 +931,7 @@ static void pl011_dma_rx_callback(void *data) + dev_dbg(uap->port.dev, "could not retrigger RX DMA job " + "fall back to interrupt mode\n"); + uap->im |= UART011_RXIM; +- pl011_write(uap->im, uap->port.membase, UART011_IMSC); ++ pl011_write(uap->im, uap, UART011_IMSC); + } + } + +@@ -945,7 +944,7 @@ static inline void pl011_dma_rx_stop(struct uart_amba_port *uap) + { + /* FIXME. Just disable the DMA enable */ + uap->dmacr &= ~UART011_RXDMAE; +- pl011_write(uap->dmacr, uap->port.membase, UART011_DMACR); ++ pl011_write(uap->dmacr, uap, UART011_DMACR); + } + + /* +@@ -989,7 +988,7 @@ static void pl011_dma_rx_poll(unsigned long args) + spin_lock_irqsave(&uap->port.lock, flags); + pl011_dma_rx_stop(uap); + uap->im |= UART011_RXIM; +- pl011_write(uap->im, uap->port.membase, UART011_IMSC); ++ pl011_write(uap->im, uap, UART011_IMSC); + spin_unlock_irqrestore(&uap->port.lock, flags); + + uap->dmarx.running = false; +@@ -1051,7 +1050,7 @@ static void pl011_dma_startup(struct uart_amba_port *uap) + skip_rx: + /* Turn on DMA error (RX/TX will be enabled on demand) */ + uap->dmacr |= UART011_DMAONERR; +- pl011_write(uap->dmacr, uap->port.membase, UART011_DMACR); ++ pl011_write(uap->dmacr, uap, UART011_DMACR); + + /* + * ST Micro variants has some specific dma burst threshold +@@ -1060,7 +1059,7 @@ skip_rx: + */ + if (uap->vendor->dma_threshold) + pl011_write(ST_UART011_DMAWM_RX_16 | ST_UART011_DMAWM_TX_16, +- uap->port.membase, ST_UART011_DMAWM); ++ uap, ST_UART011_DMAWM); + + if (uap->using_rx_dma) { + if (pl011_dma_rx_trigger_dma(uap)) +@@ -1085,12 +1084,12 @@ static void pl011_dma_shutdown(struct uart_amba_port *uap) + return; + + /* Disable RX and TX DMA */ +- while (pl011_read(uap->port.membase, UART01x_FR) & UART01x_FR_BUSY) ++ while (pl011_read(uap, UART01x_FR) & UART01x_FR_BUSY) + barrier(); + + spin_lock_irq(&uap->port.lock); + uap->dmacr &= ~(UART011_DMAONERR | UART011_RXDMAE | UART011_TXDMAE); +- pl011_write(uap->dmacr, uap->port.membase, UART011_DMACR); ++ pl011_write(uap->dmacr, uap, UART011_DMACR); + spin_unlock_irq(&uap->port.lock); + + if (uap->using_tx_dma) { +@@ -1191,7 +1190,7 @@ static void pl011_stop_tx(struct uart_port *port) + container_of(port, struct uart_amba_port, port); + + uap->im &= ~UART011_TXIM; +- pl011_write(uap->im, uap->port.membase, UART011_IMSC); ++ pl011_write(uap->im, uap, UART011_IMSC); + pl011_dma_tx_stop(uap); + } + +@@ -1201,7 +1200,7 @@ static void pl011_tx_chars(struct uart_amba_port *uap, bool from_irq); + static void pl011_start_tx_pio(struct uart_amba_port *uap) + { + uap->im |= UART011_TXIM; +- pl011_write(uap->im, uap->port.membase, UART011_IMSC); ++ pl011_write(uap->im, uap, UART011_IMSC); + pl011_tx_chars(uap, false); + } + +@@ -1221,7 +1220,7 @@ static void pl011_stop_rx(struct uart_port *port) + + uap->im &= ~(UART011_RXIM|UART011_RTIM|UART011_FEIM| + UART011_PEIM|UART011_BEIM|UART011_OEIM); +- pl011_write(uap->im, uap->port.membase, UART011_IMSC); ++ pl011_write(uap->im, uap, UART011_IMSC); + + pl011_dma_rx_stop(uap); + } +@@ -1232,7 +1231,7 @@ static void pl011_enable_ms(struct uart_port *port) + container_of(port, struct uart_amba_port, port); + + uap->im |= UART011_RIMIM|UART011_CTSMIM|UART011_DCDMIM|UART011_DSRMIM; +- pl011_write(uap->im, uap->port.membase, UART011_IMSC); ++ pl011_write(uap->im, uap, UART011_IMSC); + } + + static void pl011_rx_chars(struct uart_amba_port *uap) +@@ -1252,7 +1251,7 @@ __acquires(&uap->port.lock) + dev_dbg(uap->port.dev, "could not trigger RX DMA job " + "fall back to interrupt mode again\n"); + uap->im |= UART011_RXIM; +- pl011_write(uap->im, uap->port.membase, UART011_IMSC); ++ pl011_write(uap->im, uap, UART011_IMSC); + } else { + #ifdef CONFIG_DMA_ENGINE + /* Start Rx DMA poll */ +@@ -1273,10 +1272,10 @@ static bool pl011_tx_char(struct uart_amba_port *uap, unsigned char c, + bool from_irq) + { + if (unlikely(!from_irq) && +- pl011_read(uap->port.membase, UART01x_FR) & UART01x_FR_TXFF) ++ pl011_read(uap, UART01x_FR) & UART01x_FR_TXFF) + return false; /* unable to transmit character */ + +- pl011_write(c, uap->port.membase, UART01x_DR); ++ pl011_write(c, uap, UART01x_DR); + uap->port.icount.tx++; + + return true; +@@ -1323,8 +1322,7 @@ static void pl011_modem_status(struct uart_amba_port *uap) + { + unsigned int status, delta; + +- status = pl011_read(uap->port.membase, UART01x_FR); +- status &= UART01x_FR_MODEM_ANY; ++ status = pl011_read(uap, UART01x_FR) & UART01x_FR_MODEM_ANY; + + delta = status ^ uap->old_status; + uap->old_status = status; +@@ -1352,15 +1350,15 @@ static void check_apply_cts_event_workaround(struct uart_amba_port *uap) + return; + + /* workaround to make sure that all bits are unlocked.. */ +- pl011_write(0x00, uap->port.membase, UART011_ICR); ++ pl011_write(0x00, uap, UART011_ICR); + + /* + * WA: introduce 26ns(1 uart clk) delay before W1C; + * single apb access will incur 2 pclk(133.12Mhz) delay, + * so add 2 dummy reads + */ +- dummy_read = pl011_read(uap->port.membase, UART011_ICR); +- dummy_read = pl011_read(uap->port.membase, UART011_ICR); ++ dummy_read = pl011_read(uap, UART011_ICR); ++ dummy_read = pl011_read(uap, UART011_ICR); + } + + static irqreturn_t pl011_int(int irq, void *dev_id) +@@ -1372,15 +1370,15 @@ static irqreturn_t pl011_int(int irq, void *dev_id) + int handled = 0; + + spin_lock_irqsave(&uap->port.lock, flags); +- imsc = pl011_read(uap->port.membase, UART011_IMSC); +- status = pl011_read(uap->port.membase, UART011_RIS) & imsc; ++ imsc = pl011_read(uap, UART011_IMSC); ++ status = pl011_read(uap, UART011_RIS) & imsc; + if (status) { + do { + check_apply_cts_event_workaround(uap); + + pl011_write(status & ~(UART011_TXIS|UART011_RTIS| + UART011_RXIS), +- uap->port.membase, UART011_ICR); ++ uap, UART011_ICR); + + if (status & (UART011_RTIS|UART011_RXIS)) { + if (pl011_dma_rx_running(uap)) +@@ -1397,7 +1395,7 @@ static irqreturn_t pl011_int(int irq, void *dev_id) + if (pass_counter-- == 0) + break; + +- status = pl011_read(uap->port.membase, UART011_RIS) & imsc; ++ status = pl011_read(uap, UART011_RIS) & imsc; + } while (status != 0); + handled = 1; + } +@@ -1411,7 +1409,7 @@ static unsigned int pl011_tx_empty(struct uart_port *port) + { + struct uart_amba_port *uap = + container_of(port, struct uart_amba_port, port); +- unsigned int status = pl011_read(uap->port.membase, UART01x_FR); ++ unsigned int status = pl011_read(uap, UART01x_FR); + return status & (UART01x_FR_BUSY|UART01x_FR_TXFF) ? 0 : TIOCSER_TEMT; + } + +@@ -1420,7 +1418,7 @@ static unsigned int pl011_get_mctrl(struct uart_port *port) + struct uart_amba_port *uap = + container_of(port, struct uart_amba_port, port); + unsigned int result = 0; +- unsigned int status = pl011_read(uap->port.membase, UART01x_FR); ++ unsigned int status = pl011_read(uap, UART01x_FR); + + #define TIOCMBIT(uartbit, tiocmbit) \ + if (status & uartbit) \ +@@ -1440,7 +1438,7 @@ static void pl011_set_mctrl(struct uart_port *port, unsigned int mctrl) + container_of(port, struct uart_amba_port, port); + unsigned int cr; + +- cr = pl011_read(uap->port.membase, UART011_CR); ++ cr = pl011_read(uap, UART011_CR); + + #define TIOCMBIT(tiocmbit, uartbit) \ + if (mctrl & tiocmbit) \ +@@ -1460,7 +1458,7 @@ static void pl011_set_mctrl(struct uart_port *port, unsigned int mctrl) + } + #undef TIOCMBIT + +- pl011_write(cr, uap->port.membase, UART011_CR); ++ pl011_write(cr, uap, UART011_CR); + } + + static void pl011_break_ctl(struct uart_port *port, int break_state) +@@ -1471,12 +1469,12 @@ static void pl011_break_ctl(struct uart_port *port, int break_state) + unsigned int lcr_h; + + spin_lock_irqsave(&uap->port.lock, flags); +- lcr_h = pl011_read(uap->port.membase, uap->lcrh_tx); ++ lcr_h = pl011_read(uap, uap->lcrh_tx); + if (break_state == -1) + lcr_h |= UART01x_LCRH_BRK; + else + lcr_h &= ~UART01x_LCRH_BRK; +- pl011_write(lcr_h, uap->port.membase, uap->lcrh_tx); ++ pl011_write(lcr_h, uap, uap->lcrh_tx); + spin_unlock_irqrestore(&uap->port.lock, flags); + } + +@@ -1486,9 +1484,8 @@ static void pl011_quiesce_irqs(struct uart_port *port) + { + struct uart_amba_port *uap = + container_of(port, struct uart_amba_port, port); +- unsigned char __iomem *regs = uap->port.membase; + +- pl011_write(pl011_read(regs, UART011_MIS), regs, UART011_ICR); ++ pl011_write(pl011_read(uap, UART011_MIS), uap, UART011_ICR); + /* + * There is no way to clear TXIM as this is "ready to transmit IRQ", so + * we simply mask it. start_tx() will unmask it. +@@ -1502,8 +1499,8 @@ static void pl011_quiesce_irqs(struct uart_port *port) + * (including tx queue), so we're also fine with start_tx()'s caller + * side. + */ +- pl011_write(pl011_read(regs, UART011_IMSC) & ~UART011_TXIM, +- regs, UART011_IMSC); ++ pl011_write(pl011_read(uap, UART011_IMSC) & ~UART011_TXIM, uap, ++ UART011_IMSC); + } + + static int pl011_get_poll_char(struct uart_port *port) +@@ -1518,11 +1515,11 @@ static int pl011_get_poll_char(struct uart_port *port) + */ + pl011_quiesce_irqs(port); + +- status = pl011_read(uap->port.membase, UART01x_FR); ++ status = pl011_read(uap, UART01x_FR); + if (status & UART01x_FR_RXFE) + return NO_POLL_CHAR; + +- return pl011_read(uap->port.membase, UART01x_DR); ++ return pl011_read(uap, UART01x_DR); + } + + static void pl011_put_poll_char(struct uart_port *port, +@@ -1531,10 +1528,10 @@ static void pl011_put_poll_char(struct uart_port *port, + struct uart_amba_port *uap = + container_of(port, struct uart_amba_port, port); + +- while (pl011_read(uap->port.membase, UART01x_FR) & UART01x_FR_TXFF) ++ while (pl011_read(uap, UART01x_FR) & UART01x_FR_TXFF) + barrier(); + +- pl011_write(ch, uap->port.membase, UART01x_DR); ++ pl011_write(ch, uap, UART01x_DR); + } + + #endif /* CONFIG_CONSOLE_POLL */ +@@ -1560,15 +1557,14 @@ static int pl011_hwinit(struct uart_port *port) + /* Clear pending error and receive interrupts */ + pl011_write(UART011_OEIS | UART011_BEIS | UART011_PEIS | + UART011_FEIS | UART011_RTIS | UART011_RXIS, +- uap->port.membase, UART011_ICR); ++ uap, UART011_ICR); + + /* + * Save interrupts enable mask, and enable RX interrupts in case if + * the interrupt is used for NMI entry. + */ +- uap->im = pl011_read(uap->port.membase, UART011_IMSC); +- pl011_write(UART011_RTIM | UART011_RXIM, uap->port.membase, +- UART011_IMSC); ++ uap->im = pl011_read(uap, UART011_IMSC); ++ pl011_write(UART011_RTIM | UART011_RXIM, uap, UART011_IMSC); + + if (dev_get_platdata(uap->port.dev)) { + struct amba_pl011_data *plat; +@@ -1582,7 +1578,7 @@ static int pl011_hwinit(struct uart_port *port) + + static void pl011_write_lcr_h(struct uart_amba_port *uap, unsigned int lcr_h) + { +- pl011_write(lcr_h, uap->port.membase, uap->lcrh_rx); ++ pl011_write(lcr_h, uap, uap->lcrh_rx); + if (uap->lcrh_rx != uap->lcrh_tx) { + int i; + /* +@@ -1590,14 +1586,14 @@ static void pl011_write_lcr_h(struct uart_amba_port *uap, unsigned int lcr_h) + * to get this delay write read only register 10 times + */ + for (i = 0; i < 10; ++i) +- pl011_write(0xff, uap->port.membase, UART011_MIS); +- pl011_write(lcr_h, uap->port.membase, uap->lcrh_tx); ++ pl011_write(0xff, uap, UART011_MIS); ++ pl011_write(lcr_h, uap, uap->lcrh_tx); + } + } + + static int pl011_allocate_irq(struct uart_amba_port *uap) + { +- pl011_write(uap->im, uap->port.membase, UART011_IMSC); ++ pl011_write(uap->im, uap, UART011_IMSC); + + return request_irq(uap->port.irq, pl011_int, 0, "uart-pl011", uap); + } +@@ -1612,12 +1608,11 @@ static void pl011_enable_interrupts(struct uart_amba_port *uap) + spin_lock_irq(&uap->port.lock); + + /* Clear out any spuriously appearing RX interrupts */ +- pl011_write(UART011_RTIS | UART011_RXIS, uap->port.membase, +- UART011_ICR); ++ pl011_write(UART011_RTIS | UART011_RXIS, uap, UART011_ICR); + uap->im = UART011_RTIM; + if (!pl011_dma_rx_running(uap)) + uap->im |= UART011_RXIM; +- pl011_write(uap->im, uap->port.membase, UART011_IMSC); ++ pl011_write(uap->im, uap, UART011_IMSC); + spin_unlock_irq(&uap->port.lock); + } + +@@ -1636,21 +1631,21 @@ static int pl011_startup(struct uart_port *port) + if (retval) + goto clk_dis; + +- pl011_write(uap->vendor->ifls, uap->port.membase, UART011_IFLS); ++ pl011_write(uap->vendor->ifls, uap, UART011_IFLS); + + spin_lock_irq(&uap->port.lock); + + /* restore RTS and DTR */ + cr = uap->old_cr & (UART011_CR_RTS | UART011_CR_DTR); + cr |= UART01x_CR_UARTEN | UART011_CR_RXE | UART011_CR_TXE; +- pl011_write(cr, uap->port.membase, UART011_CR); ++ pl011_write(cr, uap, UART011_CR); + + spin_unlock_irq(&uap->port.lock); + + /* + * initialise the old status of the modem signals + */ +- uap->old_status = pl011_read(uap->port.membase, UART01x_FR) & UART01x_FR_MODEM_ANY; ++ uap->old_status = pl011_read(uap, UART01x_FR) & UART01x_FR_MODEM_ANY; + + /* Startup DMA */ + pl011_dma_startup(uap); +@@ -1691,9 +1686,9 @@ static void pl011_shutdown_channel(struct uart_amba_port *uap, + { + unsigned long val; + +- val = pl011_read(uap->port.membase, lcrh); ++ val = pl011_read(uap, lcrh); + val &= ~(UART01x_LCRH_BRK | UART01x_LCRH_FEN); +- pl011_write(val, uap->port.membase, lcrh); ++ pl011_write(val, uap, lcrh); + } + + /* +@@ -1707,11 +1702,11 @@ static void pl011_disable_uart(struct uart_amba_port *uap) + + uap->autorts = false; + spin_lock_irq(&uap->port.lock); +- cr = pl011_read(uap->port.membase, UART011_CR); ++ cr = pl011_read(uap, UART011_CR); + uap->old_cr = cr; + cr &= UART011_CR_RTS | UART011_CR_DTR; + cr |= UART01x_CR_UARTEN | UART011_CR_TXE; +- pl011_write(cr, uap->port.membase, UART011_CR); ++ pl011_write(cr, uap, UART011_CR); + spin_unlock_irq(&uap->port.lock); + + /* +@@ -1728,8 +1723,8 @@ static void pl011_disable_interrupts(struct uart_amba_port *uap) + + /* mask all interrupts and clear all pending ones */ + uap->im = 0; +- pl011_write(uap->im, uap->port.membase, UART011_IMSC); +- pl011_write(0xffff, uap->port.membase, UART011_ICR); ++ pl011_write(uap->im, uap, UART011_IMSC); ++ pl011_write(0xffff, uap, UART011_ICR); + + spin_unlock_irq(&uap->port.lock); + } +@@ -1881,8 +1876,8 @@ pl011_set_termios(struct uart_port *port, struct ktermios *termios, + pl011_enable_ms(port); + + /* first, disable everything */ +- old_cr = pl011_read(port->membase, UART011_CR); +- pl011_write(0, port->membase, UART011_CR); ++ old_cr = pl011_read(uap, UART011_CR); ++ pl011_write(0, uap, UART011_CR); + + if (termios->c_cflag & CRTSCTS) { + if (old_cr & UART011_CR_RTS) +@@ -1915,8 +1910,8 @@ pl011_set_termios(struct uart_port *port, struct ktermios *termios, + quot -= 2; + } + /* Set baud rate */ +- pl011_write(quot & 0x3f, port->membase, UART011_FBRD); +- pl011_write(quot >> 6, port->membase, UART011_IBRD); ++ pl011_write(quot & 0x3f, uap, UART011_FBRD); ++ pl011_write(quot >> 6, uap, UART011_IBRD); + + /* + * ----------v----------v----------v----------v----- +@@ -1925,7 +1920,7 @@ pl011_set_termios(struct uart_port *port, struct ktermios *termios, + * ----------^----------^----------^----------^----- + */ + pl011_write_lcr_h(uap, lcr_h); +- pl011_write(old_cr, port->membase, UART011_CR); ++ pl011_write(old_cr, uap, UART011_CR); + + spin_unlock_irqrestore(&port->lock, flags); + } +@@ -2066,9 +2061,9 @@ static void pl011_console_putchar(struct uart_port *port, int ch) + struct uart_amba_port *uap = + container_of(port, struct uart_amba_port, port); + +- while (pl011_read(uap->port.membase, UART01x_FR) & UART01x_FR_TXFF) ++ while (pl011_read(uap, UART01x_FR) & UART01x_FR_TXFF) + barrier(); +- pl011_write(ch, uap->port.membase, UART01x_DR); ++ pl011_write(ch, uap, UART01x_DR); + } + + static void +@@ -2093,10 +2088,10 @@ pl011_console_write(struct console *co, const char *s, unsigned int count) + * First save the CR then disable the interrupts + */ + if (!uap->vendor->always_enabled) { +- old_cr = pl011_read(uap->port.membase, UART011_CR); ++ old_cr = pl011_read(uap, UART011_CR); + new_cr = old_cr & ~UART011_CR_CTSEN; + new_cr |= UART01x_CR_UARTEN | UART011_CR_TXE; +- pl011_write(new_cr, uap->port.membase, UART011_CR); ++ pl011_write(new_cr, uap, UART011_CR); + } + + uart_console_write(&uap->port, s, count, pl011_console_putchar); +@@ -2106,10 +2101,10 @@ pl011_console_write(struct console *co, const char *s, unsigned int count) + * and restore the TCR + */ + do { +- status = pl011_read(uap->port.membase, UART01x_FR); ++ status = pl011_read(uap, UART01x_FR); + } while (status & UART01x_FR_BUSY); + if (!uap->vendor->always_enabled) +- pl011_write(old_cr, uap->port.membase, UART011_CR); ++ pl011_write(old_cr, uap, UART011_CR); + + if (locked) + spin_unlock(&uap->port.lock); +@@ -2122,10 +2117,10 @@ static void __init + pl011_console_get_options(struct uart_amba_port *uap, int *baud, + int *parity, int *bits) + { +- if (pl011_read(uap->port.membase, UART011_CR) & UART01x_CR_UARTEN) { ++ if (pl011_read(uap, UART011_CR) & UART01x_CR_UARTEN) { + unsigned int lcr_h, ibrd, fbrd; + +- lcr_h = pl011_read(uap->port.membase, uap->lcrh_tx); ++ lcr_h = pl011_read(uap, uap->lcrh_tx); + + *parity = 'n'; + if (lcr_h & UART01x_LCRH_PEN) { +@@ -2140,13 +2135,13 @@ pl011_console_get_options(struct uart_amba_port *uap, int *baud, + else + *bits = 8; + +- ibrd = pl011_read(uap->port.membase, UART011_IBRD); +- fbrd = pl011_read(uap->port.membase, UART011_FBRD); ++ ibrd = pl011_read(uap, UART011_IBRD); ++ fbrd = pl011_read(uap, UART011_FBRD); + + *baud = uap->port.uartclk * 4 / (64 * ibrd + fbrd); + + if (uap->vendor->oversampling) { +- if (pl011_read(uap->port.membase, UART011_CR) ++ if (pl011_read(uap, UART011_CR) + & ST_UART011_CR_OVSFACT) + *baud *= 2; + } +@@ -2348,8 +2343,8 @@ static int pl011_register_port(struct uart_amba_port *uap) + int ret; + + /* Ensure interrupts from this UART are masked and cleared */ +- pl011_write(0, uap->port.membase, UART011_IMSC); +- pl011_write(0xffff, uap->port.membase, UART011_ICR); ++ pl011_write(0, uap, UART011_IMSC); ++ pl011_write(0xffff, uap, UART011_ICR); + + if (!amba_reg.state) { + ret = uart_register_driver(&amba_reg); diff --git a/SOURCES/4003-tty-amba-pl011-add-support-for-32-bit-register-acces.patch b/SOURCES/4003-tty-amba-pl011-add-support-for-32-bit-register-acces.patch new file mode 100644 index 0000000..c2fdb4b --- /dev/null +++ b/SOURCES/4003-tty-amba-pl011-add-support-for-32-bit-register-acces.patch @@ -0,0 +1,79 @@ +From: Russell King <rmk+kernel(a)arm.linux.org.uk> +Date: Mon, 16 Nov 2015 17:40:52 +0000 +Subject: tty: amba-pl011: add support for 32-bit register access + +Add support for 32-bit register accesses to the AMBA PL011 UART. This +is needed for ZTE UARTs, which require 32-bit accesses as opposed to +the more normal 16-bit accesses. + +Signed-off-by: Russell King <rmk+kernel(a)arm.linux.org.uk> +Reviewed-by: Peter Hurley <peter(a)hurleysoftware.com> +Signed-off-by: Greg Kroah-Hartman <gregkh(a)linuxfoundation.org> + +Git-commit: 84c3e03bdd1146191b7222ed62a08512199a45c7 +Git-repo: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git +[cov(a)codeaurora.org: Backport to CentOS 7.2] +Signed-off-by: Christopher Covington <cov(a)codeaurora.org> +--- + drivers/tty/serial/amba-pl011.c | 15 +++++++++++++-- + 1 file changed, 13 insertions(+), 2 deletions(-) + +diff --git a/drivers/tty/serial/amba-pl011.c b/drivers/tty/serial/amba-pl011.c +index 61512af..bb49704 100644 +--- a/drivers/tty/serial/amba-pl011.c ++++ b/drivers/tty/serial/amba-pl011.c +@@ -74,6 +74,7 @@ + /* There is by now at least one vendor with differing details, so handle it */ + struct vendor_data { + unsigned int ifls; ++ bool access_32b; + unsigned int lcrh_tx; + unsigned int lcrh_rx; + bool oversampling; +@@ -172,6 +173,7 @@ struct uart_amba_port { + unsigned int lcrh_rx; /* vendor-specific */ + unsigned int old_cr; /* state during shutdown */ + bool autorts; ++ bool access_32b; + unsigned int fixed_baud; /* vendor-set fixed baud rate */ + char type[12]; + #ifdef CONFIG_DMA_ENGINE +@@ -187,13 +189,20 @@ struct uart_amba_port { + static unsigned int pl011_read(const struct uart_amba_port *uap, + unsigned int reg) + { +- return readw(uap->port.membase + reg); ++ void __iomem *addr = uap->port.membase + reg; ++ ++ return uap->access_32b ? readl(addr) : readw(addr); + } + + static void pl011_write(unsigned int val, const struct uart_amba_port *uap, + unsigned int reg) + { +- writew(val, uap->port.membase + reg); ++ void __iomem *addr = uap->port.membase + reg; ++ ++ if (uap->access_32b) ++ writel(val, addr); ++ else ++ writew(val, addr); + } + + /* +@@ -2381,6 +2390,7 @@ static int pl011_probe(struct amba_device *dev, const struct amba_id *id) + if (IS_ERR(uap->clk)) + return PTR_ERR(uap->clk); + ++ uap->access_32b = vendor->access_32b; + uap->vendor = vendor; + uap->lcrh_rx = vendor->lcrh_rx; + uap->lcrh_tx = vendor->lcrh_tx; +@@ -2462,6 +2472,7 @@ static int sbsa_uart_probe(struct platform_device *pdev) + if (!uap) + return -ENOMEM; + ++ uap->access_32b = vendor_sbsa.access_32b; + uap->vendor = &vendor_sbsa; + uap->fifosize = 32; + uap->port.irq = platform_get_irq(pdev, 0); diff --git a/SOURCES/4004-tty-amba-pl011-use-iotype-instead-of-access_32b-to-t.patch b/SOURCES/4004-tty-amba-pl011-use-iotype-instead-of-access_32b-to-t.patch new file mode 100644 index 0000000..c8250c4 --- /dev/null +++ b/SOURCES/4004-tty-amba-pl011-use-iotype-instead-of-access_32b-to-t.patch @@ -0,0 +1,119 @@ +From: Timur Tabi <timur(a)codeaurora.org> +Date: Mon, 4 Jan 2016 15:37:42 -0600 +Subject: tty: amba-pl011: use iotype instead of access_32b to track 32-bit I/O + +Instead of defining a new field in the uart_amba_port structure, use the +existing iotype field of the uart_port structure, which is intended for +this purpose. If we need to use 32-bit register access, we set iotype +to UPIO_MEM32, otherwise we set it to UPIO_MEM. + +For early console, specify the "mmio32" option on the kernel command-line. +Example: + + earlycon=pl011,mmio32,0x3ced1000 + +Signed-off-by: Timur Tabi <timur(a)codeaurora.org> +Signed-off-by: Greg Kroah-Hartman <gregkh(a)linuxfoundation.org> + +Git-commit: 3b78fae793c027140cfe635ef216bf60aa6498f4 +Git-repo: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git +[cov(a)codeaurora.org: Backport to CentOS 7.2] +Signed-off-by: Christopher Covington <cov(a)codeaurora.org> +--- + Documentation/kernel-parameters.txt | 5 ++++- + drivers/tty/serial/amba-pl011.c | 15 ++++++++------- + 2 files changed, 12 insertions(+), 8 deletions(-) + +diff --git a/Documentation/kernel-parameters.txt b/Documentation/kernel-parameters.txt +index 1d6f045..59bebdd 100644 +--- a/Documentation/kernel-parameters.txt ++++ b/Documentation/kernel-parameters.txt +@@ -990,10 +990,13 @@ bytes respectively. Such letter suffixes can also be entirely omitted. + unspecified, the h/w is not initialized. + + pl011,<addr> ++ pl011,mmio32,<addr> + Start an early, polled-mode console on a pl011 serial + port at the specified address. The pl011 serial port + must already be setup and configured. Options are not +- yet supported. ++ yet supported. If 'mmio32' is specified, then only ++ the driver will use only 32-bit accessors to read/write ++ the device registers. + + msm_serial,<addr> + Start an early, polled-mode console on an msm serial +diff --git a/drivers/tty/serial/amba-pl011.c b/drivers/tty/serial/amba-pl011.c +index bb49704..85cf7d0 100644 +--- a/drivers/tty/serial/amba-pl011.c ++++ b/drivers/tty/serial/amba-pl011.c +@@ -173,7 +173,6 @@ struct uart_amba_port { + unsigned int lcrh_rx; /* vendor-specific */ + unsigned int old_cr; /* state during shutdown */ + bool autorts; +- bool access_32b; + unsigned int fixed_baud; /* vendor-set fixed baud rate */ + char type[12]; + #ifdef CONFIG_DMA_ENGINE +@@ -191,7 +190,7 @@ static unsigned int pl011_read(const struct uart_amba_port *uap, + { + void __iomem *addr = uap->port.membase + reg; + +- return uap->access_32b ? readl(addr) : readw(addr); ++ return (uap->port.iotype == UPIO_MEM32) ? readl(addr) : readw(addr); + } + + static void pl011_write(unsigned int val, const struct uart_amba_port *uap, +@@ -199,7 +198,7 @@ static void pl011_write(unsigned int val, const struct uart_amba_port *uap, + { + void __iomem *addr = uap->port.membase + reg; + +- if (uap->access_32b) ++ if (uap->port.iotype == UPIO_MEM32) + writel(val, addr); + else + writew(val, addr); +@@ -2224,7 +2223,10 @@ static void pl011_putc(struct uart_port *port, int c) + { + while (readl(port->membase + UART01x_FR) & UART01x_FR_TXFF) + ; +- writeb(c, port->membase + UART01x_DR); ++ if (port->iotype == UPIO_MEM32) ++ writel(c, port->membase + UART01x_DR); ++ else ++ writeb(c, port->membase + UART01x_DR); + while (readl(port->membase + UART01x_FR) & UART01x_FR_BUSY) + ; + } +@@ -2337,7 +2339,6 @@ static int pl011_setup_port(struct device *dev, struct uart_amba_port *uap, + uap->port.dev = dev; + uap->port.mapbase = mmiobase->start; + uap->port.membase = base; +- uap->port.iotype = UPIO_MEM; + uap->port.fifosize = uap->fifosize; + uap->port.flags = UPF_BOOT_AUTOCONF; + uap->port.line = index; +@@ -2390,11 +2391,11 @@ static int pl011_probe(struct amba_device *dev, const struct amba_id *id) + if (IS_ERR(uap->clk)) + return PTR_ERR(uap->clk); + +- uap->access_32b = vendor->access_32b; + uap->vendor = vendor; + uap->lcrh_rx = vendor->lcrh_rx; + uap->lcrh_tx = vendor->lcrh_tx; + uap->fifosize = vendor->get_fifosize(dev); ++ uap->port.iotype = vendor->access_32b ? UPIO_MEM32 : UPIO_MEM; + uap->port.irq = dev->irq[0]; + uap->port.ops = &amba_pl011_pops; + +@@ -2472,9 +2473,9 @@ static int sbsa_uart_probe(struct platform_device *pdev) + if (!uap) + return -ENOMEM; + +- uap->access_32b = vendor_sbsa.access_32b; + uap->vendor = &vendor_sbsa; + uap->fifosize = 32; ++ uap->port.iotype = vendor_sbsa.access_32b ? UPIO_MEM32 : UPIO_MEM; + uap->port.irq = platform_get_irq(pdev, 0); + uap->port.ops = &sbsa_uart_pops; + uap->fixed_baud = baudrate; diff --git a/SOURCES/4005-tty-amba-pl011-Use-32-bit-accesses-for-SBSA-UART.patch b/SOURCES/4005-tty-amba-pl011-Use-32-bit-accesses-for-SBSA-UART.patch new file mode 100644 index 0000000..1d5e226 --- /dev/null +++ b/SOURCES/4005-tty-amba-pl011-Use-32-bit-accesses-for-SBSA-UART.patch @@ -0,0 +1,29 @@ +From: Christopher Covington <cov(a)codeaurora.org> +Date: Tue, 19 Apr 2016 13:52:25 -0400 +Subject: tty: amba-pl011: Use 32-bit accesses for SBSA UART + +Version 2 of the Server Base System Architecture (SBSAv2) describes UART +hardware registers as 32 bits wide, giving no guidance on access sizes. The +SBSA UART driver previously assumed partial-length 16 and 8 bit accesses would +work. But the SBSAv2 UART hardware on the Qualcomm Technologies QDF2432 only +supports full-length 32 bit register accesses, so use those exclusively. This +is compatible with SBSAv3, which explicitly requires UART hardware support 32 +(and 16 and sometimes 8) bit accesses. + +Signed-off-by: Christopher Covington <cov@codeaurora> +--- + drivers/tty/serial/amba-pl011.c | 1 + + 1 file changed, 1 insertion(+) + +diff --git a/drivers/tty/serial/amba-pl011.c b/drivers/tty/serial/amba-pl011.c +index 85cf7d0..7127ae0 100644 +--- a/drivers/tty/serial/amba-pl011.c ++++ b/drivers/tty/serial/amba-pl011.c +@@ -104,6 +104,7 @@ static struct vendor_data vendor_arm = { + }; + + static struct vendor_data vendor_sbsa = { ++ .access_32b = true, + .oversampling = false, + .dma_threshold = false, + .cts_event_workaround = false, diff --git a/SOURCES/4006-irqchip-Fully-support-ACPI-GICv3-ITS.patch b/SOURCES/4006-irqchip-Fully-support-ACPI-GICv3-ITS.patch new file mode 100644 index 0000000..555fe45 --- /dev/null +++ b/SOURCES/4006-irqchip-Fully-support-ACPI-GICv3-ITS.patch @@ -0,0 +1,49 @@ +From: Christopher Covington <cov(a)codeaurora.org> +Date: Fri, 29 Apr 2016 16:06:41 -0400 +Subject: irqchip: Fully support ACPI GICv3 ITS + +Remove stray references to device-tree-specific strings. + +Signed-off-by: Christopher Covington <cov(a)codeaurora.org> +--- + drivers/irqchip/irq-gic-v3-its.c | 13 ++++++------- + 1 file changed, 6 insertions(+), 7 deletions(-) + +diff --git a/drivers/irqchip/irq-gic-v3-its.c b/drivers/irqchip/irq-gic-v3-its.c +index 3da7a09..2989634 100644 +--- a/drivers/irqchip/irq-gic-v3-its.c ++++ b/drivers/irqchip/irq-gic-v3-its.c +@@ -887,8 +887,8 @@ static int its_alloc_tables(struct its_node *its) + order); + if (order >= MAX_ORDER) { + order = MAX_ORDER - 1; +- pr_warn("%s: Device Table too large, reduce its page order to %u\n", +- its->domain->of_node->full_name, order); ++ pr_warn("ITS: Device Table too large, reduce its page order to %u\n", ++ order); + } + } + +@@ -897,8 +897,8 @@ static int its_alloc_tables(struct its_node *its) + if (alloc_pages > GITS_BASER_PAGES_MAX) { + alloc_pages = GITS_BASER_PAGES_MAX; + order = get_order(GITS_BASER_PAGES_MAX * psz); +- pr_warn("%s: Device Table too large, reduce its page order to %u (%u pages)\n", +- its->domain->of_node->full_name, order, alloc_pages); ++ pr_warn("ITS: Device Table too large, reduce its page order to %u (%u pages)\n", ++ order, alloc_pages); + } + + base = (void *)__get_free_pages(GFP_KERNEL | __GFP_ZERO, order); +@@ -965,9 +965,8 @@ retry_baser: + } + + if (val != tmp) { +- pr_err("ITS: %s: GITS_BASER%d doesn't stick: %lx %lx\n", +- its->domain->of_node->full_name, i, +- (unsigned long) val, (unsigned long) tmp); ++ pr_err("ITS: GITS_BASER%d doesn't stick: %lx %lx\n", ++ i, (unsigned long) val, (unsigned long) tmp); + err = -ENXIO; + goto out_free; + } diff --git a/SOURCES/4007-acpi-add-support-for-extended-IRQ-to-PCI-link.patch b/SOURCES/4007-acpi-add-support-for-extended-IRQ-to-PCI-link.patch new file mode 100644 index 0000000..2bbb6ad --- /dev/null +++ b/SOURCES/4007-acpi-add-support-for-extended-IRQ-to-PCI-link.patch @@ -0,0 +1,113 @@ +From: Sinan Kaya <okaya(a)codeaurora.org> +Date: Mon, 14 Apr 2014 17:48:54 -0500 +Subject: acpi: add support for extended IRQ to PCI link + +The ACPI compiler uses the extended format when +used interrupt numbers are greater than 256. +The PCI link code currently only supports simple +interrupt format. The IRQ numbers are represented +using 32 bits when extended IRQ syntax. This patch +changes the interrupt number type to 32 bits and +places an upper limit of 512 as possible interrupt +id. Additional checks have been placed to prevent +out of bounds writes. + +Signed-off-by: Sinan Kaya <okaya(a)codeaurora.org> +--- + drivers/acpi/pci_link.c | 39 +++++++++++++++++++++++++-------------- + 1 file changed, 25 insertions(+), 14 deletions(-) + +diff --git a/drivers/acpi/pci_link.c b/drivers/acpi/pci_link.c +index cfd7581..422f5d2 100644 +--- a/drivers/acpi/pci_link.c ++++ b/drivers/acpi/pci_link.c +@@ -1,6 +1,7 @@ + /* + * pci_link.c - ACPI PCI Interrupt Link Device Driver ($Revision: 34 $) + * ++ * Copyright (c) 2014, The Linux Foundation. All rights reserved. + * Copyright (C) 2001, 2002 Andy Grover <andrew.grover(a)intel.com> + * Copyright (C) 2001, 2002 Paul Diefenbaugh <paul.s.diefenbaugh(a)intel.com> + * Copyright (C) 2002 Dominik Brodowski <devel(a)brodo.de> +@@ -71,12 +72,12 @@ static struct acpi_scan_handler pci_link_handler = { + * later even the link is disable. Instead, we just repick the active irq + */ + struct acpi_pci_link_irq { +- u8 active; /* Current IRQ */ ++ u32 active; /* Current IRQ */ + u8 triggering; /* All IRQs */ + u8 polarity; /* All IRQs */ + u8 resource_type; + u8 possible_count; +- u8 possible[ACPI_PCI_LINK_MAX_POSSIBLE]; ++ u32 possible[ACPI_PCI_LINK_MAX_POSSIBLE]; + u8 initialized:1; + u8 reserved:7; + }; +@@ -441,7 +442,7 @@ static int acpi_pci_link_set(struct acpi_pci_link *link, int irq) + * enabled system. + */ + +-#define ACPI_MAX_IRQS 256 ++#define ACPI_MAX_IRQS 512 + #define ACPI_MAX_ISA_IRQ 16 + + #define PIRQ_PENALTY_PCI_AVAILABLE (0) +@@ -497,13 +498,16 @@ int __init acpi_irq_penalty_init(void) + penalty; + } + +- } else if (link->irq.active) { ++ } else if (link->irq.active && ++ (link->irq.active < ACPI_MAX_IRQS)) { + acpi_irq_penalty[link->irq.active] += + PIRQ_PENALTY_PCI_POSSIBLE; + } + } + /* Add a penalty for the SCI */ +- acpi_irq_penalty[acpi_gbl_FADT.sci_interrupt] += PIRQ_PENALTY_PCI_USING; ++ if (acpi_gbl_FADT.sci_interrupt < ACPI_MAX_IRQS) ++ acpi_irq_penalty[acpi_gbl_FADT.sci_interrupt] += ++ PIRQ_PENALTY_PCI_USING; + return 0; + } + +@@ -547,14 +551,19 @@ static int acpi_pci_link_allocate(struct acpi_pci_link *link) + irq = link->irq.possible[link->irq.possible_count - 1]; + + if (acpi_irq_balance || !link->irq.active) { +- /* +- * Select the best IRQ. This is done in reverse to promote +- * the use of IRQs 9, 10, 11, and >15. +- */ +- for (i = (link->irq.possible_count - 1); i >= 0; i--) { +- if (acpi_irq_penalty[irq] > +- acpi_irq_penalty[link->irq.possible[i]]) +- irq = link->irq.possible[i]; ++ ++ if (irq < ACPI_MAX_IRQS) { ++ /* ++ * Select the best IRQ. This is done in reverse to ++ * promote the use of IRQs 9, 10, 11, and >15. ++ */ ++ for (i = (link->irq.possible_count - 1); i >= 0; ++ i--) { ++ if ((link->irq.possible[i] < ACPI_MAX_IRQS) && ++ (acpi_irq_penalty[irq] > ++ acpi_irq_penalty[link->irq.possible[i]])) ++ irq = link->irq.possible[i]; ++ } + } + } + +@@ -566,7 +575,9 @@ static int acpi_pci_link_allocate(struct acpi_pci_link *link) + acpi_device_bid(link->device)); + return -ENODEV; + } else { +- acpi_irq_penalty[link->irq.active] += PIRQ_PENALTY_PCI_USING; ++ if (link->irq.active < ACPI_MAX_IRQS) ++ acpi_irq_penalty[link->irq.active] += ++ PIRQ_PENALTY_PCI_USING; + printk(KERN_WARNING PREFIX "%s [%s] enabled at IRQ %d\n", + acpi_device_name(link->device), + acpi_device_bid(link->device), link->irq.active); diff --git a/SOURCES/4008-irqchip-gic-v3-ACPI-Add-redistributor-support-via-GI.patch b/SOURCES/4008-irqchip-gic-v3-ACPI-Add-redistributor-support-via-GI.patch new file mode 100644 index 0000000..f6b8c2c --- /dev/null +++ b/SOURCES/4008-irqchip-gic-v3-ACPI-Add-redistributor-support-via-GI.patch @@ -0,0 +1,68 @@ +From: Tomasz Nowicki <tn(a)semihalf.com> +Date: Tue, 19 Jan 2016 14:11:16 +0100 +Subject: irqchip/gic-v3: ACPI: Add redistributor support via GICC structures + +Following ACPI spec: +On systems supporting GICv3 and above, GICR Base Address in MADT GICC +structure holds the 64-bit physical address of the associated Redistributor. +If all of the GIC Redistributors are in the always-on power domain, +GICR structures should be used to describe the Redistributors instead, +and this field must be set to 0. + +It means that we have two ways to initialize registirbutors map. +1. via GICD structure which can accommodate many redistributors as a region +2. via GICC which is able to describe single redistributor + +This patch is going to add support for second option. +Considering redistributors, GICD and GICC subtables have be mutually +exclusive. While discovering and mapping redistributor, we need to know +its size in advance. For the GICC case, redistributor can be in +a power-domain that is off, thus we cannot relay on GICR TYPER register. +Therefore, we get GIC version from distributor register and map 2xSZ_64K +for GICv3. [While the upstream version of this patch includes support for +GICv4, this backport omits it for simplicity.] + +Acked-by: Marc Zyngier <marc.zyngier(a)arm.com> +Signed-off-by: Hanjun Guo <hanjun.guo(a)linaro.org> +Signed-off-by: Tomasz Nowicki <tn(a)semihalf.com> +Signed-off-by: Marc Zyngier <marc.zyngier(a)arm.com> + +Git-commit: b70fb7af67158250bf16db467926e6e105d8bc49 +Git-repo: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git +[cov(a)codeaurora.org: Backport GICv3 essentials to CentOS 7.2] +Signed-off-by: Christopher Covington <cov(a)codeaurora.org> +--- + drivers/irqchip/irq-gic-v3.c | 6 +++++- + 1 file changed, 5 insertions(+), 1 deletion(-) + +diff --git a/drivers/irqchip/irq-gic-v3.c b/drivers/irqchip/irq-gic-v3.c +index f729b97..cf75d81 100644 +--- a/drivers/irqchip/irq-gic-v3.c ++++ b/drivers/irqchip/irq-gic-v3.c +@@ -49,6 +49,7 @@ struct gic_chip_data { + u64 redist_stride; + u32 nr_redist_regions; + unsigned int irq_nr; ++ bool single_redist; + }; + + static struct gic_chip_data gic_data __read_mostly; +@@ -453,6 +454,9 @@ static int gic_populate_rdist(void) + return 0; + } + ++ if (gic_data.single_redist) ++ break; ++ + if (gic_data.redist_stride) { + ptr += gic_data.redist_stride; + } else { +@@ -1092,7 +1096,7 @@ gic_v3_acpi_init(struct acpi_table_header *table, struct irq_domain **domain) + gic_acpi_parse_madt_redist, table, + ACPI_MADT_TYPE_GENERIC_REDISTRIBUTOR, 0); + if (!count) +- pr_info("No valid GICR entries exist\n"); ++ gic_data.single_redist = true; + else if (count < 0) { + pr_err("Error during GICR entries parsing\n"); + err = -EINVAL; diff --git a/SPECS/kernel-aarch64.spec b/SPECS/kernel-aarch64.spec index ad66cd6..52ee2d1 100644 --- a/SPECS/kernel-aarch64.spec +++ b/SPECS/kernel-aarch64.spec @@ -12,7 +12,7 @@ Summary: The Linux kernel %define rpmversion 4.2.0 %define pkgrelease 0.21.el7 -%define centupdate 0.27.el7 +%define centupdate 0.28.el7 # allow pkg_release to have configurable %{?dist} tag %define specrelease %%SPECRELEASE%% @@ -344,6 +344,16 @@ Patch2000: KEYS-Fix-keyring-ref-leak-in-join_session_keyring.patch # NXP Patches Patch3001: NXP-Layerscape-support.patch +# QDF2432 Patches +Patch4001: 4001-tty-amba-pl011-add-register-accessor-functions.patch +Patch4002: 4002-tty-amba-pl011-convert-accessor-functions-to-take-ua.patch +Patch4003: 4003-tty-amba-pl011-add-support-for-32-bit-register-acces.patch +Patch4004: 4004-tty-amba-pl011-use-iotype-instead-of-access_32b-to-t.patch +Patch4005: 4005-tty-amba-pl011-Use-32-bit-accesses-for-SBSA-UART.patch +Patch4006: 4006-irqchip-Fully-support-ACPI-GICv3-ITS.patch +Patch4007: 4007-acpi-add-support-for-extended-IRQ-to-PCI-link.patch +Patch4008: 4008-irqchip-gic-v3-ACPI-Add-redistributor-support-via-GI.patch + # empty final patch to facilitate testing of kernel patches Patch999999: linux-kernel-test.patch @@ -693,6 +703,16 @@ git am %{PATCH2000} # Apply NXP patches git am %{PATCH3001} +# Apply QDF2432 patches +git am %{PATCH4001} +git am %{PATCH4002} +git am %{PATCH4003} +git am %{PATCH4004} +git am %{PATCH4005} +git am %{PATCH4006} +git am %{PATCH4007} +git am %{PATCH4008} + # Any further pre-build tree manipulations happen here. chmod +x scripts/checkpatch.pl @@ -1458,6 +1478,9 @@ fi %kernel_variant_files %{with_debug} kernel-debug debug %changelog +* Mon May 09 2016 Christopher Covington <cov(a)codeaurora.org> [4.2.0-0.28.el7] +- Initial QDF2432 support + * Tue Mar 22 2016 Jim Perrin <jperrin(a)centos.org> [4.2.0-0.27.el7] - Initial NXP support -- Qualcomm Innovation Center, Inc. Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project

9 years, 10 months

Re: [CentOS-devel] Minishift in PaaS SIG

by Lalatendu Mohanty

On Tue, Mar 21, 2017 at 10:32 PM, Lalatendu Mohanty <lmohanty(a)redhat.com> wrote: > > > On Tue, Mar 21, 2017 at 3:47 AM, Marcin Dulak <marcin.dulak(a)gmail.com> > wrote: > >> >> >> On Thu, Mar 16, 2017 at 11:58 AM, Marcin Dulak <marcin.dulak(a)gmail.com> >> wrote: >> >>> >>> >>> On Thu, Mar 16, 2017 at 11:55 AM, Lalatendu Mohanty <lmohanty(a)redhat.com >>> > wrote: >>> >>>> >>>> >>>> On Wed, Mar 15, 2017 at 1:30 AM, Marcin Dulak <marcin.dulak(a)gmail.com> >>>> wrote: >>>> >>>>> Hi, >>>>> >>>>> On Tue, Mar 14, 2017 at 7:17 PM, Lalatendu Mohanty < >>>>> lmohanty(a)redhat.com> wrote: >>>>> >>>>>> Hi All, >>>>>> >>>>>> In last couple of Paas SIG meetings we discussed around if we should >>>>>> provide Minishift from PaaS SIG and the general agreement was that it will >>>>>> benefit the CentOS community. As a member of Minishift project and PaaS >>>>>> SIG member I will work to build Minishift in the CentOS build system and >>>>>> doing the releases through PaaS SIG. I have copied the recent release >>>>>> announcement of Minishift in this mail to give you some context about >>>>>> Minishift . >>>>>> >>>>>> Previously we were working on Atomic Developer Bundle (ADB) which was >>>>>> part of Atomic SIG. Minishift is the next generation tool to replace ADB >>>>>> as it address lot of ADB's short comings. It is written in Go and it is >>>>>> light weight and designed to provide better user experience. >>>>>> >>>>>> We have been doing couple of beta releases in Minishift project as >>>>>> we move towards the 1.0.0 release. The next release is planned to be a >>>>>> release candidate release then followed by 1.0.0 release. >>>>>> >>>>>> If you are interested to help us in building, testing, releasing >>>>>> Minishift through PaaS SIG, please let us know. >>>>>> >>>>> >>>>> I would like to help. >>>>> Got https://github.com/minishift/minishift/blob/master/READM >>>>> E.md#deploying-a-sample-application run with virtualbox 5.1.14r112924 >>>>> and minishift-1.0.0-beta.5-linux-amd64.tgz >>>>> >>>>> My packaging experience: >>>>> https://admin.fedoraproject.org/pkgdb/packager/marcindulak/ >>>>> >>>> >>>> Thanks for the offer for helping with Minishift. >>>> >>>>> >>>>> Any specific tasks that may correspond to my profile? >>>>> >>>> >>>> There are two tasks for Minishift. First we need to create a RPM for >>>> Minishift binary. >>>> >>> >>> OK, I think I can contribute to this. >>> >> >> https://copr.fedorainfracloud.org/coprs/marcindulak/minishift/builds/ - >> it looks like the following dependencies are needed on CentOS7, and a >> couple packages less on Fedora: >> >> DEBUG util.py:439: Error: No Package found for golang(github.com/DATA-DOG/godog) >> DEBUG util.py:439: Error: No Package found for golang(github.com/DATA-DOG/godog/gherkin) >> DEBUG util.py:439: Error: No Package found for golang(github.com/asaskevich/govalidator) >> DEBUG util.py:439: Error: No Package found for golang(github.com/blang/semver) >> DEBUG util.py:439: Error: No Package found for golang(github.com/docker/go-units) >> DEBUG util.py:439: Error: No Package found for golang(github.com/docker/machine/drivers/fakedriver) >> DEBUG util.py:439: Error: No Package found for golang(github.com/docker/machine/drivers/hyperv) >> DEBUG util.py:439: Error: No Package found for golang(github.com/docker/machine/drivers/virtualbox) >> DEBUG util.py:439: Error: No Package found for golang(github.com/docker/machine/drivers/vmwarefusion) >> DEBUG util.py:439: Error: No Package found for golang(github.com/docker/machine/libmachine) >> DEBUG util.py:439: Error: No Package found for golang(github.com/docker/machine/libmachine/auth) >> DEBUG util.py:439: Error: No Package found for golang(github.com/docker/machine/libmachine/drivers) >> DEBUG util.py:439: Error: No Package found for golang(github.com/docker/machine/libmachine/drivers/plugin) >> DEBUG util.py:439: Error: No Package found for golang(github.com/docker/machine/libmachine/drivers/plugin/localbinary) >> DEBUG util.py:439: Error: No Package found for golang(github.com/docker/machine/libmachine/engine) >> DEBUG util.py:439: Error: No Package found for golang(github.com/docker/machine/libmachine/host) >> DEBUG util.py:439: Error: No Package found for golang(github.com/docker/machine/libmachine/log) >> DEBUG util.py:439: Error: No Package found for golang(github.com/docker/machine/libmachine/mcnerror) >> DEBUG util.py:439: Error: No Package found for golang(github.com/docker/machine/libmachine/mcnflag) >> DEBUG util.py:439: Error: No Package found for golang(github.com/docker/machine/libmachine/mcnutils) >> DEBUG util.py:439: Error: No Package found for golang(github.com/docker/machine/libmachine/provision) >> DEBUG util.py:439: Error: No Package found for golang(github.com/docker/machine/libmachine/provision/pkgaction) >> DEBUG util.py:439: Error: No Package found for golang(github.com/docker/machine/libmachine/provision/provisiontest) >> DEBUG util.py:439: Error: No Package found for golang(github.com/docker/machine/libmachine/provision/serviceaction) >> DEBUG util.py:439: Error: No Package found for golang(github.com/docker/machine/libmachine/shell) >> DEBUG util.py:439: Error: No Package found for golang(github.com/docker/machine/libmachine/ssh) >> DEBUG util.py:439: Error: No Package found for golang(github.com/docker/machine/libmachine/state) >> DEBUG util.py:439: Error: No Package found for golang(github.com/docker/machine/libmachine/swarm) >> DEBUG util.py:439: Error: No Package found for golang(github.com/golang/glog) >> DEBUG util.py:439: Error: No Package found for golang(github.com/google/go-github/github) >> DEBUG util.py:439: Error: No Package found for golang(github.com/inconshreveable/go-update) >> DEBUG util.py:439: Error: No Package found for golang(github.com/kardianos/osext) >> DEBUG util.py:439: Error: No Package found for golang(github.com/olekukonko/tablewriter) >> DEBUG util.py:439: Error: No Package found for golang(github.com/pborman/uuid) >> DEBUG util.py:439: Error: No Package found for golang(github.com/pkg/browser) >> DEBUG util.py:439: Error: No Package found for golang(github.com/spf13/viper) >> DEBUG util.py:439: Error: No Package found for golang(golang.org/x/oauth2) >> DEBUG util.py:439: Error: No Package found for golang(k8s.io/kubernetes/pkg/api) >> DEBUG util.py:439: Error: No Package found for golang(k8s.io/kubernetes/pkg/api/v1) >> DEBUG util.py:439: Error: No Package found for golang(k8s.io/kubernetes/pkg/client/unversioned) >> DEBUG util.py:439: Error: No Package found for golang(k8s.io/kubernetes/pkg/client/unversioned/clientcmd) >> DEBUG util.py:439: Error: No Package found for golang(k8s.io/kubernetes/pkg/client/unversioned/clientcmd/api) >> DEBUG util.py:439: Error: No Package found for golang(k8s.io/kubernetes/pkg/client/unversioned/clientcmd/api/latest) >> >> Don't know about the required dependencies versions. >> >> I see also that several dependencies have been added to minishift git 250c9ed compared to beta5. >> >> https://copr.fedorainfracloud.org/coprs/logic/vault/ seems working on getting some of the dependencies into Fedora, >> >> but there are also several packages present in Fedora but absent in EPEL7 (the main one: k8s). >> >> Hi Marcin, > > Thanks for taking the initiative. WIll take a look and see if I can find a > way to fix this. In the mean time can you please put the the spec file some > place ( may be in a temporary github repository), so that we can > collaborate on this? > > > Also have you tried gofed [1] ? Not sure if it will help us, but worth a try. [1] https://github.com/gofed/gofed > Marcin >> >> >>> >>> >>>> Second we need to build the minishift-centos ISO in CBS. I will send >>>> you a separate mail on this and lets collaborate. >>>> >>> >>> Marcin >>> >>> >>>> Thanks, >>>> Lala >>>> >>>>> >>>>> Marcin >>>>> >>>>> >>>>>> >>>>>> >>>>>> >>>>>> *Release announcement for Minishift 1.0.0-Beta.5 : * >>>>>> >>>>>> The Minishift team is pleased to announce the release of Minishift >>>>>> 1.0.0 Beta 5. >>>>>> >>>>>> Minishift [1] is a command-line tool that provisions and manages >>>>>> single-node OpenShift clusters optimized for development workflows. You can >>>>>> run Minishift on GNU/Linux, Microsoft Windows or macOS. >>>>>> >>>>>> Release highlights >>>>>> >>>>>> ------------------------ >>>>>> >>>>>> This release adds several features, enhancements, and bug fixes, >>>>>> including: >>>>>> >>>>>> - >>>>>> >>>>>> Minishift is now configured to use nip.io instead of xip.io [4]. >>>>>> - >>>>>> >>>>>> The default routes for application will be created with the >>>>>> <VM IP>.nip.io routing suffix. >>>>>> - >>>>>> >>>>>> The sudoers role was added to the “developer” user [5]. >>>>>> - >>>>>> >>>>>> This role allows the “developer” to impersonate system:admin >>>>>> when running a command. For example, you can run “$ oc get nodes --as >>>>>> system:admin” while logged in as the developer user. >>>>>> - >>>>>> >>>>>> An important bug for proxy server (http/https) support was fixed >>>>>> [10]. >>>>>> - >>>>>> >>>>>> We had a bug where registration was failing in proxy >>>>>> environments. >>>>>> - >>>>>> >>>>>> OpenShift related subcommands from the root context were moved >>>>>> under the “minishift openshift” command [11]. >>>>>> >>>>>> >>>>>> This release also includes many changes and bug fixes, which are >>>>>> detailed in the release notes [2] and milestone [3] . For information >>>>>> about getting started, using, and developing Minishift, see the >>>>>> documentation [6]. >>>>>> >>>>>> Additional components >>>>>> >>>>>> ----------------------------- >>>>>> >>>>>> >>>>>> - >>>>>> >>>>>> We released new versions of the Boot2Docker ISO (v1.0.2) [ 8] and >>>>>> the CentOS ISO (v1.0.0-rc3) [7] images. >>>>>> - >>>>>> >>>>>> We added the ‘fuse-sshfs’ package to both the ISO images. With >>>>>> SSHFS, users can mount host folders. Currently this is a manual process [9] >>>>>> but we are working on automating it. >>>>>> >>>>>> >>>>>> Please give the new release a try and let us know your feedback. The >>>>>> Minishift community hangs out at #minishift channel on Freenode and it is >>>>>> the perfect place to discuss anything Minishift related. >>>>>> >>>>>> [1] https://github.com/minishift/minishift >>>>>> >>>>>> [2] https://github.com/minishift/minishift/releases/tag/v1.0.0-beta.5 >>>>>> >>>>>> [3] https://github.com/minishift/minishift/milestone/10 >>>>>> >>>>>> [4] https://github.com/minishift/minishift/issues/501 >>>>>> >>>>>> [5] https://github.com/minishift/minishift/issues/509 >>>>>> >>>>>> [6] https://github.com/minishift/minishift#documentation >>>>>> >>>>>> [7] https://github.com/minishift/minishift-centos-iso/releases/t >>>>>> ag/v1.0.0-rc.3 >>>>>> >>>>>> [8] https://github.com/minishift/minishift-b2d-iso/releases/tag/ >>>>>> v1.0.2 >>>>>> >>>>>> [9] https://github.com/minishift/minishift/blob/master/docs/mana >>>>>> ging-minishift.md#sshfs >>>>>> >>>>>> [10] https://github.com/minishift/minishift/issues/489 >>>>>> >>>>>> [11] https://github.com/minishift/minishift/issues/465 >>>>>> >>>>>> >>>>>> Thanks, >>>>>> Lala >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> CentOS-devel mailing list >>>>>> CentOS-devel(a)centos.org >>>>>> https://lists.centos.org/mailman/listinfo/centos-devel >>>>>> >>>>>> >>>>> >>>>> _______________________________________________ >>>>> CentOS-devel mailing list >>>>> CentOS-devel(a)centos.org >>>>> https://lists.centos.org/mailman/listinfo/centos-devel >>>>> >>>>> >>>> >>>> _______________________________________________ >>>> CentOS-devel mailing list >>>> CentOS-devel(a)centos.org >>>> https://lists.centos.org/mailman/listinfo/centos-devel >>>> >>>> >>> >> >> _______________________________________________ >> CentOS-devel mailing list >> CentOS-devel(a)centos.org >> https://lists.centos.org/mailman/listinfo/centos-devel >> >> >

9 years

[CentOS] CentOS 7 on a new Dell Precision

by Tony Schreiner

I am trying to install CentOS 7 on a Dell Precision 3640 and am having some driver problems. I had to use kmod-e1000e from ElReo enable networking on the: 00:1f.6 Ethernet controller [0200]: Intel Corporation Ethernet Connection (11) I219-LM [8086:0d4c] I still don't have graphics. When starting Gnome, it shows the graphic screen briefly but reverts to the text login. It has two graphics cards: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:9bc5] (rev 05) 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Lexa XT [Radeon PRO WX 3200] [1002:6981] (rev 10) lsmod shows i915 and amdgpu modules loaded but Xorg.0.log says the modules amdgpu cannot be found. Is it a version issue? Dell has a Radeon driver for RHEL 8, but not for 7. I have no xorg.conf file. [ 54.839] X.Org X Server 1.20.4 X Protocol Version 11, Revision 0 [ 54.840] Build Operating System: 3.10.0-957.1.3.el7.x86_64 [ 54.840] Current Operating System: Linux isr3c538b3kenn 3.10.0 1160.25.1.el7.x86_64 #1 SMP Wed Apr 28 21:49:45 UTC 2021 x86_64 [ 54.840] Kernel command line: BOOT_IMAGE=/vmlinuz-3.10.01160.25.1.el7.x86_64 root=/dev/mapper/centos-root ro crashkernel=auto rd.lvm.lv=centos/root rd.lvm.lv=centos/swap rhgb quiet LANG=en_US.UTF-8 [ 54.840] Build Date: 24 February 2021 09:09:20PM [ 54.840] Build ID: xorg-x11-server 1.20.4-15.el7_9 [ 54.840] Current version of pixman: 0.34.0 [ 54.840] Before reporting problems, check http://wiki.x.orgto make sure that you have the latest version. [ 54.840] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 54.840] (==) Log file: "/var/log/Xorg.0.log", Time: Mon May 3 14:31:21 2021 [ 54.840] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [ 54.840] (==) No Layout section. Using the first Screen section. [ 54.840] (==) No screen section available. Using defaults. [ 54.840] (**) |-->Screen "Default Screen Section" (0) [ 54.840] (**) | |-->Monitor "<default monitor>" [ 54.840] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [ 54.840] (==) Automatically adding devices [ 54.840] (==) Automatically enabling devices [ 54.840] (==) Automatically adding GPU devices [ 54.840] (==) Automatically binding GPU devices [ 54.840] (==) Max clients allowed: 256, resource mask: 0x1fffff [ 54.840] (==) FontPath set to: catalogue:/etc/X11/fontpath.d, built-ins [ 54.840] (==) ModulePath set to "/usr/lib64/xorg/modules" [ 54.840] (II) The server relies on udev to provide the list of input devices . If no devices become available, reconfigure udev or disable AutoAddDevices. [ 54.840] (II) Loader magic: 0x561cda874020 [ 54.840] (II) Module ABI versions: [ 54.840] X.Org ANSI C Emulation: 0.4 [ 54.840] X.Org Video Driver: 24.0 [ 54.840] X.Org XInput driver : 24.1 [ 54.840] X.Org Server Extension : 10.0 [ 54.841] (II) xfree86: Adding drm device (/dev/dri/card0) [ 54.841] (II) Platform probe for /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card0 [ 54.843] (--) PCI:*(0@0:2:0) 8086:9bc5:1028:098d rev 5, Mem @0xa1000000/16777216, 0x80000000/268435456, I/O @ 0x00004000/64, BIOS @ 0x????????/131072 [ 54.843] (--) PCI: (1@0:0:0) 1002:6981:1028:2b0d rev 16, Mem @0x4100000000/4294967296, 0x4080000000/2097152, 0xa2100000/262144, I/O @0x00003000/256, BIOS @ 0x????????/131072 [ 54.843] (II) LoadModule: "glx" [ 54.844] (II) Loading /usr/lib64/xorg/modules/extensions/libglx.so [ 54.844] (II) Module glx: vendor="X.Org Foundation" [ 54.844] compiled for 1.20.4, module version = 1.0.0 [ 54.844] ABI class: X.Org Server Extension, version 10.0 [ 54.844] (==) Matched ati as autoconfigured driver 0 [ 54.844] (==) Matched modesetting as autoconfigured driver 1 [ 54.844] (==) Matched fbdev as autoconfigured driver 2 [ 54.844] (==) Matched vesa as autoconfigured driver 3 [ 54.844] (==) Assigned the driver to the xf86ConfigLayout [ 54.844] (II) LoadModule: "ati" [ 54.844] (II) Loading /usr/lib64/xorg/modules/drivers/ati_drv.so [ 54.844] (II) Module ati: vendor="X.Org Foundation" [ 54.844] compiled for 1.20.4, module version = 19.0.1 [ 54.844] Module class: X.Org Video Driver [ 54.844] ABI class: X.Org Video Driver, version 24.0 [ 54.844] (II) LoadModule: "amdgpu" [ 54.844] (WW) Warning, couldn't open module amdgpu [ 54.844] (EE) Failed to load module "amdgpu" (module does not exist, 0) [ 54.844] (II) LoadModule: "modesetting" [ 54.844] (II) Loading /usr/lib64/xorg/modules/drivers/modesetting_drv.so [ 54.844] (II) Module modesetting: vendor="X.Org Foundation" [ 54.844] compiled for 1.20.4, module version = 1.20.4 [ 54.844] Module class: X.Org Video Driver [ 54.844] ABI class: X.Org Video Driver, version 24.0 [ 54.844] (II) LoadModule: "fbdev" [ 54.844] (II) Loading /usr/lib64/xorg/modules/drivers/fbdev_drv.so [ 54.844] (II) Module fbdev: vendor="X.Org Foundation" [ 54.844] compiled for 1.20.1, module version = 0.5.0 [ 54.844] Module class: X.Org Video Driver [ 54.844] ABI class: X.Org Video Driver, version 24.0 [ 54.844] (II) LoadModule: "vesa" [ 54.844] (II) Loading /usr/lib64/xorg/modules/drivers/vesa_drv.so [ 54.844] (II) Module vesa: vendor="X.Org Foundation" [ 54.844] compiled for 1.20.1, module version = 2.4.0 [ 54.844] Module class: X.Org Video Driver [ 54.844] ABI class: X.Org Video Driver, version 24.0 [ 54.844] (II) modesetting: Driver for Modesetting Kernel Drivers: kms [ 54.844] (II) FBDEV: driver for framebuffer: fbdev [ 54.844] (II) VESA: driver for VESA chipsets: vesa [ 54.844] (++) using VT number 2 [ 54.845] (WW) Falling back to old probe method for modesetting [ 54.845] (II) modeset(1): using default device [ 54.845] (II) Loading sub module "fbdevhw" [ 54.845] (II) LoadModule: "fbdevhw" [ 54.845] (II) Loading /usr/lib64/xorg/modules/libfbdevhw.so [ 54.845] (II) Module fbdevhw: vendor="X.Org Foundation" [ 54.845] compiled for 1.20.4, module version = 0.0.2 [ 54.845] ABI class: X.Org Video Driver, version 24.0 [ 54.845] (EE) Unable to find a valid framebuffer device [ 54.845] (WW) Falling back to old probe method for fbdev [ 54.845] (II) Loading sub module "fbdevhw" [ 54.845] (II) LoadModule: "fbdevhw" [ 54.845] (II) Loading /usr/lib64/xorg/modules/libfbdevhw.so [ 54.845] (II) Module fbdevhw: vendor="X.Org Foundation" [ 54.845] compiled for 1.20.4, module version = 0.0.2 [ 54.845] ABI class: X.Org Video Driver, version 24.0 [ 54.845] (II) FBDEV(3): using default device [ 54.845] vesa: Refusing to run on UEFI [ 54.845] (II) modeset(G0): using drv /dev/dri/card0 [ 54.845] (EE) Screen 0 deleted because of no matching config section. [ 54.845] (II) UnloadModule: "modesetting" [ 54.845] (EE) Screen 1 deleted because of no matching config section. [ 54.845] (II) UnloadModule: "fbdev" [ 54.845] (II) UnloadSubModule: "fbdevhw" [ 54.845] (II) modeset(0): Creating default Display subsection in Screen sect ion "Default Screen Section" for depth/fbbpp 24/32 [ 54.845] (==) modeset(0): Depth 24, (==) framebuffer bpp 32 [ 54.845] (DB) xf86MergeOutputClassOptions unsupported bus type 0 [ 54.845] (==) modeset(0): RGB weight 888 [ 54.845] (==) modeset(0): Default visual is TrueColor [ 54.845] (II) Loading sub module "glamoregl" [ 54.845] (II) LoadModule: "glamoregl" [ 54.845] (II) Loading /usr/lib64/xorg/modules/libglamoregl.so [ 54.847] (II) Module glamoregl: vendor="X.Org Foundation" [ 54.847] compiled for 1.20.4, module version = 1.0.1 [ 54.847] ABI class: X.Org ANSI C Emulation, version 0.4 [ 54.890] (II) modeset(0): glamor X acceleration enabled on AMD POLARIS12 (DRM 3.27.0, 3.10.0-1160.25.1.el7.x86_64, LLVM 7.0.1) [ 54.890] (II) modeset(0): glamor initialized [ 54.890] (II) modeset(0): Output DP-1 has no monitor section [ 54.890] (II) modeset(0): Output DP-2 has no monitor section [ 54.890] (II) modeset(0): Output DP-3 has no monitor section [ 54.890] (II) modeset(0): Output DP-4 has no monitor section [ 54.890] (II) modeset(0): EDID for output DP-1 [ 54.890] (II) modeset(0): EDID for output DP-2 [ 54.890] (II) modeset(0): EDID for output DP-3 [ 54.890] (II) modeset(0): EDID for output DP-4 [ 54.890] (II) modeset(0): Output DP-1 disconnected [ 54.890] (II) modeset(0): Output DP-2 disconnected [ 54.890] (II) modeset(0): Output DP-3 disconnected [ 54.890] (II) modeset(0): Output DP-4 disconnected [ 54.890] (WW) modeset(0): No outputs definitely connected, trying again... [ 54.890] (II) modeset(0): Output DP-1 disconnected [ 54.890] (II) modeset(0): Output DP-2 disconnected [ 54.890] (II) modeset(0): Output DP-3 disconnected [ 54.890] (II) modeset(0): Output DP-4 disconnected [ 54.890] (WW) modeset(0): Unable to find connected outputs - setting 1024x76 8 initial framebuffer [ 54.890] (==) modeset(0): Using gamma correction (1.0, 1.0, 1.0) [ 54.890] (==) modeset(0): DPI set to (96, 96) [ 54.890] (II) Loading sub module "fb" [ 54.890] (II) LoadModule: "fb" [ 54.890] (II) Loading /usr/lib64/xorg/modules/libfb.so [ 54.890] (II) Module fb: vendor="X.Org Foundation" [ 54.890] compiled for 1.20.4, module version = 1.0.0 [ 54.890] ABI class: X.Org ANSI C Emulation, version 0.4 [ 54.890] (II) FBDEV(1): Creating default Display subsection in Screen section "Default Screen Section" for depth/fbbpp 24/32 [ 54.890] (==) FBDEV(1): Depth 24, (==) framebuffer bpp 32 [ 54.890] (==) FBDEV(1): RGB weight 888 [ 54.890] (==) FBDEV(1): Default visual is TrueColor [ 54.890] (==) FBDEV(1): Using gamma correction (1.0, 1.0, 1.0) [ 54.890] (II) FBDEV(1): hardware: EFI VGA (video memory: 6892kB) [ 54.890] (DB) xf86MergeOutputClassOptions unsupported bus type 0 [ 54.890] (II) FBDEV(1): checking modes against framebuffer device... [ 54.890] (II) FBDEV(1): checking modes against monitor... [ 54.890] (II) FBDEV(1): Virtual size is 1680x1050 (pitch 1680) [ 54.890] (**) FBDEV(1): Built-in mode "current": 176.4 MHz, 82.9 kHz, 77.2 Hz [ 54.890] (II) FBDEV(1): Modeline "current"x0.0 176.43 1680 1712 1920 2128 1050 1054 1058 1074 -hsync -vsync -csync (82.9 kHz b) [ 54.890] (==) FBDEV(1): DPI set to (96, 96) [ 54.890] (II) Loading sub module "fb" [ 54.890] (II) LoadModule: "fb" [ 54.890] (II) Loading /usr/lib64/xorg/modules/libfb.so [ 54.890] (II) Module fb: vendor="X.Org Foundation" [ 54.890] compiled for 1.20.4, module version = 1.0.0 [ 54.890] ABI class: X.Org ANSI C Emulation, version 0.4 [ 54.890] (**) FBDEV(1): using shadow framebuffer [ 54.890] (II) Loading sub module "shadow" [ 54.890] (II) LoadModule: "shadow" [ 54.890] (II) Loading /usr/lib64/xorg/modules/libshadow.so [ 54.890] (II) Module shadow: vendor="X.Org Foundation [ 54.890] compiled for 1.20.4, module version = 1.1.0 [ 54.890] ABI class: X.Org ANSI C Emulation, version 0.4 [ 54.890] (==) modeset(G0): Depth 24, (==) framebuffer bpp 32 [ 54.890] (==) modeset(G0): RGB weight 888 [ 54.890] (==) modeset(G0): Default visual is TrueColor [ 54.890] (II) Loading sub module "glamoregl" [ 54.890] (II) LoadModule: "glamoregl" [ 54.890] (II) Loading /usr/lib64/xorg/modules/libglamoregl.so [ 54.890] (II) Module glamoregl: vendor="X.Org Foundation" [ 54.890] compiled for 1.20.4, module version = 1.0.1 [ 54.890] ABI class: X.Org ANSI C Emulation, version 0.4 [ 54.893] (II) modeset(G0): glamor X acceleration enabled on AMD POLARIS12 DRM 3.27.0, 3.10.0-1160.25.1.el7.x86_64, LLVM 7.0.1) [ 54.893] (II) modeset(G0): glamor initialized [ 54.893] (II) modeset(G0): Output DP-1-1 has no monitor section [ 54.893] (II) modeset(G0): Output DP-1-2 has no monitor section [ 54.893] (II) modeset(G0): Output DP-1-3 has no monitor section [ 54.893] (II) modeset(G0): Output DP-1-4 has no monitor section [ 54.893] (II) modeset(G0): EDID for output DP-1-1 [ 54.893] (II) modeset(G0): EDID for output DP-1-2 [ 54.893] (II) modeset(G0): EDID for output DP-1-3 [ 54.893] (II) modeset(G0): EDID for output DP-1-4 [ 54.893] (==) modeset(G0): Using gamma correction (1.0, 1.0, 1.0) [ 54.893] (==) modeset(G0): DPI set to (96, 96) [ 54.893] (II) Loading sub module "fb" [ 54.893] (II) LoadModule: "fb" [ 54.893] (II) Loading /usr/lib64/xorg/modules/libfb.so [ 54.893] (II) Module fb: vendor="X.Org Foundation" [ 54.893] compiled for 1.20.4, module version = 1.0.0 [ 54.893] ABI class: X.Org ANSI C Emulation, version 0.4 [ 54.893] (EE) modeset(G0): drmSetMaster failed: Invalid argument [ 54.893] (EE) Fatal server error: [ 54.893] (EE) AddScreen/ScreenInit failed for gpu driver 0 -1 [ 54.893] (EE) [ 54.893] (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. [ 54.893] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. [ 54.893] (EE) [ 54.895] (EE) Server terminated with error (1). Closing log file. Thanks if you have any recommendations. tony

4 years, 11 months

Re: [CentOS] CentOS Digest, Vol 134, Issue 12

by magesh.kuppusamy＠gmail.com

Sent from BlackBerry Passport Original Message From: centos-request(a)centos.org Sent: Saturday, March 12, 2016 5:30 PM To: centos(a)centos.org Reply To: centos(a)centos.org Subject: CentOS Digest, Vol 134, Issue 12 Send CentOS mailing list submissions to centos(a)centos.or',g To subscribe or unsubscribe via the World Wide Web, visit https://lists.centos.org/mailman/listinfo/centos or, via email, send a message with subject or body 'help' to centos-request(a)centos.org You can reach the person managing the list at centos-owner(a)centos.org When replying, please edit your Subject line so it is more specific than "Re: Contents of CentOS digest..." Today's Topics: 1. CentOS-announce Digest, Vol 133, Issue 5 (centos-announce-request(a)centos.org) 2. Re: Openshot 2.x (beta) on C7?? (Chris Beattie) 3. Re: Openshot 2.x (beta) on C7?? (Nux!) 4. CentOS 7 and display managers (m.roth(a)5-cent.us) 5. Re: CentOS 7 and display managers (Richard) 6. Re: CentOS 7 and display managers (m.roth(a)5-cent.us) 7. Re: CentOS 7 and display managers (Valeri Galtsev) 8. Re: CentOS 7 and display managers (m.roth(a)5-cent.us) 9. Re: CentOS 7 and display managers (Frank Cox) 10. Re: CentOS 7 and display managers (Scot P. Floess) 11. Centos and automatic update on server (Alessandro Baggi) 12. Re: Centos and automatic update on server (Alice Wonder) 13. Re: Centos and automatic update on server (m.roth(a)5-cent.us) 14. Re: Centos and automatic update on server (m.roth(a)5-cent.us) 15. Re: Centos and automatic update on server (David Nelson) ---------------------------------------------------------------------- Message: 1 Date: Fri, 11 Mar 2016 12:00:02 +0000 From: centos-announce-request(a)centos.org To: centos-announce(a)centos.org Subject: [CentOS] CentOS-announce Digest, Vol 133, Issue 5 Message-ID: <mailman.5.1457697602.15401.centos-announce(a)centos.org> Content-Type: text/plain; charset="us-ascii" Send CentOS-announce mailing list submissions to centos-announce(a)centos.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request(a)centos.org You can reach the person managing the list at centos-announce-owner(a)centos.org When replying, please edit your Subject line so it is more specific than "Re: Contents of CentOS-announce digest..." Today's Topics: 1. CESA-2016:0428 Moderate CentOS 6 libssh2 Security Update (Johnny Hughes) 2. CESA-2016:0428 Moderate CentOS 7 libssh2 Security Update (Johnny Hughes) 3. CESA-2016:C001 ipa and glusterfs Update (Johnny Hughes) 4. CESA-2016:0430 Important CentOS 7 xerces-c Security Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Thu, 10 Mar 2016 12:05:04 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2016:0428 Moderate CentOS 6 libssh2 Security Update Message-ID: <20160310120504.GA20915(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2016:0428 Moderate Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-0428.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 3dd5f11872a5254b65711f88a89b4400c87329ed185af7d69d1d705f94abe13d libssh2-1.4.2-2.el6_7.1.i686.rpm c00dbe2421aada7e7eb2bc87e5160014aae7673e684011783dc34cfa9dd1fcae libssh2-devel-1.4.2-2.el6_7.1.i686.rpm 4be2256b4afe177140a3e87fdc0061d76b3f142ef7264aeb0f9d7a8b5b8fe3b7 libssh2-docs-1.4.2-2.el6_7.1.i686.rpm x86_64: 3dd5f11872a5254b65711f88a89b4400c87329ed185af7d69d1d705f94abe13d libssh2-1.4.2-2.el6_7.1.i686.rpm 729dc417c94e9efbe67f10fe848ce3571945f054bd87fec428179b58dd09bef6 libssh2-1.4.2-2.el6_7.1.x86_64.rpm c00dbe2421aada7e7eb2bc87e5160014aae7673e684011783dc34cfa9dd1fcae libssh2-devel-1.4.2-2.el6_7.1.i686.rpm 2004db099a3302057dbf799c09012d8d9bc1360ddf043ecef2e485f0b3b7fc86 libssh2-devel-1.4.2-2.el6_7.1.x86_64.rpm d2faf5949f869b6b295c3241707e3f40a74f7c1862da57daaaca77aabce535aa libssh2-docs-1.4.2-2.el6_7.1.x86_64.rpm Source: 042b1f294e214d514f5b16332956e168cc168c90a416bcfe4bbc1625636581fc libssh2-1.4.2-2.el6_7.1.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 2 Date: Thu, 10 Mar 2016 12:53:35 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2016:0428 Moderate CentOS 7 libssh2 Security Update Message-ID: <20160310125335.GA39205(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2016:0428 Moderate Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-0428.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 3a25e00b04b27ba59fa17adb97791702dcccb56e130eb5f51651d6fe4fe42f89 libssh2-1.4.3-10.el7_2.1.i686.rpm 1e1f93e449e678597bfdd99bed306c9bb8d5b513ffcaea13d32f5b7434900300 libssh2-1.4.3-10.el7_2.1.x86_64.rpm e76bdc2e93bbb6c4ac8705d50eef1f114ee8b8674e8436063359ac5518b10191 libssh2-devel-1.4.3-10.el7_2.1.i686.rpm b176ee6feaf699eb9ed7466309ab9a9e8d6a7cccaf2e38a15093c484dbd22548 libssh2-devel-1.4.3-10.el7_2.1.x86_64.rpm f76b77eed1cc006c0947abd138084a5808d97b311ebf0e13fbf3504248698f4e libssh2-docs-1.4.3-10.el7_2.1.noarch.rpm Source: 2181b44f7d4636eb0920582a519d1adabae94f34cb49c531a5a2b31e2ad4cf57 libssh2-1.4.3-10.el7_2.1.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 3 Date: Thu, 10 Mar 2016 17:33:15 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2016:C001 ipa and glusterfs Update Message-ID: <20160310173315.GA44278(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and BugFix Advisory 2016:C001 Upstream details at : https://bugs.centos.org/view.php?id=10538 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 96963d839797a7601ef6a4922c94e7ef82b42fcb70533f9a31c43adceee2fb19 glusterfs-3.7.1-16.0.1.el7.centos.x86_64.rpm 0edd9669023af5881cd554a25f11af30c4ad1cec2ac515355a55541ca5afd444 glusterfs-api-3.7.1-16.0.1.el7.centos.x86_64.rpm 1ff4ab3dee2755555db663d522929c45949544d023f0af862e595234eb206b1e glusterfs-api-devel-3.7.1-16.0.1.el7.centos.x86_64.rpm 310cdbc4645b1dff02f7fd1ab15ca11f3d2b65a49e684a3015de264cc9055d2d glusterfs-cli-3.7.1-16.0.1.el7.centos.x86_64.rpm 7ebb8186125e4246b0ba612961872e3a6229351d15c6849c9b4d3d57587005f0 glusterfs-client-xlators-3.7.1-16.0.1.el7.centos.x86_64.rpm fb6f197ac33e79768892ec98548521cba9dbabbaf6dd577a1b9d09c461c344bc glusterfs-devel-3.7.1-16.0.1.el7.centos.x86_64.rpm c50c59c56d305efd2caaf49f9a03a934f60d6d60b9ede5fa6f9c7c41d4d0af3e glusterfs-fuse-3.7.1-16.0.1.el7.centos.x86_64.rpm 8eb112d7a006b9edcf0a6dce79abb6018909c8d9b6baa645f623f5cc4a38a837 glusterfs-libs-3.7.1-16.0.1.el7.centos.x86_64.rpm 959d24d812bb0679000f78d9e17b13476e424bb811b159eea8632d98dd2b46a3 glusterfs-rdma-3.7.1-16.0.1.el7.centos.x86_64.rpm be195e50fcbd3c190e90ecbe5690a664e01bf953ae29be709a4a6aba662736bb ipa-admintools-4.2.0-15.0.1.el7.centos.6.x86_64.rpm 46df2769ffc4e7439ddd6a8a140b0afcb4f45204aa717dbe4fc027dd4c5dda71 ipa-client-4.2.0-15.0.1.el7.centos.6.x86_64.rpm c64d59f138beb4fb8a8a3a200c7696213eebf5c07ac50bb43a7faaadd1b5b9c0 ipa-python-4.2.0-15.0.1.el7.centos.6.x86_64.rpm c20a31a1e4ac386e50c55839ef25b4ad1b3c261d60981da35d7c0d6a7d773ee9 ipa-server-4.2.0-15.0.1.el7.centos.6.x86_64.rpm 9accd7c6001f0f0c02b37eae8538e3045eaaf0f04008d5202fd4007368ba0a64 ipa-server-dns-4.2.0-15.0.1.el7.centos.6.x86_64.rpm 5a5a91ff922ba863eef85723f589d3c940d2e8e529683ca811016688f7bcc95a ipa-server-trust-ad-4.2.0-15.0.1.el7.centos.6.x86_64.rpm 2bc01ee09379a075724d311ff883fac2564ac27826a5b4ee0d4c7c09492a75c4 python-gluster-3.7.1-16.0.1.el7.centos.x86_64.rpm Source: e2ca01712e5f0c52b16a9397597ca15597bccf692881404f695f6cec8f97d925 glusterfs-3.7.1-16.0.1.el7.centos.src.rpm febdf5cf5065c93fb4ba44c02f3ac44bfe1a02b2ff5c489e3a4ec8556c99762f ipa-4.2.0-15.0.1.el7.centos.6.src.rpm NOTE: This rebuild was done to all the packages to have a DIST tag of .el7.centos. -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos at irc.freenode.net ------------------------------ Message: 4 Date: Thu, 10 Mar 2016 17:35:16 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2016:0430 Important CentOS 7 xerces-c Security Update Message-ID: <20160310173516.GA44370(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2016:0430 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-0430.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 0102baca3c47fdb3a16d421d42be3c2e1944ef95cf0bad1b42d01e8fda4d5f83 xerces-c-3.1.1-8.el7_2.i686.rpm 06c92060b15956706630e2d2fd84d72ad71db65151b4435828980d869a7d4f11 xerces-c-3.1.1-8.el7_2.x86_64.rpm 9009f3e814779b14a0e0d6a75fbe555804f2a031e70b15309fe6734205c1c4d2 xerces-c-devel-3.1.1-8.el7_2.i686.rpm dad423ae642a29be177bb4825f71ad3fa5d8db98c4ee658f12094e30c3a88d04 xerces-c-devel-3.1.1-8.el7_2.x86_64.rpm 7fbb6adaf2adb7f3dbf34bf3f2c9e9ea4da1bd61660d84856189583511eec395 xerces-c-doc-3.1.1-8.el7_2.noarch.rpm Source: 95181791907cd7b8bc12c5814cf8e8182aec7dd51faa88224c6f1ec3f4a2336c xerces-c-3.1.1-8.el7_2.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org https://lists.centos.org/mailman/listinfo/centos-announce End of CentOS-announce Digest, Vol 133, Issue 5 *********************************************** ------------------------------ Message: 2 Date: Fri, 11 Mar 2016 15:53:29 +0000 From: Chris Beattie <cbeattie(a)geninfo.com> To: 'CentOS mailing list' <centos(a)centos.org> Subject: Re: [CentOS] Openshot 2.x (beta) on C7?? Message-ID: <C56CB550F3B0CC428EFC662940A0C2E6A70634F8(a)EX10MS2.geninfo.com> Content-Type: text/plain; charset="us-ascii" On 3/11/2016 2:02 AM, Sorin Srbu wrote: >>> Looks like installing openshot 2.x on C7 isn't as trivial >> >> It is not trivial at all. The best way to handle this will be to find the >> required packages in Fedora and rebuild them. > > So what's the easy way? > > Switch to Ubuntu or something? 8-O Maybe Fedora, maybe Ubuntu? It's more time-consuming than hard to build a virtual machine these days, and it's not even that time-consuming. Is there a distro that already has what you want all packaged up? Run it in a VM. Take a snapshot first if you want to try something potentially system-breaking or that's going to spew files everywhere. On a single-user machine, the performance should be within a few percent of running on the bare metal. So, if you test drive some beta software and it doesn't perform well on a VM, it's probably not going to be much better running on a same-spec physical machine. NB: I administer several hundred virtual desktops, so I chugged rather than sipped the virtualization Kool-Aid. :-) -- -Chris ------------------------------ Message: 3 Date: Fri, 11 Mar 2016 16:07:24 +0000 (GMT) From: Nux! <nux(a)li.nux.ro> To: CentOS mailing list <centos(a)centos.org> Subject: Re: [CentOS] Openshot 2.x (beta) on C7?? Message-ID: <1470053539.78961.1457712444140.JavaMail.zimbra(a)li.nux.ro> Content-Type: text/plain; charset=utf-8 Ubuntu in a docker? -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro ----- Original Message ----- > From: "Chris Beattie" <cbeattie(a)geninfo.com> > To: "CentOS mailing list" <centos(a)centos.org> > Sent: Friday, 11 March, 2016 15:53:29 > Subject: Re: [CentOS] Openshot 2.x (beta) on C7?? > On 3/11/2016 2:02 AM, Sorin Srbu wrote: >>>> Looks like installing openshot 2.x on C7 isn't as trivial >>> >>> It is not trivial at all. The best way to handle this will be to find the >>> required packages in Fedora and rebuild them. >> >> So what's the easy way? >> >> Switch to Ubuntu or something? 8-O > > Maybe Fedora, maybe Ubuntu? It's more time-consuming than hard to build a > virtual machine these days, and it's not even that time-consuming. Is there a > distro that already has what you want all packaged up? Run it in a VM. Take a > snapshot first if you want to try something potentially system-breaking or > that's going to spew files everywhere. On a single-user machine, the > performance should be within a few percent of running on the bare metal. So, > if you test drive some beta software and it doesn't perform well on a VM, it's > probably not going to be much better running on a same-spec physical machine. > > NB: I administer several hundred virtual desktops, so I chugged rather than > sipped the virtualization Kool-Aid. :-) > > -- > -Chris > _______________________________________________ > CentOS mailing list > CentOS(a)centos.org > https://lists.centos.org/mailman/listinfo/centos ------------------------------ Message: 4 Date: Fri, 11 Mar 2016 11:33:57 -0500 From: m.roth(a)5-cent.us To: "CentOS" <centos(a)centos.org> Subject: [CentOS] CentOS 7 and display managers Message-ID: <19814dd6ca3be28d95ab776fd52cbb58.squirrel(a)host290.hostmonster.com> Content-Type: text/plain;charset=utf-8 <rant> Dear gnome developers - could you *possibly* be more anti-Unix? I mean, thanks *so* much for trying to turn Linux into Windows or Macs.... </rant> So, now that I've gotten that out, the KDE display manager, on the login screen, easily lets you choose window managers. Gnome utterly refuses to consider such an idea. I've just yum groupinstall "KDE Plasma Workspaces" on one of my user's new system... and I cannot figure out, not in googling, and there's nothing vaguely obvious anywhere, how to change to KDE from gnome. Anyone got a pointer? mark, frustrated ------------------------------ Message: 5 Date: Fri, 11 Mar 2016 16:42:34 +0000 From: Richard <lists-centos(a)listmail.innovate.net> To: CentOS mailing list <centos(a)centos.org> Subject: Re: [CentOS] CentOS 7 and display managers Message-ID: <D655042E52FAB736EED4FCD8(a)ritz.innovate.net> Content-Type: text/plain; charset=us-ascii > Date: Friday, March 11, 2016 11:33:57 -0500 > From: m.roth(a)5-cent.us > > So, now that I've gotten that out, the KDE display manager, on the > login screen, easily lets you choose window managers. Gnome utterly > refuses to consider such an idea. > > I've just yum groupinstall "KDE Plasma Workspaces" on one of my > user's new system... and I cannot figure out, not in googling, and > there's nothing vaguely obvious anywhere, how to change to KDE from > gnome. > With gnome there is a "gear wheel" on the password entry page -- on the right below the password box, next to the "sign in" label. If I select it I can switch between gnome and mate. Does KDE show there as an option? ------------------------------ Message: 6 Date: Fri, 11 Mar 2016 11:46:20 -0500 From: m.roth(a)5-cent.us To: "CentOS mailing list" <centos(a)centos.org> Subject: Re: [CentOS] CentOS 7 and display managers Message-ID: <8f02f00958f1b8f56d9235b4bf7a0564.squirrel(a)host290.hostmonster.com> Content-Type: text/plain;charset=utf-8 Richard wrote: > > >> Date: Friday, March 11, 2016 11:33:57 -0500 >> From: m.roth(a)5-cent.us >> >> So, now that I've gotten that out, the KDE display manager, on the >> login screen, easily lets you choose window managers. Gnome utterly >> refuses to consider such an idea. >> >> I've just yum groupinstall "KDE Plasma Workspaces" on one of my >> user's new system... and I cannot figure out, not in googling, and >> there's nothing vaguely obvious anywhere, how to change to KDE from >> gnome. > > With gnome there is a "gear wheel" on the password entry page -- on > the right below the password box, next to the "sign in" label. If I > select it I can switch between gnome and mate. Does KDE show there as > an option? Fascinating. Not in ours. It displays our issue, and in the upper left, some icons that let you deal with sound, I think, connection, maybe, and I forget what else. mark ------------------------------ Message: 7 Date: Fri, 11 Mar 2016 10:52:12 -0600 (CST) From: "Valeri Galtsev" <galtsev(a)kicp.uchicago.edu> To: "CentOS mailing list" <centos(a)centos.org> Subject: Re: [CentOS] CentOS 7 and display managers Message-ID: <13369.128.135.52.6.1457715132.squirrel(a)cosmo.uchicago.edu> Content-Type: text/plain;charset=iso-8859-1 On Fri, March 11, 2016 10:46 am, m.roth(a)5-cent.us wrote: > Richard wrote: >> >> >>> Date: Friday, March 11, 2016 11:33:57 -0500 >>> From: m.roth(a)5-cent.us >>> >>> So, now that I've gotten that out, the KDE display manager, on the >>> login screen, easily lets you choose window managers. Gnome utterly >>> refuses to consider such an idea. >>> >>> I've just yum groupinstall "KDE Plasma Workspaces" on one of my >>> user's new system... and I cannot figure out, not in googling, and >>> there's nothing vaguely obvious anywhere, how to change to KDE from >>> gnome. >> >> With gnome there is a "gear wheel" on the password entry page -- on >> the right below the password box, next to the "sign in" label. If I >> select it I can switch between gnome and mate. Does KDE show there as >> an option? > > Fascinating. Not in ours. It displays our issue, and in the upper left, > some icons that let you deal with sound, I think, connection, maybe, and I > forget what else. In my case the gear which when clicked of gives you drop down choices of Desktop Environments (DE) installed appears only after I click on particular user. In other words, when user has password field, he also has a gear to click on to choose DE. I hope, this helps. Valeri > > mark > > _______________________________________________ > CentOS mailing list > CentOS(a)centos.org > https://lists.centos.org/mailman/listinfo/centos > ++++++++++++++++++++++++++++++++++++++++ Valeri Galtsev Sr System Administrator Department of Astronomy and Astrophysics Kavli Institute for Cosmological Physics University of Chicago Phone: 773-702-4247 ++++++++++++++++++++++++++++++++++++++++ ------------------------------ Message: 8 Date: Fri, 11 Mar 2016 12:05:49 -0500 From: m.roth(a)5-cent.us To: "CentOS mailing list" <centos(a)centos.org> Subject: Re: [CentOS] CentOS 7 and display managers Message-ID: <3ddbfe316694094045c2b88aa5c3f7d9.squirrel(a)host290.hostmonster.com> Content-Type: text/plain;charset=utf-8 Valeri Galtsev wrote: > On Fri, March 11, 2016 10:46 am, m.roth(a)5-cent.us wrote: >> Richard wrote: >>>> Date: Friday, March 11, 2016 11:33:57 -0500 >>>> From: m.roth(a)5-cent.us >>>> >>>> So, now that I've gotten that out, the KDE display manager, on the >>>> login screen, easily lets you choose window managers. Gnome utterly >>>> refuses to consider such an idea. >>>> >>>> I've just yum groupinstall "KDE Plasma Workspaces" on one of my >>>> user's new system... and I cannot figure out, not in googling, and >>>> there's nothing vaguely obvious anywhere, how to change to KDE from >>>> gnome. >>> >>> With gnome there is a "gear wheel" on the password entry page -- on >>> the right below the password box, next to the "sign in" label. If I >>> select it I can switch between gnome and mate. Does KDE show there as >>> an option? >> >> Fascinating. Not in ours. It displays our issue, and in the upper left, >> some icons that let you deal with sound, I think, connection, maybe, and >> I forget what else. > > In my case the gear which when clicked of gives you drop down choices of > Desktop Environments (DE) installed appears only after I click on > particular user. In other words, when user has password field, he also has > a gear to click on to choose DE. > > I hope, this helps. Ah, that was it, it's not on the screen where you put in your username, it's on the password screen. On the other hand, the easier solution was to just create /etc/sysconfig/desktop, which did not exist, and add the two lines to it. Thanks, folks. mark ------------------------------ Message: 9 Date: Fri, 11 Mar 2016 11:16:38 -0600 From: Frank Cox <theatre(a)melvilletheatre.com> To: centos(a)centos.org Subject: Re: [CentOS] CentOS 7 and display managers Message-ID: <20160311111638.bc745cc6c6aa1e38a7d26885(a)melvilletheatre.com> Content-Type: text/plain; charset=US-ASCII On Fri, 11 Mar 2016 10:52:12 -0600 (CST) Valeri Galtsev wrote: > > Fascinating. Not in ours. It displays our issue, and in the upper left, > > some icons that let you deal with sound, I think, connection, maybe, and I > > forget what else. > > In my case the gear which when clicked of gives you drop down choices of > Desktop Environments (DE) installed appears only after I click on > particular user. In other words, when user has password field, he also has > a gear to click on to choose DE. With gdm the gear only shows up if you have more than one whatever.session file in /usr/share/xsessions. gnome-classic-session and gnome-session-xsession provides this file for gnome sessions, mate-session-manager provides it for mate, and I don't know what provides it for kde. lightdm is a lot more configurable than gdm, and it's easy to use that instead: systemctl disable gdm systemctl enable lightdm systemctl isolate graphical.target Then you can easily configure /etc/lightdm/lightdm-gtk-greeter.conf to do pretty much what you want it to do. I haven't yet figured out how to get rid of the blank photo man beside the password prompt, though. -- MELVILLE THEATRE ~ Real D 3D Digital Cinema ~ www.melvilletheatre.com ------------------------------ Message: 10 Date: Fri, 11 Mar 2016 18:07:29 -0500 (EST) From: "Scot P. Floess" <sfloess(a)nc.rr.com> To: CentOS mailing list <centos(a)centos.org> Subject: Re: [CentOS] CentOS 7 and display managers Message-ID: <alpine.LRH.2.20.1603111805520.2021(a)admin.flossware.com> Content-Type: text/plain; charset=US-ASCII; format=flowed I think its in /usr/share/desktop DISPLAYMANAGER=KDE or something like that On Fri, 11 Mar 2016, m.roth(a)5-cent.us wrote: > <rant> > Dear gnome developers - could you *possibly* be more anti-Unix? I mean, > thanks *so* much for trying to turn Linux into Windows or Macs.... > </rant> > > So, now that I've gotten that out, the KDE display manager, on the login > screen, easily lets you choose window managers. Gnome utterly refuses to > consider such an idea. > > I've just yum groupinstall "KDE Plasma Workspaces" on one of my user's new > system... and I cannot figure out, not in googling, and there's nothing > vaguely obvious anywhere, how to change to KDE from gnome. > > Anyone got a pointer? > > mark, frustrated > > _______________________________________________ > CentOS mailing list > CentOS(a)centos.org > https://lists.centos.org/mailman/listinfo/centos > Scot P. Floess RHCT (Certificate Number 605010084735240) Chief Architect FlossWare http://sourceforge.net/projects/flossware http://flossware.sourceforge.net https://github.com/organizations/FlossWare ------------------------------ Message: 11 Date: Fri, 11 Mar 2016 19:41:54 +0100 From: Alessandro Baggi <alessandro.baggi(a)gmail.com> To: CentOS mailing list <centos(a)centos.org> Subject: [CentOS] Centos and automatic update on server Message-ID: <CA+1R4jQzwzFomCO-sfWeFTsjXA3XNzq3cTKZYET0UY9q8Hjn7Q(a)mail.gmail.com> Content-Type: text/plain; charset=UTF-8 Hi list, I know that there are automatic update with yum-cron but never tried. In my experiences I never did automatic backup because if update was broken my installation will be broken and I wait some time before apply update. Today seems to be that automatic update are used more than before. What do you think about automatic update? It is a good practice on a server? What is your experiences? Thanks in advance. Alessandro ------------------------------ Message: 12 Date: Fri, 11 Mar 2016 10:47:26 -0800 From: Alice Wonder <alice(a)domblogger.net> To: centos(a)centos.org Subject: Re: [CentOS] Centos and automatic update on server Message-ID: <56E312BE.40606(a)domblogger.net> Content-Type: text/plain; charset=windows-1252; format=flowed On 03/11/2016 10:41 AM, Alessandro Baggi wrote: > Hi list, I know that there are automatic update with yum-cron but never > tried. > In my experiences I never did automatic backup because if update was broken > my installation will be broken and I wait some time before apply update. > Today seems to be that automatic update are used more than before. > What do you think about automatic update? It is a good practice on a > server? What is your experiences? > > Thanks in advance. > > Alessandro For me, yum-cron only downloads the updates and e-mails me to let me know they are ready. It does not actually apply them. To apply them, I ssh in and run the command "yum update" and they install fast w/o me needing to wait for the download. That lets me test everything that is critical and make sure it works after the update. ------------------------------ Message: 13 Date: Fri, 11 Mar 2016 13:55:12 -0500 From: m.roth(a)5-cent.us To: "CentOS mailing list" <centos(a)centos.org> Subject: Re: [CentOS] Centos and automatic update on server Message-ID: <f37b628d428c3e57349bbd146e31c2f9.squirrel(a)host290.hostmonster.com> Content-Type: text/plain;charset=utf-8 Alessandro Baggi wrote: > Hi list, I know that there are automatic update with yum-cron but never > tried. > In my experiences I never did automatic backup because if update was > broken > my installation will be broken and I wait some time before apply update. > Today seems to be that automatic update are used more than before. > What do you think about automatic update? It is a good practice on a > server? What is your experiences? > 1. Under *NO* *CIRCUMSTANCES* would I *ever* have that running on a production machine. That's what test boxes are for. 2. If it was my own machine at home, thanks, but I want to wake up, or come home, to a guaranteed working system. I'll update, so I can always undo. ------------------------------ Message: 14 Date: Fri, 11 Mar 2016 13:58:32 -0500 From: m.roth(a)5-cent.us To: "CentOS mailing list" <centos(a)centos.org> Subject: Re: [CentOS] Centos and automatic update on server Message-ID: <4a4e118ea85aafda74981ea49ac92734.squirrel(a)host290.hostmonster.com> Content-Type: text/plain;charset=utf-8 Sorry, <enter> accidentally got hit before I finished. m.roth(a)5-cent.us wrote: > Alessandro Baggi wrote: >> Hi list, I know that there are automatic update with yum-cron but never >> tried. >> In my experiences I never did automatic backup because if update was >> broken >> my installation will be broken and I wait some time before apply update. >> Today seems to be that automatic update are used more than before. >> What do you think about automatic update? It is a good practice on a >> server? What is your experiences? > > 1. Under *NO* *CIRCUMSTANCES* would I *ever* have that running on > a production machine. That's what test boxes are for. > 2. If it was my own machine at home, thanks, but I want to wake up, > or come home, to a guaranteed working system. I'll update, so > I can always undo. 3. Systems like backup servers, etc, sure. They're not critical. 4. We don't do it on users' systems unless we're *sure* that it won't break something. Finally, on systems where there is a concern that something might break, like video drivers, we put excludes in /etc/yum.conf, and disable them under controlled conditions (i.e., one of us is sitting there doing it.) mark ------------------------------ Message: 15 Date: Fri, 11 Mar 2016 11:22:17 -0800 From: David Nelson <david(a)davidnelson.net> To: CentOS mailing list <centos(a)centos.org> Subject: Re: [CentOS] Centos and automatic update on server Message-ID: <ED7CF038-5FCC-4F1A-A956-1510729C28EC(a)davidnelson.net> Content-Type: text/plain; charset=us-ascii Personally I enable yum-cron on relatively simple configs without much that could break, for example a LAMP server. Especially when they are public-facing and thus have greater exposure to security threats. But I don't as often on things that are internal-only and/or have a more complex setup such as running software I had to compile from source. > On Mar 11, 2016, at 10:41, Alessandro Baggi <alessandro.baggi(a)gmail.com> wrote: > > Hi list, I know that there are automatic update with yum-cron but never > tried. > In my experiences I never did automatic backup because if update was broken > my installation will be broken and I wait some time before apply update. > Today seems to be that automatic update are used more than before. > What do you think about automatic update? It is a good practice on a > server? What is your experiences? > > Thanks in advance. > > Alessandro > _______________________________________________ > CentOS mailing list > CentOS(a)centos.org > https://lists.centos.org/mailman/listinfo/centos ------------------------------ _______________________________________________ CentOS mailing list CentOS(a)centos.org https://lists.centos.org/mailman/listinfo/centos End of CentOS Digest, Vol 134, Issue 12 ***************************************

10 years

Re: [CentOS] IPv6 broken on Linode

by Alice Wonder

On 02/16/2017 04:34 AM, Alice Wonder wrote: > On 02/16/2017 04:20 AM, James Hogarth wrote: >> On 16 February 2017 at 12:02, James Hogarth <james.hogarth(a)gmail.com> >> wrote: >>> On 16 February 2017 at 11:46, James Hogarth <james.hogarth(a)gmail.com> >>> wrote: >>>> On 16 February 2017 at 11:35, Alice Wonder <alice(a)domblogger.net> >>>> wrote: >>>>> On 02/16/2017 03:28 AM, James Hogarth wrote: >>>>>> >>>>>> On 16 February 2017 at 10:42, Alice Wonder <alice(a)domblogger.net> >>>>>> wrote: >>>>>>> >>>>>>> On 02/16/2017 02:32 AM, James Hogarth wrote: >>>>>>>> >>>>>>>> >>>>>>>> On 16 February 2017 at 10:17, Alice Wonder >>>>>>>> <alice(a)domblogger.net> wrote: >>>>>>>>> >>>>>>>>> >>>>>>>>> On 02/16/2017 02:03 AM, James Hogarth wrote: >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On 16 February 2017 at 09:09, Alice Wonder <alice(a)domblogger.net> >>>>>>>>>> wrote: >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On 02/16/2017 12:54 AM, Tony Mountifield wrote: >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> In article >>>>>>>>>>>> <4cbb9dc4-f063-3434-b7a1-d4d0e6581b5e(a)domblogger.net>, >>>>>>>>>>>> Alice Wonder <alice(a)domblogger.net> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> https://forum.linode.com/viewtopic.php?f=19&t=14570&p=72785 >>>>>>>>>>>>> >>>>>>>>>>>>> I can not figure out what I need to do. >>>>>>>>>>>>> >>>>>>>>>>>>> Apparently according to linode support, the VM is trying to >>>>>>>>>>>>> grab an >>>>>>>>>>>>> IPv6 >>>>>>>>>>>>> address with some privacy stuff enabled by default causing >>>>>>>>>>>>> it to >>>>>>>>>>>>> not >>>>>>>>>>>>> grab the IPv6 address that is assigned to me. >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> Does the accepted answer at the following link give you any >>>>>>>>>>>> useful >>>>>>>>>>>> hints? >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> http://superuser.com/questions/243669/how-to-avoid-exposing-my-mac-address-… >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> Cheers >>>>>>>>>>>> Tony >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> Not really - I tried >>>>>>>>>>> >>>>>>>>>>> net.ipv6.conf.all.use_tempaddr = 0 >>>>>>>>>>> >>>>>>>>>>> and it still fails to grab the proper IPv6 >>>>>>>>>>> >>>>>>>>>>> -=- >>>>>>>>>>> >>>>>>>>>>> Just in case, I did ask Linode support to verify that my >>>>>>>>>>> hardware >>>>>>>>>>> address >>>>>>>>>>> is >>>>>>>>>>> what it is suppose to be. Still waiting to hear on that. >>>>>>>>>>> >>>>>>>>>>> _______________________________________________ >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> it still is key=value ... it uses the ifcfg- files (via the rh >>>>>>>>>> plugin) and they are all key=value >>>>>>>>>> >>>>>>>>>> It would be helpful if you could paste the journal output >>>>>>>>>> (journalctl >>>>>>>>>> -u NetworkManager) from the time period of attempting to get an >>>>>>>>>> address ... >>>>>>>>>> >>>>>>>>>> also the nmcli conn sh <connection_name> information for the >>>>>>>>>> interface >>>>>>>>>> along with your ifcfg- files >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> ifcfg-lo is the only one that exists on any of the servers - >>>>>>>>> including >>>>>>>>> the >>>>>>>>> VMs that grab the correct IPv6 address. >>>>>>>>> >>>>>>>>> from /sbin/ifconfig -a : >>>>>>>>> >>>>>>>> >>>>>>>> For a start stop using ifconfig ... it's broken at this point on >>>>>>>> linux, especially on multi ip and ipv6 scenarios >>>>>>>> >>>>>>>> Use `ip -6 addr sh` for ipv6 specfic stuff, or just ip addr sh >>>>>>>> to see >>>>>>>> all IP address stuff regardless of family >>>>>>>> >>>>>>>>> eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 >>>>>>>>> inet 178.79.185.217 netmask 255.255.255.0 broadcast >>>>>>>>> 178.79.185.255 >>>>>>>>> inet6 fe80::a8ad:d312:4ef4:7272 prefixlen 64 scopeid >>>>>>>>> 0x20<link> >>>>>>>>> inet6 2a01:7e00::825f:e564:ad53:72fc prefixlen 64 >>>>>>>>> scopeid >>>>>>>>> 0x0<global> >>>>>>>>> ether f2:3c:91:18:8a:7e txqueuelen 1000 (Ethernet) >>>>>>>>> RX packets 9903 bytes 1088621 (1.0 MiB) >>>>>>>>> RX errors 0 dropped 0 overruns 0 frame 0 >>>>>>>>> TX packets 7786 bytes 1087223 (1.0 MiB) >>>>>>>>> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 >>>>>>>>> >>>>>>>>> That hardware address - the 18:8a:7e corresponds with what the >>>>>>>>> IPv6 >>>>>>>>> address >>>>>>>>> is suppose to be. But that's not the address it is grabbing, >>>>>>>>> despite >>>>>>>>> the >>>>>>>>> fact that net.ipv6.conf.all.use_tempaddr = 0 is set. >>>>>>>>> >>>>>>>>> I'm seriously wondering if the real issue is a mis-configured dhcp >>>>>>>>> server >>>>>>>>> in >>>>>>>>> their London facility because nothing makes sense. >>>>>>>>> >>>>>>>>> journalctl -u NetworkManager >>>>>>>>> >>>>>>>>> reports no journal entries found. >>>>>>>>> >>>>>>>> >>>>>>>> So are you not using NetworkManager then? there should be some >>>>>>>> logs ... >>>>>>>> >>>>>>>> >>>>>>>>> I think the problem must be on their end. >>>>>>>>> >>>>>>>>> It all was working fine until they migrated the VM because of a >>>>>>>>> hardware >>>>>>>>> issue, and I suspect now all the hardware address privacy stuff >>>>>>>>> being >>>>>>>>> the >>>>>>>>> issue is barking up the wrong tree because all the reading I >>>>>>>>> have done >>>>>>>>> seems >>>>>>>>> to indicate that with >>>>>>>>> >>>>>>>>> net.ipv6.conf.all.use_tempaddr = 0 >>>>>>>>> >>>>>>>>> that a fake temporary hardware address would not be sent to >>>>>>>>> their dhcp >>>>>>>>> server when obtaining the address, but the real one, that >>>>>>>>> should be >>>>>>>>> fetching >>>>>>>>> my assigned address. >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> Only if the kernel is doing SLAAC ... if other things (eg NM) are >>>>>>>> handling it directly they may act differently ... but then from the >>>>>>>> lack of logs is NM actually handling this? >>>>>>>> >>>>>>>> Does systemctl status NetworkManager show it running and does nmcli >>>>>>>> show anything? >>>>>>>> >>>>>>> >>>>>>> systemctl status NetworkManager >>>>>>> ● NetworkManager.service - Network Manager >>>>>>> Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; >>>>>>> enabled; >>>>>>> vendor preset: enabled) >>>>>>> Active: active (running) since Thu 2017-02-16 08:19:34 UTC; 2h >>>>>>> 19min >>>>>>> ago >>>>>>> >>>>>>> * more stuff * >>>>>>> >>>>>>> nmcli >>>>>>> eth0: connected to Wired connection 1 >>>>>>> "Red Hat Virtio network device" >>>>>>> ethernet (virtio_net), F2:3C:91:18:8A:7E, hw, mtu 1500 >>>>>>> ip4 default, ip6 default >>>>>>> inet4 178.79.185.217/24 >>>>>>> route4 178.79.187.246/32 >>>>>>> inet6 2a01:7e00::825f:e564:ad53:72fc/64 >>>>>>> inet6 fe80::a8ad:d312:4ef4:7272/64 >>>>>>> route6 2a01:7e00::/64 >>>>>>> >>>>>>> * more stuff for other interfaces * >>>>>>> >>>>>>> -=- >>>>>>> >>>>>>> The output of >>>>>>> >>>>>>> sysctl -a | grep net.ipv6 : >>>>>>> >>>>>>> https://librelamp.com/sysctl.txt >>>>>>> >>>>>>> It looks from that like it should not be hiding the real MAC >>>>>>> address. >>>>>>> >>>>>> >>>>>> >>>>>> do nmcli conn show "Wired connection 1" >>>>>> >>>>>> the entries of interest are: >>>>>> >>>>>> ipv6.ip6-privacy >>>>>> ipv6.addr-gen-mode >>>>>> >>>>>> man nm-settings to get what they mean >>>>>> _______________________________________________ >>>>>> CentOS mailing list >>>>>> CentOS(a)centos.org >>>>>> https://lists.centos.org/mailman/listinfo/centos >>>>>> >>>>> >>>>> ipv6.ip6-privacy: -1 (unknown) >>>>> ipv6.addr-gen-mode: stable-privacy >>>>> >>>> >>>> >>>> Okay so from the man page: >>>> >>>> The permitted values are: >>>> "eui64", or >>>> "stable-privacy". If >>>> the property is set to >>>> "eui64", the addresses >>>> will be generated using >>>> the interface tokens >>>> derived from hardware >>>> address. This makes the >>>> host part of the >>>> address to stay >>>> constant, making it >>>> possible to track >>>> host's presence when it >>>> changes networks. The >>>> address changes when >>>> the interface hardware >>>> is replaced. The value >>>> of "stable-privacy" >>>> enables use of >>>> cryptographically >>>> secure hash of a secret >>>> host-specific key along >>>> with the connection >>>> identification and the >>>> network address as >>>> specified by RFC7217. >>>> This makes it >>>> impossible to use the >>>> address track host's >>>> presence, and makes the >>>> address stable when the >>>> network interface >>>> hardware is replaced. >>>> >>>> >>>> I'm not certain (would have to go get changelogs) but I suspect this >>>> was a change at 7.3 with the rebase of NetworkManager >>>> >>>> From what you say you want it sounds like you want eui64 - the one >>>> based entire on the current MAC - whereas the present version is using >>>> stable-privacy to avoid tracking. >>>> >>>> Note that this is distinct and different to ip6-privacy which is >>>> concerned about the automatic generation of temporary addresses to use >>>> for outbound communication. >>> >>> Okay a little more research as I'm curious when it changed from EUI64 >>> by default ... >>> >>> https://blogs.gnome.org/lkundrak/2015/12/03/networkmanager-and-privacy-in-t… >>> >>> >>> NM changed upstream to stable-privacy at 1.2 (the privacy extensions >>> for the external connections were added at 1.0.4) >>> >>> RHEL 7.2 enabled privacy extensions by default: >>> >>> https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/ht… >>> >>> >>> But at that milestone we had NM 1.0.6 >>> >>> At the RHEL 7.3 release NM was rebased to 1.4.0 >>> >>> It was briefly referenced with this change in the 7.3 release notes >>> but honestly it's pretty opaque ... >>> >>> https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/ht… >>> >>> >>> "NetworkManager now supports new device types, improved stacking of >>> virtual devices, LLDP, stable privacy IPv6 addresses (RFC 7217), >>> detects duplicate IPv4 addresses, and controls a host name through >>> systemd-hostnamed. Additionally, the user can set a DHCP timeout >>> property and DNS priorities." >>> >>> Of course unless you knew what RFC 7217 was you'd have no idea this >>> was the effect and there's no note that stable-privacy is the new >>> default behaviour ARGH >>> >>> Disappointingly it's not listed in the "Networking" part of the >>> release notes .... >>> >>> I think I'll raise the priority on my blog for the article I'm >>> intending on the NM rebase ... there are nice things in the rebase >>> like the arbitrary layering of teams, vlans and bridges but then >>> there's unexpected stuff like this as well which should be made more >>> visible. >>> >>> So ... Alice if you want to configure the system with the older EUI64 >>> behaviour then in your ifcfg file for that interface you need >>> IPV6_ADDR_GEN_MODE=eui64 and then restart NetworkManager (or `nmcli >>> conn reload` rather than a full service restart or `nmcli conn mod >>> "Wired Connection 1" ipv6.addr-gen-mode eui64` to do it at the CLI >>> without editing files and needing a connection reload). >> >> Oh and last message about this ... >> >> This was the email to fedora-devel at the time of the NM 1.2 >> introduction: >> >> https://lists.fedoraproject.org/pipermail/devel/2015-November/216754.html >> >> Systems that existed prior to the package didn't change their >> configuration, it was only newly built systems that picked up the new >> default - which might explain what you saw depending on how they >> handled the migration. >> >> There's a good reason that stable-privacy was moved to for automatic >> addressing, but for your setup you may want to set the older eui64 to >> keep things consistent. >> _______________________________________________ >> CentOS mailing list >> CentOS(a)centos.org >> https://lists.centos.org/mailman/listinfo/centos >> > > I suspect this is it. However - > > cat /etc/sysconfig/network-scripts/ifcfg-eth0 > IPV6_ADDR_GEN_MODE=eui64 > > yet it still lists stable-privacy > > But I think that is it, so I'll figure it out. > > Thank you so much. nmcli c modify "Wired connection 1" ipv6.addr-gen-mode eui64 That solved it. Again, thank you so much. Now I need to set that on all my other linodes, which I suspect are only working on IPv6 because they haven't been restarted in a long time.

9 years, 1 month

Re: [CentOS-es] [iptables] denegar rando dependiendo la IP de la fuenta ?

by angel jauregui

@David voy hacer pruebas como me indicas......... El 5 de noviembre de 2013 09:19, David González Romero <dgrvedado(a)gmail.com>escribió: > Hace un forward en el IPtables de que todo lo que vaya al 0/0 port 80, 443, > 21, 20, etc... vaya al 3128... > > Squid no necesita configuacion adicional para https lo soporta > perfectamente bien. Tu puedes controlar los accesos por dominios, o por > IP... escoge el que te guste. > > Saludos, > David > > > El 5 de noviembre de 2013 12:07, angel jauregui > <darkdiabliyo(a)gmail.com>escribió: > > > mmm es qye hay varios listillos que se lo podrian brincar :S... existe la > > problematica que en esa red todos tienen acceso admin a sus propios > > equipos. Generalmente siempre estan conectados con una cuenta de usuario > > dentro del dominio local, pero a veces se logean con la cuenta admin. > > > > Y como soy un prestador de servicios y no quieren invertir, la unica > > solucion es poner el proxy como GW. > > > > Para prevenir retardos coloque en el proxy 2 tarjetas de red 1Gb en > > virtual, y configure el switch cisco como VLAN en los 2 puertos donde > > conecto el proxy. > > > > Saludos ! > > > > > > El 5 de noviembre de 2013 08:52, Ramón Macías Zamora <rmacias(a)rks.ec > > >escribió: > > > > > Efectivamente el problema que tienes es porque está usando proxy > > > transparente. > > > > > > Si no usas proxy transparente si puedes controlarlo con las acl > normales, > > > sin embargo para que funcione el proxy debes configurar manualmente el > > > proxy en los navegadores (En Firefox -> Preferencias -> Avanzado -> > red > > -> > > > Conexión dar click en Configurar -> Configuración Manual del Proxy > > > > > > Saludos > > > > > > -- > > > > > > > > > > > > Ramón Macías Zamora > > > Tecnología, Investigación y Desarrollo > > > www.rks.ec - www.raykasolutions.com > > > Guayaquil - Ecuador > > > msn: ramon_macias(a)hotmail.com > > > skype: ramon_macias > > > UserLinux# 180926 (http://counter.li.org) > > > Cel: 593-8-0192238 > > > Tel: 593 4 6044566 > > > > > > <http://www.raykasolutions.com/> > > > > > > > > > WEB SITES, HOSTINGS, DOMINIOS, MANTENIMIENTO DE EQUIPOS, REDES, > > SERVIDORES > > > LINUX, SOPORTE. > > > > > > > > > 2013/11/5 angel jauregui <darkdiabliyo(a)gmail.com> > > > > > > > @Ramon no entiendo cuando mencionas "forzar a que los usuarios > > configuren > > > > el proxy" ??? > > > > > > > > Los usuarios no tienen que configurar nada, ya que por consecuencia > el > > GW > > > > que se les asigna es el del proxy, el proxy en si actua como > > > > Proxy+Router+firewall. > > > > > > > > No entendi :S > > > > > > > > Saludos ! > > > > > > > > > > > > El 5 de noviembre de 2013 08:38, Ramón Macías Zamora <rmacias(a)rks.ec > > > > >escribió: > > > > > > > > > Yo creo que la solución ahí es forzar a que los usuarios configuren > > el > > > > > proxy en vez de usar proxy transparente que sólo funciona para > http y > > > no > > > > > para https. > > > > > > > > > > Saludos > > > > > > > > > > -- > > > > > > > > > > > > > > > > > > > > Ramón Macías Zamora > > > > > Tecnología, Investigación y Desarrollo > > > > > www.rks.ec - www.raykasolutions.com > > > > > Guayaquil - Ecuador > > > > > msn: ramon_macias(a)hotmail.com > > > > > skype: ramon_macias > > > > > UserLinux# 180926 (http://counter.li.org) > > > > > Cel: 593-8-0192238 > > > > > Tel: 593 4 6044566 > > > > > > > > > > <http://www.raykasolutions.com/> > > > > > > > > > > > > > > > WEB SITES, HOSTINGS, DOMINIOS, MANTENIMIENTO DE EQUIPOS, REDES, > > > > SERVIDORES > > > > > LINUX, SOPORTE. > > > > > > > > > > > > > > > 2013/11/5 angel jauregui <darkdiabliyo(a)gmail.com> > > > > > > > > > > > @David asi tengo la denegacion tambien, pero si el usuario > cambia a > > > > > "https" > > > > > > la pagina ya no es bloqueada, se brinca el filtro. > > > > > > > > > > > > Esto mas que nada porque en IPTables la regla indica que > cualquier > > > cosa > > > > > que > > > > > > va al 80 se rediriga al 3128 (puerto squid), y al cambiar a > HTTPS, > > ya > > > > no > > > > > se > > > > > > aplica la regla. > > > > > > > > > > > > Ahora no puedo quitar el puerto https y forzar solo http, ya que > > > > existen > > > > > > paginas de gobierno que requieren https, y se me vendria el mundo > > > > encima > > > > > > :S. > > > > > > > > > > > > Estoy intentando con estas reglas, ustedes que opinan: > > > > > > > > > > > > *# dar acceso a facebook para una ip fija* > > > > > > shell# iptables -A FORWARD -p tcp -s 10.1.0.10 -d > > IP_CIDR_DEFACEBOOK > > > > -j > > > > > > ACCEPT > > > > > > > > > > > > *# quitar acceso facebook para cualquiera del segmento* > > > > > > shell# iptables -A FORWARD -p tcp -s 10.1.0.0/24 -d > > > IP_CIDR_DEFACEBOOK > > > > > -j > > > > > > REJECT > > > > > > > > > > > > Saludos ! > > > > > > > > > > > > > > > > > > El 5 de noviembre de 2013 05:08, David González Romero > > > > > > <dgrvedado(a)gmail.com>escribió: > > > > > > > > > > > > > Tu has probado esta opción en Squid? > > > > > > > > > > > > > > acl denys url_regex "/etc/squid/denys" > > > > > > > Donde > > > > > > > /etc/squid/denys contiene: > > > > > > > facebook > > > > > > > twitter > > > > > > > ..... > > > > > > > Y luego > > > > > > > http_access deny restric > > > > > > > > > > > > > > Al menos así me funciona a mi. > > > > > > > > > > > > > > > > > > > > > Otra opcion sería comentar la línea "acl SSL_ports port 443" > para > > > > > evitar > > > > > > > conexiones por el 443... > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Saludos, > > > > > > > David > > > > > > > > > > > > > > > > > > > > > > > > > > > > El 4 de noviembre de 2013 18:47, angel jauregui > > > > > > > <darkdiabliyo(a)gmail.com>escribió: > > > > > > > > > > > > > > > Buenas. > > > > > > > > > > > > > > > > Estoy implementando limitaciones en la red, el objetivo es > > quitar > > > > > > acceso > > > > > > > a > > > > > > > > Redes Sociales, en primera instancia tengo SQUID que logra > > tapar > > > el > > > > > > > acceso > > > > > > > > a los sitios mediante http. > > > > > > > > > > > > > > > > El problema es que si los sitios tienes HTTPS, este es > > > > accesible.... > > > > > > > > > > > > > > > > En este caso http://facebook.com esta denegad por Squid. > > > > > > > > Pero al poner https://facebook.com entra exitosamente. > > > > > > > > > > > > > > > > La unica ocurrencia que tuve es usar IPTABLES, asi que puse > > esta > > > > > regla > > > > > > > que > > > > > > > > me esta haceindo cumplir el objetivo "En parte": > > > > > > > > > > > > > > > > iptables -I FORWARD -m tcp -p tcp -m iprange --dst-range > > > > > > > > 173.252.64.0-173.252.127.255 -j REJECT > > > > > > > > > > > > > > > > Donde: 173.252.64.0-173.252.127.255 ---> es el rando CIDr de > > > > > facebook. > > > > > > > > > > > > > > > > El problema *ahora radica* en que no logro hacer que ciertas > > IPs > > > > > > Locales > > > > > > > > (privilegiada - jefes) SI puedan acceder a redes sociales :S > !. > > > > > > > > > > > > > > > > Intente ANTEponiendo esta regla: > > > > > > > > > > > > > > > > iptables -I FORWARD *-s ip_del_jefe *-m tcp -p tcp -m iprange > > > > > > --dst-range > > > > > > > > 173.252.64.0-173.252.127.255 -j ACCEPT > > > > > > > > > > > > > > > > Pero aun asi, se sigue bloqueando el sitio :S.... > > > > > > > > > > > > > > > > *shell# iptables -L -n* > > > > > > > > REJECT tcp -- 0.0.0.0/0 0.0.0.0/0 > > tcp > > > > > > > > destination IP range 173.252.64.0-173.252.127.255 reject-with > > > > > > > > icmp-port-unreachable > > > > > > > > ACCEPT tcp -- 10.1.0.150 0.0.0.0/0 > > tcp > > > > > > > > destination IP range 173.252.64.0-173.252.127.255 > > > > > > > > > > > > > > > > -- > > > > > > > > M.S.I. Angel Haniel Cantu Jauregui. > > > > > > > > > > > > > > > > Celular: (011-52-1)-899-871-17-22 > > > > > > > > E-Mail: angel.cantu(a)sie-group.net > > > > > > > > Web: http://www.sie-group.net/ > > > > > > > > Cd. Reynosa Tamaulipas. > > > > > > > > _______________________________________________ > > > > > > > > CentOS-es mailing list > > > > > > > > CentOS-es(a)centos.org > > > > > > > > http://lists.centos.org/mailman/listinfo/centos-es > > > > > > > > > > > > > > > _______________________________________________ > > > > > > > CentOS-es mailing list > > > > > > > CentOS-es(a)centos.org > > > > > > > http://lists.centos.org/mailman/listinfo/centos-es > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > M.S.I. Angel Haniel Cantu Jauregui. > > > > > > > > > > > > Celular: (011-52-1)-899-871-17-22 > > > > > > E-Mail: angel.cantu(a)sie-group.net > > > > > > Web: http://www.sie-group.net/ > > > > > > Cd. Reynosa Tamaulipas. > > > > > > _______________________________________________ > > > > > > CentOS-es mailing list > > > > > > CentOS-es(a)centos.org > > > > > > http://lists.centos.org/mailman/listinfo/centos-es > > > > > > > > > > > _______________________________________________ > > > > > CentOS-es mailing list > > > > > CentOS-es(a)centos.org > > > > > http://lists.centos.org/mailman/listinfo/centos-es > > > > > > > > > > > > > > > > > > > > > -- > > > > M.S.I. Angel Haniel Cantu Jauregui. > > > > > > > > Celular: (011-52-1)-899-871-17-22 > > > > E-Mail: angel.cantu(a)sie-group.net > > > > Web: http://www.sie-group.net/ > > > > Cd. Reynosa Tamaulipas. > > > > _______________________________________________ > > > > CentOS-es mailing list > > > > CentOS-es(a)centos.org > > > > http://lists.centos.org/mailman/listinfo/centos-es > > > > > > > _______________________________________________ > > > CentOS-es mailing list > > > CentOS-es(a)centos.org > > > http://lists.centos.org/mailman/listinfo/centos-es > > > > > > > > > > > -- > > M.S.I. Angel Haniel Cantu Jauregui. > > > > Celular: (011-52-1)-899-871-17-22 > > E-Mail: angel.cantu(a)sie-group.net > > Web: http://www.sie-group.net/ > > Cd. Reynosa Tamaulipas. > > _______________________________________________ > > CentOS-es mailing list > > CentOS-es(a)centos.org > > http://lists.centos.org/mailman/listinfo/centos-es > > > _______________________________________________ > CentOS-es mailing list > CentOS-es(a)centos.org > http://lists.centos.org/mailman/listinfo/centos-es > -- M.S.I. Angel Haniel Cantu Jauregui. Celular: (011-52-1)-899-871-17-22 E-Mail: angel.cantu(a)sie-group.net Web: http://www.sie-group.net/ Cd. Reynosa Tamaulipas.

12 years, 5 months

Re: [CentOS] Centos 5.8: starting firefox-16.0.1 kills X

by fred smith

On Thu, Oct 18, 2012 at 11:59:16AM +0100, James Pearson wrote: > fred smith wrote: > > This just started happening this evening. > > > > a little history: > > way back last year, or thereabouts, I posted about a weird problem I was > > having. over the course of 2 or 3 days I figured out how to fix it, but > > not what the cause was. the fix amounts to navigating to my user's > > .local/share/mime directory and removing the file named "globs". > > > > So, back in the present: this evening that same problem recurred for > > the 3rd or 4th time since the original event mentioned above. so I > > deleted that file, logged off and back on (without the log off/on, the > > problem still occurs). > > > > Having done that, I went to fire up firefox and KABOOM!! > > X dies and I land back at a login prompt. > > several times. > > every time. > > tried running firefox from a terminal but I don't see anything > > echoed to the terminal before it is blown away. > > > > I still have the tarball from mozilla.org, so I moved aside the directory > > where the firefox runtime stuff is, re-extracted the tarball and it still > > croaks in the same way. > > > > I'd appreciate some ideas to try, if anyone has any. Thanks in advance! > > Are there any backtraces/errors in /var/log/Xorg.*.log* or /var/log/gdm/* ? Oh yes. DUH. Of course. sorry, senior moment causing me to completely blank out on the thought of looking at logs. FWIW, Firefox 14 works fine.... one of the Xorg.<stuff> logs, dated late yesterday, contains this backtrace at the end: Backtrace: 0: /usr/bin/Xorg(xf86SigHandler+0x81) [0x80c9461] 1: [0x845420] 2: /lib/libc.so.6(cfree+0x34) [0x71e8c4] 3: /usr/lib/xorg/modules/extensions/libGLcore.so(_mesa_free+0x1d) [0x22f88d] 4: /usr/lib/xorg/modules/extensions/libGLcore.so(XMesaDestroyVisual+0x1d) [0x37fa5d] 5: /usr/lib/xorg/modules/extensions/libGLcore.so [0x34d952] 6: /usr/lib/xorg/modules/extensions/libglx.so(__glXResetScreens+0x37) [0xf8c217] 7: /usr/lib/xorg/modules/extensions/libglx.so [0xf8b45c] 8: /usr/bin/Xorg(CloseDownExtensions+0x46) [0x8097856] 9: /usr/bin/Xorg(main+0x49f) [0x807091f] 10: /lib/libc.so.6(__libc_start_main+0xdc) [0x6cae9c] 11: /usr/bin/Xorg(FontFileCompleteXLFD+0x205) [0x806fc01] Fatal server error: Caught signal 11. Server aborting in another posting in this thread, Tru Hyunh asked about the general X setup. Vanilla Centos 5.8 except it's using a recent Nvidia driver to run a GeForce 9800GT card. (NVIDIA-Linux-x86-290.10). Other info, I don't know what would be helpful. I'll paste in here the contents of the X.org log file from which the backtrace above came, in case that might be helpful. Or, ask any specific question and I'll try to answer. X Window System Version 7.1.1 Release Date: 12 May 2006 X Protocol Version 11, Revision 0, Release 7.1.1 Build Operating System: Linux 2.6.18-53.el5 i686 Red Hat, Inc. Current Operating System: Linux fcshome.stoneham.ma.us 2.6.18-308.16.1.el5PAE #1 SMP Tue Oct 2 22:49:17 EDT 2012 i686 Build Date: 04 October 2012 Build ID: xorg-x11-server 1.1.1-48.91.el5_8.2 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Wed Oct 17 20:49:08 2012 (==) Using config file: "/etc/X11/xorg.conf" (==) ServerLayout "single head configuration" (**) |-->Screen "Screen0" (0) (**) | |-->Monitor "Monitor0" (**) | |-->Device "Videocard0" (**) |-->Input Device "Mouse0" (**) |-->Input Device "Keyboard0" (==) FontPath set to: unix/:7100, built-ins (==) RgbPath set to "/usr/share/X11/rgb" (**) ModulePath set to "/usr/lib/xorg/modules" (==) Max clients allowed: 512, resource mask: 0xfffff (II) Open ACPI successful (/var/run/acpid.socket) (II) Module ABI versions: X.Org ANSI C Emulation: 0.3 X.Org Video Driver: 1.0 X.Org XInput driver : 0.6 X.Org Server Extension : 0.3 X.Org Font Renderer : 0.5 (II) Loader running on linux (II) LoadModule: "bitmap" (II) Loading /usr/lib/xorg/modules/fonts/libbitmap.so (II) Module bitmap: vendor="X.Org Foundation" compiled for 7.1.1, module version = 1.0.0 Module class: X.Org Font Renderer ABI class: X.Org Font Renderer, version 0.5 (II) Loading font Bitmap (II) LoadModule: "pcidata" (II) Loading /usr/lib/xorg/modules/libpcidata.so (II) Module pcidata: vendor="X.Org Foundation" compiled for 7.1.1, module version = 1.0.0 ABI class: X.Org Video Driver, version 1.0 (++) using VT number 7 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 1002,5957 card 1002,5957 rev 00 class 06,00,00 hdr 00 (II) PCI: 00:02:0: chip 1002,5978 card 0000,0000 rev 00 class 06,04,00 hdr 01 (II) PCI: 00:0a:0: chip 1002,597f card 0000,0000 rev 00 class 06,04,00 hdr 01 (II) PCI: 00:11:0: chip 1002,4391 card 1458,b002 rev 00 class 01,06,01 hdr 00 (II) PCI: 00:12:0: chip 1002,4397 card 1458,5004 rev 00 class 0c,03,10 hdr 80 (II) PCI: 00:12:1: chip 1002,4398 card 1458,5004 rev 00 class 0c,03,10 hdr 00 (II) PCI: 00:12:2: chip 1002,4396 card 1458,5004 rev 00 class 0c,03,20 hdr 00 (II) PCI: 00:13:0: chip 1002,4397 card 1458,5004 rev 00 class 0c,03,10 hdr 80 (II) PCI: 00:13:1: chip 1002,4398 card 1458,5004 rev 00 class 0c,03,10 hdr 00 (II) PCI: 00:13:2: chip 1002,4396 card 1458,5004 rev 00 class 0c,03,20 hdr 00 (II) PCI: 00:14:0: chip 1002,4385 card 1458,4385 rev 3a class 0c,05,00 hdr 80 (II) PCI: 00:14:1: chip 1002,439c card 1458,5002 rev 00 class 01,01,8a hdr 00 (II) PCI: 00:14:2: chip 1002,4383 card 1458,a022 rev 00 class 04,03,00 hdr 00 (II) PCI: 00:14:3: chip 1002,439d card 1002,439d rev 00 class 06,01,00 hdr 80 (II) PCI: 00:14:4: chip 1002,4384 card 0000,0000 rev 00 class 06,04,01 hdr 81 (II) PCI: 00:14:5: chip 1002,4399 card 1458,5004 rev 00 class 0c,03,10 hdr 00 (II) PCI: 00:18:0: chip 1022,1200 card 0000,0000 rev 00 class 06,00,00 hdr 80 (II) PCI: 00:18:1: chip 1022,1201 card 0000,0000 rev 00 class 06,00,00 hdr 80 (II) PCI: 00:18:2: chip 1022,1202 card 0000,0000 rev 00 class 06,00,00 hdr 80 (II) PCI: 00:18:3: chip 1022,1203 card 0000,0000 rev 00 class 06,00,00 hdr 80 (II) PCI: 00:18:4: chip 1022,1204 card 0000,0000 rev 00 class 06,00,00 hdr 80 (II) PCI: 01:00:0: chip 10de,0614 card 1462,1721 rev a2 class 03,00,00 hdr 00 (II) PCI: 02:00:0: chip 10ec,8168 card 1458,e000 rev 02 class 02,00,00 hdr 00 (II) PCI: End of PCI scan (II) Host-to-PCI bridge: (II) Bus 0: bridge is at (0:0:0), (0,0,3), BCTRL: 0x0008 (VGA_EN is set) (II) Bus 0 I/O range: [0] -1 0 0x00000000 - 0x0000ffff (0x10000) IX[B] (II) Bus 0 non-prefetchable memory range: [0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B] (II) Bus 0 prefetchable memory range: [0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B] (II) PCI-to-PCI bridge: (II) Bus 1: bridge is at (0:2:0), (0,1,1), BCTRL: 0x0008 (VGA_EN is set) (II) Bus 1 I/O range: [0] -1 0 0x0000e000 - 0x0000efff (0x1000) IX[B] (II) Bus 1 non-prefetchable memory range: [0] -1 0 0xf8000000 - 0xfbffffff (0x4000000) MX[B] (II) Bus 1 prefetchable memory range: [0] -1 0 0xd0000000 - 0xdfffffff (0x10000000) MX[B] (II) PCI-to-PCI bridge: (II) Bus 2: bridge is at (0:10:0), (0,2,2), BCTRL: 0x0000 (VGA_EN is cleared) (II) Bus 2 I/O range: [0] -1 0 0x0000d000 - 0x0000dfff (0x1000) IX[B] (II) Bus 2 non-prefetchable memory range: [0] -1 0 0xfdc00000 - 0xfdcfffff (0x100000) MX[B] (II) Bus 2 prefetchable memory range: [0] -1 0 0xfdf00000 - 0xfdffffff (0x100000) MX[B] (II) PCI-to-ISA bridge: (II) Bus -1: bridge is at (0:20:3), (0,-1,-1), BCTRL: 0x0008 (VGA_EN is set) (II) Subtractive PCI-to-PCI bridge: (II) Bus 3: bridge is at (0:20:4), (0,3,3), BCTRL: 0x0000 (VGA_EN is cleared) (II) Bus 3 I/O range: [0] -1 0 0x0000c000 - 0x0000cfff (0x1000) IX[B] (II) Bus 3 non-prefetchable memory range: [0] -1 0 0xfde00000 - 0xfdefffff (0x100000) MX[B] (II) Bus 3 prefetchable memory range: [0] -1 0 0xfdd00000 - 0xfddfffff (0x100000) MX[B] (--) PCI:*(1:0:0) nVidia Corporation unknown chipset (0x0614) rev 162, Mem @ 0xfa000000/24, 0xd0000000/28, 0xf8000000/25, I/O @ 0xef00/7 (II) Addressable bus resource ranges are [0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B] [1] -1 0 0x00000000 - 0x0000ffff (0x10000) IX[B] (II) OS-reported resource ranges: [0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [5] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] (II) PCI Memory resource overlap reduced 0xe0000000 from 0xe0000000 to 0xdfffffff (II) Active PCI resource ranges: [0] -1 0 0xfdfe0000 - 0xfdfeffff (0x10000) MX[B] [1] -1 0 0xfdfff000 - 0xfdffffff (0x1000) MX[B] [2] -1 0 0xfe028000 - 0xfe028fff (0x1000) MX[B] [3] -1 0 0xfe024000 - 0xfe027fff (0x4000) MX[B] [4] -1 0 0xfe029000 - 0xfe0290ff (0x100) MX[B] [5] -1 0 0xfe02a000 - 0xfe02afff (0x1000) MX[B] [6] -1 0 0xfe02b000 - 0xfe02bfff (0x1000) MX[B] [7] -1 0 0xfe02c000 - 0xfe02c0ff (0x100) MX[B] [8] -1 0 0xfe02d000 - 0xfe02dfff (0x1000) MX[B] [9] -1 0 0xfe02e000 - 0xfe02efff (0x1000) MX[B] [10] -1 0 0xfe02f000 - 0xfe02f3ff (0x400) MX[B] [11] -1 0 0xe0000000 - 0xdfffffff (0x0) MX[B]O [12] -1 0 0xf8000000 - 0xf9ffffff (0x2000000) MX[B](B) [13] -1 0 0xd0000000 - 0xdfffffff (0x10000000) MX[B](B) [14] -1 0 0xfa000000 - 0xfaffffff (0x1000000) MX[B](B) [15] -1 0 0x0000de00 - 0x0000deff (0x100) IX[B] [16] -1 0 0x0000fa00 - 0x0000fa0f (0x10) IX[B] [17] -1 0 0x0000fb00 - 0x0000fb0f (0x10) IX[B] [18] -1 0 0x0000fc00 - 0x0000fc03 (0x4) IX[B] [19] -1 0 0x0000fd00 - 0x0000fd07 (0x8) IX[B] [20] -1 0 0x0000fe00 - 0x0000fe03 (0x4) IX[B] [21] -1 0 0x0000ff00 - 0x0000ff07 (0x8) IX[B] [22] -1 0 0x0000ef00 - 0x0000ef7f (0x80) IX[B](B) (II) Active PCI resource ranges after removing overlaps: [0] -1 0 0xfdfe0000 - 0xfdfeffff (0x10000) MX[B] [1] -1 0 0xfdfff000 - 0xfdffffff (0x1000) MX[B] [2] -1 0 0xfe028000 - 0xfe028fff (0x1000) MX[B] [3] -1 0 0xfe024000 - 0xfe027fff (0x4000) MX[B] [4] -1 0 0xfe029000 - 0xfe0290ff (0x100) MX[B] [5] -1 0 0xfe02a000 - 0xfe02afff (0x1000) MX[B] [6] -1 0 0xfe02b000 - 0xfe02bfff (0x1000) MX[B] [7] -1 0 0xfe02c000 - 0xfe02c0ff (0x100) MX[B] [8] -1 0 0xfe02d000 - 0xfe02dfff (0x1000) MX[B] [9] -1 0 0xfe02e000 - 0xfe02efff (0x1000) MX[B] [10] -1 0 0xfe02f000 - 0xfe02f3ff (0x400) MX[B] [11] -1 0 0xe0000000 - 0xdfffffff (0x0) MX[B]O [12] -1 0 0xf8000000 - 0xf9ffffff (0x2000000) MX[B](B) [13] -1 0 0xd0000000 - 0xdfffffff (0x10000000) MX[B](B) [14] -1 0 0xfa000000 - 0xfaffffff (0x1000000) MX[B](B) [15] -1 0 0x0000de00 - 0x0000deff (0x100) IX[B] [16] -1 0 0x0000fa00 - 0x0000fa0f (0x10) IX[B] [17] -1 0 0x0000fb00 - 0x0000fb0f (0x10) IX[B] [18] -1 0 0x0000fc00 - 0x0000fc03 (0x4) IX[B] [19] -1 0 0x0000fd00 - 0x0000fd07 (0x8) IX[B] [20] -1 0 0x0000fe00 - 0x0000fe03 (0x4) IX[B] [21] -1 0 0x0000ff00 - 0x0000ff07 (0x8) IX[B] [22] -1 0 0x0000ef00 - 0x0000ef7f (0x80) IX[B](B) (II) OS-reported resource ranges after removing overlaps with PCI: [0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [5] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] (II) All system resource ranges: [0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [4] -1 0 0xfdfe0000 - 0xfdfeffff (0x10000) MX[B] [5] -1 0 0xfdfff000 - 0xfdffffff (0x1000) MX[B] [6] -1 0 0xfe028000 - 0xfe028fff (0x1000) MX[B] [7] -1 0 0xfe024000 - 0xfe027fff (0x4000) MX[B] [8] -1 0 0xfe029000 - 0xfe0290ff (0x100) MX[B] [9] -1 0 0xfe02a000 - 0xfe02afff (0x1000) MX[B] [10] -1 0 0xfe02b000 - 0xfe02bfff (0x1000) MX[B] [11] -1 0 0xfe02c000 - 0xfe02c0ff (0x100) MX[B] [12] -1 0 0xfe02d000 - 0xfe02dfff (0x1000) MX[B] [13] -1 0 0xfe02e000 - 0xfe02efff (0x1000) MX[B] [14] -1 0 0xfe02f000 - 0xfe02f3ff (0x400) MX[B] [15] -1 0 0xe0000000 - 0xdfffffff (0x0) MX[B]O [16] -1 0 0xf8000000 - 0xf9ffffff (0x2000000) MX[B](B) [17] -1 0 0xd0000000 - 0xdfffffff (0x10000000) MX[B](B) [18] -1 0 0xfa000000 - 0xfaffffff (0x1000000) MX[B](B) [19] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [20] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] [21] -1 0 0x0000de00 - 0x0000deff (0x100) IX[B] [22] -1 0 0x0000fa00 - 0x0000fa0f (0x10) IX[B] [23] -1 0 0x0000fb00 - 0x0000fb0f (0x10) IX[B] [24] -1 0 0x0000fc00 - 0x0000fc03 (0x4) IX[B] [25] -1 0 0x0000fd00 - 0x0000fd07 (0x8) IX[B] [26] -1 0 0x0000fe00 - 0x0000fe03 (0x4) IX[B] [27] -1 0 0x0000ff00 - 0x0000ff07 (0x8) IX[B] [28] -1 0 0x0000ef00 - 0x0000ef7f (0x80) IX[B](B) (II) LoadModule: "glx" (II) Loading /usr/lib/xorg/modules/extensions/libglx.so (II) Module glx: vendor="X.Org Foundation" compiled for 7.1.1, module version = 1.0.0 ABI class: X.Org Server Extension, version 0.3 (==) AIGLX enabled (II) Loading extension GLX (II) LoadModule: "extmod" (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so (II) Module extmod: vendor="X.Org Foundation" compiled for 7.1.1, module version = 1.0.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 0.3 (II) Loading extension SHAPE (II) Loading extension MIT-SUNDRY-NONSTANDARD (II) Loading extension BIG-REQUESTS (II) Loading extension SYNC (II) Loading extension MIT-SCREEN-SAVER (II) Loading extension XC-MISC (II) Loading extension XFree86-VidModeExtension (II) Loading extension XFree86-Misc (II) Loading extension XFree86-DGA (II) Loading extension DPMS (II) Loading extension TOG-CUP (II) Loading extension Extended-Visual-Information (II) Loading extension XVideo (II) Loading extension XVideo-MotionCompensation (II) Loading extension X-Resource (II) LoadModule: "nvidia" (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so (II) Module nvidia: vendor="NVIDIA Corporation" compiled for 4.0.2, module version = 1.0.0 Module class: X.Org Video Driver (II) LoadModule: "mouse" (II) Loading /usr/lib/xorg/modules/input/mouse_drv.so (II) Module mouse: vendor="X.Org Foundation" compiled for 7.1.1, module version = 1.1.1 Module class: X.Org XInput Driver ABI class: X.Org XInput driver, version 0.6 (II) LoadModule: "kbd" (II) Loading /usr/lib/xorg/modules/input/kbd_drv.so (II) Module kbd: vendor="X.Org Foundation" compiled for 7.1.1, module version = 1.1.0 Module class: X.Org XInput Driver ABI class: X.Org XInput driver, version 0.6 (II) NVIDIA dlloader X Driver 290.10 Wed Nov 16 19:29:07 PST 2011 (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs (II) Primary Device is: PCI 01:00:0 (--) Assigning device section with no busID to primary device (--) Chipset NVIDIA GPU found (II) Loading sub module "fb" (II) LoadModule: "fb" (II) Loading /usr/lib/xorg/modules/libfb.so (II) Module fb: vendor="X.Org Foundation" compiled for 7.1.1, module version = 1.0.0 ABI class: X.Org ANSI C Emulation, version 0.3 (II) Loading sub module "wfb" (II) LoadModule: "wfb" (II) Loading /usr/lib/xorg/modules/libwfb.so (II) Module wfb: vendor="NVIDIA Corporation" compiled for 7.1.99.2, module version = 1.0.0 (II) Loading sub module "ramdac" (II) LoadModule: "ramdac" (II) Loading /usr/lib/xorg/modules/libramdac.so (II) Module ramdac: vendor="X.Org Foundation" compiled for 7.1.1, module version = 0.1.0 ABI class: X.Org Video Driver, version 1.0 (II) resource ranges after xf86ClaimFixedResources() call: [0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [4] -1 0 0xfdfe0000 - 0xfdfeffff (0x10000) MX[B] [5] -1 0 0xfdfff000 - 0xfdffffff (0x1000) MX[B] [6] -1 0 0xfe028000 - 0xfe028fff (0x1000) MX[B] [7] -1 0 0xfe024000 - 0xfe027fff (0x4000) MX[B] [8] -1 0 0xfe029000 - 0xfe0290ff (0x100) MX[B] [9] -1 0 0xfe02a000 - 0xfe02afff (0x1000) MX[B] [10] -1 0 0xfe02b000 - 0xfe02bfff (0x1000) MX[B] [11] -1 0 0xfe02c000 - 0xfe02c0ff (0x100) MX[B] [12] -1 0 0xfe02d000 - 0xfe02dfff (0x1000) MX[B] [13] -1 0 0xfe02e000 - 0xfe02efff (0x1000) MX[B] [14] -1 0 0xfe02f000 - 0xfe02f3ff (0x400) MX[B] [15] -1 0 0xe0000000 - 0xdfffffff (0x0) MX[B]O [16] -1 0 0xf8000000 - 0xf9ffffff (0x2000000) MX[B](B) [17] -1 0 0xd0000000 - 0xdfffffff (0x10000000) MX[B](B) [18] -1 0 0xfa000000 - 0xfaffffff (0x1000000) MX[B](B) [19] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [20] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] [21] -1 0 0x0000de00 - 0x0000deff (0x100) IX[B] [22] -1 0 0x0000fa00 - 0x0000fa0f (0x10) IX[B] [23] -1 0 0x0000fb00 - 0x0000fb0f (0x10) IX[B] [24] -1 0 0x0000fc00 - 0x0000fc03 (0x4) IX[B] [25] -1 0 0x0000fd00 - 0x0000fd07 (0x8) IX[B] [26] -1 0 0x0000fe00 - 0x0000fe03 (0x4) IX[B] [27] -1 0 0x0000ff00 - 0x0000ff07 (0x8) IX[B] [28] -1 0 0x0000ef00 - 0x0000ef7f (0x80) IX[B](B) (II) resource ranges after probing: [0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [4] -1 0 0xfdfe0000 - 0xfdfeffff (0x10000) MX[B] [5] -1 0 0xfdfff000 - 0xfdffffff (0x1000) MX[B] [6] -1 0 0xfe028000 - 0xfe028fff (0x1000) MX[B] [7] -1 0 0xfe024000 - 0xfe027fff (0x4000) MX[B] [8] -1 0 0xfe029000 - 0xfe0290ff (0x100) MX[B] [9] -1 0 0xfe02a000 - 0xfe02afff (0x1000) MX[B] [10] -1 0 0xfe02b000 - 0xfe02bfff (0x1000) MX[B] [11] -1 0 0xfe02c000 - 0xfe02c0ff (0x100) MX[B] [12] -1 0 0xfe02d000 - 0xfe02dfff (0x1000) MX[B] [13] -1 0 0xfe02e000 - 0xfe02efff (0x1000) MX[B] [14] -1 0 0xfe02f000 - 0xfe02f3ff (0x400) MX[B] [15] -1 0 0xe0000000 - 0xdfffffff (0x0) MX[B]O [16] -1 0 0xf8000000 - 0xf9ffffff (0x2000000) MX[B](B) [17] -1 0 0xd0000000 - 0xdfffffff (0x10000000) MX[B](B) [18] -1 0 0xfa000000 - 0xfaffffff (0x1000000) MX[B](B) [19] 0 0 0x000a0000 - 0x000affff (0x10000) MS[B] [20] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[B] [21] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[B] [22] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [23] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] [24] -1 0 0x0000de00 - 0x0000deff (0x100) IX[B] [25] -1 0 0x0000fa00 - 0x0000fa0f (0x10) IX[B] [26] -1 0 0x0000fb00 - 0x0000fb0f (0x10) IX[B] [27] -1 0 0x0000fc00 - 0x0000fc03 (0x4) IX[B] [28] -1 0 0x0000fd00 - 0x0000fd07 (0x8) IX[B] [29] -1 0 0x0000fe00 - 0x0000fe03 (0x4) IX[B] [30] -1 0 0x0000ff00 - 0x0000ff07 (0x8) IX[B] [31] -1 0 0x0000ef00 - 0x0000ef7f (0x80) IX[B](B) [32] 0 0 0x000003b0 - 0x000003bb (0xc) IS[B] [33] 0 0 0x000003c0 - 0x000003df (0x20) IS[B] (II) Setting vga for screen 0. (**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32 (==) NVIDIA(0): RGB weight 888 (==) NVIDIA(0): Default visual is TrueColor (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0) (**) NVIDIA(0): Option "NoLogo" "true" (**) NVIDIA(0): Option "AddARGBGLXVisuals" "True" (**) NVIDIA(0): Option "DisableGLXRootClipping" "True" (**) Oct 17 20:49:08 NVIDIA(0): Enabling 2D acceleration (EE) Oct 17 20:49:08 NVIDIA(0): Failed to initialize the GLX module; please check in your X (EE) Oct 17 20:49:08 NVIDIA(0): log file that the GLX module has been loaded in your X (EE) Oct 17 20:49:08 NVIDIA(0): server, and that the module is the NVIDIA GLX module. If (EE) Oct 17 20:49:08 NVIDIA(0): you continue to encounter problems, Please try (EE) Oct 17 20:49:08 NVIDIA(0): reinstalling the NVIDIA driver. (II) Oct 17 20:49:09 NVIDIA(GPU-0): Display (Samsung SyncMaster (DFP-0)) does not support NVIDIA (II) Oct 17 20:49:09 NVIDIA(GPU-0): 3D Vision stereo. (II) Oct 17 20:49:09 NVIDIA(0): NVIDIA GPU GeForce 9800 GT (G92) at PCI:1:0:0 (GPU-0) (--) Oct 17 20:49:09 NVIDIA(0): Memory: 524288 kBytes (--) Oct 17 20:49:09 NVIDIA(0): VideoBIOS: 62.92.69.00.08 (II) Oct 17 20:49:09 NVIDIA(0): Detected PCI Express Link width: 16X (--) Oct 17 20:49:09 NVIDIA(0): Interlaced video modes are supported on this GPU (--) Oct 17 20:49:09 NVIDIA(0): Connected display device(s) on GeForce 9800 GT at PCI:1:0:0 (--) Oct 17 20:49:09 NVIDIA(0): Samsung SyncMaster (DFP-0) (--) Oct 17 20:49:09 NVIDIA(0): Samsung SyncMaster (DFP-0): 330.0 MHz maximum pixel clock (--) Oct 17 20:49:09 NVIDIA(0): Samsung SyncMaster (DFP-0): Internal Dual Link TMDS (**) Oct 17 20:49:09 NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID has been (**) Oct 17 20:49:09 NVIDIA(0): enabled on all display devices. (WW) Oct 17 20:49:09 NVIDIA(0): The EDID for Samsung SyncMaster (DFP-0) contradicts itself: (WW) Oct 17 20:49:09 NVIDIA(0): mode "1920x1080" is specified in the EDID; however, the (WW) Oct 17 20:49:09 NVIDIA(0): EDID's valid VertRefresh range (56.000-60.000 Hz) would (WW) Oct 17 20:49:09 NVIDIA(0): exclude this mode's VertRefresh (50.0 Hz); ignoring (WW) Oct 17 20:49:09 NVIDIA(0): VertRefresh check for mode "1920x1080". (WW) Oct 17 20:49:09 NVIDIA(0): The EDID for Samsung SyncMaster (DFP-0) contradicts itself: (WW) Oct 17 20:49:09 NVIDIA(0): mode "1280x720" is specified in the EDID; however, the (WW) Oct 17 20:49:09 NVIDIA(0): EDID's valid VertRefresh range (56.000-60.000 Hz) would (WW) Oct 17 20:49:09 NVIDIA(0): exclude this mode's VertRefresh (50.0 Hz); ignoring (WW) Oct 17 20:49:09 NVIDIA(0): VertRefresh check for mode "1280x720". (WW) Oct 17 20:49:09 NVIDIA(0): The EDID for Samsung SyncMaster (DFP-0) contradicts itself: (WW) Oct 17 20:49:09 NVIDIA(0): mode "720x576" is specified in the EDID; however, the (WW) Oct 17 20:49:09 NVIDIA(0): EDID's valid VertRefresh range (56.000-60.000 Hz) would (WW) Oct 17 20:49:09 NVIDIA(0): exclude this mode's VertRefresh (50.0 Hz); ignoring (WW) Oct 17 20:49:09 NVIDIA(0): VertRefresh check for mode "720x576". (WW) Oct 17 20:49:09 NVIDIA(0): The EDID for Samsung SyncMaster (DFP-0) contradicts itself: (WW) Oct 17 20:49:09 NVIDIA(0): mode "1920x1080" is specified in the EDID; however, the (WW) Oct 17 20:49:09 NVIDIA(0): EDID's valid VertRefresh range (56.000-60.000 Hz) would (WW) Oct 17 20:49:09 NVIDIA(0): exclude this mode's VertRefresh (50.0 Hz); ignoring (WW) Oct 17 20:49:09 NVIDIA(0): VertRefresh check for mode "1920x1080". (WW) Oct 17 20:49:09 NVIDIA(0): The EDID for Samsung SyncMaster (DFP-0) contradicts itself: (WW) Oct 17 20:49:09 NVIDIA(0): mode "1280x720" is specified in the EDID; however, the (WW) Oct 17 20:49:09 NVIDIA(0): EDID's valid VertRefresh range (56.000-60.000 Hz) would (WW) Oct 17 20:49:09 NVIDIA(0): exclude this mode's VertRefresh (50.0 Hz); ignoring (WW) Oct 17 20:49:09 NVIDIA(0): VertRefresh check for mode "1280x720". (WW) Oct 17 20:49:09 NVIDIA(0): The EDID for Samsung SyncMaster (DFP-0) contradicts itself: (WW) Oct 17 20:49:09 NVIDIA(0): mode "720x576" is specified in the EDID; however, the (WW) Oct 17 20:49:09 NVIDIA(0): EDID's valid VertRefresh range (56.000-60.000 Hz) would (WW) Oct 17 20:49:09 NVIDIA(0): exclude this mode's VertRefresh (50.0 Hz); ignoring (WW) Oct 17 20:49:09 NVIDIA(0): VertRefresh check for mode "720x576". (II) Oct 17 20:49:09 NVIDIA(0): Assigned Display Device: DFP-0 (II) Oct 17 20:49:09 NVIDIA(0): Validated modes: (II) Oct 17 20:49:09 NVIDIA(0): "2048x1152" (II) Oct 17 20:49:09 NVIDIA(0): "1280x1024" (II) Oct 17 20:49:09 NVIDIA(0): "1280x960" (II) Oct 17 20:49:09 NVIDIA(0): "1280x800" (II) Oct 17 20:49:09 NVIDIA(0): "1152x864" (II) Oct 17 20:49:09 NVIDIA(0): "1152x768" (II) Oct 17 20:49:09 NVIDIA(0): "1024x768" (II) Oct 17 20:49:09 NVIDIA(0): "800x600" (II) Oct 17 20:49:09 NVIDIA(0): "640x480" (II) Oct 17 20:49:09 NVIDIA(0): Virtual screen size determined to be 2048 x 1152 (--) Oct 17 20:49:09 NVIDIA(0): DPI set to (101, 100); computed from "UseEdidDpi" X config (--) Oct 17 20:49:09 NVIDIA(0): option (**) Oct 17 20:49:09 NVIDIA(0): Enabling 32-bit ARGB GLX visuals. (--) Depth 24 pixmap format is 32 bpp (II) do I need RAC? No, I don't. (II) resource ranges after preInit: [0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [4] -1 0 0xfdfe0000 - 0xfdfeffff (0x10000) MX[B] [5] -1 0 0xfdfff000 - 0xfdffffff (0x1000) MX[B] [6] -1 0 0xfe028000 - 0xfe028fff (0x1000) MX[B] [7] -1 0 0xfe024000 - 0xfe027fff (0x4000) MX[B] [8] -1 0 0xfe029000 - 0xfe0290ff (0x100) MX[B] [9] -1 0 0xfe02a000 - 0xfe02afff (0x1000) MX[B] [10] -1 0 0xfe02b000 - 0xfe02bfff (0x1000) MX[B] [11] -1 0 0xfe02c000 - 0xfe02c0ff (0x100) MX[B] [12] -1 0 0xfe02d000 - 0xfe02dfff (0x1000) MX[B] [13] -1 0 0xfe02e000 - 0xfe02efff (0x1000) MX[B] [14] -1 0 0xfe02f000 - 0xfe02f3ff (0x400) MX[B] [15] -1 0 0xe0000000 - 0xdfffffff (0x0) MX[B]O [16] -1 0 0xf8000000 - 0xf9ffffff (0x2000000) MX[B](B) [17] -1 0 0xd0000000 - 0xdfffffff (0x10000000) MX[B](B) [18] -1 0 0xfa000000 - 0xfaffffff (0x1000000) MX[B](B) [19] 0 0 0x000a0000 - 0x000affff (0x10000) MS[B] [20] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[B] [21] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[B] [22] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [23] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] [24] -1 0 0x0000de00 - 0x0000deff (0x100) IX[B] [25] -1 0 0x0000fa00 - 0x0000fa0f (0x10) IX[B] [26] -1 0 0x0000fb00 - 0x0000fb0f (0x10) IX[B] [27] -1 0 0x0000fc00 - 0x0000fc03 (0x4) IX[B] [28] -1 0 0x0000fd00 - 0x0000fd07 (0x8) IX[B] [29] -1 0 0x0000fe00 - 0x0000fe03 (0x4) IX[B] [30] -1 0 0x0000ff00 - 0x0000ff07 (0x8) IX[B] [31] -1 0 0x0000ef00 - 0x0000ef7f (0x80) IX[B](B) [32] 0 0 0x000003b0 - 0x000003bb (0xc) IS[B] [33] 0 0 0x000003c0 - 0x000003df (0x20) IS[B] (II) Oct 17 20:49:09 NVIDIA: Using 768.00 MB of virtual memory for indirect memory access. (II) Oct 17 20:49:09 NVIDIA(0): Setting mode "2048x1152" (II) Loading extension NV-GLX (==) NVIDIA(0): Disabling shared memory pixmaps (==) NVIDIA(0): Backing store disabled (==) NVIDIA(0): Silken mouse enabled (**) Option "dpms" (**) NVIDIA(0): DPMS enabled (II) Loading extension NV-CONTROL (WW) Oct 17 20:49:09 NVIDIA(0): Option "TwinViewXineramaInfoOrder" requested "CRT", but no (WW) Oct 17 20:49:09 NVIDIA(0): such display device could be found, or all display devices (WW) Oct 17 20:49:09 NVIDIA(0): by that name are currently unavailable. (WW) Oct 17 20:49:09 NVIDIA(0): Option "TwinViewXineramaInfoOrder" requested "TV", but no such (WW) Oct 17 20:49:09 NVIDIA(0): display device could be found, or all display devices by (WW) Oct 17 20:49:09 NVIDIA(0): that name are currently unavailable. (==) RandR enabled (II) Setting vga for screen 0. (II) Initializing built-in extension MIT-SHM (II) Initializing built-in extension XInputExtension (II) Initializing built-in extension XTEST (II) Initializing built-in extension XKEYBOARD (II) Initializing built-in extension XC-APPGROUP (II) Initializing built-in extension SECURITY (II) Initializing built-in extension XINERAMA (II) Initializing built-in extension XFIXES (II) Initializing built-in extension XFree86-Bigfont (II) Initializing built-in extension RENDER (II) Initializing built-in extension RANDR (II) Initializing built-in extension COMPOSITE (II) Initializing built-in extension DAMAGE (II) Initializing built-in extension XEVIE (EE) AIGLX: DRI module not loaded (II) Loading local sub module "GLcore" (II) LoadModule: "GLcore" (II) Loading /usr/lib/xorg/modules/extensions/libGLcore.so (II) Module GLcore: vendor="X.Org Foundation" compiled for 7.1.1, module version = 1.0.0 ABI class: X.Org Server Extension, version 0.3 (II) GLX: Initialized MESA-PROXY GL provider for screen 0 (**) Option "Protocol" "auto" (**) Mouse0: Device: "/dev/input/mice" (**) Mouse0: Protocol: "auto" (**) Option "CorePointer" (**) Mouse0: Core Pointer (**) Option "Device" "/dev/input/mice" (**) Option "Emulate3Buttons" "no" (**) Option "ZAxisMapping" "4 5" (**) Mouse0: ZAxisMapping: buttons 4 and 5 (**) Mouse0: Buttons: 9 (**) Option "CoreKeyboard" (**) Keyboard0: Core Keyboard (**) Option "Protocol" "standard" (**) Keyboard0: Protocol: standard (**) Option "AutoRepeat" "500 30" (**) Option "XkbRules" "xorg" (**) Keyboard0: XkbRules: "xorg" (**) Option "XkbModel" "pc105" (**) Keyboard0: XkbModel: "pc105" (**) Option "XkbLayout" "us" (**) Keyboard0: XkbLayout: "us" (**) Option "CustomKeycodes" "off" (**) Keyboard0: CustomKeycodes disabled (II) XINPUT: Adding extended input device "Keyboard0" (type: KEYBOARD) (II) XINPUT: Adding extended input device "Mouse0" (type: MOUSE) (--) Mouse0: PnP-detected protocol: "ExplorerPS/2" (II) Mouse0: ps2EnableDataReporting: succeeded Backtrace: 0: /usr/bin/Xorg(xf86SigHandler+0x81) [0x80c9461] 1: [0x845420] 2: /lib/libc.so.6(cfree+0x34) [0x71e8c4] 3: /usr/lib/xorg/modules/extensions/libGLcore.so(_mesa_free+0x1d) [0x22f88d] 4: /usr/lib/xorg/modules/extensions/libGLcore.so(XMesaDestroyVisual+0x1d) [0x37fa5d] 5: /usr/lib/xorg/modules/extensions/libGLcore.so [0x34d952] 6: /usr/lib/xorg/modules/extensions/libglx.so(__glXResetScreens+0x37) [0xf8c217] 7: /usr/lib/xorg/modules/extensions/libglx.so [0xf8b45c] 8: /usr/bin/Xorg(CloseDownExtensions+0x46) [0x8097856] 9: /usr/bin/Xorg(main+0x49f) [0x807091f] 10: /lib/libc.so.6(__libc_start_main+0xdc) [0x6cae9c] 11: /usr/bin/Xorg(FontFileCompleteXLFD+0x205) [0x806fc01] Fatal server error: Caught signal 11. Server aborting > > James Pearson > _______________________________________________ > CentOS mailing list > CentOS(a)centos.org > http://lists.centos.org/mailman/listinfo/centos -- ---- Fred Smith -- fredex(a)fcshome.stoneham.ma.us ----------------------------- I can do all things through Christ who strengthens me. ------------------------------ Philippians 4:13 -------------------------------

13 years, 5 months

Re: [CentOS] yum update / kernal update failed - remove or repair

by Simon Matter

> I have managed to find out what happened in the yum update and it turns > out it was a mess. It looks like the server ran out of memory in the > middle and things then started to fail. Any advice on how to recover from > this would be greatly appreciated I may sound old school but my suggestion would be to forget yum aka dnf for now and just fix the real stuff using rpm. I always considered yum a wrapper for rpm (I wish it was) and was able to fix a system with rpm alone and later make yum behave again. It usually boils down to analyzing what is in the rpm db and what is on the filesystem actually. You can then remove invalid rpm db content as well as wrong filesystem content. It's a bit of work and you may create helper scripts as needed but you can fix almost everything that way. Regards, Simon > > The log below shows: > > [root@vps2 ~]# yum history info 22 > Loaded plugins: fastestmirror, langpacks > Repository mariadb is listed more than once in the configuration > Transaction ID : 22 > Begin time : Sun Jan 19 18:15:33 2020 > Begin rpmdb : 795:6c5cd82e3ada047c7071fea1524f41fd13fab6a1 > End time : 19:19:32 2020 (63 minutes) > End rpmdb : 801:6d1b278ccbeef6f68ff494cb28eaed5c7be4124b > User : root <root> > Return-Code : Failure: 1 > Command Line : update > Transaction performed with: > Installed rpm-4.11.3-40.el7.x86_64 @anaconda > Installed yum-3.4.3-163.el7.centos.noarch @anaconda > Installed yum-plugin-fastestmirror-1.1.31-52.el7.noarch @anaconda > Packages Altered: > Updated MariaDB-client-10.4.10-1.el7.centos.x86_64 @mariadb > Update 10.4.11-1.el7.centos.x86_64 @mariadb > Updated MariaDB-common-10.4.10-1.el7.centos.x86_64 @mariadb > Update 10.4.11-1.el7.centos.x86_64 @mariadb > Updated MariaDB-compat-10.4.10-1.el7.centos.x86_64 @mariadb > Update 10.4.11-1.el7.centos.x86_64 @mariadb > ** Updated MariaDB-server-10.4.10-1.el7.centos.x86_64 @mariadb > Loading mirror speeds from cached hostfile > * base: mirror.as29550.net > * epel: www.mirrorservice.org > * extras: www.mirrorservice.org > * remi-php73: mirrors.ukfast.co.uk > * remi-safe: mirrors.ukfast.co.uk > * updates: www.mirrorservice.org > ** Update 10.4.11-1.el7.centos.x86_64 @?mariadb > ** Updated MariaDB-shared-10.4.10-1.el7.centos.x86_64 @mariadb > Update 10.4.11-1.el7.centos.x86_64 @mariadb > ** Updated ca-certificates-2018.2.22-70.0.el7_5.noarch @anaconda > ** Update 2019.2.32-76.el7_7.noarch @?updates > Updated certbot-0.39.0-1.el7.noarch @epel > Update 1.0.0-1.el7.noarch @epel > Updated clamav-0.101.4-1.el7.x86_64 @epel > Update 0.101.5-1.el7.x86_64 @epel > Updated clamav-data-0.101.4-1.el7.noarch @epel > Update 0.101.5-1.el7.noarch @epel > Updated clamav-devel-0.101.4-1.el7.x86_64 @epel > Update 0.101.5-1.el7.x86_64 @epel > Updated clamav-filesystem-0.101.4-1.el7.noarch @epel > Update 0.101.5-1.el7.noarch @epel > Updated clamav-lib-0.101.4-1.el7.x86_64 @epel > Update 0.101.5-1.el7.x86_64 @epel > Updated clamav-update-0.101.4-1.el7.x86_64 @epel > Update 0.101.5-1.el7.x86_64 @epel > Updated clamd-0.101.4-1.el7.x86_64 @epel > Update 0.101.5-1.el7.x86_64 @epel > Updated curl-7.29.0-54.el7.x86_64 @anaconda > Update 7.29.0-54.el7_7.1.x86_64 @updates > Updated fail2ban-0.9.7-1.el7.noarch @epel > Update 0.10.4-1.el7.noarch @epel > Updated fail2ban-firewalld-0.9.7-1.el7.noarch @epel > Update 0.10.4-1.el7.noarch @epel > Updated fail2ban-sendmail-0.9.7-1.el7.noarch @epel > Update 0.10.4-1.el7.noarch @epel > Updated fail2ban-server-0.9.7-1.el7.noarch @epel > Update 0.10.4-1.el7.noarch @epel > Updated fail2ban-systemd-0.9.7-1.el7.noarch @epel > Update 0.10.4-1.el7.noarch @epel > Updated fribidi-1.0.2-1.el7.x86_64 @anaconda > Update 1.0.2-1.el7_7.1.x86_64 @updates > Updated iproute-4.11.0-25.el7.x86_64 @anaconda > Update 4.11.0-25.el7_7.2.x86_64 @updates > Install kernel-3.10.0-1062.9.1.el7.x86_64 @updates > Updated kernel-headers-3.10.0-1062.4.3.el7.x86_64 @updates > Update 3.10.0-1062.9.1.el7.x86_64 @updates > Updated kernel-tools-3.10.0-1062.4.3.el7.x86_64 @updates > Update 3.10.0-1062.9.1.el7.x86_64 @updates > Updated kernel-tools-libs-3.10.0-1062.4.3.el7.x86_64 @updates > Update 3.10.0-1062.9.1.el7.x86_64 @updates > Updated libblkid-2.23.2-61.el7.x86_64 @anaconda > Update 2.23.2-61.el7_7.1.x86_64 @updates > Updated libcurl-7.29.0-54.el7.x86_64 @anaconda > Update 7.29.0-54.el7_7.1.x86_64 @updates > Updated libgs-9.25-2.el7_7.2.x86_64 @updates > Update 9.25-2.el7_7.3.x86_64 @updates > Updated libmount-2.23.2-61.el7.x86_64 @anaconda > Update 2.23.2-61.el7_7.1.x86_64 @updates > Updated libsmartcols-2.23.2-61.el7.x86_64 @anaconda > Update 2.23.2-61.el7_7.1.x86_64 @updates > Updated libsss_idmap-1.16.4-21.el7.x86_64 @anaconda > Update 1.16.4-21.el7_7.1.x86_64 @updates > Updated libsss_nss_idmap-1.16.4-21.el7.x86_64 @anaconda > Update 1.16.4-21.el7_7.1.x86_64 @updates > Updated libuuid-2.23.2-61.el7.x86_64 @anaconda > Update 2.23.2-61.el7_7.1.x86_64 @updates > Updated libwebp7-1.0.2-1.el7.remi.x86_64 @remi-safe > Update 1.0.3-1.el7.remi.x86_64 @remi-safe > ** Updated microcode_ctl-2:2.1-53.3.el7_7.x86_64 @updates > Update 2:2.1-53.7.el7_7.x86_64 @updates > Updated nss-3.44.0-4.el7.x86_64 @anaconda > Update 3.44.0-7.el7_7.x86_64 @updates > Updated nss-softokn-3.44.0-5.el7.x86_64 @anaconda > Update 3.44.0-8.el7_7.x86_64 @updates > Updated nss-softokn-freebl-3.44.0-5.el7.x86_64 @anaconda > Update 3.44.0-8.el7_7.x86_64 @updates > Updated nss-sysinit-3.44.0-4.el7.x86_64 @anaconda > Update 3.44.0-7.el7_7.x86_64 @updates > Updated nss-tools-3.44.0-4.el7.x86_64 @anaconda > Update 3.44.0-7.el7_7.x86_64 @updates > Updated nss-util-3.44.0-3.el7.x86_64 @anaconda > Update 3.44.0-4.el7_7.x86_64 @updates > Updated numactl-libs-2.0.12-3.el7.x86_64 @anaconda > Update 2.0.12-3.el7_7.1.x86_64 @updates > Updated pgdg-redhat-repo-42.0-5.noarch > @/pgdg-centos10-10-2.noarch > Update 42.0-6.noarch @pgdg10 > Updated php-7.3.12-1.el7.remi.x86_64 @remi-php73 > Update 7.3.13-1.el7.remi.x86_64 @remi-php73 > Updated php-cli-7.3.12-1.el7.remi.x86_64 @remi-php73 > Update 7.3.13-1.el7.remi.x86_64 @remi-php73 > Updated php-common-7.3.12-1.el7.remi.x86_64 @remi-php73 > Update 7.3.13-1.el7.remi.x86_64 @remi-php73 > Updated php-gd-7.3.12-1.el7.remi.x86_64 @remi-php73 > Update 7.3.13-1.el7.remi.x86_64 @remi-php73 > Updated php-json-7.3.12-1.el7.remi.x86_64 @remi-php73 > Update 7.3.13-1.el7.remi.x86_64 @remi-php73 > Updated php-ldap-7.3.12-1.el7.remi.x86_64 @remi-php73 > Update 7.3.13-1.el7.remi.x86_64 @remi-php73 > Updated php-mysqlnd-7.3.12-1.el7.remi.x86_64 @remi-php73 > Update 7.3.13-1.el7.remi.x86_64 @remi-php73 > Updated php-odbc-7.3.12-1.el7.remi.x86_64 @remi-php73 > Update 7.3.13-1.el7.remi.x86_64 @remi-php73 > Updated php-pdo-7.3.12-1.el7.remi.x86_64 @remi-php73 > Update 7.3.13-1.el7.remi.x86_64 @remi-php73 > ** Updated php-pear-1:1.10.10-2.el7.remi.noarch @remi-php70 > ** Update 1:1.10.10-4.el7.remi.noarch @?remi-php73 > Updated php-pgsql-7.3.12-1.el7.remi.x86_64 @remi-php73 > Update 7.3.13-1.el7.remi.x86_64 @remi-php73 > Updated php-process-7.3.12-1.el7.remi.x86_64 @remi-php73 > Update 7.3.13-1.el7.remi.x86_64 @remi-php73 > Updated php-xml-7.3.12-1.el7.remi.x86_64 @remi-php73 > Update 7.3.13-1.el7.remi.x86_64 @remi-php73 > Updated php-xmlrpc-7.3.12-1.el7.remi.x86_64 @remi-php73 > Update 7.3.13-1.el7.remi.x86_64 @remi-php73 > Updated postgresql10-10.11-1PGDG.rhel7.x86_64 @pgdg10 > Update 10.11-2PGDG.rhel7.x86_64 @pgdg10 > Updated postgresql10-contrib-10.11-1PGDG.rhel7.x86_64 @pgdg10 > Update 10.11-2PGDG.rhel7.x86_64 @pgdg10 > Updated postgresql10-libs-10.11-1PGDG.rhel7.x86_64 @pgdg10 > Update 10.11-2PGDG.rhel7.x86_64 @pgdg10 > ** Updated postgresql10-server-10.11-1PGDG.rhel7.x86_64 @pgdg10 > Update 10.11-2PGDG.rhel7.x86_64 @pgdg10 > ** Updated proftpd-1.3.5e-7.el7.x86_64 @epel > Update 1.3.5e-8.el7.x86_64 @epel > Updated python-perf-3.10.0-1062.4.3.el7.x86_64 @updates > Update 3.10.0-1062.9.1.el7.x86_64 @updates > Updated python-requests-2.6.0-7.el7_7.noarch @updates > Update 2.6.0-8.el7_7.noarch @updates > Updated python2-acme-0.39.0-1.el7.noarch @epel > Update 1.0.0-1.el7.noarch @epel > Updated python2-certbot-0.39.0-1.el7.noarch @epel > Update 1.0.0-1.el7.noarch @epel > Updated python2-certbot-apache-0.39.0-1.el7.noarch @epel > Update 1.0.0-1.el7.noarch @epel > Updated selinux-policy-3.13.1-252.el7.1.noarch @updates > Update 3.13.1-252.el7_7.6.noarch @updates > Updated selinux-policy-targeted-3.13.1-252.el7.1.noarch @updates > Update 3.13.1-252.el7_7.6.noarch @updates > Updated sos-3.7-7.el7.centos.noarch @updates > Update 3.7-10.el7.centos.noarch @updates > ** Updated sssd-client-1.16.4-21.el7.x86_64 @anaconda > Update 1.16.4-21.el7_7.1.x86_64 @updates > Updated tcpdump-14:4.9.2-4.el7.x86_64 @anaconda > Update 14:4.9.2-4.el7_7.1.x86_64 @updates > Updated util-linux-2.23.2-61.el7.x86_64 @anaconda > Update 2.23.2-61.el7_7.1.x86_64 @updates > Scriptlet output: > 1 error: Couldn't fork %post(libsss_idmap-1.16.4-21.el7_7.1.x86_64): > Cannot allocate memory > 2 error: Couldn't fork > %post(libsss_nss_idmap-1.16.4-21.el7_7.1.x86_64): Cannot allocate > memory > 3 error: Couldn't fork %pre(ca-certificates-2019.2.32-76.el7_7.noarch): > Cannot allocate memory > 4 error: ca-certificates-2019.2.32-76.el7_7.noarch: install failed > 5 error: Couldn't fork %post(certbot-1.0.0-1.el7.noarch): Cannot > allocate memory > 6 error: Couldn't fork > %pre(MariaDB-server-10.4.11-1.el7.centos.x86_64): Cannot allocate > memory > 7 error: MariaDB-server-10.4.11-1.el7.centos.x86_64: install failed > 8 error: Couldn't fork %post(sssd-client-1.16.4-21.el7_7.1.x86_64): > Cannot allocate memory > 9 error: Couldn't fork %post(kernel-tools-3.10.0-1062.9.1.el7.x86_64): > Cannot allocate memory > 10 error: Couldn't fork %pre(php-pear-1:1.10.10-4.el7.remi.noarch): > Cannot allocate memory > 11 error: php-pear-1:1.10.10-4.el7.remi.noarch: install failed > 12 warning: /etc/clamd.d/scan.conf created as > /etc/clamd.d/scan.conf.rpmnew > 13 error: Couldn't fork > %triggerin(microcode_ctl-2:2.1-53.7.el7_7.x86_64): Cannot allocate > memory > 14 error: php-pear-1:1.10.10-2.el7.remi.noarch: erase skipped > 15 error: MariaDB-server-10.4.10-1.el7.centos.x86_64: erase skipped > 16 error: Couldn't fork > %preun(MariaDB-shared-10.4.10-1.el7.centos.x86_64): Cannot allocate > memory > 17 error: MariaDB-shared-10.4.10-1.el7.centos.x86_64: erase failed > 18 error: Couldn't fork > %postun(MariaDB-compat-10.4.10-1.el7.centos.x86_64): Cannot allocate > memory > 19 error: ca-certificates-2018.2.22-70.0.el7_5.noarch: erase skipped > 20 error: Couldn't fork %preun(microcode_ctl-2:2.1-53.3.el7_7.x86_64): > Cannot allocate memory > 21 error: microcode_ctl-2:2.1-53.3.el7_7.x86_64: erase failed > 22 error: Couldn't fork > %preun(postgresql10-server-10.11-1PGDG.rhel7.x86_64): Cannot allocate > memory > 23 error: postgresql10-server-10.11-1PGDG.rhel7.x86_64: erase failed > 24 error: Couldn't fork %postun(libmount-2.23.2-61.el7.x86_64): Cannot > allocate memory > 25 error: Couldn't fork %preun(sssd-client-1.16.4-21.el7.x86_64): Cannot > allocate memory > 26 error: sssd-client-1.16.4-21.el7.x86_64: erase failed > 27 error: Couldn't fork %postun(libblkid-2.23.2-61.el7.x86_64): Cannot > allocate memory > 28 error: Couldn't fork %postun(postgresql10-10.11-1PGDG.rhel7.x86_64): > Cannot allocate memory > 29 error: Couldn't fork %postun(clamav-lib-0.101.4-1.el7.x86_64): Cannot > allocate memory > 30 error: Couldn't fork > %postun(kernel-tools-3.10.0-1062.4.3.el7.x86_64): Cannot allocate memory > 31 error: Couldn't fork %postun(libcurl-7.29.0-54.el7.x86_64): Cannot > allocate memory > 32 error: Couldn't fork %postun(nss-3.44.0-4.el7.x86_64): Cannot > allocate memory > 33 error: Couldn't fork %postun(nss-softokn-3.44.0-5.el7.x86_64): Cannot > allocate memory > 34 error: Couldn't fork %postun(nss-util-3.44.0-3.el7.x86_64): Cannot > allocate memory > 35 error: Couldn't fork > %postun(postgresql10-libs-10.11-1PGDG.rhel7.x86_64): Cannot allocate > memory > 36 error: Couldn't fork %postun(libuuid-2.23.2-61.el7.x86_64): Cannot > allocate memory > 37 error: Couldn't fork %postun(libsss_idmap-1.16.4-21.el7.x86_64): > Cannot allocate memory > 38 error: Couldn't fork %postun(libsss_nss_idmap-1.16.4-21.el7.x86_64): > Cannot allocate memory > 39 error: Couldn't fork %postun(libsmartcols-2.23.2-61.el7.x86_64): > Cannot allocate memory > 40 error: Couldn't fork %postun(libwebp7-1.0.2-1.el7.remi.x86_64): > Cannot allocate memory > 41 error: Couldn't fork %postun(fribidi-1.0.2-1.el7.x86_64): Cannot > allocate memory > 42 error: Couldn't fork %preun(proftpd-1.3.5e-7.el7.x86_64): Cannot > allocate memory > 43 error: proftpd-1.3.5e-7.el7.x86_64: erase failed > 44 error: Couldn't fork %postun(numactl-libs-2.0.12-3.el7.x86_64): > Cannot allocate memory > 45 error: Couldn't fork %posttrans(kernel-3.10.0-1062.9.1.el7.x86_64): > Cannot allocate memory > 46 error: Couldn't fork > %posttrans(microcode_ctl-2:2.1-53.7.el7_7.x86_64): Cannot allocate > memory > history info > [root@vps2 ~]# > _______________________________________________ > CentOS mailing list > CentOS(a)centos.org > https://lists.centos.org/mailman/listinfo/centos >

6 years, 2 months

Re: [CentOS] Apache 2.2

by Devraj Mukherjee

Hi Dag, Also notice the following messages Oct 1 06:42:21 charlie kernel: protections[]: 0 0 0 Oct 1 06:42:21 charlie kernel: Node 0 DMA: 0*4kB 1*8kB 0*16kB 2*32kB 3*64kB 0*128kB 2*256kB 1*512kB 0*1024kB 1*2048kB 2*4096kB = 11528kB Oct 1 06:42:21 charlie kernel: Node 0 Normal: 0*4kB 5*8kB 6*16kB 2*32kB 1*64kB 0*128kB 1*256kB 3*512kB 0*1024kB 0*2048kB 0*4096kB = 2056kB Oct 1 06:42:21 charlie kernel: Node 0 HighMem: empty Oct 1 06:42:21 charlie kernel: Swap cache: add 2889479, delete 2889467, find 905741/1017940, race 0+15 Oct 1 06:42:21 charlie kernel: Free swap: 0kB Oct 1 06:42:21 charlie kernel: 1179648 pages of RAM Oct 1 06:42:21 charlie kernel: 168514 reserved pages Oct 1 06:42:21 charlie kernel: 626131 pages shared Oct 1 06:42:21 charlie kernel: 12 pages swap cached Oct 1 06:42:21 charlie kernel: Out of Memory: Killed process 1999 (httpd). Oct 1 07:01:29 charlie kernel: oom-killer: gfp_mask=0x1d2 Oct 1 07:01:30 charlie kernel: Mem-info: Oct 1 07:01:30 charlie kernel: Node 0 DMA per-cpu: Oct 1 07:01:30 charlie kernel: cpu 0 hot: low 2, high 6, batch 1 Oct 1 07:01:30 charlie kernel: cpu 0 cold: low 0, high 2, batch 1 Oct 1 07:01:30 charlie kernel: cpu 1 hot: low 2, high 6, batch 1 Oct 1 07:01:30 charlie kernel: cpu 1 cold: low 0, high 2, batch 1 Oct 1 07:01:30 charlie kernel: cpu 2 hot: low 2, high 6, batch 1 Oct 1 07:01:30 charlie kernel: cpu 2 cold: low 0, high 2, batch 1 Oct 1 07:01:30 charlie kernel: cpu 3 hot: low 2, high 6, batch 1 Oct 1 07:01:30 charlie kernel: cpu 3 cold: low 0, high 2, batch 1 Oct 1 07:01:30 charlie kernel: Node 0 Normal per-cpu: Oct 1 07:01:30 charlie kernel: cpu 0 hot: low 32, high 96, batch 16 Oct 1 07:01:31 charlie kernel: cpu 0 cold: low 0, high 32, batch 16 Oct 1 07:01:31 charlie kernel: cpu 1 hot: low 32, high 96, batch 16 Oct 1 07:01:31 charlie kernel: cpu 1 cold: low 0, high 32, batch 16 Oct 1 07:01:31 charlie kernel: cpu 2 hot: low 32, high 96, batch 16 Oct 1 07:01:33 charlie kernel: cpu 2 cold: low 0, high 32, batch 16 Oct 1 07:04:15 charlie kernel: cpu 3 hot: low 32, high 96, batch 16 Oct 1 07:24:04 charlie kernel: cpu 3 cold: low 0, high 32, batch 16 Oct 1 07:48:23 charlie kernel: Node 0 HighMem per-cpu: empty Oct 1 07:48:23 charlie kernel: Oct 1 07:48:23 charlie kernel: Free pages: 13640kB (0kB HighMem) Oct 1 07:48:23 charlie kernel: Active:10282 inactive:956850 dirty:0 writeback:0 unstable:0 free:3410 slab:9415 mapped:967735 pagetables:23309 Oct 1 07:48:23 charlie kernel: Node 0 DMA free:11528kB min:4kB low:8kB high:12kB active:0kB inactive:0kB present:16384kB pages_scanned:2977 a ll_unreclaimable? yes Oct 1 07:48:23 charlie kernel: protections[]: 0 0 0 Oct 1 07:48:23 charlie kernel: Node 0 Normal free:2112kB min:2160kB low:4320kB high:6480kB active:42928kB inactive:3825600kB present:4702208k B pages_scanned:5985945 all_unreclaimable? yes Oct 1 07:48:23 charlie kernel: protections[]: 0 0 0 Oct 1 07:48:23 charlie kernel: Node 0 HighMem free:0kB min:128kB low:256kB high:384kB active:0kB inactive:0kB present:0kB pages_scanned:0 all _unreclaimable? no Oct 1 07:48:23 charlie kernel: protections[]: 0 0 0 Oct 1 07:48:23 charlie kernel: Node 0 DMA: 0*4kB 1*8kB 0*16kB 2*32kB 3*64kB 0*128kB 2*256kB 1*512kB 0*1024kB 1*2048kB 2*4096kB = 11528kB Oct 1 07:48:28 charlie kernel: Node 0 Normal: 12*4kB 232*8kB 13*16kB 0*32kB 0*64kB 0*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 2112k B Oct 1 07:48:28 charlie kernel: Node 0 HighMem: empty Oct 1 07:48:28 charlie kernel: Swap cache: add 2902771, delete 2902761, find 906274/1018789, race 0+20 Oct 1 07:48:29 charlie kernel: Free swap: 0kB Oct 1 07:48:29 charlie kernel: 1179648 pages of RAM Oct 1 07:49:47 charlie kernel: 168514 reserved pages Oct 1 07:49:47 charlie kernel: 664563 pages shared Oct 1 07:49:47 charlie kernel: 10 pages swap cached Oct 1 07:49:47 charlie kernel: Out of Memory: Killed process 1996 (httpd). Oct 1 07:49:47 charlie kernel: oom-killer: gfp_mask=0x1d2 Oct 1 07:49:47 charlie kernel: Mem-info: Oct 1 07:49:48 charlie kernel: Node 0 DMA per-cpu: Oct 1 07:49:48 charlie kernel: cpu 0 hot: low 2, high 6, batch 1 Oct 1 07:49:48 charlie kernel: cpu 0 cold: low 0, high 2, batch 1 Oct 1 07:49:48 charlie kernel: cpu 1 hot: low 2, high 6, batch 1 Oct 1 07:49:48 charlie kernel: cpu 1 cold: low 0, high 2, batch 1 Oct 1 07:49:48 charlie kernel: cpu 2 hot: low 2, high 6, batch 1 Oct 1 07:49:48 charlie kernel: cpu 2 cold: low 0, high 2, batch 1 Oct 1 07:49:48 charlie kernel: cpu 3 hot: low 2, high 6, batch 1 Oct 1 07:49:48 charlie kernel: cpu 3 cold: low 0, high 2, batch 1 Oct 1 07:49:48 charlie kernel: Node 0 Normal per-cpu: Oct 1 07:49:48 charlie kernel: cpu 0 hot: low 32, high 96, batch 16 Oct 1 07:49:48 charlie kernel: cpu 0 cold: low 0, high 32, batch 16 Oct 1 07:49:48 charlie kernel: cpu 1 hot: low 32, high 96, batch 16 Oct 1 07:49:48 charlie kernel: cpu 1 cold: low 0, high 32, batch 16 Oct 1 07:49:48 charlie kernel: cpu 2 hot: low 32, high 96, batch 16 Oct 1 07:49:48 charlie kernel: cpu 2 cold: low 0, high 32, batch 16 Oct 1 07:49:48 charlie kernel: cpu 3 hot: low 32, high 96, batch 16 Oct 1 07:49:48 charlie kernel: cpu 3 cold: low 0, high 32, batch 16 Oct 1 07:49:48 charlie kernel: Node 0 HighMem per-cpu: empty Oct 1 07:49:48 charlie kernel: Oct 1 07:49:48 charlie kernel: Free pages: 13664kB (0kB HighMem) Oct 1 07:49:48 charlie kernel: Active:133982 inactive:832635 dirty:0 writeback:0 unstable:0 free:3416 slab:9418 mapped:967370 pagetables:2324 6 Oct 1 07:49:48 charlie kernel: Node 0 DMA free:11528kB min:4kB low:8kB high:12kB active:0kB inactive:0kB present:16384kB pages_scanned:2985 a ll_unreclaimable? yes Oct 1 07:49:48 charlie kernel: protections[]: 0 0 0 Oct 1 07:49:48 charlie kernel: Node 0 Normal free:2136kB min:2160kB low:4320kB high:6480kB active:535160kB inactive:3331308kB present:4702208 kB pages_scanned:4548753 all_unreclaimable? yes Oct 1 07:49:48 charlie kernel: protections[]: 0 0 0 Oct 1 07:49:48 charlie kernel: Node 0 HighMem free:0kB min:128kB low:256kB high:384kB active:0kB inactive:0kB present:0kB pages_scanned:0 all _unreclaimable? no Oct 1 07:49:48 charlie kernel: protections[]: 0 0 0 Oct 1 07:49:48 charlie kernel: Node 0 DMA: 0*4kB 1*8kB 0*16kB 2*32kB 3*64kB 0*128kB 2*256kB 1*512kB 0*1024kB 1*2048kB 2*4096kB = 11528kB Oct 1 07:49:48 charlie kernel: Node 0 Normal: 10*4kB 234*8kB 14*16kB 0*32kB 0*64kB 0*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 2136k B Oct 1 07:49:48 charlie kernel: Node 0 HighMem: empty Oct 1 07:49:48 charlie kernel: Swap cache: add 2914909, delete 2914909, find 907117/1019856, race 0+21 Oct 1 07:49:48 charlie kernel: Free swap: 0kB Oct 1 07:49:48 charlie kernel: 1179648 pages of RAM Oct 1 07:49:48 charlie kernel: 168514 reserved pages Oct 1 07:49:48 charlie kernel: 653992 pages shared Oct 1 07:49:48 charlie kernel: 0 pages swap cached Oct 1 07:49:48 charlie kernel: Out of Memory: Killed process 31946 (httpd). Oct 1 08:10:14 charlie syslogd 1.4.1: restart. Oct 1 08:10:14 charlie syslog: syslogd startup succeeded Oct 1 08:10:14 charlie kernel: klogd 1.4.1, log source = /proc/kmsg started. Oct 1 08:10:14 charlie kernel: Bootdata ok (command line is ro root=/dev/VolGroup00/Root vga=791) Oct 1 08:10:14 charlie kernel: Linux version 2.6.9-42.0.2.plus.c4smp (buildcentos@v20z-x86-64) (gcc version 3.4.6 20060404 (Red Hat 3.4.6-3)) #1 SMP Sat Aug 26 12:53:43 CDT 2006 Oct 1 08:10:14 charlie kernel: BIOS-provided physical RAM map: Oct 1 08:10:14 charlie kernel: BIOS-e820: 0000000000000000 - 00000000000a0000 (usable) Oct 1 08:10:14 charlie kernel: BIOS-e820: 0000000000100000 - 00000000dffc0000 (usable) Oct 1 08:10:14 charlie kernel: BIOS-e820: 00000000dffc0000 - 00000000dffcfc00 (ACPI data) Oct 1 08:10:14 charlie kernel: BIOS-e820: 00000000dffcfc00 - 00000000dffff000 (reserved) Oct 1 08:10:14 charlie kernel: BIOS-e820: 00000000e0000000 - 00000000f0000000 (reserved) Oct 1 08:10:14 charlie kernel: BIOS-e820: 00000000fec00000 - 00000000fec90000 (reserved) Oct 1 08:10:14 charlie kernel: BIOS-e820: 00000000fed00000 - 00000000fed00400 (reserved) Oct 1 08:10:14 charlie kernel: BIOS-e820: 00000000fee00000 - 00000000fee10000 (reserved) Oct 1 08:10:14 charlie syslog: klogd startup succeeded Oct 1 08:10:14 charlie kernel: BIOS-e820: 00000000ffb00000 - 0000000100000000 (reserved) Oct 1 08:10:14 charlie kernel: BIOS-e820: 0000000100000000 - 0000000120000000 (usable) Oct 1 08:10:14 charlie irqbalance: irqbalance startup succeeded Oct 1 08:10:14 charlie portmap: portmap startup succeeded Oct 1 08:10:14 charlie rpc.statd[2999]: Version 1.0.6 Starting Oct 1 08:10:14 charlie kernel: No NUMA configuration found Oct 1 08:10:14 charlie kernel: Faking a node at 0000000000000000-0000000120000000 Oct 1 08:10:14 charlie kernel: Bootmem setup node 0 0000000000000000-0000000120000000 Oct 1 08:10:14 charlie nfslock: rpc.statd startup succeeded Oct 1 08:10:14 charlie kernel: No mptable found. Oct 1 08:10:14 charlie kernel: DMI 2.3 present. Oct 1 08:10:14 charlie kernel: ACPI: PM-Timer IO Port: 0x808 Oct 1 08:10:14 charlie kernel: ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) Oct 1 08:10:15 charlie kernel: Processor #0 15:4 APIC version 16 Oct 1 08:10:15 charlie kernel: ACPI: LAPIC (acpi_id[0x02] lapic_id[0x06] enabled) Oct 1 08:10:15 charlie kernel: Processor #6 15:4 APIC version 16 Oct 1 08:10:15 charlie kernel: ACPI: LAPIC (acpi_id[0x03] lapic_id[0x01] enabled) Oct 1 08:10:15 charlie kernel: Processor #1 15:4 APIC version 16 Oct 1 08:10:15 charlie kernel: ACPI: LAPIC (acpi_id[0x04] lapic_id[0x07] enabled) Oct 1 08:10:15 charlie kernel: Processor #7 15:4 APIC version 16 Oct 1 08:10:15 charlie kernel: ACPI: LAPIC (acpi_id[0x05] lapic_id[0x02] disabled) Oct 1 08:10:15 charlie kernel: ACPI: LAPIC (acpi_id[0x06] lapic_id[0x04] disabled) Oct 1 08:10:15 charlie kernel: ACPI: LAPIC (acpi_id[0x07] lapic_id[0x03] disabled) On 10/2/06, Devraj Mukherjee <devraj(a)gmail.com> wrote: > you mean 2.6.9-42.0.2.plus.c4smp > > On 10/2/06, Dag Wieers <dag(a)wieers.com> wrote: > > On Mon, 2 Oct 2006, Devraj Mukherjee wrote: > > > > > I suspect that Apache 2.0.52 as distributed with CentOS has a memory > > > leak issue. Is anyone aware of this? > > > > Being more specific might make your mail more valuable. A memory leak > > in what module ? How to reproduce it ? Is it a known Apache issue or > > something specific to how the CentOS Apache has been compiled ? > > Why do you suspect there is a memory leak ? > > > > Any reference would make your post useful, now it's not. > > > > > > BTW Did you know the kernel you are running has a bug ? > > > > Kind regards, > > -- dag wieers, dag(a)wieers.com, http://dag.wieers.com/ -- > > [all I want is a warm bed and a kind word and unlimited power] > > _______________________________________________ > > CentOS mailing list > > CentOS(a)centos.org > > http://lists.centos.org/mailman/listinfo/centos > > > > > -- > "I never look back darling, it distracts from the now", Edna Mode (The > Incredibles) > -- "I never look back darling, it distracts from the now", Edna Mode (The Incredibles)

19 years, 6 months

Re: [CentOS] Could not complete SSL handshake to Amazon EC2 host

by Tim Dunphy

Hi Eric, > NRPE: Error receiving data from daemon > Seems as this is not a SSL Problem. Do you have a nagios user account? Cat > /etc/passwd Yep! Both hosts have nagios user accounts. Demonstrating from the client: [root@ops:~] #id nagios uid=2002(nagios) gid=2002(nagios) groups=2002(nagios),2008(nagioscmd) And this is from the monitoring server: [root@monitor1:~] #id nagios uid=1001(nagios) gid=1001(nagios) groups=1001(nagios),1002(nagcmd) I do notice a slight difference in the user id and group id numbers. But I don't think that could be causing any issue. Does anyone else disagree? I might want to standardize user accounts at some point howver. Thanks! Tim On Fri, May 1, 2015 at 1:03 PM, Eric Lehmann <e.lehmann88(a)gmail.com> wrote: > Hi > > NRPE: Error receiving data from daemon > > Seems as this is not a SSL Problem. Do you have a nagios user account? Cat > /etc/passwd > Am 01.05.2015 18:45 schrieb "Tim Dunphy" <bluethundr(a)gmail.com>: > > > > > > > Oh my mistake. I mean nrpe without parameters. It should say something > > > about SSL/TLS aktiv or so. > > > You could test nrpe without SSL. Use nrpe -n - H host > > > > > > > > This is what I see about ssl if I just run nrpe on the client without any > > flags: > > > > [root@ops:~] #nrpe| head -8 > > > > NRPE - Nagios Remote Plugin Executor > > Copyright (c) 1999-2008 Ethan Galstad (nagios(a)nagios.org) > > Version: 2.15 > > Last Modified: 09-06-2013 > > License: GPL v2 with exemptions (-l for more info) > > SSL/TLS Available: Anonymous DH Mode, OpenSSL 0.9.6 or higher required > > TCP Wrappers Available > > > > And if I go back to the monitoring host and try to run nrpe with the -n > > flag, this is what I get: > > > > [root@monitor1:~] #/usr/local/nagios/libexec/check_nrpe -n -H > > ops.jokefire.com > > *CHECK_NRPE: Error receiving data from daemon.* > > > > And still getting the SSL error without the -n flag: > > > > [root@monitor1:~] #/usr/local/nagios/libexec/check_nrpe -H > > ops.jokefire.com > > *CHECK_NRPE: Error - Could not complete SSL handshake.* > > > > Running nmap from the monitor host I can see that the nrpe port is open: > > > > [root@monitor1:~] #nmap -p 5666 ops.jokefire.com > > > > Starting Nmap 6.40 ( http://nmap.org ) at 2015-05-01 12:38 EDT > > Nmap scan report for ops.jokefire.com (54.225.218.125) > > Host is up (0.011s latency). > > rDNS record for 54.225.218.125: > ec2-54-225-218-125.compute-1.amazonaws.com > > PORT STATE SERVICE > > *5666/tcp open nrpe* > > > > Nmap done: 1 IP address (1 host up) scanned in 0.14 seconds > > > > Yet if I try telnetting to it, it connects, then closes the connection > > immediately: > > > > [root@monitor1:~] #telnet ops.jokefire.com 5666 > > Trying 54.225.218.125... > > *Connected to ops.jokefire.com <http://ops.jokefire.com>.* > > Escape character is '^]'. > > *Connection closed by foreign host.* > > > > Going back to the ops host that I want to monitor, I can verify that the > > port is listening: > > > > [root@ops:~] #lsof -i :5666 > > COMMAND PID USER FD TYPE DEVICE SIZE NODE NAME > > xinetd 1434 root 5u IPv4 4063 TCP *:nrpe (LISTEN) > > > > > > And I can verify that the nrpe conf is owned by the nagios user and > group: > > > > [root@ops:~] #ls -l /usr/local/nagios/etc/nrpe.cfg > > -rw-r--r-- 1 nagios nagios 7988 May 1 00:37 > /usr/local/nagios/etc/nrpe.cfg > > > > I think that covers all your suggestions. Except for Eero's suggestion to > > try running nrpe without xinetd. I can try to get to that later, but I > may > > not have time for that suggestion today. But as I demonstrate above, the > > problem is not that nrpe isn't listening. > > > > This remains a really odd situation. Does anyone else have any clues? > > > > Thanks, > > Tim > > > > > > > > On Fri, May 1, 2015 at 7:43 AM, Eric Lehmann <e.lehmann88(a)gmail.com> > > wrote: > > > > > Oh my mistake. I mean nrpe without parameters. It should say something > > > about SSL/TLS aktiv or so. > > > You could test nrpe without SSL. Use nrpe -n - H host > > > Am 01.05.2015 13:18 schrieb "Eero Volotinen" <eero.volotinen(a)iki.fi>: > > > > > > > well. how about trying default setting and running nrped without > > xinetd. > > > > > > > > -- > > > > Eero > > > > > > > > 2015-05-01 14:14 GMT+03:00 Tim Dunphy <bluethundr(a)gmail.com>: > > > > > > > > > > This is strange... > > > > > > Do you have SSL aktive on both systems? Run nrpr localy without > > > > > parameters > > > > > > (this should return some nrpe stats) and check ldd for libssl. > > > > > > > > > > > > > > > I don't seem to have that command. > > > > > > > > > > > > > > > [root@monitor1:~] #find / -name "*nrpr" 2> /dev/null > > > > > [root@monitor1:~] # > > > > > > > > > > And that's on either system. > > > > > > > > > > And if I do an ldd on both, this is what I can tell: > > > > > > > > > > Server: > > > > > > > > > > [root@monitor1:~] #ldd /usr/local/nagios/libexec/check_nrpe > > > > > linux-vdso.so.1 => (0x00007fffd895d000) > > > > > * libssl.so.10 => /lib64/libssl.so.10 (0x00007fc61722a000)* > > > > > * libcrypto.so.10 => /lib64/libcrypto.so.10 > > > (0x00007fc616e43000)* > > > > > libnsl.so.1 => /lib64/libnsl.so.1 (0x00007fc616c29000) > > > > > libc.so.6 => /lib64/libc.so.6 (0x00007fc616868000) > > > > > libgssapi_krb5.so.2 => /lib64/libgssapi_krb5.so.2 > > > > > (0x00007fc61661c000) > > > > > libkrb5.so.3 => /lib64/libkrb5.so.3 (0x00007fc616338000) > > > > > libcom_err.so.2 => /lib64/libcom_err.so.2 > > (0x00007fc616134000) > > > > > libk5crypto.so.3 => /lib64/libk5crypto.so.3 > > > (0x00007fc615f02000) > > > > > libdl.so.2 => /lib64/libdl.so.2 (0x00007fc615cfd000) > > > > > libz.so.1 => /lib64/libz.so.1 (0x00007fc615ae7000) > > > > > /lib64/ld-linux-x86-64.so.2 (0x00007fc6174a0000) > > > > > libkrb5support.so.0 => /lib64/libkrb5support.so.0 > > > > > (0x00007fc6158d8000) > > > > > libkeyutils.so.1 => /lib64/libkeyutils.so.1 > > > (0x00007fc6156d3000) > > > > > libresolv.so.2 => /lib64/libresolv.so.2 > (0x00007fc6154b9000) > > > > > libpthread.so.0 => /lib64/libpthread.so.0 > > (0x00007fc61529d000) > > > > > libselinux.so.1 => /lib64/libselinux.so.1 > > (0x00007fc615077000) > > > > > libpcre.so.1 => /lib64/libpcre.so.1 (0x00007fc614e16000) > > > > > liblzma.so.5 => /lib64/liblzma.so.5 (0x00007fc614bf1000) > > > > > > > > > > > > > > > Client: > > > > > > > > > > [root@ops:~] #ldd /usr/local/nagios/libexec/check_nrpe > > > > > * libssl.so.6 => /lib64/libssl.so.6 (0x00002aaaaaaba000)* > > > > > * libcrypto.so.6 => /lib64/libcrypto.so.6 > > (0x00002aaaaad08000)* > > > > > libnsl.so.1 => /lib64/libnsl.so.1 (0x00002aaaab05a000) > > > > > libc.so.6 => /lib64/libc.so.6 (0x00002aaaab273000) > > > > > libgssapi_krb5.so.2 => /usr/lib64/libgssapi_krb5.so.2 > > > > > (0x00002aaaab5cc000) > > > > > libkrb5.so.3 => /usr/lib64/libkrb5.so.3 > (0x00002aaaab7fa000) > > > > > libcom_err.so.2 => /lib64/libcom_err.so.2 > > (0x00002aaaaba90000) > > > > > libk5crypto.so.3 => /usr/lib64/libk5crypto.so.3 > > > > > (0x00002aaaabc92000) > > > > > libdl.so.2 => /lib64/libdl.so.2 (0x00002aaaabeb7000) > > > > > libz.so.1 => /lib64/libz.so.1 (0x00002aaaac0bc000) > > > > > /lib64/ld-linux-x86-64.so.2 (0x0000555555554000) > > > > > libkrb5support.so.0 => /usr/lib64/libkrb5support.so.0 (0x0 > > > > > 0002aaaac2d0000) > > > > > libkeyutils.so.1 => /lib64/libkeyutils.so.1 > > > (0x00002aaaac4d8000) > > > > > libresolv.so.2 => /lib64/libresolv.so.2 > (0x00002aaaac6db000) > > > > > libselinux.so.1 => /lib64/libselinux.so.1 > > (0x00002aaaac8f0000) > > > > > libsepol.so.1 => /lib64/libsepol.so.1 (0x00002aaaacb09000) > > > > > > > > > > > > > > > So it looks like everything is OK from the SSL end of things. Any > > other > > > > > ideas or suggestions? > > > > > > > > > > Thanks > > > > > Tim > > > > > > > > > > On Fri, May 1, 2015 at 5:46 AM, Eric Lehmann < > e.lehmann88(a)gmail.com> > > > > > wrote: > > > > > > > > > > > This is strange... > > > > > > Do you have SSL aktive on both systems? Run nrpr localy without > > > > > parameters > > > > > > (this should return some nrpe stats) and check ldd for libssl. > > > > > > Am 01.05.2015 07:32 schrieb "Tim Dunphy" <bluethundr(a)gmail.com>: > > > > > > > > > > > > > Hi Eric, > > > > > > > > > > > > > > Thanks for your reply. I do have nrpe running under xinetd on > > the > > > > host > > > > > > I'm > > > > > > > trying to monitor. > > > > > > > > > > > > > > And running the nrpe checl locally: > > > > > > > > > > > > > > [root@ops:~] #/usr/local/nagios/libexec/check_nrpe -H > localhost > > > > > > > NRPE v2.15 > > > > > > > > > > > > > > [root@ops:~] #grep only_from /etc/xinetd.d/nrpe > > > > > > > only_from = 127.0.0.1 216.120.248.126 > > > > > > > > > > > > > > And I do have port 5666 open on the security group for this > host. > > > > > > > > > > > > > > And I made sure the local firewall was stopped, because I am > > > blocking > > > > > > ports > > > > > > > with the security groups instead. > > > > > > > > > > > > > > [root@ops:~] #service iptables status > > > > > > > Firewall is stopped. > > > > > > > > > > > > > > It's only when checking from the monitoring host that nrpe > fails: > > > > > > > > > > > > > > [root@monitor1:~] #/usr/local/nagios/libexec/check_nrpe -H > > > > > > > ops.jokefire.com > > > > > > > CHECK_NRPE: Error - Could not complete SSL handshake. > > > > > > > > > > > > > > Really, really puzzling. This is driving me up a wall!! I hopeI > > can > > > > > solve > > > > > > > this soon.... > > > > > > > > > > > > > > Thanks for any and all help with this one!! > > > > > > > Tim > > > > > > > > > > > > > > On Fri, May 1, 2015 at 1:02 AM, Eric Lehmann < > > > e.lehmann88(a)gmail.com> > > > > > > > wrote: > > > > > > > > > > > > > > > Hi > > > > > > > > Does the deamon run under xinetd? Then you have to configure > > the > > > > > > > only_from > > > > > > > > in */etc/**xinetd.d**/**nrpe* to. > > > > > > > > > > > > > > > > Regards > > > > > > > > Eric > > > > > > > > Am 01.05.2015 06:46 schrieb "Tim Dunphy" < > bluethundr(a)gmail.com > > >: > > > > > > > > > > > > > > > > > Hello, > > > > > > > > > > > > > > > > > > I am trying to monitor a host in the Amazon EC2 cloud. > > > > > > > > > > > > > > > > > > Yet when I try to check NRPE from the monitoring host I am > > > > getting > > > > > an > > > > > > > SSL > > > > > > > > > handshake error: > > > > > > > > > > > > > > > > > > [root@monitor1:~] #/usr/local/nagios/libexec/check_nrpe -H > > > > > > > > > ops.jokefire.com > > > > > > > > > CHECK_NRPE: Error - Could not complete SSL handshake. > > > > > > > > > > > > > > > > > > And if I telnet into the host on port 5666 to see if the FW > > > port > > > > is > > > > > > > open, > > > > > > > > > the connection closes right away: > > > > > > > > > > > > > > > > > > [root@monitor1:~] #telnet ops.somewhere.com 5666 > > > > > > > > > Trying 54.225.218.125... > > > > > > > > > Connected to ops.somewhere.com. > > > > > > > > > Escape character is '^]'. > > > > > > > > > Connection closed by foreign host. > > > > > > > > > > > > > > > > > > You can see there it connects, but then it closes > immediately > > > > after > > > > > > the > > > > > > > > > connection. > > > > > > > > > > > > > > > > > > I have NRPE running on the host I want to monitor: > > > > > > > > > > > > > > > > > > [root@ops:~] #lsof -i :5666 > > > > > > > > > COMMAND PID USER FD TYPE DEVICE SIZE NODE NAME > > > > > > > > > xinetd 1434 root 5u IPv4 4063 TCP *:nrpe > > (LISTEN) > > > > > > > > > > > > > > > > > > And I have the IP of my nagios server listed in the xinetd > > conf > > > > > file: > > > > > > > > > > > > > > > > > > [root@ops:~] #cat /etc/xinetd.d/nrpe > > > > > > > > > # default: on > > > > > > > > > # description: NRPE (Nagios Remote Plugin Executor) > > > > > > > > > service nrpe > > > > > > > > > { > > > > > > > > > flags = REUSE > > > > > > > > > socket_type = stream > > > > > > > > > port = 5666 > > > > > > > > > wait = no > > > > > > > > > user = nagios > > > > > > > > > group = nagios > > > > > > > > > server = /usr/local/nagios/bin/nrpe > > > > > > > > > server_args = -c /usr/local/nagios/etc/nrpe.cfg > > > > --inetd > > > > > > > > > log_on_failure += USERID > > > > > > > > > disable = no > > > > > > > > > only_from = 127.0.0.1 xx.xx.xx.xx # <- > > > > representing > > > > > > my > > > > > > > > real > > > > > > > > > nagios server IP > > > > > > > > > } > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > And I have my default security group for that host open on > > port > > > > > 5666 > > > > > > to > > > > > > > > the > > > > > > > > > world for this experiment. I plan on locking that down > again > > > to > > > > > the > > > > > > > > single > > > > > > > > > IP of my monitoring host once I get this resolved. > > > > > > > > > > > > > > > > > > Does anyone have any suggestions on how I can get that > > problem > > > > > > solved? > > > > > > > > > > > > > > > > > > Thanks, > > > > > > > > > Tim > > > > > > > > > > > > > > > > > > -- > > > > > > > > > GPG me!! > > > > > > > > > > > > > > > > > > gpg --keyserver pool.sks-keyservers.net --recv-keys > F186197B > > > > > > > > > _______________________________________________ > > > > > > > > > CentOS mailing list > > > > > > > > > CentOS(a)centos.org > > > > > > > > > http://lists.centos.org/mailman/listinfo/centos > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > > > CentOS mailing list > > > > > > > > CentOS(a)centos.org > > > > > > > > http://lists.centos.org/mailman/listinfo/centos > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > GPG me!! > > > > > > > > > > > > > > gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B > > > > > > > _______________________________________________ > > > > > > > CentOS mailing list > > > > > > > CentOS(a)centos.org > > > > > > > http://lists.centos.org/mailman/listinfo/centos > > > > > > > > > > > > > _______________________________________________ > > > > > > CentOS mailing list > > > > > > CentOS(a)centos.org > > > > > > http://lists.centos.org/mailman/listinfo/centos > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > GPG me!! > > > > > > > > > > gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B > > > > > _______________________________________________ > > > > > CentOS mailing list > > > > > CentOS(a)centos.org > > > > > http://lists.centos.org/mailman/listinfo/centos > > > > > > > > > _______________________________________________ > > > > CentOS mailing list > > > > CentOS(a)centos.org > > > > http://lists.centos.org/mailman/listinfo/centos > > > > > > > _______________________________________________ > > > CentOS mailing list > > > CentOS(a)centos.org > > > http://lists.centos.org/mailman/listinfo/centos > > > > > > > > > > > -- > > GPG me!! > > > > gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B > > _______________________________________________ > > CentOS mailing list > > CentOS(a)centos.org > > http://lists.centos.org/mailman/listinfo/centos > > > _______________________________________________ > CentOS mailing list > CentOS(a)centos.org > http://lists.centos.org/mailman/listinfo/centos > -- GPG me!! gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B

10 years, 11 months

Jump to page: