Processed: severity of 526406 is important
Processing commands for cont...@bugs.debian.org: > severity 526406 important Bug#526406: linux-image-2.6.29-1-amd64: Kernel BUG 2.6.29 + cpufreq on heavy load Severity set to `important' from `critical' > 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#464197: Any update on this issue?
Antonio Ospite writes: > can the latest version of your code be found in this thread? Yes, the version I posted on 2008-04-06 is the latest one. When building a local linux-2.6 2.6.26-9.kon.1 version, I put the patch at debian/patches/debian/dfsg/sound-pci-cs46xx.patch and added it to the list in debian/patches/series/1. Currently, my primary problem with this patch is that the cs46xx module gets inserted before /usr is mounted, and it then doesn't receive the firmware from userspace and fails to initialize the device. From the source, it appears that snd_card_cs46xx_probe returns -EIO in this situation. To get sound after this, I have to rmmod and insmod cs46xx again, or do: printf ":00:0d.0" > "/sys/module/snd_cs46xx/drivers/pci:Sound Fusion CS46xx/bind" The hexadecimal numbers depend on the PCI slot, I guess. pgpkHbJ5zqRCF.pgp Description: PGP signature
Bug#464197: Any update on this issue?
On Fri, 01 May 2009 11:16:58 +0300 Kalle Olavi Niemitalo wrote: > Antonio Ospite writes: > > > can the latest version of your code be found in this thread? > > Yes, the version I posted on 2008-04-06 is the latest one. When > building a local linux-2.6 2.6.26-9.kon.1 version, I put the > patch at debian/patches/debian/dfsg/sound-pci-cs46xx.patch and > added it to the list in debian/patches/series/1. > OK, thanks. About the SND_CS46XX_NEW_DSP issue, from a first glance to the driver it looks like that in order to support it we have to make a binary image for any file in the imgs/ dir. Does this look ok to you? > Currently, my primary problem with this patch is that the cs46xx > module gets inserted before /usr is mounted, and it then doesn't > receive the firmware from userspace and fails to initialize the > device. From the source, it appears that snd_card_cs46xx_probe > returns -EIO in this situation. To get sound after this, I have > to rmmod and insmod cs46xx again, or do: > > printf ":00:0d.0" > "/sys/module/snd_cs46xx/drivers/pci:Sound Fusion > CS46xx/bind" > > The hexadecimal numbers depend on the PCI slot, I guess. > >From what I know the proper solution should be to add the firmware images to an initrd image. I'll let you know the results of my tests. Regards, Antonio -- A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? Web site: http://www.studenti.unina.it/~ospite Public key: http://www.studenti.unina.it/~ospite/aopubkey.asc pgp9XI4QEVOQY.pgp Description: PGP signature
Bug#464197: Any update on this issue?
Antonio Ospite writes: > About the SND_CS46XX_NEW_DSP issue, from a first glance to > the driver it looks like that in order to support it we have to make a > binary image for any file in the imgs/ dir. Does this look ok to you? I guess that's what needs to be done. The difficulty is with pointers in struct dsp_segment_desc and struct dsp_module_desc. You'll have to replace those with integers (presumably file offsets) and concatenate the structures in the binary file while ensuring proper alignment. It seems quite doable but I don't need the SND_CS46XX_NEW_DSP features myself and cannot test them. > From what I know the proper solution should be to add the firmware > images to an initrd image. I'll let you know the results of my tests. In the patch, I added a MODULE_FIRMWARE line that should make it possible for initrd-building scripts to include the firmware. However, in the 2.6.26 initrd image I have here, the snd-cs46xx.ko module itself is not included; presumably because the driver isn't needed for booting. So I think it would be pointless to include the firmware there. pgpINghydWr8v.pgp Description: PGP signature
Bug#526065: 526065: kvm load problems is a BIOS issue
After enabling hardware virtualization in the BIOS, the kvm-intel module loads. I'll close this, since the driver was working OK. -- Ross Boylan wk: (415) 514-8146 185 Berry St #5700 r...@biostat.ucsf.edu Dept of Epidemiology and Biostatistics fax: (415) 514-8150 University of California, San Francisco San Francisco, CA 94107-1739 hm: (415) 550-1062 -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#526065: marked as done (linux-image-2.6.29-trunk-amd64: kvm-intel won't load in 2.6.29)
Your message dated Fri, 01 May 2009 10:21:20 -0700 with message-id <1241198480.14425.5.ca...@iron.psg.net> and subject line Re: 526065: closing kvm load problems has caused the Debian Bug report #526065, regarding linux-image-2.6.29-trunk-amd64: kvm-intel won't load in 2.6.29 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.) -- 526065: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=526065 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-image-2.6.29-trunk-amd64 Version: 2.6.29-1~experimental.2~snapshot.13314 Severity: normal *** Please type your report below this line *** markov:~# modprobe -v kvm-intel insmod /lib/modules/2.6.29-trunk-amd64/kernel/arch/x86/kvm/kvm-intel.ko FATAL: Error inserting kvm_intel (/lib/modules/2.6.29-trunk-amd64/kernel/arch/x86/kvm/kvm-intel.ko): Operation not supported markov:~# uname -a Linux markov 2.6.29-trunk-amd64 #1 SMP Fri Apr 3 00:43:29 UTC 2009 x86_64 GNU/Linux This appears to render kvm unusable for me, though I am not sure how it is supposed to work. m-a also won't build modules from kvm-source, though I'm not sure that should be necessary with recent kernels such as 2.6.29. The compilation needed some files which were in headers-common rather than headers-amd64. I have both installed, but they are in different directories. The machine has 2 Xeon CPU's with 8 cores each. They have Intel-VT. -- Package-specific info: ** Version: Linux version 2.6.29-trunk-amd64 (Debian 2.6.29-1~experimental.2~snapshot.13314) (wa...@debian.org) (gcc version 4.3.3 (GCC) ) #1 SMP Fri Apr 3 00:43:29 UTC 2009 ** Command line: root=/dev/mapper/turtle-root ro quiet vga=0x376 ** Not tainted ** Kernel log: [ 10.118882] coretemp coretemp.7: Using relative temperature scale! [ 87.129658] kjournald starting. Commit interval 5 seconds [ 87.144523] EXT3 FS on md0, internal journal [ 87.144963] EXT3-fs: mounted filesystem with ordered data mode. [ 87.205138] kjournald starting. Commit interval 5 seconds [ 87.208686] EXT3 FS on dm-8, internal journal [ 87.209143] EXT3-fs: mounted filesystem with ordered data mode. [ 87.258305] kjournald starting. Commit interval 5 seconds [ 87.264348] EXT3 FS on dm-9, internal journal [ 87.264798] EXT3-fs: mounted filesystem with ordered data mode. [ 87.291022] kjournald starting. Commit interval 5 seconds [ 87.294714] EXT3 FS on dm-2, internal journal [ 87.295165] EXT3-fs: mounted filesystem with ordered data mode. [ 87.314955] kjournald starting. Commit interval 5 seconds [ 87.315645] EXT3 FS on dm-3, internal journal [ 87.316094] EXT3-fs: mounted filesystem with ordered data mode. [ 87.374562] kjournald starting. Commit interval 5 seconds [ 87.380682] EXT3 FS on dm-10, internal journal [ 87.381143] EXT3-fs: mounted filesystem with ordered data mode. [ 87.486275] Adding 1951888k swap on /dev/mapper/sda2_crypt. Priority:-1 extents:1 across:1951888k [ 87.525014] Adding 1951888k swap on /dev/mapper/sdb2_crypt. Priority:-2 extents:1 across:1951888k [ 88.773097] e1000e :07:00.0: irq 31 for MSI/MSI-X [ 88.828826] e1000e :07:00.0: irq 31 for MSI/MSI-X [ 91.332917] e1000e: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None [ 95.734226] NET: Registered protocol family 10 [ 95.769534] lo: Disabled Privacy Extensions [ 96.493106] lp: driver loaded but no devices found [ 96.544569] ppdev: user-space parallel port driver [ 99.957349] e1000e :06:00.0: irq 30 for MSI/MSI-X [ 100.008078] e1000e :06:00.0: irq 30 for MSI/MSI-X [ 100.010951] ADDRCONF(NETDEV_UP): eth0: link is not ready [ 101.429405] [drm] Initialized drm 1.1.0 20060810 [ 101.434533] pci :03:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 [ 101.434539] pci :03:00.0: setting latency timer to 64 [ 101.434668] [drm] Initialized radeon 1.29.0 20080528 on minor 0 [ 101.434876] mtrr: type mismatch for d000,1000 old: write-back new: write-combining [ 101.620904] mtrr: type mismatch for d000,1000 old: write-back new: write-combining [ 101.634869] mtrr: type mismatch for d000,1000 old: write-back new: write-combining [ 101.634917] mtrr: type mismatch for d000,1000 old: write-back new: write-combining [ 101.634954] mtrr: type mismatch for d000,1000 old: write-back new: write-combining [ 101.659208] [drm] Setting GART location based on new memory map [ 101.662516] [drm] Loading R500 Microcode [ 101.662519] platform radeon_cp.0: firmware: requesting radeon/R520_cp.bin [ 101.725044] radeon_cp: Failed to load firmware "
Bug#526525: Kernel linux-image-2.6.26-2-amd64 does not see root RAID device /dev/md0
Package: linux-image-2.6.26-2-amd64 Version: 2.6.26-15 Severity: important Kernel from linux-image-2.6.26-2-amd64 does not see root RAID device /dev/md0 so boot sequence drops busybox shell. 2.6.26-2-686-bigmem and 2.6.26-2-686 work properly. This is after an install with no issues from the std 32-bit install iso image. Machine is a Dell T610 server with 8 GB RAM and 8 cores (two four-core Xeons, I think) -- Package-specific info: -- System Information: Debian Release: 5.0.1 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.26-2-686-bigmem (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages linux-image-2.6.26-2-amd64 depends on: ii debconf [debconf-2.0] 1.5.24 Debian configuration management sy ii initramfs-tools [linux-initra 0.92o tools for generating an initramfs ii module-init-tools 3.4-1 tools for managing Linux kernel mo linux-image-2.6.26-2-amd64 recommends no packages. Versions of packages linux-image-2.6.26-2-amd64 suggests: ii grub 0.97-47lenny2 GRand Unified Bootloader (Legacy v pn linux-doc-2.6.26 (no description available) -- debconf information: shared/kernel-image/really-run-bootloader: true linux-image-2.6.26-2-amd64/postinst/bootloader-error-2.6.26-2-amd64: linux-image-2.6.26-2-amd64/preinst/lilo-initrd-2.6.26-2-amd64: true linux-image-2.6.26-2-amd64/postinst/depmod-error-2.6.26-2-amd64: false linux-image-2.6.26-2-amd64/postinst/old-dir-initrd-link-2.6.26-2-amd64: true linux-image-2.6.26-2-amd64/postinst/create-kimage-link-2.6.26-2-amd64: true linux-image-2.6.26-2-amd64/preinst/initrd-2.6.26-2-amd64: linux-image-2.6.26-2-amd64/preinst/lilo-has-ramdisk: linux-image-2.6.26-2-amd64/preinst/abort-install-2.6.26-2-amd64: linux-image-2.6.26-2-amd64/postinst/old-initrd-link-2.6.26-2-amd64: true linux-image-2.6.26-2-amd64/postinst/depmod-error-initrd-2.6.26-2-amd64: false linux-image-2.6.26-2-amd64/postinst/bootloader-test-error-2.6.26-2-amd64: linux-image-2.6.26-2-amd64/preinst/overwriting-modules-2.6.26-2-amd64: true linux-image-2.6.26-2-amd64/postinst/kimage-is-a-directory: linux-image-2.6.26-2-amd64/preinst/failed-to-move-modules-2.6.26-2-amd64: linux-image-2.6.26-2-amd64/prerm/would-invalidate-boot-loader-2.6.26-2-amd64: true linux-image-2.6.26-2-amd64/postinst/old-system-map-link-2.6.26-2-amd64: true linux-image-2.6.26-2-amd64/preinst/abort-overwrite-2.6.26-2-amd64: linux-image-2.6.26-2-amd64/preinst/bootloader-initrd-2.6.26-2-amd64: true linux-image-2.6.26-2-amd64/preinst/elilo-initrd-2.6.26-2-amd64: true linux-image-2.6.26-2-amd64/prerm/removing-running-kernel-2.6.26-2-amd64: true Best Regards. Please keep in touch. This is unedited. P-) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#526519: marked as done (cmake immediately hangs if run in i386 chroot on amd64 host)
Your message dated Fri, 1 May 2009 22:50:23 +0300 with message-id <200905012250.29607.modes...@vainius.eu> and subject line Re: Bug#526519: cmake immediately hangs if run in i386 chroot on amd64 host has caused the Debian Bug report #526519, regarding cmake immediately hangs if run in i386 chroot on amd64 host 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.) -- 526519: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=526519 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: cmake Version: 2.6.3-2 Severity: normal If i use cmake in an i386 chroot on an amd64 machine, it just prints "Linux" and hangs. The same happens inside an i386 pbuilder environment on an amd64 machine (therefore I think this problem is not caused by a dirty chroot). How to reproduce: - create i386 chroot on amd64 machine - touch CMakeLists.txt - cmake . Running a debug version of cmake (built on another, real i386 machine) inside gdb and pressing Ctrl-C after "Linux" has been printed gives #0 0xf7ced04e in read () from /lib/libc.so.6 #1 0xf7c9505e in _IO_file_underflow () from /lib/libc.so.6 #2 0xf7c969cb in _IO_default_uflow () from /lib/libc.so.6 #3 0xf7c97de8 in __uflow () from /lib/libc.so.6 #4 0xf7c8ad07 in _IO_getline_info () from /lib/libc.so.6 #5 0xf7c8ac51 in _IO_getline () from /lib/libc.so.6 #6 0xf7c89b2a in fgets () from /lib/libc.so.6 #7 0x080f6402 in RunCommandViaPopen (command=0x847e14c "uname -s ", dir=0x0, outp...@0xffd35740, retv...@0xffd35744, verbose=false) at /mnt/debian/packages/cmake/cmake-2.6.3/Source/cmSystemTools.cxx:936 #8 0x08147193 in cmExecProgramCommand::InitialPass (this=0x847e8e0, ar...@0xffd35784) at /mnt/debian/packages/cmake/cmake-2.6.3/Source/cmExecProgramCommand.cxx:117 #9 0x0816ea70 in cmCommand::InvokeInitialPass (this=0x847e8e0, ar...@0x847fe84, stat...@0xffd358ec) at /mnt/debian/packages/cmake/cmake-2.6.3/Source/cmCommand.h:73 #10 0x080cb2b3 in cmMakefile::ExecuteCommand (this=0x8477ed0, l...@0x847fe78, stat...@0xffd358ec) at /mnt/debian/packages/cmake/cmake-2.6.3/Source/cmMakefile.cxx:399 #11 0x08152ed3 in cmIfFunctionBlocker::IsFunctionBlocked (this=0x8484230, l...@0x847ec78, m...@0x8477ed0, instat...@0xffd35a9c) at /mnt/debian/packages/cmake/cmake-2.6.3/Source/cmIfCommand.cxx:119 #12 0x080c34c3 in cmMakefile::IsFunctionBlocked (this=0x8477ed0, l...@0x847ec78, stat...@0xffd35a9c) at /mnt/debian/packages/cmake/cmake-2.6.3/Source/cmMakefile.cxx:2454 #13 0x080cb03a in cmMakefile::ExecuteCommand (this=0x8477ed0, l...@0x847ec78, stat...@0xffd35a9c) at /mnt/debian/packages/cmake/cmake-2.6.3/Source/cmMakefile.cxx:360 #14 0x08152ed3 in cmIfFunctionBlocker::IsFunctionBlocked (this=0x847ab20, l...@0x84857b8, m...@0x8477ed0, instat...@0xffd35c48) at /mnt/debian/packages/cmake/cmake-2.6.3/Source/cmIfCommand.cxx:119 #15 0x080c34c3 in cmMakefile::IsFunctionBlocked (this=0x8477ed0, l...@0x84857b8, stat...@0xffd35c48) at /mnt/debian/packages/cmake/cmake-2.6.3/Source/cmMakefile.cxx:2454 #16 0x080cb03a in cmMakefile::ExecuteCommand (this=0x8477ed0, l...@0x84857b8, stat...@0xffd35c48) at /mnt/debian/packages/cmake/cmake-2.6.3/Source/cmMakefile.cxx:360 #17 0x080d6815 in cmMakefile::ReadListFile (this=0x8477ed0, filename_in=0x0, external_in=0x847a184 "/usr/share/cmake-2.6/Modules/CMakeDetermineSystem.cmake", fullPath=0x0, noPolicyScope=) at /mnt/debian/packages/cmake/cmake-2.6.3/Source/cmMakefile.cxx:670 #18 0x081c5247 in cmGlobalGenerator::EnableLanguage (this=0x84779c8, languag...@0xffd35f6c, mf=0x8477ed0) at /mnt/debian/packages/cmake/cmake-2.6.3/Source/cmGlobalGenerator.cxx:262 #19 0x081cf120 in cmGlobalUnixMakefileGenerator3::EnableLanguage (this=0x84779c8, languag...@0xffd35f6c, mf=0x8477ed0, optional=) at /mnt/debian/packages/cmake/cmake-2.6.3/Source/cmGlobalUnixMakefileGenerator3.cxx:46 #20 0x080c82ca in cmMakefile::EnableLanguage (this=0x8477ed0, la...@0xffd35f6c, optional=false) at /mnt/debian/packages/cmake/cmake-2.6.3/Source/cmMakefile.cxx:2705 #21 0x08141795 in cmProjectCommand::InitialPass (this=0x8479a38, ar...@0xffd35fb4) at /mnt/debian/packages/cmake/cmake-2.6.3/Source/cmProjectCommand.cxx:76 #22 0x0816ea70 in cmCommand::InvokeInitialPass (this=0x8479a38, ar...@0x8479a24, stat...@0xffd36118) at /mnt/debian/packages/cmake/cmake-2.6.3/Source/cmCommand.h:73 #23 0x080cb2b3 in cmMakefile::ExecuteCommand (this=0x8477ed0, l...@0x8479a18, stat...@0xffd36118) at /mnt/debian/packages/cmake/cmake-2.6.3/Source/cmMakefile.cxx:399 #24 0x080d6815 in cmMakefile::Re
Processed (with 1 errors): Re: Bug#526519: cmake immediately hangs if run in i386 chroot on amd64 host
Processing commands for cont...@bugs.debian.org: > Version: 2.6.26-14 Unknown command or malformed arguments to command. > reassign 526519 linux-image-2.6.26-1-amd64 2.6.26-13 Bug#526519: cmake immediately hangs if run in i386 chroot on amd64 host Bug reassigned from package `cmake' to `linux-image-2.6.26-1-amd64'. > fixed 526519 2.6.26-14 Bug#526519: cmake immediately hangs if run in i386 chroot on amd64 host Bug marked as fixed in version 2.6.26-14. > forcemerge 518921 526519 Bug number 518921 not found. (Is it archived?) > 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
Processed: unarchiving 518921, forcibly merging 518921 526519, archiving 518921
Processing commands for cont...@bugs.debian.org: > unarchive 518921 Bug 518921 [linux-image-2.6.26-1-amd64] i386 missing syscall detection is broken on amd64 Bug 521863 [linux-image-2.6.26-1-amd64] popen broken on some systems Unarchived Bug 518921 Unarchived Bug 521863 > forcemerge 518921 526519 Bug#518921: i386 missing syscall detection is broken on amd64 Bug#526519: cmake immediately hangs if run in i386 chroot on amd64 host Bug#521863: popen broken on some systems Forcibly Merged 518921 521863 526519. > archive 518921 Bug 518921 [linux-image-2.6.26-1-amd64] i386 missing syscall detection is broken on amd64 Bug 521863 [linux-image-2.6.26-1-amd64] popen broken on some systems Bug 526519 [linux-image-2.6.26-1-amd64] cmake immediately hangs if run in i386 chroot on amd64 host archived 518921 to archive/21 (from 518921) deleted 518921 (from 518921) archived 521863 to archive/63 (from 518921) deleted 521863 (from 518921) archived 526519 to archive/19 (from 518921) deleted 526519 (from 518921) > 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#526542: initramfs-tools: fails if swap is encrypted and LVM is used
Package: initramfs-tools Version: 0.92o Severity: important Use LVM and have a swap an encrypted partition. Then suspend to disk. Then try to resume now all those nasty "no sed", "no tr" errors during boot (before the passphrase prompt) will kick into effect, and your system will boot normally, instead of resuming. Also, there is a useless prompt where the computer asks at every boot to identify the swap, even though the correct path in the LVM is on the prompt (but says that that's not good). Once the sed and tr are in the generated iniramfs, all is OK. -- Package-specific info: -- /proc/cmdline root=/dev/hda2 ro quiet -- /proc/filesystems ext3 -- lsmod Module Size Used by i915 25856 2 drm66120 3 i915 binfmt_misc 7336 1 ppdev 6500 0 parport_pc 27576 0 lp 8140 0 parport30964 3 ppdev,parport_pc,lp acpi_cpufreq6636 1 cpufreq_conservative 5896 0 cpufreq_userspace 3204 0 cpufreq_stats 3844 0 cpufreq_powersave 1824 0 microcode 8336 0 nfsd 187644 17 auth_rpcgss31048 1 nfsd exportfs4000 1 nfsd nfs 217432 0 lockd 54040 2 nfsd,nfs nfs_acl 2880 2 nfsd,nfs sunrpc163156 13 nfsd,auth_rpcgss,nfs,lockd,nfs_acl ipv6 210372 22 loop 13164 0 snd_hda_intel 323540 1 snd_pcm_oss32096 0 snd_mixer_oss 12256 1 snd_pcm_oss snd_pcm62788 2 snd_hda_intel,snd_pcm_oss arc41824 2 ecb 2624 2 snd_seq_dummy 2660 0 snd_seq_oss24636 0 iwlagn 76676 0 snd_seq_midi5760 0 iwlcore74724 1 iwlagn pcmcia 29940 0 snd_rawmidi18688 1 snd_seq_midi snd_seq_midi_event 6368 2 snd_seq_oss,snd_seq_midi psmouse32016 0 led_class 3876 1 iwlcore rtc_cmos8704 0 snd_seq41576 6 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event firmware_class 6888 3 microcode,iwlagn,pcmcia rtc_core 13948 1 rtc_cmos i2c_i8018112 0 mac80211 114864 2 iwlagn,iwlcore rtc_lib 2848 1 rtc_core yenta_socket 20780 1 rsrc_nonstatic 9344 1 yenta_socket serio_raw 4804 0 i2c_core 20564 1 i2c_i801 iTCO_wdt9572 0 pcmcia_core30484 3 pcmcia,yenta_socket,rsrc_nonstatic snd_timer 17992 2 snd_pcm,snd_seq cfg80211 21320 3 iwlagn,iwlcore,mac80211 snd_seq_device 6412 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq video 16240 0 snd45688 11 snd_hda_intel,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_device output 2784 1 video intel_agp 22460 1 soundcore 6440 1 snd joydev 8672 0 wmi 6408 0 snd_page_alloc 7336 2 snd_hda_intel,snd_pcm battery10116 0 agpgart29780 3 drm,intel_agp button 6032 0 ac 4132 0 evdev 8324 9 dcdbas 6336 0 ext3 105128 5 jbd40820 1 ext3 mbcache 7396 1 ext3 sha256_generic 11392 0 cbc 3264 1 dm_crypt 11268 1 crypto_blkcipher 15204 4 ecb,cbc,dm_crypt dm_mirror 15936 0 dm_log 8548 1 dm_mirror dm_snapshot15332 0 dm_mod 46772 15 dm_crypt,dm_mirror,dm_log,dm_snapshot usbhid 23364 0 hid33868 1 usbhid ide_disk 10464 4 ata_piix 15460 0 ata_generic 4580 0 libata143788 2 ata_piix,ata_generic scsi_mod 129948 1 libata dock8368 1 libata piix5800 3 atkbd 15476 0 firewire_ohci 18020 0 firewire_core 32096 1 firewire_ohci crc_itu_t 2080 1 firewire_core ide_pci_generic 3588 0 ide_core 84548 3 ide_disk,piix,ide_pci_generic ehci_hcd 29292 0 tg3 104836 0 libphy 17248 1 tg3 uhci_hcd 19088 0 usbcore 118392 4 usbhid,ehci_hcd,uhci_hcd thermal15132 0 processor 33420 4 acpi_cpufreq,thermal fan 4324 0 thermal_sys 9416 4 video,thermal,processor,fan -- /etc/kernel-img.conf # Kernel image management overrides #
Bug#526562: tgt: FTBFS: storage size of 'cred' isn't known
Package: tgt Version: 20070924-1 Severity: serious From my pbuilder build log: ... cc -c -Wall -g -O2 -DISCSI -D_LARGEFILE64_SOURCE -I../include -I/include -I. - g -O2 -Wall -Wstrict-prototypes -fPIC mgmt.c -o mgmt.o mgmt.c: In function 'ipc_perm': mgmt.c:341: error: storage size of 'cred' isn't known mgmt.c:341: warning: unused variable 'cred' make[1]: *** [mgmt.o] Error 1 make[1]: Leaving directory `/tmp/buildd/tgt-20070924/usr' make: *** [build-stamp] Error 2 dpkg-buildpackage: failure: debian/rules build gave error exit status 2 -- Daniel Schepler -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#526551: linux-image-2.6.29-1-686: Does not halt/reboot on EeePC 901
Package: linux-image-2.6.29-1-686 Version: 2.6.29-3 Severity: normal System shutdown (poweroff or reboot) does not complete. Screen blanks and then it hangs. Have to press powerbutton for some seconds to turn it off. The system will NOT start again, it hangs with hdd-led on at power-on. The funny part: everything is ok if the ac-powersupply is disconnected and the eeepc is running on battery! For example, to start the eeepc after a unsuccessful poweroff, i have to unplug the powersupply, press the powerbutton and then it will start. Rebooting is working when running on battery, too. I have also issues with resuming from suspend with this kernel. -- Package-specific info: -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.26-2-686 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages linux-image-2.6.29-1-686 depends on: ii debconf [debconf-2.0] 1.5.26 Debian configuration management sy ii initramfs-tools [linux-initra 0.93.2 tools for generating an initramfs ii module-init-tools 3.7-pre9-1 tools for managing Linux kernel mo Versions of packages linux-image-2.6.29-1-686 recommends: ii libc6-i6862.9-9 GNU C Library: Shared libraries [i Versions of packages linux-image-2.6.29-1-686 suggests: ii grub 0.97-53GRand Unified Bootloader (Legacy v pn linux-doc-2.6.29 (no description available) -- debconf information: linux-image-2.6.29-1-686/preinst/abort-overwrite-2.6.29-1-686: shared/kernel-image/really-run-bootloader: true linux-image-2.6.29-1-686/preinst/overwriting-modules-2.6.29-1-686: true linux-image-2.6.29-1-686/preinst/elilo-initrd-2.6.29-1-686: true linux-image-2.6.29-1-686/preinst/initrd-2.6.29-1-686: linux-image-2.6.29-1-686/preinst/bootloader-initrd-2.6.29-1-686: true linux-image-2.6.29-1-686/postinst/bootloader-test-error-2.6.29-1-686: linux-image-2.6.29-1-686/postinst/depmod-error-initrd-2.6.29-1-686: false linux-image-2.6.29-1-686/prerm/removing-running-kernel-2.6.29-1-686: true linux-image-2.6.29-1-686/preinst/lilo-has-ramdisk: linux-image-2.6.29-1-686/postinst/old-system-map-link-2.6.29-1-686: true linux-image-2.6.29-1-686/postinst/kimage-is-a-directory: linux-image-2.6.29-1-686/postinst/old-dir-initrd-link-2.6.29-1-686: true linux-image-2.6.29-1-686/preinst/lilo-initrd-2.6.29-1-686: true linux-image-2.6.29-1-686/postinst/depmod-error-2.6.29-1-686: false linux-image-2.6.29-1-686/postinst/bootloader-error-2.6.29-1-686: linux-image-2.6.29-1-686/preinst/failed-to-move-modules-2.6.29-1-686: linux-image-2.6.29-1-686/postinst/create-kimage-link-2.6.29-1-686: true linux-image-2.6.29-1-686/prerm/would-invalidate-boot-loader-2.6.29-1-686: true linux-image-2.6.29-1-686/preinst/abort-install-2.6.29-1-686: linux-image-2.6.29-1-686/postinst/old-initrd-link-2.6.29-1-686: true -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#526551: Further information
Last working kernel is: 2.6.26-2-686 (reboot/halt ok on AC and battery, has issues with rt-wireless on suspend/resume). A bios-update to version 1903 and some workarounds (unload snd_hda_intel module and/or unload rt2860sta module before reboot/halt) found on the net did not help. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
