Please reject linux-2.6 2.6.32-7
linux-2.6 version 2.6.32-7 includes an incomplete bug fix that will result in failure to boot 32-bit userland on a 64-bit kernel. 2.6.32-8 will have the complete bug fix. Ben. -- Ben Hutchings friends: People who know you well, but like you anyway. signature.asc Description: This is a digitally signed message part
Bug#567204: linux-image-686-bigmem: serious filesystem corruption with bigmem kernels
On Wed, Feb 03, 2010 at 11:22:06AM +0100, Cesare Leonardi wrote: M. Dietrich wrote: my system had serious filesystem corruption with several -bigmem kernel in the past (from 2.6.28 to 2.6.32). Does this mean that with normal 686 or 486 kernel the corruption doesn't happen? yes. However many years ago i've experienced frequent filesystem corruption but i couldn't figure out why. Eventually i discovered was some hdparm settings... Was a lot hard to find, so i hope this could help you. ;-) there are no special settings installed using hdparm: /dev/sda: multcount = 0 (off) IO_support= 1 (32-bit) readonly = 0 (off) readahead = 256 (on) geometry = 30401/255/63, sectors = 488397168, start = 0 for sure i can't guarantee that this isn't related to some hardware fault like broken ram or the like but i checked ram with memtest86+. If i were you, i would also install smartmontools and try something like: smartctl -a /dev/yourdisk I'd put particular attention in the Vendor Specific SMART Attributes with Thresholds table to find something strange. it's already installed, this is the output: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 085 069 034Pre-fail Always - 98867399 3 Spin_Up_Time0x0003 100 100 000Pre-fail Always - 0 4 Start_Stop_Count0x0032 001 001 020Old_age Always FAILING_NOW 248712 5 Reallocated_Sector_Ct 0x0033 100 100 036Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 075 060 030Pre-fail Always - 40211526 9 Power_On_Hours 0x0032 095 095 000Old_age Always - 269350284038985 10 Spin_Retry_Count0x0013 100 100 034Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020Old_age Always - 448 184 End-to-End_Error0x0032 100 253 000Old_age Always - 0 187 Reported_Uncorrect 0x003a 100 100 000Old_age Always - 0 189 High_Fly_Writes 0x0022 100 100 045Old_age Always - 0 190 Airflow_Temperature_Cel 0x0032 071 052 000Old_age Always - 29 (Lifetime Min/Max 10/48) 191 G-Sense_Error_Rate 0x0032 100 100 000Old_age Always - 19 192 Power-Off_Retract_Count 0x0022 062 062 000Old_age Always - 77434 193 Load_Cycle_Count0x001a 001 001 000Old_age Always - 320283 194 Temperature_Celsius 0x0012 029 048 000Old_age Always - 29 (0 10 0 0) 195 Hardware_ECC_Recovered 0x0010 070 061 000Old_age Offline - 98881899 196 Reallocated_Event_Count 0x003e 096 096 000Old_age Always - 3645 (28548, 0) 197 Current_Pending_Sector 0x 100 100 000Old_age Offline - 0 198 Offline_Uncorrectable 0x0032 100 100 000Old_age Always - 0 199 UDMA_CRC_Error_Count0x 200 200 000Old_age Offline - 0 200 Multi_Zone_Error_Rate 0x 100 253 000Old_age Offline - 0 202 Data_Address_Mark_Errs 0x 100 253 000Old_age Offline - 0 i wonder how to interpret that. Start_Stop_Count has FAILING_NOW, maybe because hdaps is stopping the device often? why is that bad? hm. but everything else looks fine, right? And try to hear if the disk make suspicious noise. it doesnt - silent as a sleeping baby. If you have a minimum suspect for the ram, try to temporarly remove some bank, if you have more than one, or replace completely if you can. In the past i've seen at least two cases where memtest run ok for about a day but the system had sporadic system freeze and BSOD (Windows PCs). When i've replaced the ram the problems disapperead. removing would reduce mem size and the need for bigmem kernel obsolete. replacing isn't possible right now. point is: i never had strange behaviour related to mem like kernel-freezes or program core dumps and i use the system quite alot with big (cross-)compiles and everything that uses mem alot... thing is that i discovered fs corruption by accident - git complained about a defect repo. then i forced a fsck run at boot and that failed. maybe all bigmem users should force a fsck and see if they already suffer from a similar corruption. if not this bug should be closed because it seems to be hw related. but i don't know how where to search, especially because this computer is a tool to do my work on. best regards, michael -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
linux-2.6_2.6.32-7_amd64.changes ACCEPTED
Accepted: firmware-linux-free_2.6.32-7_all.deb to main/l/linux-2.6/firmware-linux-free_2.6.32-7_all.deb linux-2.6_2.6.32-7.diff.gz to main/l/linux-2.6/linux-2.6_2.6.32-7.diff.gz linux-2.6_2.6.32-7.dsc to main/l/linux-2.6/linux-2.6_2.6.32-7.dsc linux-doc-2.6.32_2.6.32-7_all.deb to main/l/linux-2.6/linux-doc-2.6.32_2.6.32-7_all.deb linux-headers-2.6.32-2-all-amd64_2.6.32-7_amd64.deb to main/l/linux-2.6/linux-headers-2.6.32-2-all-amd64_2.6.32-7_amd64.deb linux-headers-2.6.32-2-all_2.6.32-7_amd64.deb to main/l/linux-2.6/linux-headers-2.6.32-2-all_2.6.32-7_amd64.deb linux-headers-2.6.32-2-amd64_2.6.32-7_amd64.deb to main/l/linux-2.6/linux-headers-2.6.32-2-amd64_2.6.32-7_amd64.deb linux-headers-2.6.32-2-common-vserver_2.6.32-7_amd64.deb to main/l/linux-2.6/linux-headers-2.6.32-2-common-vserver_2.6.32-7_amd64.deb linux-headers-2.6.32-2-common_2.6.32-7_amd64.deb to main/l/linux-2.6/linux-headers-2.6.32-2-common_2.6.32-7_amd64.deb linux-headers-2.6.32-2-vserver-amd64_2.6.32-7_amd64.deb to main/l/linux-2.6/linux-headers-2.6.32-2-vserver-amd64_2.6.32-7_amd64.deb linux-image-2.6.32-2-amd64_2.6.32-7_amd64.deb to main/l/linux-2.6/linux-image-2.6.32-2-amd64_2.6.32-7_amd64.deb linux-image-2.6.32-2-vserver-amd64_2.6.32-7_amd64.deb to main/l/linux-2.6/linux-image-2.6.32-2-vserver-amd64_2.6.32-7_amd64.deb linux-libc-dev_2.6.32-7_amd64.deb to main/l/linux-2.6/linux-libc-dev_2.6.32-7_amd64.deb linux-manual-2.6.32_2.6.32-7_all.deb to main/l/linux-2.6/linux-manual-2.6.32_2.6.32-7_all.deb linux-patch-debian-2.6.32_2.6.32-7_all.deb to main/l/linux-2.6/linux-patch-debian-2.6.32_2.6.32-7_all.deb linux-source-2.6.32_2.6.32-7_all.deb to main/l/linux-2.6/linux-source-2.6.32_2.6.32-7_all.deb linux-support-2.6.32-2_2.6.32-7_all.deb to main/l/linux-2.6/linux-support-2.6.32-2_2.6.32-7_all.deb Override entries for your package: firmware-linux-free_2.6.32-7_all.deb - optional kernel linux-2.6_2.6.32-7.dsc - source devel linux-doc-2.6.32_2.6.32-7_all.deb - optional doc linux-headers-2.6.32-2-all-amd64_2.6.32-7_amd64.deb - optional kernel linux-headers-2.6.32-2-all_2.6.32-7_amd64.deb - optional kernel linux-headers-2.6.32-2-amd64_2.6.32-7_amd64.deb - optional kernel linux-headers-2.6.32-2-common-vserver_2.6.32-7_amd64.deb - optional kernel linux-headers-2.6.32-2-common_2.6.32-7_amd64.deb - optional kernel linux-headers-2.6.32-2-vserver-amd64_2.6.32-7_amd64.deb - optional kernel linux-image-2.6.32-2-amd64_2.6.32-7_amd64.deb - optional kernel linux-image-2.6.32-2-vserver-amd64_2.6.32-7_amd64.deb - optional kernel linux-libc-dev_2.6.32-7_amd64.deb - optional devel linux-manual-2.6.32_2.6.32-7_all.deb - optional doc linux-patch-debian-2.6.32_2.6.32-7_all.deb - optional kernel linux-source-2.6.32_2.6.32-7_all.deb - optional kernel linux-support-2.6.32-2_2.6.32-7_all.deb - optional devel Announcing to debian-devel-chan...@lists.debian.org Closing bugs: 568025 568030 Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#568025: marked as done (FTBFS on sparc)
Your message dated Thu, 04 Feb 2010 09:53:32 + with message-id e1ncyoy-vd...@ries.debian.org and subject line Bug#568025: fixed in linux-2.6 2.6.32-7 has caused the Debian Bug report #568025, regarding FTBFS on sparc 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 ow...@bugs.debian.org immediately.) -- 568025: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=568025 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.32-6 Severity: important Justification: fails to build from source Since we enabled dynamic ftrace, the recordmcount.pl script is used in the build process. This script wrongly detects the target architecture during Debian builds for sparc, and reports it as not supported: https://buildd.debian.org/fetch.cgi?pkg=linux-2.6;ver=2.6.32-6;arch=sparc;stamp=1265049730 Ben. -- System Information: Debian Release: squeeze/sid APT prefers proposed-updates APT policy: (500, 'proposed-updates'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: i386 (x86_64) Kernel: Linux 2.6.32-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash ---End Message--- ---BeginMessage--- Source: linux-2.6 Source-Version: 2.6.32-7 We believe that the bug you reported is fixed in the latest version of linux-2.6, which is due to be installed in the Debian FTP archive: firmware-linux-free_2.6.32-7_all.deb to main/l/linux-2.6/firmware-linux-free_2.6.32-7_all.deb linux-2.6_2.6.32-7.diff.gz to main/l/linux-2.6/linux-2.6_2.6.32-7.diff.gz linux-2.6_2.6.32-7.dsc to main/l/linux-2.6/linux-2.6_2.6.32-7.dsc linux-doc-2.6.32_2.6.32-7_all.deb to main/l/linux-2.6/linux-doc-2.6.32_2.6.32-7_all.deb linux-headers-2.6.32-2-all-amd64_2.6.32-7_amd64.deb to main/l/linux-2.6/linux-headers-2.6.32-2-all-amd64_2.6.32-7_amd64.deb linux-headers-2.6.32-2-all_2.6.32-7_amd64.deb to main/l/linux-2.6/linux-headers-2.6.32-2-all_2.6.32-7_amd64.deb linux-headers-2.6.32-2-amd64_2.6.32-7_amd64.deb to main/l/linux-2.6/linux-headers-2.6.32-2-amd64_2.6.32-7_amd64.deb linux-headers-2.6.32-2-common-vserver_2.6.32-7_amd64.deb to main/l/linux-2.6/linux-headers-2.6.32-2-common-vserver_2.6.32-7_amd64.deb linux-headers-2.6.32-2-common_2.6.32-7_amd64.deb to main/l/linux-2.6/linux-headers-2.6.32-2-common_2.6.32-7_amd64.deb linux-headers-2.6.32-2-vserver-amd64_2.6.32-7_amd64.deb to main/l/linux-2.6/linux-headers-2.6.32-2-vserver-amd64_2.6.32-7_amd64.deb linux-image-2.6.32-2-amd64_2.6.32-7_amd64.deb to main/l/linux-2.6/linux-image-2.6.32-2-amd64_2.6.32-7_amd64.deb linux-image-2.6.32-2-vserver-amd64_2.6.32-7_amd64.deb to main/l/linux-2.6/linux-image-2.6.32-2-vserver-amd64_2.6.32-7_amd64.deb linux-libc-dev_2.6.32-7_amd64.deb to main/l/linux-2.6/linux-libc-dev_2.6.32-7_amd64.deb linux-manual-2.6.32_2.6.32-7_all.deb to main/l/linux-2.6/linux-manual-2.6.32_2.6.32-7_all.deb linux-patch-debian-2.6.32_2.6.32-7_all.deb to main/l/linux-2.6/linux-patch-debian-2.6.32_2.6.32-7_all.deb linux-source-2.6.32_2.6.32-7_all.deb to main/l/linux-2.6/linux-source-2.6.32_2.6.32-7_all.deb linux-support-2.6.32-2_2.6.32-7_all.deb to main/l/linux-2.6/linux-support-2.6.32-2_2.6.32-7_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 568...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. dann frazier da...@debian.org (supplier of updated linux-2.6 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Wed, 03 Feb 2010 18:35:21 -0700 Source: linux-2.6 Binary: linux-source-2.6.32 linux-doc-2.6.32 linux-manual-2.6.32 linux-patch-debian-2.6.32 firmware-linux-free linux-support-2.6.32-2 linux-base linux-libc-dev linux-headers-2.6.32-2-all linux-headers-2.6.32-2-all-alpha linux-headers-2.6.32-2-common linux-image-2.6.32-2-alpha-generic linux-headers-2.6.32-2-alpha-generic linux-image-2.6.32-2-alpha-smp linux-headers-2.6.32-2-alpha-smp linux-image-2.6.32-2-alpha-legacy linux-headers-2.6.32-2-alpha-legacy linux-headers-2.6.32-2-all-amd64 linux-image-2.6.32-2-amd64 linux-headers-2.6.32-2-amd64 linux-headers-2.6.32-2-common-vserver linux-image-2.6.32-2-vserver-amd64 linux-headers-2.6.32-2-vserver-amd64
Bug#568030: marked as done (FTBFS on armel (and maybe others))
Your message dated Thu, 04 Feb 2010 09:53:32 + with message-id e1ncyoy-vk...@ries.debian.org and subject line Bug#568030: fixed in linux-2.6 2.6.32-7 has caused the Debian Bug report #568030, regarding FTBFS on armel (and maybe others) 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 ow...@bugs.debian.org immediately.) -- 568030: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=568030 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.32-6 Severity: important Justification: fails to build from source From https://buildd.debian.org/fetch.cgi?pkg=linux-2.6;ver=2.6.32-6;arch=armel;stamp=1265064985: CC kernel/time/clocksource.o /build/buildd-linux-2.6_2.6.32-6-armel-0P0u54/linux-2.6-2.6.32/debian/build/source_armel_none/kernel/time/clocksource.c: In function 'clocksource_register': /build/buildd-linux-2.6_2.6.32-6-armel-0P0u54/linux-2.6-2.6.32/debian/build/source_armel_none/kernel/time/clocksource.c:556: error: implicit declaration of function 'clocksource_max_deferment' Upstream stable release 2.6.32.7 added this function, conditional on CONFIG_GENERIC_TIME, but added an unconditional use. This has been fixed in mainline in commit a362c638bdf052bf424bce7645d39b101090f6ba (clocksource/events: Fix fallout of generic code changes). Ben. -- System Information: Debian Release: squeeze/sid APT prefers proposed-updates APT policy: (500, 'proposed-updates'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: i386 (x86_64) Kernel: Linux 2.6.32-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash ---End Message--- ---BeginMessage--- Source: linux-2.6 Source-Version: 2.6.32-7 We believe that the bug you reported is fixed in the latest version of linux-2.6, which is due to be installed in the Debian FTP archive: firmware-linux-free_2.6.32-7_all.deb to main/l/linux-2.6/firmware-linux-free_2.6.32-7_all.deb linux-2.6_2.6.32-7.diff.gz to main/l/linux-2.6/linux-2.6_2.6.32-7.diff.gz linux-2.6_2.6.32-7.dsc to main/l/linux-2.6/linux-2.6_2.6.32-7.dsc linux-doc-2.6.32_2.6.32-7_all.deb to main/l/linux-2.6/linux-doc-2.6.32_2.6.32-7_all.deb linux-headers-2.6.32-2-all-amd64_2.6.32-7_amd64.deb to main/l/linux-2.6/linux-headers-2.6.32-2-all-amd64_2.6.32-7_amd64.deb linux-headers-2.6.32-2-all_2.6.32-7_amd64.deb to main/l/linux-2.6/linux-headers-2.6.32-2-all_2.6.32-7_amd64.deb linux-headers-2.6.32-2-amd64_2.6.32-7_amd64.deb to main/l/linux-2.6/linux-headers-2.6.32-2-amd64_2.6.32-7_amd64.deb linux-headers-2.6.32-2-common-vserver_2.6.32-7_amd64.deb to main/l/linux-2.6/linux-headers-2.6.32-2-common-vserver_2.6.32-7_amd64.deb linux-headers-2.6.32-2-common_2.6.32-7_amd64.deb to main/l/linux-2.6/linux-headers-2.6.32-2-common_2.6.32-7_amd64.deb linux-headers-2.6.32-2-vserver-amd64_2.6.32-7_amd64.deb to main/l/linux-2.6/linux-headers-2.6.32-2-vserver-amd64_2.6.32-7_amd64.deb linux-image-2.6.32-2-amd64_2.6.32-7_amd64.deb to main/l/linux-2.6/linux-image-2.6.32-2-amd64_2.6.32-7_amd64.deb linux-image-2.6.32-2-vserver-amd64_2.6.32-7_amd64.deb to main/l/linux-2.6/linux-image-2.6.32-2-vserver-amd64_2.6.32-7_amd64.deb linux-libc-dev_2.6.32-7_amd64.deb to main/l/linux-2.6/linux-libc-dev_2.6.32-7_amd64.deb linux-manual-2.6.32_2.6.32-7_all.deb to main/l/linux-2.6/linux-manual-2.6.32_2.6.32-7_all.deb linux-patch-debian-2.6.32_2.6.32-7_all.deb to main/l/linux-2.6/linux-patch-debian-2.6.32_2.6.32-7_all.deb linux-source-2.6.32_2.6.32-7_all.deb to main/l/linux-2.6/linux-source-2.6.32_2.6.32-7_all.deb linux-support-2.6.32-2_2.6.32-7_all.deb to main/l/linux-2.6/linux-support-2.6.32-2_2.6.32-7_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 568...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. dann frazier da...@debian.org (supplier of updated linux-2.6 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Wed, 03 Feb 2010 18:35:21 -0700 Source: linux-2.6 Binary: linux-source-2.6.32 linux-doc-2.6.32 linux-manual-2.6.32 linux-patch-debian-2.6.32 firmware-linux-free linux-support-2.6.32-2 linux-base linux-libc-dev linux-headers-2.6.32-2-all
Bug#517995: marked as done ([linux-image-2.6.28-1-686] Intel sound dont work)
Your message dated Thu, 4 Feb 2010 11:07:04 +0100 with message-id 20100204100704.ga9...@stro.at and subject line Re: Bug#517995: [linux-image-2.6.28-1-686] Intel sound dont work has caused the Debian Bug report #517995, regarding [linux-image-2.6.28-1-686] Intel sound dont work 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 ow...@bugs.debian.org immediately.) -- 517995: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=517995 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.28-1-686 Version: 2.6.28-1 Severity: normal --- Please enter the report below this line. --- Hi, I have this sound card: 0:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03) Subsystem: Dell Device 0233 Flags: bus master, fast devsel, latency 0, IRQ 21 Memory at f6adc000 (64-bit, non-prefetchable) [size=16K] Capabilities: access denied Kernel driver in use: HDA Intel Kernel modules: snd-hda-intel Using the kernel 2.6.26 the sound work, but using the 2.6.28 the sound dont work, but no errors are showed. The modules are the same, look: [rona...@mobilix ~]$ uname -a Linux mobilix 2.6.26-1-686 #1 SMP Sat Jan 10 18:29:31 UTC 2009 i686 GNU/Linux [rona...@mobilix ~]$ lsmod | grep snd snd_hda_intel 324248 1 snd_pcm_oss 32800 0 snd_mixer_oss 12320 1 snd_pcm_oss snd_pcm 62596 2 snd_hda_intel,snd_pcm_oss snd_seq_dummy 2660 0 snd_seq_oss 24992 0 snd_seq_midi 5728 0 snd_rawmidi 18496 1 snd_seq_midi snd_seq_midi_event 6432 2 snd_seq_oss,snd_seq_midi snd_seq 41456 6 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event snd_timer 17800 2 snd_pcm,snd_seq snd_seq_device 6380 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq snd 45604 11 snd_hda_intel,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_device soundcore 6368 1 snd snd_page_alloc 7816 2 snd_hda_intel,snd_pcm Now with the 2.6.28 [rona...@mobilix ~]$ uname -a Linux mobilix 2.6.28-1-686 #1 SMP Mon Feb 23 03:13:24 UTC 2009 i686 GNU/Linux [rona...@mobilix ~]$ lsmod | grep snd snd_hda_intel 362712 1 snd_pcm_oss 32128 0 snd_mixer_oss 12256 1 snd_pcm_oss snd_pcm 63332 2 snd_hda_intel,snd_pcm_oss snd_seq_dummy 2628 0 snd_seq_oss 24636 0 snd_seq_midi 5760 0 snd_rawmidi 18784 1 snd_seq_midi snd_seq_midi_event 6368 2 snd_seq_oss,snd_seq_midi snd_seq 41576 6 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event snd_timer 17992 2 snd_pcm,snd_seq snd_seq_device 6412 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq snd 45912 11 snd_hda_intel,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_device soundcore 6440 1 snd snd_page_alloc 8200 2 snd_hda_intel,snd_pcm Thanks Ronaldo --- System information. --- Architecture: i386 Kernel: Linux 2.6.28-1-686 Debian Release: 5.0 500 unstable200.97.11.11 500 testing 200.97.11.11 500 stable 200.97.11.11 --- Package information. --- Depends (Version) | Installed =-+-= module-init-tools | 3.4-1 initramfs-tools(= 0.55) | 0.92o OR yaird(= 0.0.13) | OR linux-initramfs-tool | -8---8---8---8---8---8---8---8---8-- Please attach the file: /tmp/reportbug-ng-linux-image-2.6.28-1-686-ABZuGW.txt to the mail. I'd do it myself if the output wasn't too long to handle. Thank you! -8---8---8---8---8---8---8---8---8-- -- This door is baroquen, please wiggle Handel. (If I wiggle Handel, will it wiggle Bach?) -- Found on a door in the MSU music building -- Prof. Ronaldo Reis Júnior | .''`. UNIMONTES/DBG/Lab. Ecologia Comportamental e Computacional | : :' : Campus Universitário Prof. Darcy Ribeiro, Vila Mauricéia | `. `'` CP: 126, CEP: 39401-089, Montes Claros - MG - Brasil | `- Fone: (38) 3229-8192 | ronaldo.r...@unimontes.br | chrys...@gmail.com | http://www.ppgcb.unimontes.br/lecc | ICQ#: 5692561 | LinuxUser#: 205366 -- Favor NÃO ENVIAR arquivos do Word ou Powerpoint Prefira enviar em PDF, Texto, OpenOffice (ODF), HTML, or RTF. --- Output from package bug script --- ** Version: Linux version 2.6.28-1-686 (Debian 2.6.28-1)
Bug#517804: marked as done (base: CPU scaling for the 2nd core stops working after suspend to RAM)
Your message dated Thu, 4 Feb 2010 11:08:33 +0100 with message-id 20100204100833.gb9...@stro.at and subject line Re: Bug#517804: base: CPU scaling for the 2nd core stops working after suspend to RAM has caused the Debian Bug report #517804, regarding base: CPU scaling for the 2nd core stops working after suspend to RAM 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 ow...@bugs.debian.org immediately.) -- 517804: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=517804 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: base Severity: normal I don't exactly know wether this bug related to base system or to linux kernel or cpufreq subsystem I'm using cpufreq for dynamic CPU scaling on my notebook Dell D630. After resuming from suspend2ram cpu scaling is lost for core #1. Below is the cpufreq-info output before and after suspend2ram: --- v...@dell:~$ cpufreq-info cpufrequtils 004: cpufreq-info (C) Dominik Brodowski 2004-2006 Report errors and bugs to cpuf...@lists.linux.org.uk, please. analyzing CPU 0: driver: acpi-cpufreq CPUs which need to switch frequency at the same time: 0 1 hardware limits: 800 MHz - 2.20 GHz available frequency steps: 2.20 GHz, 2.20 GHz, 1.60 GHz, 1.20 GHz, 800 MHz available cpufreq governors: userspace, powersave, ondemand, conservative, performance current policy: frequency should be within 800 MHz and 2.20 GHz. The governor ondemand may decide which speed to use within this range. current CPU frequency is 800 MHz. analyzing CPU 1: driver: acpi-cpufreq CPUs which need to switch frequency at the same time: 0 1 hardware limits: 800 MHz - 2.20 GHz available frequency steps: 2.20 GHz, 2.20 GHz, 1.60 GHz, 1.20 GHz, 800 MHz available cpufreq governors: userspace, powersave, ondemand, conservative, performance current policy: frequency should be within 800 MHz and 2.20 GHz. The governor ondemand may decide which speed to use within this range. current CPU frequency is 800 MHz. - v...@dell:~$ cpufreq-info cpufrequtils 004: cpufreq-info (C) Dominik Brodowski 2004-2006 Report errors and bugs to cpuf...@lists.linux.org.uk, please. analyzing CPU 0: driver: acpi-cpufreq CPUs which need to switch frequency at the same time: 0 hardware limits: 800 MHz - 2.20 GHz available frequency steps: 2.20 GHz, 2.20 GHz, 1.60 GHz, 1.20 GHz, 800 MHz available cpufreq governors: userspace, powersave, ondemand, conservative, performance current policy: frequency should be within 800 MHz and 2.20 GHz. The governor ondemand may decide which speed to use within this range. current CPU frequency is 800 MHz. analyzing CPU 1: no or unknown cpufreq driver is active on this CPU manual reloading acpi_cpufreq kernel module helps to turn CPU 1 scaling on. -- System Information: Debian Release: 5.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/2 CPU cores) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash ---End Message--- ---BeginMessage--- On Tue, 08 Dec 2009, Moritz Muehlenhoff wrote: Hi, The next release of Debian (6.0, code name Squeeze) will be based on 2.6.32. Please test the current 2.6.32 from unstable and tell us whether the problem persists. If so, we should report it upstream to the kernel.org developers. The 2.6.32 kernel is available from packages.debian.org and can be installed in both Debian stable, testing and unstable installations. Thanks, Moritz closing as no activity since inital report. most probably fixed by newer 2.6.32 in squeeze, can be reopened if reproducible with it. thanks for the report. ---End Message---
Processed: Re: Bug#523964: linux-image-2.6.28-1-486: memory corruption on resuming from STR/ACPI State 3
Processing commands for cont...@bugs.debian.org: tags 523964 moreinfo Bug #523964 [linux-2.6] linux-image-2.6.28-1-486: memory corruption on resuming from STR/ACPI State 3 Added tag(s) moreinfo. stop Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#567747: After upgrade, all system lock up when X start
Package: linux-source-2.6.32 Version: 2.6.32-6 Severity: normal For me Linux does not find TMDS panel connected to a mac mini. Applying http://lists.freedesktop.org/archives/intel-gfx/2009-December/004979.html fixes the problem for me on kernel.org 2.6.32 but the patch still applies on Debian 2.6.32-1-686 (2.6.32.4). The kernel fails to detect some hardware when the i2c bus is in an unexpected state. The UMS code is less prone to this issue so disabling KMS also resolved the issue for me. -- System Information: Debian Release: 5.0.4 APT prefers stable APT policy: (990, 'stable'), (500, 'testing'), (300, 'unstable'), (295, 'experimental'), (290, 'stable-i386'), (280, 'testing-i386'), (270, 'unstable-i386'), (150, 'experimental-i386') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-trunk-amd64 (SMP w/1 CPU core) 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 linux-source-2.6.32 depends on: ii binutils2.18.1~cvs20080103-7 The GNU assembler, linker and bina ii bzip2 1.0.5-1 high-quality block-sorting file co Versions of packages linux-source-2.6.32 recommends: ii gcc 4:4.3.2-2 The GNU C compiler ii libc6-dev [libc-dev] 2.10.2-2 GNU C Library: Development Librari ii make 3.81-5 The GNU version of the make util Versions of packages linux-source-2.6.32 suggests: ii kernel-package11.015 A utility for building Linux kerne ii libncurses5-dev [ncurses- 5.7+20081213-1 developer's libraries and docs for pn libqt3-mt-dev none (no description available) -- debconf-show failed -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: linux-image-2.6.26-2-686: Fails to load Atheros wifi
Processing commands for cont...@bugs.debian.org: tags 524132 moreinfo Bug #524132 [linux-image-2.6.26-2-686] linux-image-2.6.26-2-686: Fails to load Atheros wifi Added tag(s) moreinfo. stop Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#523964: linux-image-2.6.28-1-486: memory corruption on resuming from STR/ACPI State 3
tags 523964 moreinfo stop On Fri, 29 Jan 2010, Kushal Koolwal wrote: Hi Moritz, Sorry for not seeing your message earlier. Actually I have not been checking this email address any more but just happen to log in. Does this error still occur with the 2.6.30 kernel from unstable? I had to disable the following option in 2.6.28-1-486 in order to get rid of the error: # CONFIG_X86_CHECK_BIOS_CORRUPTION is not set egrep CONFIG_X86_CHECK_BIOS_CORRUPTION /boot/config-2.6.* /boot/config-2.6.28-1-amd64:# CONFIG_X86_CHECK_BIOS_CORRUPTION is not set /boot/config-2.6.30-2-amd64:# CONFIG_X86_CHECK_BIOS_CORRUPTION is not set /boot/config-2.6.31-1-amd64:# CONFIG_X86_CHECK_BIOS_CORRUPTION is not set /boot/config-2.6.32-1-amd64:# CONFIG_X86_CHECK_BIOS_CORRUPTION is not set seems to have been never set. Let me know if you need more information. I have bookmarked the BUG report page so I will know if there is any new reply from you. yes please boot 2.6.32 linux image from squeeze / unstable (preferably latest version in unstable) and tell us if you can still repdouce mem corruption with it. squeeze will be released with 2.6.32 so it's a worthwile exercise to see if acpi improved since 2.6.28 for you. thanks. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#524132: linux-image-2.6.26-2-686: Fails to load Atheros wifi
tags 524132 moreinfo stop On Tue, 14 Apr 2009, Bryan Leaman wrote: Kernel 2.6.26-2-686 does not recognize the Atheros AR2425 wifi card in my EeePC 904HA. dmesg shows no indication of any wifi capabilities. have you tried newer linux images from backports or testing? does this bug still occur? sorry for the late reply but we have a huge bug backlog. thanks for feedback. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#567747: (fwd) drm/i915: Fix DDC on some systems by clearing BIOS GMBUS setup.
we have a report that this fix is need for mac mini
http://bugs.debian.org/567747
could you please apply belows to 2.6.32
- Forwarded message from Linux Kernel Mailing List
linux-ker...@vger.kernel.org -
Date: Fri, 11 Dec 2009 06:59:57 GMT
From: Linux Kernel Mailing List linux-ker...@vger.kernel.org
To: git-commits-h...@vger.kernel.org
Subject: drm/i915: Fix DDC on some systems by clearing BIOS GMBUS setup.
Gitweb: http://git.kernel.org/linus/f0217c42c9ab3d772e543f635ce628b9478f70b6
Commit: f0217c42c9ab3d772e543f635ce628b9478f70b6
Parent: d09c23de9f967a7b7dcee0ffc57222ddbd821aba
Author: Eric Anholt e...@anholt.net
AuthorDate: Tue Dec 1 11:56:30 2009 -0800
Committer: Eric Anholt e...@anholt.net
CommitDate: Tue Dec 1 11:56:30 2009 -0800
drm/i915: Fix DDC on some systems by clearing BIOS GMBUS setup.
This is a sync of a fix I made in the old UMS code. If the BIOS uses
the GMBUS and doesn't clear that setup, then our bit-banging I2C can
fail, leading to monitors not being detected.
Signed-off-by: Eric Anholt e...@anholt.net
---
drivers/gpu/drm/i915/i915_reg.h | 14 ++
drivers/gpu/drm/i915/i915_suspend.c |5 -
drivers/gpu/drm/i915/intel_drv.h|2 ++
drivers/gpu/drm/i915/intel_i2c.c| 19 +++
4 files changed, 39 insertions(+), 1 deletions(-)
diff --git a/drivers/gpu/drm/i915/i915_reg.h b/drivers/gpu/drm/i915/i915_reg.h
index 6b59602..c4a2735 100644
--- a/drivers/gpu/drm/i915/i915_reg.h
+++ b/drivers/gpu/drm/i915/i915_reg.h
@@ -414,6 +414,13 @@
# define GPIO_DATA_VAL_IN (1 12)
# define GPIO_DATA_PULLUP_DISABLE (1 13)
+#define GMBUS0 0x5100
+#define GMBUS1 0x5104
+#define GMBUS2 0x5108
+#define GMBUS3 0x510c
+#define GMBUS4 0x5110
+#define GMBUS5 0x5120
+
/*
* Clock control power management
*/
@@ -2166,6 +2173,13 @@
#define PCH_GPIOE 0xc5020
#define PCH_GPIOF 0xc5024
+#define PCH_GMBUS0 0xc5100
+#define PCH_GMBUS1 0xc5104
+#define PCH_GMBUS2 0xc5108
+#define PCH_GMBUS3 0xc510c
+#define PCH_GMBUS4 0xc5110
+#define PCH_GMBUS5 0xc5120
+
#define PCH_DPLL_A 0xc6014
#define PCH_DPLL_B 0xc6018
diff --git a/drivers/gpu/drm/i915/i915_suspend.c
b/drivers/gpu/drm/i915/i915_suspend.c
index cd10d9b..c5a6df9 100644
--- a/drivers/gpu/drm/i915/i915_suspend.c
+++ b/drivers/gpu/drm/i915/i915_suspend.c
@@ -27,7 +27,7 @@
#include drmP.h
#include drm.h
#include i915_drm.h
-#include i915_drv.h
+#include intel_drv.h
static bool i915_pipe_enabled(struct drm_device *dev, enum pipe pipe)
{
@@ -816,6 +816,9 @@ int i915_restore_state(struct drm_device *dev)
for (i = 0; i 3; i++)
I915_WRITE(SWF30 + (i 2), dev_priv-saveSWF2[i]);
+ /* I2C state */
+ intel_i2c_reset_gmbus(dev);
+
return 0;
}
diff --git a/drivers/gpu/drm/i915/intel_drv.h b/drivers/gpu/drm/i915/intel_drv.h
index 8a22f25..9ffa31e 100644
--- a/drivers/gpu/drm/i915/intel_drv.h
+++ b/drivers/gpu/drm/i915/intel_drv.h
@@ -162,6 +162,8 @@ void intel_i2c_destroy(struct i2c_adapter *adapter);
int intel_ddc_get_modes(struct intel_output *intel_output);
extern bool intel_ddc_probe(struct intel_output *intel_output);
void intel_i2c_quirk_set(struct drm_device *dev, bool enable);
+void intel_i2c_reset_gmbus(struct drm_device *dev);
+
extern void intel_crt_init(struct drm_device *dev);
extern void intel_hdmi_init(struct drm_device *dev, int sdvox_reg);
extern bool intel_sdvo_init(struct drm_device *dev, int output_device);
diff --git a/drivers/gpu/drm/i915/intel_i2c.c b/drivers/gpu/drm/i915/intel_i2c.c
index c7eab72..b94acc4 100644
--- a/drivers/gpu/drm/i915/intel_i2c.c
+++ b/drivers/gpu/drm/i915/intel_i2c.c
@@ -118,6 +118,23 @@ static void set_data(void *data, int state_high)
udelay(I2C_RISEFALL_TIME); /* wait for the line to change state */
}
+/* Clears the GMBUS setup. Our driver doesn't make use of the GMBUS I2C
+ * engine, but if the BIOS leaves it enabled, then that can break our use
+ * of the bit-banging I2C interfaces. This is notably the case with the
+ * Mac Mini in EFI mode.
+ */
+void
+intel_i2c_reset_gmbus(struct drm_device *dev)
+{
+ struct drm_i915_private *dev_priv = dev-dev_private;
+
+ if (IS_IGDNG(dev)) {
+ I915_WRITE(PCH_GMBUS0, 0);
+ } else {
+ I915_WRITE(GMBUS0, 0);
+ }
+}
+
/**
* intel_i2c_create - instantiate an Intel i2c bus using the specified GPIO reg
* @dev: DRM device
@@ -168,6 +185,8 @@ struct i2c_adapter *intel_i2c_create(struct drm_device
*dev, const u32 reg,
if(i2c_bit_add_bus(chan-adapter))
goto out_free;
+ intel_i2c_reset_gmbus(dev);
+
/* JJJ: raise SCL and SDA? */
intel_i2c_quirk_set(dev, true);
Bug#567561: xserver-xorg-video-intel: Intermittent flickers then blank screen after resuming from suspend
On 4 February 2010 06:20, Brice Goglin brice.gog...@ens-lyon.org wrote:
reassign 567561 linux-2.6 2.6.32-5
forwarded 567561 http://bugzilla.kernel.org/show_bug.cgi?id=14781
tags 567561 +fixed-upstream
thank you
Iain Buclaw wrote:
This issue has also been reported elsewhere too:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/492392
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/506444
It actually seems that this problem has been fixed in Linux current
stable:
http://bugzilla.kernel.org/show_bug.cgi?id=14781
So can we please sync 2.6.32-trunk with upstream?
I am reassigning the bug to the kernel then.
Brice
Thought I might give it a try in the meantime (patch I used attached).
The results I got were that flickering continued, but stopped after a while
- no crash - which is progress!
What stopped the flickering fullstop was:
options i915 powersave=0
Inside /etc/modprobe.d/i915-powersave.conf
Regards
--
Iain Bucław
*(p e ? p++ : p) = (c 0x0f) + '0';
diff -Naurp a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_display.c
--- a/drivers/gpu/drm/i915/intel_display.c 2010-02-03 23:13:41.482798291 +
+++ b/drivers/gpu/drm/i915/intel_display.c 2010-02-03 23:20:29.487796558 +
@@ -3665,125 +3665,6 @@ static void intel_gpu_idle_timer(unsigne
queue_work(dev_priv-wq, dev_priv-idle_work);
}
-void intel_increase_renderclock(struct drm_device *dev, bool schedule)
-{
- drm_i915_private_t *dev_priv = dev-dev_private;
-
- if (IS_IGDNG(dev))
- return;
-
- if (!dev_priv-render_reclock_avail) {
- DRM_DEBUG(not reclocking render clock\n);
- return;
- }
-
- /* Restore render clock frequency to original value */
- if (IS_G4X(dev) || IS_I9XX(dev))
- pci_write_config_word(dev-pdev, GCFGC, dev_priv-orig_clock);
- else if (IS_I85X(dev))
- pci_write_config_word(dev-pdev, HPLLCC, dev_priv-orig_clock);
- DRM_DEBUG(increasing render clock frequency\n);
-
- /* Schedule downclock */
- if (schedule)
- mod_timer(dev_priv-idle_timer, jiffies +
- msecs_to_jiffies(GPU_IDLE_TIMEOUT));
-}
-
-void intel_decrease_renderclock(struct drm_device *dev)
-{
- drm_i915_private_t *dev_priv = dev-dev_private;
-
- if (IS_IGDNG(dev))
- return;
-
- if (!dev_priv-render_reclock_avail) {
- DRM_DEBUG(not reclocking render clock\n);
- return;
- }
-
- if (IS_G4X(dev)) {
- u16 gcfgc;
-
- /* Adjust render clock... */
- pci_read_config_word(dev-pdev, GCFGC, gcfgc);
-
- /* Down to minimum... */
- gcfgc = ~GM45_GC_RENDER_CLOCK_MASK;
- gcfgc |= GM45_GC_RENDER_CLOCK_266_MHZ;
-
- pci_write_config_word(dev-pdev, GCFGC, gcfgc);
- } else if (IS_I965G(dev)) {
- u16 gcfgc;
-
- /* Adjust render clock... */
- pci_read_config_word(dev-pdev, GCFGC, gcfgc);
-
- /* Down to minimum... */
- gcfgc = ~I965_GC_RENDER_CLOCK_MASK;
- gcfgc |= I965_GC_RENDER_CLOCK_267_MHZ;
-
- pci_write_config_word(dev-pdev, GCFGC, gcfgc);
- } else if (IS_I945G(dev) || IS_I945GM(dev)) {
- u16 gcfgc;
-
- /* Adjust render clock... */
- pci_read_config_word(dev-pdev, GCFGC, gcfgc);
-
- /* Down to minimum... */
- gcfgc = ~I945_GC_RENDER_CLOCK_MASK;
- gcfgc |= I945_GC_RENDER_CLOCK_166_MHZ;
-
- pci_write_config_word(dev-pdev, GCFGC, gcfgc);
- } else if (IS_I915G(dev)) {
- u16 gcfgc;
-
- /* Adjust render clock... */
- pci_read_config_word(dev-pdev, GCFGC, gcfgc);
-
- /* Down to minimum... */
- gcfgc = ~I915_GC_RENDER_CLOCK_MASK;
- gcfgc |= I915_GC_RENDER_CLOCK_166_MHZ;
-
- pci_write_config_word(dev-pdev, GCFGC, gcfgc);
- } else if (IS_I85X(dev)) {
- u16 hpllcc;
-
- /* Adjust render clock... */
- pci_read_config_word(dev-pdev, HPLLCC, hpllcc);
-
- /* Up to maximum... */
- hpllcc = ~GC_CLOCK_CONTROL_MASK;
- hpllcc |= GC_CLOCK_133_200;
-
- pci_write_config_word(dev-pdev, HPLLCC, hpllcc);
- }
- DRM_DEBUG(decreasing render clock frequency\n);
-}
-
-/* Note that no increase function is needed for this - increase_renderclock()
- * will also rewrite these bits
- */
-void intel_decrease_displayclock(struct drm_device *dev)
-{
- if (IS_IGDNG(dev))
- return;
-
- if (IS_I945G(dev) || IS_I945GM(dev) || IS_I915G(dev) ||
- IS_I915GM(dev)) {
- u16 gcfgc;
-
- /* Adjust render clock... */
- pci_read_config_word(dev-pdev, GCFGC, gcfgc);
-
- /* Down to minimum... */
- gcfgc = ~0xf0;
- gcfgc |= 0x80;
-
- pci_write_config_word(dev-pdev, GCFGC, gcfgc);
- }
-}
-
#define CRTC_IDLE_TIMEOUT 1000 /* ms */
static void intel_crtc_idle_timer(unsigned long arg)
@@ -3897,12 +3778,6 @@ static void intel_idle_update(struct wor
mutex_lock(dev-struct_mutex);
- /* GPU isn't processing, downclock it. */
- if (!dev_priv-busy) {
- intel_decrease_renderclock(dev);
- intel_decrease_displayclock(dev);
- }
-
list_for_each_entry(crtc, dev-mode_config.crtc_list, head) {
/* Skip inactive CRTCs */
if (!crtc-fb)
@@ -3936,8 +3811,11 @@ void intel_mark_busy(struct drm_device *
if (!drm_core_check_feature(dev, DRIVER_MODESET))
return;
- dev_priv-busy = true;
-
Re: Debian 2.6.32 CONFIG_WIRELESS_OLD_REGULATORY, wireless-regdb and crda
On Thursday 04 February 2010 11:42:33 Luis R. Rodriguez wrote: On Mon, Feb 1, 2010 at 6:10 PM, Paul Wise p...@debian.org wrote: On Mon, 2010-02-01 at 09:58 -0800, Luis R. Rodriguez wrote: I can help with this only if no one else is up for it. I personally however find building a key on the fly for each build pretty pointless and would like to know if a package would be acceptable upstream on Debian if OpenSSL is used to allow administrators to add their own keys into the /etc/wireless-regdb/pubkeys/ dir for CRDA and from the start only trust John's key. As part of upstream, you're probably the best person to do the packaging stuff for Debian. OK, in that case here is my first shot at this. http://wireless.kernel.org/download/wireless-regdb/debs/ http://wireless.kernel.org/download/crda/debs/ Tim -- notice both packages have a Replaces: wireless-crda. If debian upstreams both packages then I think it would be good to separate the packages as I am recommending for integration on Debian and for Ubuntu to also use the same debian packages as debian. I think this would mean also having the new Ubuntu kernels depend on these new packages instead of the old wireless-crda. The package is very simple, I took what I could from Kel's work but did leave in the signature check stuff, used openssl and also just used cdbs. The wireless-regdb does not change *that* often so I do not expect debian itself to need a custom regulatory database to be automatically built and propagated so I left all the watch stuff out and can do manual updates for now, I can commit to that for now. If that is a requirement however, I am not that familiar with new package policies and am unclear how to do that. I would prefer if we can get something started and uploaded for now which at least meets the requirements for integration into an eventual stable release, but that's just me. Please review and let me know what you think. These demonstrate that most of what I've attempted to explain about the difficulties of getting this software into the Debian software pool in a maintainable form has been taken lightly. To reiterate what I think is most important: The software should be built from its preferable form of modification to produce the resulting binary. This helps to make the source package available to other developers to modify and rebuild without invasive packaging changes. An alternative approach: http://sidux.net/kelmo/sidux/crap/crda/crda_1.1.1-1.dsc Also, it seems that the REGDB_CHANGED stuff in wireless-regdb/Makefile does not work as expected - the sha1sum.txt file possibly contains the hash from an old db.txt Thanks, Kel. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#523735: Works with kernel-package now, but it is still confusing
Hi, any plans on uploading a new version that fixes this bug? Also, I'm still nog 100% sure I understand what is happening here. From what I understand: 1) Official kernel packages pass 2 arguments to the script, the second is the filename of the kernel binary. 2) kernel-package generated packages pass 2 arguments to the script, the second is the filename of the kernel binary. Is there another way of generating a kernel image that does not pass this parameter? If so, which is that and could a comment about it perhaps be added? If not, why is there a check for the second parameter in the first place? # kernel-package passes an extra arg if [ -n $2 ]; then Furthermore, the current comment is confusing. It suggests that _only_ kernel-package passes the extra arg, while original linux images also pass it. Gr. Matthijs signature.asc Description: Digital signature
Web Site Designing SEO (internet marketing) for low cost - Coimbatore, INDIA
-- Does your company need any of our Services ? ___ Our Best Services Offered.. Web designing / Web development / SEO-Internet Marketing/ Domain Registration and Hosting Logo Designing/Brochure Designing/E-Brochure In Addition to this we do AD POSTING TO MAJOR CLASSIFIEDS EMAIL HARVESTING ARTICLE SUBMISSION DIRECTORY SUBMISSION READYMADE SOFTWARES HR - JOB CONSULTANCY etc., _ For more information log on to http://www.teamads.com (with live chat option) Get in Touch with us - ad...@teamads.com online enquiries : enpershyaam - Yahoo enpershyaam - Skype enpershyaam - Gmail Mobile: +91 99422 20302 +91 90420 96924 Thank you !
Bug#568397: linux-image-2.6.32-trunk-amd64: null pointer dereference on USB CDC ACM device with no endpoints on control interface
Package: linux-2.6 Version: 2.6.32-5 Severity: normal Hi, while playing with an USB device, I found that the kernel dereferences a NULL pointer if a CDC ACM device declares to have no endpoints associated with the CDC control interface. I believe the validity check should be more stringent here. The relevant bits of code look like this: epctrl = control_interface-cur_altsetting-endpoint[0].desc; epread = data_interface-cur_altsetting-endpoint[0].desc; epwrite = data_interface-cur_altsetting-endpoint[1].desc; No further verification except for swapped data endpoints is performed afterwards. Simon -- Package-specific info: ** Version: Linux version 2.6.32-trunk-amd64 (Debian 2.6.32-5) (b...@decadent.org.uk) (gcc version 4.3.4 (Debian 4.3.4-6) ) #1 SMP Sun Jan 10 22:40:40 UTC 2010 ** Command line: BOOT_IMAGE=/vmlinuz-2.6.32-trunk-amd64 root=/dev/mapper/richter-root ro quiet ** Not tainted ** Kernel log: [11278.817700] cdc_acm 2-3:1.0: This device cannot do calls on its own. It is not a modem. [11278.817743] BUG: unable to handle kernel NULL pointer dereference at 0004 [11278.817746] IP: [a02b9ca9] acm_probe+0x4d6/0xcb1 [cdc_acm] [11278.817756] PGD 600d1067 PUD 60086067 PMD 0 [11278.817760] Oops: [#1] SMP [11278.817762] last sysfs file: /sys/devices/pci:00/:00:12.0/usb2/2-3/manufacturer [11278.817765] CPU 0 [11278.817767] Modules linked in: radeon ttm drm_kms_helper drm agpgart i2c_algo_bit ppdev lp sco bridge stp rfcomm bnep l2cap crc16 powernow_k8 cpufreq_powersave cpufreq_userspace cpufreq_conservative cpufreq_stats binfmt_misc deflate zlib_deflat ellia serpent blowfish cast5 des_generic cbc cryptd aes_x86_64 aes_generic xcbc rmd160 sha256_generic sha1_generic hmac crypto_null af_key fuse nfsd exportfs nfs lockd fscache nfs_acl auth_rpcgss sunrpc nls_utf8 cifs hwmon_vid loop dm_crypt snd_hd altek snd_hda_intel snd_seq_midi snd_hda_codec snd_rawmidi snd_seq_midi_event snd_hwdep snd_seq snd_seq_device snd_pcm_oss snd_mixer_oss snd_pcm snd_timer usbhid pl2303 snd btusb shpchp cdc_acm i2c_piix4 hid usbserial parport_pc edac_core k8temp e h soundcore parport i2c_core processor rfkill snd_page_alloc pcspkr evdev ext3 jbd mbcache dm_mod ide_cd_mod cdrom sd_mod crc_t10dif ata_generic ide_pci_gener c ahci ohci_hcd ehci_hcd atiixp r8169 libata 8139too 8139cp mii floppy button ide_core usbcore nls_base scsi_mod thermal fan thermal_sys [last unloaded: scsi_wait_scan] [11278.817841] Pid: 309, comm: khubd Not tainted 2.6.32-trunk-amd64 #1 GA-MA74GM-S2H [11278.817843] RIP: 0010:[a02b9ca9] [a02b9ca9] acm_probe+0x4d6/0xcb1 [cdc_acm] [11278.817849] RSP: 0018:88006cea1930 EFLAGS: 00010293 [11278.817851] RAX: RBX: 880052c08800 RCX: [11278.817853] RDX: RSI: 80d0 RDI: 8800376ea000 [11278.817856] RBP: 8800376e9000 R08: 000c R09: 880062ae9888 [11278.817858] R10: 80d000d0 R11: 000186a0 R12: 880062ae9888 [11278.817860] R13: 880052c08000 R14: R15: 880052c08000 [11278.817863] FS: 7f4dc9bf5910() GS:88000180() knlGS: [11278.817866] CS: 0010 DS: 0018 ES: 0018 CR0: 8005003b [11278.817868] CR2: 0004 CR3: 60157000 CR4: 06f0 [11278.817870] DR0: DR1: DR2: [11278.817873] DR3: DR6: 0ff0 DR7: 0400 [11278.817875] Process khubd (pid: 309, threadinfo 88006cea, task 88006cdff810) [11278.817877] Stack: [11278.817879] 813c7d84 88006f5329a0 810fcb34 [11278.817882] 0 880060130090 8113cebf 880052c08800 [11278.817886] 0 880062ae9840 88006013 [11278.817890] Call Trace: [11278.817897] [810fcb34] ? iput+0x27/0x60 [11278.817902] [8113cebf] ? sysfs_addrm_finish+0x66/0x204 [11278.817914] [a005975a] ? usb_match_one_id+0x23/0x7f [usbcore] [11278.817924] [a005a6dd] ? usb_probe_interface+0x107/0x157 [usbcore] [11278.817930] [8120e0e8] ? driver_probe_device+0xa3/0x14b [11278.817934] [8120e1ff] ? __device_attach+0x0/0x39 [11278.817937] [8120d713] ? bus_for_each_drv+0x46/0x77 [11278.817940] [8120e2bb] ? device_attach+0x60/0x7e [11278.817942] [8120d58b] ? bus_probe_device+0x1f/0x38 [11278.817948] [8120c258] ? device_add+0x3a2/0x537 [11278.817956] [a005942a] ? usb_set_configuration+0x589/0x5f2 [usbcore] [11278.817965] [a0060dac] ? generic_probe+0x61/0xa9 [usbcore] [11278.817969] [8120e0e8] ? driver_probe_device+0xa3/0x14b [11278.817972] [8120e1ff] ? __device_attach+0x0/0x39 [11278.817975] [8120d713] ? bus_for_each_drv+0x46/0x77 [11278.817978] [8120e2bb] ? device_attach+0x60/0x7e
Bug#516968: closed by maximilian attems m...@stro.at (Re: SATA drive usage)
On Mon, Feb 1, 2010 at 15:09, Debian Bug Tracking System ow...@bugs.debian.org wrote: This is an automatic notification regarding your Bug report which was filed against the linux-2.6 package: #516968: base: SATA drive is resumed at boot, even if not used It has been closed by maximilian attems m...@stro.at. Their explanation is attached below along with your original report. If this explanation is unsatisfactory and you have not received a better one in a separate message then please contact maximilian attems m...@stro.at by replying to this email. -- 516968: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=516968 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- Forwarded message -- From: maximilian attems m...@stro.at To: 516968-d...@bugs.debian.org Date: Mon, 1 Feb 2010 14:55:38 +0100 Subject: Re: SATA drive usage just add your small hdparam snipped in /etc/rc.local anyway not a kernel bug, but just a userspace policy, thus closing. /etc/rc.local is executed AFTER kernel spins-up the disk. i don't want to put disk to sleep every boot. it is already in 'start in sleep mode' but someway kernel spins-up the disk even if it is not to be mounted. this is kernel thing i think so, or sata_nv kernel module. normally, all disks are spinned-up in BIOS's post stage. but when disk has set option 'start in sleep mode' post stage skips the disk. the same kernel should do. -- Forwarded message -- From: Mark Poks markp...@wp.pl To: Debian Bug Tracking System sub...@bugs.debian.org Date: Tue, 24 Feb 2009 20:17:00 +0100 Subject: base: SATA drive is resumed at boot, even if not used Package: base Severity: important i have extra SATA disk which i use rarely. so to reduce some power consumption and noise - i put the disk to 'start in sleep state'. i've done it with hdparam -s /dev/sdX. obviously i have removed all links in fstab to that drive. to prevent any auto mount. motor of the disk is no longer starting when bios is booting-up the machine, but unfortunetly it does when system starts INIT section (after initrd finishes it's job). i cannot discover what exactly makes disk to start it's motor but it's possibly sata_nv driver - motor begins to work near logs from this driver. i would like to start my extra disks on demand - when they are needed, but as for now i can't do that. Mark -- System Information: Debian Release: 5.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686-bigmem (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
Re: Please reject linux-2.6 2.6.32-7
On Thu, Feb 04, 2010 at 08:22:32AM +, Ben Hutchings wrote: linux-2.6 version 2.6.32-7 includes an incomplete bug fix that will result in failure to boot 32-bit userland on a 64-bit kernel. 2.6.32-8 will have the complete bug fix. Looks like the amd64 build has been approved - can we avoid accepting the other archs? i386, in particular, will cause a lot of problems. -- dann frazier -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#568414: linux-image-2.6.32-trunk-amd64: Please add/enable CONFIG_DVB_LGS8GXX=m
Package: linux-2.6 Version: 2.6.32-5 Severity: normal I'm not able to use my USB DMB tuner which get the following error in dmesg [ 427.984996] dvb-usb: found a 'Conexant DMB-TH Stick' in warm state. [ 428.328052] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. [ 428.328316] DVB: registering new adapter (Conexant DMB-TH Stick) [ 430.571246] DVB: Unable to find symbol lgs8gxx_attach() [ 430.571250] dvb-usb: no frontend was attached by 'Conexant DMB-TH Stick' [ 430.571689] input: IR-receiver inside an USB DVB receiver as /devices/pci:00/:00:1a.7/usb1/1-4/1-4.4/input/input8 [ 430.571744] dvb-usb: schedule remote query interval to 100 msecs. [ 430.572027] dvb-usb: Conexant DMB-TH Stick successfully initialized and connected. [ 430.572049] usbcore: registered new interface driver dvb_usb_cxusb Please enable LGS8GXX Thanks -- Package-specific info: ** Version: Linux version 2.6.32-trunk-amd64 (Debian 2.6.32-5) (b...@decadent.org.uk) (gcc version 4.3.4 (Debian 4.3.4-6) ) #1 SMP Sun Jan 10 22:40:40 UTC 2010 ** Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-trunk-amd64 root=UUID=ddf616cc-0e18-47c9-8ab5-8515f6d55fc2 ro quiet ** Not tainted ** Kernel log: [22798.784599]groups: 0-1 (cpu_power = 2048) [22798.784604] CPU1 attaching sched-domain: [22798.784606] domain 0: span 0-1 level MC [22798.784608] groups: 1 0 [22798.784612] domain 1: span 0-1 level CPU [22798.784614]groups: 0-1 (cpu_power = 2048) [22798.988717] VFS: busy inodes on changed media or resized disk sr0 [22799.008702] VFS: busy inodes on changed media or resized disk sr0 [22800.894856] VFS: busy inodes on changed media or resized disk sr0 [22800.912845] VFS: busy inodes on changed media or resized disk sr0 [22800.930839] VFS: busy inodes on changed media or resized disk sr0 [22802.896956] VFS: busy inodes on changed media or resized disk sr0 [22802.914970] VFS: busy inodes on changed media or resized disk sr0 [22802.932936] VFS: busy inodes on changed media or resized disk sr0 [22804.898060] VFS: busy inodes on changed media or resized disk sr0 [22804.916047] VFS: busy inodes on changed media or resized disk sr0 [22804.952033] VFS: busy inodes on changed media or resized disk sr0 [22806.896165] VFS: busy inodes on changed media or resized disk sr0 [22806.914173] VFS: busy inodes on changed media or resized disk sr0 [22806.932142] VFS: busy inodes on changed media or resized disk sr0 [22808.898291] VFS: busy inodes on changed media or resized disk sr0 [22808.916259] VFS: busy inodes on changed media or resized disk sr0 [22808.952245] VFS: busy inodes on changed media or resized disk sr0 [22810.908733] VFS: busy inodes on changed media or resized disk sr0 [22823.383872] hub 1-0:1.0: over-current change on port 1 [22823.37] /build/buildd-linux-2.6_2.6.32-5-amd64-9RvY2G/linux-2.6-2.6.32/debian/build/source_amd64_none/drivers/hid/usbhid/hid-core.c: can't reset device, :00:1a.7-4.2/input0, status -71 [22823.403984] usb 1-4: clear tt 1 (0080) error -71 [22823.408372] /build/buildd-linux-2.6_2.6.32-5-amd64-9RvY2G/linux-2.6-2.6.32/debian/build/source_amd64_none/drivers/hid/usbhid/hid-core.c: can't reset device, :00:1a.7-4.2/input0, status -71 [22823.412358] usb 1-4: clear tt 1 (0080) error -71 [22823.424000] /build/buildd-linux-2.6_2.6.32-5-amd64-9RvY2G/linux-2.6-2.6.32/debian/build/source_amd64_none/drivers/hid/usbhid/hid-core.c: can't reset device, :00:1a.7-4.2/input0, status -71 [22823.427987] usb 1-4: clear tt 1 (0080) error -71 [22823.432375] /build/buildd-linux-2.6_2.6.32-5-amd64-9RvY2G/linux-2.6-2.6.32/debian/build/source_amd64_none/drivers/hid/usbhid/hid-core.c: can't reset device, :00:1a.7-4.2/input0, status -71 [22823.436362] usb 1-4: clear tt 1 (0080) error -71 [22823.448007] /build/buildd-linux-2.6_2.6.32-5-amd64-9RvY2G/linux-2.6-2.6.32/debian/build/source_amd64_none/drivers/hid/usbhid/hid-core.c: can't reset device, :00:1a.7-4.2/input0, status -71 [22823.451990] usb 1-4: clear tt 1 (0080) error -71 [22823.464009] /build/buildd-linux-2.6_2.6.32-5-amd64-9RvY2G/linux-2.6-2.6.32/debian/build/source_amd64_none/drivers/hid/usbhid/hid-core.c: can't reset device, :00:1a.7-4.2/input0, status -71 [22823.467993] usb 1-4: clear tt 1 (0080) error -71 [22823.472382] /build/buildd-linux-2.6_2.6.32-5-amd64-9RvY2G/linux-2.6-2.6.32/debian/build/source_amd64_none/drivers/hid/usbhid/hid-core.c: can't reset device, :00:1a.7-4.2/input0, status -71 [22823.476368] usb 1-4: clear tt 1 (0080) error -71 [22823.484008] hub 1-0:1.0: over-current change on port 2 [22823.488013] /build/buildd-linux-2.6_2.6.32-5-amd64-9RvY2G/linux-2.6-2.6.32/debian/build/source_amd64_none/drivers/hid/usbhid/hid-core.c: can't reset device, :00:1a.7-4.2/input0, status -71 [22823.491997] usb 1-4: clear tt 1 (0080) error -71 [22823.496384] /build/buildd-linux-2.6_2.6.32-5-amd64-9RvY2G/linux-2.6-2.6.32/debian/build/source_amd64_none/drivers/hid/usbhid/hid-core.c: can't
Bug#568416: 64-bit kernel/32-bit userland boot failure
Source: linux-2.6 Version: 2.6.32-7 Severity: grave This release is known to cause boot problems on 32-bit systems w/ a 64-bit kernel: http://article.gmane.org/gmane.linux.kernel/946249 -- dann frazier -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#568422: linux-image-2.6-amd64: Please update to depend on latest kernel
Subject: linux-image-2.6-amd64: Please update to depend on latest kernel Package: linux-image-2.6-amd64 Version: 2.6.32+23 Severity: important Can this package be updated more frequently in Sid to depend on the latest kernel, as 2.6.32-2 is out today I see; yet this is still depending on the old -trunk release. It makes checking for updates much more time consuming without it. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages linux-image-2.6-amd64 depends on: ii linux-image-2.6.32-trunk-amd6 2.6.32-5 Linux 2.6.32 for 64-bit PCs linux-image-2.6-amd64 recommends no packages. linux-image-2.6-amd64 suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#568414: linux-image-2.6.32-trunk-amd64: Please add/enable CONFIG_DVB_LGS8GXX=m
On Fri, Feb 05, 2010 at 01:28:27AM +0800, H.W. Wan wrote: Package: linux-2.6 Version: 2.6.32-5 Severity: normal outdated I'd recommned newer on unstable has many fixes. I'm not able to use my USB DMB tuner which get the following error in dmesg [ 427.984996] dvb-usb: found a 'Conexant DMB-TH Stick' in warm state. [ 428.328052] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. [ 428.328316] DVB: registering new adapter (Conexant DMB-TH Stick) [ 430.571246] DVB: Unable to find symbol lgs8gxx_attach() [ 430.571250] dvb-usb: no frontend was attached by 'Conexant DMB-TH Stick' [ 430.571689] input: IR-receiver inside an USB DVB receiver as /devices/pci:00/:00:1a.7/usb1/1-4/1-4.4/input/input8 [ 430.571744] dvb-usb: schedule remote query interval to 100 msecs. [ 430.572027] dvb-usb: Conexant DMB-TH Stick successfully initialized and connected. [ 430.572049] usbcore: registered new interface driver dvb_usb_cxusb Please enable LGS8GXX wow that driver didn't get ported to request_firmware() that's cool you seem to be the ideal tester for that patch: http://patchwork.kernel.org/patch/56822/ -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#524132: linux-image-2.6.26-2-686: Fails to load Atheros wifi
On Thu, Feb 04, 2010 at 12:13:11PM -0500, bllea...@aol.com wrote: Wow, I had forgotten about that. Turns out I just needed to install a new madwifi modules for the specific kernel version. Then it started working. --Bryan did you try ath5k in newer linux images? aka 2.6.32? that be close to the image we will release for squeeze. thanks for your feedback. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 568416
Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35lenny7 tags 568416 + pending Bug #568416 [src:linux-2.6] 64-bit kernel/32-bit userland boot failure Added tag(s) pending. End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#568422: marked as done (linux-image-2.6-amd64: Please update to depend on latest kernel)
Your message dated Thu, 4 Feb 2010 19:43:02 +0100 with message-id 20100204184302.gm9...@baikonur.stro.at and subject line Re: Bug#568422: linux-image-2.6-amd64: Please update to depend on latest kernel has caused the Debian Bug report #568422, regarding linux-image-2.6-amd64: Please update to depend on latest kernel 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 ow...@bugs.debian.org immediately.) -- 568422: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=568422 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Subject: linux-image-2.6-amd64: Please update to depend on latest kernel Package: linux-image-2.6-amd64 Version: 2.6.32+23 Severity: important Can this package be updated more frequently in Sid to depend on the latest kernel, as 2.6.32-2 is out today I see; yet this is still depending on the old -trunk release. It makes checking for updates much more time consuming without it. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages linux-image-2.6-amd64 depends on: ii linux-image-2.6.32-trunk-amd6 2.6.32-5 Linux 2.6.32 for 64-bit PCs linux-image-2.6-amd64 recommends no packages. linux-image-2.6-amd64 suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- On Thu, Feb 04, 2010 at 06:19:23PM +, Dennis 123321 wrote: Subject: linux-image-2.6-amd64: Please update to depend on latest kernel Package: linux-image-2.6-amd64 Version: 2.6.32+23 Severity: important Can this package be updated more frequently in Sid to depend on the latest kernel, as 2.6.32-2 is out today I see; yet this is still depending on the old -trunk release. It makes checking for updates much more time consuming without it. no concrete code nor suggestion how to solve this. also this what unstable is for to sync such releases. Requiring stable ABI is a price to pay for. closing as nothing new. this needs just a bit of patience, also it is important for us not to sync if we know that a specific release had a huge regression. ---End Message---
Bug#568414: linux-image-2.6.32-trunk-amd64: Please add/enable CONFIG_DVB_LGS8GXX=m
Hi maximilian, I would love to test however the tuner use the chipset lgs8gl5 instead of lgs8g75 which do not need to load the firmware On Fri, Feb 5, 2010 at 2:09 AM, maximilian attems m...@stro.at wrote: On Fri, Feb 05, 2010 at 01:28:27AM +0800, H.W. Wan wrote: Package: linux-2.6 Version: 2.6.32-5 Severity: normal outdated I'd recommned newer on unstable has many fixes. I'm not able to use my USB DMB tuner which get the following error in dmesg [ 427.984996] dvb-usb: found a 'Conexant DMB-TH Stick' in warm state. [ 428.328052] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. [ 428.328316] DVB: registering new adapter (Conexant DMB-TH Stick) [ 430.571246] DVB: Unable to find symbol lgs8gxx_attach() [ 430.571250] dvb-usb: no frontend was attached by 'Conexant DMB-TH Stick' [ 430.571689] input: IR-receiver inside an USB DVB receiver as /devices/pci:00/:00:1a.7/usb1/1-4/1-4.4/input/input8 [ 430.571744] dvb-usb: schedule remote query interval to 100 msecs. [ 430.572027] dvb-usb: Conexant DMB-TH Stick successfully initialized and connected. [ 430.572049] usbcore: registered new interface driver dvb_usb_cxusb Please enable LGS8GXX wow that driver didn't get ported to request_firmware() that's cool you seem to be the ideal tester for that patch: http://patchwork.kernel.org/patch/56822/
Processed: Re: Bug#568317: linux-image-* postinst did not correctly run lilo
Processing commands for cont...@bugs.debian.org: reassign 568317 linux-2.6 Bug #568317 [perl] perl: Executes every second $_ test only Bug reassigned from package 'perl' to 'linux-2.6'. Bug No longer marked as found in versions perl/5.10.0-19lenny2. retitle 568317 linux-image-* postinst did not correctly run lilo Bug #568317 [linux-2.6] perl: Executes every second $_ test only Changed Bug title to 'linux-image-* postinst did not correctly run lilo' from 'perl: Executes every second $_ test only' thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#568414: linux-image-2.6.32-trunk-amd64: Please add/enable CONFIG_DVB_LGS8GXX=m
On Fri, Feb 05, 2010 at 02:39:09AM +0800, Hing Wah Wan wrote: Hi maximilian, I would love to test however the tuner use the chipset lgs8gl5 instead of lgs8g75 which do not need to load the firmware sure you need to apply mentioned patch on top of latest linux-2.6 and then rebuild the image extract firmware. but by the looks of your response you don't know what a source patch is, thus you will most likely get a specific image to test soon. thanks for your patience. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#568414: linux-image-2.6.32-trunk-amd64: Please add/enable CONFIG_DVB_LGS8GXX=m
Hi maximilian, I know what a patch is (I'm a developer). I'm mentioning the device use the chipset LGS8GL5 ( LGS8GXX_PROD_LGS8GL5) instead of LGS8G75 ( LGS8GXX_PROD_LGS8G75) which do not require loading that blob so I'm not able to test if it will work properly. Thanks On Fri, Feb 5, 2010 at 2:44 AM, maximilian attems m...@stro.at wrote: On Fri, Feb 05, 2010 at 02:39:09AM +0800, Hing Wah Wan wrote: Hi maximilian, I would love to test however the tuner use the chipset lgs8gl5 instead of lgs8g75 which do not need to load the firmware sure you need to apply mentioned patch on top of latest linux-2.6 and then rebuild the image extract firmware. but by the looks of your response you don't know what a source patch is, thus you will most likely get a specific image to test soon. thanks for your patience.
Re: Bug#568317: linux-image-* postinst did not correctly run lilo
reassign 568317 linux-2.6 retitle 568317 linux-image-* postinst did not correctly run lilo thanks On Thu, Feb 04, 2010 at 04:49:23PM +1100, paul.sz...@sydney.edu.au wrote: This is not a bug in perl, works as documented in 'man perlretut'. Right. The issue is with the /g modifier, as shown with script: This is bad usage in the linux-source-2.6.26 package. My /var/lib/dpkg/info/linux-image-2.6.26-*.postinst file has header: Should I report this bug (spurious, un-needed /g) to the linux-source-2.6.26 package, or will you be able to re-assign, or otherwise let Mr Srivastava know? Reassigning now. I see similar m//g usage in /var/lib/dpkg/info/linux-image-2.6.32-trunk-amd64.postinst but you could probably follow up and explain what exactly was incorrect about running lilo. -- Niko Tyni nt...@debian.org -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#568414: linux-image-2.6.32-trunk-amd64: Please add/enable CONFIG_DVB_LGS8GXX=m
On Fri, Feb 05, 2010 at 03:00:41AM +0800, Hing Wah Wan wrote: Hi maximilian, I know what a patch is (I'm a developer). I'm mentioning the device use the chipset LGS8GL5 ( LGS8GXX_PROD_LGS8GL5) instead of LGS8G75 ( LGS8GXX_PROD_LGS8G75) which do not require loading that blob so I'm not able to test if it will work properly. Thanks well that is easy, you can just blacklist aboves, see man modprobe.conf put the blacklist in /etc/modprobe.d -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 568414
Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35lenny7 tags 568414 + pending Bug #568414 [linux-2.6] linux-image-2.6.32-trunk-amd64: Please add/enable CONFIG_DVB_LGS8GXX=m Added tag(s) pending. End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#568428: linux-source-2.6.32: Unable to use MagicPro ProTV DMB-TH usb Tuner (Conexant DMB-TH Stick)
Package: linux-source-2.6.32
Version: 2.6.32-5
Severity: normal
Without comment out the following line related to draining video/message, I'm
not able to view/scan any channel for my tuner.
--- cxusb.c.orig2009-12-03 11:51:21.0 +0800
+++ cxusb.c 2010-02-05 02:08:41.0 +0800
@@ -370,7 +370,7 @@
{
if (onoff) {
u8 buf[2] = { 0x03, 0x00 };
- cxusb_d680_dmb_drain_video(adap-dev);
+// cxusb_d680_dmb_drain_video(adap-dev);
return cxusb_ctrl_msg(adap-dev, CMD_STREAMING_ON,
buf, sizeof(buf), NULL, 0);
} else {
@@ -1135,8 +1135,8 @@
/* Drain USB pipes to avoid hang after reboot */
for (n = 0; n 5; n++) {
- cxusb_d680_dmb_drain_message(d);
- cxusb_d680_dmb_drain_video(d);
+// cxusb_d680_dmb_drain_message(d);
+// cxusb_d680_dmb_drain_video(d);
msleep(200);
}
However i'm not sure if this will break other user.
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (990, 'unstable'), (500, 'transitional'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32 (SMP w/2 CPU cores)
Locale: LANG=en_HK.UTF-8, LC_CTYPE=zh_HK.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages linux-source-2.6.32 depends on:
ii binutils 2.20-5 The GNU assembler, linker and bina
ii bzip2 1.0.5-4high-quality block-sorting file co
Versions of packages linux-source-2.6.32 recommends:
ii gcc 4:4.4.2-3 The GNU C compiler
ii libc6-dev [libc-dev] 2.10.2-5 Embedded GNU C Library: Developmen
ii make 3.81-7 An utility for Directing compilati
Versions of packages linux-source-2.6.32 suggests:
ii kernel-package12.032 A utility for building Linux kerne
ii libncurses5-dev [ncurses- 5.7+20090803-2 developer's libraries and docs for
ii libqt3-mt-dev 3:3.3.8b-6 Qt development files (Threaded)
-- no debconf information
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#568454: linux-source-2.6.32: fails to build vt6656
Package: linux-source-2.6.32 Version: 2.6.32-6 Severity: normal I don't really care what vt6656 is but it breaks my build. I just recycled a config that worked for me with some earlier upstream kernel and it fails with the Debian one. exec debian/rules DEBIAN_REVISION=6i APPEND_TO_VERSION=-intel-i2c-reset KPKG_SUBARCH=pentiumm ARCH_IN_NAME=YES INITRD=YES kernel_image kernel_headers kernel_debug == making target debian/stamp/conf/vars [new prereqs: ]== == making target debian/stamp/build/kernel [new prereqs: vars]== This is kernel package version 12.032. restore_upstream_debianization test ! -f scripts/package/builddeb.kpkg-dist || mv -f scripts/package/builddeb.kpkg-dist scripts/package/builddeb test ! -f scripts/package/Makefile.kpkg-dist || mv -f scripts/package/Makefile.kpkg-dist scripts/package/Makefile /usr/bin/make EXTRAVERSION=-intel-i2c-reset ARCH=i386 \ bzImage make[1]: Entering directory `/srv/linux-source-2.6.32' scripts/kconfig/conf -s arch/x86/Kconfig make[1]: Leaving directory `/srv/linux-source-2.6.32' make[1]: Entering directory `/srv/linux-source-2.6.32' CHK include/linux/version.h CHK include/linux/utsrelease.h SYMLINK include/asm - include/asm-x86 CALLscripts/checksyscalls.sh CHK include/linux/compile.h Kernel: arch/x86/boot/bzImage is ready (#1) make[1]: Leaving directory `/srv/linux-source-2.6.32' /usr/bin/make EXTRAVERSION=-intel-i2c-reset ARCH=i386 \ modules make[1]: Entering directory `/srv/linux-source-2.6.32' CHK include/linux/version.h CHK include/linux/utsrelease.h SYMLINK include/asm - include/asm-x86 CALLscripts/checksyscalls.sh make[4]: *** No rule to make target `drivers/staging/vt6656/firmware.o', needed by `drivers/staging/vt6656/vt6656_stage.o'. Stop. make[3]: *** [drivers/staging/vt6656] Error 2 make[2]: *** [drivers/staging] Error 2 make[1]: *** [drivers] Error 2 make[1]: Leaving directory `/srv/linux-source-2.6.32' make: *** [debian/stamp/build/kernel] Error 2 -- System Information: Debian Release: 5.0.4 APT prefers stable APT policy: (900, 'stable'), (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.32-intel-i2c-reset (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages linux-source-2.6.32 depends on: ii binutils2.18.1~cvs20080103-7 The GNU assembler, linker and bina ii bzip2 1.0.5-1 high-quality block-sorting file co Versions of packages linux-source-2.6.32 recommends: ii gcc 4:4.3.2-2 The GNU C compiler ii libc6-dev [libc-dev] 2.10.2-5 Embedded GNU C Library: Developmen ii make 3.81-5 The GNU version of the make util Versions of packages linux-source-2.6.32 suggests: ii kernel-package12.032 A utility for building Linux kerne ii libncurses5-dev [ncurses- 5.7+20081213-1 developer's libraries and docs for pn libqt3-mt-dev none (no description available) -- no debconf information -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#568457: FTBFS [powerpc] - format '%x' expects type 'unsigned int'
Source: linux-2.6 Version: 2.6.32-7 Severity: serious I tried to do a local build of trunk on powerpc, and hit the following bug (apparently introduced in 2.6.32-7): cc1: warnings being treated as errors /tmp/buildd/linux-2.6-2.6.32/debian/build/source_powerpc_none/arch/powerpc/kernel/time.c: In function 'register_decrementer_clockevent': /tmp/buildd/linux-2.6-2.6.32/debian/build/source_powerpc_none/arch/powerpc/kernel/time.c:922: error: format '%x' expects type 'unsigned int', but argument 3 has type 'long unsigned int' -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 568457
Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35lenny7 tags 568457 + pending Bug #568457 [src:linux-2.6] FTBFS [powerpc] - format '%x' expects type 'unsigned int' Added tag(s) pending. End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#568317: linux-image-* postinst did not correctly run lilo
Niko Tyni wrote: Reassigning now. ... Thanks. ... you could probably follow up and explain what exactly was incorrect about running lilo. Looking at my /var/lib/dpkg/info/linux-image-*.postinst files, I see in the code reading and parsing $CONF_LOC = '/etc/kernel-img.conf': ... $do_symlink = if /do_symlinks\s*=\s*(no|false|0)\s*$/ig; ... $do_bootloader = Yes if /do_bootloader\s*=\s*(yes|true|1)\s*$/ig; $explicit_do_loader = YES if /do_bootloader\s*=\s*(yes|true|1)\s*$/ig; ... Most of the match patterns are used once only; using /g on them is not necessary, and is probably wasteful (though perl is fast enough to handle such things). The pattern /do_bootloader.../ig is used twice. The first one may match; the second one will surely not match because of the spurious /g, thus explicit_do_loader will never be set (and lilo not run, or run after a question left un-answered in unattended runs of apt-get install). --- Minor issues, while I am criticizing perl style... These patterns are anchored at the end, should also be anchored at the beginning (and with explicit m//) like: $do_symlink = if m/^\s*do_symlinks\s*=\s*(no|false|0)\s*$/i; ... $image_dest = $1 if m/^\s*image_dest\s*=\s*(\S+)\s*$/i; I wonder about the need to use my() in a single-level script. --- Cheers, Paul Paul Szabo p...@maths.usyd.edu.au http://www.maths.usyd.edu.au/u/psz/ School of Mathematics and Statistics University of SydneyAustralia -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#568414: linux-image-2.6.32-trunk-amd64: Please add/enable CONFIG_DVB_LGS8GXX=m
On Thu, 2010-02-04 at 19:59 +0100, maximilian attems wrote: On Fri, Feb 05, 2010 at 03:00:41AM +0800, Hing Wah Wan wrote: Hi maximilian, I know what a patch is (I'm a developer). I'm mentioning the device use the chipset LGS8GL5 ( LGS8GXX_PROD_LGS8GL5) instead of LGS8G75 ( LGS8GXX_PROD_LGS8G75) which do not require loading that blob so I'm not able to test if it will work properly. Thanks well that is easy, you can just blacklist aboves, see man modprobe.conf put the blacklist in /etc/modprobe.d This isn't the problem. The cxusb driver needs one of several different 'front-end' drivers for different devices, including lgs8gl5 (which apprently doesn't support all LGS8GL5 variants!) and lgs8gxx. However, it does not select lgs8gxx, and front-end drivers will not built unless another driver selects them (or CONFIG_DVB_FE_CUSTOMISE is set, which it isn't). I have just applied a fix for this, so lgs8gxx will be included in future. Ben. -- Ben Hutchings friends: People who know you well, but like you anyway. signature.asc Description: Digital signature
Bug#547183: We really need new megaraid_sas
On Wed, Feb 03, 2010 at 03:15:03PM +, Ben Hutchings wrote: On Wed, 2010-02-03 at 14:34 +0100, Ondra 'Kepi' kudlik wrote: Please, increase severity of this bug report and take a look at it. There are more and more servers with this controlers and there is no possibility to have debian running on them now. Backported kernel is not solution because xen version is only provided in 2.6.26 I need new servers online asap and not sure what to do, no sucess with backporting it myself. If this is *necessary* for supporting the new hardware, we will consider the bug important and investigate backporting the driver. Previously it was only reported that omreport did not work fully with the current driver and new hardware. I have added the necessary changes to the pending changes for the next stable update. Please test the result by following the instructions in http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-official-vcs. Ben. -- Ben Hutchings In a hierarchy, every employee tends to rise to his level of incompetence. signature.asc Description: Digital signature
Processed: bug 568397 is forwarded to linux-...@vger.kernel.org
Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35lenny7 forwarded 568397 linux-...@vger.kernel.org Bug #568397 [linux-2.6] linux-image-2.6.32-trunk-amd64: null pointer dereference on USB CDC ACM device with no endpoints on control interface Set Bug forwarded-to-address to 'linux-...@vger.kernel.org'. End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#568397: linux-image-2.6.32-trunk-amd64: null pointer dereference on USB CDC ACM device with no endpoints on control interface
On Thu, Feb 04, 2010 at 03:51:32PM +0100, Simon Richter wrote: Package: linux-2.6 Version: 2.6.32-5 Severity: normal Hi, while playing with an USB device, I found that the kernel dereferences a NULL pointer if a CDC ACM device declares to have no endpoints associated with the CDC control interface. I believe the validity check should be more stringent here. I agree. Let's see what upstream has to say. Ben. The relevant bits of code look like this: epctrl = control_interface-cur_altsetting-endpoint[0].desc; epread = data_interface-cur_altsetting-endpoint[0].desc; epwrite = data_interface-cur_altsetting-endpoint[1].desc; No further verification except for swapped data endpoints is performed afterwards. Simon -- Package-specific info: ** Version: Linux version 2.6.32-trunk-amd64 (Debian 2.6.32-5) (b...@decadent.org.uk) (gcc version 4.3.4 (Debian 4.3.4-6) ) #1 SMP Sun Jan 10 22:40:40 UTC 2010 ** Command line: BOOT_IMAGE=/vmlinuz-2.6.32-trunk-amd64 root=/dev/mapper/richter-root ro quiet ** Not tainted ** Kernel log: [11278.817700] cdc_acm 2-3:1.0: This device cannot do calls on its own. It is not a modem. [11278.817743] BUG: unable to handle kernel NULL pointer dereference at 0004 [11278.817746] IP: [a02b9ca9] acm_probe+0x4d6/0xcb1 [cdc_acm] [11278.817756] PGD 600d1067 PUD 60086067 PMD 0 [11278.817760] Oops: [#1] SMP [11278.817762] last sysfs file: /sys/devices/pci:00/:00:12.0/usb2/2-3/manufacturer [11278.817765] CPU 0 [11278.817767] Modules linked in: radeon ttm drm_kms_helper drm agpgart i2c_algo_bit ppdev lp sco bridge stp rfcomm bnep l2cap crc16 powernow_k8 cpufreq_powersave cpufreq_userspace cpufreq_conservative cpufreq_stats binfmt_misc deflate zlib_deflat ellia serpent blowfish cast5 des_generic cbc cryptd aes_x86_64 aes_generic xcbc rmd160 sha256_generic sha1_generic hmac crypto_null af_key fuse nfsd exportfs nfs lockd fscache nfs_acl auth_rpcgss sunrpc nls_utf8 cifs hwmon_vid loop dm_crypt snd_hd altek snd_hda_intel snd_seq_midi snd_hda_codec snd_rawmidi snd_seq_midi_event snd_hwdep snd_seq snd_seq_device snd_pcm_oss snd_mixer_oss snd_pcm snd_timer usbhid pl2303 snd btusb shpchp cdc_acm i2c_piix4 hid usbserial parport_pc edac_core k8temp e h soundcore parport i2c_core processor rfkill snd_page_alloc pcspkr evdev ext3 jbd mbcache dm_mod ide_cd_mod cdrom sd_mod crc_t10dif ata_generic ide_pci_gener c ahci ohci_hcd ehci_hcd atiixp r8169 libata 8139too 8139cp mii floppy button ide_core usbcore nls_base scsi_mod thermal fan thermal_sys [last unloaded: scsi_wait_scan] [11278.817841] Pid: 309, comm: khubd Not tainted 2.6.32-trunk-amd64 #1 GA-MA74GM-S2H [11278.817843] RIP: 0010:[a02b9ca9] [a02b9ca9] acm_probe+0x4d6/0xcb1 [cdc_acm] [11278.817849] RSP: 0018:88006cea1930 EFLAGS: 00010293 [11278.817851] RAX: RBX: 880052c08800 RCX: [11278.817853] RDX: RSI: 80d0 RDI: 8800376ea000 [11278.817856] RBP: 8800376e9000 R08: 000c R09: 880062ae9888 [11278.817858] R10: 80d000d0 R11: 000186a0 R12: 880062ae9888 [11278.817860] R13: 880052c08000 R14: R15: 880052c08000 [11278.817863] FS: 7f4dc9bf5910() GS:88000180() knlGS: [11278.817866] CS: 0010 DS: 0018 ES: 0018 CR0: 8005003b [11278.817868] CR2: 0004 CR3: 60157000 CR4: 06f0 [11278.817870] DR0: DR1: DR2: [11278.817873] DR3: DR6: 0ff0 DR7: 0400 [11278.817875] Process khubd (pid: 309, threadinfo 88006cea, task 88006cdff810) [11278.817877] Stack: [11278.817879] 813c7d84 88006f5329a0 810fcb34 [11278.817882] 0 880060130090 8113cebf 880052c08800 [11278.817886] 0 880062ae9840 88006013 [11278.817890] Call Trace: [11278.817897] [810fcb34] ? iput+0x27/0x60 [11278.817902] [8113cebf] ? sysfs_addrm_finish+0x66/0x204 [11278.817914] [a005975a] ? usb_match_one_id+0x23/0x7f [usbcore] [11278.817924] [a005a6dd] ? usb_probe_interface+0x107/0x157 [usbcore] [11278.817930] [8120e0e8] ? driver_probe_device+0xa3/0x14b [11278.817934] [8120e1ff] ? __device_attach+0x0/0x39 [11278.817937] [8120d713] ? bus_for_each_drv+0x46/0x77 [11278.817940] [8120e2bb] ? device_attach+0x60/0x7e [11278.817942] [8120d58b] ? bus_probe_device+0x1f/0x38 [11278.817948] [8120c258] ? device_add+0x3a2/0x537 [11278.817956] [a005942a] ? usb_set_configuration+0x589/0x5f2 [usbcore] [11278.817965] [a0060dac] ? generic_probe+0x61/0xa9 [usbcore] [11278.817969]
Bug#516968: closed by maximilian attems m...@stro.at (Re: SATA drive usage)
On Thu, Feb 04, 2010 at 05:34:15PM +0100, Marek Poks wrote: [...] /etc/rc.local is executed AFTER kernel spins-up the disk. i don't want to put disk to sleep every boot. it is already in 'start in sleep mode' but someway kernel spins-up the disk even if it is not to be mounted. this is kernel thing i think so, or sata_nv kernel module. normally, all disks are spinned-up in BIOS's post stage. but when disk has set option 'start in sleep mode' post stage skips the disk. the same kernel should do. [...] The kernel will scan the partition table for each disk. This is not a bug and we have no intention of changing it. Ben. -- Ben Hutchings In a hierarchy, every employee tends to rise to his level of incompetence. signature.asc Description: Digital signature
Bug#568317: linux-image-* postinst did not correctly run lilo
The linux-image postinst is known to be in bad shape but we are slowly cleaning it up. If you can provide patches, that would be most helpful. Ben. -- Ben Hutchings In a hierarchy, every employee tends to rise to his level of incompetence. signature.asc Description: Digital signature
Bug#568428: linux-source-2.6.32: Unable to use MagicPro ProTV DMB-TH usb Tuner (Conexant DMB-TH Stick)
On Fri, Feb 05, 2010 at 02:52:33AM +0800, H.W. Wan wrote: Package: linux-source-2.6.32 Version: 2.6.32-5 Severity: normal Without comment out the following line related to draining video/message, I'm not able to view/scan any channel for my tuner. [...] However i'm not sure if this will break other user. I expect that it will. The upstream developers may be able to find a proper fix, so please report this upstream at http://bugzilla.kernel.org (product 'v4l-dvb', component 'dvb-usb') and let us know the bug number. Ben. -- Ben Hutchings In a hierarchy, every employee tends to rise to his level of incompetence. signature.asc Description: Digital signature
Bug#568454: linux-source-2.6.32: fails to build vt6656
On Thu, Feb 04, 2010 at 08:58:30PM +0100, Michal Suchanek hramr...@centrum.cz wrote: Package: linux-source-2.6.32 Version: 2.6.32-6 Severity: normal I don't really care what vt6656 is but it breaks my build. I just recycled a config that worked for me with some earlier upstream kernel and it fails with the Debian one. [...] We remove the firmware from this driver, and since we don't build it in official kernel images we haven't yet made it use the firmware loader. Fixing up staging drivers is not a high priority for us; please just disable the driver. Ben. -- Ben Hutchings In a hierarchy, every employee tends to rise to his level of incompetence. signature.asc Description: Digital signature
Processed: severity of 568454 is minor
Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35lenny7 severity 568454 minor Bug #568454 [linux-source-2.6.32] linux-source-2.6.32: fails to build vt6656 Severity set to 'minor' from 'normal' End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#544692: linux-image-2.6.30-1-686: pcspeaker mute
On Wed, Sep 02, 2009 at 02:07:10PM +0200, Erwan David wrote: Package: linux-image-2.6.30-1-686 Version: 2.6.30-6 Severity: normal Since upgrading to 2.6.30, my pcspeaker is mute, instead beeps are sent to the soundcard which is a regeression since my sound card usually has no speaker, only a headphone from time to time. Hi, The next release of Debian (6.0, code name Squeeze) will be based on 2.6.32. Please test the current 2.6.32 from unstable/testing and tell us whether the problem persists. If so, we should report it upstream to the kernel.org developers. The 2.6.32 kernel is available from packages.debian.org and can be installed in both Debian stable, testing and unstable installations. Thanks, Moritz -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#544398: linux-image-2.6.30-1-686: skge driver fail
On Mon, Aug 31, 2009 at 01:04:23PM +0400, Vladimir Stavrinov wrote: Package: linux-image-2.6.30-1-686 Version: 2.6.30-6 Severity: normal The server working for a years without problems, one moment become unavailable on network. Investigation from local console show the system is working properly, except network. Any host is unavailable, but Ethernet interface is up and respond to local ping. More over, pull out and push in back the Ethernet cord end on the switch cause Link Down and Link UP respectively messages from the system. The hosts on the neighbor ports on the switch are seen on the network. After reboot the problem gone away. I have found the reason of this situation in the kernel.log: the message duplicated on console appeared at the moment when server become unavailable: Hi, The next release of Debian (6.0, code name Squeeze) will be based on 2.6.32. Please test the current 2.6.32 from unstable/testing and tell us whether the problem persists. If so, we should report it upstream to the kernel.org developers. The 2.6.32 kernel is available from packages.debian.org and can be installed in both Debian stable, testing and unstable installations. Thanks, Moritz -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#544524: Partially fixed in 2.6.31-1
On Wed, Nov 18, 2009 at 03:16:30AM +, Ben Hutchings wrote: On Mon, 2009-11-16 at 17:30 +0100, Simon Richter wrote: Hi, the memory leak has gone away in 2.6.31-1 (upstream commit bc146d23d1358af43f03793c3ad8c9f16bbcffcb), but the RAID issue probably still remains. Have you reported the remaining bug upstream? If not, please report it at http://bugzilla.kernel.org, and let us know the bug number. Simon, did you report it? If so, what's the bug number? Cheers, Moritz -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#539026: linux-image-2.6.30-1-686: agpgart module fails to initialize
On Tue, Jul 28, 2009 at 11:20:39AM -0400, Andres Salomon wrote: Package: linux-image-2.6.30-1-686 Version: 2.6.30-3 During boot, I see: [1.347047] Linux agpgart interface v0.103 [1.366133] [drm] Initialized drm 1.1.0 20060810 [1.378704] i915 :00:02.0: power state changed by ACPI to D0 [1.378719] i915 :00:02.0: PCI INT A - GSI 16 (level, low) - IRQ 16 [1.378726] i915 :00:02.0: setting latency timer to 64 [1.378745] [drm:drm_fill_in_dev] *ERROR* Cannot initialize the agpgart module. [1.378807] DRM: Fill_in_dev failed. [1.378862] i915 :00:02.0: PCI INT A disabled [1.378870] i915: probe of :00:02.0 failed with error -22 This is with the following /proc/cmdline: root=/dev/sda1 ro quiet And the following in /etc/initramfs-tools/modules: i915 modeset=1 This is problematic because it breaks KMS. Hi, Please test the current 2.6.32 from unstable/testing and tell us whether the problem persists. If so, we should report it upstream. Thanks, Moritz -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#347186: marked as done (linux-image-2.6.14-2-alpha-generic: garbled Matrox framebuffer)
Your message dated Fri, 5 Feb 2010 00:52:14 +0100 with message-id 20100204235214.ga6...@galadriel.inutil.org and subject line Re: [linux-2.6] more on bterm has caused the Debian Bug report #347186, regarding linux-image-2.6.14-2-alpha-generic: garbled Matrox framebuffer 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 ow...@bugs.debian.org immediately.) -- 347186: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=347186 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.14-7 Severity: important Sigh, can't get a break with alpha kernel support around here. After upgrading to 2.6.14 (from 2.4.27), the Matrox framebuffer no longer works correctly on my alpha with a Matrox Millenium II. The matroxfb_base module loads without error, but gives me corrupt video output only. Card info from lspci: :00:05.0 VGA compatible controller: Matrox Graphics, Inc. MGA 2164W [Millennium II] and lspci -n: :00:05.0 0300: 102b:051b dmesg output: matroxfb: Matrox Millennium II (PCI) detected PInS memtype = 0 matroxfb: 640x480x8bpp (virtual: 640x6553) matroxfb: framebuffer at 0x900, mapped to 0xfc880900, size 4194304 fb0: MATROX frame buffer device fb0: initializing hardware Happy to test potential driver fixes, though due to issues with *other* hardware in this system I didn't test the framebuffer with any previous 2.6 kernels and can't tell you whether it worked with them. Thanks, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. vor...@debian.org http://www.debian.org/ signature.asc Description: Digital signature ---End Message--- ---BeginMessage--- Gabriele Gorla wrote: --- Please enter the report below this line. --- I just swapped the millennium II with a ATI RAGE XL (atyfb module). bterm still (mis-)behaves exactly the same as with matroxfb. I start doubting the bterm problem is an issue with the matroxfb driver. As a side note, loading atyfb does not corrupt the screen even if the fbcon module is not loaded. The console stays in text mode until the fbcon module is loaded (with matroxfb the console goes in graphics mode immediately producing a garbled display until fbcon is loaded as well) Alpha is dropped from the set of release architectures for Squeeze. I'm closing this bug. Cheers, Moritz ---End Message---
Bug#568317: linux-image-* postinst did not correctly run lilo
Dear Ben, ... If you can provide patches, that would be most helpful. See below. I now see that the sources of these files are in package kernel-package (I do not know how that relates to linux-2.6). I only patched the spurious /g modifiers and cleaned up the patterns e.g. to anchor at the beginning; did not drop the unnecessary my(). Cheers, Paul Paul Szabo p...@maths.usyd.edu.au http://www.maths.usyd.edu.au/u/psz/ School of Mathematics and Statistics University of SydneyAustralia --- usr/share/kernel-package/pkg/headers/postinst.bak 2008-05-02 15:06:28.0 +1000 +++ usr/share/kernel-package/pkg/headers/postinst 2010-02-05 10:30:23.0 +1100 @@ -146,8 +146,8 @@ s/\#.*$//g; next if /^\s*$/; - $src_postinst_hook = $1 if /src_postinst_hook\s*=\s*(\S+)/ig; - $header_postinst_hook = $1 if /header_postinst_hook\s*=\s*(\S+)/ig; + $src_postinst_hook = $1 if m/^\s*src_postinst_hook\s*=\s*(\S+)\s*$/i; + $header_postinst_hook = $1 if m/^\s*header_postinst_hook\s*=\s*(\S+)\s*$/i; } close CONF; $have_conffile = Yes; --- usr/share/kernel-package/pkg/source/postinst.bak2008-05-02 15:06:28.0 +1000 +++ usr/share/kernel-package/pkg/source/postinst2010-02-05 10:31:06.0 +1100 @@ -57,7 +57,7 @@ s/\#.*$//g; next if /^\s*$/; - $src_postinst_hook = $1 if /src_postinst_hook\s*=\s*(\S+)/ig; + $src_postinst_hook = $1 if m/^\s*src_postinst_hook\s*=\s*(\S+)\s*$/i; } close CONF; $have_conffile = Yes; --- usr/share/kernel-package/pkg/doc/postinst.bak 2008-05-02 15:06:28.0 +1000 +++ usr/share/kernel-package/pkg/doc/postinst 2010-02-05 10:31:51.0 +1100 @@ -57,7 +57,7 @@ s/\#.*$//g; next if /^\s*$/; - $src_postinst_hook = $1 if /src_postinst_hook\s*=\s*(\S+)/ig; + $src_postinst_hook = $1 if m/^\s*src_postinst_hook\s*=\s*(\S+)\s*$/i; } close CONF; $have_conffile = Yes; --- usr/share/kernel-package/pkg/image/postinst.bak 2008-11-25 04:01:32.0 +1100 +++ usr/share/kernel-package/pkg/image/postinst 2010-02-05 10:43:59.0 +1100 @@ -116,60 +116,60 @@ warn Option image_in_boot is deprecated, and will go away. Use link_in_boot instead.\n if m/image_in_boot\s*=\s*/; - $do_symlink = if /do_symlinks\s*=\s*(no|false|0)\s*$/ig; - $no_symlink = if /no_symlinks\s*=\s*(no|false|0)\s*$/ig; - $reverse_symlink = if /reverse_symlink\s*=\s*(no|false|0)\s*$/ig; - $link_in_boot= if /link_in_boot\s*=\s*(no|false|0)\s*$/ig; - $link_in_boot= if /image_in_boot\s*=\s*(no|false|0)\s*$/ig; - $move_image = if /move_image\s*=\s*(no|false|0)\s*$/ig; - $clobber_modules = '' if /clobber_modules\s*=\s*(no|false|0)\s*$/ig; - $do_boot_enable = '' if /do_boot_enable\s*=\s*(no|false|0)\s*$/ig; - $do_bootfloppy = '' if /do_bootfloppy\s*=\s*(no|false|0)\s*$/ig; - $relative_links = '' if /relative_links \s*=\s*(no|false|0)\s*$/ig; - $do_bootloader = '' if /do_bootloader\s*=\s*(no|false|0)\s*$/ig; - $do_initrd = '' if /do_initrd\s*=\s*(no|false|0)\s*$/ig; - $warn_initrd = '' if /warn_initrd\s*=\s*(no|false|0)\s*$/ig; - $use_hard_links = '' if /use_hard_links\s*=\s*(no|false|0)\s*$/ig; - $silent_modules = '' if /silent_modules\s*=\s*(no|false|0)\s*$/ig; - $silent_loader = '' if /silent_loader\s*=\s*(no|false|0)\s*$/ig; - $warn_reboot = '' if /warn_reboot\s*=\s*(no|false|0)\s*$/ig; - $minimal_swap= '' if /minimal_swap\s*=\s*(no|false|0)\s*$/ig; - $ignore_depmod_err = '' if /ignore_depmod_err\s*=\s*(no|false|0)\s*$/ig; - $relink_src_link = '' if /relink_src_link\s*=\s*(no|false|0)\s*$/ig; - $relink_build_link = '' if /relink_build_link\s*=\s*(no|false|0)\s*$/ig; - $force_build_link = '' if /force_build_link\s*=\s*(no|false|0)\s*$/ig; - - $do_symlink = Yes if /do_symlinks\s*=\s*(yes|true|1)\s*$/ig; - $no_symlink = Yes if /no_symlinks\s*=\s*(yes|true|1)\s*$/ig; - $reverse_symlink = Yes if /reverse_symlinks\s*=\s*(yes|true|1)\s*$/ig; - $link_in_boot= Yes if /link_in_boot\s*=\s*(yes|true|1)\s*$/ig; - $link_in_boot= Yes if /image_in_boot\s*=\s*(yes|true|1)\s*$/ig; - $move_image = Yes if /move_image\s*=\s*(yes|true|1)\s*$/ig; - $clobber_modules = Yes if /clobber_modules\s*=\s*(yes|true|1)\s*$/ig; - $do_boot_enable = Yes if /do_boot_enable\s*=\s*(yes|true|1)\s*$/ig; - $do_bootfloppy = Yes if /do_bootfloppy\s*=\s*(yes|true|1)\s*$/ig; - $do_bootloader = Yes if /do_bootloader\s*=\s*(yes|true|1)\s*$/ig; - $explicit_do_loader = YES if /do_bootloader\s*=\s*(yes|true|1)\s*$/ig; - $relative_links = Yes if /relative_links\s*=\s*(yes|true|1)\s*$/ig; - $do_initrd = Yes if /do_initrd\s*=\s*(yes|true|1)\s*$/ig; - $warn_initrd = Yes if
Bug#568317: linux-image-* postinst did not correctly run lilo
On Fri, Feb 05, 2010 at 10:54:33AM +1100, paul.sz...@sydney.edu.au wrote: Dear Ben, ... If you can provide patches, that would be most helpful. See below. I now see that the sources of these files are in package kernel-package (I do not know how that relates to linux-2.6). I only patched the spurious /g modifiers and cleaned up the patterns e.g. to anchor at the beginning; did not drop the unnecessary my(). [...] kernel-package has an old version of the script templates. The templates used by linux-2.6 are in debian/templates/temp.image.plain. Ben. -- Ben Hutchings In a hierarchy, every employee tends to rise to his level of incompetence. signature.asc Description: Digital signature
Bug#562486: please enable tomoyo
On Feb 05, Moritz Muehlenhoff j...@inutil.org wrote: OTOH enabling it for Squeeze doesn't make much sense if we don't yet have compatible user space tools. It would still make sense (if the current kernel really has all the features needed) because backporting and keeping up to date any userspace package is much easier than backporting (or just rebuilding with a different configuration) a Debian kernel package. -- ciao, Marco signature.asc Description: Digital signature
Re: Debian 2.6.32 CONFIG_WIRELESS_OLD_REGULATORY, wireless-regdb and crda
On Thu, Feb 4, 2010 at 6:03 AM, Kel Modderman k...@otaku42.de wrote: On Thursday 04 February 2010 11:42:33 Luis R. Rodriguez wrote: On Mon, Feb 1, 2010 at 6:10 PM, Paul Wise p...@debian.org wrote: On Mon, 2010-02-01 at 09:58 -0800, Luis R. Rodriguez wrote: I can help with this only if no one else is up for it. I personally however find building a key on the fly for each build pretty pointless and would like to know if a package would be acceptable upstream on Debian if OpenSSL is used to allow administrators to add their own keys into the /etc/wireless-regdb/pubkeys/ dir for CRDA and from the start only trust John's key. As part of upstream, you're probably the best person to do the packaging stuff for Debian. OK, in that case here is my first shot at this. http://wireless.kernel.org/download/wireless-regdb/debs/ http://wireless.kernel.org/download/crda/debs/ Tim -- notice both packages have a Replaces: wireless-crda. If debian upstreams both packages then I think it would be good to separate the packages as I am recommending for integration on Debian and for Ubuntu to also use the same debian packages as debian. I think this would mean also having the new Ubuntu kernels depend on these new packages instead of the old wireless-crda. The package is very simple, I took what I could from Kel's work but did leave in the signature check stuff, used openssl and also just used cdbs. The wireless-regdb does not change *that* often so I do not expect debian itself to need a custom regulatory database to be automatically built and propagated so I left all the watch stuff out and can do manual updates for now, I can commit to that for now. If that is a requirement however, I am not that familiar with new package policies and am unclear how to do that. I would prefer if we can get something started and uploaded for now which at least meets the requirements for integration into an eventual stable release, but that's just me. Please review and let me know what you think. These demonstrate that most of what I've attempted to explain about the difficulties of getting this software into the Debian software pool in a maintainable form has been taken lightly. To reiterate what I think is most important: The software should be built from its preferable form of modification to produce the resulting binary. What's the point? This helps to make the source package available to other developers to modify and rebuild without invasive packaging changes. The source will always be available and users can themselves apt-get source wireless-regdb and compile their own regdb at any time, just as with CRDA. An alternative approach: http://sidux.net/kelmo/sidux/crap/crda/crda_1.1.1-1.dsc I think I must just suck at packaging modern debian packages, can you elaborate a little on what this adds, I can't tell. Also, it seems that the REGDB_CHANGED stuff in wireless-regdb/Makefile does not work as expected - the sha1sum.txt file possibly contains the hash from an old db.txt Yeah, John -- can you please run: sha1sum db.txt sha1sum.txt and commit that? Maybe there is a way to add it as a hook to git commit? Luis -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Debian 2.6.32 CONFIG_WIRELESS_OLD_REGULATORY, wireless-regdb and crda
On Thu, Feb 04, 2010 at 04:25:53PM -0800, Luis R. Rodriguez wrote: Also, it seems that the REGDB_CHANGED stuff in wireless-regdb/Makefile does not work as expected - the sha1sum.txt file possibly contains the hash from an old db.txt Yeah, John -- can you please run: sha1sum db.txt sha1sum.txt and commit that? Maybe there is a way to add it as a hook to git commit? I can just put it into the Makefile. Anyway, what is REGDB_CHANGED supposed to be doing? -- John W. LinvilleSomeday the world will need a hero, and you linvi...@tuxdriver.com might be all we have. Be ready. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#568317: linux-image-* postinst did not correctly run lilo
Dear Ben, kernel-package has an old version of the script templates. The templates used by linux-2.6 are in debian/templates/temp.image.plain. Where do I find that? I am using (working, building on) Debian lenny, building from linux-source-2.6.26-21.tar.bz2 . (Anyway, are not my suggested changes simple enough so you do not need actual patch files?) Thanks, Paul Paul Szabo p...@maths.usyd.edu.au http://www.maths.usyd.edu.au/u/psz/ School of Mathematics and Statistics University of SydneyAustralia -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Debian 2.6.32 CONFIG_WIRELESS_OLD_REGULATORY, wireless-regdb and crda
On Thu, Feb 4, 2010 at 4:43 PM, John W. Linville linvi...@tuxdriver.com wrote: On Thu, Feb 04, 2010 at 04:25:53PM -0800, Luis R. Rodriguez wrote: Also, it seems that the REGDB_CHANGED stuff in wireless-regdb/Makefile does not work as expected - the sha1sum.txt file possibly contains the hash from an old db.txt Yeah, John -- can you please run: sha1sum db.txt sha1sum.txt and commit that? Maybe there is a way to add it as a hook to git commit? I can just put it into the Makefile. Anyway, what is REGDB_CHANGED supposed to be doing? It detects to see if you have edited db.txt and if so, it should build your own key and stuff. Luis -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#539026: marked as done (linux-image-2.6.30-1-686: agpgart module fails to initialize)
Your message dated Fri, 5 Feb 2010 01:27:57 -0500 with message-id 20100205012757.15313...@mycelium.queued.net and subject line Re: linux-image-2.6.30-1-686: agpgart module fails to initialize has caused the Debian Bug report #539026, regarding linux-image-2.6.30-1-686: agpgart module fails to initialize 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 ow...@bugs.debian.org immediately.) -- 539026: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=539026 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.30-1-686 Version: 2.6.30-3 During boot, I see: [1.347047] Linux agpgart interface v0.103 [1.366133] [drm] Initialized drm 1.1.0 20060810 [1.378704] i915 :00:02.0: power state changed by ACPI to D0 [1.378719] i915 :00:02.0: PCI INT A - GSI 16 (level, low) - IRQ 16 [1.378726] i915 :00:02.0: setting latency timer to 64 [1.378745] [drm:drm_fill_in_dev] *ERROR* Cannot initialize the agpgart module. [1.378807] DRM: Fill_in_dev failed. [1.378862] i915 :00:02.0: PCI INT A disabled [1.378870] i915: probe of :00:02.0 failed with error -22 This is with the following /proc/cmdline: root=/dev/sda1 ro quiet And the following in /etc/initramfs-tools/modules: i915 modeset=1 This is problematic because it breaks KMS. ---End Message--- ---BeginMessage--- Hi, Thanks, KMS on 2.6.32 works on my x200s. Closing this.. ---End Message---
Processed: tagging as pending bugs that are closed by packages in NEW
Processing commands for cont...@bugs.debian.org:
# Fri Feb 5 07:03:17 UTC 2010
# Tagging as pending bugs that are closed by packages in NEW
# http://ftp-master.debian.org/new.html
#
# Source package in NEW: libtap-formatter-junit-perl
tags 568265 + pending
Bug #568265 [wnpp] ITP: libtap-formatter-junit-perl -- Perl module for
converting TAP output to JUnit output
Added tag(s) pending.
# Source package in NEW: mono-uia-winforms
tags 550107 + pending
Bug #550107 [libmono-uia-winforms1.0-cil] libmono-uia-winforms1.0-cil: long
description no sentence
Added tag(s) pending.
# Source package in NEW: linux-2.6
tags 568025 + pending
Bug #568025 {Done: dann frazier da...@debian.org} [linux-2.6] FTBFS on sparc
Added tag(s) pending.
# Source package in NEW: linux-2.6
tags 568030 + pending
Bug #568030 {Done: dann frazier da...@debian.org} [linux-2.6] FTBFS on armel
(and maybe others)
Added tag(s) pending.
End of message, stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
