Bug#841850: linux-image-4.7.0-1-686_4.7.8-1_i386.deb does not boot on Thinkpad T41

[Salvatore Bonaccorso]

Control: tags -1 + pending confirmed

Hi!

On Thu, Oct 27, 2016 at 06:21:55AM +0200, Petra Ruebe-Pugliese wrote:
> On Wed. 26. Oct. 2016, at 09:05 Salvatore Bonaccorso (car...@debian.org) 
> wrote:
> > 
> > > On Wednesday 26 October 2016 at 07:36:21 +0200  Salvatore Bonaccorso 
> > > (car...@debian.org) wrote:
> > > [...]
> > > > 
> > > > There seem to be an upstream fix now for this issue:
> > > > 
> > > > https://git.kernel.org/linus/ff8560512b8d4b7ca3ef4fd69166634ac30b2525
> > > > 
> > > > Can you by chance confirm that this works as well for you?
> > > 
>  [...]
> > 
> > Yes you can follow the same procedure starting from a new source tree
> > without the previous applied. 
> > 
> > You can get the above patch as well directly via
> > https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/patch/?id=ff8560512b8d4b7ca3ef4fd69166634ac30b2525
>   Done
> > so that you don't have to copy paste it from the webpage to a file. It
> > should apply with only some fuzz to the source. 
> 
>  So I did the following:
> 
>   -> Create a new temporary directory and change into it
> 
>   -> apt-get source linux
> 
>   -> cd linux-4.7.8
> 
>   -> bash debian/bin/test-patches  -f 686  
> ../upstream-patch-ff8560512b8d4b7ca3ef4fd69166634ac30b2525 
> 
>   -> install the resulting
> [...]  35M Oct 27 01:48 
> linux-image-4.7.0-1-686-unsigned_4.7.8-1a~test_i386.deb
>  on Thinkpad T41
> 
>   -> reboot that Thinkpad -- and it worked fine  :-)

Great, thanks a lot for confirming that! Your triaging help is very
much appreciated.

I pushed the patch to the packaging repo for the next upload.

Regards,
Salvatore

Bug#841850: linux-image-4.7.0-1-686_4.7.8-1_i386.deb does not boot on Thinkpad T41

[Petra Ruebe-Pugliese]

On Wed. 26. Oct. 2016, at 09:05 Salvatore Bonaccorso (car...@debian.org) wrote:
> 
> > On Wednesday 26 October 2016 at 07:36:21 +0200  Salvatore Bonaccorso 
> > (car...@debian.org) wrote:
> > [...]
> > > 
> > > There seem to be an upstream fix now for this issue:
> > > 
> > > https://git.kernel.org/linus/ff8560512b8d4b7ca3ef4fd69166634ac30b2525
> > > 
> > > Can you by chance confirm that this works as well for you?
> > 
 [...]
> 
> Yes you can follow the same procedure starting from a new source tree
> without the previous applied. 
> 
> You can get the above patch as well directly via
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/patch/?id=ff8560512b8d4b7ca3ef4fd69166634ac30b2525
  Done
> so that you don't have to copy paste it from the webpage to a file. It
> should apply with only some fuzz to the source. 

 So I did the following:

  -> Create a new temporary directory and change into it

  -> apt-get source linux

  -> cd linux-4.7.8

  -> bash debian/bin/test-patches  -f 686  
../upstream-patch-ff8560512b8d4b7ca3ef4fd69166634ac30b2525 

  -> install the resulting
[...]  35M Oct 27 01:48 linux-image-4.7.0-1-686-unsigned_4.7.8-1a~test_i386.deb
 on Thinkpad T41

  -> reboot that Thinkpad -- and it worked fine  :-)

Best
Petra

Bug#841850: linux-image-4.7.0-1-686_4.7.8-1_i386.deb does not boot on Thinkpad T41

[Salvatore Bonaccorso]

Hi Petra,

