Bug#969747: next API change already fixed upstream
Hi, I have to correct myself regarding > However even 0.10.1-1 will stop working in a few months as it says > 'Met.no LocationforecastLTS API states that this version > of the webservice is deprecated, and the plugin needs to be > adapted to use a newer version, or it will stop working within > a few months. > Please file a bug on https://bugzilla.xfce.org if no one > else has done so yet.' > Unfortunately so far even upstream does not provide an update as > 'Latest Release > 0.10.0 (2019/08/11) > xfce4-weather-plugin-0.10.0.tar.bz2' > https://docs.xfce.org/panel-plugins/xfce4-weather-plugin#latest_release Now XFCE is maintained elsewhere: https://gitlab.xfce.org/panel-plugins/xfce4-weather-plugin And someone claimed at upstream that there is already a patch to 0.10.1 that will allow plugin to work after the coming API change = from 1.9 to 2.0 in panel-plugin/weather.h: https://gitlab.xfce.org/panel-plugins/xfce4-weather-plugin/-/issues/23 https://gitlab.xfce.org/panel-plugins/xfce4-weather-plugin/-/issues/18 patch: https://gitlab.xfce.org/panel-plugins/xfce4-weather-plugin/-/commit/97601ab2ad1f9810516be6d3d91c5c9b16d6397a I did not try it from my side as I don't know how to make a debian package from upstream source. Dear Maintainer, May I ask you to kindly - update Sid using latest '0.10.1' from trunk which is apparently more up to date than 0.10.1-1+b1 currently in sid ? - update Buster ? as 0.8.10-1 is now useless as it uses an obsolete API and thus cannot get weather data anymore. Thank you, Franck Richter
Bug#969747: fixed in xfce4-weather-plugin 0.10.1-1
Control: fixed -1 0.10.1-1 Control: merge -1 970259 Hi Alexis & FX, It is normal that xfce4-weather-plugin 0.8.10-1 does not work anymore. See Jiff bug report #970259 for explanations. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970259 Above report propose a patch & an unofficial .deb. I did not try any of them. You can fix xfce4-weather-plugi by upgrading to 0.10.1-1 (current version in Bullseye) You can't install Bullseye binary .deb due to dependencies (as Alexis reported). But you can compile it from source: https://packages.debian.org/source/bullseye/xfce4-weather-plugin I did it and plugin works in Buster. However even 0.10.1-1 will stop working in a few months as it says 'Met.no LocationforecastLTS API states that this version of the webservice is deprecated, and the plugin needs to be adapted to use a newer version, or it will stop working within a few months. Please file a bug on https://bugzilla.xfce.org if no one else has done so yet.' Unfortunately so far even upstream does not provide an update as 'Latest Release 0.10.0 (2019/08/11) xfce4-weather-plugin-0.10.0.tar.bz2' https://docs.xfce.org/panel-plugins/xfce4-weather-plugin#latest_release BR, Franck Richter
Bug#920759: workaround
Control: retitle -1 (with workaround) amdgpu+linux-images 4.9 & 4.19 crash randomly & always after X started, when dpm is enabled Workaround: disable dynamic power management ex: put in /etc/default/grub: GRUB_CMDLINE_LINUX_DEFAULT="quiet amdgpu.dpm=0" Mechanism guess: As behavior (works or crashes) depends of linux-image package (see below), and seems to evolve randomly across package versions (an older package version works, then a newer crashes, then a newer newer works again): This suggests that a variable/structure is not properly initialized inside amdgpu dynamic power management code. Then depending of the RAM content during package compilation, a good value (=> package will work) or a bad value (=> will crash) is built-in inside the package. This could explain the apparent random behavior across package versions. Work = (C) + (B) + linux-image-4.19.0-0.bpo.4-amd64-unsigned 4.19.28-2~bpo9+1 = upstream 10-Mar-2019 Crash = (B) + linux-image-4.19.0-0.bpo.4-amd64-unsigned 4.19.28-2~bpo9+1 = upstream 10-Mar-2019 Work = (B) + linux-image-4.19.0-0.bpo.2-amd64-unsigned 4.19.16-1~bpo9+1 = upstream 16-Jan-2019 Crash = (B) + linux-image-4.9.0-9-amd64 4.9.161-1 = upstream 27-Feb-2019 Crash = (A) + linux-image-4.9.0-8-amd64 4.9.144-1 = upstream 08-Dec-2018 Work = (A) + linux-image-4.9.0-8-amd64 4.9.135-1 = upstream 20-Oct-2018 (C) = disabled dynamic power management (B) = (firmware-amd-graphics 20190114-1) + (1920x1200 59.95Hz 8bit per RGB = nothing special) (A) = (firmware-amd-graphics 20161130-4) Kind Regards, Franck
Bug#920759: amdgpu+linux-images 4.9 & 4.19 crash randomly & always after X started
Control: retitle -1 amdgpu+linux-images 4.9 & 4.19 crash randomly & always after X started Control: found -1 4.19.28-2~bpo9+1 Control: found -1 4.9.161-1 I wonder why I bought a radeon RX card...
Bug#920759: amdgpu+linux-images 4.9 & 4.19 crash randomly & always after X started
With kernel driver amdgpu & [AMD/ATI] Baffin [Polaris11] (radeon RX560). Unfortunately new releases of kernel images crash too. => 4.19 is not anymore the solution vs 4.9. linux-images 4.9 & 4.19 often (not systematically) crash randomly & always after X started (but I am seldomly a few minutes in console mode). Usually within a few minutes after login. I wonder why a version works, then a newer crashes, even with very different patch application dates, ex: 4.9.135 of 20-Oct-2018 works & 4.19.16 of 16-Jan-2019 works, whereas in between 4.9.144-1 of 08-Dec-2018 crashes. CrashZ (T>10, T>C)= (B) + linux-image-4.19.0-0.bpo.4-amd64-unsigned 4.19.28-2~bpo9+1 = upstream 10-Mar-2019 Work (T>>10) = (B) + linux-image-4.19.0-0.bpo.2-amd64-unsigned 4.19.16-1~bpo9+1 = upstream 16-Jan-2019 CrashM (T=C=1) = (B) + linux-image-4.9.0-9-amd64 4.9.161-1 = upstream 27-Feb-2019 Crash = (A) + linux-image-4.9.0-8-amd64 4.9.144-1 = upstream 08-Dec-2018 Work= (A) + linux-image-4.9.0-8-amd64 4.9.135-1 = upstream 20-Oct-2018 CrashZ = hard crashes: Keyboard do not respond anymore & Magic SysRq key do not work. CrashM = Magic SysRq keys work (and allow a safe reboot). T=number of tests C=number of crashes (B) = (firmware-amd-graphics 20190114-1) + (1920x1200 59.95Hz 8bit per RGB = nothing special) (A) = (firmware-amd-graphics 20161130-4) Graphic card: PowerColor Red Dragon Radeon™ RX 560 16CU 2GB GDDR5 OC RADEON RX 560 AXRX 560 2GBD5-DHV2/OC https://www.powercolor.com/product?id=1496308686 'AMDGPU(0): Chipset: "POLARIS11" (ChipID = 0x67ff)' Kind Regards, Franck
Bug#920759: 4.19.16-1 does not crash
4.19.16-1 does not crash. linux-image-4.19.0-0.bpo.2-amd 4.19.16-1~bpo9+1 (stretch-backports) but one has to update to firmware-amd-graphics 20190114-1 (from testing buster) otherwise X does not start with firmware-amd-graphics 20161130-4 (from stretch) Kind Regards, Franck
Bug#921121: reported upstream
Hi Sven & Kathryn,
Sven, thanks for your workaround.
FYI regarding "Does anyone know how to contact the admins of this service?"
Someone reported the same issue to mozilla:
https://bugzilla.mozilla.org/show_bug.cgi?id=1524830
Apparently it is more than just the aus server pointing to the wrong widevine
version, it is firefox that do not fetch esr version.
Thus another workaround was proposed in above bugzilla report:
cd /usr/lib/firefox-esr/defaults/pref
edit channel-prefs.js and change the line:
pref("app.update.channel", "default");
to
pref("app.update.channel", "esr");
then restart firefox.
It worked for me: 60.5.0esr-1~deb9u1 then automatically gets widevine
4.10.1196.0 instead of 1.4.8.1008
Regards,
Franck
Bug#862400: several bios updates exist since 2007
Hi Arturo, I cannot help for kernel, however, and you probably already know it: Several bios updates became available since 10/04/2007 version. Did you consider them ? (ie checking release logs) Will you try ? See http://h20564.www2.hpe.com/hpsc/swd/public/detail?swItemId=MTX_1304cdfaf92247a1836bac775b#tab-history RECOMMENDED * Systems ROMPaq Firmware Upgrade for HP ProLiant DL380 G5 (P56) Servers Type: BIOS (Entitlement Required) - System ROM Version: 2015.08.16 (A)(1 Oct 2015) Cheers, Franck
Bug#646606: xfce4: xfce launcher freeze X with calc
Package: xfce4 Version: 4.8.0.3 Severity: normal Dear Maintainer, How to reproduce: # aptitude install apcalc Create a new launcher in the panel. Then - Properties - Add 'Terminal' - Edit 'Terminal' Replace Command 'xfce4-terminal' by 'calc' Save everything and be sure to know SysRq keys. Activate launcher. X freeze (still visible, mouse move, but that's all. ctrl-alt-F1 dead). Note: calc works well if started in xfce4-terminal. Best regards, Franck -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages xfce4 depends on: ii gtk2-engines-xfce 2.8.1-3 ii orage 4.8.2-1 ii thunar 1.2.3-2 ii xfce4-appfinder4.8.0-3 ii xfce4-mixer4.8.0-2 ii xfce4-panel4.8.6-1 ii xfce4-session 4.8.2-1 ii xfce4-settings 4.8.2-2+b1 ii xfce4-utils4.8.2-3 ii xfconf 4.8.0-3 ii xfdesktop4 4.8.3-1 ii xfwm4 4.8.2-1 Versions of packages xfce4 recommends: ii desktop-base 6.0.7 ii tango-icon-theme 0.8.90-5 ii thunar-volman 0.6.0-4+b1 ii xfce4-notifyd 0.2.2-1 ii xorg 1:7.6+9 Versions of packages xfce4 suggests: ii xfce4-goodies 4.8.2 ii xfprint4 4.6.1-2 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#636075: boinc io stats confirmed, this is not with the client, though
Hi Steffen, Thank for your following up and confirmation that intensive writing can occur with some applications. Even if this is application related, I think boinc should offer to: - control the application. Ex: max write allowed is x Mb/unit (would be a good solution) and/or - report the application activity. Ex: application wrote today x Mb, avg y Mb/s (not a solution, but allows to detect a problem) Otherwise users have to blindly rely in application willingness to (1) inform if they make high disk IO (2) be bug free (one could imagine a bug leading to heavy IO) I think it is like for ram/cpu usage: user allows his computer to be used, but with some ram/cpu limitation. In a similar way boinc should allow to set some disk IO limitation (especially write IO). That's just my opinion. I am not sure how easy/time consuming it would be to implement this. So feel free to close this bug if you think this is not a priority for other users. Kind regards and thanks again, Franck -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#636075: boinc-client: Boinc is (too) disk intensive
Hi Steffen, Thanks for your input. As on your system you have low disk IO, I reinstalled boinc (this time manually on HDD) and checked one application at a time from project Wold Community Grid. 1 Conditions: IO throughput for 1 task running at a time (if 2 runnings at same time = I divided by 2 the write IO/hr) On a dual core Core2@3.2Ghz (faster CPU/more cores will have higher write IO). Set Task check point to disk at most every 6s 2 Findings: It is application dependant: - Nice applications (write small amount) (ca. 200kb/min) Help Conquer Cancer (ca. 800kb/min) FightAIDS@Home - Guilty application: The Clean Energy Project - Phase 2 This one write *** 2 to 2.9 Gb/hr *** ! (again only 1 running on one core on an old CPU) And nearly no read = that's a waste of participant's ressources and computer. 'System Requirements' announced on 'World Community Grid' says Memory Available 1,024 MB Disk Space 2,048 MB But nowhere it is indicated that it is so write intensive ! Their might be other guilty applications, but I cannot check them all. Furthermore it may be task dependant too. 3 Conclusion I think Boinc should control applications, and allow the user to set 'max writing', as it todays allow 'max cpu', 'max memory'. Thus suggested potential solutions: a- Applications to announce estimated write I/O (read I/O too?) b- Boinc allow user to limit max I/O per tasks (and if exceed, stop task use other applications). When user set, can compare to Application announcement to avoid starting with limit estimation. c- install by default in /home (ex: /home/boinc) not in /var/lib/boinc-client. This will increase the chances to land on a HDD and not on a SSD. 4 details 'Clean Energy Project - Phase 2' IO Conditions: - $ time iotop -u boinc -a might need to install 'aptitude install iotop' - check that Process ID are the same before and after measurements. Because some processes disappear and new ones appear (during same task!); but iotop only shows current running Processes, not anymore disappeared one = one can miss some IO. - with Project 'World Community Grid' Application 'The Clean Energy Project - Phase 2 6.40' Starting task E202831_920_C.27.C21H11NOS3Si.00590497.3.set1d06_1 using cep2 version 640 - Set Task check point to disk at most every 6s Result1: TID PRIO USER DISK READ DISK WRITE SWAPIN IOCOMMAND 5328 idle boinc 0.00 B 1180.60 M 0.00 % 0.01 % ../../projects/www.worldcommunitygrid.o~86.svp.n.opt 2378613406239751723 41381 0 5151 idle boinc 0.00 B140.00 K 0.00 % 0.00 % ../../projects/www.worldcommunitygrid.o~chem_prod_linux.x86 -float 1 -stop 43200 5153 idle boinc 0.00 B 32.00 K 0.00 % 0.00 % ../../projects/www.worldcommunitygrid.o~chem_prod_linux.x86 -float 1 -stop 43200 5330 idle boinc 0.00 B112.00 K 0.00 % 0.00 % ../../projects/www.worldcommunitygrid.o~86.svp.n.opt 2378613406239751723 41381 0 1951 idle boinc 0.00 B 84.00 K 0.00 % 0.00 % boinc --check_all_logins --redirectio --dir /var/lib/boinc-client 5152 idle boinc 0.00 B 0.00 B 0.00 % 0.00 % ../../projects/www.worldcommunitygrid.o~chem_prod_linux.x86 -float 1 -stop 43200 5329 idle boinc 0.00 B 0.00 B 0.00 % 0.00 % ../../projects/www.worldcommunitygrid.o~86.svp.n.opt 2378613406239751723 41381 0 real 26m45.474s user 0m10.609s sys0m2.836s 1180.6/(26*60+455)*3600/1024 = 2.06Gb/hr Result2: TID PRIO USER DISK READ DISK WRITE SWAPIN IOCOMMAND 5328 idle boinc 0.00 B829.65 M 0.00 % 0.01 % ../../projects/www.worldcommunitygrid.o~86.svp.n.opt 2378613406239751723 41381 0 5151 idle boinc 0.00 B 84.00 K 0.00 % 0.00 % ../../projects/www.worldcommunitygrid.o~chem_prod_linux.x86 -float 1 -stop 43200 5153 idle boinc 0.00 B 28.00 K 0.00 % 0.00 % ../../projects/www.worldcommunitygrid.o~chem_prod_linux.x86 -float 1 -stop 43200 5330 idle boinc 0.00 B 64.00 K 0.00 % 0.00 % ../../projects/www.worldcommunitygrid.o~86.svp.n.opt 2378613406239751723 41381 0 1951 idle boinc 0.00 B 56.00 K 0.00 % 0.00 % boinc --check_all_logins --redirectio --dir /var/lib/boinc-client 5152 idle boinc 0.00 B 0.00 B 0.00 % 0.00 % ../../projects/www.worldcommunitygrid.o~chem_prod_linux.x86 -float 1 -stop 43200 5329 idle boinc 0.00 B 0.00 B 0.00 % 0.00 % ../../projects/www.worldcommunitygrid.o~86.svp.n.opt 2378613406239751723 41381 0 real 16m55.249s user 0m6.636s sys0m1.816s 829.65/(16*60+55)*3600/1024 = 2.87Gb/hr ResultA: Just for the fun, I let it run Total DISK READ: 0.00 B/s | Total DISK WRITE: 0.00 B/s TID PRIO USER DISK READ DISK WRITE SWAPIN IO
Bug#636075: boinc-client: Boinc is (too) disk intensive
Hi Kevin, You probably posted as same time as me above. 3 points I disagree with you: 1. Clean Energy project system requirements do NOT state the high disk transfer. It just mention the large disk space needed (2Gb). (so nothing to see with the up to 2.9Gb/hr I found) Ref: When selecting projects in My Projects (https://secure.worldcommunitygrid.org/ms/viewMyProjects.do) there is a link near Clean Energy project stating Please review the system requirements before opting to participate in this project I stored this link in system_requirements.txt I don't see the disk transfer in it. 2. Boinc should control (1) your project and (2) where the data are saved See my 3 in previous message. 3. I never had 3 workunits running in parallel. I don't know why above shows like that (3 in progress = another bug ?, or because I aborted units ?), but I only have one dual core, so max 2 units runs in parallel. But you are right, I don't remember having seen 2 workunits from Clean Energy project running at same time. I do agree that further discussions specific to WCG should happen on WCG Forum. Thanks, Franck System Requirements What are the recommended minimum system specifications? How much data will I download and upload while participating with World Community Grid? How do I know if my computer is running the 64-bit research application? What are the recommended minimum system specifications? In order to participate in World Community Grid, you will need to have at least the following: The ability to display graphics (if you wish to see the graphics) An Internet connection In addition, each research project has its own requirement for memory and disk space. These are as follows: Research ProjectMemory AvailableDisk Space Operating Systems Computing for Clean Water 400 MB 100 MB Windows1,5, Mac, Linux3,5 The Clean Energy Project - Phase 2 1,024 MB2,048 MB Windows1, Mac, Linux3,4 Discovering Dengue Drugs - Together - Phase 2 1,024 MB250 MB Windows1, Mac, Linux3 Help Cure Muscular Dystrophy - Phase 2 64 MB 50 MB Windows1, Mac2, Linux3 Help Fight Childhood Cancer 250 MB 100 MB Windows1, Mac, Linux3 Help Conquer Cancer 250 MB 50 MB Windows1, Mac, Linux3 Human Proteome Folding - Phase 2250 MB 100 MB Windows1, Mac2, Linux3 FightAIDS@Home 250 MB 100 MB Windows1, Mac, Linux3 1. World Community Grid supports the following Windows platforms: Windows XP, Vista, 7, Server 2003, Server 2008 2. For these projects, only Mac computers using Intel processors are supported 3. Only Linux on x86 and x86-64 is supported 4. Users who choose to run this project are encouraged to set the 'Leave applications in memory while suspended' option in their device profile 5. 64-bit application available Return to Top How much data will I download and upload while participating with World Community Grid? The amount of data that you transfer depends upon how your processing preferences are set to run, how powerful your computer is and how often your computer is on. It also varies based upon which research projects you run on your computer. An average computer contributing to World Community Grid returns about 2 results per day. Each of the research projects at World Community Grid uses a different application, input files and output files. As a result, the size used for each of these varies by project. This is outlined on the chart below. Please note that the data is compressed during transfer and is decompressed after it has been downloaded. As a result it will occupy more space on disk than the numbers shown below. Research ProjectOne-Time Download Per Workunit Download Per Workunit Upload Computing for Clean Water 10 MB 0.001 MB0.5 MB The Clean Energy Project - Phase 2 200 MB 0.1 MB 20 - 80 MB Discovering Dengue Drugs - Together - Phase 2 10 MB 1-20 MB 1 MB Help Cure Muscular Dystrophy - Phase 2 0.7 MB 0.1 MB 0.2 MB Help Fight Childhood Cancer 1.0 MB 0.1 MB 0.1 MB Help Conquer Cancer 1.0 MB 0.1 MB 0.1 MB Human Proteome Folding - Phase 212.0 MB 1.5 MB 0.1 MB FightAIDS@Home 1.5 MB 0.1 MB 0.1 MB Return to Top How do I know if my computer is running the 64-bit research application? On a Windows machine, you can use the Windows task manager to view the process name. 64-bit research applications will end with windows_intelx86_64, while 32-bit applications will end with windows_intelx86 On a Linux machine, you can find the PID of the research application (which will start with the name wcg) and then execute the command file -L /proc//exe There is no 64-bit research application for Mac machines at this time.
Bug#636075: boinc-client: Boinc is (too) disk intensive
Hello Steffen, First thank you very much for your quick comments ! I am sorry that I couldn't convince you. The BOINC client itself does about nothing. How much IO is required just depends on the scientific application. I also thought that the IO amount may depend of the project, and not of boinc directly. But boinc manage the projects and I can only file bugs against boinc so I hope it is acceptable. Thanks for your '$du' data, but I wish to underline that the point is the disk IO amount, not the footprint on the disk. So 'du' will not help you to see it (because you can overwrite many times the same data, du will not show you that). (FYI from memory I had something like 100Mb footprint used by boinc. Now deleted (maybe I should have kept but...)) How is your disk IO amount ? $ iostat ( to have it you may need to #aptitude install sysstat ) I could suggest to upstream to have the individual projects announce their estimate for max disk space and disk I/O per task. - Yes announcing disk I/O write amount would be a good idea. - How do you think on ? (if easy to do) install by default in /home/boinc (create a specific user). This will increase the chances to land on a HDD and not on a SSD. Because I assume, normally people don't put their home on a SSD (and people having a laptop maybe won't run boinc). This would be a wishlist item, then. I put 'important' because it has a major effect on an SSD, which for me make boinc unusable. 4 important = a bug which has a major effect on the usability of a package, without rendering it completely unusable to everyone. My point was to warn other users about heavy writings involved, to avoid them wearing out to quickly their SSD. I don't think this belong to 'wishlist', because nobody would see it. I hope you can have the same opinion than me. If you are not yet convinced by your own iostat (then you are a lucky guy... or I must be very unlucky), here are: 1. from my ssd smart 198 Total Read Sectors 1054749553 199 Total Write Sectors 2404159500 200 Total Read Command 18727160 201 Total Write Command 18137047 208 avg Erase 485 209 remaining life 91 As you see, Total Write Total Read = To come to such Totals, I assume it is not linked to only one project, but to many projects. 2. boinc start-stop impact on iostat See start-stop-boinc-impact.txt Not so long test, but gives some ideas. Below command also showed high write activities when boinc was running. I have no records, but you should just let it run for a while and look at it. Time to time shots of several 10Mb are written. $ iostat -p /dev/sda 2 You had not mentioned the project you were joining. Sorry I didn't record which projects were runnings (2 at same time, dualcore) when I tested. Looking at http://www.worldcommunitygrid.org selected projects are: The Clean Energy Project - Phase 2 Help Conquer Cancer Human Proteome Folding - Phase 2 FightAIDS@Home Discovering Dengue Drugs - Together - Phase 2 The Clean Energy Project Discovering Dengue Drugs - Together These are the last tasks I ran X119570355201005271402_ 0-- In Progress 7/30/11 19:27:518/6/11 19:27:51 0.000.0 / 0.0 X119570353201005271402_ 0-- In Progress 7/30/11 19:27:518/6/11 19:27:51 0.000.0 / 0.0 X119570311201005271403_ 0-- In Progress 7/30/11 19:27:278/6/11 19:27:27 0.000.0 / 0.0 E202814_ 445_ C.28.C18H6N6OS2Se.00479563.4.set1d06_ 0-- In Progress 7/30/11 19:27:278/9/11 19:27:27 0.000.0 / 0.0 or465_ 6_ 10-- User Aborted7/30/11 19:24:047/30/11 19:27:270.000.0 / 0.0 X119571294201005131342_ 1-- User Aborted7/30/11 19:24:037/30/11 19:24:370.000.0 / 0.0 X119571297201005131342_ 1-- User Aborted7/30/11 19:23:457/30/11 19:27:270.010.4 / 0.0 E202814_ 977_ C.27.C19H8N4S3Se.00538161.3.set1d06_ 0-- User Aborted 7/30/11 19:23:427/30/11 19:27:270.010.3 / 0.0 faah23578_ ZINC00631422_ x1HHPxtl_ 03_ 1-- User Aborted7/30/11 13:14:367/30/11 16:39:550.000.1 / 0.0 E202811_ 452_ C.27.C24H14N2O.00075148.3.set1d06_ 0--User Aborted 7/30/11 11:23:297/30/11 16:39:550.113.5 / 0.0 X119500648201005260958_ 1-- Valid 7/30/11 10:57:43 7/30/11 16:39:551.0431.4 / 24.2 X119500657201005260958_ 1-- Valid 7/30/11 10:57:42 7/30/11 13:14:351.2136.3 / 27.1 faah23575_ ZINC00871887_ x1HHPxtl_ 01_ 0-- User Aborted7/30/11 09:38:527/30/11 16:39:553.2497.6 / 0.0
Bug#615489: xserver-xorg-video-nouveau: EDID checksum is invalid with Dell 3008WFP
missing attachment: dmesg |tail -n 100 edid_error.txt Regards, [51658.256027] [51658.364458] [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 166 [51658.364461] [drm:drm_edid_block_valid] *ERROR* Raw EDID: [51658.364468] 300 ff ff ff ff ff ff 00 10 ac 35 40 4c 32 38 30 ..5@L280 [51658.364470] 314 12 01 03 80 41 29 78 ea 8f 95 ad 4f 32 b2 25 .A)xO2.% [51658.364471] 30f 50 54 a5 4b 00 81 80 a9 40 d1 00 71 4f 81 00 .pt.k@..qo.. [51658.364473] 381 c0 b3 00 01 01 b0 68 00 a0 a0 40 2e 60 30 20 ...h...@.`0 [51658.364475] 336 00 81 90 21 00 00 1e 00 00 00 ff 00 52 57 39 6...!RW9 [51658.364476] 331 35 38 35 46 30 38 32 4c 0a 28 3c 80 a0 70 b0 1585F082L.(..p. [51658.364478] 323 40 30 20 3f ff ff ff ff ff ff ff ff ff ff ff #@0 ?... [51658.364479] 3ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [51658.364480] [51689.139276] [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 187 [51689.139279] [drm:drm_edid_block_valid] *ERROR* Raw EDID: [51689.139282] 300 ff ff ff ff ff ff 00 10 ac 35 40 4c 32 38 30 ..5@L280 [51689.139284] 314 12 01 03 80 41 29 78 ea 8f 95 ad 4f 32 b2 25 .A)xO2.% [51689.139285] 30f 50 54 a5 4b 00 81 80 a9 40 d1 00 71 4f 81 00 .pt.k@..qo.. [51689.139287] 381 c0 b3 00 01 01 bf ff ff ff ff ff ff ff ff ff [51689.139288] 3ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [51689.139290] 3ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [51689.139291] 3ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [51689.139293] 3ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [51689.139294] [51999.139103] [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 246 [51999.139107] [drm:drm_edid_block_valid] *ERROR* Raw EDID: [51999.139109] 300 ff ff ff ff ff ff 00 10 ac 35 40 4c 32 38 30 ..5@L280 [51999.139111] 314 12 01 03 80 41 29 78 ea 8f 95 af ff ff ff ff .A)x [51999.139112] 3ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [51999.139114] 3ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [51999.139115] 3ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [51999.139117] 3ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [51999.139118] 3ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [51999.139120] 3ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [51999.139121] [52092.140313] [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 146 [52092.140317] [drm:drm_edid_block_valid] *ERROR* Raw EDID: [52092.140319] 300 ff ff ff ff ff ff 00 10 ac 35 40 4c 32 38 30 ..5@L280 [52092.140321] 314 12 01 03 80 41 ff ff ff ff ff ff ff ff ff ff .A.. [52092.140323] 3ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [52092.140324] 3ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [52092.140325] 3ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [52092.140327] 3ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [52092.140328] 3ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [52092.140330] 3ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [52092.140331] [52154.141925] [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 246 [52154.141929] [drm:drm_edid_block_valid] *ERROR* Raw EDID: [52154.141931] 300 ff ff ff ff ff ff 00 10 ac 35 7f ff ff ff ff ..5. [52154.141933] 3ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [52154.141935] 3ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [52154.141936] 3ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [52154.141938] 3ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [52154.141939] 3ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [52154.141941] 3ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [52154.141942] 3ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [52154.141943] [52154.248856] [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 106 [52154.248859] [drm:drm_edid_block_valid] *ERROR* Raw EDID: [52154.248862] 300 ff ff ff ff ff ff 00 10 ac 35 40 4c 32 38 30 ..5@L280 [52154.248863] 314 12 01 03 80 41 29 78 ea 8f 95 ad 4f 32 b2 3f .A)xO2.? [52154.248865] 3ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [52154.248867] 3ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [52154.248868] 3ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [52154.248869] 3ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [52154.248871] 3ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Bug#495367: xserver-xorg-video-radeon: Radeon and RadeonHD drivers do not allow 2560x1600
Hi, Just to update the situation with the new sid drivers and todays git. Basically git regresses compared to actual sid drivers (more black video modes). [Tested drivers] - sid: xserver-xorg-video-radeon 1:6.9.0-1+lenny4 - git: downloaded on 5-Oct-2008 git clone git://anongit.freedesktop.org/git/xorg/driver/xf86-video-ati [Result notations] - F=flicker, means, the screen appears shortly, then turns black, reappears shortly... - B=black screen, screen does not appear at all (based on min. 1 min test). - Ok=works fine (based on min. 1 min test). [Results] Resolution Frequency: results 2560x1600 59.9: sid=B git=B 1920x1440 60.0: sid=W git=B (many monitor messages 'entering power save' but in fact never enters) 1600x1200 85.0: sid=W git=B 1280x1024 85.0: sid=W git=W 1280x768 60.0: sid=F git=F 1024x768 85.0: sid=W git=W 1024x768 60.0: sid=W git=W Note: All above video modes are listed by xrandr. Regards, Franck -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#495367: xserver-xorg-video-radeon: Radeon and RadeonHD drivers do not allow 2560x1600
Just to correct the notations. Hi, Just to update the situation with the new sid drivers and todays git. Basically git regresses compared to actual sid drivers (more black video modes). [Tested drivers] - sid: xserver-xorg-video-radeon 1:6.9.0-1+lenny4 - git: downloaded on 5-Oct-2008 git clone git://anongit.freedesktop.org/git/xorg/driver/xf86-video-ati [Result notations] - F=flicker, means, the screen appears shortly, then turns black, reappears shortly... - B=black screen, screen does not appear at all (based on min. 1 min test). - W=works fine (based on min. 1 min test). [Results] Resolution Frequency: results 2560x1600 59.9: sid=B git=B 1920x1440 60.0: sid=W git=B (many monitor messages 'entering power save' but in fact never enters) 1600x1200 85.0: sid=W git=B 1280x1024 85.0: sid=W git=W 1280x768 60.0: sid=F git=F 1024x768 85.0: sid=W git=W 1024x768 60.0: sid=W git=W Note: All above video modes are listed by xrandr. Regards, Franck -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#495367: xserver-xorg-video-radeon: Radeon and RadeonHD drivers do not allow 2560x1600
On Thu, Aug 21, 2008 at 01:07:56AM +0200, Marc wrote : I have tried right now (wednesday-thursday) both radeon and radeonhd git's, and I can confirm they work on my system, although I can only reach 1280x768 resolution on my box so I can not help you with the bug. I think your problem might be that you should put the prefix=usr in the autogen line. It worked for me as follows: # ./autogen.sh --prefix=/usr/ # make # sudo checkinstall I would be glad I have helped you, as this is my first time around here !! Regards, Marc /// Thanks for your input Marc. I tried with radeon. Unfortunately it was not that. Nevertherless I could learn something: 1920x1440: git=black screen; 6.9.0-1+lenny2=ok 1280x768: git=flicker; 6.9.0-1+lenny2=flicker flicker means, the screen appear shortly, then turns black, reappear shortly... So I learned that: - even if 6.9.0-1+lenny2 works in 1920x1440 works, git does not work - both does not work in 1280x768 (suprising knowing it should be easier to display) = looks like it is not a problem of dual-dvi vs single-dvi Note that I didn't use checkinstall but: # aptitude build-dep xserver-xorg-video-ati $ git clone git://anongit.freedesktop.org/git/xorg/driver/xf86-video-ati $ cd xf86-video-ati/ $ ./autogen.sh --prefix=/usr $ make # make install So to be complete I usually do: # aptitude build-dep xserver-xorg-video-ati (delete previous git if existing) $ git clone git://anongit.freedesktop.org/git/xorg/driver/xf86-video-ati $ cd xf86-video-ati/ $ ./autogen.sh $ make # make install prefix=/usr then restarting X with ctrl-alt-backspace Then to reinstall original radeon (after it failed) # aptitude reinstall xserver-xorg-video-ati # aptitude reinstall xserver-xorg-video-radeon Again thanks for having tried to help me, Franck -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#360478: linux-image-2.6.16-1-k7: mount encrypted ide crash
Hi Maximilian, So far I didn't experience any crash, even after several mount-unmount. = I believe problem is solved and this bug report can be closed. I tested with: dpkg -l cryptsetup dmsetup linux-image-2.6.18-3-k7 ii cryptsetup1.0.4+svn26-1 ii dmsetup 1.02.12-1 ii linux-image-2.6.18-3-k7 2.6.18-8 Regards Happy new year to you too, Franck On Tue, Jan 02, 2007 at 09:29:25AM +0100, maximilian attems wrote : tags 360478 moreinfo stop On Sun, 02 Apr 2006, franck wrote: Since 2.6.16 I experience some crashes when mounting an encrypted ide partition. Crashes does not always happen but let's say 50% time. If it shall crash it always happen just when mounting the partition. Effects are : X or console freeze. Under console, SysRq Sync + remount may allow to recover the console after some 'sleeping time' (however no 'DONE' appearing). Later '/sbin/reboot' sometimes hangs and SysRq reboot is the only way. can we have an update on that based on current testing and linux image 2.6.18! In case the console comes back one can save from dmesg: ... BUG: soft lockup detected on CPU#0! Pid: 4199, comm:mount EIP: 0060:[b0130097] CPU: 0 EIP is at find_get_pages+0x41/0x45 EFLAGS: 0246Not tainted (2.6.16-1-k7 #1) EAX: 8821 EBX: eb11fc80 ECX: eb11fc8c EDX: b17625e0 ESI: 0001 EDI: 0001 EBP: 0001 DS: 007b ES: 007b CR0: 8005003b CR2: af8d95e4 CR3: 3b954000 CR4: 06d0 [b01357a4] pagevec_lookup+0x1a/0x21 [b013613e] invalidate_mapping_pages+0x92/0xa7 [b0136160] invalidate_inode_pages+0xd/0x11 [b014c707] kill_bdev+0xb/0x22 [b014cdfb] set_blocksize+0x6f/0x7b [b014ce1d] sb_set_blocksize+0x16/0x3c [f08d1089] ext3_fill_super+0x3bd/0x1368 [ext3] [b01a3a36] snprintf+0x1a/0x1e [b014c495] get_sb_bdev+0xc5/0x10f [f08cf49f] ext3_get_sb+0x1a/0x1e [ext3] [f08d0ccc] ext3_fill_super+0x0/0x1368 [ext3] [b014bca2] do_kern_mount+0x88/0x12d [b015d428] do_mount+0x629/0x684 [b0152be8] link_path_walk+0xb0/0xbb [b013a193] __handle_mm_fault+0x348/0x650 [b0152fb3] do_path_lookup+0x17f/0x19a [b0133b8f] get_page_from_freelist+0x7e/0x294 [b0133df3] __alloc_pages+0x4e/0x261 [b01341c2] __get_free_pages+0x2f/0x34 [b015c27e] copy_mount_options+0x28/0x10e [b015d4f5] sys_mount+0x72/0xad [b01028ff] sysenter_past_esp+0x54/0x75 SysRq : Emergency Sync SysRq : Emergency Remount R/O ... I never experienced such problem with 2.6.15. I booted with 2.6.12 and did not see the same problem - seems to come from 2.6.16. I tried to reproduce it on an encrypted USB stick (to avoid any risk of hdd corruption resulting from trials), but I couldn't - seems linked to hdd. I can reproduce it on several different hdd. FYI encryption comes from: dpkg -l cryptsetup dmsetup ii cryptsetup1.0.2+1.0.3-rc3-1 configures encrypted block devices ii dmsetup 1.02.03-1 The Linux Kernel Device Mapper userspace library Kind regards, Franck R. happy new year -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
