Bug#611750: Asus EeePC resume from hibernation fails
found 611750 linux-2.6/2.6.32-30 found 611750 linux-2.6/2.6.32-31 # regression from 2.6.32-27 retitle 611750 [regression] Asus EeePC: resume from hibernate fails when memory is scarce quit Hi, Gerald Turner wrote: I've upgraded to 2.6.32-31 some weeks ago and have noticed that the problem still exists, resume doesn't fail every time, so this afternoon I'm trying a more thorough examination. [...] For the first 10 consecutive suspend/resume cycles I had nothing but an empty gnome desktop and gnome-terminal running. Then I added pidgin and ekiga. At cycle 15 I fired up emacs. At cycle 20 I launched a handful of random gnome utilities (gcalctool, gconf-editor, gucharmap, nautilus, file-roller, palimpsest, gnome-dictionary). The 25th resume failed. Could it be memory related? Sorry for the long silence. Yes, that is believable; thanks for tracking it down. I haven't yet mulled over the above evidence carefully, but here are some basic questions anyway. - Does the latest squeeze kernel exhibit the same problem? How about a sid kernel? - Does 2.6.32-29 (available on snapshot.debian.org) behave the same way? - Does backing out the patch x86, hotplug: Use mwait to offline a processor, fix the legacy case that Frédéric mentioned[1] help? Looking forward to your thoughts, Jonathan [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=611750#198 -- 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/20110827061430.ga4...@elie.gateway.2wire.net
Processed: Re: Asus EeePC resume from hibernation fails
Processing commands for cont...@bugs.debian.org: found 611750 linux-2.6/2.6.32-30 Bug #611750 [linux-2.6] Asus EeePC resume from hibernation fails Bug Marked as found in versions linux-2.6/2.6.32-30. found 611750 linux-2.6/2.6.32-31 Bug #611750 [linux-2.6] Asus EeePC resume from hibernation fails Bug Marked as found in versions linux-2.6/2.6.32-31. # regression from 2.6.32-27 retitle 611750 [regression] Asus EeePC: resume from hibernate fails when memory is scarce Bug #611750 [linux-2.6] Asus EeePC resume from hibernation fails Changed Bug title to '[regression] Asus EeePC: resume from hibernate fails when memory is scarce' from 'Asus EeePC resume from hibernation fails' quit Stopping processing here. Please contact me if you need assistance. -- 611750: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=611750 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.131442568429870.transcr...@bugs.debian.org
Bug#611750: Asus EeePC resume from hibernation fails
Hi Sergei, Sergei Stolyarov wrote: I'm using Samsung N150, problem still exists: sometimes system wake up correctly, sometimes with instant reboot after finishing resume. Please file a separate report if you can still reproduce this, and we can merge them later if they turn out to have the same cause. 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/20110827061818.ga4...@elie.gateway.2wire.net
Bug#622259: resuming from hibernation sometimes fails on eeepc 1002HA
found 622259 linux-2.6/2.6.32-34 # regression severity 622259 important merge 622259 623149 quit Hi Robert and Frédéric, Frédéric Boiteux wrote: I've tried the 2.6.32-34 Debian kernel recently released for Squeeze, and the bug is still present. Thanks, and sorry for the late reply. I think we are long overdue to take this one upstream. I have a few questions anyway for before then: - does hibernation work for you if you try a sid (3.x) kernel? - could you attach dmesg output from right after booting? - is this reproducible this with a pristine kernel from kernel.org (e.g., 2.6.32.45, 2.6.33.18, or 2.6.35.14)? -- 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/20110827064955.ga4...@elie.gateway.2wire.net
Processed: Re: resuming from hibernation sometimes fails on eeepc 1002HA
Processing commands for cont...@bugs.debian.org: found 622259 linux-2.6/2.6.32-34 Bug #622259 [linux-2.6] linux-image-2.6.32-5-686: resuming from hibernation sometimes fails on eeepc 1002HA Bug Marked as found in versions linux-2.6/2.6.32-34. # regression severity 622259 important Bug #622259 [linux-2.6] linux-image-2.6.32-5-686: resuming from hibernation sometimes fails on eeepc 1002HA Severity set to 'important' from 'normal' merge 622259 623149 Bug#622259: linux-image-2.6.32-5-686: resuming from hibernation sometimes fails on eeepc 1002HA Bug#623149: Lenovo S10-3 fails to resume from hibernation Merged 622259 623149. quit Stopping processing here. Please contact me if you need assistance. -- 623149: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=623149 622259: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=622259 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.13144278096246.transcr...@bugs.debian.org
Bug#619049: i915: Hangcheck timer elapsed... GPU hung
Hi Dirk, Dirk Meul wrote: While I was surfing on my Eee PC 4G suddenly the GUI messed up. Active applications were evolution, empathy, skype and rhythmbox (playing music via DAAP) while I was surfing using chromium. The GUI is not usable but I am able to send this bug report via VC. With version 2.6.37-2 I never saw this, but with 2.6.38 RCs and with 2.6.38-1 this happens randomly. Sorry for the long silence. Can you reproduce this with the kernel from sid? If so, please report this upstream, following the instructions from http://intellinuxgraphics.org/how_to_report_bug.html, and let us know the bug number so we can track it. 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/20110827070850.ga7...@elie.gateway.2wire.net
Processed: Re: [xserver-xorg-video-intel] when using KMS, X puts the monitor directly into power saving mode upon startup[945G]
Processing commands for cont...@bugs.debian.org: tags 567034 - moreinfo Bug #567034 [linux-2.6] [xserver-xorg-video-intel] when using KMS, X puts the monitor directly into power saving mode upon startup[945G] Removed tag(s) moreinfo. quit Stopping processing here. Please contact me if you need assistance. -- 567034: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=567034 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.131443089320215.transcr...@bugs.debian.org
Bug#567034: marked as done ([xserver-xorg-video-intel] when using KMS, X puts the monitor directly into power saving mode upon startup[945G])
Your message dated Sat, 27 Aug 2011 02:41:13 -0500 with message-id 20110827074113.ga8...@elie.gateway.2wire.net and subject line Re: [xserver-xorg-video-intel] when using KMS, X puts the monitor directly into power saving mode upon startup[945G] has caused the Debian Bug report #567034, regarding [xserver-xorg-video-intel] when using KMS, X puts the monitor directly into power saving mode upon startup[945G] 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.) -- 567034: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=567034 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: xserver-xorg-video-intel Version: 2:2.9.1-2 Severity: important --- Please enter the report below this line. --- When X starts the monitor immediately flashes that it is going into power saving mode, before a display manager has a chance to start. It wakes upon entering ctl-alt-F1 through ctl-alt-F6 but returns to power saving mode with control-alt-F7. Top, etc indicates that X is in fact running. Disabling KMS solves the problem Attached is a log from one of the failed X startup attempts rather than the most recent successful one without KMS. If any further info is needed, let me know. --- System information. --- Architecture: amd64 Kernel: Linux 2.6.32-trunk-amd64 Debian Release: squeeze/sid 500 unstablemirror.csclub.uwaterloo.ca 500 unstablehttp.us.debian.org --- Package information. --- Depends(Version) | Installed -+-=== libc6 (= 2.2.5) | 2.10.2-5 libdrm-intel1(= 2.4.11) | 2.4.15-1 libdrm2 (= 2.4.3) | 2.4.15-1 libpciaccess0 (= 0.8.0+git20071002) | 0.11.0-1 libxext6 (= 0) | 2:1.1.1-2 libxfixes3 (= 1:4.0.1) | 1:4.0.4-1 libxv1 | 2:1.0.5-1 libxvmc1 | 2:1.0.5-1 xserver-xorg-core (= 2:1.6.99.900) | 2:1.7.4-2 Package's Recommends field is empty. Package's Suggests field is empty. -8---8---8---8---8---8---8---8---8-- Please attach the file: /tmp/reportbug-ng-xserver-xorg-video-intel-kPjrP7.txt to the mail. I'd do it myself if the output wasn't too long to handle. Thank you! -8---8---8---8---8---8---8---8---8-- X.Org X Server 1.7.4 Release Date: 2010-01-08 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.32.4-dsa-amd64 x86_64 Debian Current Operating System: Linux bob 2.6.32-trunk-amd64 #1 SMP Sun Jan 10 22:40:40 UTC 2010 x86_64 Kernel command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-trunk-amd64 root=UUID=a51880f6-1f94-46e5-b75a-aca17bfb77e2 ro quiet Build Date: 20 January 2010 11:36:07PM xorg-server 2:1.7.4-2 (bui...@brahms.debian.org) Current version of pixman: 0.16.4 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Tue Jan 26 10:25:49 2010 (==) Using config file: /etc/X11/xorg.conf (==) No Layout section. Using the first Screen section. (**) |--Screen Default Screen (0) (**) | |--Monitor Configured Monitor (==) No device specified for screen Default Screen. Using the first device section listed. (**) | |--Device intel (==) Automatically adding devices (==) Automatically enabling devices (WW) The directory /usr/share/fonts/X11/cyrillic does not exist. Entry deleted from font path. (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType, built-ins (==) ModulePath set to /usr/lib/xorg/modules (II) Cannot locate a core pointer device. (II) Cannot locate a core keyboard device. (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. (II) Loader magic: 0x7c1600 (II) Module ABI versions: X.Org ANSI C Emulation: 0.4 X.Org Video Driver: 6.0 X.Org XInput driver : 7.0 X.Org Server Extension : 2.0 (++) using VT number 7 (--) PCI:*(0:0:2:0) 8086:2772:8086:4c43 Intel Corporation 82945G/GZ Integrated Graphics Controller rev 2, Mem @ 0xe010/524288, 0xd000/268435456,
Bug#639438: heavy NFS client usage triggers kernel BUG
Package: linux-2.6 Version: 2.6.32-35 Severity: normal Hi, heavy NFS client usage seems to trigger the kernel BUG below. Fedora seems to have encountered the same on s390x, and there's even a code snippet identified, but the report timed out: https://bugzilla.redhat.com/show_bug.cgi?id=508916 Kind regards Philipp Kern -- Package-specific info: ** Version: Linux version 2.6.32-5-s390x (Debian 2.6.32-35) (da...@debian.org) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Tue Jun 14 09:22:54 UTC 2011 ** Command line: root=/dev/disk/by-path/ccw-0.0.5204-part2 BOOT_IMAGE=0 ** Tainted: D (128) * Kernel has oopsed before. ** Kernel log: [619921.521773] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. [619921.521779] ffsb D 00362ea4 0 3090 3060 0x0004 [619921.521787] [619921.521792] 0001 0001 c9bcfc60 [619921.521799]0001 fac9c830 [619921.521806]0003 83897300 ffe40e70 00368fd0 [619921.521813]00368c20 00362090 c9bcfc60 c9bcfd68 [619921.521821] Call Trace: [619921.521823] ([00362090] schedule+0xb0c/0xc30) [619921.521836] [00362ea4] __mutex_lock_slowpath+0xd4/0x14c [619921.521844] [003633a2] mutex_lock+0x4e/0x6c [619921.521849] [0012f54a] generic_file_llseek+0x36/0x74 [619921.521856] [0012de98] SyS_llseek+0x68/0xd4 [619921.521864] [000299e6] sysc_noemu+0x10/0x16 [619921.521872] [77fca9ce] 0x77fca9ce [622081.545953] INFO: task ffsb:3694 blocked for more than 120 seconds. [622081.545961] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. [622081.545967] ffsb D 00362ea4 0 3694 3671 0x0004 [622081.545975] 83897368 003685d8 0003e60a 018dbc20 [622081.545981]018dbc20 ffcd0770 ffcd0770 018dbc60 [622081.545988]003685d8 fac9f380 feebd238 [622081.545995]0003 83897300 ffcd0738 fac9f7a8 [622081.546002]00368c20 00362090 018dbc60 018dbd68 [622081.546009] Call Trace: [622081.546012] ([00362090] schedule+0xb0c/0xc30) [622081.546025] [00362ea4] __mutex_lock_slowpath+0xd4/0x14c [622081.546032] [003633a2] mutex_lock+0x4e/0x6c [622081.546038] [0012f54a] generic_file_llseek+0x36/0x74 [622081.546045] [0012de98] SyS_llseek+0x68/0xd4 [622081.546052] [000299e6] sysc_noemu+0x10/0x16 [622081.546061] [77fca9ce] 0x77fca9ce [622081.546083] INFO: task ffsb:3706 blocked for more than 120 seconds. [622081.546086] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. [622081.546091] ffsb D 00362ea4 0 3706 3671 0x0004 [622081.546098] 83887368 003685d8 0003e60a 3954bc20 [622081.546104]3954bc20 ffcd0038 ffcd0038 3954bc60 [622081.546111]003685d8 fa9f40f8 feebd238 [622081.546118]0002 83887300 ffcd fa9f4520 [622081.546125]00368c20 00362090 3954bc60 3954bd68 [622081.546132] Call Trace: [622081.546134] ([00362090] schedule+0xb0c/0xc30) [622081.546140] [00362ea4] __mutex_lock_slowpath+0xd4/0x14c [622081.546146] [003633a2] mutex_lock+0x4e/0x6c [622081.546152] [0012f54a] generic_file_llseek+0x36/0x74 [622081.546157] [0012de98] SyS_llseek+0x68/0xd4 [622081.546163] [000299e6] sysc_noemu+0x10/0x16 [622081.546169] [77fca9ce] 0x77fca9ce [622081.546178] INFO: task ffsb:3729 blocked for more than 120 seconds. [622081.546182] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. [622081.546187] ffsb D 00362ea4 0 3729 3671 0x0004 [622081.546194] 83897368 003685d8 0003e60a 4e53bc20 [622081.546200]4e53bc20 63970770 63970770 4e53bc60 [622081.546207]003685d8 16d9f380 fef810e0 [622081.546214]16d9f720 83897300 63970738 0001 [622081.546220]00368c20 00362090 4e53bc60 4e53bd68 [622081.546228] Call Trace: [622081.546230] ([00362090] schedule+0xb0c/0xc30) [622081.546236] [00362ea4] __mutex_lock_slowpath+0xd4/0x14c [622081.546242] [003633a2] mutex_lock+0x4e/0x6c [622081.546247] [0012f54a] generic_file_llseek+0x36/0x74 [622081.546252] [0012de98]
Bug#639439: reportbug script fails on s390: no PCI bus
Package: linux-2.6 Version: 2.6.32-35 Severity: normal Hi, I get the following error message when reportbug tries to execute the bug script: | Gathering additional data, this may take a while... | Include network configuration and status from this computer? y | pcilib: Cannot open /proc/bus/pci | lspci: Cannot find any working access method. | The package bug script /usr/share/bug/linux-image-2.6.32-5-s390x/script exited with an error status (return code = 256). Do you still want to file a report? [y|N|q|?]? y The call to PCI utilities should not cause the script to fail on architectures that don't have a PCI bus. Kind regards Philipp Kern -- Package-specific info: ** Version: Linux version 2.6.32-5-s390x (Debian 2.6.32-35) (da...@debian.org) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Tue Jun 14 09:22:54 UTC 2011 -- 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/20110827092357.14522.69173.report...@i43prktlin1.ipd.uni-karlsruhe.de
Processed: retitle 639438 to heavy NFS client usage triggers kernel BUGG on s390 (s390x)
Processing commands for cont...@bugs.debian.org: retitle 639438 heavy NFS client usage triggers kernel BUGG on s390 (s390x) Bug #639438 [linux-2.6] heavy NFS client usage triggers kernel BUG Changed Bug title to 'heavy NFS client usage triggers kernel BUGG on s390 (s390x)' from 'heavy NFS client usage triggers kernel BUG' thanks Stopping processing here. Please contact me if you need assistance. -- 639438: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=639438 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.131443780719501.transcr...@bugs.debian.org
Bug#611750: Asus EeePC resume from hibernation fails
Hi, recently I've found a recomendation to unload wifi module (ath9k) before hibernate, after that my laptop is resuming ok. Without unloading the module sometimes go to reboot immediately after resume. It's about three weeks resuming is working fine (almost). Unfortunately I've done some other things like setting kernel options, upgrading to 3.0.0 so I'm not sure that module removing really helped but not something else. So you can consider bug is not reproduced here anymore. On Sat, Aug 27, 2011 at 1:18 PM, Jonathan Nieder jrnie...@gmail.com wrote: Hi Sergei, Sergei Stolyarov wrote: I'm using Samsung N150, problem still exists: sometimes system wake up correctly, sometimes with instant reboot after finishing resume. Please file a separate report if you can still reproduce this, and we can merge them later if they turn out to have the same cause. Thanks, Jonathan -- Sergei Stolyarov -- 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/ca+dmb89h_4jf7o9is6aw7jnw7gjnhd69q9qwroxpvtgirrq...@mail.gmail.com
Bug#639453: linux-image-2.6.39-bpo.2-amd64: Dropped Connections and Failed to create cgroup nnnn: -17 Kernel Message When vsftpd Spawning a New Process
Package: linux-2.6
Version: 2.6.39-3~bpo60+1
Severity: normal
I am experiencing the following issue with a Debian squeeze based server and
the most recent squeeze-backports kernel:
I realized that some vstfpd daemons randomly drop connections (sending a FIN
right after the initial TCP hand shake was completed). Furthermore, a Failed
to create cgroup : -17 message is logged by the kernel.
Furthermore, I am observing a steadily increasing number of directories named
like pids being created in the root of the cgroup virtual filesystem (mounted
at /cgroup). For each connection attempt to a vsftpd daemon a new directory is
created. Those directories seem to be never deleted. After a few days of uptime
there are about 7,500 directories while there constantly are only about 150
processes running (more or less idling, this server usually has low load).
When stracing vsftpd the call that fails seems to be this one (full output
below):
clone(child_stack=0, flags=0x2800|SIGCHLD) = -1 EEXIST (File exists)
Which makes me believe that those zombie directories in /cgroup might
conflict with the new pid . The longer the server is up the more likely it
becomes that connections are dropped.
Side note: The affected vsftpd daemons are running on a server that also is
hosting an LXC-based virtual server. I have experienced a steadily increasing
soft IRQ load on the server while a cgroup virtual filesystem being mounted. I
have upgraded to the recent squeeze-backports kernel which seems not to suffer
from this soft IRQ issue. vsftpd daemons running inside LXC containers do not
drop connections.
Below is some information I thought might be useful. If required, I will gladly
provide any additional information.
I am using vsftpd 2.3.2-3 which AFAIK is the most recent version available from
the squeeze and squeeze-backports repositories.
strace vsftpd /etc/vsftp.conf output (successful connection attempt):
alarm(1)= 0
rt_sigreturn(0x1) = -1 EINTR (Interrupted system call)
alarm(0)= 1
wait4(-1, NULL, WNOHANG, NULL) = 6385
wait4(-1, NULL, WNOHANG, NULL) = -1 ECHILD (No child processes)
accept(3, {sa_family=AF_INET, sin_port=htons(46631),
sin_addr=inet_addr(xxx.xxx.xxx.xxx)}, [16]) = 4
clone(child_stack=0, flags=0x2800|SIGCHLD) = 6387
close(4)= 0
accept(3, 0x7fffc3ecdf70, [28]) = ? ERESTARTSYS (To be restarted)
strace vsftpd /etc/vsftp.conf output (failed connection attempt):
alarm(1)= 0
rt_sigreturn(0x1) = -1 EINTR (Interrupted system call)
alarm(0)= 1
wait4(-1, NULL, WNOHANG, NULL) = 6387
wait4(-1, NULL, WNOHANG, NULL) = -1 ECHILD (No child processes)
accept(3, {sa_family=AF_INET, sin_port=htons(47917),
sin_addr=inet_addr(xxx.xxx.xxx.xxx)}, [16]) = 4
clone(child_stack=0, flags=0x2800|SIGCHLD) = -1 EEXIST (File exists)
close(4)= 0
accept(33, 0x7fffc3ecdf70, [28]) = ? ERESTARTSYS (To be restarted)
-- Package-specific info:
** Version:
Linux version 2.6.39-bpo.2-amd64 (Debian 2.6.39-3~bpo60+1)
(norb...@tretkowski.de) (gcc version 4.4.5 (Debian 4.4.5-8) ) #1 SMP Tue Jul 26
10:35:23 UTC 2011
** Command line:
BOOT_IMAGE=/vmlinuz-2.6.39-bpo.2-amd64 root=/dev/mapper/VG1-LV_ROOT ro quiet
** Not tainted
** Model information
sys_vendor: HP
product_name: ProLiant DL380 G6
product_version:
chassis_vendor: HP
chassis_version:
bios_vendor: HP
bios_version: P62
** Loaded modules:
Module Size Used by
ipt_LOG12605 6
xt_time12459 0
xt_connlimit 12554 0
xt_helper 12507 0
xt_realm 12423 0
xt_NFQUEUE 12544 0
xt_tcpmss 12425 0
xt_addrtype12557 3
xt_pkttype 12427 0
xt_TPROXY 12806 0
nf_tproxy_core 12404 1 xt_TPROXY,[permanent]
ip6_tables 21907 1 xt_TPROXY
nf_defrag_ipv6 12757 1 xt_TPROXY
xt_CLASSIFY12429 0
xt_mark12453 1
xt_hashlimit 13124 0
xt_comment 12427 24
ipt_REJECT 12465 4
xt_length 12460 0
xt_connmark12637 0
xt_owner 12423 0
xt_recent 13006 0
xt_iprange 12504 0
xt_policy 12506 0
xt_conntrack 12639 11
iptable_raw12524 0
veth 13170 0
xt_multiport 12518 6
xt_state 12503 8
xt_tcpudp 12527 46
xt_physdev 12468 2
iptable_mangle 12536 1
iptable_nat12928 0
nf_nat 18045 1 iptable_nat
nf_conntrack_ipv4 18081 22 iptable_nat,nf_nat
nf_conntrack 56001 8
Bug#639462: linux-image: unable to access (some) USB disks
Package: linux-2.6 Severity: minor Hi I had a USB disk that used to work (I think back in Squeeze); suddenly it no longer got a device and I could not use it. It was not super important, so I did not file the report back then. On my laptop I see the following in my dmesg log: (3.0.0-1-686-pae) [ 3865.900092] usb 1-1: new high speed USB device number 8 using ehci_hcd [ 3866.033178] usb 1-1: config 1 has an invalid interface number: 2 but max is 1 [ 3866.033187] usb 1-1: config 1 has no interface number 1 [ 3866.034295] usb 1-1: New USB device found, idVendor=04b4, idProduct=6830 [ 3866.034302] usb 1-1: New USB device strings: Mfr=0, Product=83, SerialNumber=70 [ 3866.034307] usb 1-1: Product: Cypress AT2LP RC58 [ 3866.034312] usb 1-1: SerialNumber: M000 [ 3866.035199] scsi9 : usb-storage 1-1:1.0 [ 3866.037076] generic-usb 0003:04B4:6830.0006: hiddev0,hidraw2: USB HID v1.10 Device [Cypress AT2LP RC58] on usb-:00:1d.7-1/input2 [ 3888.144064] usb 1-1: reset high speed USB device number 8 using ehci_hcd [ 3909.136069] usb 1-1: reset high speed USB device number 8 using ehci_hcd The reset high speed USB device keeps repeating until I unplug (or unpower) the USB device. On my newer home PC I see a slightly different message: (3.0.0-1-amd64) [ 51.874852] usb 1-1: new high speed USB device number 3 using ehci_hcd [ 52.007827] usb 1-1: config 1 has an invalid interface number: 2 but max is 1 [ 52.008210] usb 1-1: config 1 has no interface number 1 [ 52.009948] usb 1-1: New USB device found, idVendor=04b4, idProduct=6830 [ 52.010335] usb 1-1: New USB device strings: Mfr=0, Product=83, SerialNumber=70 [ 52.010919] usb 1-1: Product: Cypress AT2LP RC58 [ 52.011596] usb 1-1: SerialNumber: M000 [ 52.012790] scsi16 : usb-storage 1-1:1.0 [ 52.013838] ums-cypress: probe of 1-1:1.2 failed with error -5 [ 52.015651] generic-usb 0003:04B4:6830.0002: hiddev0,hidraw0: USB HID v1.10 Device [Cypress AT2LP RC58] on usb-:00:1a.7-1/input2 [ 74.071858] usb 1-1: reset high speed USB device number 3 using ehci_hcd [ 76.599841] usb 1-1: USB disconnect, device number 3 Last I checked I could mount USBpens and another USB disk (from a different vendor). ~Niels -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.0.0-1-686-pae (SMP w/2 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- 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/20110827123433.6611.76050.report...@getsu.thykier.net
Bug#639462: linux-image: unable to access (some) USB disks
On 2011-08-27 14:34, Niels Thykier wrote: Package: linux-2.6 Severity: minor Hi I had a USB disk that used to work (I think back in Squeeze); suddenly it no longer got a device and I could not use it. It was not super important, so I did not file the report back then. On my laptop I see the following in my dmesg log: (3.0.0-1-686-pae) [ 3865.900092] usb 1-1: new high speed USB device number 8 using ehci_hcd [ 3866.033178] usb 1-1: config 1 has an invalid interface number: 2 but max is 1 [ 3866.033187] usb 1-1: config 1 has no interface number 1 [ 3866.034295] usb 1-1: New USB device found, idVendor=04b4, idProduct=6830 [ 3866.034302] usb 1-1: New USB device strings: Mfr=0, Product=83, SerialNumber=70 [ 3866.034307] usb 1-1: Product: Cypress AT2LP RC58 [ 3866.034312] usb 1-1: SerialNumber: M000 [ 3866.035199] scsi9 : usb-storage 1-1:1.0 [ 3866.037076] generic-usb 0003:04B4:6830.0006: hiddev0,hidraw2: USB HID v1.10 Device [Cypress AT2LP RC58] on usb-:00:1d.7-1/input2 [ 3888.144064] usb 1-1: reset high speed USB device number 8 using ehci_hcd [ 3909.136069] usb 1-1: reset high speed USB device number 8 using ehci_hcd The reset high speed USB device keeps repeating until I unplug (or unpower) the USB device. On my newer home PC I see a slightly different message: (3.0.0-1-amd64) [ 51.874852] usb 1-1: new high speed USB device number 3 using ehci_hcd [ 52.007827] usb 1-1: config 1 has an invalid interface number: 2 but max is 1 [ 52.008210] usb 1-1: config 1 has no interface number 1 [ 52.009948] usb 1-1: New USB device found, idVendor=04b4, idProduct=6830 [ 52.010335] usb 1-1: New USB device strings: Mfr=0, Product=83, SerialNumber=70 [ 52.010919] usb 1-1: Product: Cypress AT2LP RC58 [ 52.011596] usb 1-1: SerialNumber: M000 [ 52.012790] scsi16 : usb-storage 1-1:1.0 [ 52.013838] ums-cypress: probe of 1-1:1.2 failed with error -5 [ 52.015651] generic-usb 0003:04B4:6830.0002: hiddev0,hidraw0: USB HID v1.10 Device [Cypress AT2LP RC58] on usb-:00:1a.7-1/input2 [ 74.071858] usb 1-1: reset high speed USB device number 3 using ehci_hcd [ 76.599841] usb 1-1: USB disconnect, device number 3 Last I checked I could mount USBpens and another USB disk (from a different vendor). ~Niels [...] Not sure if it is relevant; but the dmesg calls it a Cypress, but the device says Packard Bell is the vendor. ~Niels -- 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/4e58e564.4070...@thykier.net
Bug#639453: linux-image-2.6.39-bpo.2-amd64: Dropped Connections and Failed to create cgroup nnnn: -17 Kernel Message When vsftpd Spawning a New Process
On Sat, 2011-08-27 at 12:38 +0200, Dirk Weinhardt wrote: Package: linux-2.6 Version: 2.6.39-3~bpo60+1 Severity: normal I am experiencing the following issue with a Debian squeeze based server and the most recent squeeze-backports kernel: I realized that some vstfpd daemons randomly drop connections (sending a FIN right after the initial TCP hand shake was completed). Furthermore, a Failed to create cgroup : -17 message is logged by the kernel. Furthermore, I am observing a steadily increasing number of directories named like pids being created in the root of the cgroup virtual filesystem (mounted at /cgroup). For each connection attempt to a vsftpd daemon a new directory is created. Those directories seem to be never deleted. After a few days of uptime there are about 7,500 directories while there constantly are only about 150 processes running (more or less idling, this server usually has low load). Do they persist if you restart vsftpd? When stracing vsftpd the call that fails seems to be this one (full output below): clone(child_stack=0, flags=0x2800|SIGCHLD) = -1 EEXIST (File exists) Which makes me believe that those zombie directories in /cgroup might conflict with the new pid . The longer the server is up the more likely it becomes that connections are dropped. Side note: The affected vsftpd daemons are running on a server that also is hosting an LXC-based virtual server. I have experienced a steadily increasing soft IRQ load on the server while a cgroup virtual filesystem being mounted. I have upgraded to the recent squeeze-backports kernel which seems not to suffer from this soft IRQ issue. [...] That is bug #629373. Ben. signature.asc Description: This is a digitally signed message part
Bug#639453: linux-image-2.6.39-bpo.2-amd64: Dropped Connections and Failed to create cgroup nnnn: -17 Kernel Message When vsftpd Spawning a New Process
Furthermore, I am observing a steadily increasing number of directories named like pids being created in the root of the cgroup virtual filesystem (mounted at /cgroup). For each connection attempt to a vsftpd daemon a new directory is created. Those directories seem to be never deleted. After a few days of uptime there are about 7,500 directories while there constantly are only about 150 processes running (more or less idling, this server usually has low load). Do they persist if you restart vsftpd? Yes, all those directories persist if vsftp is restarted. The only way (I am aware of so far) to get rid of those is rebooting the system. Thanks for your quick response. Dirk -- 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/4e58ee40.30...@weinhardt.biz
Incomplete upload found in Debian upload queue
Probably you are the uploader of the following file(s) in the Debian upload queue directory: linux-2.6_3.0.0-3.diff.gz linux-2.6_3.0.0-3.dsc This looks like an upload, but a .changes file is missing, so the job cannot be processed. If no .changes file arrives within 23:29:38, the files will be deleted. If you didn't upload those files, please just ignore this message. 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/e1qxjdb-0006ka...@franck.debian.org
Processing of linux-2.6_3.0.0-3_multi.changes
linux-2.6_3.0.0-3_multi.changes uploaded successfully to localhost along with the files: linux-2.6_3.0.0-3.dsc linux-2.6_3.0.0-3.diff.gz linux-doc-3.0.0_3.0.0-3_all.deb linux-manual-3.0.0_3.0.0-3_all.deb linux-patch-debian-3.0.0_3.0.0-3_all.deb linux-source-3.0.0_3.0.0-3_all.deb linux-support-3.0.0-1_3.0.0-3_all.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/e1qxji7-0007mx...@franck.debian.org
Bug#635344: marked as done (cifs: kernel BUG at mm/slab.c:3059!)
Your message dated Sat, 27 Aug 2011 15:09:16 + with message-id e1qxkvy-00028p...@franck.debian.org and subject line Bug#635344: fixed in linux-2.6 3.0.0-3 has caused the Debian Bug report #635344, regarding cifs: kernel BUG at mm/slab.c:3059! 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.) -- 635344: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=635344 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 3.0.0-1 Severity: normal Hi! Today I did an upgrade to latest the Kernel release and after a short time had the system stopped with this: Jul 25 09:04:19 sti-nelson kernel: [ 670.769745] BUG: unable to handle kernel NULL pointer dereference at 00a0 Jul 25 09:04:19 sti-nelson kernel: [ 670.769774] IP: [81336123] down_write+0x16/0x27 Jul 25 09:04:19 sti-nelson kernel: [ 670.769787] PGD 0 Jul 25 09:04:19 sti-nelson kernel: [ 670.769792] Oops: 0002 [#1] SMP Jul 25 09:04:19 sti-nelson kernel: [ 670.769801] CPU 1 Jul 25 09:04:19 sti-nelson kernel: [ 670.769804] Modules linked in: des_generic ecb md4 hmac nls_utf8 cifs fscache ip6table_filter ip6_tables ebtable_nat ebtables powernow_k8 cpufreq_conservative cpufreq_userspa ce cpufreq_stats mperf ipt_REJECT xt_CHECKSUM iptable_mangle xt_tcpudp iptable_filter cpufreq_powersave ip_tables x_tables bridge stp ppdev lp vboxnetadp(O) vboxnetflt(O) vboxdrv(O) binfmt_misc fuse loop kvm_amd kvm usbhid hid snd_hda_codec_realtek sg nouveau ttm snd_hda_intel drm_kms_helper snd_hda_codec drm edac_core i2c_algo_bit sp5100_tco sr_mod edac_mce_amd snd_hwdep snd_pcm ohci_hcd snd_seq snd_timer snd_seq_device snd mxm_wmi i2c_piix4 i2c_core r8169 ata_generic k8temp ehci_hcd soundcore usbcore mii wmi pata_atiixp cdrom snd_page_alloc video parport_pc evdev floppy psmouse parport button processor serio_raw ext4 mbcache j bd2 crc16 dm_mod sd_mod crc_t10dif thermal ahci libahci fan thermal_sys libata scsi_mod Jul 25 09:04:19 sti-nelson kernel: [ 670.769990] Jul 25 09:04:19 sti-nelson kernel: [ 670.769994] Pid: 2738, comm: chromium Tainted: G O 3.0.0-1-amd64 #1 Itautec S.A. Infoway/SM 3321 Jul 25 09:04:19 sti-nelson kernel: [ 670.770008] RIP: 0010:[81336123] [81336123] down_write+0x16/0x27 Jul 25 09:04:19 sti-nelson kernel: [ 670.770019] RSP: 0018:88012a577ea8 EFLAGS: 00010296 Jul 25 09:04:19 sti-nelson kernel: [ 670.770025] RAX: 00a0 RBX: 00a0 RCX: fb80 Jul 25 09:04:19 sti-nelson kernel: [ 670.770032] RDX: 0001 RSI: 0003 RDI: 88012a576000 Jul 25 09:04:19 sti-nelson kernel: [ 670.770039] RBP: 00a0 R08: 7fc650822000 R09: Jul 25 09:04:19 sti-nelson kernel: [ 670.770046] R10: 7fc6720c3c18 R11: 0213 R12: 88012a4bf200 Jul 25 09:04:19 sti-nelson kernel: [ 670.770054] R13: 88011c7d8c38 R14: 7fc650822000 R15: 88011c7d8c38 Jul 25 09:04:19 sti-nelson kernel: [ 670.770061] FS: 7fc66c85a960() GS:88013fc8() knlGS:0b14c840 Jul 25 09:04:19 sti-nelson kernel: [ 670.770070] CS: 0010 DS: ES: CR0: 80050033 Jul 25 09:04:19 sti-nelson kernel: [ 670.770075] CR2: 00a0 CR3: 000130f18000 CR4: 06e0 Jul 25 09:04:19 sti-nelson kernel: [ 670.770083] DR0: DR1: DR2: Jul 25 09:04:19 sti-nelson kernel: [ 670.770090] DR3: DR6: 0ff0 DR7: 0400 Jul 25 09:04:19 sti-nelson kernel: [ 670.770097] Process chromium (pid: 2738, threadinfo 88012a576000, task 880130f54f60) Jul 25 09:04:19 sti-nelson kernel: [ 670.770105] Stack: Jul 25 09:04:19 sti-nelson kernel: [ 670.770108] 8115b236 88011c7d8c38 Jul 25 09:04:19 sti-nelson kernel: [ 670.770120] 7fc6503a2000 810d587c 88011c7d8c38 880139d99440 Jul 25 09:04:19 sti-nelson kernel: [ 670.770132] 810d6941 880139d99440 880139d99448 Jul 25 09:04:19 sti-nelson kernel: [ 670.770143] Call Trace: Jul 25 09:04:19 sti-nelson kernel: [ 670.770150] [8115b236] ? shm_close+0x26/0xa2 Jul 25 09:04:19 sti-nelson kernel: [ 670.770157] [810d587c] ? remove_vma+0x2c/0x71 Jul 25 09:04:19 sti-nelson kernel: [ 670.770164] [810d6941] ? do_munmap+0x2da/0x2f3 Jul 25 09:04:19 sti-nelson kernel: [ 670.770172] [8115c0ab] ? sys_shmdt+0x9a/0x127 Jul 25 09:04:19 sti-nelson kernel: [ 670.770182] [8133ba92] ?
Bug#637436: marked as done (cifs: kernel BUG at mm/slab.c:3059!)
Your message dated Sat, 27 Aug 2011 15:09:16 + with message-id e1qxkvy-00028p...@franck.debian.org and subject line Bug#635344: fixed in linux-2.6 3.0.0-3 has caused the Debian Bug report #635344, regarding cifs: kernel BUG at mm/slab.c:3059! 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.) -- 635344: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=635344 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 3.0.0-1 Severity: important Hi! I was using my computer and saw a kernel BUG: Aug 11 08:58:13 sti-nelson kernel: [144574.621166] kernel BUG at /tmp/buildd/linux-2.6-3.0.0/debian/build/source_amd64_none/mm/slab.c:3059! Aug 11 08:58:13 sti-nelson kernel: [144574.621176] invalid opcode: [#1] SMP Aug 11 08:58:13 sti-nelson kernel: [144574.621190] CPU 1 Aug 11 08:58:13 sti-nelson kernel: [144574.621193] Modules linked in: des_generic ecb md4 hmac nls_utf8 cifs fscache btrfs zlib_deflate crc32c libcrc32c ufs qnx4 hfsplus hfs minix ntfs vfat msdos fat jfs xfs reiserfs ext3 jbd ext2 ip6table_filter ip6_tables ebtable_nat ebtables ipt_REJECT xt_CHECKSUM iptable_mangle xt_tcpudp iptable_filter ip_tables x_tables bridge stp powernow_k8 cpufreq_conservative cpufreq_userspace cpufreq_stats mperf cpufreq_powersave ppdev lp binfmt_misc fuse loop kvm_amd kvm usbhid hid snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_seq snd_timer snd_seq_device ohci_hcd snd ehci_hcd nouveau ttm drm_kms_helper drm usbcore sg soundcore k8temp r8169 sr_mod mii i2c_algo_bit mxm_wmi wmi sp5100_tco edac_core ata_generic i2c_piix4 edac_mce_amd snd_page_alloc i2c_core video evdev cdrom pata_atiixp parport_pc floppy psmouse parport button serio_raw processor ext4 mbcache jbd2 crc16 dm_mod sd_mod crc_t10dif ahci libahci fan thermal therma l_sys libata scsi_mod Aug 11 08:58:13 sti-nelson kernel: [144574.621406] Aug 11 08:58:13 sti-nelson kernel: [144574.621410] Pid: 25134, comm: chromium Not tainted 3.0.0-1-amd64 #1 Itautec S.A. Infoway/SM 3321 Aug 11 08:58:13 sti-nelson kernel: [144574.621422] RIP: 0010:[810ec222] [810ec222] cache_alloc+0x133/0x258 Aug 11 08:58:13 sti-nelson kernel: [144574.621436] RSP: 0018:880138f0fe58 EFLAGS: 00010046 Aug 11 08:58:13 sti-nelson kernel: [144574.621442] RAX: 88007d03e000 RBX: 88013f40 RCX: 0070 Aug 11 08:58:13 sti-nelson kernel: [144574.621450] RDX: 002c RSI: dead00100100 RDI: 88013f044450 Aug 11 08:58:13 sti-nelson kernel: [144574.621457] RBP: 0010 R08: 88013f044460 R09: 0010 Aug 11 08:58:13 sti-nelson kernel: [144574.621464] R10: 005b R11: 0246 R12: 88013af42800 Aug 11 08:58:13 sti-nelson kernel: [144574.621471] R13: 88013f00 R14: R15: 000492d0 Aug 11 08:58:13 sti-nelson kernel: [144574.621479] FS: 7ffbfbd22960() GS:88013fc8() knlGS:0c098840 Aug 11 08:58:13 sti-nelson kernel: [144574.621487] CS: 0010 DS: ES: CR0: 80050033 Aug 11 08:58:13 sti-nelson kernel: [144574.621494] CR2: 7ffbfd997fa0 CR3: 000138e4d000 CR4: 06e0 Aug 11 08:58:13 sti-nelson kernel: [144574.621501] DR0: DR1: DR2: Aug 11 08:58:13 sti-nelson kernel: [144574.621508] DR3: DR6: 0ff0 DR7: 0400 Aug 11 08:58:13 sti-nelson kernel: [144574.621516] Process chromium (pid: 25134, threadinfo 880138f0e000, task 880139bad0e0) Aug 11 08:58:13 sti-nelson kernel: [144574.621524] Stack: Aug 11 08:58:13 sti-nelson kernel: [144574.621527] 00012c00 003c 88000243eee0 Aug 11 08:58:13 sti-nelson kernel: [144574.621540] 0020 88013f40 80d0 80d0 Aug 11 08:58:13 sti-nelson kernel: [144574.621551] 0292 810ecd4b 880138f0ff48 A picture with a call trace (that isn't available in the log file) is available at http://people.debian.org/~naoliv/misc/kernel-bug-slab.jpg I was able to find only this on google: https://lkml.org/lkml/2011/8/4/308 I can give more information or test any patch if needed. Thank you! Best regards, Nelson -- 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=/boot/vmlinuz-3.0.0-1-amd64 root=UUID=c73f4307-2dce-4e31-939c-e6cb20668551 ro
Bug#638656: marked as done (br2684: Sent packets truncated in VC routed mode)
Your message dated Sat, 27 Aug 2011 15:09:16 +
with message-id e1qxkvy-00028u...@franck.debian.org
and subject line Bug#638656: fixed in linux-2.6 3.0.0-3
has caused the Debian Bug report #638656,
regarding br2684: Sent packets truncated in VC routed mode
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.)
--
638656: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=638656
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-2.6
Version: 3.0.0-2
Tags: upstream, patch, fixed-upstream
Hello,
The transmit function for VC-MUX routed encapsulation wrongly
strips an ethernet header from IP packets, but there is no ethernet
header so it actually truncates the IP header.
The bug was introduced in Linux 2.6.26. It was fixed upstream in
Linux 3.1-rc1 and 3.0.3 by the following patch which has been added to
the 2.6.32-longterm queue and will hopefully be included in the next
2.6.32.46 release.
Please fix Linux 2.6.32 in Squeeze/stable.
The bug also exists in Linux 2.6.26 in Lenny/oldstable but the br2684ctl
package in Lenny/oldstable does not support routed mode.
Regards.
---
commit 55041e081ef433774279ecb6fc3fd30f741f5f37
From: Chas Williams c...@cmf.nrl.navy.mil
Date: Mon, 1 Aug 2011 17:56:14 -0700
Subject: atm: br2864: sent packets truncated in VC routed mode
commit a08af810cdc29d2ca930e8a869d3d01744c392d8 upstream.
Reported-by: Pascal Hambourg pas...@plouf.fr.eu.org
Signed-off-by: Chas Williams c...@cmf.nrl.navy.mil
Signed-off-by: David S. Miller da...@davemloft.net
Signed-off-by: Greg Kroah-Hartman gre...@suse.de
---
net/atm/br2684.c |2 --
1 file changed, 2 deletions(-)
--- a/net/atm/br2684.c
+++ b/net/atm/br2684.c
@@ -242,8 +242,6 @@ static int br2684_xmit_vcc(struct sk_buf
if (brdev-payload == p_bridged) {
skb_push(skb, 2);
memset(skb-data, 0, 2);
- } else { /* p_routed */
- skb_pull(skb, ETH_HLEN);
}
}
skb_debug(skb);
---End Message---
---BeginMessage---
Source: linux-2.6
Source-Version: 3.0.0-3
We believe that the bug you reported is fixed in the latest version of
linux-2.6, which is due to be installed in the Debian FTP archive:
linux-2.6_3.0.0-3.diff.gz
to main/l/linux-2.6/linux-2.6_3.0.0-3.diff.gz
linux-2.6_3.0.0-3.dsc
to main/l/linux-2.6/linux-2.6_3.0.0-3.dsc
linux-doc-3.0.0_3.0.0-3_all.deb
to main/l/linux-2.6/linux-doc-3.0.0_3.0.0-3_all.deb
linux-manual-3.0.0_3.0.0-3_all.deb
to main/l/linux-2.6/linux-manual-3.0.0_3.0.0-3_all.deb
linux-patch-debian-3.0.0_3.0.0-3_all.deb
to main/l/linux-2.6/linux-patch-debian-3.0.0_3.0.0-3_all.deb
linux-source-3.0.0_3.0.0-3_all.deb
to main/l/linux-2.6/linux-source-3.0.0_3.0.0-3_all.deb
linux-support-3.0.0-1_3.0.0-3_all.deb
to main/l/linux-2.6/linux-support-3.0.0-1_3.0.0-3_all.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 638...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Ben Hutchings b...@decadent.org.uk (supplier of updated linux-2.6 package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sat, 27 Aug 2011 08:04:02 +0100
Source: linux-2.6
Binary: linux-tools-3.0.0 linux-source-3.0.0 linux-doc-3.0.0 linux-manual-3.0.0
linux-patch-debian-3.0.0 linux-support-3.0.0-1 linux-libc-dev
linux-headers-3.0.0-1-all linux-headers-3.0.0-1-all-alpha
linux-headers-3.0.0-1-common linux-image-3.0.0-1-alpha-generic
linux-headers-3.0.0-1-alpha-generic linux-image-3.0.0-1-alpha-smp
linux-headers-3.0.0-1-alpha-smp linux-image-3.0.0-1-alpha-legacy
linux-headers-3.0.0-1-alpha-legacy linux-headers-3.0.0-1-all-amd64
linux-image-3.0.0-1-amd64 linux-headers-3.0.0-1-amd64
linux-image-3.0.0-1-amd64-dbg xen-linux-system-3.0.0-1-amd64
linux-headers-3.0.0-1-common-rt linux-image-3.0.0-1-rt-amd64
linux-headers-3.0.0-1-rt-amd64 linux-image-3.0.0-1-rt-amd64-dbg
xen-linux-system-3.0.0-1-rt-amd64 linux-headers-3.0.0-1-all-armel
linux-image-3.0.0-1-iop32x linux-headers-3.0.0-1-iop32x
linux-image-3.0.0-1-ixp4xx linux-headers-3.0.0-1-ixp4xx
linux-image-3.0.0-1-kirkwood linux-headers-3.0.0-1-kirkwood
linux-image-3.0.0-1-orion5x
linux-headers-3.0.0-1-orion5x
Bug#638696: marked as done (FTBFS on alpha: module sht15 needs gpiolib not selected by config.)
Your message dated Sat, 27 Aug 2011 15:09:16 + with message-id e1qxkvy-00028z...@franck.debian.org and subject line Bug#638696: fixed in linux-2.6 3.0.0-3 has caused the Debian Bug report #638696, regarding FTBFS on alpha: module sht15 needs gpiolib not selected by config. 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.) -- 638696: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=638696 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 3.0.0-2 Severity: normal From the build log: CC [M] drivers/hwmon/sht15.o In file included from +/build/buildd-linux-2.6_3.0.0-2-alpha-uWIvrQ/linux-2.6-3.0.0/debian/build/source_alpha_none/arch/alp +ha/include/asm/gpio.h:20, from +/build/buildd-linux-2.6_3.0.0-2-alpha-uWIvrQ/linux-2.6-3.0.0/debian/build/source_alpha_none/include/ +linux/gpio.h:18, from +/build/buildd-linux-2.6_3.0.0-2-alpha-uWIvrQ/linux-2.6-3.0.0/debian/build/source_alpha_none/drivers/ +hwmon/sht15.c:21: /build/buildd-linux-2.6_3.0.0-2-alpha-uWIvrQ/linux-2.6-3.0.0/debian/build/source_alpha_none/include/a +sm-generic/gpio.h: In function 'gpio_get_value_cansleep': /build/buildd-linux-2.6_3.0.0-2-alpha-uWIvrQ/linux-2.6-3.0.0/debian/build/source_alpha_none/include/a +sm-generic/gpio.h:223: error: implicit declaration of function 'gpio_get_value' Full build log available at: http://buildd.debian-ports.org/status/fetch.php?pkg=linux-2.6arch=alphaver=3.0.0-2stamp=1313880281 Setting CONFIG_GPIOLIB should fix this. Regards Michael Cree. ---End Message--- ---BeginMessage--- Source: linux-2.6 Source-Version: 3.0.0-3 We believe that the bug you reported is fixed in the latest version of linux-2.6, which is due to be installed in the Debian FTP archive: linux-2.6_3.0.0-3.diff.gz to main/l/linux-2.6/linux-2.6_3.0.0-3.diff.gz linux-2.6_3.0.0-3.dsc to main/l/linux-2.6/linux-2.6_3.0.0-3.dsc linux-doc-3.0.0_3.0.0-3_all.deb to main/l/linux-2.6/linux-doc-3.0.0_3.0.0-3_all.deb linux-manual-3.0.0_3.0.0-3_all.deb to main/l/linux-2.6/linux-manual-3.0.0_3.0.0-3_all.deb linux-patch-debian-3.0.0_3.0.0-3_all.deb to main/l/linux-2.6/linux-patch-debian-3.0.0_3.0.0-3_all.deb linux-source-3.0.0_3.0.0-3_all.deb to main/l/linux-2.6/linux-source-3.0.0_3.0.0-3_all.deb linux-support-3.0.0-1_3.0.0-3_all.deb to main/l/linux-2.6/linux-support-3.0.0-1_3.0.0-3_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 638...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ben Hutchings b...@decadent.org.uk (supplier of updated linux-2.6 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 27 Aug 2011 08:04:02 +0100 Source: linux-2.6 Binary: linux-tools-3.0.0 linux-source-3.0.0 linux-doc-3.0.0 linux-manual-3.0.0 linux-patch-debian-3.0.0 linux-support-3.0.0-1 linux-libc-dev linux-headers-3.0.0-1-all linux-headers-3.0.0-1-all-alpha linux-headers-3.0.0-1-common linux-image-3.0.0-1-alpha-generic linux-headers-3.0.0-1-alpha-generic linux-image-3.0.0-1-alpha-smp linux-headers-3.0.0-1-alpha-smp linux-image-3.0.0-1-alpha-legacy linux-headers-3.0.0-1-alpha-legacy linux-headers-3.0.0-1-all-amd64 linux-image-3.0.0-1-amd64 linux-headers-3.0.0-1-amd64 linux-image-3.0.0-1-amd64-dbg xen-linux-system-3.0.0-1-amd64 linux-headers-3.0.0-1-common-rt linux-image-3.0.0-1-rt-amd64 linux-headers-3.0.0-1-rt-amd64 linux-image-3.0.0-1-rt-amd64-dbg xen-linux-system-3.0.0-1-rt-amd64 linux-headers-3.0.0-1-all-armel linux-image-3.0.0-1-iop32x linux-headers-3.0.0-1-iop32x linux-image-3.0.0-1-ixp4xx linux-headers-3.0.0-1-ixp4xx linux-image-3.0.0-1-kirkwood linux-headers-3.0.0-1-kirkwood linux-image-3.0.0-1-orion5x linux-headers-3.0.0-1-orion5x linux-image-3.0.0-1-versatile linux-headers-3.0.0-1-versatile linux-headers-3.0.0-1-all-armhf linux-image-3.0.0-1-mx5 linux-headers-3.0.0-1-mx5 linux-image-3.0.0-1-omap linux-headers-3.0.0-1-omap linux-headers-3.0.0-1-all-hppa linux-image-3.0.0-1-parisc linux-headers-3.0.0-1-parisc linux-image-3.0.0-1-parisc-smp linux-headers-3.0.0-1-parisc-smp linux-image-3.0.0-1-parisc64 linux-headers-3.0.0-1-parisc64 linux-image-3.0.0-1-parisc64-smp linux-headers-3.0.0-1-parisc64-smp
Bug#638956: marked as done (include-network bug script doesn't work in case of bonding)
Your message dated Sat, 27 Aug 2011 15:09:16 + with message-id e1qxkvy-00028e...@franck.debian.org and subject line Bug#638956: fixed in linux-2.6 3.0.0-3 has caused the Debian Bug report #638956, regarding include-network bug script doesn't work in case of bonding 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.) -- 638956: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=638956 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.32-30 Severity: minor File: /usr/share/bug/linux-image-2.6.32-5-amd64/include-network include-network does a for dir in /sys/class/net/*; do ... cat $dir/features 3 but when bonding is active, there's also a file 'bonding_masters' under /sys/class/net/ and so the 'cat' fails. I've just replaced that line with [ -f $dir/features ] cat $dir/features 3 and it works. Cheers, Sandro -- System Information: Debian Release: 6.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.37-trunk-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages linux-image-2.6.32-5-amd64 depends on: ii debconf [debconf 1.5.37 Debian configuration management sy ii initramfs-tools 0.98.7 tools for generating an initramfs ii linux-base 2.6.37-1~experimental.1 Linux image base package ii module-init-tool 3.12-1 tools for managing Linux kernel mo Versions of packages linux-image-2.6.32-5-amd64 recommends: ii firmware-linux-f 2.6.37-1~experimental.1 Binary firmware for various driver Versions of packages linux-image-2.6.32-5-amd64 suggests: pn grub | lilo none (no description available) pn linux-doc-2.6.32 none (no description available) Versions of packages linux-image-2.6.32-5-amd64 is related to: pn firmware-bnx2 none (no description available) pn firmware-bnx2xnone (no description available) pn firmware-ipw2x00 none (no description available) pn firmware-ivtv none (no description available) ii firmware-iwlwifi 0.28 Binary firmware for Intel Wireless ii firmware-linux0.28 Binary firmware for various driver ii firmware-linux-nonfree0.28 Binary firmware for various driver pn firmware-qlogic none (no description available) pn firmware-ralink none (no description available) pn xen-hypervisornone (no description available) -- debconf information excluded ---End Message--- ---BeginMessage--- Source: linux-2.6 Source-Version: 3.0.0-3 We believe that the bug you reported is fixed in the latest version of linux-2.6, which is due to be installed in the Debian FTP archive: linux-2.6_3.0.0-3.diff.gz to main/l/linux-2.6/linux-2.6_3.0.0-3.diff.gz linux-2.6_3.0.0-3.dsc to main/l/linux-2.6/linux-2.6_3.0.0-3.dsc linux-doc-3.0.0_3.0.0-3_all.deb to main/l/linux-2.6/linux-doc-3.0.0_3.0.0-3_all.deb linux-manual-3.0.0_3.0.0-3_all.deb to main/l/linux-2.6/linux-manual-3.0.0_3.0.0-3_all.deb linux-patch-debian-3.0.0_3.0.0-3_all.deb to main/l/linux-2.6/linux-patch-debian-3.0.0_3.0.0-3_all.deb linux-source-3.0.0_3.0.0-3_all.deb to main/l/linux-2.6/linux-source-3.0.0_3.0.0-3_all.deb linux-support-3.0.0-1_3.0.0-3_all.deb to main/l/linux-2.6/linux-support-3.0.0-1_3.0.0-3_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 638...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ben Hutchings b...@decadent.org.uk (supplier of updated linux-2.6 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 27 Aug 2011 08:04:02 +0100 Source: linux-2.6 Binary: linux-tools-3.0.0 linux-source-3.0.0 linux-doc-3.0.0 linux-manual-3.0.0 linux-patch-debian-3.0.0 linux-support-3.0.0-1 linux-libc-dev linux-headers-3.0.0-1-all linux-headers-3.0.0-1-all-alpha linux-headers-3.0.0-1-common linux-image-3.0.0-1-alpha-generic linux-headers-3.0.0-1-alpha-generic
linux-2.6_3.0.0-3_multi.changes ACCEPTED into unstable
Accepted: linux-2.6_3.0.0-3.diff.gz to main/l/linux-2.6/linux-2.6_3.0.0-3.diff.gz linux-2.6_3.0.0-3.dsc to main/l/linux-2.6/linux-2.6_3.0.0-3.dsc linux-doc-3.0.0_3.0.0-3_all.deb to main/l/linux-2.6/linux-doc-3.0.0_3.0.0-3_all.deb linux-manual-3.0.0_3.0.0-3_all.deb to main/l/linux-2.6/linux-manual-3.0.0_3.0.0-3_all.deb linux-patch-debian-3.0.0_3.0.0-3_all.deb to main/l/linux-2.6/linux-patch-debian-3.0.0_3.0.0-3_all.deb linux-source-3.0.0_3.0.0-3_all.deb to main/l/linux-2.6/linux-source-3.0.0_3.0.0-3_all.deb linux-support-3.0.0-1_3.0.0-3_all.deb to main/l/linux-2.6/linux-support-3.0.0-1_3.0.0-3_all.deb Override entries for your package: linux-2.6_3.0.0-3.dsc - source devel linux-doc-3.0.0_3.0.0-3_all.deb - optional doc linux-manual-3.0.0_3.0.0-3_all.deb - optional doc linux-patch-debian-3.0.0_3.0.0-3_all.deb - optional kernel linux-source-3.0.0_3.0.0-3_all.deb - optional kernel linux-support-3.0.0-1_3.0.0-3_all.deb - optional devel Announcing to debian-devel-chan...@lists.debian.org Closing bugs: 635344 638656 638696 638956 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/e1qxkvy-00028i...@franck.debian.org
Bug#639505: Asus EeePC resume from hibernation fails
submitter 639505 Sergei Stolyarov sergei.stolya...@regolit.com retitle 639505 Samsung N150 can reboot on waking from hibernation unless ath9k unloaded notfound 639505 linux-2.6/2.6.32-30 quit Hi Sergei, Sergei Stolyarov wrote: recently I've found a recomendation to unload wifi module (ath9k) before hibernate, after that my laptop is resuming ok. Thanks, that's good to know. I've cloned the bug; your bug number is #639505. :) That sounds vaguely similar to http://bugs.debian.org/611946 which was fixed in v3.1-rc1, but that one did not appear until 2.6.35 (with a patch that is not part of squeeze). So there is more to figure out here. If you get a chance to test hibernation without unloading the module on the latest kernel from sid or squeeze, that would be welcome. Cheers, 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/20110827164938.gd10...@elie.gateway.2wire.net
Processed: Re: Asus EeePC resume from hibernation fails
Processing commands for cont...@bugs.debian.org: submitter 639505 Sergei Stolyarov sergei.stolya...@regolit.com Bug #639505 [linux-2.6] [regression] Asus EeePC: resume from hibernate fails when memory is scarce Changed Bug submitter to 'Sergei Stolyarov sergei.stolya...@regolit.com' from 'Gerald Turner gtur...@unzane.com' retitle 639505 Samsung N150 can reboot on waking from hibernation unless ath9k unloaded Bug #639505 [linux-2.6] [regression] Asus EeePC: resume from hibernate fails when memory is scarce Changed Bug title to 'Samsung N150 can reboot on waking from hibernation unless ath9k unloaded' from '[regression] Asus EeePC: resume from hibernate fails when memory is scarce' notfound 639505 linux-2.6/2.6.32-30 Bug #639505 [linux-2.6] Samsung N150 can reboot on waking from hibernation unless ath9k unloaded Bug No longer marked as found in versions linux-2.6/2.6.32-30. quit Stopping processing here. Please contact me if you need assistance. -- 639505: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=639505 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.131446378812553.transcr...@bugs.debian.org
Bug#622259: resuming from hibernation sometimes fails on eeepc 1002HA
On Saturday 27 August 2011, Jonathan Nieder wrote: I think we are long overdue to take this one upstream. I have a few questions anyway for before then: - does hibernation work for you if you try a sid (3.x) kernel? Would 2.6.39+35.1 (from squeeze-backports) do? It's a lot easier to get installed ;) Or is there a specific relevant patch that's gone into 3.*? robert. -- 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/201108271837.32153.b...@humanleg.org.uk
Bug#638913: marked as done (linux-source-3.0.0: cpu frequency speedstep_centrino Intel(R) Pentium(R) M processor)
Your message dated Sat, 27 Aug 2011 12:48:17 -0500
with message-id 20110827174817.ge10...@elie.gateway.2wire.net
and subject line Re: linux-source-3.0.0: cpu frequency speedstep_centrino
Intel(R) Pentium(R) M processor
has caused the Debian Bug report #638913,
regarding linux-source-3.0.0: cpu frequency speedstep_centrino Intel(R)
Pentium(R) M processor
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.)
--
638913: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=638913
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-source-3.0.0
Version: 3.0.0-1
Severity: normal
#modproble speedstep-centrino
throws No such device for Intel(R) Pentium(R) M processor (thinkpad T42)
diff my-speedstep-centrino.c speedstep-centrino.c:
c
46d45
CPU_DOTHAN_C0,
55,57c54,55
[CPU_DOTHAN_B0] = { 6, 13, 6 },
[CPU_DOTHAN_C0] = { 6, 13, 8 },
[CPU_MP4HT_D0] = {15, 3, 4 },
---
[CPU_DOTHAN_B0] = { 6, 13, 6 },
[CPU_MP4HT_D0] = {15, 3, 4 },
198,276d195
#define OPEX(mhz, base, mva, mvb, mvc, mvd) \
{ \
.frequency = (mhz) * 1000, \
.index = (((mhz)/(base)) 8) | ((mva - 700) / 16) \
}
/* Intel Pentium M processor 730 / 1.60 GHz (Sonoma) */
static struct cpufreq_frequency_table sonoma_1596[] =
{
OPEX( 798, 133, 988, 988, 988, 988),
OPEX(1064, 133, 1116, , 1084, 1079),
OPEX(1330, 133, 1244, 1233, 1180, 1169),
OPEX(1596, 133, 1356, 1356, 1260, 1260),
{ .frequency = CPUFREQ_TABLE_END }
};
/* Intel Pentium M processor 740 / 1.73 GHz (Sonoma) */
static struct cpufreq_frequency_table sonoma_1729[] =
{
OPEX( 798, 133, 988, 988, 988, 988),
OPEX(1064, 133, 1100, 1093, 1068, 1066),
OPEX(1330, 133, 1212, 1198, 1148, 1143),
OPEX(1729, 133, 1356, 1356, 1260, 1260),
{ .frequency = CPUFREQ_TABLE_END }
};
/* Intel Pentium M processor 750 / 1.86 GHz (Sonoma) */
static struct cpufreq_frequency_table sonoma_1862[] =
{
OPEX( 798, 133, 988, 988, 988, 988),
OPEX(1064, 133, 1084, 1080, 1068, 1056),
OPEX(1330, 133, 1180, 1172, 1132, 1124),
OPEX(1596, 133, 1276, 1264, 1196, 1192),
OPEX(1862, 133, 1356, 1356, 1260, 1260),
{ .frequency = CPUFREQ_TABLE_END }
};
/* Intel Pentium M processor 760 / 2.00 GHz (Sonoma) */
static struct cpufreq_frequency_table sonoma_1995[] =
{
OPEX( 798, 133, 988, 988, 988, 988),
OPEX(1064, 133, 1084, 1070, 1052, 1048),
OPEX(1330, 133, 1164, 1152, 1116, 1109),
OPEX(1596, 133, 1244, 1233, 1180, 1169),
OPEX(1995, 133, 1356, 1356, 1260, 1260),
{ .frequency = CPUFREQ_TABLE_END }
};
/* Intel Pentium M processor 770 / 2.13 GHz (Sonoma) */
static struct cpufreq_frequency_table sonoma_2128[] =
{
OPEX( 798, 133, 988, 988, 988, 988),
OPEX(1064, 133, 1068, 1065, 1052, 1042),
OPEX(1330, 133, 1148, 1142, 1100, 1097),
OPEX(1596, 133, 1228, 1218, 1164, 1151),
OPEX(1862, 133, 1308, 1295, 1212, 1206),
OPEX(2128, 133, 1372, 1372, 1260, 1260),
{ .frequency = CPUFREQ_TABLE_END }
};
/* Intel Pentium M processor 780 / 2.26 GHz (Sonoma) */
static struct cpufreq_frequency_table sonoma_2261[] =
{
OPEX( 798, 133, 988, 988, 988, 988),
OPEX(1064, 133, 1068, 1064, 1052, 1037),
OPEX(1330, 133, 1148, 1139, 1100, 1087),
OPEX(1596, 133, 1228, 1215, 1148, 1136),
OPEX(1862, 133, 1292, 1291, 1196, 1186),
OPEX(2261, 133, 1404, 1404, 1260, 1260),
{ .frequency = CPUFREQ_TABLE_END }
};
#undef OPEX
#define SONOMA(cpuid, max, base, name) \
{ .cpu_id = cpuid,\
.model_name = Intel(R) Pentium(R) M processor name GHz, \
.max_freq = (max)*1000, \
.op_points = sonoma_##max, \
}
299,306d217
/* Builtin tables for Dothan C0 CPUs, a.k.a Sonoma */
SONOMA(cpu_ids[CPU_DOTHAN_C0], 1596, 133, 1.60),
SONOMA(cpu_ids[CPU_DOTHAN_C0], 1729, 133, 1.73),
SONOMA(cpu_ids[CPU_DOTHAN_C0], 1862, 133, 1.86),
SONOMA(cpu_ids[CPU_DOTHAN_C0], 1995, 133, 2.00),
SONOMA(cpu_ids[CPU_DOTHAN_C0], 2128, 133, 2.13),
SONOMA(cpu_ids[CPU_DOTHAN_C0], 2261, 133, 2.26),
root@chase:/usr/src# man diff
root@chase:/usr/src# man patch
root@chase:/usr/src# diff
Bug#622259: resuming from hibernation sometimes fails on eeepc 1002HA
Robert Scott wrote: On Saturday 27 August 2011, Jonathan Nieder wrote: I think we are long overdue to take this one upstream. I have a few questions anyway for before then: - does hibernation work for you if you try a sid (3.x) kernel? Would 2.6.39+35.1 (from squeeze-backports) do? It's a lot easier to get installed ;) Or is there a specific relevant patch that's gone into 3.*? Sure, 2.6.39 is fine. 3.* from sid should install fine with linux-base and initramfs-tools from squeeze-backports, by the way. :) -- 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/20110827175306.gf10...@elie.gateway.2wire.net
Bug#639462: linux-image: unable to access (some) USB disks
Hi, Niels Thykier wrote: I had a USB disk that used to work (I think back in Squeeze); suddenly it no longer got a device and I could not use it. It was not super important, so I did not file the report back then. Weird. I don't see many potentially relevant recent changes upstream, but there is v3.1-rc1~234^2 (EHCI: fix direction handling for interrupt data toggles, 2011-07-19). If you get a chance to test v3.1-rc3 or later and report back, that would be excellent. If it doesn't work, please report this upstream at http://bugzilla.kernel.org/, product Drivers, component USB, and let us know the bug number so we can track it. 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/20110827181252.gg10...@elie.gateway.2wire.net
Processed: Re: linux-image: unable to access (some) USB disks
Processing commands for cont...@bugs.debian.org: found 639462 linux-2.6/3.0.0-1 Bug #639462 [linux-2.6] linux-image: unable to access (some) USB disks Bug Marked as found in versions linux-2.6/3.0.0-1. End of message, stopping processing here. Please contact me if you need assistance. -- 639462: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=639462 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.13144688493845.transcr...@bugs.debian.org
Bug#637660: nfs-kernel-server: gss_accept_sec_context failed - Encryption type not permitted
On 25/08/11 23:14, Jiri Kanicky wrote:
On 25/08/11 22:11, Jiri Kanicky wrote:
On 25/08/11 02:23, Bastian Blank wrote:
On Sun, Aug 14, 2011 at 12:43:14AM +1000, ganomi wrote:
Please get a name.
maverick:~# klist -ke /etc/krb5.keytab
Keytab name: WRFILE:/etc/krb5.keytab
KVNO Principal
--
4 nfs/maverick.firm.local@FIRM.LOCAL (des3-cbc-sha1)
4 nfs/maverick.firm.local@FIRM.LOCAL (des-cbc-crc)
Please setup standard encryption types.
root@knightrider:~# klist -ke /etc/krb5.keytab
Keytab name: WRFILE:/etc/krb5.keytab
KVNO Principal
--
6 nfs/knightrider.firm.local@FIRM.LOCAL (des-cbc-crc)
DES is disabled in the meantime. Use other encryption types.
ERROR: GSS-API: error in handle_nullreq: gss_accept_sec_context():
GSS_S_FAILURE (Unspecified GSS failure. Minor code may provide more
information) - Encryption type not permitted
I hope this message is clear.
Bastian
Dear Bastian.
I am not sure what do you mean by setup standard encryption types.
I believe that those are the standard encryption types. I haven't use
any special configuration. I tried to use the most basic setting for
Kerberos and LDAP.
[kdcdefaults]
kdc_ports = 750,88
[realms]
FIRM.LOCAL = {
database_name = /var/lib/krb5kdc/principal
admin_keytab = FILE:/etc/krb5kdc/kadm5.keytab
acl_file = /etc/krb5kdc/kadm5.acl
key_stash_file = /etc/krb5kdc/stash
kdc_ports = 750,88
max_life = 10h 0m 0s
max_renewable_life = 7d 0h 0m 0s
master_key_type = des3-hmac-sha1
supported_enctypes = des3-hmac-sha1:normal des-cbc-crc:normal
des:normal des:v4 des:norealm des:onlyrealm des:afs3
default_principal_flags = +preauth
}
Regards,
Jiri
Hi.
I found out that NFS (in RHEL 6) does not currently support
des-hmac-sha1, des-cbc-md5 neither des-cbc-crc. However, it should
support aes256-cts-hmac-sha1-96, aes128-cts-hmac-sha1-96,
des3-cbc-sha1 a arcfour-hmac. So, I am assuming that Debian Wheezy
have the same issue.
I will try to generate keys for those which are supported and re-test
it. I will come back with the results.
Thanks for giving me the idea.
Jiri
Hi.
So, I changed the encryption type to (aes256-cts-hmac-sha1-96). I
generated new keytab on the client (knightrider).
root@knightrider:/home/ganomi# klist -ke /etc/krb5.keytab
Keytab name: WRFILE:/etc/krb5.keytab
KVNO Principal
--
7 nfs/knightrider.firm.local@FIRM.LOCAL (aes256-cts-hmac-sha1-96)
I still have the same problem.
maverick:/home/ganomi/# rpc.svcgssd -fvvv
entering poll
leaving poll
handling null request
WARNING: gss_accept_sec_context failed
ERROR: GSS-API: error in handle_nullreq: gss_accept_sec_context():
GSS_S_FAILURE (Unspecified GSS failure. Minor code may provide more
information) - No supported encryption types (config file error?)
sending null reply
writing message: \x \x608202c706092a86......1314468539 851968
2529639149 \x \x
finished handling null request
Any idea? Could it be the same issue as in
https://bugzilla.redhat.com/show_bug.cgi?format=multipleid=719776
Jiri
Bug#639438: heavy NFS client usage triggers kernel BUG
Hi Philipp, Philipp Kern wrote: heavy NFS client usage seems to trigger the kernel BUG below. Can you reproduce this reliably? If so, it would be interesting to try v3.0-rc1 or later (e.g., a sid kernel) to see if the change to use the generic bitopts implementation helped. -- 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/20110827182553.gi10...@elie.gateway.2wire.net
Bug#637660: nfs-kernel-server: gss_accept_sec_context failed - Encryption type not permitted
On Sun, Aug 28, 2011 at 04:19:48AM +1000, Jiri Kanicky wrote: ERROR: GSS-API: error in handle_nullreq: gss_accept_sec_context(): GSS_S_FAILURE (Unspecified GSS failure. Minor code may provide more information) - No supported encryption types (config file error?) The error is different from the first one. Did you configure both the server and client with this encryption type? Bastian -- Captain's Log, star date 21:34.5... -- 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/20110827182814.ga14...@wavehammer.waldi.eu.org
Bug#637660: nfs-kernel-server: gss_accept_sec_context failed - Encryption type not permitted
On 28/08/11 04:28, Bastian Blank wrote:
On Sun, Aug 28, 2011 at 04:19:48AM +1000, Jiri Kanicky wrote:
ERROR: GSS-API: error in handle_nullreq: gss_accept_sec_context():
GSS_S_FAILURE (Unspecified GSS failure. Minor code may provide more
information) - No supported encryption types (config file error?)
The error is different from the first one. Did you configure both the
server and client with this encryption type?
Bastian
Hi Bastian.
Let me summarize all the setting and logs for each server and client:
KRB5/LDAP/NFS4 SERVER (maverick)
maverick:/home/ganomi/# cat /etc/krb5kdc/kdc.conf
[kdcdefaults]
kdc_ports = 750,88
[realms]
FIRM.LOCAL = {
database_name = /var/lib/krb5kdc/principal
admin_keytab = FILE:/etc/krb5kdc/kadm5.keytab
acl_file = /etc/krb5kdc/kadm5.acl
key_stash_file = /etc/krb5kdc/stash
kdc_ports = 750,88
max_life = 10h 0m 0s
max_renewable_life = 7d 0h 0m 0s
master_key_type = des3-hmac-sha1
supported_enctypes = des3-hmac-sha1:normal des-cbc-crc:normal
des:normal des:v4 des:norealm des:onlyrealm des:afs3 aes256-cts:normal
aes128-cts:normal des3-cbc-sha16:normal
default_principal_flags = +preauth
}
maverick:/home/ganomi/# klist -ke /etc/krb5.keytab
Keytab name: WRFILE:/etc/krb5.keytab
KVNO Principal
--
5 nfs/maverick.firm.local@FIRM.LOCAL (des3-cbc-sha1)
5 nfs/maverick.firm.local@FIRM.LOCAL (des-cbc-crc)
6 nfs/maverick.firm.local@FIRM.LOCAL (aes256-cts-hmac-sha1-96)
maverick:/home/ganomi/# rpc.svcgssd -fvvv
entering poll
leaving poll
handling null request
WARNING: gss_accept_sec_context failed
ERROR: GSS-API: error in handle_nullreq: gss_accept_sec_context():
GSS_S_FAILURE (Unspecified GSS failure. Minor code may provide more
information) - No supported encryption types (config file error?)
sending null reply
writing message: \x \x608202c706092a86......1314468539 851968
2529639149 \x \x
finished handling null request
CLIENT (knightrider)
==
root@knightrider:/home/ganomi# klist -ke /etc/krb5.keytab
Keytab name: WRFILE:/etc/krb5.keytab
KVNO Principal
--
7 nfs/knightrider.firm.local@FIRM.LOCAL
mailto:nfs/knightrider.firm.local@FIRM.LOCAL (aes256-cts-hmac-sha1-96)
root@knightrider:/home/ganomi# rpc.gssd -fvvv
ir_notify_handler: sig 37 si 0x7fff26026b30 data 0x7fff26026a00
dir_notify_handler: sig 37 si 0x7fff26022470 data 0x7fff26022340
dir_notify_handler: sig 37 si 0x7fff26022470 data 0x7fff26022340
handling gssd upcall (/var/lib/nfs/rpc_pipefs/nfs/clnt17)
handle_gssd_upcall: 'mech=krb5 uid=0 enctypes=18,17,16,23,3,1,2 '
handling krb5 upcall (/var/lib/nfs/rpc_pipefs/nfs/clnt17)
process_krb5_upcall: service is 'null'
Full hostname for 'maverick.firm.local' is 'maverick.firm.local'
Full hostname for 'knightrider.firm.local' is 'knightrider.firm.local'
No key table entry found for KNIGHTRIDER$@FIRM.LOCAL while getting
keytab entry for 'KNIGHTRIDER$@FIRM.LOCAL'
No key table entry found for root/knightrider.firm.local@FIRM.LOCAL
while getting keytab entry for 'root/knightrider.firm.local@FIRM.LOCAL'
Success getting keytab entry for 'nfs/knightrider.firm.local@FIRM.LOCAL'
Successfully obtained machine credentials for principal
'nfs/knightrider.firm.local@FIRM.LOCAL' stored in ccache
'FILE:/tmp/krb5cc_machine_FIRM.LOCAL'
INFO: Credentials in CC 'FILE:/tmp/krb5cc_machine_FIRM.LOCAL' are good
until 1314506238
using FILE:/tmp/krb5cc_machine_FIRM.LOCAL as credentials cache for
machine creds
using environment variable to select krb5 ccache
FILE:/tmp/krb5cc_machine_FIRM.LOCAL
creating context using fsuid 0 (save_uid 0)
creating tcp client for server maverick.firm.local
DEBUG: port already set to 2049
creating context with server n...@maverick.firm.local
WARNING: Failed to create krb5 context for user with uid 0 for server
maverick.firm.local
WARNING: Failed to create machine krb5 context with credentials cache
FILE:/tmp/krb5cc_machine_FIRM.LOCAL for server maverick.firm.local
WARNING: Machine cache is prematurely expired or corrupted trying to
recreate cache for server maverick.firm.local
Full hostname for 'maverick.firm.local' is 'maverick.firm.local'
Full hostname for 'knightrider.firm.local' is 'knightrider.firm.local'
No key table entry found for KNIGHTRIDER$@FIRM.LOCAL while getting
keytab entry for 'KNIGHTRIDER$@FIRM.LOCAL'
No key table entry found for root/knightrider.firm.local@FIRM.LOCAL
while getting keytab entry for 'root/knightrider.firm.local@FIRM.LOCAL'
Success getting keytab entry for 'nfs/knightrider.firm.local@FIRM.LOCAL'
INFO: Credentials in CC 'FILE:/tmp/krb5cc_machine_FIRM.LOCAL' are good
until 1314506238
INFO: Credentials in CC 'FILE:/tmp/krb5cc_machine_FIRM.LOCAL' are good
until 1314506238
using FILE:/tmp/krb5cc_machine_FIRM.LOCAL as credentials
Bug#638887: udev: cdrom_id process can not be killed
On Thu, 25 Aug 2011 12:42:00 -0500, Jonathan Nieder jrnie...@gmail.com wrote: Please send the full content of /var/log/dmesg after running echo d /proc/sysrq-trigger/proc/sysrq-trigger echo w /proc/sysrq-trigger when a process is in this hung state. Attached is a diff of the output of dmesg before and after echo'ing 'd' and 'w' to /proc/sysrq-trigger. You can see the cdrom_id process hung in D state. I can also confirm that the cdrom_id process becomes hung after I physically remove my laptop from it's dock (after ejecting it with eject button on the dock). This can be seen in the second attachment, which is a diff of syslog before and after the removal. jamie. --- 3-sleepattempt/dmesg 2011-08-27 11:47:03.258128750 -0700 +++ 5-echo-w/dmesg 2011-08-27 11:48:09.427721925 -0700 @@ -1,175 +1,4 @@ -[0.00] Initializing cgroup subsys cpuset -[0.00] Initializing cgroup subsys cpu -[0.00] 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 -[0.00] Command line: BOOT_IMAGE=/vmlinuz-3.0.0-1-amd64 root=/dev/mapper/servo-root ro vga=788 -[0.00] BIOS-provided physical RAM map: -[0.00] BIOS-e820: - 0009e800 (usable) -[0.00] BIOS-e820: 0009e800 - 000a (reserved) -[0.00] BIOS-e820: 000dc000 - 0010 (reserved) -[0.00] BIOS-e820: 0010 - bb27c000 (usable) -[0.00] BIOS-e820: bb27c000 - bb282000 (reserved) -[0.00] BIOS-e820: bb282000 - bb35f000 (usable) -[0.00] BIOS-e820: bb35f000 - bb371000 (reserved) -[0.00] BIOS-e820: bb371000 - bb3f2000 (ACPI NVS) -[0.00] BIOS-e820: bb3f2000 - bb40f000 (reserved) -[0.00] BIOS-e820: bb40f000 - bb46f000 (usable) -[0.00] BIOS-e820: bb46f000 - bb668000 (reserved) -[0.00] BIOS-e820: bb668000 - bb6e8000 (ACPI NVS) -[0.00] BIOS-e820: bb6e8000 - bb70f000 (reserved) -[0.00] BIOS-e820: bb70f000 - bb717000 (usable) -[0.00] BIOS-e820: bb717000 - bb71f000 (reserved) -[0.00] BIOS-e820: bb71f000 - bb76c000 (usable) -[0.00] BIOS-e820: bb76c000 - bb778000 (ACPI NVS) -[0.00] BIOS-e820: bb778000 - bb77b000 (ACPI data) -[0.00] BIOS-e820: bb77b000 - bb78b000 (ACPI NVS) -[0.00] BIOS-e820: bb78b000 - bb78c000 (ACPI data) -[0.00] BIOS-e820: bb78c000 - bb79f000 (ACPI NVS) -[0.00] BIOS-e820: bb79f000 - bb7ff000 (ACPI data) -[0.00] BIOS-e820: bb7ff000 - bb80 (usable) -[0.00] BIOS-e820: bb80 - c000 (reserved) -[0.00] BIOS-e820: e000 - f000 (reserved) -[0.00] BIOS-e820: feaff000 - feb0 (reserved) -[0.00] BIOS-e820: fec0 - fec1 (reserved) -[0.00] BIOS-e820: fed0 - fed00400 (reserved) -[0.00] BIOS-e820: fed1c000 - fed9 (reserved) -[0.00] BIOS-e820: fee0 - fee01000 (reserved) -[0.00] BIOS-e820: ff00 - 0001 (reserved) -[0.00] BIOS-e820: 0001 - 0001fc00 (usable) -[0.00] BIOS-e820: 0002 - 00023c00 (usable) -[0.00] NX (Execute Disable) protection: active -[0.00] DMI present. -[0.00] DMI: LENOVO 3626WVF/3626WVF, BIOS 6QET62WW (1.32 ) 12/17/2010 -[0.00] e820 update range: - 0001 (usable) == (reserved) -[0.00] e820 remove range: 000a - 0010 (usable) -[0.00] No AGP bridge found -[0.00] last_pfn = 0x23c000 max_arch_pfn = 0x4 -[0.00] MTRR default type: uncachable -[0.00] MTRR fixed ranges enabled: -[0.00] 0-9 write-back -[0.00] A-B uncachable -[0.00] C-F write-protect -[0.00] MTRR variable ranges enabled: -[0.00] 0 disabled -[0.00] 1 base 0 mask F8000 write-back -[0.00] 2 base 08000 mask FC000 write-back -[0.00] 3 base 1 mask F write-back -[0.00] 4 base 2 mask FC000 write-back -[0.00] 5 base 23C00 mask FFC00 uncachable -[0.00] 6 base 0BC00 mask FFC00 uncachable -[0.00] 7 disabled -[0.00] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106 -[0.00] e820 update range: bc00 - 0001 (usable) == (reserved) -[
Bug#638887: udev: cdrom_id process can not be killed
On Thu, 25 Aug 2011 12:42:00 -0500, Jonathan Nieder jrnie...@gmail.com wrote: Does downgrading udev or the kernel help? /var/log/dpkg.log should describe the upgrade history of both, and http://snapshot.debian.org/ has historical packages. If I keep everything else the same (same version of udev) I do *not* experience the problem with kernel: 2.6.38-2-amd64 but I *do* experience the problem with kernels: 2.6.39-2-amd64 3.0.0-1-amd64 If you really think it's worthwhile to try downgrading udev let me know, but because of the effort involved I'm going to hold off on that until I hear otherwise. jamie. pgpUmupePIW0t.pgp Description: PGP signature
Bug#638887: udev: cdrom_id process can not be killed
Jameson Graef Rollins wrote:
If I keep everything else the same (same version of udev) I do *not*
experience the problem with kernel:
2.6.38-2-amd64
but I *do* experience the problem with kernels:
2.6.39-2-amd64
3.0.0-1-amd64
If you really think it's worthwhile to try downgrading udev let me know,
Nah, that shouldn't be necessary. Thanks for figuring out the kernel
regression range.
The only potentially problematic commit I could find is the following.
It might be worth testing with it backed out.
commit bf2253a6f00e
Author: Tejun Heo t...@kernel.org
Date: Fri Apr 29 10:15:14 2011 +0200
cdrom: always check_disk_change() on open
cdrom_open() called check_disk_change() after the rest of open path
succeeded which leads to the following bizarre behavior.
* After media change, if the device opened without O_NONBLOCK,
open_for_data() naturally fails with -ENOMEDIA and
check_disk_change() is never called. The media is known to be gone
and the open failure makes it obvious to the userland but device
invalidation never happens.
* But if the device is opened with O_NONBLOCK, all the checks are
bypassed and cdrom_open() doesn't notice that the media is not there
and check_disk_change() is called and invalidation happens.
There's nothing to be gained by avoiding calling check_disk_change()
on open failure. Common cases end up calling check_disk_change()
anyway. All we get is inconsistent behavior.
Fix it by moving check_disk_change() invocation to the top of
cdrom_open() so that it always gets called regardless of how the rest
of open proceeds.
Stable: 2.6.38
Signed-off-by: Tejun Heo t...@kernel.org
Reported-by: Amit Shah amit.s...@redhat.com
Tested-by: Amit Shah amit.s...@redhat.com
Cc: sta...@kernel.org
Signed-off-by: Jens Axboe jax...@fusionio.com
diff --git a/drivers/cdrom/cdrom.c b/drivers/cdrom/cdrom.c
index 514dd8efaf73..75fb965b8f72 100644
--- a/drivers/cdrom/cdrom.c
+++ b/drivers/cdrom/cdrom.c
@@ -986,6 +986,9 @@ int cdrom_open(struct cdrom_device_info *cdi, struct
block_device *bdev, fmode_t
cdinfo(CD_OPEN, entering cdrom_open\n);
+ /* open is event synchronization point, check events first */
+ check_disk_change(bdev);
+
/* if this was a O_NONBLOCK open and we should honor the flags,
* do a quick open without drive/disc integrity checks. */
cdi-use_count++;
@@ -1012,9 +1015,6 @@ int cdrom_open(struct cdrom_device_info *cdi, struct
block_device *bdev, fmode_t
cdinfo(CD_OPEN, Use count for \/dev/%s\ now %d\n,
cdi-name, cdi-use_count);
- /* Do this on open. Don't wait for mount, because they might
- not be mounting, but opening with O_NONBLOCK */
- check_disk_change(bdev);
return 0;
err_release:
if (CDROM_CAN(CDC_LOCK) cdi-options CDO_LOCK) {
--
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/20110827193456.ga13...@elie.gateway.2wire.net
Bug#638887: udev: cdrom_id process can not be killed
On Sat, 27 Aug 2011 14:34:56 -0500, Jonathan Nieder jrnie...@gmail.com wrote: The only potentially problematic commit I could find is the following. It might be worth testing with it backed out. Hey, Jonathan. I haven't done much kernel rebuilding at all, so I'm not sure what's the best way to rebuild my kernel with this patch reverted. If you can give me a few pointers on a good way to do that it would be much appreciated. Presumably I should start by apt-getting source linux-image-3.0.0-1-amd64? Is a straight debuild then the best way to rebuild the kernel after applying the change? Thanks so much for the help. jamie. pgpkXKJjEq7ma.pgp Description: PGP signature
Bug#571279: suspend-script: kernel errors when resuming from suspend
found 571279 linux-2.6/2.6.32-30 quit Hi Eric, Eric Sheesley wrote: On Wed, 2010-02-24 at 17:35 -0500, Eric wrote: I am running Debian Squeeze on a Dell Studio 1557 with core i7 processor. [...] I also thought that could be an issue and so completely disabled selinux(wasn't set to enforcing anyway though) and still the exact same behavior. It's as if the system properly resumes (I can even type commands if the last window highlighted before suspend was a terminal, i just can't see anything other than a cursor) but just shows a black screen and cursor. Sorry for the long silence. Basic questions: - Please attach the output of /usr/share/bug/linux-image-$(uname -r)/script 31 and dmesg output right after booting, to give a sense of the hardware and drivers in use. - Do you have logs from before and after the resume ( dmesg dmesg_before; \ echo mem /sys/power/state; \ dmesg dmesg_after ) with selinux disabled? - Is this reproducible without the radeon driver loaded (one can test by blacklisting the radeon driver, for example)? - Is this reproducible with version 3.x from unstable? It should be possible to install with initramfs-tools and linux-base from squeeze-backports. If so, please report this upstream at - http://bugs.freedesktop.org/, product DRI, component DRM/Radeon if it seems to be a graphics driver problem - http://bugzilla.kernel.org/, product Power Management, component Suspend/Hibernation, otherwise and let us know the bug number so we can track it. 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/20110827204337.ga2...@elie.gateway.2wire.net
Processed: Re: suspend-script: kernel errors when resuming from suspend
Processing commands for cont...@bugs.debian.org: found 571279 linux-2.6/2.6.32-30 Bug #571279 [linux-2.6] suspend-script: kernel errors when resuming from suspend Bug Marked as found in versions linux-2.6/2.6.32-30. quit Stopping processing here. Please contact me if you need assistance. -- 571279: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=571279 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.131447783112471.transcr...@bugs.debian.org
Bug#639538: de4x5 is obsolete
Package: linux-2.6 Severity: normal Md is there any reason to keep building the de4x5 driver, which has been blacklisted by default by udev since forever? trave11er i think it was relevant for alpha, there were two drivers claiming the same PCI IDs (de4x5 and tulip?) trave11er they had cards which would work with one but not the other trave11er vorlon would remember :-) Md trave11er: correct about de4x5 and tulip, but the driver is built for de4x5 as well and is blacklisted for all architectures vorlon s/they/I/ vorlon I don't think you'd want to build it on any architecture except alpha... which we're not building for trave11er the chances of people still encountering such problems are probably pretty slim by now vorlon still pretty high if they're running alpha; almost zero otherwise Md and de4x5 on i386 has no aliases in modules.alias so it cannot be autoloaded anyway vorlon yep vorlon so I would definitely stop building it. If and when someone comes along who needs it again, they can work on getting tulip fixed instead -- ciao, Marco signature.asc Description: Digital signature
Bug#622259: resuming from hibernation sometimes fails on eeepc 1002HA
On Saturday 27 August 2011, Jonathan Nieder wrote: - does hibernation work for you if you try a sid (3.x) kernel? Would 2.6.39+35.1 (from squeeze-backports) do? It's a lot easier to get installed ;) Or is there a specific relevant patch that's gone into 3.*? Sure, 2.6.39 is fine. 3.* from sid should install fine with linux-base and initramfs-tools from squeeze-backports, by the way. :) Success. Hibernation works with 2.6.39-bpo.2-686-pae. This is on a Lenovo Ideapad S10-3. robert. -- 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/201108272318.20980.b...@humanleg.org.uk
Bug#623149: marked as done (Lenovo S10-3 fails to resume from hibernation)
Your message dated Sat, 27 Aug 2011 17:46:32 -0500 with message-id 20110827224632.ga7...@elie.gateway.2wire.net and subject line Re: resuming from hibernation sometimes fails on eeepc 1002HA has caused the Debian Bug report #622259, regarding Lenovo S10-3 fails to resume from hibernation 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.) -- 622259: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=622259 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.32-5-686 Version: 2.6.32-31 Severity: important Hi, I sure the last thing Ben needs is another netbook hibernation resume failure, but here we go. Using a Lenovo ideapad S10-3 (which afaik is a pretty much standard pine trail netbook), squeeze installed from scratch, the system fails to resume from hibernation in a similar way to bugs #613790 and #611750. Downgrading to 2.6.32-29 makes hibernation work. 2.6.32-30 and 2.6.32-31 do not work. Unlike some of the other submitters I have never had success with the latter kernels. It's not even intermittent. 100% failure. Please let me know if I can supply any more information. I'm perfectly capable of compiling the odd kernel if I get the time. Thanks, robert. ---End Message--- ---BeginMessage--- Version: 2.6.39-3 Robert Scott wrote: Success. Hibernation works with 2.6.39-bpo.2-686-pae. This is on a Lenovo Ideapad S10-3. Thanks for checking. Drat. The next thing to check would be if this is reproducible with v2.6.32.45 or v2.6.33.18 from kernel.org, so we can get upstream's help in figuring out where backporting the use mwait to offline a processor patch went wrong. By the way, what CPU do you use? (Please attach /proc/cpuinfo.) ---End Message---
Bug#622259: marked as done (linux-image-2.6.32-5-686: resuming from hibernation sometimes fails on eeepc 1002HA)
Your message dated Sat, 27 Aug 2011 17:46:32 -0500 with message-id 20110827224632.ga7...@elie.gateway.2wire.net and subject line Re: resuming from hibernation sometimes fails on eeepc 1002HA has caused the Debian Bug report #622259, regarding linux-image-2.6.32-5-686: resuming from hibernation sometimes fails on eeepc 1002HA 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.) -- 622259: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=622259 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.32-31 Severity: normal Hello, Since version 2.6.32-30, the Squeeze's Debian Linux kernel sometimes fails to resume from hibernation on my Asus eeepc 1002HA. As stated in bug #611750, I've observed that when resuming from hibernation, sometimes my computer was returning to Grub2's menu (without any error message), and I had to do a normal boot on my Debian Squeeze system (with file systems corrections), loosing my hibernation's state. The fail isn't automatic, but seems to happen more frequently after a while my computer was disconnected from AC and battery. On my system, I've first done a git bisect to identify the culprit patch (testing hibernation / resume about 5 times before to tag it 'ok'), and found a security uptstream patch 2.6.32.28. Then, I've done a manual bisecting among patches included in this security patch, and actually found that my problem comes from : x86-hotplug-use-mwait-to-offline-a-processor-fix-the-legacy-case.patch I've tested the original Debian Linux kernel 2.6.32-31, I got the same problem, and I'm now running a modified version of 2.6.32-31 with this former patch reverted, with success since then (about 3 weeks). I'm defining this new separate bug report following Ben Hutchings' suggestion in #611750 report. Fred. -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information not available ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation Mobile 945GME Express Memory Controller Hub [8086:27ac] (rev 03) Subsystem: ASUSTeK Computer Inc. Device [1043:830f] 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 Kernel driver in use: agpgart-intel 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 945GME Express Integrated Graphics Controller [8086:27ae] (rev 03) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:830f] 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 16 Region 0: Memory at fbd0 (32-bit, non-prefetchable) [size=512K] Region 1: I/O ports at dc80 [size=8] Region 2: Memory at d000 (32-bit, prefetchable) [size=256M] Region 3: Memory at fbcc (32-bit, non-prefetchable) [size=256K] Expansion ROM at unassigned [disabled] Capabilities: access denied Kernel driver in use: i915 Kernel modules: i915 00:02.1 Display controller [0380]: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller [8086:27a6] (rev 03) Subsystem: ASUSTeK Computer Inc. Device [1043:830f] 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 Region 0: Memory at fbd8 (32-bit, non-prefetchable) [size=512K] Capabilities: access denied 00:1b.0 Audio device [0403]: Intel Corporation N10/ICH 7 Family High Definition Audio Controller [8086:27d8] (rev 02) Subsystem: ASUSTeK Computer Inc. Device [1043:834a] 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: 32 bytes Interrupt: pin A routed to IRQ 16 Region 0: Memory at fbcb8000 (64-bit, non-prefetchable) [size=16K] Capabilities: access denied Kernel driver in use: HDA Intel Kernel modules: snd-hda-intel 00:1c.0 PCI
Bug#580832: [powerpc] Fanspeed at 100% at mininal load
Jonathan Nieder wrote: Hi, maximilian attems wrote: they used to be hardcoded loaded by initramfs. thought that powerpc plattform code had catched up and that udev would just load them. Sorry for the long silence. It looks like after the fix to Bug#603981, this is hardcoded again. Meanwhile, upstream there was v2.6.38-rc1~405^2~3 (powerpc/powermac: Make auto-loading of therm_pm72 possible, 2010-12-05), which unfortunately only affects therm_pm72 and not the windfarm_* modules. I'm currently running unstable on my G5 Mac. I've just upgraded to the 3.0.0 kernel (from the debian package) and if I remove the windfarm_core line from /etc/modules, the machine boots up and runs without excessive fan noise. Looks like this is fixed, at least for my machine. Erik, any news? Is the current hack good enough? :) Seems to be. Do you know if anyone has contacted upstream about this? I sent a couple fof emails but didn't even receive and ACK. Cheers, Erik -- -- Erik de Castro Lopo http://www.mega-nerd.com/ -- 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/20110828114631.b65786b6a235d839b4c1c...@mega-nerd.com
