Processed: found 548434 in 2.6.30-1, fixed 548434 in 2.6.32-8
Processing commands for cont...@bugs.debian.org:
> found 548434 2.6.30-1
Bug #548434 {Done: Matteo Cypriani } [linux-2.6] fdformat fails
completely with current kernel
There is no source info for the package 'linux-2.6' at version '2.6.30-1' with
architecture ''
Unable to make a source version for version '2.6.30-1'
Bug Marked as found in versions 2.6.30-1 and reopened.
> # apparently...
> fixed 548434 2.6.32-8
Bug #548434 [linux-2.6] fdformat fails completely with current kernel
There is no source info for the package 'linux-2.6' at version '2.6.32-8' with
architecture ''
Unable to make a source version for version '2.6.32-8'
Bug Marked as fixed in versions 2.6.32-8.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
548434: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=548434
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.127743119731816.transcr...@bugs.debian.org
Bug#584881: Lockups under heavy disk IO; md (RAID) resync/check implicated
On Thu, 2010-06-24 at 11:17 +0100, Ian Jackson wrote:
> Ben Hutchings writes ("Re: Bug#584881: Lockups under heavy disk IO; md (RAID)
> resync/check implicated"):
[...]
> > > Search the web suggests that symptoms very similar to mine are not
> > > uncommon, including instances without soft lockup messages, and none
> > > of the other users seem to have a similar disk layout.
> > >
> > > I can't easily test this theory but I think the unusual disk layout is
> > > probably simply making a race easier to trigger.
> >
> > Thinking of some kind of lock-dependency bug? Blocking on a mutex for a
> > long period should still trigger a soft-lockup message. Since there are
> > no messages from the kernel it's something of a mystery what's going on.
>
> The RAID system (md driver) has a separate mechanism for blocking
> writes, which it calls a "barrier". I think it is quite capable of
> indefinitely blocking all writes to a device without necessarily
> triggering the soft lockup detector.
[...]
I/O barriers are block I/O operations (not specific to md) that inhibit
reordering of read and write operations. They certainly should not be
blocking operations. Also, device-mapper did not support barriers until
after 2.6.26 so md will not be using them in the configuration you are
using.
Ben.
--
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.
signature.asc
Description: This is a digitally signed message part
Bug#587014: screen brightness can't be modified on Panasonic S9
On Fri, 2010-06-25 at 01:19 +0900, Nicolas Limare wrote: > Package: linux-2.6 > Severity: normal > > I just tried with 2.6.34, and it doesn't work either: > * in GNOME, pressing the light up/down keys trigger the little gnome > on-screen display showing a supposed brightness change, but the screen > brightness in unchanged > * in console mode, pressing these keys does nothing (and i noticed > nothing in the logs) > > (trying with reportbug this time; tell me if any extra info is needed) Unfortunately the information-gathering script we provide for reportbug only runs if you report the bug against one of the linux-image packages and not linux-2.6. Please can you send the content of /var/log/dmesg and the output of the 'lsmod' command. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Bug#583482: marked as done (linux-image-2.6.32: please apply patch for the intel hda regression)
Your message dated Fri, 25 Jun 2010 02:44:07 +0100 with message-id <1277430247.26161.217.ca...@localhost> and subject line Re: Bug#583482: linux-image-2.6.32: please apply patch for the intel hda regression has caused the Debian Bug report #583482, regarding linux-image-2.6.32: please apply patch for the intel hda regression 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.) -- 583482: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=583482 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-2.6 Version: 2.6.32-9 Severity: important File: linux-image-2.6.32 Tags: squeeze A patch for a kernel bug that eats 25% of the cpu resources in machines with hda intel is available http://marc.info/?l=linux- kernel&m=126177838017002&w=4 and is applied to the mainline kernel 2.6.34 As I know, version 2.6.32 will be in squeeze at release time and is affected by this bug, please apply the patch to it. -- Package-specific info: ** Version: Linux version 2.6.32-3-686 (Debian 2.6.32-9) (m...@debian.org) (gcc version 4.3.4 (Debian 4.3.4-8) ) #1 SMP Thu Feb 25 06:14:20 UTC 2010 ** Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-3-686 root=UUID=2f835e28-115a-4a19-9868-936d2fea1d5b ro quiet ** Tainted: P (1) * Proprietary module has been loaded. ** Kernel log: [21848.811398] scsi23 : SCSI emulation for USB Mass Storage devices [21848.811728] usb-storage: device found at 8 [21848.811733] usb-storage: waiting for device to settle before scanning [21849.928170] usb 4-3: new full speed USB device using ohci_hcd and address 31 [21850.112593] usb 4-3: device descriptor read/64, error -62 [21850.400067] usb 4-3: device descriptor read/64, error -62 [21850.680151] usb 4-3: new full speed USB device using ohci_hcd and address 32 [21850.860141] usb 4-3: device descriptor read/64, error -62 [21851.144092] usb 4-3: device descriptor read/64, error -62 [21851.424151] usb 4-3: new full speed USB device using ohci_hcd and address 33 [21851.832138] usb 4-3: device not accepting address 33, error -62 [21852.008190] usb 4-3: new full speed USB device using ohci_hcd and address 34 [21852.416134] usb 4-3: device not accepting address 34, error -62 [21852.416181] hub 4-0:1.0: unable to enumerate USB device on port 3 [21852.684158] usb 4-3: new full speed USB device using ohci_hcd and address 35 [21852.868082] usb 4-3: device descriptor read/64, error -62 [21853.156576] usb 4-3: device descriptor read/64, error -62 [21853.436674] usb 4-3: new full speed USB device using ohci_hcd and address 36 [21853.620092] usb 4-3: device descriptor read/64, error -62 [21853.839453] usb-storage: device scan complete [21853.904178] usb 4-3: device descriptor read/64, error -62 [21854.240679] usb 4-3: new full speed USB device using ohci_hcd and address 37 [21854.648130] usb 4-3: device not accepting address 37, error -62 [21854.824157] usb 4-3: new full speed USB device using ohci_hcd and address 38 [21855.232090] usb 4-3: device not accepting address 38, error -62 [21855.232143] hub 4-0:1.0: unable to enumerate USB device on port 3 [21855.232307] usb 2-1: USB disconnect, address 8 [21855.500095] usb 4-3: new full speed USB device using ohci_hcd and address 39 [21855.680077] usb 4-3: device descriptor read/64, error -62 [21855.964144] usb 4-3: device descriptor read/64, error -62 [21856.244104] usb 4-3: new full speed USB device using ohci_hcd and address 40 [21856.424084] usb 4-3: device descriptor read/64, error -62 [21856.708147] usb 4-3: device descriptor read/64, error -62 [21856.988085] usb 4-3: new full speed USB device using ohci_hcd and address 41 [21857.396128] usb 4-3: device not accepting address 41, error -62 [21857.572151] usb 4-3: new full speed USB device using ohci_hcd and address 42 [21857.980079] usb 4-3: device not accepting address 42, error -62 [21857.980136] hub 4-0:1.0: unable to enumerate USB device on port 3 [21858.248157] usb 4-3: new full speed USB device using ohci_hcd and address 43 [21858.432142] usb 4-3: device descriptor read/64, error -62 [21858.716074] usb 4-3: device descriptor read/64, error -62 [21858.996128] usb 4-3: new full speed USB device using ohci_hcd and address 44 [21859.176093] usb 4-3: device descriptor read/64, error -62 [21859.460153] usb 4-3: device descriptor read/64, error -62 [21859.740153] usb 4-3: new full speed USB device using ohci_hcd and address 45 [21860.148080] usb 4-3: device not accepting address 45, error -62 [21860.324096] usb 4-3: new full speed USB device using ohci_hcd and address 46 [21860.732078] usb 4-3: device not accepting address 46, er
Processed: tagging 584273
Processing commands for cont...@bugs.debian.org: > # Automatically generated email from bts, devscripts version 2.10.35lenny7 > tags 584273 + pending Bug #584273 [linux-2.6] linux-image-2.6.32-5-686: takes 'forever' to boot Added tag(s) pending. > End of message, stopping processing here. Please contact me if you need assistance. -- 584273: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=584273 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.127743000424671.transcr...@bugs.debian.org
Bug#587014: screen brightness can't be modified on Panasonic S9
Package: linux-2.6 Severity: normal atached dmesg and lsmod -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (700, 'testing'), (600, 'unstable'), (550, 'experimental'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.34-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Linux version 2.6.34-1-amd64 (Debian 2.6.34-1~experimental.2) (b...@decadent.org.uk) (gcc version 4.4.4 (Debian 4.4.4-4) ) #1 SMP Sun Jun 6 22:29:25 UTC 2010 [0.00] Command line: BOOT_IMAGE=/vmlinuz-2.6.34-1-amd64 root=/dev/mapper/sda2_crypt ro quiet [0.00] BIOS-provided physical RAM map: [0.00] BIOS-e820: - 0009bc00 (usable) [0.00] BIOS-e820: 0009bc00 - 000a (reserved) [0.00] BIOS-e820: 000e - 0010 (reserved) [0.00] BIOS-e820: 0010 - dacf1000 (usable) [0.00] BIOS-e820: dacf1000 - dad31000 (ACPI NVS) [0.00] BIOS-e820: dad31000 - dad54000 (reserved) [0.00] BIOS-e820: dad54000 - dad5a000 (usable) [0.00] BIOS-e820: dad5a000 - dad5f000 (ACPI NVS) [0.00] BIOS-e820: dad5f000 - dad8b000 (reserved) [0.00] BIOS-e820: dad8b000 - dad8c000 (ACPI NVS) [0.00] BIOS-e820: dad8c000 - dad9f000 (reserved) [0.00] BIOS-e820: dad9f000 - dada2000 (ACPI NVS) [0.00] BIOS-e820: dada2000 - dadb6000 (reserved) [0.00] BIOS-e820: dadb6000 - dadd6000 (ACPI NVS) [0.00] BIOS-e820: dadd6000 - dae04000 (reserved) [0.00] BIOS-e820: dae04000 - db80 (usable) [0.00] BIOS-e820: db80 - dc00 (reserved) [0.00] BIOS-e820: dde0 - e000 (reserved) [0.00] BIOS-e820: f800 - fc00 (reserved) [0.00] BIOS-e820: fec0 - fec01000 (reserved) [0.00] BIOS-e820: fed1 - fed14000 (reserved) [0.00] BIOS-e820: fed18000 - fed1a000 (reserved) [0.00] BIOS-e820: fed1c000 - fed2 (reserved) [0.00] BIOS-e820: fee0 - fee01000 (reserved) [0.00] BIOS-e820: ffa0 - ffc0 (reserved) [0.00] BIOS-e820: ffe0 - 0001 (reserved) [0.00] BIOS-e820: 0001 - 00011800 (usable) [0.00] NX (Execute Disable) protection: active [0.00] DMI 2.6 present. [0.00] AMI BIOS detected: BIOS may corrupt low RAM, working around it. [0.00] e820 update range: - 0001 (usable) ==> (reserved) [0.00] e820 update range: - 1000 (usable) ==> (reserved) [0.00] e820 remove range: 000a - 0010 (usable) [0.00] No AGP bridge found [0.00] last_pfn = 0x118000 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-C write-protect [0.00] D-E7FFF uncachable [0.00] E8000-F write-protect [0.00] MTRR variable ranges enabled: [0.00] 0 base 0 mask F8000 write-back [0.00] 1 base 08000 mask FC000 write-back [0.00] 2 base 0C000 mask FE000 write-back [0.00] 3 base 0DC00 mask FFC00 uncachable [0.00] 4 base 1 mask FE000 write-back [0.00] 5 base 11800 mask FF800 uncachable [0.00] 6 disabled [0.00] 7 disabled [0.00] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106 [0.00] e820 update range: dc00 - 0001 (usable) ==> (reserved) [0.00] last_pfn = 0xdb800 max_arch_pfn = 0x4 [0.00] initial memory mapped : 0 - 2000 [0.00] found SMP MP-table at [880fd470] fd470 [0.00] init_memory_mapping: -db80 [0.00] 00 - 00db80 page 2M [0.00] kernel direct mapping tables up to db80 @ 16000-1b000 [0.00] init_memory_mapping: 0001-00011800 [0.00] 01 - 011800 page 2M [0.00] kernel direct mapping tables up to 11800 @ 19000-1f000 [0.00] RAMDISK: 3763f000 - 37ff [0.00] ACPI: RSDP 000f0410 00024 (v02 MATBIO) [0.00] ACPI: XSDT dadafe18 0007C (v01 MATBIO CFS9-
Processed: Re: Bug#587065: udev breaks everything
Processing commands for cont...@bugs.debian.org: > reassign 587065 linux-2.6 Bug #587065 [udev] udev breaks everything Bug reassigned from package 'udev' to 'linux-2.6'. Bug No longer marked as found in versions udev/157-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 587065: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=587065 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.127742454326946.transcr...@bugs.debian.org
Re: Bug#587065: udev breaks everything
reassign 587065 linux-2.6 thanks On Jun 25, Jasen Betts wrote: > running /etc/init.d/udev start > > (like is done by /etc/rcS/S04udev ) renders keyboard and video > inoperable and halts the boot process (as far as I can tell - network > never comes up, case power button does nothing) Add udev.children-max=1 udev.exec-delay=10 to the kernel command line and then have fun finding out the buggy module. -- ciao, Marco signature.asc Description: Digital signature
Bug#587032: linux-source-2.6.34: make menuconfig segfaults
On Thu, 2010-06-24 at 17:53 +0200, Michal Suchanek wrote: > Package: linux-source-2.6.34 > Version: 2.6.34-1~experimental.2 > Severity: normal > > > # make menuconfig > HOSTCC scripts/basic/fixdep > /bin/sh: line 1: 909 Segmentation fault scripts/basic/fixdep > scripts/basic/.fixdep.d scripts/basic/fixdep 'gcc > -Wp,-MD,scripts/basic/.fixdep.d -Wall -Wmissing-prototypes > -Wstrict-prototypes -O2 -fomit-frame-pointer -o scripts/basic/fixdep > scripts/basic/fixdep.c ' > scripts/basic/.fixdep.tmp > make[1]: *** [scripts/basic/fixdep] Error 139 > make: *** [scripts_basic] Error 2 I can't reproduce this. Please send the output of 'make V=1 menuconfig'. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
RE: How to apt-get install new kernel 2.6.34 on debian ?
Thank for > Date: Fri, 25 Jun 2010 00:44:35 +0800 > Subject: Re: How to apt-get install new kernel 2.6.34 on debian ? > From: bluestonech...@gmail.com > To: jtam...@hotmail.com > CC: bj...@mork.no; basilarc...@gmail.com; debian-kernel@lists.debian.org > > 2010/6/24 lejkt lejkt : > > > Then i try to addkeyword "non-free" in my source.list > > (/etc/apt/source.list) file, i obtain: > > > > > > deb http://security.debian.org/ lenny/updates main > > deb-src http://security.debian.org/ lenny/updates main > > > > deb http://volatile.debian.org/debian-volatile lenny/volatile main > > deb-src http://volatile.debian.org/debian-volatile lenny/volatile main > > > > > > deb http://http.us.debian.org/debian lenny main contrib non-free > > deb-src http://http.us.debian.org/debian lenny main contrib non-free > > > you should add following line to /etc/apt/source.list: > deb http://http.us.debian.org/debian experimental main contrib non-free > deb-src http://http.us.debian.org/debian experimental main contrib non-free > > then try: > apt-get update > apt-get install linux-image-2.6.34-1-686 > > BTW: I think you'd better upgrade lenny to unstable. > > -- > Liang Guo > http://bluestone.cublog.cn > > > -- > 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/aanlktikjcvugmzmdgqdvueg7hpw1ifdqd35fqqqk8...@mail.gmail.com > _ Hotmail has tools for the New Busy. Search, chat and e-mail from your inbox. http://www.windowslive.com/campaign/thenewbusy?ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_1
Bug#587014: screen brightness can't be modified on Panasonic S9
Package: linux-2.6 Severity: normal I just tried with 2.6.34, and it doesn't work either: * in GNOME, pressing the light up/down keys trigger the little gnome on-screen display showing a supposed brightness change, but the screen brightness in unchanged * in console mode, pressing these keys does nothing (and i noticed nothing in the logs) (trying with reportbug this time; tell me if any extra info is needed) -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (700, 'testing'), (600, 'unstable'), (550, 'experimental'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.34-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (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/20100624161940.ga2...@nashi.ohno.39mm.net
Processed: Close #548434
Processing commands for cont...@bugs.debian.org: > reassign 548434 linux-2.6 Bug #548434 [fdutils] fdformat fails completely with current kernel Bug reassigned from package 'fdutils' to 'linux-2.6'. Bug No longer marked as found in versions fdutils/5.5-20060227-3. > close 548434 Bug#548434: fdformat fails completely with current kernel 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explanations to ael > thanks Stopping processing here. Please contact me if you need assistance. -- 548434: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=548434 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.127739831124950.transcr...@bugs.debian.org
Re: How to apt-get install new kernel 2.6.34 on debian ?
2010/6/24 lejkt lejkt : > Then i try to add keyword "non-free" in my source.list > (/etc/apt/source.list) file, i obtain: > > > deb http://security.debian.org/ lenny/updates main > deb-src http://security.debian.org/ lenny/updates main > > deb http://volatile.debian.org/debian-volatile lenny/volatile main > deb-src http://volatile.debian.org/debian-volatile lenny/volatile main > > > deb http://http.us.debian.org/debian lenny main contrib non-free > deb-src http://http.us.debian.org/debian lenny main contrib non-free > you should add following line to /etc/apt/source.list: deb http://http.us.debian.org/debian experimental main contrib non-free deb-src http://http.us.debian.org/debian experimental main contrib non-free then try: apt-get update apt-get install linux-image-2.6.34-1-686 BTW: I think you'd better upgrade lenny to unstable. -- Liang Guo http://bluestone.cublog.cn -- 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/aanlktikjcvugmzmdgqdvueg7hpw1ifdqd35fqqqk8...@mail.gmail.com
Bug#587032: linux-source-2.6.34: make menuconfig segfaults
Package: linux-source-2.6.34 Version: 2.6.34-1~experimental.2 Severity: normal # make menuconfig HOSTCC scripts/basic/fixdep /bin/sh: line 1: 909 Segmentation fault scripts/basic/fixdep scripts/basic/.fixdep.d scripts/basic/fixdep 'gcc -Wp,-MD,scripts/basic/.fixdep.d -Wall -Wmissing-prototypes -Wstrict-prototypes -O2 -fomit-frame-pointer -o scripts/basic/fixdep scripts/basic/fixdep.c ' > scripts/basic/.fixdep.tmp make[1]: *** [scripts/basic/fixdep] Error 139 make: *** [scripts_basic] Error 2 -- System Information: Debian Release: 5.0.4 APT prefers stable APT policy: (900, 'stable'), (700, 'testing'), (500, 'oldstable'), (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.34-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages linux-source-2.6.34 depends on: ii binutils2.18.1~cvs20080103-7 The GNU assembler, linker and bina ii bzip2 1.0.5-1 high-quality block-sorting file co Versions of packages linux-source-2.6.34 recommends: ii gcc 4:4.3.2-2 The GNU C compiler ii libc6-dev [libc-dev] 2.11.1-3 Embedded GNU C Library: Developmen ii make 3.81-5 The GNU version of the "make" util Versions of packages linux-source-2.6.34 suggests: ii kernel-package12.033 A utility for building Linux kerne pn libncurses-dev | ncurses-dev (no description available) pn libqt3-mt-dev (no description available) -- no debconf information -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100624155328.933.10363.report...@ipx7a-ion.ruk.cuni.cz
RE: How to apt-get install new kernel 2.6.34 on debian ?
Hello, After having made this: GNU:~# apt-get install -t experimental linux-image-2.6.34-1-i686 Reading package lists... Done Building dependency tree Reading state information... Done E: Couldn't find package linux-image-2.6.34-1-i686 Nothing happen Then i try to addkeyword "non-free" in my source.list (/etc/apt/source.list) file, i obtain: deb http://security.debian.org/ lenny/updates main deb-src http://security.debian.org/ lenny/updates main deb http://volatile.debian.org/debian-volatile lenny/volatile main deb-src http://volatile.debian.org/debian-volatile lenny/volatile main deb http://http.us.debian.org/debian lenny main contrib non-free deb-src http://http.us.debian.org/debian lenny main contrib non-free Then i try again GNU:~# aptitude search linux-image-2.6.34 GNU:~# or GNU:~# apt-cache search linux-image-2.6.34 GNU:~# and GNU:~# apt-get install -t experimental linux-image-2.6.34-1-i686 Reading package lists... Done Building dependency tree Reading state information... Done E: Couldn't find package linux-image-2.6.34-1-i686 nothing found.. Please help me, i want to install the new kernel (2.6.34) in my computer James ~ ~ > Date: Tue, 22 Jun 2010 16:49:19 +0800 > Subject: Re: How to apt-get install new kernel 2.6.34 on debian ? > From: bluestonech...@gmail.com > To: jtam...@hotmail.com > CC: bj...@mork.no; basilarc...@gmail.com; debian-kernel@lists.debian.org > > 2010/6/22 lejkt lejkt : > > How to apt-get install new kernel 2.6.34 on debian ? > 2.6.34 is in experimental distribution. you may enable experimental > in your /etc/apt/sources.list, and run > > apt-get install -t experimental linux-image-2.6.34-1-amd64 > > or others depending on your archtecture, > > -- > Liang Guo > http://bluestone.cublog.cn > > > -- > 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/aanlktikrhkizvpvd_aat0e3bnymd_m0ynl0bet6_f...@mail.gmail.com > _ The New Busy think 9 to 5 is a cute idea. Combine multiple calendars with Hotmail. http://www.windowslive.com/campaign/thenewbusy?tile=multicalendar&ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_5
Bug#587014: [linux-2.6] screen brightness can't be modified on Panasonic S9
On Thu, Jun 24, 2010 at 11:22:51PM +0900, Nicolas Limare wrote: > Package: linux-2.6 > Severity: normal > > --- Please enter the report below this line. --- > > Presing the "light up" / "light down" keys doesn't modify the LCD > screen brightness. > Directly writing to /sys/class/backlight/panasonic/brightness has the > same effect : nothing. > /sys/class/backlight/panasonic/actual_brightness is modified, but the > screen brightness isn't affected. > > I tried to reboot with lenny 2.6.26-2 kernel on the same system, and > the brightness could be changed by pressing the up/down keys, so I > believe it is a kernel issue (but gdm couldn't properly start, so it > is not a proper workaround). > > It is a serious issue, since the screen default brightness is very > strong and uncomfortable. > > I believe it is related to > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/588983 > > I tried to use acpi packages from unstable, without improvement. please use reportbug the next time this report is missing important info, followup is possible with: reportbug -N did you try 2.6.34 from experimental, does it work there? -- 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/20100624144142.gw9...@baikonur.stro.at
Bug#587014: [linux-2.6] screen brightness can't be modified on Panasonic S9
Package: linux-2.6 Severity: normal --- Please enter the report below this line. --- Presing the "light up" / "light down" keys doesn't modify the LCD screen brightness. Directly writing to /sys/class/backlight/panasonic/brightness has the same effect : nothing. /sys/class/backlight/panasonic/actual_brightness is modified, but the screen brightness isn't affected. I tried to reboot with lenny 2.6.26-2 kernel on the same system, and the brightness could be changed by pressing the up/down keys, so I believe it is a kernel issue (but gdm couldn't properly start, so it is not a proper workaround). It is a serious issue, since the screen default brightness is very strong and uncomfortable. I believe it is related to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/588983 I tried to use acpi packages from unstable, without improvement. --- System information. --- Architecture: amd64 Kernel: Linux 2.6.32-5-amd64 Debian Release: squeeze/sid 700 testing security.debian.org 700 testing ftp.jaist.ac.jp 600 unstableftp.jaist.ac.jp 500 stable ftp.jaist.ac.jp 00:00.0 Host bridge: Intel Corporation Core Processor DRAM Controller (rev 02) Subsystem: Matsushita Electric Industrial Co., Ltd. Device 8338 Flags: bus master, fast devsel, latency 0 Capabilities: [e0] Vendor Specific Information: Len=0c Kernel driver in use: agpgart-intel 00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 02) (prog-if 00 [VGA controller]) Subsystem: Matsushita Electric Industrial Co., Ltd. Device 8338 Flags: bus master, fast devsel, latency 0, IRQ 35 Memory at f000 (64-bit, non-prefetchable) [size=4M] Memory at e000 (64-bit, prefetchable) [size=256M] I/O ports at e0b0 [size=8] Expansion ROM at [disabled] Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Capabilities: [d0] Power Management version 2 Capabilities: [a4] PCI Advanced Features Kernel driver in use: i915 00:19.0 Ethernet controller: Intel Corporation 82577LM Gigabit Network Connection (rev 06) Subsystem: Matsushita Electric Industrial Co., Ltd. Device 8338 Flags: bus master, fast devsel, latency 0, IRQ 33 Memory at f4a0 (32-bit, non-prefetchable) [size=128K] Memory at f4a29000 (32-bit, non-prefetchable) [size=4K] I/O ports at e040 [size=32] Capabilities: [c8] Power Management version 2 Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [e0] PCI Advanced Features Kernel driver in use: e1000e 00:1a.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 06) (prog-if 20 [EHCI]) Subsystem: Matsushita Electric Industrial Co., Ltd. Device 8338 Flags: bus master, medium devsel, latency 0, IRQ 16 Memory at f4a28000 (32-bit, non-prefetchable) [size=1K] Capabilities: [50] Power Management version 2 Capabilities: [58] Debug port: BAR=1 offset=00a0 Capabilities: [98] PCI Advanced Features Kernel driver in use: ehci_hcd 00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 06) Subsystem: Matsushita Electric Industrial Co., Ltd. Device 8338 Flags: bus master, fast devsel, latency 0, IRQ 22 Memory at f4a2 (64-bit, non-prefetchable) [size=16K] Capabilities: [50] Power Management version 2 Capabilities: [60] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00 Capabilities: [100] Virtual Channel Capabilities: [130] Root Complex Link Kernel driver in use: HDA Intel 00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 1 (rev 06) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 I/O behind bridge: d000-dfff Memory behind bridge: f480-f49f Capabilities: [40] Express Root Port (Slot+), MSI 00 Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit- Capabilities: [90] Subsystem: Matsushita Electric Industrial Co., Ltd. Device 8338 Capabilities: [a0] Power Management version 2 Kernel driver in use: pcieport 00:1c.1 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 2 (rev 06) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=02, subordinate=09, sec-latency=0 I/O behind bridge: c000-cfff Memory behind bridge: f460-f47f Prefetchable memory behind bridge: f4b0-f4cf Capabilities: [40] Express Root Port (Slot+), MSI 00
Bug#584881: Lockups under heavy disk IO; md (RAID) resync/check implicated
Ben Hutchings writes ("Re: Bug#584881: Lockups under heavy disk IO; md (RAID)
resync/check implicated"):
> Even if you can't get a process dump, you can get some useful
> information with:
Right, thanks.
> 'd' - show locks held
> 'l' - show backtrace for active CPUs
> 'w' - show uninterruptible tasks
I'll try these although I suspect thousands of uninterruptible tasks.
> > Search the web suggests that symptoms very similar to mine are not
> > uncommon, including instances without soft lockup messages, and none
> > of the other users seem to have a similar disk layout.
> >
> > I can't easily test this theory but I think the unusual disk layout is
> > probably simply making a race easier to trigger.
>
> Thinking of some kind of lock-dependency bug? Blocking on a mutex for a
> long period should still trigger a soft-lockup message. Since there are
> no messages from the kernel it's something of a mystery what's going on.
The RAID system (md driver) has a separate mechanism for blocking
writes, which it calls a "barrier". I think it is quite capable of
indefinitely blocking all writes to a device without necessarily
triggering the soft lockup detector.
> > I'll see if I can borrow a spare R210 from Jump, in which case I may
> > be able to reproduce the problem in controlled conditions on my coffee
> > table at home (and with access to the VGA console). Which kernel
> > should I test in that case ?
>
> Please try 2.6.34 from experimental.
Will do. I'll get back to you.
Thanks,
Ian.
--
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/19491.12472.880707.704...@chiark.greenend.org.uk
