Bug#635341: eth0 unavailable after standby until reload of e1000e
I'd give a rough estimate the malfunctioning-eth0 bug happens around half the time on resume from standby. Installing 3.0 kernel now for testing purposes.
Bug#635653: [linux-2.6] Please pick: iwlagn: check for !priv-txq in iwlagn_wait_tx_queue_empty
On Thursday 28 July 2011 00:23:00 you wrote:
Does the following work? It has been applied upstream and will
probably be part of v3.1-rc1.
Short version: Yes it works, but the patch did not apply to the curren
linux-source package.
Long Version:
I tried to apply the patch, but it seemed to be for a different version
than that of linux-source-3.0.0 version 3.0.0-1, so I had to apply it by
hand (not using git that is). See below for my diff (). Then I
configured and compiled the kernel with
make localmodconfig
make clean
make -j 3 KDEB_PKGVERSION=3.0.0-mac80211.1 deb-pkg
and installed it with
dpkg -i linux-image-3.0.0_3.0.0-mac80211.1_amd64.deb.
(It looks like I choose a wrong name for the version here because the
installation didn't do what I hoped -- to have a separate entry in the
boot loader -- and I had to remove linux-image-3.0.0-1-amd64 for it to
work out.)
Then I rebooted into runlevel 1 and tried to suspend a few times by
writing mem\n to /sys/power/state. It never failed.
BTW: Here is a workaround, for those with the same problem and installed
pm-utils package. Add the following line to a file in /etc/pm/config.d
(e.g. iwlagn):
SUSPEND_MODULES=iwlagn
Kind regards,
Florian.
diff -Ntaur linux-source-3.0.0-orig//net/mac80211/pm.c
linux-source-3.0.0/net/mac80211/pm.c
--- linux-source-3.0.0-orig//net/mac80211/pm.c 2011-07-22 04:17:23.0
+0200
+++ linux-source-3.0.0/net/mac80211/pm.c 2011-07-28 09:12:00.303443535 +0200
@@ -12,6 +12,9 @@
struct ieee80211_sub_if_data *sdata;
struct sta_info *sta;
+if (!local-open_count)
+goto suspend;
+
ieee80211_scan_cancel(local);
if (hw-flags IEEE80211_HW_AMPDU_AGGREGATION) {
diff -Ntaur linux-source-3.0.0-orig//net/mac80211/util.c
linux-source-3.0.0/net/mac80211/util.c
--- linux-source-3.0.0-orig//net/mac80211/util.c 2011-07-22 04:17:23.0
+0200
+++ linux-source-3.0.0/net/mac80211/util.c 2011-07-28 09:23:56.442994666 +0200
@@ -1146,26 +1146,36 @@
}
#endif
-/* restart hardware */
-if (local-open_count) {
-/*
- * Upon resume hardware can sometimes be goofy due to
- * various platform / driver / bus issues, so restarting
- * the device may at times not work immediately. Propagate
- * the error.
- */
-res = drv_start(local);
-if (res) {
-WARN(local-suspended, Hardware became unavailable
- upon resume. This could be a software issue
- prior to suspend or a hardware issue.\n);
-return res;
-}
+/* setup fragmentation threshold */
+drv_set_frag_threshold(local, hw-wiphy-frag_threshold);
+
+/* setup RTS threshold */
+drv_set_rts_threshold(local, hw-wiphy-rts_threshold);
+
+/* reset coverage class */
+drv_set_coverage_class(local, hw-wiphy-coverage_class);
-ieee80211_led_radio(local, true);
-ieee80211_mod_tpt_led_trig(local,
- IEEE80211_TPT_LEDTRIG_FL_RADIO, 0);
+/* everything else happens only if HW was up running */
+if (!local-open_count)
+goto wake_up;
+
+/*
+* Upon resume hardware can sometimes be goofy due to
+* various platform / driver / bus issues, so restarting
+* the device may at times not work immediately. Propagate
+* the error.
+*/
+res = drv_start(local);
+if (res) {
+WARN(local-suspended, Hardware became unavailable
+ upon resume. This could be a software issue
+ prior to suspend or a hardware issue.\n);
+return res;
}
+
+ieee80211_led_radio(local, true);
+ieee80211_mod_tpt_led_trig(local,
+ IEEE80211_TPT_LEDTRIG_FL_RADIO, 0);
/* add interfaces */
list_for_each_entry(sdata, local-interfaces, list) {
@@ -1190,12 +1200,6 @@
}
mutex_unlock(local-sta_mtx);
-/* setup fragmentation threshold */
-drv_set_frag_threshold(local, hw-wiphy-frag_threshold);
-
-/* setup RTS threshold */
-drv_set_rts_threshold(local, hw-wiphy-rts_threshold);
-
/* reconfigure hardware */
ieee80211_hw_config(local, ~0);
Bug#568008: FATAL: Error inserting padlock_sha: No such device
Hi everyone, are there any updates on this? With current Debian testing (Kernel 2.6.39), I am still getting this error on boot: FATAL: Error inserting padlock_sha (/lib/modules/2.6.39-2- amd64/kernel/drivers/crypto/padlock-sha.ko): No such device I understand it is harmless, but it should still be fixed since it irritates users suggesting something is seriously going wrong. Kind regards, Ralf -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201107281137.18506.ralfjun...@gmx.de
Bug#485070: FATAL: Error inserting padlock_sha: No such device
found 485070 linux-2.6/2.6.39-3 quit Hi, Ben Hutchings wrote: This shouldn't be a problem - all modules will be loaded and the best one for the hardware will be used. We should stop padlock-aes printing an error message in this case though. Ralf Jung wrote: are there any updates on this? With current Debian testing (Kernel 2.6.39), I am still getting this error on boot: FATAL: Error inserting padlock_sha (/lib/modules/2.6.39-2- amd64/kernel/drivers/crypto/padlock-sha.ko): No such device I understand it is harmless, but it should still be fixed since it irritates users suggesting something is seriously going wrong. Could you please report this to linux-cry...@vger.kernel.org, cc-ing this bug and Jeremy Katz ka...@redhat.com, ideally with a patch to drivers/crypto/padlock-aes.c? Thanks for your interest. Jonathan -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110728101752.GB6991@elie
Processed: Re: FATAL: Error inserting padlock_sha: No such device
Processing commands for cont...@bugs.debian.org: found 485070 linux-2.6/2.6.39-3 Bug #485070 [linux-2.6] cryptsetup: strange padlock_aes error during boot Bug #509700 [linux-2.6] kernel: modules:padlock-aes.ko trying exception Bug #540734 [linux-2.6] padlock: Error inserting padlock_aes (/lib/modules/2.6.26-2-686/kernel/drivers/crypto/padlock-aes.ko) Bug #541289 [linux-2.6] padlock: Starting MTA [ 35.356507] padlock: VIA PadLock not detected. Bug #566309 [linux-2.6] linux-image-2.6.30-2-686: aes.ko depends on device specific padlock-aes.ko Bug #568008 [linux-2.6] linux-image-2.6.32-trunk-amd64: Error inserting padlock_sha: No such device Bug Marked as found in versions linux-2.6/2.6.39-3. Bug Marked as found in versions linux-2.6/2.6.39-3. Bug Marked as found in versions linux-2.6/2.6.39-3. Bug Marked as found in versions linux-2.6/2.6.39-3. Bug Marked as found in versions linux-2.6/2.6.39-3. Bug Marked as found in versions linux-2.6/2.6.39-3. quit Stopping processing here. Please contact me if you need assistance. -- 485070: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=485070 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.131184830116222.transcr...@bugs.debian.org
Building udebs from linux-2.6
Otavio is happy for us to start building kernel udebs from linux-2.6, with the following provisos: 1. Installer team members (initially Otavio, Joey and Colin) will need commit access, to update the module selections for udebs. 2. The automatic inclusion of module dependencies sometimes results in a module being selected for multiple packages. kernel-wedge does not attempt to resolve this, and treats it as a fatal error. It should be turned into a warning when building linux-2.6 for experimental. 3. The kernel team proposed to specify the modules to be included in each udeb using wildcards. He is wary about this because currently the explicit lists of modules provide a useful check that modules have not been unexpectedly removed. (This sometimes happens due to introduction of new kconfig variables without sane defaults.) We need to check for this in some way. Also, to allow for very memory-constrained systems we will still need to specify explicit lists for some packages and flavours. Wildcards should then not match modules that were explicitly listed in another package. Finally, it may be useful to create a misc-modules udeb that would include all modules not explicitly included anywhere else or explicitly excluded. 4. kernel-wedge must remain a separate package, as it is also used for the FreeBSD kernel. Ben. signature.asc Description: This is a digitally signed message part
Changes to Debian Installer release process
I used some of Debcamp and Debconf time this year to discuss the Debian Installer release process with some people and after talking with many people it seems we agreed on the following changes on Debian Installer release process and it would be interesting to receive feedback on those to see if anyone see a problem we didn't notice yet. * Official uploads to be built against unstable Currently when we do a source upload of debian-installer it gather all build-depends on /unstable/ but the udebs from /testing/. We want to get it change and all udebs be fetched from unstable so we will migrate it all to testing when ready and not before building as done currently. This is going to make easier to Debian Installer and Debian Release teams to coordinate the migration of packages to testing. Philipp will send a mail regarding this with more details later. * Linux kernel udebs to be built from linux source package We won't get rid of kernel-wedge instead linux source package will use it during the build process to produce all the kernel udebs from it. Ben will send a mail about this later with a more detailed description. * Debian Installer daily builds to be done from source uploads The daily builds will use the archive source for building so every time we do a change in unstable in a module that is included in initrd it will trigger a binNMU in all architectures replicating what we have in daily builds. When source changes in debian-installer source package are done, a new source upload will be required. * Debian Installer experimental builds With Linux kernel udebs built from linux source we have the possibility to get the installer built against the development kernel that will be available on experimental and this is quite important to us to be able to test all this before it is available in unstable to avoid bad surprises for us and users. This will also be a handy tool for us to play with not well tested or finished stuff without breaking installer to end users. For now, I think we will need to use an infra-structure similar of what we have today for daily builds for those. * Use of britney to handle package and installer migration This is the end of the process and some details are yet unknown how this is going to happen however but our goal is to make it happen since it will alleviate a lot the amount of work to make Debian Installer release to happen. It is important to notice that it is not a single-man effort but a coordinate and shared effort of Debian Kernel, Debian Release and Debian Installer teams to get all this done. Those changes are not going to happen at once but in a progressive process and at the end this is going to make the installer release process easier to understand and handle. Please share your ideas regarding those proposed changes so we can start looking on the required changes to accomplish all this. Thanks in advance, Regards, -- Otavio Salvador ota...@debian.org -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/cap9odko9_21zxolagenchnte8+xc1p4xr6vxnavugqcwekb...@mail.gmail.com
Re: Building udebs from linux-2.6
On Thu, Jul 28, 2011 at 12:50:11PM +0200, Ben Hutchings wrote: 1. Installer team members (initially Otavio, Joey and Colin) will need commit access, to update the module selections for udebs. As long as they don't break it, well. 2. The automatic inclusion of module dependencies sometimes results in a module being selected for multiple packages. kernel-wedge does not attempt to resolve this, and treats it as a fatal error. It should be turned into a warning when building linux-2.6 for experimental. I don't see a way to detect that from the source. He is wary about this because currently the explicit lists of modules provide a useful check that modules have not been unexpectedly removed. (This sometimes happens due to introduction of new kconfig variables without sane defaults.) We need to check for this in some way. Did this problem break hell loose in the past? I can't remember anything. However we could make this part of the ABI, which we check anyway. 4. kernel-wedge must remain a separate package, as it is also used for the FreeBSD kernel. Well. I don't see much that would survive. The control generation and the module selection is not. Bastian -- Violence in reality is quite different from theory. -- Spock, The Cloud Minders, stardate 5818.4 -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110728113926.ga31...@wavehammer.waldi.eu.org
Bug#485070: cryptsetup: FATAL padlock_{aes,sha} error during boot
Hi, as per request of Jonathan at http://bugs.debian.org/cgi- bin/bugreport.cgi?bug=485070, I am reporting the mentioned bug to this list as well: With current Debian testing (Kernel 2.6.39), I am getting this error on each boot: FATAL: Error inserting padlock_sha (/lib/modules/2.6.39-2- amd64/kernel/drivers/crypto/padlock-sha.ko): No such device I understand it is harmless, but it should still be fixed since it irritates users suggesting something is seriously going wrong. No patch though, sorry, compiling and botting a custom kernel still sounds like black magic for me ;-) Kind regards, Ralf -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201107281403.27224.ralfjun...@gmx.de
Bug#578477: crashes after several days of use
Hi Jonathan, Am 28.07.2011 03:02, schrieb Jonathan Nieder: Sorry we took so long to get to this. Basic questions: From memory, as the machine in question is currently mothballed. - have you experienced the crashes on more than one machine? Do you know of anyone else having experienced it? No, I only have a single PagasosII machine. - do only a few lists of functions show up in such backtraces or do they seem arbitrary? The top of the stack is always the same; entry into the block/LVM code comes from different paths. - did the problems start after an upgrade? If so, what was the last working and first nonworking version? That is difficult to tell, as several versions prior to this one would panic in the Marvell Ethernet driver. - how have you been coping since then? Is there a workaround that could shed light on this? I have switched to another machine. Given sufficient time, I might get around to retrying it on the PegasosII; if there is a motivated developer who might want such a box, I'd also be prepared to give the machine away to good hands. - if you're able to boot with some version, could you attach a full kernel log and bugscript output (which includes lspci info, etc)? Difficult right now. The machine is a standard PegasosII, with Radeon 9200SE graphics, an Exsys EX-1065 USB expander card (NEC chipset) and a Cologne Chip ISDN card. Simon -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e315717.2050...@debian.org
Bug#635362: Realtek ALC889: HDA Intel and kernel 3.0 gives choppy sound
Le 27/07/2011 16:50, Takashi Iwai a écrit : [...] Thanks. Could you try the patch below against 3.0 tree? [...] It works just fine, now waiting forward Debian to patch their tree :) Thanks a lot for all the good work! Regards, Colomban -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e315e2f.3090...@herbesfolles.org
Bug#635362: Realtek ALC889: HDA Intel and kernel 3.0 gives choppy sound
At Thu, 28 Jul 2011 15:03:43 +0200, Colomban Wendling wrote: Le 27/07/2011 16:50, Takashi Iwai a écrit : [...] Thanks. Could you try the patch below against 3.0 tree? [...] It works just fine, now waiting forward Debian to patch their tree :) Thanks a lot for all the good work! Good to hear. The patch was tagged to stable-kernel, so it'll be likely included in 3.0.1 kernel. thanks, Takashi -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/s5hwrf28skc.wl%ti...@suse.de
Bug#630730: linux-image-2.6.32: GSO IPv6 issues
On Tue, Jun 21, 2011 at 08:32:04PM -0700, David Miller wrote: From: Ben Hutchings b...@decadent.org.uk Date: Wed, 22 Jun 2011 04:20:13 +0100 David, these look like good candidates for longterm updates. What do you think? Sure but I don't do submissions for the longterm stuff, I only work on the -stable trees that Greg is actively maintaining. What's the status of this? Have the patches been forwarded to -longterm maintainers? (is that Greg KH?); if not, I'd be happy to do it for you. Best regards, Faidon -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110728144858.ga9...@tty.gr
Bug#635770: linux-image-3.0.0-1-686-pae: sis900 eth driver oopses at seemingly random times
Package: linux-2.6 Version: 3.0.0-1 Severity: important Tags: experimental hi, so at random times, the driver will just oops with (below), and then the network just conks out, unable to do anything. when i remove it (modprobe -r) after bringing it down, and back up, it's extremely slow (see below kernel oops message). start [ cut here ] WARNING: at /build/buildd-linux-2.6_3.0.0-1-i386-ML66CU/linux-2.6-3.0.0/debian/build/source_i386_none/net /sched/sch_generic.c:255 dev_watchdog+0xb1/0x104() Hardware name: System Name NETDEV WATCHDOG: eth0 (sis900): transmit queue 0 timed out Modules linked in: microcode fuse rpcsec_gss_krb5 nfsd nfs lockd fscache auth_rpcgss nfs_acl sunrpc nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables nf_conntrack_ipv4 nf_defrag_ipv4 xt_state nf_conntrack iptable_filter ip_tables x_tables fan thermal radeonfb radeon ttm drm_kms_helper power_supply asb100 hwmon_vid snd_cmipci gameport snd_usb_audio snd_pcm_oss snd_usbmidi_lib snd_mixer_oss snd_pcm snd_page_alloc snd_opl3_lib snd_hwdep snd_mpu401_uart snd_seq_midi snd_rawmidi gspca_zc3xx gspca_main snd_seq_midi_event evdev snd_seq videodev media snd_timer snd_seq_device snd serio_raw soundcore i2c_sis96x parport_pc parport shpchp pci_hotplug button processor via_rhine loop i2c_dev i2c_algo_bit nls_ascii nls_iso8859_1 nls_utf8 vgastate fb_ddc drm i2c_core thermal_sys usb_storage dm_snapshot dm_mirror dm_region_hash dm_log dm_mod ext4 jbd2 crc16 ext3 jbd mbcache usbhid hid sg sr_mod sd_mod cdrom crc_t10dif ata_generic pata_sis libata floppy ohci_hcd ehci_hcd scsi_mod us bcore sis900 mii [last unloaded: scsi_wait_scan] Pid: 1759, comm: ifconfig Not tainted 3.0.0-1-686-pae #1 Call Trace: [c10360c1] ? warn_slowpath_common+0x6a/0x7d [c1223d50] ? dev_watchdog+0xb1/0x104 [c103613a] ? warn_slowpath_fmt+0x28/0x2c [c1223d50] ? dev_watchdog+0xb1/0x104 [c103ae67] ? local_bh_enable+0x2/0x2 [c10409f7] ? run_timer_softirq+0x166/0x209 [c1223c9f] ? netif_tx_unlock+0x3a/0x3a [c103ae67] ? local_bh_enable+0x2/0x2 [c103aefb] ? __do_softirq+0x94/0x130 [c103ae67] ? local_bh_enable+0x2/0x2 IRQ [c103b0f1] ? irq_exit+0x32/0x80 [c101b163] ? smp_apic_timer_interrupt+0x5b/0x65 [c12ae489] ? apic_timer_interrupt+0x31/0x38 [c11893e1] ? cfb_imageblit+0x199/0x478 [c1184ea9] ? bit_putcs+0x2f0/0x359 [c1184ba7] ? bit_cursor+0x3d3/0x3e5 [c1180621] ? fbcon_putcs+0x98/0xa3 [c1184bb9] ? bit_cursor+0x3e5/0x3e5 [c1182c33] ? fbcon_redraw.clone.11+0xb9/0x144 [c1180e3a] ? fbcon_prepare_logo+0x6f/0x2cd [c1183295] ? fbcon_scroll+0x5d7/0xad7 [c11cc9eb] ? scrup+0x5c/0xcb [c11ccb45] ? lf+0x23/0x54 [c11cfc13] ? do_con_write+0x848/0x1ca8 [c1181e0f] ? fbcon_cursor+0xdf/0xf4 [c11d10a9] ? con_write+0x9/0x17 [c11c1e8b] ? do_output_char+0x85/0x187 [c11c1fb6] ? process_output+0x29/0x3b [c11c2415] ? n_tty_write+0x21e/0x2cf [c102ff4d] ? try_to_wake_up+0x154/0x154 [c11bf9a8] ? tty_write+0x15e/0x1db [c11c21f7] ? process_echoes+0x22f/0x22f [c11bfa25] ? tty_write+0x1db/0x1db [c10ca124] ? vfs_write+0x81/0xd6 [c10ca2e8] ? sys_write+0x3c/0x60 [c12b221f] ? sysenter_do_call+0x12/0x28 ---[ end trace 37d80e4bb9cb6f60 ]--- eth0: Transmit timeout, status 0004 end ping -c5 www.google.com PING www.l.google.com (74.125.226.84) 56(84) bytes of data. 64 bytes from 74.125.226.84: icmp_req=1 ttl=57 time=27.0 ms 64 bytes from 74.125.226.84: icmp_req=2 ttl=57 time=26.6 ms 64 bytes from 74.125.226.84: icmp_req=3 ttl=57 time=26.4 ms 64 bytes from 74.125.226.84: icmp_req=4 ttl=57 time=26.1 ms 64 bytes from 74.125.226.84: icmp_req=5 ttl=57 time=26.3 ms --- www.l.google.com ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 20174ms rtt min/avg/max/mdev = 26.137/26.501/27.012/0.350 ms note the time it took: 20 seconds. usually it's around 4-5 seconds. i set it important because it forces me to reboot the machine, putting a dent in my workflow ;). thank you, simon -- Package-specific info: ** Version: Linux version 3.0.0-1-686-pae (Debian 3.0.0-1) (b...@decadent.org.uk) (gcc version 4.5.3 (Debian 4.5.3-3) ) #1 SMP Sun Jul 24 14:27:32 UTC 2011 ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.0.0-1-686-pae root=/dev/sda1 ro single ht=on ** Tainted: W (512) * Taint on warning. ** Kernel log: [ 449.008331] [c12ae489] ? apic_timer_interrupt+0x31/0x38 [ 449.008352] [c11893e1] ? cfb_imageblit+0x199/0x478 [ 449.008359] [c1184ea9] ? bit_putcs+0x2f0/0x359 [ 449.008366] [c1184ba7] ? bit_cursor+0x3d3/0x3e5 [ 449.008375] [c1180621] ? fbcon_putcs+0x98/0xa3 [ 449.008381] [c1184bb9] ? bit_cursor+0x3e5/0x3e5 [ 449.008387] [c1182c33] ? fbcon_redraw.clone.11+0xb9/0x144 [ 449.008393] [c1180e3a] ? fbcon_prepare_logo+0x6f/0x2cd [ 449.008399] [c1183295] ? fbcon_scroll+0x5d7/0xad7 [ 449.008407] [c11cc9eb] ? scrup+0x5c/0xcb [ 449.008413] [c11ccb45] ? lf+0x23/0x54 [ 449.008419] [c11cfc13] ? do_con_write+0x848/0x1ca8 [ 449.008426] [c1181e0f] ? fbcon_cursor+0xdf/0xf4 [ 449.008432] [c11d10a9] ?
Bug#635826: hda-intel (CX20549 (Venice)): external speaker output and mic inputs mute
Package: linux-2.6 Version: 3.0.0-1 Severity: normal Since I have installed the 3.0 linux kernel, the external speaker output does not work anymore. Additionally, capturing from internal or external microphones gives silence. The internal speaker and the (now switchable) auto-mute feature work as expected. With the 2.6.39 kernel, I had no sound problems. alsa-info.txt is attached. -- Package-specific info: ** Version: Linux version 3.0.0-1-686-pae (Debian 3.0.0-1) (b...@decadent.org.uk) (gcc version 4.5.3 (Debian 4.5.3-3) ) #1 SMP Sun Jul 24 14:27:32 UTC 2011 ** Tainted: PO (4097) * Proprietary module has been loaded. * Out-of-tree module has been loaded. ** Kernel log: [ 386.801425] HDA Intel :00:1b.0: PCI INT A - GSI 22 (level, low) - IRQ 22 [ 386.801659] HDA Intel :00:1b.0: irq 46 for MSI/MSI-X [ 386.801721] HDA Intel :00:1b.0: setting latency timer to 64 [ 386.900967] hda_codec: CX20549 (Venice): BIOS auto-probing. [ 386.901702] input: HDA Digital PCBeep as /devices/pci:00/:00:1b.0/input/input12 ** Loaded modules: Module Size Used by [...] snd_hrtimer12540 1 snd_hda_codec_conexant36407 1 snd_hda_intel 21691 3 snd_hda_codec 58364 2 snd_hda_codec_conexant,snd_hda_intel snd_hwdep 12936 1 snd_hda_codec snd_pcm_oss36377 0 snd_mixer_oss 17713 1 snd_pcm_oss snd_pcm53315 3 snd_hda_intel,snd_hda_codec,snd_pcm_oss snd_seq_midi 12744 0 snd_rawmidi22621 1 snd_seq_midi snd_seq_midi_event 13124 1 snd_seq_midi snd_seq39539 3 snd_seq_midi,snd_seq_midi_event snd_timer 22027 3 snd_hrtimer,snd_pcm,snd_seq snd_seq_device 12985 3 snd_seq_midi,snd_rawmidi,snd_seq snd38562 18 snd_hda_codec_conexant,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_rawmidi,snd_seq,snd_timer,snd_seq_device soundcore 12992 1 snd snd_page_alloc 12899 2 snd_hda_intel,snd_pcm [...] ** PCI devices: [...] 00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03) Subsystem: Benq Corporation Device 0593 Flags: bus master, fast devsel, latency 0, IRQ 46 Memory at f460 (64-bit, non-prefetchable) [size=16K] Capabilities: [50] Power Management version 2 Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00 Capabilities: [100] Virtual Channel Capabilities: [130] Root Complex Link Kernel driver in use: HDA Intel [...] upload=truescript=truecardinfo= !! !!ALSA Information Script v 0.4.60 !! !!Script ran on: Thu Jul 28 19:29:20 UTC 2011 !!Linux Distribution !!-- Debian GNU/Linux wheezy/sid \n \l !!DMI Information !!--- Manufacturer: BenQ Product Name: Joybook R56 Product Version: Not Applicable !!Kernel Information !!-- Kernel release:3.0.0-1-686-pae Operating System: GNU/Linux Architecture: i686 Processor: unknown SMP Enabled: Yes !!ALSA Version !! Driver version: 1.0.24 Library version:1.0.24.1 Utilities version: 1.0.24.2 !!Loaded ALSA modules !!--- snd_hda_intel !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes ESound Daemon: Installed - Yes (/usr/bin/esd) Running - No aRts: Installed - Yes (/usr/bin/artsd) Running - No Jack: Installed - Yes (/usr/bin/jackd) Running - No !!Soundcards recognised by ALSA !!- 0 [Intel ]: HDA-Intel - HDA Intel HDA Intel at 0xf460 irq 46 !!PCI Soundcards installed in the system !!-- 00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03) !!Advanced information - PCI Vendor/Device/Subsystem ID's !! 00:1b.0 0403: 8086:284b (rev 03) Subsystem: 17ff:0593 !!Modprobe options (Sound related) !! snd-atiixp-modem: index=-2 snd-intel8x0m: index=-2 snd-via82xx-modem: index=-2 snd-pcsp: index=-2 snd-usb-audio: index=-2 !!Loaded sound module options !!-- !!Module: snd_hda_intel bdl_pos_adj : 1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1 beep_mode : 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1 enable : Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y enable_msi : -1 id :
Bug#635539: depmod.sh: No such file or directory
confirmed, got the same error trying to build compat modules. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1311887413.2799.1.ca...@damokles.lan
Bug#635840: TP-Link TL-WN821N v2 doesn't work with kernel 3.0
Package: linux-2.6 Version: 3.0.0-1 Severity: normal Tags: sid I cannot raise up my wireless interface using kernel 3.0: # ifconfig wlan0 up wla0n: ERROR while getting interface flags: No such device With kernel 2.6.39 I'm able to run the same command and get a stable connection (using wpa_supplicant). I've used ar9170usb module but now it was removed and replaced by carl9170 (http://linuxwireless.org/en/users/Drivers/ar9170) # lsusb Bus 001 Device 003: ID 0cf3:1002 Atheros Communications, Inc. TP-Link TL-WN821N v2 [Atheros AR9001U-(2)NG] dmesg doesn't give any useful information about how my device was registered. Thank you and sorry about my english. -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information sys_vendor: OEM product_name: product_version: chassis_vendor: OEM chassis_version: bios_vendor: OEM bios_version: 1.09 board_vendor: OEM board_name: N/A board_version: N/A ** Network interface configuration: # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo iface lo inet loopback ** PCI devices: 00:00.0 Host bridge [0600]: Silicon Integrated Systems [SiS] 671MX [1039:0671] Subsystem: Elitegroup Computer Systems Device [1019:5050] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort+ SERR- PERR- INTx- Latency: 32 Region 0: Memory at a000 (32-bit, non-prefetchable) [size=256M] Capabilities: access denied Kernel driver in use: agpgart-sis 00:01.0 PCI bridge [0604]: Silicon Integrated Systems [SiS] SiS AGP Port (virtual PCI-to-PCI bridge) [1039:0003] (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0, Cache Line Size: 16 bytes Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 I/O behind bridge: 9000-9fff Memory behind bridge: b000-b00f Prefetchable memory behind bridge: c000-cfff Secondary status: 66MHz+ FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort+ SERR- PERR- BridgeCtl: Parity- SERR- NoISA+ VGA+ MAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- 00:02.0 ISA bridge [0601]: Silicon Integrated Systems [SiS] SiS968 [MuTIOL Media IO] [1039:0968] (rev 01) Subsystem: Elitegroup Computer Systems Device [1019:5a00] Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 00:02.5 IDE interface [0101]: Silicon Integrated Systems [SiS] 5513 [IDE] [1039:5513] (rev 01) (prog-if 80 [Master]) Subsystem: Elitegroup Computer Systems Device [1019:5a00] Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 128 Interrupt: pin ? routed to IRQ 16 Region 0: I/O ports at 01f0 [size=8] Region 1: I/O ports at 03f4 [size=1] Region 2: I/O ports at 0170 [size=8] Region 3: I/O ports at 0374 [size=1] Region 4: I/O ports at 1080 [size=16] Capabilities: access denied Kernel driver in use: pata_sis 00:03.0 USB Controller [0c03]: Silicon Integrated Systems [SiS] USB 1.1 Controller [1039:7001] (rev 0f) (prog-if 10 [OHCI]) Subsystem: Elitegroup Computer Systems Device [1019:5a00] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 32 (2ns max) Interrupt: pin A routed to IRQ 20 Region 0: Memory at b0104000 (32-bit, non-prefetchable) [size=4K] Kernel driver in use: ohci_hcd 00:03.1 USB Controller [0c03]: Silicon Integrated Systems [SiS] USB 1.1 Controller [1039:7001] (rev 0f) (prog-if 10 [OHCI]) Subsystem: Elitegroup Computer Systems Device [1019:5a00] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 32 (2ns max)
Processed: tagging 635539
Processing commands for cont...@bugs.debian.org: tags 635539 + pending Bug #635539 [linux-2.6] depmod.sh: No such file or directory Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 635539: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=635539 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.13118946465869.transcr...@bugs.debian.org
Processed: severity of 635539 is grave
Processing commands for cont...@bugs.debian.org: severity 635539 grave Bug #635539 [linux-2.6] depmod.sh: No such file or directory Severity set to 'grave' from 'normal' thanks Stopping processing here. Please contact me if you need assistance. -- 635539: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=635539 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.13118946545896.transcr...@bugs.debian.org
Processing of linux-kbuild-2.6_3.0.0-2_source.changes
linux-kbuild-2.6_3.0.0-2_source.changes uploaded successfully to localhost along with the files: linux-kbuild-2.6_3.0.0-2.dsc linux-kbuild-2.6_3.0.0-2.diff.gz Greetings, Your Debian queue daemon (running on host franck.debian.org) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1qmzwe-00040e...@franck.debian.org
linux-kbuild-2.6_3.0.0-2_source.changes REJECTED
Reject Reasons: source only uploads are not supported. === Please feel free to respond to this email if you don't understand why your files were rejected, or if you upload new files which address our concerns. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1qma4n-0005qz...@franck.debian.org
Processing of linux-kbuild-2.6_3.0.0-2_i386.changes
linux-kbuild-2.6_3.0.0-2_i386.changes uploaded successfully to localhost along with the files: linux-kbuild-2.6_3.0.0-2.dsc linux-kbuild-2.6_3.0.0-2.diff.gz linux-kbuild-3.0.0_3.0.0-2_i386.deb Greetings, Your Debian queue daemon (running on host franck.debian.org) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1qmana-0001tu...@franck.debian.org
Bug#635539: marked as done (depmod.sh: No such file or directory)
Your message dated Fri, 29 Jul 2011 00:32:40 + with message-id e1qmb0k-0003gr...@franck.debian.org and subject line Bug#635539: fixed in linux-kbuild-2.6 3.0.0-2 has caused the Debian Bug report #635539, regarding depmod.sh: No such file or directory 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.) -- 635539: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=635539 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 3.0.0-1 Severity: normal Hi, When trying to install omnibook (git clone git://omnibook.git.sourceforge.net/gitroot/omnibook/omnibook make install) one gets: # Removing module from locations used by previous versions rm -f /lib/modules/3.0.0-1-amd64/kernel/drivers/char/omnibook.ko rm -f /lib/modules/3.0.0-1-amd64/kernel/drivers/misc/omnibook.ko make INSTALL_MOD_PATH= INSTALL_MOD_DIR=extra -C /lib/modules/3.0.0-1-amd64/build M=/tmp/omnibook modules_install make[1]: Entering directory `/usr/src/linux-headers-3.0.0-1-amd64' INSTALL /tmp/omnibook/omnibook.ko DEPMOD 3.0.0-1-amd64 /bin/bash: /usr/src/linux-headers-3.0.0-1-common/scripts/depmod.sh: No such file or directory make[3]: *** [_emodinst_post] Error 127 make[2]: *** [sub-make] Error 2 make[1]: *** [all] Error 2 make[1]: Leaving directory `/usr/src/linux-headers-3.0.0-1-amd64' make: *** [install] Error 2 Even if omnibook is not (yet) packaged for debian, I believe something slightly changed in the depmod.sh script Thanks -- Package-specific info: ** Version: Linux version 3.0.0-1-amd64 (Debian 3.0.0-1) (b...@decadent.org.uk) (gcc version 4.5.3 (Debian 4.5.3-4) ) #1 SMP Sun Jul 24 02:24:44 UTC 2011 ** Command line: BOOT_IMAGE=/vmlinuz-3.0.0-1-amd64 root=/dev/mapper/virtlap-root ro pci=use_crs acpi_osi=Linux quiet ** Tainted: PWO (4609) * Proprietary module has been loaded. * Taint on warning. * Out-of-tree module has been loaded. ** Kernel log: [11783.479806] omnibook: Begin table match of bluetooth feature. [11783.479812] omnibook: Attempting backend acpi init. [11783.479817] omnibook: Try to init ACPI backend [11783.479836] omnibook: ACPI EC device found [11783.480491] input: Omnibook ACPI scancode generator as /devices/virtual/input/input22 [11783.480735] omnibook: hook_connect for device AT Translated Set 2 keyboard. [11783.480840] omnibook: ACPI backend init OK [11783.480846] omnibook: Returning table entry nr 0. [11783.480852] omnibook: Match succeeded: continuing with bluetooth. [11783.484521] omnibook: get_wireless raw_state: 15 [11783.484540] omnibook: Testing feature cooling at address a0ac8b80 [11783.484547] omnibook: Begin table match of cooling feature. [11783.484553] omnibook: Attempting backend compal init. [11783.484558] omnibook: CDI backend init already failed, skipping. [11783.484564] omnibook: Backend compal init failed, skipping entry. [11783.484570] omnibook: Match failed: disabling cooling. [11783.484576] omnibook: Testing feature display at address a0ac8c00 [11783.484581] omnibook: Begin table match of display feature. [11783.484586] omnibook: Attempting backend acpi init. [11783.484590] omnibook: ACPI backend has already been initialized [11783.484596] omnibook: Returning table entry nr 0. [11783.484600] omnibook: Match succeeded: continuing with display. [11783.495808] omnibook: get_display raw_state: 101 [11783.495814] omnibook: Testing feature dock at address a0ac8c80 [11783.495817] omnibook: Testing feature dump at address a0ac8d00 [11783.495820] omnibook: Testing feature fan at address a0ac8d80 [11783.495822] omnibook: Testing feature fan_policy at address a0ac8e00 [11783.495825] omnibook: Testing feature hotkeys at address a0ac8e80 [11783.495827] omnibook: Begin table match of hotkeys feature. [11783.495829] omnibook: Attempting backend compal init. [11783.495831] omnibook: CDI backend init already failed, skipping. [11783.495833] omnibook: Backend compal init failed, skipping entry. [11783.495835] omnibook: Match failed: disabling hotkeys. [11783.495837] omnibook: Testing feature dmi at address a0ac8f00 [11783.495839] omnibook: dmi feature has no backend table, io_op not initialized. [11783.495843] omnibook: Testing feature version at address a0ac8f80 [11783.495846] omnibook: version feature has no backend table, io_op not initialized. [11783.495849] omnibook: Testing feature lcd at address a0ac9000 [11783.495851] omnibook: Begin table match of lcd feature. [11783.495853] omnibook: Attempting backend compal init. [11783.495855] omnibook: CDI backend init
linux-kbuild-2.6_3.0.0-2_i386.changes ACCEPTED into unstable
Accepted: linux-kbuild-2.6_3.0.0-2.diff.gz to main/l/linux-kbuild-2.6/linux-kbuild-2.6_3.0.0-2.diff.gz linux-kbuild-2.6_3.0.0-2.dsc to main/l/linux-kbuild-2.6/linux-kbuild-2.6_3.0.0-2.dsc linux-kbuild-3.0.0_3.0.0-2_i386.deb to main/l/linux-kbuild-2.6/linux-kbuild-3.0.0_3.0.0-2_i386.deb Override entries for your package: linux-kbuild-2.6_3.0.0-2.dsc - source devel linux-kbuild-3.0.0_3.0.0-2_i386.deb - optional devel Announcing to debian-devel-chan...@lists.debian.org Closing bugs: 635539 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 Archive: http://lists.debian.org/e1qmb0k-0003gi...@franck.debian.org
Bug#635848: firmware-ralink: Doesn't work with new linux kernel 3.0
Package: firmware-ralink Version: 0.28 Severity: important Doesn't work with new linux kernel 3.0 -- System Information: Debian Release: 6.0.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.39.3.atom (SMP w/2 CPU cores) Locale: LANG=pt_BR.utf8, LC_CTYPE=pt_BR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash firmware-ralink depends on no packages. firmware-ralink recommends no packages. Versions of packages firmware-ralink suggests: ii initramfs-too 0.98.8 tools for generating an initramfs ii linux-image-2 2.6.39.3.atom-10.00.Custom Linux kernel binary image for vers ii linux-image-3 3.0.0.atom-10.00.CustomLinux kernel binary image for vers -- no debconf information -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110729034012.3460.44192.reportbug@localhost.localdomain