On Wed, Oct 26, 2016 at 08:26:32AM +0200, Petra Ruebe-Pugliese wrote:
> Hi,
> 
> On Wednesday 26 October 2016 at 07:36:21 +0200  Salvatore Bonaccorso 
> (car...@debian.org) wrote:
> [...]
> > 
> > There seem to be an upstream fix now for this issue:
> > 
> > https://git.kernel.org/linus/ff8560512b8d4b7ca3ef4fd69166634ac30b2525
> > 
> > Can you by chance confirm that this works as well for you?
> 
>  Not sure.  I am not at all knowledgeable in kernel compilation.
>  I did what I did last time by rigorously following the
>  explanations on
>  
> https://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-official
> 
>  So should I start again with the same basic sources as obtained
>  by yesterday's "apt-get source linux" and then call
>  "bash debian/bin/test-patches ../newpatch"
>  where "newpatch" would be a file containing the final lines
>  from that webpage, i.e.:
> 
> -snip-
> diff --git a/arch/x86/kernel/smpboot.c b/arch/x86/kernel/smpboot.c
> index 951f093..42f5eb7 100644
> --- a/arch/x86/kernel/smpboot.c
> +++ b/arch/x86/kernel/smpboot.c
> @@ -1409,15 +1409,17 @@ __init void prefill_possible_map(void)
>  
>   /* No boot processor was found in mptable or ACPI MADT */
>   if (!num_processors) {
> - int apicid = boot_cpu_physical_apicid;
> - int cpu = hard_smp_processor_id();
> + if (boot_cpu_has(X86_FEATURE_APIC)) {
> + int apicid = boot_cpu_physical_apicid;
> + int cpu = hard_smp_processor_id();
>  
> - pr_warn("Boot CPU (id %d) not listed by BIOS\n", cpu);
> + pr_warn("Boot CPU (id %d) not listed by BIOS\n", cpu);
>  
> - /* Make sure boot cpu is enumerated */
> - if (apic->cpu_present_to_apicid(0) == BAD_APICID &&
> - apic->apic_id_valid(apicid))
> - generic_processor_info(apicid, boot_cpu_apic_version);
> + /* Make sure boot cpu is enumerated */
> + if (apic->cpu_present_to_apicid(0) == BAD_APICID &&
> + apic->apic_id_valid(apicid))
> + generic_processor_info(apicid, 
> boot_cpu_apic_version);
> + }
>  
>   if (!num_processors)
>   num_processors = 1;
> -snap-
> 
>  If so, I could start that experiment tonight and have a look
>  at the result tomorrow morning.

Yes you can follow the same procedure starting from a new source tree
without the previous applied. 

You can get the above patch as well directly via
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/patch/?id=ff8560512b8d4b7ca3ef4fd69166634ac30b2525
so that you don't have to copy paste it from the webpage to a file. It
should apply with only some fuzz to the source. 

Thanks a lot for testing,

If it is confirmed, then I can attach the attached changes to the
packaging repository.

Regards,
Salvatore
>From 8b720b82338b2995badbde42b6156b6f8738538b Mon Sep 17 00:00:00 2001
From: Salvatore Bonaccorso 
Date: Wed, 26 Oct 2016 08:14:56 +0200
Subject: [PATCH] [x86] boot/smp: Don't try to poke disabled/non-existent APIC

Closes: #841850
---
 debian/changelog   |  5 ++
 ...p-Don-t-try-to-poke-disabled-non-existent.patch | 73 ++
 debian/patches/series  |  1 +
 3 files changed, 79 insertions(+)
 create mode 100644 debian/patches/bugfix/x86/x86-boot-smp-Don-t-try-to-poke-disabled-non-existent.patch

diff --git a/debian/changelog b/debian/changelog
index 7242a7f..c5aef53 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,10 +1,15 @@
 linux (4.8.4-1~exp2) UNRELEASED; urgency=medium
 
+  [ Ben Hutchings ]
   * cpufreq: Re-enable CPU_FREQ_STAT, which can no longer be modular
   * [armhf] dts: imx53: add support for USB armory board (Closes: #840137)
   * kconfig: Renumber SYMBOL_NEW, fixing regression of allnoconfig
 (Closes: #841357)
 
+  [ Salvatore Bonaccorso ]
+  * [x86] boot/smp: Don't try to poke disabled/non-existent APIC
+(Closes: #841850)
+
  -- Ben Hutchings   Mon, 24 Oct 2016 02:25:26 +0100
 
 linux (4.8.4-1~exp1) experimental; urgency=medium
diff --git a/debian/patches/bugfix/x86/x86-boot-smp-Don-t-try-to-poke-disabled-non-existent.patch b/debian/patches/bugfix/x86/x86-boot-smp-Don-t-try-to-poke-disabled-non-existent.patch
new file mode 100644
index 000..663982a
--- /dev/null
+++ b/debian/patches/bugfix/x86/x86-boot-smp-Don-t-try-to-poke-disabled-non-existent.patch
@@ -0,0 +1,73 @@
+From: =?UTF-8?q?Ville=20Syrj=C3=A4l=C3=A4?= 
+Date: Sat, 22 Oct 2016 05:18:04 +0300
+Subject: x86/boot/smp: Don't try to poke disabled/non-existent APIC
+MIME-Version: 1.0
+Content-Type: text/plain; charset=UTF-8

Bug#841850: linux-image-4.7.0-1-686_4.7.8-1_i386.deb does not boot on Thinkpad T41

[Petra Ruebe-Pugliese]

Hi,

On Wednesday 26 October 2016 at 07:36:21 +0200  Salvatore Bonaccorso 
(car...@debian.org) wrote:
[...]
> 
> There seem to be an upstream fix now for this issue:
> 
> https://git.kernel.org/linus/ff8560512b8d4b7ca3ef4fd69166634ac30b2525
> 
> Can you by chance confirm that this works as well for you?

 Not sure.  I am not at all knowledgeable in kernel compilation.
 I did what I did last time by rigorously following the
 explanations on
 
https://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-official

 So should I start again with the same basic sources as obtained
 by yesterday's "apt-get source linux" and then call
 "bash debian/bin/test-patches ../newpatch"
 where "newpatch" would be a file containing the final lines
 from that webpage, i.e.:

-snip-
diff --git a/arch/x86/kernel/smpboot.c b/arch/x86/kernel/smpboot.c
index 951f093..42f5eb7 100644
--- a/arch/x86/kernel/smpboot.c
+++ b/arch/x86/kernel/smpboot.c
@@ -1409,15 +1409,17 @@ __init void prefill_possible_map(void)
 
/* No boot processor was found in mptable or ACPI MADT */
if (!num_processors) {
-   int apicid = boot_cpu_physical_apicid;
-   int cpu = hard_smp_processor_id();
+   if (boot_cpu_has(X86_FEATURE_APIC)) {
+   int apicid = boot_cpu_physical_apicid;
+   int cpu = hard_smp_processor_id();
 
-   pr_warn("Boot CPU (id %d) not listed by BIOS\n", cpu);
+   pr_warn("Boot CPU (id %d) not listed by BIOS\n", cpu);
 
-   /* Make sure boot cpu is enumerated */
-   if (apic->cpu_present_to_apicid(0) == BAD_APICID &&
-   apic->apic_id_valid(apicid))
-   generic_processor_info(apicid, boot_cpu_apic_version);
+   /* Make sure boot cpu is enumerated */
+   if (apic->cpu_present_to_apicid(0) == BAD_APICID &&
+   apic->apic_id_valid(apicid))
+   generic_processor_info(apicid, 
boot_cpu_apic_version);
+   }
 
if (!num_processors)
num_processors = 1;
-snap-

 If so, I could start that experiment tonight and have a look
 at the result tomorrow morning.

Petra  (now away for most of the day)

Bug#841850: linux-image-4.7.0-1-686_4.7.8-1_i386.deb does not boot on Thinkpad T41

[Salvatore Bonaccorso]

Hi Ben, hi Petra,

On Mon, Oct 24, 2016 at 02:35:07PM +0100, Ben Hutchings wrote:
> On Mon, 2016-10-24 at 11:49 +0200, Petra Ruebe-Pugliese wrote:
> [...]
> >  Okay.  So I've sacrificed the less important of the two
> >  notebooks again and repeated the "apt-get dist-upgrade"
> >  so that the current kernel got installed again.
> > 
> >  In doing so, two messages appeared that looked approximately
> >  like this:
> > 
> >   /etc/kernel-img.conf:4: ignoring unknown parameter relative_links
> >   /etc/kernel-img.conf:6: ignoring unknown parameter do_bootfloppy
> >
> >  The second of these lines reminds me of the fact that with
> >  previous kernel versions the boot process used to stop in the
> >  same place for quite some (disquieting!) time and then continued
> >  with some message about a read error on /dev/fd
> 
> I don't know what 'do_bootfloppy' used to do, but I think it's unrelated to 
> loading of the floppy driver.  It sounds like you have quite an old 
> installation that might also have some obsolete scripts left in the boot 
> process.  Also, note that the /dev/fd directory is unrelated to floppy drives.
> 
> >  This was the case on all my computers, although these two
> >  thinkpads no longer have a floppy drive.
> > 
> >  Now to the photo.  I've tried to make one.
> >  With these new boot parameters there is a lot of output rushing
> >  through which I could not catch.  So I'm sending only what was
> >  to be seen when it stopped.  Maybe that's enough to put you on
> >  the right track.  If not, please tell me what else I can do
> >  to bring some light into the matter.
> 
> OK, this is the same crash that someone else reported and I think I
> know which change triggered it (though not why).

There seem to be an upstream fix now for this issue:

https://git.kernel.org/linus/ff8560512b8d4b7ca3ef4fd69166634ac30b2525

Can you by chance confirm that this works as well for you?

Regards,
Salvatore

Bug#841850: linux-image-4.7.0-1-686_4.7.8-1_i386.deb does not boot on Thinkpad T41

[Petra Ruebe-Pugliese]

On Monday, 24 October 2016, at 14:35 Ben Hutchings (b...@decadent.org.uk) wrote:
[...]
> 
> OK, this is the same crash that someone else reported and I think I
> know which change triggered it (though not why).
> 
> Does the attached patch fix the crash?  (Instructions for rebuilding
> the package are at
> .)
> 
> Ben.

 The third attempt to generate that patched kernel finally
 succeeded (doing the compilation overnight, with a large
 external harddisk as additional storage medium).

 I installed the resulting
   35M Oct 26 03:44 linux-image-4.7.0-1-686-unsigned_4.7.8-1a~test_i386.deb
 on one of the affected notebooks, and it booted flawlessly  :-)

 Petra

Bug#841850: linux-image-4.7.0-1-686_4.7.8-1_i386.deb does not boot on Thinkpad T41

[Ben Hutchings]

On Mon, 2016-10-24 at 11:49 +0200, Petra Ruebe-Pugliese wrote:
[...]
>  Okay.  So I've sacrificed the less important of the two
>  notebooks again and repeated the "apt-get dist-upgrade"
>  so that the current kernel got installed again.
> 
>  In doing so, two messages appeared that looked approximately
>  like this:
> 
>   /etc/kernel-img.conf:4: ignoring unknown parameter relative_links
>   /etc/kernel-img.conf:6: ignoring unknown parameter do_bootfloppy
>
>  The second of these lines reminds me of the fact that with
>  previous kernel versions the boot process used to stop in the
>  same place for quite some (disquieting!) time and then continued
>  with some message about a read error on /dev/fd

I don't know what 'do_bootfloppy' used to do, but I think it's unrelated to 
loading of the floppy driver.  It sounds like you have quite an old 
installation that might also have some obsolete scripts left in the boot 
process.  Also, note that the /dev/fd directory is unrelated to floppy drives.

>  This was the case on all my computers, although these two
>  thinkpads no longer have a floppy drive.
> 
>  Now to the photo.  I've tried to make one.
>  With these new boot parameters there is a lot of output rushing
>  through which I could not catch.  So I'm sending only what was
>  to be seen when it stopped.  Maybe that's enough to put you on
>  the right track.  If not, please tell me what else I can do
>  to bring some light into the matter.

OK, this is the same crash that someone else reported and I think I
know which change triggered it (though not why).

Does the attached patch fix the crash?  (Instructions for rebuilding
the package are at
.)

Ben.

-- 
Ben Hutchings
For every complex problem
there is a solution that is simple, neat, and wrong.
From 21285bd44b2144b121eeb35abed99fa6ece2a5a4 Mon Sep 17 00:00:00 2001
From: Ben Hutchings 
Date: Mon, 24 Oct 2016 03:05:42 +0100
Subject: [PATCH] Revert "arch/x86: Handle non enumerated CPU after physical
 hotplug"

This reverts commit 4927f9e7a267883ca0741d3fefa063faf43a9344, which
was commit 2a51fe083eba7f99cbda72f5ef90cdf2f4df882c upstream.
---
 arch/x86/kernel/smpboot.c | 18 +++---
 1 file changed, 3 insertions(+), 15 deletions(-)

diff --git a/arch/x86/kernel/smpboot.c b/arch/x86/kernel/smpboot.c
index 82b17373b66a..75a045424be7 100644
--- a/arch/x86/kernel/smpboot.c
+++ b/arch/x86/kernel/smpboot.c
@@ -1406,21 +1406,9 @@ __init void prefill_possible_map(void)
 {
 	int i, possible;
 
-	/* No boot processor was found in mptable or ACPI MADT */
-	if (!num_processors) {
-		int apicid = boot_cpu_physical_apicid;
-		int cpu = hard_smp_processor_id();
-
-		pr_warn("Boot CPU (id %d) not listed by BIOS\n", cpu);
-
-		/* Make sure boot cpu is enumerated */
-		if (apic->cpu_present_to_apicid(0) == BAD_APICID &&
-		apic->apic_id_valid(apicid))
-			generic_processor_info(apicid, boot_cpu_apic_version);
-
-		if (!num_processors)
-			num_processors = 1;
-	}
+	/* no processor from mptable or madt */
+	if (!num_processors)
+		num_processors = 1;
 
 	i = setup_max_cpus ?: 1;
 	if (setup_possible_cpus == -1) {


signature.asc
Description: This is a digitally signed message part

Bug#841850: linux-image-4.7.0-1-686_4.7.8-1_i386.deb does not boot on Thinkpad T41

[Ben Hutchings]

Control: severity -1 important
Control: tag -1 moreinfo

On Sun, 2016-10-23 at 22:17 +0200, Petra Ruebe-Pugliese wrote:
> Package: src:linux
> Version: 4.7.8-1
> Severity: critical
> Justification: breaks the whole system
> 
> Dear Maintainer,
> 
> when performing this week's regular update on my Debian Testing
> systems, linux-image-4.7.0-1-686 was updated from 4.7.6-1 to
> 4.7.8-1_i386.deb on two Thinkpads T41.
> 
> On both of them, the system failed to boot after that update:
> grub started correctly and let me "choose" the system to boot
> (there is only one!);  after that I saw a blank screen with a
> blinking cursor in the upper left corner, and that was all.
> Something seemed to be "going on" (fan working more than usual);
> but no further reaction was to be obtained from the system(s).
> 
> Downgrading to linux-image-4.7.0-1-686_4.7.6-1_i386.deb via
> rescue-CD and "dpkg -i" (fortunately!!!) solved the problem.

> (There was no similar problem with linux-image-4.7.0-1-686-pae_4.7.8-
> 1_i386.deb
>  on two old PCs I was updating at the same time, nor with the
>  corresponding version on an AMD64 PC.)

Or on most other PCs, it seems - so I'm reducing the severity.

> -- Package-specific info:
> ** Version:
> Linux version 4.7.0-1-686 (debian-ker...@lists.debian.org) (gcc
> version 5.4.1 20160904 (Debian 5.4.1-2) ) #1 SMP Debian 4.7.6-1
> (2016-10-07)
> 
>  4.7.6-1 is now running correctly again, 4.7.8-1 did not boot, see
> above!
>  (So the first line does _not_ describe the problematic system!)
[...]

We're going to need some more information about where things went
wrong, which you should be able to get by replacing the 'quiet'
parameter on the boot command line with 'earlyprintk=vga'.  Please send
a photo of the log messages.

Ben.

-- 
Ben Hutchings
For every complex problem
there is a solution that is simple, neat, and wrong.

signature.asc
Description: This is a digitally signed message part

Bug#841850: linux-image-4.7.0-1-686_4.7.8-1_i386.deb does not boot on Thinkpad T41

[Petra Ruebe-Pugliese]

Package: src:linux
Version: 4.7.8-1
Severity: critical
Justification: breaks the whole system

Dear Maintainer,

when performing this week's regular update on my Debian Testing
systems, linux-image-4.7.0-1-686 was updated from 4.7.6-1 to
4.7.8-1_i386.deb on two Thinkpads T41.

On both of them, the system failed to boot after that update:
grub started correctly and let me "choose" the system to boot
(there is only one!);  after that I saw a blank screen with a
blinking cursor in the upper left corner, and that was all.
Something seemed to be "going on" (fan working more than usual);
but no further reaction was to be obtained from the system(s).

Downgrading to linux-image-4.7.0-1-686_4.7.6-1_i386.deb via
rescue-CD and "dpkg -i" (fortunately!!!) solved the problem.

(There was no similar problem with linux-image-4.7.0-1-686-pae_4.7.8-1_i386.deb
 on two old PCs I was updating at the same time, nor with the
 corresponding version on an AMD64 PC.)

Greetings
  Petra


-- Package-specific info:
** Version:
Linux version 4.7.0-1-686 (debian-ker...@lists.debian.org) (gcc version 5.4.1 
20160904 (Debian 5.4.1-2) ) #1 SMP Debian 4.7.6-1 (2016-10-07)

 4.7.6-1 is now running correctly again, 4.7.8-1 did not boot, see above!
 (So the first line does _not_ describe the problematic system!)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-4.7.0-1-686 
root=UUID=496e0e0a-6e7c-46c2-9132-315243394a2d ro framebuffer=false quiet 
fb=false systemd.show_status=true

** Not tainted

** Kernel log:
[   28.664766] [drm] register mmio size: 65536
[   28.665108] agpgart-intel :00:00.0: AGP 2.0 bridge
[   28.665133] agpgart-intel :00:00.0: putting AGP V2 device into 1x mode
[   28.665183] radeon :01:00.0: putting AGP V2 device into 1x mode
[   28.665218] radeon :01:00.0: GTT: 256M 0xD000 - 0xDFFF
[   28.665236] radeon :01:00.0: VRAM: 128M 0xE000 - 
0xE7FF (32M used)
[   28.665802] [drm] Detected VRAM RAM=128M, BAR=128M
[   28.665812] [drm] RAM width 64bits DDR
[   28.666000] [TTM] Zone  kernel: Available graphics memory: 254772 kiB
[   28.666007] [TTM] Initializing pool allocator
[   28.666094] [drm] radeon: 32M of VRAM memory ready
[   28.666102] [drm] radeon: 256M of GTT memory ready.
[   28.666165] [drm] radeon: power management initialized
[   28.672409] radeon :01:00.0: WB disabled
[   28.672430] radeon :01:00.0: fence driver on ring 0 use gpu addr 
0xd000 and cpu addr 0xe0784000
[   28.672438] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[   28.672444] [drm] Driver supports precise vblank timestamp query.
[   28.672473] [drm] radeon: irq initialized.
[   28.672503] [drm] Loading R100 Microcode
[   29.806006] Adding 1253032k swap on /dev/sda5.  Priority:-1 extents:1 
across:1253032k FS
[   31.399282] radeon :01:00.0: firmware: direct-loading firmware 
radeon/R100_cp.bin
[   31.399675] [drm] radeon: ring at 0xD0001000
[   31.399708] [drm] ring test succeeded in 1 usecs
[   31.400728] [drm] ib test succeeded in 0 usecs
[   31.415037] [drm] Panel ID String: 1024x768
[   31.415051] [drm] Panel Size 1024x768
[   31.415229] [drm] No TV DAC info found in BIOS
[   31.415399] [drm] Radeon Display Connectors
[   31.415406] [drm] Connector 0:
[   31.415411] [drm]   VGA-1
[   31.415420] [drm]   DDC: 0x60 0x60 0x60 0x60 0x60 0x60 0x60 0x60
[   31.415425] [drm]   Encoders:
[   31.415430] [drm] CRT1: INTERNAL_DAC1
[   31.415436] [drm] Connector 1:
[   31.415440] [drm]   DVI-D-1
[   31.415445] [drm]   HPD1
[   31.415453] [drm]   DDC: 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64
[   31.415458] [drm]   Encoders:
[   31.415463] [drm] DFP1: INTERNAL_TMDS1
[   31.415468] [drm] Connector 2:
[   31.415473] [drm]   LVDS-1
[   31.415477] [drm]   Encoders:
[   31.415482] [drm] LCD1: INTERNAL_LVDS
[   31.415487] [drm] Connector 3:
[   31.415491] [drm]   SVIDEO-1
[   31.415496] [drm]   Encoders:
[   31.415500] [drm] TV1: INTERNAL_DAC2
[   31.519004] [drm] fb mappable at 0xE004
[   31.519014] [drm] vram apper at 0xE000
[   31.519018] [drm] size 786432
[   31.519022] [drm] fb depth is 8
[   31.519026] [drm]pitch is 1024
[   31.524653] fbcon: radeondrmfb (fb0) is primary device
[   31.581140] Console: switching to colour frame buffer device 128x48
[   31.586351] radeon :01:00.0: fb0: radeondrmfb frame buffer device
[   31.586745] [drm] Initialized radeon 2.45.0 20080528 for :01:00.0 on 
minor 0
[   35.646219] systemd-sysv-generator[416]: Overwriting existing symlink 
/run/systemd/generator.late/chrony.service with real service.
[  371.780145] usb 1-4: new high-speed USB device number 2 using ehci-pci
[  371.912886] usb 1-4: New USB device found, idVendor=0781, idProduct=5406
[  371.912899] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  371.912909] usb 1-4: Product: U3 Cruzer Micro
[  371.912917] usb 1-4: Manufacturer: SanDisk
[  371.912926] usb 1-4: SerialNumber: 08782107F6117022
[