Bug#901921: I have a mor helpfull oops dump on this. See attachment.

2018-06-23 Thread Wil van Lierop
Regards, Oops#1 Part1 <4>[16465.655648] CR2: CR3: 000427a0a002 CR4: 003606e0 <4>[16465.655683] DR0: DR1: DR2: <4>[16465.655718] DR3: DR6: fffe0ff0 DR7: 0400 <4>[16465.655759] Call

Bug#901921: linux-image-4.16.0-2-amd64: kernel oops on shutdown

2018-06-20 Thread Wil van Lierop
Package: src:linux Version: 4.16.16-1 Severity: important Tags: d-i Dear Maintainer, * What led up to the situation? Trying to shutdown system. * What exactly did you do (or not do) that was effective (or ineffective)? Trying a gracefull shutdown of the system. * What was

Bug#891364: firmware-amd-graphics: please update amdgpu firmware for polaris10

2018-02-24 Thread Wil van Lierop
Package: firmware-amd-graphics Version: 20170823-1 Severity: wishlist Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? dmesg repeatedly could not load firmware. * What exactly did you do (or not do) that wa

Bug#673597: [gnuradio] no --theme gnome directories on a KDE system leaves package broken on configure

2012-05-19 Thread wil van lierop
Package: gnuradio Version: 3.5.3.2-1 Severity: grave --- Please enter the report below this line. --- Package can not be configured after install and result in broken installation. Adding set -x to the post install and/or post removal script reveals the issue on a KDE wheezy desktop. wil@

Bug#566528: [cpufreqd] cpufreq-info no longer returns correct frequency range

2010-01-24 Thread Wil van Lierop (dutchfish)
On Sunday 24 January 2010 04:21:08 you wrote: > can you describe what goes wrong? What do you do and what do you expect > to happen? I have tested this on 2.6.32.3 to 2.6.32.5 and with 2.6.32-trunk-amd64 from debian/testing. Since cpufreqd 2.3.3-4: 1. current policy: frequency should be within

Bug#566528: [cpufreqd] cpufreq-info no longer returns correct frequency range

2010-01-23 Thread Wil van Lierop (dutchfish)
Package: cpufreqd Version: 2.3.3-4 Severity: normal --- Please enter the report below this line. --- since 2.3.3-4 something goes wrong with setting correct min/max settings used governer. Correct hardware limts are however detected. cpufrequtils 006: cpufreq-info (C) Dominik Brodowski 2004-20

Bug#467508: kernel oops with screen and networked application

2008-02-25 Thread Wil van Lierop
Package: linux-image-2.6.18-6-486 Version: 2.6.18.dfsg.1-18etch1 Severity: critical Justification: breaks the whole system Prerequisites: Running a so called screen under root user simultane with a screen session under a non-priviliged user containing a networked application that has a reasonab