[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#746312: marked as done (Toshiba Satellite Pro 4220: needs acpi=off with kernel 3.13/3.14)

Your message dated Mon, 31 Aug 2020 01:34:16 +0200
with message-id <20200830233414.7373bf7skdsttcgq@percival.namespace.at>
and subject line Re: Bug#748517: Solved in 3.14.7-1
has caused the Debian Bug report #748517,
regarding Toshiba Satellite Pro 4220: needs acpi=off with kernel 3.13/3.14
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 have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
748517: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748517
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-image-13.1-686-pae
Version: linux-image-3.13-1-686-pae
Severity: normal

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation? Upgrade to Kernel 3.13 on Testing
   * What exactly did you do (or not do) that was effective (or
     ineffective)? Boot Kernel 3.13
   * What was the outcome of this action? Laptop becomes very slow and unresponive
   * What outcome did you expect instead? Normal performance. Up to Kernel 3.12, everything was 
*** End of the template - remove these template lines ***


-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'testing-updates'), (102, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 3.13-1-686-pae (SMP w/1 CPU core)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

--- End Message ---
--- Begin Message --- 
* Daniel Wiese <dnl.wiese@googlemail.com>:
> After updating to version 3.14.7-1, the problem disappeared.

Thanks for the feedback, closing this report.

Chris

--- End Message ---
Reply to: