For some reason a new apt-get dist-upgrade fixed bug. A new kernel package was pulled but the version did not change.
On 7/7/12, Jonathan Nieder <jrnie...@gmail.com> wrote: > Hi, > > Joshua wrote: > >> Version: 3.0.0-3 > [...] >> I have some nonstandard console settings that require running >> /etc/init.d/kbd to configure console. Using the newer console-setup >> is a non-starter for reasons that are not relevant at this time. >> >> Somewhere in the last two months (it's hard to tell exactly), there >> was a regression such that after restoring from hibernate, some >> console settings are not restored correctly. Running /etc/init.d/kbd >> start successfully restores them. > > Thanks for reporting. Before investigating further, a few questions: > > The Debian kernel team does not maintain 3.0.y any more. Does a 3.2.y > or 3.4.y kernel reproduce the problem? > > You mentioned that this is a regression. What is the oldest broken > kernel and newest non-broken one you know of? (/var/log/dpkg.log > might help to jog memory, and there are precompiled historical kernels > at http://snapshot.debian.org/ if you need to test some.) > > Can you more precisely describe the symptoms? If I had the same > hardware as you, what steps should I perform to reproduce the bug, > what is the expected result, what happens instead, and how does the > difference indicate a bug? > > Hope that helps, > Jonathan > -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/ca+jjjyseekf8kd+6iihej1soeno04gqucmtxhnk4vtg7zco...@mail.gmail.com
