Bug#637281: No dkms in linux-image-3.0.0-1
Package: linux-2.6 Version: 3.0.0-1 Severity: normal When installing linux-image-3.0.0.1 (a,d linux-headers, linux-kbuild) I get run-parts: executing /etc/kernel/postinst.d/dkms 3.0.0-1-686-pae /boot/vmlinuz-3.0.0-1-686-pae Error! Could not locate dkms.conf file. File: does not exist. I have graphical driver and virtualbox as dkms, thus I cannot use this package... -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information not available ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation Core Processor DRAM Controller [8086:0040] (rev 02) Subsystem: Hewlett-Packard Company Device [103c:304b] 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 Capabilities: access denied 00:16.0 Communication controller [0780]: Intel Corporation 5 Series/3400 Series Chipset HECI Controller [8086:3b64] (rev 06) Subsystem: Hewlett-Packard Company Device [103c:304b] 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 Interrupt: pin A routed to IRQ 5 Region 0: Memory at f0027100 (64-bit, non-prefetchable) [size=16] Capabilities: access denied 00:16.3 Serial controller [0700]: Intel Corporation 5 Series/3400 Series Chipset KT Controller [8086:3b67] (rev 06) (prog-if 02 [16550]) Subsystem: Hewlett-Packard Company Device [103c:304b] 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 Interrupt: pin B routed to IRQ 17 Region 0: I/O ports at 2180 [size=8] Region 1: Memory at f0024000 (32-bit, non-prefetchable) [size=4K] Capabilities: access denied Kernel driver in use: serial 00:19.0 Ethernet controller [0200]: Intel Corporation 82578DM Gigabit Network Connection [8086:10ef] (rev 05) Subsystem: Hewlett-Packard Company Device [103c:304b] 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 Interrupt: pin B routed to IRQ 40 Region 0: Memory at f000 (32-bit, non-prefetchable) [size=128K] Region 1: Memory at f0025000 (32-bit, non-prefetchable) [size=4K] Region 2: I/O ports at 2100 [size=32] Capabilities: access denied Kernel driver in use: e1000e 00:1a.0 USB Controller [0c03]: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller [8086:3b3c] (rev 05) (prog-if 20 [EHCI]) Subsystem: Hewlett-Packard Company Device [103c:304b] 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 Interrupt: pin A routed to IRQ 20 Region 0: Memory at f0026800 (32-bit, non-prefetchable) [size=1K] Capabilities: access denied Kernel driver in use: ehci_hcd 00:1b.0 Audio device [0403]: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio [8086:3b56] (rev 05) Subsystem: Hewlett-Packard Company Device [103c:304b] 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: 64 bytes Interrupt: pin A routed to IRQ 42 Region 0: Memory at f002 (64-bit, non-prefetchable) [size=16K] Capabilities: access denied Kernel driver in use: HDA Intel 00:1c.0 PCI bridge [0604]: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 1 [8086:3b42] (rev 05) (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: 64 bytes Bus: primary=00, secondary=18, subordinate=18, sec-latency=0 I/O behind bridge: 1000-1fff Memory behind bridge: f010-f01f Prefetchable memory behind bridge: e000-efff Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort+ SERR- PERR- BridgeCtl: Parity- SERR+ NoISA- VGA+ MAbort- Reset- FastB2B-
Bug#636306: mount.nfs: page allocation failure. order:4, mode:0xc0d0
Instead of switching to cifs, I tried swapiness=100, and just doubling up on the backup job: 25 23 * * * disk-backup || (sleep 100; disk-backup) Last night the first backup failed, second backup worked. Yippee. The first backup failed by a simple test for the presence of a file the nfs mount. I wonder is there some kind of cleanup event that the first nfs mount failure causes that I could run on this system periodically? -- 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/4e4236e7.8060...@elbournb.fsnet.co.uk
Bug#618006: [PATCH 2.6.32.y] Input: bcm5974 - add support for MacBookPro8
Andy has the hardware, or at least had access to the hardware back then. I have the hardware too now, but I don't have time to run the tests. This patch is fairly trivial - but I can test it some time in the next few days if needed. cheers, Andy -- 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/cahj+3c7osttwxtqobsm6rhtjxvb3dnq6sadxaknvehkmkis...@mail.gmail.com
Bug#637240: linux-image-3.0.0-1-686-pae: Several problems after updating to kernel 3.0
El 2011-08-09 a las 17:08 -0500, Jonathan Nieder escribió: Thanks for testing. Re (2), the first question is where it is hanging. Does booting without the broadcom and bluetooth drivers work any better? If you can get into a rescue shell with the break=modules commandline parameter, it might be possible to get a backtrace during the hang, like so: echo 1 /proc/sys/kernel/sysrq ... trigger the hang ... alt+sysrq, C (or D, or T, whatever makes sense) initramfs-tools(8) and Documentation/sysrq.txt have details. I hate to say this but after a cold start the error/hang is not reproducible anymore... and I did nothing. Now the system restarts/shutdowns fine, with no delay nor errors on the screen. Let's make this bug about (2). Could you file a separate bug for (1)? Sure, I'm still facing the NM problem, will write a new bug for that. Thanks. I think you can close now this report. Greetings, -- Camaleón -- 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/20110810074709.ga4...@stt008.linux.site
Bug#635353: marked as done (wait longer for USB disks)
Your message dated Wed, 10 Aug 2011 08:14:16 + with message-id 20110810081416.ga20...@vostochny.stro.at and subject line Re: wait longer for USB disks has caused the Debian Bug report #635353, regarding wait longer for USB disks 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.) -- 635353: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=635353 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Severity: wishlist Version: 3.0.0-1 At boot this, Checking file systems...fsck from util-linux 2.19.1 fsck.ext3: Unable to resolve 'UUID=c914c362-4b46-48be-afaf-6e061825b2ed' fsck died with exit status 8 ^[[31mfailed (code 8).^[[39;49m File system check failed. A log is being saved in /var/log/fsck/checkfs if that location is writable. Please repair the file system manually. ... ^[[31mfailed!^[[39;49m A maintenance shell will now be started. CONTROL-D will terminate this shell and resume system boot. ... ^[[33m(warning).^[[39;49m Give root password for maintenance (or type Control-D to continue): is performed too fast, before the USB disks come on line. Perhaps it should wait the few extra seconds for the USB disks, or I must put some file with sleep 5 into /etc/init.d/ etc. etc. but where would be best? This is all due to this kernel? problem. Jul 25 07:25:28 jidanni3 kernel: [ 12.379058] usb 1-5: unable to read config index 0 descriptor/start: -32 Jul 25 07:25:28 jidanni3 kernel: [ 12.379232] usb 1-5: chopping to 0 config(s) Jul 25 07:25:28 jidanni3 kernel: [ 22.392216] usb 1-5: string descriptor 0 read error: -110 Jul 25 07:25:28 jidanni3 kernel: [ 22.395397] usb 1-5: New USB device found, idVendor=0951, idProduct=1606 Jul 25 07:25:28 jidanni3 kernel: [ 22.395407] usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=4 Jul 25 07:25:28 jidanni3 kernel: [ 22.397197] usb 1-5: no configuration chosen from 0 choices however waiting a few seconds will get it reread fine... ---End Message--- ---BeginMessage--- duplicate bug with no new, info thus closing. -- maks ---End Message---
Bug#635573: Endless message of Unable to enumerate usb device on port 5
Ok thanks again Jonathan. 2011/8/9, Jonathan Nieder jrnie...@gmail.com: tags 635573 + pending quit Hor Jiun Shyong wrote: After installing your linux-image-2.6.39-3-amd64_2.6.39-4~a.test1_amd64.deb, the message Unable to enumerate usb device on port 5 does not appear anymore and console is not spammed with the message. Thanks for checking. Thanks for your help. Will this fix be pushed to the latest debian kernel? Yep, it's part of v3.1-rc1 and v3.0.1. -- 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/CAJ4U3BdxsaZCgQoxz-3s0TS9Zn29=wfuie+fqeowvyw3x-b...@mail.gmail.com
Bug#637240: linux-image-3.0.0-1-686-pae: Several problems after updating to kernel 3.0
2011/8/10 Camaleón noela...@gmail.com:
I hate to say this but after a cold start the error/hang is not
reproducible anymore... and I did nothing. Now the system
restarts/shutdowns fine, with no delay nor errors on the screen.
I spoke too soon.
While the system still restarts with no issues, if I force an unload
of the wireless card module (modprobe -r brcmsmac) I can reproduce the
hang... and this time with a call trace (see attached document).
I think this is what makes NM to malfunction (it does not detect the
broadcom wifi card) :-?
Greetings,
--
Camaleón
Aug 10 10:37:43 stt300 kernel: [ 2641.292083] INFO: task wpa_supplicant:1207
blocked for more than 120 seconds.
Aug 10 10:37:43 stt300 kernel: [ 2641.292095] echo 0
/proc/sys/kernel/hung_task_timeout_secs disables this message.
Aug 10 10:37:43 stt300 kernel: [ 2641.292106] wpa_supplicant D 0
1207 1 0x
Aug 10 10:37:43 stt300 kernel: [ 2641.292124] f5445240 00200086 c141d684
c1487980
Aug 10 10:37:43 stt300 kernel: [ 2641.292139] f54453ec c1487980
f5445240 c1487980 c1487980 c12aca2c
Aug 10 10:37:43 stt300 kernel: [ 2641.292152] f5333f54 f5333f54 f5333e54
f5333e94 c120b244 f5cc7c80 ffa6 f5333f54
Aug 10 10:37:43 stt300 kernel: [ 2641.292167] Call Trace:
Aug 10 10:37:43 stt300 kernel: [ 2641.292183] [c12aca2c] ?
_cond_resched+0x5/0x18
Aug 10 10:37:43 stt300 kernel: [ 2641.292192] [c120b244] ?
verify_iovec+0x3d/0x75
Aug 10 10:37:43 stt300 kernel: [ 2641.292200] [c1203115] ?
__sys_sendmsg+0x128/0x18c
Aug 10 10:37:43 stt300 kernel: [ 2641.292207] [c12033f6] ?
sock_sendmsg_nosec+0xc9/0xc9
Aug 10 10:37:43 stt300 kernel: [ 2641.292216] [c12ad027] ?
__mutex_lock_common.clone.5+0xe2/0x131
Aug 10 10:37:43 stt300 kernel: [ 2641.292224] [c12acf37] ?
mutex_lock+0x17/0x25
Aug 10 10:37:43 stt300 kernel: [ 2641.292231] [c1210ad9] ? dev_load+0x8/0x5c
Aug 10 10:37:43 stt300 kernel: [ 2641.292238] [c1298f6b] ?
wext_handle_ioctl+0x55/0x182
Aug 10 10:37:43 stt300 kernel: [ 2641.292245] [c12131cb] ?
dev_ioctl+0x565/0x59a
Aug 10 10:37:43 stt300 kernel: [ 2641.292254] [c1011c19] ?
intel_pmu_enable_all+0x7f/0xcd
Aug 10 10:37:43 stt300 kernel: [ 2641.292261] [c1014908] ?
x86_pmu_enable+0x1a8/0x21a
Aug 10 10:37:43 stt300 kernel: [ 2641.292271] [c104e8a7] ?
hrtimer_forward+0x10f/0x123
Aug 10 10:37:43 stt300 kernel: [ 2641.292278] [c12034bf] ?
might_fault+0x5/0x5
Aug 10 10:37:43 stt300 kernel: [ 2641.292287] [c10d55e1] ?
do_vfs_ioctl+0x48f/0x4c8
Aug 10 10:37:43 stt300 kernel: [ 2641.292294] [c1204acf] ?
sys_sendmsg+0x3c/0x47
Aug 10 10:37:43 stt300 kernel: [ 2641.292302] [c10522fb] ?
timekeeping_get_ns+0x10/0x48
Aug 10 10:37:43 stt300 kernel: [ 2641.292311] [c1029cfe] ?
need_resched+0x11/0x1a
Aug 10 10:37:43 stt300 kernel: [ 2641.292318] [c1029d0c] ?
should_resched+0x5/0x1f
Aug 10 10:37:43 stt300 kernel: [ 2641.292325] [c12aca2c] ?
_cond_resched+0x5/0x18
Aug 10 10:37:43 stt300 kernel: [ 2641.292332] [c1158d9a] ?
copy_to_user+0x2e/0x4d
Aug 10 10:37:43 stt300 kernel: [ 2641.292340] [c10d565e] ?
sys_ioctl+0x44/0x66
Aug 10 10:37:43 stt300 kernel: [ 2641.292348] [c103a2b8] ?
sys_gettimeofday+0x27/0x5a
Aug 10 10:37:43 stt300 kernel: [ 2641.292357] [c12b221f] ?
sysenter_do_call+0x12/0x28
Aug 10 10:37:43 stt300 kernel: [ 2641.292405] INFO: task NetworkManager:2712
blocked for more than 120 seconds.
Aug 10 10:37:43 stt300 kernel: [ 2641.292410] echo 0
/proc/sys/kernel/hung_task_timeout_secs disables this message.
Aug 10 10:37:43 stt300 kernel: [ 2641.292415] NetworkManager D c10d87c6 0
2712 1 0x
Aug 10 10:37:43 stt300 kernel: [ 2641.292423] f4ec4ed0 0082 f541fe14
c10d87c6 f541fe7c c1487980
Aug 10 10:37:43 stt300 kernel: [ 2641.292437] f4ec507c f5ccd94c c1487980
f4ec4ed0 c1487980 c1487980 f541fe90 0720
Aug 10 10:37:43 stt300 kernel: [ 2641.292451] f5ccd94c 4040 0800
f4993500 c1029d0c f541fd38 f541ff54 bfeeab84
Aug 10 10:37:43 stt300 kernel: [ 2641.292465] Call Trace:
Aug 10 10:37:43 stt300 kernel: [ 2641.292471] [c10d87c6] ?
__d_lookup_rcu+0xba/0xf0
Aug 10 10:37:43 stt300 kernel: [ 2641.292480] [c1029d0c] ?
should_resched+0x5/0x1f
Aug 10 10:37:43 stt300 kernel: [ 2641.292487] [c120b244] ?
verify_iovec+0x3d/0x75
Aug 10 10:37:43 stt300 kernel: [ 2641.292496] [c12ad027] ?
__mutex_lock_common.clone.5+0xe2/0x131
Aug 10 10:37:43 stt300 kernel: [ 2641.292504] [c12acf37] ?
mutex_lock+0x17/0x25
Aug 10 10:37:43 stt300 kernel: [ 2641.292510] [c1210ad9] ? dev_load+0x8/0x5c
Aug 10 10:37:43 stt300 kernel: [ 2641.292517] [c1298f6b] ?
wext_handle_ioctl+0x55/0x182
Aug 10 10:37:43 stt300 kernel: [ 2641.292524] [c12131cb] ?
dev_ioctl+0x565/0x59a
Aug 10 10:37:43 stt300 kernel: [ 2641.292532] [c111df91] ?
security_sk_alloc+0xd/0xf
Aug 10 10:37:43 stt300 kernel: [ 2641.292540] [c12064a1] ?
sk_prot_alloc+0x7f/0xf7
Aug 10 10:37:43 stt300 kernel: [ 2641.292548] [c12034bf] ?
Re: Processed: reassign 633535 to systemtap
Hi Frank and Ritesh, The last module unloaded was generated by SystemTap. There is much more information needed from the submitter, regardless. I didn't get your email. Please remember to Cc: 633535-submit...@bugs.debian.org or the emails won't reach the submitter of the bug. - What was that ptrace-related workload being run? (On debian, ptrace has no relations to systemtap.) - What are those itrace / itrace2 dmesg's? It's a toy project of mine that uses ptrace to get a trace of all executed instructions of a process and to correlate this against symbols of loaded libraries. It's not exactly ready yet but it does support i386, amd64, armel and kfreebsd-i386. I was looking at adding thread support last time iirc but it is not done yet. - How long before the kernel error was the last systemtap script completed? - Can the problem be reproduced? Reliably or intermittently? On a freshly booted machine? It's definitely too late now sorry. Let's close the bug now. I'll reopen it if I ever hit the bug again. -Timo -- 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/84r54t1r5q@sauna.l.org
Xen dom0 support in kernel 3.0.0
Hi to the kernel team, I hope you (at least Ben, which I saw there) did a safe trip after Debconf11! :) Seems that there's a known issue about dom0 support for the VGA text console in the 3.0.0 kernel. Please see these: http://wiki.xen.org/xenwiki/XenParavirtOps#head-3d39973f716a47ae62d3501b5b578f53c67bb8c1 under: Dom0 console doesn't show any output and remains blank There's a patch here: http://git.kernel.org/?p=linux/kernel/git/konrad/xen.git;a=commit;h=c2419b4a4727f67af2fc2cd68b0d878b75e781bb Also, I've been told by pasik on #xen-api (freenode) that that patch is already queued for linux 3.0.2 stable-update, and it's in for 3.1 in upstream linux. I don't want to bother you too much about our Xen stuff, it's only affecting my development server (on which I'm currently trying to package xapi), which I can by the way still ssh into. I just wanted to let you know about the issue since I couldn't find out what the problem was without the help of pasik on IRC. But maybe you knew already, and this is only noise? :) So, I just wonder: do you guys are planning to upgrade to 3.0.2 somehow soon in SID? Are you currently working on it? Or maybe, you could apply the patch in current SID 3.0.0? Cheers, Thomas Goirand (zigo) -- 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/4e426534.4080...@debian.org
Processed: reassign 637281 to dkms
Processing commands for cont...@bugs.debian.org: reassign 637281 dkms Bug #637281 [linux-2.6] No dkms in linux-image-3.0.0-1 Bug reassigned from package 'linux-2.6' to 'dkms'. Bug No longer marked as found in versions 3.0.0-1. thanks Stopping processing here. Please contact me if you need assistance. -- 637281: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=637281 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.1312978065627.transcr...@bugs.debian.org
Re: Xen dom0 support in kernel 3.0.0
On Wed, 2011-08-10 at 19:02 +0800, Thomas Goirand wrote: Hi to the kernel team, I hope you (at least Ben, which I saw there) did a safe trip after Debconf11! :) Seems that there's a known issue about dom0 support for the VGA text console in the 3.0.0 kernel. Please see these: http://wiki.xen.org/xenwiki/XenParavirtOps#head-3d39973f716a47ae62d3501b5b578f53c67bb8c1 under: Dom0 console doesn't show any output and remains blank There's a patch here: http://git.kernel.org/?p=linux/kernel/git/konrad/xen.git;a=commit;h=c2419b4a4727f67af2fc2cd68b0d878b75e781bb Also, I've been told by pasik on #xen-api (freenode) that that patch is already queued for linux 3.0.2 stable-update, and it's in for 3.1 in upstream linux. I don't want to bother you too much about our Xen stuff, it's only affecting my development server (on which I'm currently trying to package xapi), which I can by the way still ssh into. I just wanted to let you know about the issue since I couldn't find out what the problem was without the help of pasik on IRC. But maybe you knew already, and this is only noise? :) So, I just wonder: do you guys are planning to upgrade to 3.0.2 somehow soon in SID? It doesn't exist yet, but when it does, yes. (But we won't change the upstream version number.) Are you currently working on it? Or maybe, you could apply the patch in current SID 3.0.0? Done, will be in 3.0.0-2. Ben. signature.asc Description: This is a digitally signed message part
Bug#637308: xen-linux-system-2.6.32-5-xen-amd64: with kernel option 'nosmp', dom0 hangup while init PCI-Express Fusion-MPT SAS
Package: xen-linux-system-2.6.32-5-xen-amd64 Version: 2.6.32-35 Severity: normal With kernel options 'nosmp' dom0 hang mptbase: ioc0: WARNING - Issuing Reset from mpt_config!! mptbase: ioc0: Initiating recovery mptbase: ioc0: Attempting Retry Config request type 0x1, page 0x1, action 0 mptbase: ioc0: WARNING - Issuing Reset from mpt_config!! mptbase: ioc0: Initiating recovery mptbase: ioc0: WARNING - Issuing Reset from mpt_config!! mptbase: ioc0: Initiating recovery mptbase: ioc0: Attempting Retry Config request type 0x0, page 0x2, action 0 mptbase: ioc0: WARNING - Issuing Reset from mpt_config!! mptbase: ioc0: Initiating recovery udevadm settle - timeout of 180 seconds reached, the event queu contains: /sys/devices/pci :00 :00 :02.0 :01 :00.0 :02 :01.0 :04 :00.0 (569) udevd[50]: worker [60] unexpectedly returned with status 0x0100 udevd[50]: worker [60] failed while handling '/sys/devices/pci :00 :00 :02.0 :01 :00.0 :02 :01.0 :04 :00.0' mptbase: ioc0: WARNING - Issuing Reset from mpt_config!! mptbase: ioc0: Initiating recovery If boot xen kernel on bare metall with option nosmp, then all ok. $lspci 00:00.0 Host bridge: Intel Corporation 5000P Chipset Memory Controller Hub (rev b1) 00:02.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x8 Port 2-3 (rev b1) 00:03.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x4 Port 3 (rev b1) 00:04.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x4 Port 4 (rev b1) 00:05.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x4 Port 5 (rev b1) 00:06.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x4 Port 6 (rev b1) 00:07.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x4 Port 7 (rev b1) 00:08.0 System peripheral: Intel Corporation 5000 Series Chipset DMA Engine (rev b1) 00:10.0 Host bridge: Intel Corporation 5000 Series Chipset FSB Registers (rev b1) 00:10.1 Host bridge: Intel Corporation 5000 Series Chipset FSB Registers (rev b1) 00:10.2 Host bridge: Intel Corporation 5000 Series Chipset FSB Registers (rev b1) 00:11.0 Host bridge: Intel Corporation 5000 Series Chipset Reserved Registers (rev b1) 00:13.0 Host bridge: Intel Corporation 5000 Series Chipset Reserved Registers (rev b1) 00:15.0 Host bridge: Intel Corporation 5000 Series Chipset FBD Registers (rev b1) 00:16.0 Host bridge: Intel Corporation 5000 Series Chipset FBD Registers (rev b1) 00:1d.0 USB Controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #1 (rev 09) 00:1d.1 USB Controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #2 (rev 09) 00:1d.2 USB Controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #3 (rev 09) 00:1d.3 USB Controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #4 (rev 09) 00:1d.7 USB Controller: Intel Corporation 631xESB/632xESB/3100 Chipset EHCI USB2 Controller (rev 09) 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev d9) 00:1f.0 ISA bridge: Intel Corporation 631xESB/632xESB/3100 Chipset LPC Interface Controller (rev 09) 00:1f.3 SMBus: Intel Corporation 631xESB/632xESB/3100 Chipset SMBus Controller (rev 09) 01:00.0 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Upstream Port (rev 01) 01:00.3 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express to PCI-X Bridge (rev 01) 02:00.0 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Downstream Port E1 (rev 01) 02:01.0 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Downstream Port E2 (rev 01) 02:02.0 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Downstream Port E3 (rev 01) 04:00.0 SCSI storage controller: LSI Logic / Symbios Logic SAS1064ET PCI-Express Fusion-MPT SAS (rev 04) 05:00.0 Ethernet controller: Intel Corporation 80003ES2LAN Gigabit Ethernet Controller (Serdes) (rev 01) 05:00.1 Ethernet controller: Intel Corporation 80003ES2LAN Gigabit Ethernet Controller (Serdes) (rev 01) 08:00.0 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet Controller (rev 06) 08:00.1 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet Controller (rev 06) 0c:0c.0 VGA compatible controller: ATI Technologies Inc ES1000 (rev 02) $ cat /sys/devices/pci\:00/\:00\:02.0/\:01\:00.0/\:02\:01.0/\:04\:00.0/device 0x0056 -- 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.32-5-xen-amd64 (SMP w/8 CPU cores) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages xen-linux-system-2.6.32-5-xen-amd64 depends on: ii linux-image-2.6.32-5-xen-amd6 2.6.32-35 Linux 2.6.32 for 64-bit PCs, Xen d ii xen-hypervisor-4.0-amd64 [xen 4.0.1-2The Xen Hypervisor on AMD64 xen-linux-system-2.6.32-5-xen-amd64 recommends no
Bug#637308: xen-linux-system-2.6.32-5-xen-amd64: with kernel option 'nosmp', dom0 hangup while init PCI-Express Fusion-MPT SAS
On Wed, 2011-08-10 at 16:51 +0400, Konstantin Alekseev wrote: Package: xen-linux-system-2.6.32-5-xen-amd64 Version: 2.6.32-35 Severity: normal With kernel options 'nosmp' dom0 hang [...] Why does this matter to you? Ben. signature.asc Description: This is a digitally signed message part
Processed: tagging 637308
Processing commands for cont...@bugs.debian.org: tags 637308 + moreinfo Bug #637308 [xen-linux-system-2.6.32-5-xen-amd64] xen-linux-system-2.6.32-5-xen-amd64: with kernel option 'nosmp', dom0 hangup while init PCI-Express Fusion-MPT SAS Added tag(s) moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 637308: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=637308 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.131298105312470.transcr...@bugs.debian.org
Bug#637308: xen-linux-system-2.6.32-5-xen-amd64: with kernel option 'nosmp', dom0 hangup while init PCI-Express Fusion-MPT SAS
http://docs.ganeti.org/ganeti/2.2/html/install.html For optimum performance when running both CPU and I/O intensive instances, it’s also recommended that the dom0 is restricted to one CPU only, for example by booting with the kernel parameter nosmp. Also this benchmarking advises disable smp http://web2.clarkson.edu/class/cs644/xen/files/repeatedxen-usenix04.pdf 2011/8/10 Ben Hutchings b...@decadent.org.uk On Wed, 2011-08-10 at 16:51 +0400, Konstantin Alekseev wrote: Package: xen-linux-system-2.6.32-5-xen-amd64 Version: 2.6.32-35 Severity: normal With kernel options 'nosmp' dom0 hang [...] Why does this matter to you? Ben. -- Konstantin
Bug#637308: xen-linux-system-2.6.32-5-xen-amd64: with kernel option 'nosmp', dom0 hangup while init PCI-Express Fusion-MPT SAS
On Wed, 2011-08-10 at 17:08 +0400, Константин Алексеев wrote: http://docs.ganeti.org/ganeti/2.2/html/install.html For optimum performance when running both CPU and I/O intensive instances, it’s also recommended that the dom0 is restricted to one CPU only, for example by booting with the kernel parameter nosmp. Also this benchmarking advises disable smp http://web2.clarkson.edu/class/cs644/xen/files/repeatedxen-usenix04.pdf Ignoring whether or not this is good advice (I expect it very much depends on your workload) this can be better achieved by adding dom0_max_vcpus=1 to your hypervisor command line or by hot-unplugging vCPUS once the system has booted (by echoing 0 into /sys/devices/system/cpu/cpu*/online for those CPUs). (the later give you the option of adding back VCPUs dynamically if you find you need to) That said, nosmp really ought to work I suppose so if this still happens on a recent kernel (e.g. 3.0) then I would appreciate it if you would also report this issue upstream (see http://wiki.xen.org/xenwiki/ReportingBugs) Did you confirm that this doesn't also happen under native? On first glance it looks more like an issue with a specific driver than a Xen issue. Ian. 2011/8/10 Ben Hutchings b...@decadent.org.uk On Wed, 2011-08-10 at 16:51 +0400, Konstantin Alekseev wrote: Package: xen-linux-system-2.6.32-5-xen-amd64 Version: 2.6.32-35 Severity: normal With kernel options 'nosmp' dom0 hang [...] Why does this matter to you? Ben. -- Konstantin -- Ian Campbell mixed emotions: Watching a bus-load of lawyers plunge off a cliff. With five empty seats. -- 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/1312982282.26263.219.ca...@zakaz.uk.xensource.com
Bug#637308: xen-linux-system-2.6.32-5-xen-amd64: with kernel option 'nosmp', dom0 hangup while init PCI-Express Fusion-MPT SAS
Yes, under native it does not happen. 2011/8/10 Ian Campbell i...@hellion.org.uk Did you confirm that this doesn't also happen under native? On first glance it looks more like an issue with a specific driver than a Xen issue. -- Konstantin
Bug#635912: More Details for driver problem
Hello, because this bug seems to have some deep problems i contacted the support of Realtek. In the time between i got help from Mr. Cheng from Realtek. The problem is not solved up to now, but i will post what we have found out so far: RTL8169 series are PCI Gigabit Ethernet Controller. The r8168 driver is for PCI-E products, not PCI products! One assumption was that there is a problem with the CPU power saving. So I disabled cool'n quiet in the BIOS and obviously it makes an effect! I could perform ping to my router without packet loss, but contact to the IMAP-Server fails. This seems to be the right way to come closer to the problem. The question is why the frequency stepping of the cpu has effect to the ethernet problem? All my tests where made with the newest driver version 6.015.00 for RTL8169. Another problem is that Mr. Cheng requested the driver informations: root@PC# ethtool -i eth2 driver: r8169 version: 2.3LK-NAPI firmware-version: bus-info: :02:07.0 Mr. Cheng writes to me that it is the inbox driver version, not the realtek driver version. Can anybody say what the inbox driver is? lsmod shows to me that the r8169 driver is loaded - so i can't understand this? I will made some further tests now with cool'n quiet disabled. Some ideas how i can debug the problem in detail would be helpful. Regards Karsten -- 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/70052403ae1867942844796484278478.squir...@dct.mine.nu
Bug#618006: [PATCH 2.6.32.y] Input: bcm5974 - add support for MacBookPro8
On Wed, Aug 10, 2011 at 08:45:09AM +0100, Andy Botting wrote: Andy has the hardware, or at least had access to the hardware back then. I have the hardware too now, but I don't have time to run the tests. This patch is fairly trivial - but I can test it some time in the next few days if needed. Please do. -- 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/20110810145159.ga7...@suse.de
Bug#535460: nfs-kernel-server: Consumes memory indefinitely and results in kernel panic eventually
Youssef Eldakar wrote: html style=direction: ltr; Please configure your mailer to send plain text in the future if possible. [...] I am not sure if this is a regression. In the cluster, NFS was replaced with OpenAFS, so I am not sure if the issue still exists with a recent software installation since this was a while ago. However, if you are interested, I might be able to set up a new test environment. Makes sense. Yes, that would be interesting (though if it's too much trouble, just let us know and we can wait for the next person experiencing the problem :)). Thanks for the update. -- 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/20110810151833.gd31...@elie.gateway.2wire.net
Bug#535460: nfs-kernel-server: Consumes memory indefinitely and results in kernel panic eventually
On 08/06/2011 12:12 AM, Jonathan Nieder wrote: Hi Youssef, Youssef Eldakar wrote: I am using nfs-kernel-server with Kerberos authentication to export /home to a cluster of over a thousand nodes. While nfs-kernel-server is running, memory usage goes up indefinitely on the NFS server. After several days, the system crashes with a kernel panic due to being out of memory. If I stop nfs-kernel-server, memory usage appears to go down slowly. Hm, that's no good. Sorry for the long silence. I have no better advice than - try as recent a kernel as possible - try a custom kernel with CONFIG_DEBUG_KMEMLEAK enabled to make the problem easier to track down. Thanks for the advice. Is this a regression (i.e., did previous kernel versions work okay)? I am not sure if this is a regression. In the cluster, NFS was replaced with OpenAFS, so I am not sure if the issue still exists with a recent software installation since this was a while ago. However, if you are interested, I might be able to set up a new test environment. -- Youssef Eldakar Bibliotheca Alexandrina -- 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/4e42a050.2050...@bibalex.org
Bug#535460: nfs-kernel-server: Consumes memory indefinitely and results in kernel panic eventually
On 08/06/2011 12:12 AM, Jonathan Nieder wrote: Hi Youssef, Youssef Eldakar wrote: I am using nfs-kernel-server with Kerberos authentication to export /home to a cluster of over a thousand nodes. While nfs-kernel-server is running, memory usage goes up indefinitely on the NFS server. After several days, the system crashes with a kernel panic due to being out of memory. If I stop nfs-kernel-server, memory usage appears to go down slowly. Hm, that's no good. Sorry for the long silence. I have no better advice than - try as recent a kernel as possible - try a custom kernel with CONFIG_DEBUG_KMEMLEAK enabled to make the problem easier to track down. Thanks for the advice. Is this a regression (i.e., did previous kernel versions work okay)? I am not sure if this is a regression. In the cluster, NFS was replaced with OpenAFS, so I am not sure if the issue still exists with a recent software installation since this was a while ago. However, if you are interested, I might be able to set up a new test environment. -- Youssef Eldakar Bibliotheca Alexandrina -- 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/4e42a054.9040...@bibalex.org
Bug#535460: nfs-kernel-server: Consumes memory indefinitely and results in kernel panic eventually
On 08/10/2011 05:18 PM, Jonathan Nieder wrote: Youssef Eldakar wrote: html style=direction: ltr; Please configure your mailer to send plain text in the future if possible. Whoops, sorry about that. I fixed it. [...] I am not sure if this is a regression. In the cluster, NFS was replaced with OpenAFS, so I am not sure if the issue still exists with a recent software installation since this was a while ago. However, if you are interested, I might be able to set up a new test environment. Makes sense. Yes, that would be interesting (though if it's too much trouble, just let us know and we can wait for the next person experiencing the problem :)). I will let you know if I manage to set something up next week. -- Youssef Eldakar Bibliotheca Alexandrina -- 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/4e42a4fb.8080...@bibalex.org
Minibus 4X4 au Maroc
Bonjour Nous avons le plaisir de porter à votre connaissance que nous sommes une agence de transport touristique installé à Marrakech au MAROC. Nous disposons d'un parc de véhicules diversifié de 06 à 17 places , ainsi que des 4X4 . Nos chauffeurs sont des professionnels prêts à mettre à votre disposition leur maîtrise du service du transport au Maroc . Nous demeurons à votre entière disposition pour toute information concernant les détails des services que nous assurons. Mohamed ASHAB Gérant Gsm : 00 212 (0) 6 72 21 72 10 ASHAB TOURS S.A.R.L Tel : + 212 (0) 5 24 44 82 45 Fax : + 212 (0) 5 24 44 82 53 E-mail : ashabto...@menara.ma Adresse : Avenue 11 Janvier , Immeuble ATLASSI C1 Appartement N°: 05 Marrakech-MAROC -- 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/20110810153553.5cf3c13a7...@liszt.debian.org
Bug#633024:
2011/8/9, maximilian attems m...@stro.at: just use rootdelay bootparam, instead of such hacks. I'm sorry if I was unclear, but rootdelay does NOT help in this situation. As the documentation explains, rootdelay delays between SCSI scan and mdadm / LVM assembly / scan. I need a delay between mdadm assembly and LVM scan, not after SCSI scan. It seems the local-top/lvm2 starts BEFORE local-top/mdadm is finished. The sleep 2 was the only thing which works consistently. Probably a udevadm settle or something should also do the trick. I'll try that and report back. -- 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/CAD+_0YoN3BsTHzR=+qmnyj8fcyzrfxqyd9qlzbhfdsxvp60...@mail.gmail.com
Bug#620848: linux-image-2.6.32-5-amd64: unable to enumerate usb device 6
Hi Hans, Hans-J. Ullrich wrote: It would be nice, if you could give me just a little info, that I know the status. :) When a fixed version is uploaded, it will show up as green in the chart at http://bugs.debian.org/620848. FWIW the planned next upload (3.0.0-2) includes the patch. Meanwhile we should look into fixing this in the 2.6.32.y longterm tree (and hence in squeeze). I will try to find time to prepare a package to test later today. Thanks, 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/20110810181904.ga15...@elie.gateway.2wire.net
Bug#552706: marked as done (BUG: soft lockup - CPU#0 stuck for 61s! - :nfs:nfs_access_cache_shrinker)
Your message dated Wed, 10 Aug 2011 20:51:04 +0200 with message-id 20110810185104.GA@pisco.westfalen.local and subject line Re: BUG: soft lockup - CPU#0 stuck for 61s! - :nfs:nfs_access_cache_shrinker has caused the Debian Bug report #552706, regarding BUG: soft lockup - CPU#0 stuck for 61s! - :nfs:nfs_access_cache_shrinker 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.) -- 552706: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=552706 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.26-19 Severity: important We get the following backtrace way too often, it repeats for all CPUs, but I'm pasting it only once here. [633582.838114] BUG: soft lockup - CPU#0 stuck for 61s! [init:1] [633582.838114] Modules linked in: nfs lockd nfs_acl sunrpc ipip tunnel4 ipv6 bonding coretemp ipmi_devintf ipmi_si ipmi_watchdog ipmi_msghandler loop snd_pcm snd_timer snd soundcore sn d_page_alloc i2c_i801 serio_raw rng_core pcspkr i2c_core psmouse button i5000_edac shpchp edac_core pci_hotplug joydev evdev ext3 jbd mbcache dm_mirror dm_log dm_snapshot dm_mod sg sr_m od cdrom ata_generic ata_piix ses sd_mod libata enclosur dock usbhid hid ff_memless ide_pci_generic megaraid_sas ide_core ehci_hc bnx2 firmware_class uhci_hcd scsi_mod e1000e thermal processor fan thermal_sys [last unloaded: scsi_wait_scan] [633582.838114] CPU 0: [63352.838114] Modules linked in: nfs lockd nfs_acl sunrpc ipip tunnel4 ipv6bonding coretemp ipmi_devintf ipmi_si ipmi_watchdog ipmi_msghandler loop snd_pcm snd_timer snd soundcore sn d_page_alloc i2c_i801 serio_ra rng_core pcspkr i2c_core psmouse button i5000_edac shpchp edac_core pci_hotlug joydev evdev ext3 jbd mbcache dm_mirror dm_log dm_snapshot dm_mod sg sr_m od cdrom ata_generic ata_piix ses sd_mod libata enclosure dockusbhid hid ff_memless ide_pci_generic megaraid_sas ide_core ehci_hcd bnx2firmware_cl= ass uhci_hcd scsi_mod e1000e thermal processor fan thermal_sys [last unloaded: scsi_wait_scan] [633582.838114] Pid: 1, comm: initNot tainted 2.6.26-2-amd64 #1 [633582.838114] RIP: 0010:[8042a3c] [8042a23c] _spin_lock+0x12/0x15 [633582.838114] RSP: 0018:8101bf077b70 EFLAGS: 0293 [633582.838114] RAX: 0001311 RBX: RCX: 00153793 [633582.838114] RDX: 000 RSI: 00d0 RDI: a0342714 [633582.838114] RBP: R08: 0064 R09: 810001101200 [633582.838114] R10: 000c R11: fffa016c378 R12: 0020 [633582.838114] R13: 0020 R14: 0020 R15: 000a [633582.838114] FS: 7f264a972770() GS:fff8053c000() knlGS: [633582.838114] CS: 0010 DS: ES: CR0: 8005003b [633582.838114] CR2: 00608f70 CR3: 0001bc8d000 CR4: 06e0 [633582.838114] DR0: DR1: 000 DR2: [633582.838114] DR3: DR6: 0f0 DR7: 0400 [633582.838114]=20 [633582.838114] Call Trace: [633582.838114] [a0308539] :nfs:nfs_access_cache_shrinker+0x26/0x1e9 [633582.838114] [8027b323] shrink_slab+0x60/0x159 [633582.838114] [8027b76] try_to_free_pages+0x25a/0x361 [633582.838114] [8027a6b7] isolate_pges_global+0x0/0x2f [633582.838114] [80276abd] __alloc_pages_internal+026a/0x3bf [633582.838114] [80295590] kmem_getpages+0x96/0x15f [633582.838114] [80295bfb] fallback_alloc+0x146/0x1e1 [633582.838114] [80296260] kmem_cache_alloc+0xc4/0xf6 [633582.838114] [802a33ba] getname+0x25/0x1a7 [633582.838114] [802a501b] __user_walk_fd+0x19/0x4c [633582.838114] [8029e181] vfs_stat_fd+0x1b/0x4a [633582.838114] [8029e20c] sys_newstat+0x19/0x31 [633582.838114] [802a7c48] sys_select+0x123/0x183 [633582.838114] [8020beca] system_call_after_swapgs+0x8a/0x8f [633582.838114]=20 [633610.757164] BUG: soft lockup - CPU#1 stuck for 61s! [bb-iostat.sh:194= 00] [633610.797166] Modules linked in: nfs lockd nfs_acl sunrpc ipip tunnel4 ipv6 bonding coretemp ipmi_devintf ipmi_si ipmi_watchdog ipmi_msghandler loop snd_pcm snd_timer snd soundcore sn d_page_alloc i2c_i801 serio_raw rng_core pcspkr i2c_core psmouse button i5000_edac shpchp edac_core pci_hotplug joydev evdev ext3 jbd mbcache dm_mirror dm_log dm_snapshot dm_mod sg sr_m od cdrom ata_generic ata_piix ses sd_mod libata enclosure dock usbhid hid ff_memless ide_pci_generic megaraid_sas ide_coe ehci_hcd bnx2 firmware_class uhci_hcd scsi_mod e1000e
Bug#637392: linux-image-2.6.32-5-amd64: [drm:r600_audio_bits_per_sample] *ERROR* Unknown bits per sample 0xf using 16 instead
Package: linux-2.6
Version: 2.6.32-35
Severity: important
Hello, it seems like my video driver is failing. My screen just switches off
itself and I see the following messages in my dmesg:
{ *** BEGIN OF dmesg OUTPUT CHUNK ***
[7.097844] [drm] radeon kernel modesetting enabled.
[7.097908] radeon :01:00.0: PCI INT A - GSI 16 (level, low) - IRQ 16
[7.097914] radeon :01:00.0: setting latency timer to 64
[7.099510] [drm] radeon: Initializing kernel modesetting.
[7.099694] [drm] register mmio base: 0xFE9E
[7.099696] [drm] register mmio size: 65536
[7.099826] ATOM BIOS: RV635PRO
[7.099841] [drm] Clocks initialized !
[7.099858] mtrr: type mismatch for d000,1000 old: write-back new:
write-combining
[7.099861] [drm] Detected VRAM RAM=256M, BAR=256M
[7.099862] [drm] RAM width 128bits DDR
[7.099900] [TTM] Zone kernel: Available graphics memory: 2030490 kiB.
[7.099916] [drm] radeon: 256M of VRAM memory ready
[7.099918] [drm] radeon: 512M of GTT memory ready.
[7.099950] alloc irq_desc for 28 on node -1
[7.099952] alloc kstat_irqs on node -1
[7.099964] radeon :01:00.0: irq 28 for MSI/MSI-X
[7.099968] radeon :01:00.0: radeon: using MSI.
[7.03] [drm] radeon: irq initialized.
[7.05] [drm] GART: num cpu pages 131072, num gpu pages 131072
[7.100572] [drm] Loading RV635 Microcode
[7.100576] platform radeon_cp.0: firmware: requesting radeon/RV635_pfp.bin
[7.155453] r600_cp: Failed to load firmware radeon/RV635_pfp.bin
[7.155495] [drm:r600_startup] *ERROR* Failed to load firmware!
[7.155532] radeon :01:00.0: disabling GPU acceleration
[7.155597] radeon :01:00.0: 88012c2fe000 unpin not necessary
[7.155600] radeon :01:00.0: 88012c2fe000 unpin not necessary
[7.155618] [drm] Enabling audio support
[7.155727] [drm] Default TV standard: NTSC
[7.155795] [drm] Radeon Display Connectors
[7.155797] [drm] Connector 0:
[7.155798] [drm] DVI-I
[7.155799] [drm] HPD1
[7.155802] [drm] DDC: 0x7e50 0x7e50 0x7e54 0x7e54 0x7e58 0x7e58 0x7e5c
0x7e5c
[7.155803] [drm] Encoders:
[7.155805] [drm] DFP1: INTERNAL_UNIPHY
[7.155807] [drm] CRT2: INTERNAL_KLDSCP_DAC2
[7.155808] [drm] Connector 1:
[7.155810] [drm] DIN
[7.155811] [drm] Encoders:
[7.155812] [drm] TV1: INTERNAL_KLDSCP_DAC2
[7.155813] [drm] Connector 2:
[7.155815] [drm] DVI-I
[7.155816] [drm] HPD2
[7.155818] [drm] DDC: 0x7e40 0x7e40 0x7e44 0x7e44 0x7e48 0x7e48 0x7e4c
0x7e4c
[7.155820] [drm] Encoders:
[7.155821] [drm] CRT1: INTERNAL_KLDSCP_DAC1
[7.155822] [drm] DFP2: INTERNAL_KLDSCP_LVTMA
[7.305072] [drm] fb mappable at 0xD004
[7.305075] [drm] vram apper at 0xD000
[7.305077] [drm] size 8294400
[7.305078] [drm] fb depth is 24
[7.305079] [drm]pitch is 7680
[7.319339] Console: switching to colour frame buffer device 240x67
[7.325068] fb0: radeondrmfb frame buffer device
[7.325069] registered panic notifier
[7.325074] [drm] Initialized radeon 2.0.0 20080528 for :01:00.0 on
minor 0
[ 8798.657508] [drm:r600_audio_bits_per_sample] *ERROR* Unknown bits per sample
0xf using 16 instead.
}*** END OF dmesg OUTPUT CHUNK ***
The last line in log is [drm:r600_audio_bits_per_sample] *ERROR* Unknown bits
per sample 0xf using 16 instead and I see a lot of them ... The only way to
recover from this situation is to reboot machine.
-- Package-specific info:
** Version:
Linux version 2.6.32-5-amd64 (Debian 2.6.32-35) (da...@debian.org) (gcc version
4.3.5 (Debian 4.3.5-4) ) #1 SMP Tue Jun 14 09:42:28 UTC 2011
** Command line:
BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-amd64
root=UUID=b88c9b9a-8744-4408-a480-58770bb6671d ro quiet
** Not tainted
** Kernel log:
[4.484359] [drm] DIN
[4.484360] [drm] Encoders:
[4.484361] [drm] TV1: INTERNAL_KLDSCP_DAC2
[4.484362] [drm] Connector 2:
[4.484363] [drm] DVI-I
[4.484364] [drm] HPD2
[4.484366] [drm] DDC: 0x7e40 0x7e40 0x7e44 0x7e44 0x7e48 0x7e48 0x7e4c
0x7e4c
[4.484367] [drm] Encoders:
[4.484368] [drm] CRT1: INTERNAL_KLDSCP_DAC1
[4.484369] [drm] DFP2: INTERNAL_KLDSCP_LVTMA
[4.529012] usb 3-3: new high speed USB device using ehci_hcd and address 2
[4.628680] alloc irq_desc for 22 on node -1
[4.628683] alloc kstat_irqs on node -1
[4.628690] HDA Intel :00:1b.0: PCI INT A - GSI 22 (level, low) - IRQ
22
[4.628739] HDA Intel :00:1b.0: setting latency timer to 64
[4.631579] [drm] fb mappable at 0xD004
[4.631581] [drm] vram apper at 0xD000
[4.631582] [drm] size 8294400
[4.631583] [drm] fb depth is 24
[4.631584] [drm]pitch is 7680
[4.645749] Console: switching to colour frame buffer device 240x67
[4.650354] fb0: radeondrmfb frame buffer device
[4.650356] registered panic notifier
[4.650360] [drm]
Bug#637395: linux-image-3.0.0-1-686-pae: EEE-PC 1000H: cpufreq cannot be set to ondemand
Package: linux-2.6 Version: 3.0.0-1 Severity: normal EXACT STEPS LEADING TO PROBLEM (done as root): 1. echo ondemand /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor 2. cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor EXPECTED OUTCOME: ondemand ACTUAL OUTCOME: performance Gnome cpufreq applet shows Performance. This also cannot be changed to Ondemand, another frequency cannot be selected neither. REPRODUCIBILITY: always EXTRA SOFTWARE INSTALLED: cpufrequtils 007-2 gnome-applets 2.30.0-4 (for cpufreq-applet) OTHER COMMENTS: cpufreq-applet shows the frequencies: 1.6GHz, 1.4GHz, 1.2GHz, 999MHz, 799MHz, 599MHz, 399MHz, 199MHz but 1.6GHz, 1.33GHz and 799MHz are expected only (like in = 2.39.x) I tried the same with a Lenovo t420i with linux-image-3.0.0-1-amd64 and it works as expected (so cpufreq works). On the EEE-PC it worked fine with 2.6.39-2-i686-pae. -- 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=/vmlinuz-3.0.0-1-686-pae root=/dev/mapper/bigend-root ro quiet printk.time=0 splash video=i915:modeset=1 ** Tainted: CO (5120) * Module from drivers/staging has been loaded. * Out-of-tree module has been loaded. ** Kernel log: speakup: module is from the staging directory, the quality is unknown, you have been warned. input: Speakup as /devices/virtual/input/input12 initialized device: /dev/synth, node (MAJOR 10, MINOR 25) speakup 3.1.6: initialized synth name on entry is: (null) speakup_soft: module is from the staging directory, the quality is unknown, you have been warned. synth probe initialized device: /dev/softsynth, node (MAJOR 10, MINOR 26) Adding 3903484k swap on /dev/mapper/bigend-swap. Priority:-1 extents:1 across:3903484k EXT3-fs: barriers not enabled kjournald starting. Commit interval 5 seconds EXT3-fs (sda1): using internal journal EXT3-fs (sda1): mounted filesystem with ordered data mode EXT3-fs: barriers not enabled kjournald starting. Commit interval 5 seconds EXT3-fs (dm-5): using internal journal EXT3-fs (dm-5): mounted filesystem with ordered data mode EXT3-fs: barriers not enabled kjournald starting. Commit interval 5 seconds EXT3-fs (dm-3): using internal journal EXT3-fs (dm-3): mounted filesystem with ordered data mode EXT3-fs: barriers not enabled kjournald starting. Commit interval 5 seconds EXT3-fs (dm-4): using internal journal EXT3-fs (dm-4): mounted filesystem with ordered data mode RPC: Registered named UNIX socket transport module. RPC: Registered udp transport module. RPC: Registered tcp transport module. RPC: Registered tcp NFSv4.1 backchannel transport module. FS-Cache: Loaded FS-Cache: Netfs 'nfs' registered for caching Installing knfsd (copyright (C) 1996 o...@monad.swb.de). fuse init (API version 7.16) pciehp: Unknown parameter `pciehp_slot_with_bus' NET: Registered protocol family 15 alg: No test for cipher_null (cipher_null-generic) alg: No test for ecb(cipher_null) (ecb-cipher_null) alg: No test for digest_null (digest_null-generic) alg: No test for compress_null (compress_null-generic) padlock_sha: VIA PadLock Hash Engine not detected. NET4: DECnet for Linux: V.2.5.68s (C) 1995-2003 Linux DECnet Project Team DECnet: Routing cache hash table of 1024 buckets, 8Kbytes NET: Registered protocol family 12 ATL1E :03:00.0: irq 44 for MSI/MSI-X ADDRCONF(NETDEV_UP): eth0: link is not ready input: ACPI Virtual Keyboard Device as /devices/virtual/input/input13 ADDRCONF(NETDEV_UP): wlan0: link is not ready apm: BIOS not found. Bluetooth: BNEP (Ethernet Emulation) ver 1.3 Bluetooth: BNEP filters: protocol multicast Bluetooth: RFCOMM TTY layer initialized Bluetooth: RFCOMM socket layer initialized Bluetooth: RFCOMM ver 1.11 composite sync not supported composite sync not supported lp: driver loaded but no devices found ppdev: user-space parallel port driver p4-clockmod: Warning: EST-capable CPU detected. The acpi-cpufreq module offers voltage scaling in addition to frequency scaling. You should use that instead of p4-clockmod, if possible. ondemand governor failed, too long transition latency of HW, fallback to performance governor p4-clockmod: P4/Xeon(TM) CPU On-Demand Clock Modulation available cpufreq-nforce2: No nForce2 chipset. powernow: This module only works with AMD K7 CPUs ondemand governor failed, too long transition latency of HW, fallback to performance governor ondemand governor failed, too long transition latency of HW, fallback to performance governor Ebtables v2.0 registered ip_tables: (C) 2000-2006 Netfilter Core Team ip6_tables: (C) 2000-2006 Netfilter Core Team Disabling lock debugging due to kernel taint vboxdrv: Found 2 processor cores. vboxdrv: fAsync=0 offMin=0x1e0 offMax=0x1950 vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'. vboxdrv: Successfully loaded version 4.0.8 (interface 0x0018). composite sync not supported composite
Bug#637392: linux-image-2.6.32-5-amd64: [drm:r600_audio_bits_per_sample] *ERROR* Unknown bits per sample 0xf using 16 instead
Hi Volodymyr, Volodymyr Shcherbyna wrote: Hello, it seems like my video driver is failing. My screen just switches off itself and I see the following messages in my dmesg: [...] The last line in log is [drm:r600_audio_bits_per_sample] *ERROR* Unknown bits per sample 0xf using 16 instead and I see a lot of them ... The only way to recover from this situation is to reboot machine. Hmm, that's no good. Does this always happen at boot, or after a certain trigger, or at seemingly random times? Is it easy to reproduce? Did it start happening with an upgrade, or has it always happened on this machine? Does it happen with the kernel from sid, too? Any other weird symptoms? This might have been fixed by v2.6.33-rc8~14^2~1^2~6 = v2.6.32.0.0~67 (drm/radeon/kms: suspend and resume audio stuff, 2010-01-28), so results from testing the kernel in sid would be very helpful. Thanks for reporting. Regards, 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/20110810212950.gc7...@elie.gateway.2wire.net
Bug#637395: linux-image-3.0.0-1-686-pae: EEE-PC 1000H: cpufreq cannot be set to ondemand
Hi Thomas, Thomas Renard wrote: EXACT STEPS LEADING TO PROBLEM (done as root): 1. echo ondemand /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor 2. cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor EXPECTED OUTCOME: ondemand ACTUAL OUTCOME: performance What is your detected list of available governors? # cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors powersave userspace conservative ondemand performance [...] cpufreq-applet shows the frequencies: 1.6GHz, 1.4GHz, 1.2GHz, 999MHz, 799MHz, 599MHz, 399MHz, 199MHz but 1.6GHz, 1.33GHz and 799MHz are expected only (like in = 2.39.x) I tried the same with a Lenovo t420i with linux-image-3.0.0-1-amd64 and it works as expected (so cpufreq works). On the EEE-PC it worked fine with 2.6.39-2-i686-pae. Hmm, weird. Maybe it's using a different cpufreq driver than before. Please attach dmesg output from booting the good and bad kernels, without the speakup and virtualbox drivers if possible. -- 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/20110810214553.gd7...@elie.gateway.2wire.net
Bug#637406: linux-2.6: Slow lvm performance with raid1 and 1 missing device
Package: linux-2.6 Severity: important I've set up a raid1 device with one missing device and created a lvm logical volume on it (pvcreate, vgcreate, lvcreate). Disk IO is significantly slower than when I do the same set-up using the onde device directly and no raid1. I've tested this with different hard drives and on different machines. According to 'top' the [kdmflush] hogs the CPU at 99-100% during any access to the filesystem on logical volume. I've also tested this with an earlier kernel (2.6.26 lenny) and got the same problem. According to iostat when using the device disk utilisation of the underlying device is constantly 100%. Thanks, Michael -- System Information: Debian Release: 6.0.2 APT prefers stable APT policy: (900, 'stable'), (500, 'stable-updates'), (100, 'oldstable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- 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/20110810234343.7574.1635.report...@blue.gn.apc.org
Bug#637407: linux-image-3.0.0-1-686-pae: Only grub2 adds an entry in menu.lst (grub1 doesn't)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Package: linux-2.6 Version: 3.0.0-1 Severity: normal *** Please type your report below this line *** Hi, Thank you for maintaining Debian's important kernel packages. It seems to me this some problems might be avoided by improving this package's dependencies. I happened to notice that the depricated grub1 package did not add an entry for this package's kernel to /boot/grub/menu.lst. It looks to me like /usr/sbin/update-grub.real ignores this kernel because it associates it with xen. Unless I'm mistaken, the failing version of grub1 was 0.97-1. Fortunately, version 1.99-11 of grub2 worked. Maybe this package should conflict with, or break, grub1. Thanks, Kingsley PS: My normal email address is loaner.com. -BEGIN PGP SIGNATURE- Charset: UTF8 Version: Hush 3.0 Note: This signature can be verified at https://www.hushtools.com/verify wsBcBAEBAgAGBQJOQxPvAAoJEJcphLrL8UMT7TAIAICaTpMrLhwX83GiHFPNm8vvYvn4 CX7hR1ty9l1KBRUOYv++qyBaDCr0JAhvgqgAfvJqHdmYzfDtTUJNTNsz37Ikh0c64fCk bHFZrh2FEz1a+soQpEUXj/wJ1yJljvuBSpjr55l0vYsBI34wS7dNoziGeOB/4nWbOUIV mEGJlS9FEJVseKwbJg4LSXc9JFNx2Cx38xD7p5njpkUlRlGS6H7PEwmu2Oc8aBPqdMAw 6H3Vi5heuEl6FbAONckJyZqm/SpbPnLH84s/H1kHBegSri5voG3nJg1v8/gZaTTNaC6P BOGfd1mQWcR7BYFAknVLG4w/m0oemS4Eo2OpirCdcDk= =BZBa -END PGP SIGNATURE- -- 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/20110810232743.5ec19e6...@smtp.hushmail.com
Bug#637407: linux-image-3.0.0-1-686-pae: Only grub2 adds an entry in menu.lst (grub1 doesn't)
Hi Kingsley, Kingsley wrote: I happened to notice that the depricated grub1 package did not add an entry for this package's kernel to /boot/grub/menu.lst. It looks to me like /usr/sbin/update-grub.real ignores this kernel because it associates it with xen. Unless I'm mistaken, the failing version of grub1 was 0.97-1. That seems unlikely, given that the version in lenny was already 0.97-47. Could you look up the failing grub version (it should be in /var/log/dpkg.log)? Thanks for reporting, 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/20110811000831.ga14...@elie.gateway.2wire.net
Processed: Re: The Intel parport bug
Processing commands for cont...@bugs.debian.org: reassign 630593 linux-2.6 Bug #630593 [linux-image-2.6] The Intel parport bug Warning: Unknown package 'linux-image-2.6' Bug reassigned from package 'linux-image-2.6' to 'linux-2.6'. forcemerge 630769 630593 Bug#630769: [Linux-parport] The Intel parport bug Bug#630593: The Intel parport bug Forcibly Merged 630593 630769. retitle 630593 linux-parport: does not detect EPP modes correctly on Intel chipsets Bug #630593 [linux-2.6] The Intel parport bug Bug #630769 [linux-2.6] [Linux-parport] The Intel parport bug Changed Bug title to 'linux-parport: does not detect EPP modes correctly on Intel chipsets' from 'The Intel parport bug' Changed Bug title to 'linux-parport: does not detect EPP modes correctly on Intel chipsets' from '[Linux-parport] The Intel parport bug' found 630593 linux-2.6/2.6.18.dfsg.1-10 Bug #630593 [linux-2.6] linux-parport: does not detect EPP modes correctly on Intel chipsets Bug #630769 [linux-2.6] linux-parport: does not detect EPP modes correctly on Intel chipsets Bug Marked as found in versions linux-2.6/2.6.18.dfsg.1-10. Bug Marked as found in versions linux-2.6/2.6.18.dfsg.1-10. found 630593 linux-2.6/2.6.22-6 Bug #630593 [linux-2.6] linux-parport: does not detect EPP modes correctly on Intel chipsets Bug #630769 [linux-2.6] linux-parport: does not detect EPP modes correctly on Intel chipsets Bug Marked as found in versions linux-2.6/2.6.22-6. Bug Marked as found in versions linux-2.6/2.6.22-6. tags 630593 = upstream Bug #630593 [linux-2.6] linux-parport: does not detect EPP modes correctly on Intel chipsets Bug #630769 [linux-2.6] linux-parport: does not detect EPP modes correctly on Intel chipsets Added tag(s) upstream; removed tag(s) patch. Added tag(s) upstream; removed tag(s) patch. quit Stopping processing here. Please contact me if you need assistance. -- 630593: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=630593 630769: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=630769 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.131302929227274.transcr...@bugs.debian.org
Bug#630593: The Intel parport bug
Jonathan Nieder wrote: Leopold Palomo-Avellaneda wrote: After such a long time it is probably appropriate to just remove the test [...] I have applied the patch to the standard debian kernel and it compiles and runs perfectly. Applied to some Dell hardware, now the EPP mode is detected and, after some initial tests it's working. I don't have any hope that it would be solved in the linux kernel I think otherwise: this patch should be a shoe-in For history divers: the quirk was introduced between 2.3.10pre5 and 2.3.10 (thanks to Dave Jones for the git tree that makes such searches easy!). That means some time around June or July, 1999. At the time Tim Waugh seems to have been an active parport_pc user, so maybe it would be worth getting his thoughts on such a patch, too, in the vague hope that he remembers --- though it _is_ a long time ago. Sorry for the noise; I forgot to mention that when sending the first message. -- 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/20110811024815.ga20...@elie.gateway.2wire.net
Processed: Re: The Intel parport bug
Processing commands for cont...@bugs.debian.org: # less misleading description retitle 630593 parport_pc: EPP mode detection fails due to Check for Intel bug Bug #630593 [linux-2.6] linux-parport: does not detect EPP modes correctly on Intel chipsets Bug #630769 [linux-2.6] linux-parport: does not detect EPP modes correctly on Intel chipsets Changed Bug title to 'parport_pc: EPP mode detection fails due to Check for Intel bug' from 'linux-parport: does not detect EPP modes correctly on Intel chipsets' Changed Bug title to 'parport_pc: EPP mode detection fails due to Check for Intel bug' from 'linux-parport: does not detect EPP modes correctly on Intel chipsets' End of message, stopping processing here. Please contact me if you need assistance. -- 630593: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=630593 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.131303652021806.transcr...@bugs.debian.org
Processed: Re: [linux-2.6] Please pick: iwlagn: check for !priv-txq in iwlagn_wait_tx_queue_empty
Processing commands for cont...@bugs.debian.org: notfound 635653 3.0.0-1-amd64 Bug #635653 [linux-2.6] [linux-2.6] Please pick: iwlagn: check for !priv-txq in iwlagn_wait_tx_queue_empty There is no source info for the package 'linux-2.6' at version '3.0.0-1-amd64' with architecture '' Unable to make a source version for version '3.0.0-1-amd64' Bug No longer marked as found in versions 3.0.0-1-amd64. found 635653 linux-2.6/3.0.0-1 Bug #635653 [linux-2.6] [linux-2.6] Please pick: iwlagn: check for !priv-txq in iwlagn_wait_tx_queue_empty Bug Marked as found in versions linux-2.6/3.0.0-1. tags 635653 + upstream fixed-upstream Bug #635653 [linux-2.6] [linux-2.6] Please pick: iwlagn: check for !priv-txq in iwlagn_wait_tx_queue_empty Added tag(s) upstream and fixed-upstream. End of message, stopping processing here. Please contact me if you need assistance. -- 635653: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=635653 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.131303764425900.transcr...@bugs.debian.org
Bug#569135: xserver-xorg-video-intel: corruption on external VGA display
Hi Christophe, Christophe Rhodes wrote: A note to let you know that I've tested the vanilla kernel, and at least v2.6.36-rc3 seems free of the VGA corruption that led me to write this bug report. [...] This means that the problem described in this bug is now solved for my purposes; unfortunately, it doesn't mean that the problem is solved in squeeze... Thanks for the nice report last year. There have been some fixes in this area of the kernel in squeeze since then, so if you get a chance to test a recent 2.6.32.y kernel, that would be interesting. Ciao, 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/20110811050459.ga24...@elie.gateway.2wire.net
