Your message dated Wed, 19 Feb 2025 16:06:36 +0100 (CET)
with message-id <20250219150636.8e2d5be2...@eldamar.lan>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #983338,
regarding RPI-3B+: serial console shows garbage / no longer wor
Your message dated Sat, 31 Aug 2024 14:35:32 +0200 (CEST)
with message-id <20240831123532.dbb62be2...@eldamar.lan>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #983879,
regarding linux-image-amd64: Serial port doesn't work af
Your message dated Sat, 10 Aug 2024 13:57:53 +0200 (CEST)
with message-id <20240810115753.9d75ebe2...@eldamar.lan>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #833035,
regarding linux: Keyspan USB serial adapter USA-49WLC failed t
Processing control commands:
> merge -1 1071456
Bug #1077620 [autopkgtest] autopkgtest: timed out waiting for 'login prompt on
serial console'
Bug #1071456 [autopkgtest] autopkgtest-virt-qemu: autopkgtest [15:14:50]:
ERROR: testbed failure: sent `auxverb_debug_fail', got `
Package: src:linux
Version: 6.6.15-2
Severity: normal
X-Debbugs-Cc: fores...@nom.one
Dear Maintainer,
When booting with an encrypted root filesystem, the LUKS unlock
passphrase prompt normally appears on the serial console shortly after
the first device-mapper messages. It looks like this
On Fri, 11 Nov 2022 16:12:32 +0100
Salvatore Bonaccorso wrote:
> Jakob, were you able to forward the patch upstream? I'm including
> Johan and linux-usb list in this reply now.
No, I originally wanted to understand the differences of the firmware
loading mechanism as I assumed a patch migrating
is applied in mainline?
Jakob, were you able to forward the patch upstream? I'm including
Johan and linux-usb list in this reply now.
Johan, fo context, it is about an older bug reported in Debian as
https://bugs.debian.org/833035 with users of the Keyspan USB serial
adapter USA-49WLC fal
Processing control commands:
> notfound -1 linux-5.15.15-1
Bug #833035 [src:linux] linux: Keyspan USB serial adapter USA-49WLC failed to
load firmware since 3.16.0-4-amd64
The source 'linux' and version 'linux-5.15.15-1' do not appear to match any
binary packages
No lo
Control: notfound -1 linux-5.15.15-1
Control: found -1 linux/5.15.15-1
signature.asc
Description: This is a digitally signed message part.
Processing control commands:
> found -1 linux-5.15.15-1
Bug #833035 [src:linux] linux-image-3.16.0-4-amd64: Keyspan USB serial adapter
USA-49WLC failed to load firmware
The source 'linux' and version 'linux-5.15.15-1' do not appear to match any
binary packages
Marked as
Control: found -1 linux-5.15.15-1
Control: retitle -1 linux: Keyspan USB serial adapter USA-49WLC failed to load
firmware since 3.16.0-4-amd64
On Monday, 7 February 2022 15:33:49 CEST Jakob Haufe wrote:
> This still affects 5.15.0-3-amd64:
Updating bug metadata accordingly
> The patch a
Hi Jakob,
On Mon, Feb 07, 2022 at 03:33:49PM +0100, Jakob Haufe wrote:
> This still affects 5.15.0-3-amd64:
>
> [624300.704569] usb 5-1: new full-speed USB device number 2 using ohci-pci
> [624300.901723] usb 5-1: New USB device found, idVendor=06cd, idProduct=011a,
> bcdDevice=80.01
> [624300.9
b_serial_port *port = tty->driver_data;
@@ -1599,7 +1614,10 @@
/* download the firmware to a pre-renumeration device */
static int keyspan_fake_startup(struct usb_serial *serial)
{
- char *fw_name;
+ int response;
+ const struct ihex_binrec *record;
+ char*fw_name;
+ const struct firmware *fw;
Your message dated Wed, 28 Jul 2021 06:03:43 +
with message-id
and subject line Bug#961056: fixed in linux 5.10.46-3
has caused the Debian Bug report #961056,
regarding debian-installer: qemu-system-s390x installation fails due to
incorrect serial device
to be marked as done.
This means
Hi,
On Tue, May 19, 2020 at 08:24:27PM +0200, Valentin Vidić wrote:
> On Tue, May 19, 2020 at 07:23:21PM +0200, John Paul Adrian Glaubitz wrote:
> > Please see #926539 [1].
>
> Thanks, I have sent the patch for the driver instead:
>
> https://lkml.org/lkml/2020/5/19/854
This appears to be app
t; Bug#833035: linux-image-3.16.0-4-amd64: Keyspan USB serial adapter
> > > > USA-49WLC failed to load firmware
> > > >
> > > > whatever became of the proposed patch. i'm running ubuntu 16.04.3,
> > > > kernel 4.4.0-97-generi
Processing control commands:
> tags -1 + moreinfo
Bug #833035 [src:linux] linux-image-3.16.0-4-amd64: Keyspan USB serial adapter
USA-49WLC failed to load firmware
Added tag(s) moreinfo.
--
833035: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833035
Debian Bug Tracking System
Contact
Control: tags -1 + moreinfo
Hi,
On Thu, Oct 19, 2017 at 05:29:41PM -0400, Paul Fox wrote:
> chris wrote:
> > On 10/16/2017 11:32 AM, Paul Fox wrote:
> > > ben, chris -- regarding this bug:
> > > Bug#833035: linux-image-3.16.0-4-amd64: Keyspan USB serial ada
el the onboard
serial port is disabled.
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and h
Your message dated Sat, 24 Apr 2021 07:17:22 -0700 (PDT)
with message-id <60842872.1c69fb81.c5790.3...@mx.google.com>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #690727,
regarding linux-image-3.2.0-3-686-pae: user space serial c
Your message dated Fri, 23 Apr 2021 15:54:46 +0200
with message-id
and subject line Re: Bug#708344: xen: serial passthrough broken in Debian Wheezy
has caused the Debian Bug report #708344,
regarding xen: serial passthrough broken in Debian Wheezy
to be marked as done.
This means that you claim
Processing control commands:
> Severity -1 normal
Bug #986863 [src:linux] linux: Serial terminal for RPi 4 and p400 corrupted
during bootup
Severity set to 'normal' from 'important'
--
986863: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986863
Debian Bug Tra
ore clock
> frequency changes, the UART baud rate will also change."
>
> (from
> <https://www.raspberrypi.org/documentation/configuration/uart.md>).
Ugh, great... FSVO.
I can confirm both force_turbo=1 and core_freq=250 worked for keeping
the serial port functioning after vc
On Mon, 2021-04-12 at 17:39 -0500, Gunnar Wolf wrote:
> Source: linux
> Version: 5.10.0-5
> Severity: important
>
> During the boot process of the Raspberry Pi models 4 (4 and 8GB) and
> p400, the console starts working correctly, but as the vc4 video gets
> initialized, the console gets corrupted
Processing control commands:
> notfound -1 5.9.15-1
Bug #986863 [src:linux] linux: Serial terminal for RPi 4 and p400 corrupted
during bootup
Ignoring request to alter found versions of bug #986863 to the same values
previously set
> found -1 5.10.4-1
Bug #986863 [src:linux] linux:
Control: notfound -1 5.9.15-1
Control: found -1 5.10.4-1
Marking two adjacent kernel versions where the breakage first appeared.
Processing commands for cont...@bugs.debian.org:
> found 986863 5.10.0-6-arm64
Bug #986863 [src:linux] linux: Serial terminal for RPi 4 and p400 corrupted
during bootup
The source 'linux' and version '5.10.0-6-arm64' do not appear to match any
binary packages
Marked as
found 986863 5.10.0-6-arm64
notfound 986863 5.8.0-3-arm64
thanks
I blacklisted the vc4 module, and the console works reliably again, so
that's a way to get a working system. I will blacklist in the images I
produce, but this should not be needed for users to know!
I am also trying with a kernel f
Package: linux-image-amd64
Version: 4.19+105+deb10u9
Severity: important
I have several all in one FEC MegaPos MP3435. On all of them after
upgrade of the system from stretch to buster some (or all) of the serial
ports stop to work. Fortunatelly I boot them via PXE with LTSP and can
switch
Steps to reproduce:
- Build an image using the recipes here:
https://salsa.debian.org/raspi-team/image-specs
or download a prebuild image from here:
https://raspi.debian.net/tested-images/
- connect a 3V3 serial console to pins 6, 8, and 10 on the 40 pin GPIO
header
- Boot into the
Package: linux-image-5.10.0-3-arm64
Version: 5.10.13-1
Severity: important
Dear Maintainer,
In the context of tigervnc-standalone-server and xfce4, the serial console on a
Raspberry Pi 3 only prints garbage from the time of login via the serial
console.
Here is the original issue from the
Your message dated Fri, 11 Sep 2020 20:36:04 +
with message-id
and subject line Bug#960355: fixed in initramfs-tools 0.138
has caused the Debian Bug report #960355,
regarding Invalid serial console blocks system boot
to be marked as done.
This means that you claim that the problem has been
Your message dated Fri, 11 Sep 2020 20:36:04 +
with message-id
and subject line Bug#960355: fixed in initramfs-tools 0.138
has caused the Debian Bug report #960355,
regarding Invalid serial console blocks system boot
to be marked as done.
This means that you claim that the problem has been
Your message dated Mon, 24 Aug 2020 22:00:08 +
with message-id
and subject line Bug#963619: fixed in linux 5.8.3-1~exp1
has caused the Debian Bug report #963619,
regarding raspberry-pi: the AUX serial driver is not enabled
to be marked as done.
This means that you claim that the problem has
Hi Ben and Debian Kernel team - do we have any news on the review of
this patch?
Thanks in advance,
Guilherme
e
command-line). The situation is easily reproducible and we can find various
reports dating back some years. The reports usually are of the form
"machine can't boot if wrong console is provided" or slightly different
forms of that, almost always relating serial consoles with boot issues
The previous patch removed the CONFIG_SERIAL_8250_ASPEED_VUART symbol.
The problem is fixed in this patch.
>From 4d99aeaf7941c9df0e8a9760d1388e9f9a28a438 Mon Sep 17 00:00:00 2001
From: Marc Kleine-Budde
Date: Wed, 24 Jun 2020 09:38:58 +0200
Subject: [PATCH] [armhf] enable AUX serial port dri
Package: src:linux
Version: 5.6.14-2
Severity: normal
Tags: patch
Dear Maintainer,
The AUX serial driver for all raspberry pi models is not enabled in
the armhf kernel variant. In the armel and arm64 variant it is.
Attached patch switches on the needed config symbols.
regards,
Marc
ing checkfs_once() to "inherit" the bad
return from printf.
The big issue comes now: checkfs() runs a loop, and given in this corner
case checkfs_once() returns an error state, the loop goes on forever,
effectively preventing the boot.
I consider this a bug specially because we had repo
Your message dated Fri, 15 May 2020 23:48:38 +0100
with message-id <79d76a6cb696073e28d9659460657b46b34a5e26.ca...@decadent.org.uk>
and subject line Re: Invalid serial console blocks system boot
has caused the Debian Bug report #960355,
regarding Invalid serial console blocks system boot
Package: initramfs-tools-core
Version: 0.137
Putting a serial console on a non-existent/broken serial port
via the last "console=" argument of the kernel command line
causes the initrd to hang without completing the boot process.
If the problematic serial console argument comes fi
k3399-gru.dtsi in the
> kernel tree. Setting a serial console this way seems to be ordinary, a
> lot of other devices have it too.
I think most devices for which the kernel provides the device tree are
development boards, so a serial console is a fairly sensible default
for them. It sou
, and the installer could do
that by default.
I'm using rk3399-gru-kevin.dtb from the Debian package. The stdout-path
property comes from arch/arm64/boot/dts/rockchip/rk3399-gru.dtsi in the
kernel tree. Setting a serial console this way seems to be ordinary, a
lot of other devices have i
Your message dated Wed, 26 Feb 2020 23:10:45 +
with message-id
and subject line Re: Bug#952452: initramfs-tools: prefers serial console over
framebuffer console
has caused the Debian Bug report #952452,
regarding initramfs-tools: prefers serial console over framebuffer console
to be marked
On 24/02/2020 19:50, Alper Nebi Yasak wrote:
I'm using Debian on an arm64 chromebook, and not setting "console=tty1"
in the kernel command line results in a number of weird behaviours
related to the initramfs.
Turns out my device-tree has (for debugging purposes?):
chosen {
std
see the "Please unlock disk" cryptsetup prompt and can't type a
passphrase; unless plymouth is installed.
I'm able to boot the encrypted system as a QEMU virtual machine and I
get similar behaviour there, no messages or prompts are printed to the
graphical console and instead a
On Thu, 25 Oct 2018 11:06:38 +0200 Paul van Tilburg
wrote:
Source: linux
Version: 4.18.10-2
Severity: normal
Dear Maintainer,
Since the upgrade of our system from Debian 9 (Stretch) to 10 (Buster), but
also from Ubuntu 16.04 LTS (Xenial) to 18.04 LTS (Bionic), the serial port
of our Atom
Package: src:linux
Version: 5.2.9-2
Severity: normal
Dear Maintainer,
with the 32bit kernel I do not have a serial console on my RPi 3B+.
The serial console works fine with the 64bit kernel.
Please, add the missing configuration items to enable the console:
SERIAL_8250_EXTENDED=y
Your message dated Mon, 15 Apr 2019 18:00:52 +
with message-id <8f3b2d55-6a01-623a-c6d4-f44ca25e4...@nachtgeist.net>
and subject line Re: Bug#887668: linux-image-4.14.0-rc3-amd64: MosChip MCS9922
serial+parallel port PCI-e card no longer working
has caused the Debian Bug report #
Your message dated Tue, 12 Feb 2019 09:07:11 +
with message-id
and subject line Bug#903824: fixed in linux 4.19.20-1
has caused the Debian Bug report #903824,
regarding please build usb-serial-modules udeb on armhf and arm64
to be marked as done.
This means that you claim that the problem
I take it that this never got properly sorted?
The instructions URL (
https://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-official)
doesn't work anymore; could someone please suggest an alternative?
I have downloaded the .patch file, but need a steer on what to do with it
pleas
Source: linux
Version: 4.18.10-2
Severity: normal
Dear Maintainer,
Since the upgrade of our system from Debian 9 (Stretch) to 10 (Buster), but
also from Ubuntu 16.04 LTS (Xenial) to 18.04 LTS (Bionic), the serial port
of our Atom E3950-based board can no longer be used.
I have traced the cause
Your message dated Thu, 19 Jul 2018 19:17:38 +
with message-id
and subject line Bug#903122: fixed in linux 4.9.110-2
has caused the Debian Bug report #903122,
regarding debian-installer-9-netboot-amd64: Please add char/virtio_console
module (paravirtualized serial) to netinst
to be marked as
package: linux
version: 4.16.16-2
severity: wishlist
Hi,
The usb-serial-modules udeb is available on a number of architectures. Please
also build it on armhf and arm64.
Thanks!
Cheers,
Ivo
Your message dated Thu, 12 Jul 2018 04:20:43 +
with message-id
and subject line Bug#903122: fixed in linux 4.17.6-1
has caused the Debian Bug report #903122,
regarding debian-installer-9-netboot-amd64: Please add char/virtio_console
module (paravirtualized serial) to netinst
to be marked as
On Tue, 2018-07-10 at 02:32 +0200, Cyril Brulebois wrote:
> Control: reassign -1 src:linux
> Control: tag -1 patch
>
> Ben Hutchings (2018-07-09):
> > I would say virtio-modules. All the virtio class drivers depend on
> > virtio and virtio_ring, which means that adding them to any other
> > pack
Processing control commands:
> reassign -1 src:linux
Bug #903122 [debian-installer-9-netboot-amd64]
debian-installer-9-netboot-amd64: Please add char/virtio_console module
(paravirtualized serial) to netinst
Bug reassigned from package 'debian-installer-9-netboot-amd64' to 'sr
Control: reassign -1 src:linux
Control: tag -1 patch
Ben Hutchings (2018-07-09):
> I would say virtio-modules. All the virtio class drivers depend on
> virtio and virtio_ring, which means that adding them to any other
> package would require that package to depend on virtio-modules.
>
> (The Xe
On Sun, 2018-07-08 at 06:37 +0200, Cyril Brulebois wrote:
[...]
> Vincent Caron (2018-07-06):
[...]
> > If this module makes it to netinst's initrd, one would use those kvm
> > args:
> >
> > -chardev file,path=virtiocon0.log,id=virtiocon0
> > -device virtio-
ds back from the
> guest to the host large logs, it might overrun the UART buffer which
> complains with kernel messages about overused IRQ).
>
> While turning to paravirtualized serial, I realized that the
> char/virtio_console kernel module is missing in the netinst's init
>>From [1], I tested all amd64 linux-image packages from 4.13.13-1 (last working
> one) through 4.15~rc8-1~exp1 (still broken).
Sorry I got my references wrong. This should have read:
From [3], I tested all amd64 linux-image packages from 4.13.13-1 (last
working one) through 4.15~rc8-1~exp1 (
chris wrote:
> On 10/16/2017 11:32 AM, Paul Fox wrote:
> > ben, chris -- regarding this bug:
> > Bug#833035: linux-image-3.16.0-4-amd64: Keyspan USB serial adapter
> > USA-49WLC failed to load firmware
> >
> > whatever became of the proposed p
On 10/16/2017 11:32 AM, Paul Fox wrote:
ben, chris -- regarding this bug:
Bug#833035: linux-image-3.16.0-4-amd64: Keyspan USB serial adapter
USA-49WLC failed to load firmware
whatever became of the proposed patch. i'm running ubuntu 16.04.3,
kernel 4.4.0-97-generic, and the fa
ben, chris -- regarding this bug:
Bug#833035: linux-image-3.16.0-4-amd64: Keyspan USB serial adapter
USA-49WLC failed to load firmware
whatever became of the proposed patch. i'm running ubuntu 16.04.3,
kernel 4.4.0-97-generic, and the failure is still present there.
Your message dated Tue, 20 Jun 2017 13:00:12 +
with message-id
and subject line Bug#864368: fixed in linux 4.11.6-1
has caused the Debian Bug report #864368,
regarding Expand kernel serial port configuration
to be marked as done.
This means that you claim that the problem has been dealt with
Your message dated Mon, 12 Jun 2017 20:00:10 +
with message-id
and subject line Bug#864368: fixed in linux 4.9.30-2
has caused the Debian Bug report #864368,
regarding Expand kernel serial port configuration
to be marked as done.
This means that you claim that the problem has been dealt with
bout changing it. It can always be overridden through the
> '8250.nr_uarts' kernel parameter where needed.
On my system, this meant that I could not use the serial console to do
an install. Doing console=ttyS4 on the command-line didn't work because
the kernel didn't support anyth
On Wed, 2017-06-07 at 18:10 +0100, Ben Hutchings wrote:
> Control: reassign -1 src:linux 4.9.30-1
> Control: severity -1 important
>
> On Wed, 2017-06-07 at 09:38 -0700, Dave Hansen wrote:
> [...]
> > Please raise:
> >
> > CONFIG_SERIAL_8250_RUNTIME_UARTS
> >
> > to something larger, perhaps
UNTIME_UARTS=16
That seems reasonable.
> The second issue is that the "mid" serial driver is not configured in
> this package. Please add the "8250_MID" driver by default and have it
> built in (as opposed to being as a module). Some systems which have
> seria
Processing control commands:
> reassign -1 src:linux 4.9.30-1
Bug #864368 [linux-image-4.9.0-3-amd64] Expand kernel serial port configuration
Bug reassigned from package 'linux-image-4.9.0-3-amd64' to 'src:linux'.
Ignoring request to alter found versions of bug #86
are two things that cause the apparent hang:
One, the system has only has PCI serial ports. The traditional, legacy
serial ports (at the low I/O ports like 0x3F8) are either not present or
not connected. The kernel is only configured for 4 runtime serial ports
(CONFIG_SERIAL_8250_RUNTIME_UARTS=4
Forgot attaching the log to the report, so here goes nothing
omap-aes.log
Description: Binary data
On 08/02/2016 16:56, Ben Hutchings wrote:
On Mon, 2016-08-01 at 22:51 -0700, Chris Rhodin wrote:
[...]
I get this from dmesg. I'm assuming the new error -2 indicates the file
was not found.
[...]
Yes. And the other error code (-110) indicates a time-out.
Can you test whether the attached pa
do this by
following the instructions at
<https://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-official>.
Ben.
--
Ben Hutchings
73.46% of all statistics are made up.
--- a/drivers/usb/serial/keyspan.c
+++ b/drivers/usb/serial/keyspan.c
@@ -38,6 +38,8 @@
#include
#i
On 07/31/2016 17:31, Ben Hutchings wrote:
Control: retitle -1 linux-image-3.16.0-4-amd64: Keyspan USB serial adapter
USA-49WLC failed to load firmware
Control: tag -1 moreinfo
On Sun, 2016-07-31 at 00:16 -0700, Chris Rhodin wrote:
Subject: linux-image-3.16.0-4-amd64: Keyspan USB serial
Processing control commands:
> retitle -1 linux-image-3.16.0-4-amd64: Keyspan USB serial adapter USA-49WLC
> failed to load firmware
Bug #833035 [src:linux] (no subject)
Changed Bug title to 'linux-image-3.16.0-4-amd64: Keyspan USB serial adapter
USA-49WLC failed to load firmware
Control: retitle -1 linux-image-3.16.0-4-amd64: Keyspan USB serial adapter
USA-49WLC failed to load firmware
Control: tag -1 moreinfo
On Sun, 2016-07-31 at 00:16 -0700, Chris Rhodin wrote:
> Subject: linux-image-3.16.0-4-amd64: Keyspan USB serial adapter USA-
> 49WLC failed to load fi
Your message dated Fri, 04 Dec 2015 22:17:07 +
with message-id <1449267427.2824.2.ca...@decadent.org.uk>
and subject line Re: Bug#807069: USB to serial(ttyUSB) port crash in debian.
task khubd:369 blocked for more than 120 seconds.
has caused the Debian Bug report #807069,
regarding
Package: linux-source
Version: 3.12
We are using sierra modem for 4G LTE networks. we used to communicate
with modem using AT commands via ttyUSB ports.
Recently we observed a crash in usb driver interface when we try to
post some AT commands. After the crash the kernel seems to be hanged.
We wer
Your message dated Fri, 24 Oct 2014 14:29:00 +0200
with message-id <20141024122900.ga15...@lorien.valinor.li>
and subject line Re: Bug#766607: linux: ("regression") No serial console output
when connecting to virtual serial console for the guest during d-i installation
initiated
o netcfg/get_ipaddress=192.168.122.123 suite=unstable
-- console=ttyS0,115200n8
in the example case.
When altough using the current d-i with a 3.16.2-2 the kernel I don't
see anymore neither the kernel boot messages nor the started d-i
anymore when virt-install connects to the virtual serial console
> not see any device in /dev tree except from ttyS0 and ttyS1 Can i
> assume that is it working?
if you do "tail -f /dev/ttySx" x = 0 or x = 1
it may print whatever that arrives at them.
/Jeffrin.
--
software engineer
rajagiri school of engineering and technology
--
To UNSUBSCRIBE, email to
Hi Everyone,
I have a multiport serial card which uses Exar XR17V358 chip and
debian system with 3.8.7 version kernel. Debian perfectly recognize my
card and lspci output says kernel driver in use: serial but i could
not see any device in /dev tree except from ttyS0 and ttyS1 Can i
assume that is
Now a new kernel,
3.13-1-amd64 #1 SMP Debian 3.13.10-1 (2014-04-15) x86_64 GNU/Linux
and the bug is still there.
And no feedback.
What's going on here?
--
hihi...
Package: src:linux
Version: 3.13.7-1
Severity: normal
Dear Maintainer,
* What led up to the situation?
Upgrading the kernel.
* What exactly did you do (or not do) that was effective (or
ineffective)?
Try to use the serial port. :)
* What was the outcome of this action
this in
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/5334838b.5030...@b2-fortbildung.de
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 16/06/2013 17:46, Ben Hutchings ha scritto:
> On Sun, 2013-06-16 at 15:10 +0200, Franco Martelli wrote:
>> I've an annoying error message at boot time that is related to
>> initramfs-tools, thought because it doesn't appear in dmesg
>> output. If l
On Sun, 2013-06-16 at 15:10 +0200, Franco Martelli wrote:
> I've an annoying error message at boot time that is related to
> initramfs-tools, thought because it doesn't appear in dmesg output. If
> libata(CONFIG_ATA), ata_generic(CONFIG_ATA_GENERIC),
> sata_nv(CONFIG_SATA_NV), pata_amd(CONFIG_PATA_
t: nForce3 Serial ATA Controller
vendor: NVIDIA Corporation
physical id: a
bus info: pci@:00:0a.0
logical name: scsi0
version: a2
width: 32 bits
clock: 66MHz
capabilities: ide pm bus_master cap_list emulated
configuration: driver=sata_
s to
bcc. For xen-devel the background can be found at
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=708344
The gist is that with:
irq = [ 4 ]
ioports = [ '3f8-3ff' ]
in the guest config the serial port used to work with Jeremy's xen.git
(used
0.4
[0.196187] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
[0.196271] intel_idle: does not run on family 6 model 23
[0.196892] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[0.217565] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[0.218010] Linux agpg
On Tue, 2013-06-04 at 17:32 +0200, Jonas Meurer wrote:
> Just gave Linux 3.9-1-amd64 from Debian/sid a try. The issue is
> reproducible with this DomU kernel.
Could you post dmesg, /proc/ioports and /proc/interrupts from this
kernel please?
Ian.
--
To UNSUBSCRIBE, email to debian-kernel-requ.
Hey,
Am 2013-06-03 18:17, schrieb Ian Campbell:
On Mon, 2013-06-03 at 17:25 +0200, Jonas Meurer wrote:
Hello,
did anybody else discover issue with serial passthrough on Linux 3.2.0
from Debbian Wheezy?
I haven't, but Squeeze was based on the out of tree xen.git kernel
while
Wheezy
Your message dated Tue, 4 Jun 2013 00:28:55 +0200
with message-id <20130603222855.GB5604@pisco.westfalen.local>
and subject line Closing
has caused the Debian Bug report #458191,
regarding linux-image-2.6.22-3-amd64: serial port is detected but doesn't get
an interrupt so it doesn&#
Package: src:linux
Version: 3.2.41-2
Severity: important
Hello,
I just discovered a strange bug with serial passthrough in xen 4.1 on
Debian Wheezy. The Dom0 has a GSM modem connected to serial port. The
serial port is passed through to a DomU with options 'irq = [ 4 ]' and
'iopor
the same in another IBM Bladecenter with slightly different
> # > parts and firmware versions. There loading qla2xxx does not fix the
> # > user space console output. Even worse (on a virtual console):
> # [etc]
> tags 690727 - moreinfo
Bug #690727 [src:linux] linux-image-3.2.0-3
Ben Hutchings writes:
> On Tue, 2012-10-16 at 20:44 +0200, Ferenc Wagner wrote:
>
>> This is an issue on IBM HS20 blades with serial over LAN console. In short,
>> kernel messages get through all right, but user space messages are buffered
>> until the qla2xxx FC HBA
Ben Hutchings writes:
> On Tue, 2012-10-16 at 20:44 +0200, Ferenc Wagner wrote:
>
>> This is an issue on IBM HS20 blades with serial over LAN console. In short,
>> kernel messages get through all right, but user space messages are buffered
>> until the qla2xxx FC HBA
Ben Hutchings writes:
> On Tue, 2012-10-16 at 20:44 +0200, Ferenc Wagner wrote:
>
>> This is an issue on IBM HS20 blades with serial over LAN console. In short,
>> kernel messages get through all right, but user space messages are buffered
>> until the qla2xxx FC HBA
On Tue, 2012-10-16 at 20:44 +0200, Ferenc Wagner wrote:
> Package: src:linux
> Version: 3.2.23-1
> Severity: normal
>
> Dear Maintainer,
>
> This is an issue on IBM HS20 blades with serial over LAN console. In short,
> kernel messages get through all right, but user spa
1 - 100 of 309 matches
Mail list logo
