Processing of firmware-nonfree_0.14+lenny1_ia64.changes
firmware-nonfree_0.14+lenny1_ia64.changes uploaded successfully to localhost along with the files: firmware-nonfree_0.14+lenny1.dsc firmware-nonfree_0.14+lenny1.tar.gz firmware-bnx2_0.14+lenny1_all.deb firmware-ipw2x00_0.14+lenny1_all.deb firmware-iwlwifi_0.14+lenny1_all.deb firmware-qlogic_0.14+lenny1_all.deb firmware-ralink_0.14+lenny1_all.deb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
firmware-nonfree override disparity
There are disparities between your recently accepted upload and the override file for the following file(s): firmware-iwlwifi_0.14+lenny1_all.deb: package says section is non-free/admin, override says non-free/misc. Please note that a list of new sections were recently added to the archive: cli-mono, database, debug, fonts, gnu-r, gnustep, haskell, httpd, java, kernel, lisp, localization, ocaml, php, ruby, vcs, video, xfce, zope. At this time a script was used to reclassify packages into these sections. If this is the case, please only reply to this email if the new section is inappropriate, otherwise please update your package at the next upload. Either the package or the override file is incorrect. If you think the override is correct and the package wrong please fix the package so that this disparity is fixed in the next upload. If you feel the override is incorrect then please reply to this mail and explain why. Please INCLUDE the list of packages as seen above, or we won't be able to deal with your mail due to missing information. [NB: this is an automatically generated mail; if you replied to one like it before and have not received a response yet, please ignore this mail. Your reply needs to be processed by a human and will be in due course, but until then the installer will send these automated mails; sorry.] -- Debian distribution maintenance software (This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#506586: linux-image-2.6.26-1-amd64: Hard system freeze on accessing remote smbfs (cifs)
Hi Johannes, Ben! You wrote: I mount a remote windows share via this fstab entry: //nas.ads.mwn.de/remote/home/johannes/local-mount-point cifs noauto,user,credentials=/home/johannes/.smbcredentials (in one line) cd'ing to the local-mount-point and issuing du -hs . leads to an immediate freeze of the system (sometimes immediate reboot). I'm wondering, what kind of cifs server is the share being mounted from? In my case, nmap reports the remote machine is a NetApp FAS3020 or FAS 3040 NAS device (Data ONTAP 7.0.X - 7.2.X) -- +--+ | Bas Zoetekouw | Sweet day, so cool, so calm, so bright, | || The bridall of the earth and skie: | | b...@zoetekouw.net | The dew shall weep thy fall tonight;| +|For thou must die. | +-+ -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
firmware-nonfree_0.14+lenny1_ia64.changes ACCEPTED
Accepted: firmware-bnx2_0.14+lenny1_all.deb to pool/non-free/f/firmware-nonfree/firmware-bnx2_0.14+lenny1_all.deb firmware-ipw2x00_0.14+lenny1_all.deb to pool/non-free/f/firmware-nonfree/firmware-ipw2x00_0.14+lenny1_all.deb firmware-iwlwifi_0.14+lenny1_all.deb to pool/non-free/f/firmware-nonfree/firmware-iwlwifi_0.14+lenny1_all.deb firmware-nonfree_0.14+lenny1.dsc to pool/non-free/f/firmware-nonfree/firmware-nonfree_0.14+lenny1.dsc firmware-nonfree_0.14+lenny1.tar.gz to pool/non-free/f/firmware-nonfree/firmware-nonfree_0.14+lenny1.tar.gz firmware-qlogic_0.14+lenny1_all.deb to pool/non-free/f/firmware-nonfree/firmware-qlogic_0.14+lenny1_all.deb firmware-ralink_0.14+lenny1_all.deb to pool/non-free/f/firmware-nonfree/firmware-ralink_0.14+lenny1_all.deb Override entries for your package: firmware-bnx2_0.14+lenny1_all.deb - optional non-free/admin firmware-ipw2x00_0.14+lenny1_all.deb - optional non-free/admin firmware-iwlwifi_0.14+lenny1_all.deb - optional non-free/admin firmware-nonfree_0.14+lenny1.dsc - optional non-free/admin firmware-qlogic_0.14+lenny1_all.deb - optional non-free/admin firmware-ralink_0.14+lenny1_all.deb - optional non-free/admin Announcing to debian-chan...@lists.debian.org 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#521727: linux-image-2.6-686: desktop app are not responsive (kmail, firefox, OO)
On Sun, 29 Mar 2009, Alain Baeckeroot wrote: Le 29/03/2009 à 21:28, maximilian attems écrit : if you would take 5 minutes checking the bug reports you would see that aboves bug is already reported and is tracked for the next 2.6.26 update. I have checked but missed it, sorry to not be perfect :-) #521420 [i|+| ] [linux-2.6] linux-2.6: SQLite performance regression http://bugs.debian.org/cgi-bin/pkgreport.cgi?src=linux-2.6 concerning preempt and higher hz that is left for dicussion on debian kernel and seems out of topic here. should i fill a new bug tagged wish for a linux-image-desktop ? It _does_ really change the usability with big documents/mail no newer bug won't help, what is needed are benchmark test runs against higher HZ and one for PREEMPT. higher HZ should no longer matter since nohz, so it should be fine for server workloads too, but this needs to be shown. afais HZ_1000 is also the fedora default. -- maks -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#521615: Further info
I suspect that it has something todo with the kernel-parameter hpet=force. I tried the current git-kernel (2.6.29-git3) with hpet=force and it worked and atm I have linux-image-2.6.26-1-686 without hpet=force and it seems to work, too. I'm going to try vanilla-2.6.26.8, today too, to see if this bug is introduced by the debian patches or by the kernel. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#521829: linux-image-2.6.26-1-sparc64: loop is not a module. loop-aes is useless.
Package: linux-image-2.6.26-1-sparc64 Version: 2.6.26-13lenny2 Severity: important loop should be compiled as a module so loop-aes could be used. It's very annoying because on x86/x64 platforms this is the default. -- System Information: Debian Release: 5.0 APT prefers stable APT policy: (500, 'stable') Architecture: sparc (sparc64) Kernel: Linux 2.6.26-1-sparc64 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-1-sparc64 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-1-sparc64 recommends no packages. Versions of packages linux-image-2.6.26-1-sparc64 suggests: pn fdutilsnone(no description available) pn linux-doc-2.6.26 none(no description available) ii silo 1.4.13a+git20070930-3 Sparc Improved LOader -- debconf information: shared/kernel-image/really-run-bootloader: true linux-image-2.6.26-1-sparc64/postinst/old-initrd-link-2.6.26-1-sparc64: true linux-image-2.6.26-1-sparc64/preinst/lilo-has-ramdisk: linux-image-2.6.26-1-sparc64/preinst/abort-install-2.6.26-1-sparc64: linux-image-2.6.26-1-sparc64/preinst/elilo-initrd-2.6.26-1-sparc64: true linux-image-2.6.26-1-sparc64/postinst/old-dir-initrd-link-2.6.26-1-sparc64: true linux-image-2.6.26-1-sparc64/prerm/removing-running-kernel-2.6.26-1-sparc64: true * linux-image-2.6.26-1-sparc64/preinst/already-running-this-2.6.26-1-sparc64: linux-image-2.6.26-1-sparc64/postinst/bootloader-test-error-2.6.26-1-sparc64: linux-image-2.6.26-1-sparc64/prerm/would-invalidate-boot-loader-2.6.26-1-sparc64: true linux-image-2.6.26-1-sparc64/postinst/old-system-map-link-2.6.26-1-sparc64: true linux-image-2.6.26-1-sparc64/preinst/bootloader-initrd-2.6.26-1-sparc64: true linux-image-2.6.26-1-sparc64/preinst/lilo-initrd-2.6.26-1-sparc64: true linux-image-2.6.26-1-sparc64/postinst/kimage-is-a-directory: linux-image-2.6.26-1-sparc64/postinst/depmod-error-2.6.26-1-sparc64: false linux-image-2.6.26-1-sparc64/preinst/overwriting-modules-2.6.26-1-sparc64: true linux-image-2.6.26-1-sparc64/preinst/failed-to-move-modules-2.6.26-1-sparc64: linux-image-2.6.26-1-sparc64/postinst/create-kimage-link-2.6.26-1-sparc64: true linux-image-2.6.26-1-sparc64/postinst/bootloader-error-2.6.26-1-sparc64: linux-image-2.6.26-1-sparc64/postinst/depmod-error-initrd-2.6.26-1-sparc64: false linux-image-2.6.26-1-sparc64/preinst/initrd-2.6.26-1-sparc64: linux-image-2.6.26-1-sparc64/preinst/abort-overwrite-2.6.26-1-sparc64: -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 521829
Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.9.26etch2 tags 521829 + pending Bug#521829: linux-image-2.6.26-1-sparc64: loop is not a module. loop-aes is useless. There were no tags set. Tags added: 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#485034: linux-image-2.6.25-2-686: ath5k associates but no network
On Sun, 2009-03-29 at 10:38 -0700, Bill Wohler wrote: maximilian attems m...@stro.at wrote: I did, however, try WEP with 2.6.26. My box still did not associate. could you please try a more recent kernel like 2.6.29. ath5k saw a lot of work since. Thanks. There are a couple of issues which will get in my way: 1. The new kernels have really, really large /lib/modules directories and are too big for my / partition. [...] This was true of 2.6.28 but the problem was fixed in 2.6.29. Ben. signature.asc Description: This is a digitally signed message part
Bug#501326: marked as done (linux-image-2.6.26-1-amd64: ACPI power off doesn't work)
Your message dated Mon, 30 Mar 2009 16:13:18 +0200 with message-id 20090330141318.gi27...@stro.at and subject line Re: linux-image-2.6.26-1-amd64: ACPI power off doesn't work has caused the Debian Bug report #501326, regarding linux-image-2.6.26-1-amd64: ACPI power off doesn't 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.) -- 501326: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=501326 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.26-1-amd64 Version: 2.6.26-7 Severity: important Asus A8N SLI-Premium Since upgrading to 2.6.26, motherboard reboots instead of powering off computer when acpi power off is called. I have the latest BIOS from www.asus.com.tw. It's very annoying, because I use Wake On LAN to remotely power on my computer when needed. With 2.6.26 I have to manually power off computer, and then WOL stops working, plus I cannot remotely power off computer! -- Package-specific info: ** Version: Linux version 2.6.26-1-amd64 (Debian 2.6.26-7) (wa...@debian.org) (gcc version 4.1.3 20080623 (prerelease) (Debian 4.1.2-23)) #1 SMP Wed Oct 1 11:14:14 UTC 2008 ** Command line: root=/dev/mapper/sistema_vg-root_lv vga=0x317 ro ** Not tainted ** Kernel log: [ 14.414845] parport_pc 00:09: driver attached [ 14.414855] saa7134[0]: subsystem: 153b:1142, board: Terratec Cinergy 400 TV [card=8,autodetected] [ 14.417672] saa7134[0]: board init: gpio is 5 [ 14.422844] sd 3:0:0:1: [sdd] Attached SCSI removable disk [ 14.425153] input: saa7134 IR (Terratec Cinergy 40 as /class/input/input6 [ 14.430920] sd 3:0:0:1: Attached scsi generic sg4 type 0 [ 14.442913] sd 3:0:0:2: [sde] Attached SCSI removable disk [ 14.446772] sd 3:0:0:2: Attached scsi generic sg5 type 0 [ 14.454844] sd 3:0:0:3: [sdf] Attached SCSI removable disk [ 14.458894] sd 3:0:0:3: Attached scsi generic sg6 type 0 [ 14.472824] pnp: the driver 'ns558' has been registered [ 14.472824] ns558 00:0b: driver attached [ 14.494363] gameport: NS558 PnP Gameport is pnp00:0b/gameport0, io 0x201, speed 904kHz [ 14.553757] Error: Driver 'pcspkr' is already registered, aborting... [ 14.659665] saa7134[0]: i2c eeprom 00: 3b 15 42 11 ff ff ff ff ff ff ff ff ff ff ff ff [ 14.664349] saa7134[0]: i2c eeprom 10: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 14.669001] saa7134[0]: i2c eeprom 20: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 14.673589] saa7134[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 14.677618] saa7134[0]: i2c eeprom 40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 14.682578] saa7134[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 14.690096] saa7134[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 14.695025] saa7134[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 14.699296] saa7134[0]: i2c eeprom 80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 14.703457] saa7134[0]: i2c eeprom 90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 14.707538] saa7134[0]: i2c eeprom a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 14.711615] saa7134[0]: i2c eeprom b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 14.715618] saa7134[0]: i2c eeprom c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 14.719560] saa7134[0]: i2c eeprom d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 14.723453] saa7134[0]: i2c eeprom e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 14.723915] saa7134[0]: i2c eeprom f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 14.818235] All bytes are equal. It is not a TEA5767 [ 14.821552] tuner' 2-0060: chip found @ 0xc0 (saa7134[0]) [ 14.862876] tuner-simple 2-0060: creating new instance [ 14.865548] tuner-simple 2-0060: type set to 5 (Philips PAL_BG (FI1216 and compatibles)) [ 14.897834] saa7134[0]: registered device video0 [v4l2] [ 14.901622] saa7134[0]: registered device vbi0 [ 14.905622] ACPI: PCI Interrupt Link [APCJ] enabled at IRQ 23 [ 14.908940] ACPI: PCI Interrupt :00:04.0[A] - Link [APCJ] - GSI 23 (level, low) - IRQ 23 [ 14.912959] PCI: Setting latency timer of device :00:04.0 to 64 [ 15.240300] intel8x0_measure_ac97_clock: measured 54687 usecs [ 15.241627] intel8x0: clocking to 46875 [ 15.532002] hda: UDMA/66 mode selected [ 16.338108] Adding 923728k swap on /dev/sda2. Priority:10 extents:1 across:923728k [ 16.366902] Adding 979924k swap on /dev/sdb1. Priority:10 extents:1 across:979924k [ 22.482207] loop: module loaded [
Bug#351908: marked as done ([powerpc,dual-g5-mac] initial boot failure)
Your message dated Mon, 30 Mar 2009 16:14:25 +0200 with message-id 20090330141425.gj27...@stro.at and subject line Re: Re: [powerpc,dual-g5-mac] initial boot failure has caused the Debian Bug report #351908, regarding [powerpc,dual-g5-mac] initial boot failure 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.) -- 351908: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=351908 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.15-4 I'm trying to install Debian testing on a PowerMac11,2 (PowerMac G5, dual 2GHz processors, January 2006) using a current etch d-i ISO. From the boot screen I have tried install64 install64 video=ofonly These start the boot process which leaves some OF text on the screen (black on white) and overwrites it with the following in a white IBM- like font on a black background: Found initrd at 0xc00...1736 trying to initialize btext ... CF000100 MM Init CF000100 MM Init Done CF12 Setup Arch ... and at this point the box (or at least the display) freezes. After a short time the fan comes on. The display adaptor is a PCI nVidia GeForce 6600. -- 犬 Chris Burdess They that can give up essential liberty to obtain a little safety deserve neither liberty nor safety. - Benjamin Franklin PGP.sig Description: This is a digitally signed message part ---End Message--- ---BeginMessage--- Sorry, I no longer have this machine to test on. thus closing, thanks for the report. ---End Message---
Bug#425349: marked as done (linux-image-2.6.21-1-powerpc64: No X on IBM Intellistation 285)
Your message dated Mon, 30 Mar 2009 16:17:38 +0200 with message-id 20090330141738.gk27...@stro.at and subject line Re: linux-image-2.6.21-1-powerpc64: No X on IBM Intellistation 285 has caused the Debian Bug report #425349, regarding linux-image-2.6.21-1-powerpc64: No X on IBM Intellistation 285 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.) -- 425349: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=425349 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.21-1-powerpc64 Version: 2.6.21-2 Severity: normal *** Please type your report below this line *** The kernel build needs to have CONFIG_FB_IBM_GXT4500 set to 'y' for this machine otherwise, despite the console working slowly, the X server will not work (I have an external driver for the GXT4500 card). -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.19 Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash ---End Message--- ---BeginMessage--- Version: 2.6.26-1 The kernel build needs to have CONFIG_FB_IBM_GXT4500 set to 'y' for this debian/config/powerpc/config:CONFIG_FB_IBM_GXT4500=m fb is build modular since, thus closing. -- maks ---End Message---
Bug#492266: marked as done (xfs_fsr broken on powerpc)
Your message dated Mon, 30 Mar 2009 16:17:15 +0200 with message-id 20090330141715.gn3...@baikonur.stro.at and subject line Re: xfs_fsr broken on powerpc has caused the Debian Bug report #492266, regarding xfs_fsr broken on powerpc 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.) -- 492266: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=492266 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: xfsdump Version: 2.2.48-1 Attempting to defragment an xfs filesystem fails: xfs_fsr /dev/power/data /san start inode=0 unable to get handle: /san: Invalid argument # uname -a Linux power 2.6.22-3-powerpc64 #1 SMP Wed Nov 14 00:29:55 UTC 2007 ppc64 GNU/Linux Daniel Bakken ---End Message--- ---BeginMessage--- Version: 2.6.29-1 xfs improved since, thanks for the report. ---End Message---
Bug#435226: marked as done (linux-image-2.6.22-1-powerpc nvidia frame buffer and ams problems)
Your message dated Mon, 30 Mar 2009 16:15:59 +0200 with message-id 20090330141558.gm3...@baikonur.stro.at and subject line Re: linux-image-2.6.22-1-powerpc nvidia frame buffer and ams problems has caused the Debian Bug report #435226, regarding linux-image-2.6.22-1-powerpc nvidia frame buffer and ams problems 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.) -- 435226: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=435226 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.22-1-powerpc Version: 2.6.22-3 Severity: normal *** Please type your report below this line *** Since linux-image-2.6.22-1-powerpc_2.6.22-1_powerpc.deb was out I decided to give it a try in my 12 powerbook. I have tried versions 2.6.22-1, 2.6.22-2 and 2.6.22-3. It all seems to work ok except for: 1) the framebuffer 'resolution' detection, I mean that in the booting process I get taller letters (deformed, they are stretched, also happens the same with the penguin logo) and the prompt is lost somewhere down under the screen. I can solve this by blindly typing: fbset 1024x768-60, but this didn't happen with kernels up to (and included) 2.6.21. I have tried several possible combinations in yaboot.conf: - append=video=nv:1024x768-60 ... - append=video=rivafb:1024x768-60 ... without luck. Being video=ofonly the only one that gives a 'correct' frame buffer, but I lose the ability to dim the screen backlight. 2) it seems there's no ams (apple motion sensor) module built, it would be nice to have it. -- Package-specific info: ** Version: Linux version 2.6.22-1-powerpc (Debian 2.6.22-3) (wa...@debian.org) (gcc version 4.1.3 20070718 (prerelease) (Debian 4.1.2-14)) #1 Sun Jul 29 13:58:06 CEST 2007 ** Not tainted ** Kernel log: bcm43xx: Core 4: ID 0x804, rev 0x9, vendor 0x4243 bcm43xx: PHY connected bcm43xx: Detected PHY: Analog: 2, Type 2, Revision 2 bcm43xx: Detected Radio: ID: 2205017f (Manuf: 17f Ver: 2050 Rev: 2) bcm43xx: Radio turned off bcm43xx: Radio turned off input: appletouch as /class/input/input8 usbcore: registered new interface driver appletouch sd 0:0:0:0: [sda] Attached SCSI removable disk sd 0:0:0:1: [sdb] Attached SCSI removable disk sd 0:0:0:2: [sdc] Attached SCSI removable disk sd 0:0:0:3: [sdd] Attached SCSI removable disk snd-aoa-fabric-layout: found bus with layout 72 snd-aoa-fabric-layout: Using PMF GPIOs snd-aoa-codec-tas: found tas3004 snd-aoa-fabric-layout: can use this codec snd-aoa-codec-tas: tas found, addr 0x35 on /p...@f200/mac...@17/i...@18000/i2c-...@0/co...@6a Adding 2441396k swap on /dev/hda6. Priority:-1 extents:1 across:2441396k EXT3 FS on hda3, internal journal loop: module loaded adt746x: version 1 (supported) adt746x: Thermostat bus: 1, address: 0x2e, limit_adjust: 0, fan_speed: -1 sensor 0: HDD BOTTOMSIDE sensor 1: CPU TOPSIDE sensor 2: GPU ON DIE adt746x: ADT7467 initializing adt746x: Lowering max temperatures from 73, 80, 109 to 70, 50, 70 fuse init (API version 7.8) kjournald starting. Commit interval 5 seconds EXT3 FS on hda5, internal journal EXT3-fs: mounted filesystem with ordered data mode. kjournald starting. Commit interval 5 seconds EXT3 FS on hda4, internal journal EXT3-fs: mounted filesystem with ordered data mode. snd-powermac no longer handles any machines with a layout-id property in the device-tree, use snd-aoa. NET: Registered protocol family 15 NET: Registered protocol family 10 lo: Disabled Privacy Extensions lp: driver loaded but no devices found Bluetooth: Core ver 2.11 NET: Registered protocol family 31 Bluetooth: HCI device and connection manager initialized Bluetooth: HCI socket layer initialized Bluetooth: L2CAP ver 2.8 Bluetooth: L2CAP socket layer initialized usb 1-1: usbfs: USBDEVFS_CONTROL failed cmd hid2hci rqt 64 rq 0 len 0 ret -62 Bluetooth: RFCOMM socket layer initialized Bluetooth: RFCOMM TTY layer initialized Bluetooth: RFCOMM ver 1.8 usb 1-1: USB disconnect, address 2 bcm43xx: PHY connected usb 1-1: new full speed USB device using ohci_hcd and address 4 bcm43xx: Microcode rev 0x122, pl 0x99 (2005-01-22 22:40:08) bcm43xx: Radio turned on bcm43xx: Radio enabled by hardware bcm43xx: Chip initialized bcm43xx: 30-bit DMA initialized bcm43xx: Keys cleared bcm43xx: Selected 802.11 core (phytype 2) ADDRCONF(NETDEV_UP): eth2: link is not ready usb 1-1: configuration #1 chosen from 1 choice bcm43xx: set security called, .level = 0, .enabled = 0, .encrypt = 0 ADDRCONF(NETDEV_UP): eth1: link is not ready SoftMAC: Open Authentication completed with 00:40:10:10:00:03 ADDRCONF(NETDEV_CHANGE): eth2: link becomes ready
Processed: bug 510195 is forwarded to http://bugzilla.kernel.org/show_bug.cgi?id=12330
Processing commands for cont...@bugs.debian.org: forwarded 510195 http://bugzilla.kernel.org/show_bug.cgi?id=12330 Bug#510195: linux-image-2.6.26-1-powerpc: macmini g4 1.07ghz does not boot with 2.6.26-1-powerpc Noted your statement that Bug has been forwarded to http://bugzilla.kernel.org/show_bug.cgi?id=12330. 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#521370: mkinitramfs doesn't find firmware files
Hi, maks.
On Mar 27 2009, maximilian attems wrote:
right thanks for report.
you can try belows patch,
you will need to apply it to /usr/share/initramfs-tools/hook-functions
commit dabf87a52411c729536051e78b2ad587f767be54
Author: maximilian attems m...@debian.org
Date: Fri Mar 27 10:35:20 2009 +0100
hook-functions: Add firmware from versioned directories too.
First see if there is a $(uname -a) versioned firmware around
and if there is add it first.
Builds the cpio image fine.
Thanks, Rogério Brito.
--
Rogério Brito : rbr...@{mackenzie,ime.usp}.br : GPG key 1024D/7C2CAEB8
http://www.ime.usp.br/~rbrito : http://meusite.mackenzie.com.br/rbrito
Projects: algorithms.berlios.de : lame.sf.net : vrms.alioth.debian.org
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#413666: marked as done (linux-image-powerpc64: wireless extensions broken for 32-bit userspace)
Your message dated Mon, 30 Mar 2009 16:20:19 +0200 with message-id 20090330142019.go3...@baikonur.stro.at and subject line Re: linux-image-powerpc64: wireless extensions broken for 32-bit userspace has caused the Debian Bug report #413666, regarding linux-image-powerpc64: wireless extensions broken for 32-bit userspace 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.) -- 413666: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=413666 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-powerpc64 Severity: normal This bug report exists upstream but for your information and for tracking... The wireless extensions used by wpa supplicant, wireless-tools and various other programs are broken for 32-bit programs running on 64-bit kernels because they use pointers within structs and have no compat structs. More information at http://thread.gmane.org/gmane.linux.kernel.wireless.general/935 -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: powerpc (ppc) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.21-rc1 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) ---End Message--- ---BeginMessage--- Version: 2.6.24-1 closing as this has been dealt with since, thanks for report. ---End Message---
Bug#458562: marked as done (firmware-iwlwifi: iwlwifi should conflict with ipw3945d)
Your message dated Mon, 30 Mar 2009 16:27:51 +0200 with message-id 20090330142751.gl27...@stro.at and subject line Re: firmware-iwlwifi: iwlwifi should conflict with ipw3945d has caused the Debian Bug report #458562, regarding firmware-iwlwifi: iwlwifi should conflict with ipw3945d 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.) -- 458562: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=458562 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: firmware-iwlwifi Severity: normal Hi, Running an ipw3945 card in my laptop, I had problems since sometime to make it work. The old ipw3945 module did not work anymore, so I tried to use the new iwlwifi driver coming with 2.6.23 and the firmware-iwlwifi. Because this does not conflict with ipw3945d, the ipw3945 service was always started on boot time and it was not possible to have the new iwl3945 module running. I guess that making the package conflict could be an elegant solution. I can provide more info it needed. Didrik -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.23-1-686 (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 ---End Message--- ---BeginMessage--- latest stable release has no ipw3945d anymore, so there is not much point anymore to that request. thus closing -- maks ---End Message---
Bug#502997: marked as done (package could be named better)
Your message dated Mon, 30 Mar 2009 16:29:55 +0200 with message-id 20090330142954.gm27...@stro.at and subject line Re: package could be named better has caused the Debian Bug report #502997, regarding package could be named better 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.) -- 502997: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=502997 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: firmware-iwlwifi Version: 0.13 Severity: wishlist A name (or alias) like 'iwlwifi-firmware' would be helpful (as I assumed that would be roughly what the package name for any firmware I was missing would be). -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (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/bash firmware-iwlwifi depends on no packages. firmware-iwlwifi recommends no packages. Versions of packages firmware-iwlwifi suggests: ii initramfs-tools0.92l tools for generating an initramfs ii linux-image-2.6.18 2.6.18.dfsg.1-13etch6 Linux 2.6.18 image on PPro/Celeron ii linux-image-2.6.26 2.6.26-9 Linux 2.6.26 image on PPro/Celeron -- no debconf information ---End Message--- ---BeginMessage--- I was able to find the firmware-iwlwifi package using apt-cache search iwl I think this bug can be closed or tagged wontfix. closing. -- maks ---End Message---
Processed: tagging 520551
Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.9.26etch2 tags 520551 + pending Bug#520551: openvz breakage with udev in certain virtual environments Tags were: patch Tags added: 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
Processed: tagging 521420
Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.9.26etch2 tags 521420 + pending Bug#521420: linux-2.6: SQLite performance regression Tags were: patch Tags added: 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#521865: linux-image-2.6.29-1-powerpc: keyboard not working at all
Package: linux-image-2.6.29-1-powerpc Version: 2.6.29-1 Severity: grave Justification: renders package unusable Hi! Upgrading to 2.6.29-1 did cause several problems: - The keyboard didn't react to any key pressed - An external usb keyboard didn't react to any key pressed neither - external mouse did receive power (optical red light was there) but cursor didn't move Only thing I could do was use the touchpad on my PowerBook G4, which which I at least was able to choose the shutdown thing from the gdm menu. I guess this is reason enough to call this a RC bug report. Booting with the old kernel did enable my system for using it again. Thanks. Rhonda -- Package-specific info: -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: powerpc (ppc) Kernel: Linux 2.6.28-1-powerpc Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages linux-image-2.6.29-1-powerpc depends on: ii debconf [debconf-2.0] 1.5.26 Debian configuration management sy ii initramfs-tools [linux-initra 0.93 tools for generating an initramfs ii libc6 2.9-4 GNU C Library: Shared libraries ii module-init-tools 3.7-pre9-1 tools for managing Linux kernel mo linux-image-2.6.29-1-powerpc recommends no packages. Versions of packages linux-image-2.6.29-1-powerpc suggests: pn linux-doc-2.6.29 none (no description available) pn mkvmlinuz none (no description available) -- debconf information: linux-image-2.6.29-1-powerpc/preinst/elilo-initrd-2.6.29-1-powerpc: true linux-image-2.6.29-1-powerpc/preinst/failed-to-move-modules-2.6.29-1-powerpc: linux-image-2.6.29-1-powerpc/postinst/bootloader-test-error-2.6.29-1-powerpc: linux-image-2.6.29-1-powerpc/postinst/old-initrd-link-2.6.29-1-powerpc: true linux-image-2.6.29-1-powerpc/postinst/old-dir-initrd-link-2.6.29-1-powerpc: true linux-image-2.6.29-1-powerpc/preinst/overwriting-modules-2.6.29-1-powerpc: true linux-image-2.6.29-1-powerpc/preinst/bootloader-initrd-2.6.29-1-powerpc: true linux-image-2.6.29-1-powerpc/postinst/depmod-error-2.6.29-1-powerpc: false linux-image-2.6.29-1-powerpc/preinst/abort-overwrite-2.6.29-1-powerpc: linux-image-2.6.29-1-powerpc/postinst/bootloader-error-2.6.29-1-powerpc: linux-image-2.6.29-1-powerpc/preinst/lilo-initrd-2.6.29-1-powerpc: true linux-image-2.6.29-1-powerpc/prerm/would-invalidate-boot-loader-2.6.29-1-powerpc: true linux-image-2.6.29-1-powerpc/postinst/create-kimage-link-2.6.29-1-powerpc: true linux-image-2.6.29-1-powerpc/postinst/kimage-is-a-directory: linux-image-2.6.29-1-powerpc/prerm/removing-running-kernel-2.6.29-1-powerpc: true shared/kernel-image/really-run-bootloader: true linux-image-2.6.29-1-powerpc/preinst/lilo-has-ramdisk: linux-image-2.6.29-1-powerpc/postinst/old-system-map-link-2.6.29-1-powerpc: true linux-image-2.6.29-1-powerpc/postinst/depmod-error-initrd-2.6.29-1-powerpc: false linux-image-2.6.29-1-powerpc/preinst/abort-install-2.6.29-1-powerpc: linux-image-2.6.29-1-powerpc/preinst/initrd-2.6.29-1-powerpc: -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#521691: linux-image-2.6.29-1-amd64: #521691 loopback interface breaks too
Package: linux-image-2.6.29-1-amd64 Version: 2.6.29-1 For me, the loopback interface breaks as well as ethernet CC'ing the other submitters, as that's something to test on their machines. I think this is #521691, but my computer stays online far longer than the original report - so far I've had uptimes of between 45 minutes and 13h50m before the network dies. The upgrade to 2.6.29 is also the time that eth0 became eth1, unsure if that change is from the kernel or udev. It's an upgrade from a custom-built 2.6.26; and the bug occurs both with the official Debian 2.6.29 and a make oldconfig custom one. ping -f localhost ifconfig shows both RX and TX incrementing iptables shows OUTPUT's counter incrementing, but not INPUT's Wireshark shows no packets being sent or received (tried both the lo and eth1 interfaces) ping 1.1.1.1 gets stuck doing an ARP lookup for the default gateway's address ifconfig shows both RX and TX incrementing in roughly equal amounts iptables shows OUTPUT's counter incrementing, but not INPUT's Wireshark in promisc mode shows only the outgoing ARP requests, no responses ifconfig for the *loopback* interface shows both RX and TX incrementing too, but only while the ping is running ping this machine from another machine: ifconfig shows RX incrementing, TX constant iptables shows INPUT's counter being unchanged Wireshark (on this machine) in promisc mode shows no packets being received ping6 ip6-localhost same as IPv4 measuring background network noise Without running any pings, eth1's RX is around 1 packet per 20 seconds Using forcedeth with nForce4's on-board ethernet. 00:0a.0 Bridge: nVidia Corporation CK804 Ethernet Controller (rev a3) iptables -t raw -L -v shows the same as the normal table - OUTPUT is seeing packets, PREROUTING isn't ip6tables shows the same result for the ip6-localhost ping Wireshark's main interface shows that the computer is making ARP requests for the default gateway's address, but getting no reply. Said gateway is itself crappy hardware, but this bug is new with the upgrade to 2.6.29. Wireshark's Capture interfaces dialog does show the packet counts incrementing. It also shows 5 USB buses, but their counters stay at zero. -- Package-specific info: root=/dev/sda5 ro noapic nolapic ** Not tainted (Big run-reportbug-as-root info attached bzip'd. I don't see anything interesting in there.) -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (990, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.29-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/bash Versions of packages linux-image-2.6.29-1-amd64 depends on: ii debconf [debconf-2.0] 1.5.26 Debian configuration management sy ii initramfs-tools [linux-initra 0.93.1 tools for generating an initramfs ii module-init-tools 3.7-pre9-1 tools for managing Linux kernel mo linux-image-2.6.29-1-amd64 recommends no packages. Versions of packages linux-image-2.6.29-1-amd64 suggests: ii grub 0.97-47lenny2 GRand Unified Bootloader (Legacy v ii linux-doc-2.6.29 2.6.29-10.00.Custom Linux kernel specific documentatio -- debconf information: linux-image-2.6.29-1-amd64/preinst/overwriting-modules-2.6.29-1-amd64: true linux-image-2.6.29-1-amd64/preinst/failed-to-move-modules-2.6.29-1-amd64: linux-image-2.6.29-1-amd64/postinst/old-dir-initrd-link-2.6.29-1-amd64: true linux-image-2.6.29-1-amd64/prerm/removing-running-kernel-2.6.29-1-amd64: true linux-image-2.6.29-1-amd64/postinst/create-kimage-link-2.6.29-1-amd64: true linux-image-2.6.29-1-amd64/preinst/initrd-2.6.29-1-amd64: linux-image-2.6.29-1-amd64/postinst/kimage-is-a-directory: linux-image-2.6.29-1-amd64/preinst/abort-install-2.6.29-1-amd64: linux-image-2.6.29-1-amd64/postinst/old-system-map-link-2.6.29-1-amd64: true linux-image-2.6.29-1-amd64/preinst/lilo-initrd-2.6.29-1-amd64: true shared/kernel-image/really-run-bootloader: true linux-image-2.6.29-1-amd64/postinst/bootloader-test-error-2.6.29-1-amd64: linux-image-2.6.29-1-amd64/preinst/lilo-has-ramdisk: linux-image-2.6.29-1-amd64/preinst/elilo-initrd-2.6.29-1-amd64: true linux-image-2.6.29-1-amd64/postinst/old-initrd-link-2.6.29-1-amd64: true linux-image-2.6.29-1-amd64/postinst/depmod-error-2.6.29-1-amd64: false linux-image-2.6.29-1-amd64/postinst/depmod-error-initrd-2.6.29-1-amd64: false linux-image-2.6.29-1-amd64/preinst/abort-overwrite-2.6.29-1-amd64: linux-image-2.6.29-1-amd64/postinst/bootloader-error-2.6.29-1-amd64: linux-image-2.6.29-1-amd64/prerm/would-invalidate-boot-loader-2.6.29-1-amd64: true linux-image-2.6.29-1-amd64/preinst/bootloader-initrd-2.6.29-1-amd64: true 521691_full_info.txt.bz2 Description: Binary data
linux-image-2.6.29-1-amd64 mismatched checksum
I can tried downloading/installing this package several times, from different mirrors, with no success. Synaptic/apt reports problem as checksum mismatch. I have the same problems downloading the 2.6.29-1 source. I would appreciate any help, Christhian
Bug#521515: [linux-headers-2.6.29-1-amd64] 'Documented usage'?
For me the new scheme breaks building the VMware Workstation kernel modules as well as the standalone drm.git tree. Failure output from the latter above. Even assuming neither of these conform to the 'documented usage' of kbuild (in which case I'd be interested in learning how to fix them), this leaves me wondering if any benefits of the new scheme are really worth breaking so many trees needing kernel headers? make: Entering directory `/home/daenzer/src/mesa-git/drm/linux-core' make -C /lib/modules/2.6.29-1-amd64/build SUBDIRS=`/bin/pwd` DRMSRCDIR=`/bin/pwd` modules make[1]: Entering directory `/usr/src/linux-headers-2.6.29-1-amd64' CC [M] /home/daenzer/src/mesa-git/drm/linux-core/drm_auth.o In file included from /home/daenzer/src/mesa-git/drm/linux-core/drm_auth.c:36: /home/daenzer/src/mesa-git/drm/linux-core/drmP.h:44:26: error: linux/module.h: No such file or directory /home/daenzer/src/mesa-git/drm/linux-core/drmP.h:45:26: error: linux/kernel.h: No such file or directory /home/daenzer/src/mesa-git/drm/linux-core/drmP.h:46:30: error: linux/miscdevice.h: No such file or directory /home/daenzer/src/mesa-git/drm/linux-core/drmP.h:47:22: error: linux/fs.h: No such file or directory /home/daenzer/src/mesa-git/drm/linux-core/drmP.h:48:27: error: linux/proc_fs.h: No such file or directory /home/daenzer/src/mesa-git/drm/linux-core/drmP.h:49:24: error: linux/init.h: No such file or directory /home/daenzer/src/mesa-git/drm/linux-core/drmP.h:50:24: error: linux/file.h: No such file or directory /home/daenzer/src/mesa-git/drm/linux-core/drmP.h:51:23: error: linux/pci.h: No such file or directory /home/daenzer/src/mesa-git/drm/linux-core/drmP.h:52:27: error: linux/version.h: No such file or directory /home/daenzer/src/mesa-git/drm/linux-core/drmP.h:53:25: error: linux/sched.h: No such file or directory /home/daenzer/src/mesa-git/drm/linux-core/drmP.h:54:54: error: linux/smp_lock.h: No such file or directory /home/daenzer/src/mesa-git/drm/linux-core/drmP.h:55:31: error: linux/dma-mapping.h: No such file or directory /home/daenzer/src/mesa-git/drm/linux-core/drmP.h:56:22: error: linux/mm.h: No such file or directory /home/daenzer/src/mesa-git/drm/linux-core/drmP.h:57:24: error: linux/kref.h: No such file or directory /home/daenzer/src/mesa-git/drm/linux-core/drmP.h:58:27: error: linux/pagemap.h: No such file or directory /home/daenzer/src/mesa-git/drm/linux-core/drmP.h:59:25: error: linux/mutex.h: No such file or directory /home/daenzer/src/mesa-git/drm/linux-core/drmP.h:63:20: error: asm/io.h: No such file or directory /home/daenzer/src/mesa-git/drm/linux-core/drmP.h:64:22: error: asm/mman.h: No such file or directory /home/daenzer/src/mesa-git/drm/linux-core/drmP.h:65:25: error: asm/uaccess.h: No such file or directory /home/daenzer/src/mesa-git/drm/linux-core/drmP.h:69:21: error: asm/agp.h: No such file or directory /home/daenzer/src/mesa-git/drm/linux-core/drmP.h:74:29: error: linux/workqueue.h: No such file or directory /home/daenzer/src/mesa-git/drm/linux-core/drmP.h:75:24: error: linux/poll.h: No such file or directory /home/daenzer/src/mesa-git/drm/linux-core/drmP.h:76:25: error: asm/pgalloc.h: No such file or directory In file included from /home/daenzer/src/mesa-git/drm/linux-core/drmP.h:77, from /home/daenzer/src/mesa-git/drm/linux-core/drm_auth.c:36: /home/daenzer/src/mesa-git/drm/linux-core/drm.h:75:46: error: asm/ioctl.h: No such file or directory In file included from /home/daenzer/src/mesa-git/drm/linux-core/drmP.h:77, from /home/daenzer/src/mesa-git/drm/linux-core/drm_auth.c:36: /home/daenzer/src/mesa-git/drm/linux-core/drm.h:569: error: expected specifier-qualifier-list before ‘uint32_t’ /home/daenzer/src/mesa-git/drm/linux-core/drm.h:672: error: expected specifier-qualifier-list before ‘uint64_t’ /home/daenzer/src/mesa-git/drm/linux-core/drm.h:827: error: expected specifier-qualifier-list before ‘uint64_t’ /home/daenzer/src/mesa-git/drm/linux-core/drm.h:839: error: expected specifier-qualifier-list before ‘uint64_t’ /home/daenzer/src/mesa-git/drm/linux-core/drm.h:854: error: expected specifier-qualifier-list before ‘uint64_t’ /home/daenzer/src/mesa-git/drm/linux-core/drm.h:914: error: expected specifier-qualifier-list before ‘uint64_t’ /home/daenzer/src/mesa-git/drm/linux-core/drm.h:939: error: expected specifier-qualifier-list before ‘uint32_t’ /home/daenzer/src/mesa-git/drm/linux-core/drm.h:954: error: expected specifier-qualifier-list before ‘uint64_t’ /home/daenzer/src/mesa-git/drm/linux-core/drm.h:960: error: expected specifier-qualifier-list before ‘uint64_t’ /home/daenzer/src/mesa-git/drm/linux-core/drm.h:965: error: expected specifier-qualifier-list before ‘uint32_t’ /home/daenzer/src/mesa-git/drm/linux-core/drm.h:971: error: expected specifier-qualifier-list before ‘uint32_t’ /home/daenzer/src/mesa-git/drm/linux-core/drm.h:979: error: expected specifier-qualifier-list before ‘uint32_t’ In file included from
Bug#509646: bnx2x firmware licensing
hello jsw, please post your bnx2x patch to net...@vger.kernel.org so that it can be reviewed and merged upstream! thanks :) -- maks -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#521515: [linux-headers-2.6.29-1-amd64] 'Documented usage'?
On Mon, Mar 30, 2009 at 06:27:51PM +0200, Michel Dänzer wrote: Even assuming neither of these conform to the 'documented usage' of kbuild (in which case I'd be interested in learning how to fix them), Documented usage for out of tree building is | make -C $DIR M=$(pwd) or similar. The drm tree does not even survive this test. this leaves me wondering if any benefits of the new scheme are really worth breaking so many trees needing kernel headers? It drasticaly reduces the amount of code needed to create the packages. Bastian -- You! What PLANET is this! -- McCoy, The City on the Edge of Forever, stardate 3134.0 -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: linux-image-2.6.29-1-amd64 mismatched checksum
Hi Christhian On Mon, Mar 30, 2009 at 12:01 PM, Christhian Lima cjal...@gmail.com wrote: I can tried downloading/installing this package several times, from different mirrors, with no success. Synaptic/apt reports problem as checksum mismatch. I have the same problems downloading the 2.6.29-1 source. I`ve installed the package here successfully, please provide some more information, like the complete output, command you run, and desirable you sources.lst. -- (°= Leandro Dorileo //\ldori...@gmail.com - http://www.dorilex.net V_/ Software is a matter of freedom. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: severity of 521865 is important
Processing commands for cont...@bugs.debian.org: severity 521865 important Bug#521865: linux-image-2.6.29-1-powerpc: keyboard not working at all Severity set to `important' from `grave' 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
Processed: Re: Bug#521863: popen broken on some systems
Processing commands for cont...@bugs.debian.org: reassign 521863 linux-image-2.6.26-1-amd64 Bug#521863: popen broken on some systems Bug reassigned from package `libc6' to `linux-image-2.6.26-1-amd64'. forcemerge 518921 521863 Bug#518921: i386 missing syscall detection is broken on amd64 Bug#521863: popen broken on some systems Forcibly Merged 518921 521863. 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#521615: Further info
On Mon, 30 Mar 2009, Henrik wrote: I suspect that it has something todo with the kernel-parameter hpet=force. I tried the current git-kernel (2.6.29-git3) with hpet=force and it worked and atm I have linux-image-2.6.26-1-686 without hpet=force and it seems to work, too. I'm going to try vanilla-2.6.26.8, today too, to see if this bug is introduced by the debian patches or by the kernel. you can try different snapshots prebuild: http://wiki.debian.org/DebianKernel -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#521886: linux-image-2.6.26-1-amd64: [iwl3945] should request firmware only once, not fill logs
Package: linux-image-2.6.26-1-amd64 Version: 2.6.26-13 Severity: wishlist Hello, On first install of Debian, the firmware is not present because it is part of the non-free package. However, the module keeps asking for its firmware (through udev?), which fills the log for no purpose. This can be stopped by rmmod'ing the concerned module, however I believe this is not the best policy, the module should perform its request only once. -- Package-specific info: ** Version: Linux version 2.6.26-1-amd64 (Debian 2.6.26-13) (wa...@debian.org) (gcc version 4.1.3 20080704 (prerelease) (Debian 4.1.2-24)) #1 SMP Sat Jan 10 17:57:00 UTC 2009 ** Command line: root=/dev/sda1 ro ** Not tainted ** Kernel log: [ 758.788499] firmware: requesting iwlwifi-3945-1.ucode [ 758.799547] iwl3945: iwlwifi-3945-1.ucode firmware file req failed: Reason -2 [ 758.799560] iwl3945: Could not read microcode: -2 [ 758.799739] ACPI: PCI interrupt for device :0c:00.0 disabled [ 881.501380] ACPI: PCI Interrupt :0c:00.0[A] - GSI 17 (level, low) - IRQ 17 [ 881.504064] PM: Writing back config space on device :0c:00.0 at offset 1 (was 100102, writing 100106) [ 881.504085] firmware: requesting iwlwifi-3945-1.ucode [ 881.513463] iwl3945: iwlwifi-3945-1.ucode firmware file req failed: Reason -2 [ 881.513463] iwl3945: Could not read microcode: -2 [ 881.513463] ACPI: PCI interrupt for device :0c:00.0 disabled [ 1003.973990] ACPI: PCI Interrupt :0c:00.0[A] - GSI 17 (level, low) - IRQ 17 [ 1003.974170] PM: Writing back config space on device :0c:00.0 at offset 1 (was 100102, writing 100106) [ 1003.974485] firmware: requesting iwlwifi-3945-1.ucode [ 1003.983324] iwl3945: iwlwifi-3945-1.ucode firmware file req failed: Reason -2 [ 1003.983324] iwl3945: Could not read microcode: -2 [ 1003.983324] ACPI: PCI interrupt for device :0c:00.0 disabled [ 1127.106704] ACPI: PCI Interrupt :0c:00.0[A] - GSI 17 (level, low) - IRQ 17 [ 1127.106704] PM: Writing back config space on device :0c:00.0 at offset 1 (was 100102, writing 100106) (and a lot more like this) ** Loaded modules: Module Size Used by iwl394592916 0 nls_utf86272 6 cifs 235408 6 nls_base 12932 2 nls_utf8,cifs i915 35072 2 drm91488 3 i915 ppdev 11656 0 parport_pc 31016 0 lp 14724 0 parport41776 3 ppdev,parport_pc,lp ipv6 288328 14 acpi_cpufreq 11792 1 cpufreq_stats 9120 0 cpufreq_powersave 6400 0 cpufreq_conservative11784 0 cpufreq_userspace 8452 0 cpufreq_ondemand 11792 1 freq_table 9344 3 acpi_cpufreq,cpufreq_stats,cpufreq_ondemand sbp2 25356 0 loop 19468 0 snd_hda_intel 434904 1 snd_pcm_oss41760 0 snd_mixer_oss 18816 1 snd_pcm_oss snd_pcm81672 2 snd_hda_intel,snd_pcm_oss arc46272 2 ecb 7296 2 snd_seq_dummy 7428 0 crypto_blkcipher 21636 1 ecb snd_seq_oss33152 0 snd_seq_midi 11072 0 snd_rawmidi26784 1 snd_seq_midi snd_seq_midi_event 11904 2 snd_seq_oss,snd_seq_midi snd_seq54304 6 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event firmware_class 12544 1 iwl3945 snd_timer 25744 2 snd_pcm,snd_seq mac80211 162864 1 iwl3945 snd_seq_device 11668 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq led_class 8968 1 iwl3945 serio_raw 9860 0 i2c_i801 13596 0 snd63688 11 snd_hda_intel,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_device i2c_core 27936 1 i2c_i801 soundcore 12064 1 snd intel_agp 31728 1 iTCO_wdt 15696 0 psmouse42268 0 cfg80211 30224 2 iwl3945,mac80211 pcspkr 7040 0 snd_page_alloc 13072 2 snd_hda_intel,snd_pcm wmi11712 0 battery16904 0 ac 9352 0 video 24212 0 output 7808 1 video button 11680 0 evdev 14208 6 ext3 125072 2 jbd51240 1 ext3 mbcache12804 1 ext3 ide_cd_mod 36360 3 cdrom 37928 1 ide_cd_mod ata_generic10116 0 sd_mod 29376 4 ide_pci_generic 9220 0 [permanent] uhci_hcd 25760 0 ahci 33036 3 libata165472 2 ata_generic,ahci scsi_mod 160760 3 sbp2,sd_mod,libata sdhci 19460 0 piix 12424 0
Bug#493832: ath5k disconnects regularly and has poor performance
It's lots better now. The connection is even more stable than with Madwifi, and WPA2 is functional with my card which was not true with that driver. The tx rate 18 Mbit/s is still quite low for 2,5 m (100 inch) distance and signal/noise (-47/-98 dBm) but it's not bound to 1 Mbit/s as in 2.6.28. The only reasons I still keep Madwifi are master mode and the possibility to force WiFi mode (a/b/g). Or maybe there is already master mode in ath5k and I just fail to set it (tried with the most recent wireless-tools)? -- M. -- A moze Volkswagen z Niemiec? Mamy ponad 180 000 ofert! Sprawdz http://link.interia.pl/f20e5 -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: linux-image-2.6.29-1-amd64: #521691 isn't limited to nforce hardware
Processing commands for cont...@bugs.debian.org: package linux-image-2.6.29-1-amd64 Ignoring bugs not assigned to: linux-image-2.6.29-1-amd64 retitle 521691 fails to reach network a short time after boot Bug#521691: linux-image-2.6.29-1-amd64: Forcedeth network interface fails to reach network a short time after boot Changed Bug title to `fails to reach network a short time after boot' from `linux-image-2.6.29-1-amd64: Forcedeth network interface fails to reach network a short time after boot'. severity 521691 important Bug#521691: fails to reach network a short time after boot Severity set to `important' from `normal' 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#521691: linux-image-2.6.29-1-amd64: #521691 isn't limited to nforce hardware
package linux-image-2.6.29-1-amd64 retitle 521691 fails to reach network a short time after boot severity 521691 important thanks This doesn't seem limited to particular hardware (both nForce and 3c59x affected). Torrenting triggers the bug quite quickly. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#509646: bnx2x firmware licensing
Hi maks, On Mon, Mar 30, 2009 at 05:46:35PM +0200, maximilian attems wrote: hello jsw, please post your bnx2x patch to net...@vger.kernel.org so that it can be reviewed and merged upstream! I was waiting on Eilon's licensing patch to make it into net-next, but I see that it's been there for a week now... I'm working on cleaning up my patch now. Thanks, -- John Wright j...@debian.org -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#509646: bnx2x firmware licensing
Hi Eilon, On Sun, Mar 22, 2009 at 04:17:51AM -0700, Eilon Greenstein wrote: Hi John, You are right - I'm adding a licensing to bnx2x_init_values.h similar to the bnx2 license that you quoted. However, I'm not sure if now is a good time to send such a patch to netdev for net-2.6 so I'm sending it to net-next - please let me know if this is not enough. Thanks! I'm now cleaning up the request_firmware patch to submit upstream. Is the init_ops array part of the firmware data derived from proprietary unpublished source code, or may I take that to be in its preferred form for modification? Thank you, -- John Wright j...@debian.org -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#521712: confirmation
I can also confirm this bug when compiling the not so nice mainstream em28xx code for my usb video devices: $ make running ./build.sh build make[1]: Entering directory `/home/jelle/em28xx-new' rm -rf Module.symvers; make -C /lib/modules/`if [ -d /lib/modules/2.6.21.4-eeepc ]; then echo 2.6.21.4-eeepc; else uname -r; fi`/build SUBDIRS=`pwd` modules make[2]: Entering directory `/usr/src/linux-headers-2.6.29-1-686' /usr/src/linux-headers-2.6.29-1-common/arch/x86/Makefile:41: /usr/src/linux-headers-2.6.29-1-common/arch/x86/Makefile_32.cpu: No such file or directory make[4]: *** No rule to make target `/usr/src/linux-headers-2.6.29-1-common/arch/x86/Makefile_32.cpu'. Stop. make[3]: *** [sub-make] Error 2 make[2]: *** [all] Error 2 make[2]: Leaving directory `/usr/src/linux-headers-2.6.29-1-686' make[1]: *** [default] Error 2 make[1]: Leaving directory `/home/jelle/em28xx-new' Any ideas when this will be fixed? Best regards, Jelle de Jong -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#521472: see also
see also: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=521712 http://packages.debian.org/search?searchon=contentskeywords=Makefile_32.cpumode=exactfilenamesuite=unstablearch=any Beset regards, Jelle de Jong -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#521727: linux-image-2.6-686: desktop app are not responsive (kmail, firefox, OO)
Le 30/03/2009 à 11:46, maximilian attems écrit : concerning preempt and higher hz that is left for dicussion on debian kernel and seems out of topic here. should i fill a new bug tagged wish for a linux-image-desktop ? It _does_ really change the usability with big documents/mail no newer bug won't help, what is needed are benchmark test runs against higher HZ and one for PREEMPT. higher HZ should no longer matter since nohz, so it should be fine for server workloads too, but this needs to be shown. afais HZ_1000 is also the fedora default. I don't know howto benchmark interactivity responsiveness. For me it is obvious change from unusable (OO with big calc and graphic), very laggy (kmail checking new messages) to smooth. If you have a benchmark protocol for debian i'll run it on my laptop (core2duo 1.8 GHz + 3 GB RAM) and send results. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#521712: [linux-headers-2.6.29-1-686] Short resolution
Package: linux-headers-2.6.29-1-686 Version: 2.6.29-1 --- Please enter the report below this line. --- As Google says it seems to be a recurrent error : http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=501995 A quicker fix is to rebuild kernel-headers on your computer from sources: # apt-get install linux-source-2.6.29 # cd /usr/src # tar jxf linux-source-2.6.29.tar.bz2 # cd linux-source-2.6.29 # make-kpkg build kernel_headers ##long long time # dpkg -i linux-header*.deb # cd /usr/src/linux-headers-2.6.26/include/ # rm asm ln -s asm-x86 asm Then you can rebuild you modules. --- System information. --- Architecture: i386 Kernel: Linux 2.6.29-1-686 Debian Release: squeeze/sid 500 unstable ftp.fr.debian.org --- Package information. --- Depends (Version) | Installed ==-+-= linux-headers-2.6.29-1-common (= 2.6.29-1) | 2.6.29-1 linux-kbuild-2.6.29 | 2.6.29-1 gcc-4.3 | 4.3.3-5 -- Encolpe DEGOUTE http://encolpe.degoute.free.fr/ Logiciels libres, hockey sur glace et autres activités cérébrales -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#521615: 2.6.26.8 and hpet=force works
Hello Maximilian, it has to be a debian patch which messes up my system time. I'll figure out some patches of the patchset next days. These snapshots are a great deal (thx), but I first want to find out whats up with this bug. If it can be fixed in Lenny that would be a great thing for many laptop users. Watch out for this network-bug in 2.6.29 which is atm is only fixed in git. This makes ping localhost fail :-O -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#521712: marked as done (linux-headers-2.6.29-1-686: Makefile_32.cpu file missing from header files for x86 architecture)
Your message dated Tue, 31 Mar 2009 00:11:45 +0200 with message-id 20090330221145.gp3...@baikonur.stro.at and subject line Re: Bug#521712: [linux-headers-2.6.29-1-686] Short resolution has caused the Debian Bug report #521712, regarding linux-headers-2.6.29-1-686: Makefile_32.cpu file missing from header files for x86 architecture 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.) -- 521712: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=521712 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-headers-2.6.29-1-686 Version: 2.6.29-1 Severity: normal On installation of the package there should be a file installed /usr/src/linux-headers-2.6.29-1-common/arch/x86/Makefile_32.cpu This file has traditionally contained the cpu tuning information. An extra driver which I use (virtualbox) when compiled with this header refused to compile when I installed 2.6.29 kernel from sid and the related headers. On inspection of the output I found this file is missing. The output on compiling was as follows:- ** Compiling vboxdrv make KBUILD_VERBOSE= -C /lib/modules/2.6.29-1-686/build SUBDIRS=/tmp/vbox.1 SRCROOT=/tmp/vbox.1 modules make -C /usr/src/linux-headers-2.6.29-1-686 \ KBUILD_SRC=/usr/src/linux-headers-2.6.29-1-common \ KBUILD_EXTMOD=/tmp/vbox.1 -f /usr/src/linux-headers-2.6.29-1-common/Makefile \ modules /usr/src/linux-headers-2.6.29-1-common/arch/x86/Makefile:41: /usr/src/linux-headers-2.6.29-1-common/arch/x86/Makefile_32.cpu: No such file or directory make[3]: *** No rule to make target `/usr/src/linux-headers-2.6.29-1-common/arch/x86/Makefile_32.cpu'. Stop. make[2]: *** [sub-make] Error 2 make[1]: *** [all] Error 2 make: *** [vboxdrv] Error 2 My module seems to compile when I put equivalent file from the stock 2.6.26 kernel headers which ships with Lenny release and it seemed to work. Request the maintainers to please put the file so that other people like me building drivers needing the above mentioned file are able to do so. It seems to be missing from the this kernel header package. Thanks for your attention and keep up the excellent work being done by your team. -- System Information: Debian Release: 5.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.29-1-686 (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/bash Versions of packages linux-headers-2.6.29-1-686 depends on: ii gcc-4.3 4.3.2-1.1 The GNU C compiler ii linux-headers-2.6.29-1-common 2.6.29-1 Common header files for Linux 2.6. ii linux-kbuild-2.6.29 2.6.29-1 Kbuild infrastructure for Linux 2. linux-headers-2.6.29-1-686 recommends no packages. linux-headers-2.6.29-1-686 suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- On Mon, Mar 30, 2009 at 11:28:42PM +0200, Encolpe Degoute wrote: Package: linux-headers-2.6.29-1-686 Version: 2.6.29-1 --- Please enter the report below this line. --- As Google says it seems to be a recurrent error : http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=501995 A quicker fix is to rebuild kernel-headers on your computer from sources: # apt-get install linux-source-2.6.29 # cd /usr/src # tar jxf linux-source-2.6.29.tar.bz2 # cd linux-source-2.6.29 # make-kpkg build kernel_headers ##long long time # dpkg -i linux-header*.deb # cd /usr/src/linux-headers-2.6.26/include/ # rm asm ln -s asm-x86 asm Then you can rebuild you modules. closing as duplicate useless submisson. post to a mailinglist if you want to give an howto. kernel-package use is deprecated. ---End Message---
Bug#521943: [linux-image-2.6.29-1-686] system becomes unresponsive due to soft lockup - CPU#0 stuck for 61s!
Package: linux-image-2.6.29-1-686 Version: 2.6.29-1 Severity: important --- Please enter the report below this line. --- After a few hours my laptop is on, the system suddenly becomes near totally unresponsive: the keyboard doesn't work (in particular, I can't switch to tty1 or kill X with Ctrl-Alt-Backspace), the mouse moves, but the clicks are processed with considerable delay (magnitude of minutes). The GNOME interface (panels, applets) are working, so I can see that the CPU usage is constantly to 50% (I'm on a two cores machine, so one core totally used and the other not). I've tried to let the computer alone and without inputs for a couple of hours, but nothing changed when I started again trying to bring it again to normal work. After reboot with Alt-SysRq-B, the syslog contains lots of messages like this: Mar 30 23:58:26 sieff kernel: [14450.420008] BUG: soft lockup - CPU#0 stuck for 61s! [cp:9819] Mar 30 23:58:26 sieff kernel: [14450.420008] Modules linked in: nls_utf8 nls_cp437 vfat fat nls_base usb_storage i915 drm i2c_algo_bit ppdev parport_pc lp parport binfmt_misc cpufreq_stats cpufreq_userspa ce cpufreq_powersave cpufreq_conservative tun fuse ipv6 acpi_cpufreq coretemp eeprom loop dm_crypt dm_mod snd_hda_codec_realtek joydev snd_hda_intel snd_hda_codec snd_hwdep snd_pcm_oss snd_mixer_oss snd_p cm snd_seq_dummy snd_seq_oss snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_timer snd_seq_device snd soundcore i2c_i801 yenta_socket acer_wmi rfkill intel_agp pcspkr i2c_core serio_raw psmouse rs rc_nonstatic snd_page_alloc evdev rng_core wmi battery container agpgart ac video output button ext3 jbd mbcache usbhid hid sg sr_mod cdrom sd_mod crc_t10dif ide_pci_generic ide_core ata_generic ata_piix libata b44 ssb scsi_mod sdhci_pci sdhci uhci_hcd mmc_core pcmcia pcmcia_core mii ehci_hcd led_class usbcore thermal processor fan thermal_sys [last unloaded: v4l1_compat] Mar 30 23:58:26 sieff kernel: [14450.420008] Mar 30 23:58:26 sieff kernel: [14450.420008] Pid: 9819, comm: cp Not tainted (2.6.29-1-686 #1) Aspire 5610Z Mar 30 23:58:26 sieff kernel: [14450.420008] EIP: 0060:[c01ff4be] EFLAGS: 00010246 CPU: 0 Mar 30 23:58:26 sieff kernel: [14450.420008] EIP is at __copy_from_user_ll_nocache_nozero+0x21/0x2c Mar 30 23:58:26 sieff kernel: [14450.420008] EAX: f76ff000 EBX: 1000 ECX: 0400 EDX: Mar 30 23:58:26 sieff kernel: [14450.420008] ESI: 09a7b000 EDI: f76ff000 EBP: ESP: e865ddbc Mar 30 23:58:26 sieff kernel: [14450.420008] DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068 Mar 30 23:58:26 sieff kernel: [14450.420008] CR0: 8005003b CR2: f76ff000 CR3: 2bafd000 CR4: 06d0 Mar 30 23:58:26 sieff kernel: [14450.420008] DR0: DR1: DR2: DR3: Mar 30 23:58:26 sieff kernel: [14450.420008] DR6: 0ff0 DR7: 0400 Mar 30 23:58:26 sieff kernel: [14450.420008] Call Trace: Mar 30 23:58:26 sieff kernel: [14450.420008] [c01663ce] iov_iter_copy_from_user_atomic+0x4d/0xa5 Mar 30 23:58:26 sieff kernel: [14450.420008] [c016763c] generic_file_buffered_write+0xe1/0x270 Mar 30 23:58:26 sieff kernel: [14450.420008] [c0167665] generic_file_buffered_write+0x10a/0x270 Mar 30 23:58:26 sieff kernel: [14450.420008] [c0167c05] __generic_file_aio_write_nolock+0x265/0x28d Mar 30 23:58:26 sieff kernel: [14450.420008] [c02e84cb] _spin_lock+0x5/0x7 Mar 30 23:58:26 sieff kernel: [14450.420008] [c02e84cb] _spin_lock+0x5/0x7 Mar 30 23:58:26 sieff kernel: [14450.420008] [c016845d] generic_file_aio_write+0x5d/0xb4 Mar 30 23:58:26 sieff kernel: [14450.420008] [c0188652] do_sync_write+0xc0/0x107 Mar 30 23:58:26 sieff kernel: [14450.420008] [c013ad95] sched_clock_cpu+0x136/0x147 Mar 30 23:58:26 sieff kernel: [14450.420008] [c011e23c] pick_next_task_fair+0x80/0x87 Mar 30 23:58:26 sieff kernel: [14450.420008] [c0136d6a] autoremove_wake_function+0x0/0x2d Mar 30 23:58:26 sieff kernel: [14450.420008] [c02e728b] schedule+0x6dd/0x754 Mar 30 23:58:26 sieff kernel: [14450.420008] [c01d1d68] security_file_permission+0xc/0xd Mar 30 23:58:26 sieff kernel: [14450.420008] [c0188592] do_sync_write+0x0/0x107 Mar 30 23:58:26 sieff kernel: [14450.420008] [c0188e78] vfs_write+0x7e/0xd6 Mar 30 23:58:26 sieff kernel: [14450.420008] [c0188f68] sys_write+0x3c/0x63 Mar 30 23:58:26 sieff kernel: [14450.420008] [c010343b] sysenter_do_call+0x12/0x2f Mar 30 23:58:26 sieff kernel: [14450.420008] [c02e] pci_fixup_video+0x0/0x93 I'm not able to understand what they mean. They seem to be sent out on an average of once every one or two minutes, for the entire interval during which the system is unresponsive. I hope this annoying but to be fixed as soon as possible! Thank you for your work on Debian and Linux. :-) Regards, Giovanni. --- System information. --- Architecture: i386 Kernel: Linux 2.6.29-1-686 Debian Release: squeeze/sid 500 unstable
Bug#509646: bnx2x firmware licensing
On Mon, 30 Mar 2009, John Wright wrote: On Mon, Mar 30, 2009 at 05:46:35PM +0200, maximilian attems wrote: hello jsw, please post your bnx2x patch to net...@vger.kernel.org so that it can be reviewed and merged upstream! I was waiting on Eilon's licensing patch to make it into net-next, but I see that it's been there for a week now... I'm working on cleaning up my patch now. please don't wait on such upstream merge take anyway already quite some time, once something is in linux-next you can assume it merged. kind regards -- maks -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#521944: linux-image-2.6.29-1-686: Excessive number of interrupts from hrtimer_start_expires
Package: linux-image-2.6.29-1-686 Version: 2.6.29-1 Severity: normal Running powertop on the 2.6.29-1 kernel gets me the following Top causes for wakeups: 50.8% (126.3) kernel core : hrtimer_start_expires (tick_sched_timer) 12.8% ( 31.7) kernel IPI : Rescheduling interrupts 7.4% ( 18.5) interrupt : uhci_hcd:usb3, ath 5.3% ( 13.1) interrupt : ata_piix 4.4% ( 10.9) interrupt : extra timer interrupt Previously, the major cause of interrupts had been the kernel IPI, and hence one reason for upgrading to the latest kernel version. Now there's hrtimer_start_expires, and quite frankly this is a median case - I've seen it hit as high as 500 interrupts/second occasionally. This is causing my battery to get drained at an accelerated rate and I don't think this is correct behaviour. -- Package-specific info: ** Version: Linux version 2.6.29-1-686 (Debian 2.6.29-1) (wa...@debian.org) (gcc version 4.3.3 (Debian 4.3.3-5) ) #1 SMP Tue Mar 24 23:05:52 UTC 2009 ** Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.29-1-686 root=UUID=1d2ed566-a39a-423f-8a96-59206e41336e ro quiet ** Not tainted ** Kernel log: [ 913.817857] pci :04:00.3: restoring config space at offset 0x1 (was 0x10, writing 0x17) [ 913.817857] pci :04:00.4: restoring config space at offset 0xf (was 0x1ff, writing 0x10b) [ 913.817857] pci :04:00.4: restoring config space at offset 0x4 (was 0x0, writing 0x5410) [ 913.817857] pci :04:00.4: restoring config space at offset 0x1 (was 0x10, writing 0x17) [ 913.820542] Enabling non-boot CPUs ... [ 913.821353] SMP alternatives: switching to SMP code [ 914.363428] Booting processor 1 APIC 0x1 ip 0x6000 [ 913.816617] Initializing CPU#1 [ 913.816617] Calibrating delay using timer specific routine.. 3192.03 BogoMIPS (lpj=6384069) [ 913.816617] CPU: L1 I cache: 32K, L1 D cache: 24K [ 913.816617] CPU: L2 cache: 512K [ 913.816617] [ds] using Core 2/Atom configuration [ 913.816617] CPU: Physical Processor ID: 0 [ 913.816617] CPU: Processor Core ID: 0 [ 913.816617] Intel machine check architecture supported. [ 913.816617] Intel machine check reporting enabled on CPU#1. [ 914.452394] CPU1: Intel(R) Atom(TM) CPU N270 @ 1.60GHz stepping 02 [ 914.452572] CPU0 attaching NULL sched-domain. [ 914.453038] Switched to high resolution mode on CPU 1 [ 914.464581] CPU0 attaching sched-domain: [ 914.464587] domain 0: span 0-1 level SIBLING [ 914.464591] groups: 0 1 [ 914.464600] CPU1 attaching sched-domain: [ 914.464604] domain 0: span 0-1 level SIBLING [ 914.464607] groups: 1 0 [ 914.469032] CPU1 is up [ 914.469037] ACPI: Waking up from system sleep state S3 [ 914.500538] pci :00:02.0: PME# disabled [ 914.500560] pci :00:02.0: PCI INT A - GSI 16 (level, low) - IRQ 16 [ 914.500571] pci :00:02.0: setting latency timer to 64 [ 914.500581] pci :00:02.1: PME# disabled [ 914.500659] HDA Intel :00:1b.0: PCI INT A - GSI 16 (level, low) - IRQ 16 [ 914.500671] HDA Intel :00:1b.0: setting latency timer to 64 [ 914.500712] pcieport-driver :00:1c.0: setting latency timer to 64 [ 914.500728] pcieport-driver :00:1c.1: setting latency timer to 64 [ 914.500744] pcieport-driver :00:1c.2: setting latency timer to 64 [ 914.500759] pcieport-driver :00:1c.3: setting latency timer to 64 [ 914.500813] uhci_hcd :00:1d.0: PCI INT A - GSI 16 (level, low) - IRQ 16 [ 914.500825] uhci_hcd :00:1d.0: setting latency timer to 64 [ 914.500859] usb usb1: root hub lost power or was reset [ 914.500919] uhci_hcd :00:1d.1: PCI INT B - GSI 17 (level, low) - IRQ 17 [ 914.500932] uhci_hcd :00:1d.1: setting latency timer to 64 [ 914.500964] usb usb2: root hub lost power or was reset [ 914.501047] uhci_hcd :00:1d.2: PCI INT C - GSI 18 (level, low) - IRQ 18 [ 914.501063] uhci_hcd :00:1d.2: setting latency timer to 64 [ 914.501104] usb usb3: root hub lost power or was reset [ 914.501165] uhci_hcd :00:1d.3: PCI INT D - GSI 19 (level, low) - IRQ 19 [ 914.501177] uhci_hcd :00:1d.3: setting latency timer to 64 [ 914.501210] usb usb4: root hub lost power or was reset [ 914.501288] ehci_hcd :00:1d.7: PME# disabled [ 914.501299] ehci_hcd :00:1d.7: PCI INT A - GSI 16 (level, low) - IRQ 16 [ 914.501311] ehci_hcd :00:1d.7: setting latency timer to 64 [ 914.501324] ehci_hcd :00:1d.7: PME# disabled [ 914.501368] pci :00:1e.0: setting latency timer to 64 [ 914.501432] ata_piix :00:1f.2: PCI INT B - GSI 17 (level, low) - IRQ 17 [ 914.501443] ata_piix :00:1f.2: setting latency timer to 64 [ 914.501651] r8169 :02:00.0: PME# disabled [ 914.501843] ath5k :03:00.0: PCI INT A - GSI 18 (level, low) - IRQ 18 [ 914.529635] sdhci-pci :04:00.0: restoring config space at offset 0xc (was 0x0, writing 0x8000) [ 914.529729] sdhci-pci :04:00.0: PCI INT A - GSI 19 (level, low) - IRQ 19 [ 914.529756] sdhci-pci :04:00.0: setting latency timer to 64
Bug#521712: This really is a bug.
linux-headers-2.6.29-1-686 is missing all the symlinks to linux-headers-2.6.29-1-common. For example: # ls -l /lib/modules/2.6.26-2-686/build/include/linux/agp_backend.h lrwxrwxrwx 1 root root 66 Mar 30 19:30 /lib/modules/2.6.26-2-686/build/include/linux/agp_backend.h - ../../../linux-headers-2.6.26-2-common/include/linux/agp_backend.h # ls -l /lib/modules/2.6.29-1-686/build/include/linux/agp_backend.h ls: cannot access /lib/modules/2.6.29-1-686/build/include/linux/agp_backend.h: No such file or directory # ls -l /usr/src/linux-headers-2.6.29-1-common/include/linux/agp_backend.h -rw-r--r-- 1 root root 3579 Mar 23 19:12 /usr/src/linux-headers-2.6.29-1-common/include/linux/agp_backend.h This breaks anything that tries to access the kernel headers that the /lib/modules/version/build is supposed to point to. The linux-headers for 2.6.29 are severely broken it seems. Just because someone posts a potential workaround (which really had nothing to do with it) doesn't mean the original bug isn't in fact a bug. -- Len Sorensen -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#521712: More info
OK, so I see now that the symlinks from the past release are no longer used due to new magic Makefile stuff. Rather neat. However as the original bug says, Makefile_32.cpu is in fact missing from linux-headers-2.6.29-1-common, which breaks i386. amd64 doesn't need it and hence works fine. Copying in the missing file makes drm-modules compile perfectly using module-assistant. Without it, you get an error from make about the missing include for Makefile_32.cpu -- Len Sorensen -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#521515: linux-headers-2.6.29-1-amd64: please restore symlinks into -common
On Sat, Mar 28, 2009 at 11:28:07PM +0100, Bastian Blank wrote: severity 521515 wishlist tags 521515 wontfix thanks On Fri, Mar 27, 2009 at 09:02:04PM -0400, Aaron M. Ucko wrote: As of 2.6.29-1, that no longer holds, causing trouble for packages such as openafs-modules-source that don't entirely defer to the kbuild framework. There is no reliable way to detect the include paths of the kernel without using kbuild. but would appreciate it if you could please reinstate the symlinks in the flavor-specific linux-headers packages. Nope. At least not until you show that it breaks the _documented_ usage. Out of couriosity (and to try and fix the nvidia driver build system)... Documented by who? Debian or the linux kernel? It seems openafs, vmware, nvidia, and probably many others, rely on the idea that there is a single directory with all the kernel headers as configured for the current running kernel in /lib/modules/version/build/, which was true up until the debian 2.6.29 linux-headers got released. So did this change improve anything? It certainly has made a lot of work for a lot of people for what appears to have no benefit so far. So where is the correct way to use kernel headers documented? -- Len Sorensen -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#517449: Experiencing this problem also
I experienced this problem on a machine with 12gigs of memory when I added a failed disk back into a mdadm array, output included below. The machine basically was totally frozen for 10 minutes or so until the raid array finished its sync, and then everything returned to normal. Pretty ugly, would love to see this merged in to a lenny kernel. I got pages and pages of the following, so I'm only showing the end: [1540865.693902] INFO: task sshd:15082 blocked for more than 120 seconds. [1540865.693956] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. [1540865.694002] sshd D ed0b2780 0 15082 23253 [1540865.694077]ec4450c0 00200282 c018d895 ed0b2780 c01b7f2e ec445248 c153fb40 0003 [1540865.694213]ec5cb080 ec4450c0 16ed73c7 ed43eacc ec44530c eccad200 c1679020 [1540865.694361]ed1cc0d4 c018d8c6 2c2c e7f11d8c c7fb7dbc [1540865.694509] Call Trace: [1540865.694576] [c018d895] __find_get_block+0x198/0x1a2 [1540865.694636] [c01b7f2e] security_inode_alloc+0x16/0x17 [1540865.694704] [c018d8c6] __getblk+0x27/0x26f [1540865.694757] [ee1ef6a0] do_get_write_access+0x1b6/0x367 [jbd] [1540865.694829] [c012ec51] wake_bit_function+0x0/0x3c [1540865.694882] [ee1ef869] journal_get_write_access+0x18/0x26 [jbd] [1540865.694942] [ee22e5df] __ext3_journal_get_write_access+0x13/0x32 [ext3] [1540865.695012] [ee2237e2] ext3_reserve_inode_write+0x2d/0x5d [ext3] [1540865.695067] [ee223823] ext3_mark_inode_dirty+0x11/0x27 [ext3] [1540865.695132] [ee225fcc] ext3_dirty_inode+0x50/0x63 [ext3] [1540865.695194] [c018a3f5] __mark_inode_dirty+0x21/0x148 [1540865.695245] [c0181c29] touch_atime+0xc7/0xce [1540865.695294] [c015022c] generic_file_aio_read+0x493/0x4da [1540865.695370] [c016fd62] do_sync_read+0xbf/0xfe [1540865.695436] [c012ec24] autoremove_wake_function+0x0/0x2d [1540865.695495] [ee230a51] ext3_xattr_security_get+0x31/0x3b [ext3] [1540865.695562] [c01b7f6f] security_file_permission+0xc/0xd [1540865.695621] [c016fca3] do_sync_read+0x0/0xfe [1540865.695674] [c01704ea] vfs_read+0x81/0x11e [1540865.695724] [c01738d4] kernel_read+0x32/0x43 [1540865.695775] [c01739a5] prepare_binprm+0xc0/0xc4 [1540865.695827] [c0174960] do_execve+0xd2/0x1c6 [1540865.695879] [c0102366] sys_execve+0x2a/0x4a [1540865.695926] [c0103f76] syscall_call+0x7/0xb [1540865.695988] [c02c] pci_bus_size_bridges+0x32a/0x3a0 [1540865.696044] === [1540869.985790] INFO: task sshd:15078 blocked for more than 120 seconds. [1540869.985845] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. [1540869.988032] sshd D ed0b2780 0 15078 23253 [1540869.988110]ec4af140 00200286 c018d895 ed0b2780 c01b7f2e ec4af2c8 c153fb40 0003 [1540869.988236]eca48300 ec4af140 16ecfe8f ed43eacc ec4af38c eccad200 c1679020 [1540869.988379]ed1cc0d4 c018d8c6 2929 ec38dd8c c7fb7dbc [1540869.988529] Call Trace: [1540869.988595] [c018d895] __find_get_block+0x198/0x1a2 [1540869.988653] [c01b7f2e] security_inode_alloc+0x16/0x17 [1540869.988720] [c018d8c6] __getblk+0x27/0x26f [1540869.988772] [ee1ef6a0] do_get_write_access+0x1b6/0x367 [jbd] [1540869.988847] [c012ec51] wake_bit_function+0x0/0x3c [1540869.988899] [ee1ef869] journal_get_write_access+0x18/0x26 [jbd] [1540869.988960] [ee22e5df] __ext3_journal_get_write_access+0x13/0x32 [ext3] [1540869.989033] [ee2237e2] ext3_reserve_inode_write+0x2d/0x5d [ext3] [1540869.989093] [ee223823] ext3_mark_inode_dirty+0x11/0x27 [ext3] [1540869.989159] [ee225fcc] ext3_dirty_inode+0x50/0x63 [ext3] [1540869.989218] [c018a3f5] __mark_inode_dirty+0x21/0x148 [1540869.989276] [c0181c29] touch_atime+0xc7/0xce [1540869.989326] [c015022c] generic_file_aio_read+0x493/0x4da [1540869.989384] [c016fd62] do_sync_read+0xbf/0xfe [1540869.989384] [c012ec24] autoremove_wake_function+0x0/0x2d [1540869.989384] [ee230a51] ext3_xattr_security_get+0x31/0x3b [ext3] [1540869.989384] [c01b7f6f] security_file_permission+0xc/0xd [1540869.989384] [c016fca3] do_sync_read+0x0/0xfe [1540869.989384] [c01704ea] vfs_read+0x81/0x11e [1540869.989384] [c01738d4] kernel_read+0x32/0x43 [1540869.989384] [c01739a5] prepare_binprm+0xc0/0xc4 [1540869.989384] [c0174960] do_execve+0xd2/0x1c6 [1540869.989384] [c0102366] sys_execve+0x2a/0x4a [1540869.989384] [c0103f76] syscall_call+0x7/0xb [1540869.989384] [c02c] pci_bus_size_bridges+0x32a/0x3a0 [1540869.989384] === [1540874.198475] md: md2: recovery done. Login timed out after 60 seconds. [1540874.405091] RAID1 conf printout: [1540874.405173] --- wd:2 rd:3 [1540874.405210] disk 0, wo:0, o:1, dev:sdb4 [1540874.405260] disk 1, wo:0, o:1, dev:sdc4 Debian GNU/Linux 5.0 waxwing hvc0 signature.asc Description: Digital signature
