Bug#513537: linux-image-2.6.26-1-openvz-amd64 hanging
On Wednesday 18 November 2009 01:57:34 am Tom Rathborne wrote: Hi Vitaliy, Daniel On Wed, Jul 22, 2009 at 02:20:15PM +0400, Vitaliy Gusev wrote: On Wednesday 22 July 2009 06:05:08 am Tom Rathborne wrote: Vitaliy wrote: Hello, Tom!. Does this problem still actual for you? Can you check attached patch? ( do not tune off CONFIG_USER_RESOURCE) This patch makes sense. I have applied it to the latest Debian Lenny kernel and will let you know what happens! This patch fixes lockdep warning, so you can compile kernel with LOCKDEP_DEBUG. I no longer work for Tiny Planet, but I am happy to report that the server has been running for 79 days with this patch with no kernel errors or lockups! Hello! Goog news! According to http://bugzilla.openvz.org/show_bug.cgi?id=1161 Are you sure that this bug is related to your problem? the OpenVZ bug is PATCHSENT ... case closed, more or less! :) Nice working with you! Cheers, Tom -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: linux-2.6 piuparts error
* maximilian attems | 2009-11-17 11:10:46 [+0100]:
0m54.3s ERROR: FAIL: Package purging left files on system:
/etc/kernel-img.conf not owned
oh
so either it is a failure to generate such a file in postinst (as we
shouldn't really need it!?), or one would want to remove it on purge,
which opens another can of worms as this file is unowned in real boxes
and usualy created by d-i.
the best argument is that due to the convulated questions postinst
wanted to ask you in the past we had never reached that point of
generating this conffile in postinst.
What is the long term goal? Do you plan do to get rid of kernel-img.conf
and let the individual boot loader handle this kind of things?
You are changing the default behavior of palo here. However the values
are written very late. link_in_boot for instance is only evalueted at
the begin of the script. So it should not really matter for postinst at
least.
The do_symlink thing is only required by people that don't have their
setup right, isn't it? So grub refers to /vmlinuz but kernel itself is
not in / but in /boot. So if those people would fix their boxes we could
get rid of do_symlink for instance right?
diff --git a/linux-2.6/debian/templates/temp.image.plain/postinst
b/linux-2.6/debian/templates/temp.image.plain/postinst
index ae8c797..43dba4d 100755
--- a/linux-2.6/debian/templates/temp.image.plain/postinst
+++ b/linux-2.6/debian/templates/temp.image.plain/postinst
@@ -478,24 +478,10 @@ sub handle_missing_link {
die(Failed to copy . $realimageloc . $image_name to
. $image_dest . $kimage .\n);
}
- }
- else {
+ } else {
if (! $have_conffile) {
# current default
$do_symlink = Yes;
-
- if (open(CONF, $CONF_LOC)) {
-print CONF # Kernel Image management overrides\n;
-print CONF # See kernel-img.conf(5) for details\n;
-if ($loader =~ /palo/i) {
- print CONF link_in_boot = Yes\n;
- print CONF do_symlinks = Yes\n;
- print CONF relative_links = Yes\n;
- print CONF do_bootloader = No\n;
-}
-close CONF;
- }
- $have_conffile = Yes;
}
}
Sebastian
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#513537: linux-image-2.6.26-1-openvz-amd64 hanging
On Wednesday 18 November 2009 12:25:15 pm Vitaliy Gusev wrote: On Wednesday 18 November 2009 01:57:34 am Tom Rathborne wrote: Hi Vitaliy, Daniel On Wed, Jul 22, 2009 at 02:20:15PM +0400, Vitaliy Gusev wrote: On Wednesday 22 July 2009 06:05:08 am Tom Rathborne wrote: Vitaliy wrote: Hello, Tom!. Does this problem still actual for you? Can you check attached patch? ( do not tune off CONFIG_USER_RESOURCE) This patch makes sense. I have applied it to the latest Debian Lenny kernel and will let you know what happens! This patch fixes lockdep warning, so you can compile kernel with LOCKDEP_DEBUG. I no longer work for Tiny Planet, but I am happy to report that the server has been running for 79 days with this patch with no kernel errors or lockups! Hello! Goog news! According to http://bugzilla.openvz.org/show_bug.cgi?id=1161 Are you sure that this bug is related to your problem? Have you also aplied patch diff-inotify-delay-final-put-20090204 in your kernel? My patch fix-deadlock-sk_callback_lock.patch fixes only lockdep warning. Of course, lockdep warning points to possible lockup but I think this possible lockup is not related to your problem. the OpenVZ bug is PATCHSENT ... case closed, more or less! :) Nice working with you! Cheers, Tom -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: linux-2.6 piuparts error
On Wed, Nov 18, 2009 at 11:27:04AM +0100, Sebastian Andrzej Siewior wrote: * maximilian attems | 2009-11-17 11:10:46 [+0100]: 0m54.3s ERROR: FAIL: Package purging left files on system: /etc/kernel-img.confnot owned oh so either it is a failure to generate such a file in postinst (as we shouldn't really need it!?), or one would want to remove it on purge, which opens another can of worms as this file is unowned in real boxes and usualy created by d-i. the best argument is that due to the convulated questions postinst wanted to ask you in the past we had never reached that point of generating this conffile in postinst. What is the long term goal? Do you plan do to get rid of kernel-img.conf and let the individual boot loader handle this kind of things? yes indeed the long term plan is to get rid of kernel-img.conf any eventual hooks there should be gone with lenny+1 what they should do is leave hooks in /etc/kernel dirs, grub has such a whishlist open, hope it gots resolved soon. You are changing the default behavior of palo here. Only in the case that no /etc/kernel-img.conf existed yet. haven't checked what the consequences of that particular change in the other maintainer scripts. However the values are written very late. link_in_boot for instance is only evalueted at the begin of the script. So it should not really matter for postinst at least. right The do_symlink thing is only required by people that don't have their setup right, isn't it? So grub refers to /vmlinuz but kernel itself is not in / but in /boot. So if those people would fix their boxes we could get rid of do_symlink for instance right? any sane bootloader shouldn't need that symlink mess indeed. afaik grub refers to the kernel directly in /boot, but it is lilo and many other bootloaders that prefers to have that symlinking. so it might indeed be worth also to have d-i updated on their generated kernel-img.conf thanks for your review! -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#539399: cifs crash with 2.6.30
On Wed, Nov 18, 2009 at 02:47:27AM +, Ben Hutchings wrote: Please report this upstream http://bugzilla.kernel.org and let us know the bug number. I have no account there. What You prevent from doing so Yourself? -- * Vladimir Stavrinov ** *** v...@inist.ru * * -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#539399: cifs crash with 2.6.30
On Wed, Nov 18, 2009 at 04:39:00PM +0300, Vladimir Stavrinov wrote: On Wed, Nov 18, 2009 at 02:47:27AM +, Ben Hutchings wrote: Please report this upstream http://bugzilla.kernel.org and let us know the bug number. I have no account there. What You prevent from doing so Yourself? easy. the bug reporter has the hardware/setup to test eventual fixes. so no middleman needed, please go ahead. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Custom Kernel Building in Debian
I would like to suggest addressing the building of out-of-tree modules as well. This is kind of a moving target, as Debian does not currently offer a way to build deb packages from out-of-tree modules which have been (prematurely, IMO) converted to DKMS. I'm afraid that's beyond my area of recent experience. The last time I built an out-of-tree module was back in the days when the ALSA drivers were not part of the kernel source tree, and I was using Woody, I think, with a 2.4 kernel. But make-pkpg could do that back then, and I would hope that it still can. I have no experience at all with DKMS. I do mention building out-of-tree modules in passing in my document, but I give no examples because I have none to offer in my recent experience. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#556963: [linux-image-2.6.30-2-686] psmouse.c: resync failed
Package: linux-image-2.6.30-2-686 Version: 2.6.30-8 Severity: minor I guess it's an old known bug that was in 2.18.. The mouse is often freezing cause of resync failed. dmesg [ 2068.880178] psmouse.c: bad data from KBC - timeout [ 2083.193008] psmouse.c: bad data from KBC - timeout [ 2084.192283] psmouse.c: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 3 bytes away. [ 2084.698546] psmouse.c: resync failed, issuing reconnect request [ 2115.938344] psmouse.c: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away. [ 2116.442499] psmouse.c: resync failed, issuing reconnect request [ 2182.018473] psmouse.c: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 3 bytes away. xorg.conf (i think it's not important) Section InputDevice Identifier Mouse0 Driver mouse Option CorePointer Option Device /dev/psaux Option Protocol PS/2 Option Emulate3Buttons true EndSection or Section InputDevice Identifier Mouse0 Driver mouse Option CorePointer Option Device /dev/imput/mice Option Protocol ImPS/2 Option Emulate3Buttons true EndSection --- System information. --- Architecture: i386 Kernel: Linux 2.6.30-2-686 Debian Release: 5.0.3 990 stable www.debian-multimedia.org 990 stable security.debian.org 990 stable ftp.uk.debian.org 990 stable dl.google.com 500 unstableftp.de.debian.org 500 testing ftp.fr.debian.org 500 proposed-updates ftp.fr.debian.org 500 oldstable ftp.fr.debian.org 500 lenny www.lamaresh.net 1 lenny-backports www.backports.org --- Package information. --- Depends (Version) | Installed =-+-= module-init-tools | 3.4-1 initramfs-tools(= 0.55) | 0.92o OR yaird(= 0.0.13) | 0.0.13-5 OR linux-initramfs-tool | Recommends (Version) | Installed =-+-=== libc6-i686| 2.10.1-7 Suggests (Version) | Installed ===-+-=== linux-doc-2.6.30| grub| 0.97-47lenny2 OR lilo| -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#556967: IPv6 is not compiled as module
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Package: linux-2.6 Version: 2.6.31-2 Severity: important Maybe the Severity is to low rated as that is a security bug! The IPv6 support is not compiled as module than fix in the kernel. So there is no way to switch IPv6 off. That might leeds in security violation as it might be overlooked so there might be no security setting on IPv6 at all and the machine open for all. So please drow away that protocol (put it as module as it was before) and let the admin decide to use it or not! - -- Package-specific info: ** Version: Linux version 2.6.31-1-686 (Debian 2.6.31-2) (b...@decadent.org.uk) (gcc version 4.3.4 (Debian 4.3.4-6) ) #1 SMP Sun Nov 15 20:39:33 UTC 2009 ** Command line: root=LABEL=root ro vga=0x318 ** Not tainted ** Kernel log: [5.978943] input: PC Speaker as /devices/platform/pcspkr/input/input4 [5.994955] ACPI: CPU1 (power states: C1[C1] C2[C2] C3[C3]) [6.006490] processor LNXCPU:01: registered as cooling_device1 [6.018120] ACPI: Processor [CPU1] (supports 8 throttling states) [6.104231] ACPI: Battery Slot [BAT0] (battery present) [6.122269] thinkpad_acpi: ThinkPad ACPI Extras v0.23 [6.133779] thinkpad_acpi: http://ibm-acpi.sf.net/ [6.144855] thinkpad_acpi: ThinkPad BIOS 7NETB3WW (2.13 ), EC 7MHT25WW-1.03 [6.155749] thinkpad_acpi: Lenovo ThinkPad X61s, model 7669A26 [6.181010] thinkpad_acpi: radio switch found; radios are disabled [6.183203] yenta_cardbus :05:00.0: CardBus bridge found [17aa:20c6] [6.203029] thinkpad_acpi: This ThinkPad has standard ACPI backlight brightness control, supported by the ACPI video driver [6.213862] thinkpad_acpi: Disabling thinkpad-acpi brightness events by default... [6.249016] Registered led device: tpacpi::thinklight [6.274330] Registered led device: tpacpi::power [6.286531] i801_smbus :00:1f.3: PCI INT A - GSI 23 (level, low) - IRQ 23 [6.297745] Registered led device: tpacpi::standby [6.308843] Registered led device: tpacpi::thinkvantage [6.309726] yenta_cardbus :05:00.0: ISA IRQ mask 0x0890, PCI irq 16 [6.309733] yenta_cardbus :05:00.0: Socket status: 3006 [6.309739] yenta_cardbus :05:00.0: pcmcia: parent PCI bridge I/O window: 0x4000 - 0x7fff [6.309744] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x4000-0x7fff: clean. [6.310940] yenta_cardbus :05:00.0: pcmcia: parent PCI bridge Memory window: 0xd400 - 0xd7ef [6.310944] yenta_cardbus :05:00.0: pcmcia: parent PCI bridge Memory window: 0xd800 - 0xdbff [6.387943] thinkpad_acpi: Standard ACPI backlight interface available, not loading native one. [6.392210] ath9k :03:00.0: PCI INT A - GSI 17 (level, low) - IRQ 17 [6.392227] ath9k :03:00.0: setting latency timer to 64 [6.411295] input: ThinkPad Extra Buttons as /devices/virtual/input/input5 [6.424846] Error: Driver 'pcspkr' is already registered, aborting... [6.522672] ath: EEPROM regdomain: 0x62 [6.522676] ath: EEPROM indicates we should expect a direct regpair map [6.522680] ath: Country alpha2 being used: 00 [6.522682] ath: Regpair used: 0x62 [6.582369] HDA Intel :00:1b.0: PCI INT B - GSI 17 (level, low) - IRQ 17 [6.593422] hda_intel: probe_mask set to 0x1 for device 17aa:20ac [6.604747] HDA Intel :00:1b.0: setting latency timer to 64 [6.606854] phy0: Selected rate control algorithm 'ath9k_rate_control' [6.607593] Registered led device: ath9k-phy0::radio [6.618999] Registered led device: ath9k-phy0::assoc [6.630471] Registered led device: ath9k-phy0::tx [6.641410] Registered led device: ath9k-phy0::rx [6.656823] phy0: Atheros AR5418 MAC/BB Rev:2 AR5133 RF Rev:81: mem=0xf8e2, irq=17 [6.794689] IBM TrackPoint firmware: 0x0e, buttons: 3/3 [6.833625] input: TPPS/2 IBM TrackPoint as /devices/platform/i8042/serio1/input/input6 [7.001058] Clocksource tsc unstable (delta = -258205080 ns) [7.087271] input: HDA Digital PCBeep as /devices/pci:00/:00:1b.0/input/input7 [7.725690] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver [7.773915] usbcore: registered new interface driver hiddev [7.784979] usbcore: registered new interface driver usbhid [7.795825] usbhid: v2.6:USB HID core driver [8.378983] padlock: VIA PadLock Hash Engine not detected. [8.741437] XFS mounting filesystem dm-1 [8.905379] Ending clean XFS mount for filesystem: dm-1 [8.996263] XFS mounting filesystem dm-2 [9.179948] Ending clean XFS mount for filesystem: dm-2 [9.231872] XFS mounting filesystem dm-0 [9.361342] Ending clean XFS mount for filesystem: dm-0 [9.425814] Adding 2096472k swap on /dev/mapper/swap0. Priority:2 extents:1 across:2096472k [9.966734] ip_tables: (C) 2000-2006 Netfilter Core Team [ 10.199371] nf_conntrack version 0.5.0 (15979 buckets, 63916 max) [ 10.210434] CONFIG_NF_CT_ACCT is deprecated and will
Bug#522922: test build available
Hi, I made test on HP DL160 G6 and works without problem. Please add support for this NIC in next official release of kernel package. Thanks Package: linux-2.6 Version: 2.6.26-20.bug522922.1 Severity: normal Linux version 2.6.26-2-amd64 (Debian 2.6.26-20.bug522922.1) (da...@debian.org) (gcc version 4.1.3 20080704 (prerelease) (Debian 4.1.2-25)) #1 SMP Sat Oct 24 15:58:33 UTC 2009 ** Model information sys_vendor: HP product_name: ProLiant DL160 G6 product_version: chassis_vendor: HP chassis_version: bios_vendor: HP bios_version: O33 ** Network status: *** IP interfaces and addresses: 1: lo: LOOPBACK,UP,LOWER_UP mtu 16436 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: BROADCAST,MULTICAST mtu 1500 qdisc noop state DOWN qlen 1000 link/ether 00:26:55:7b:6e:b0 brd ff:ff:ff:ff:ff:ff 3: eth1: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast state UP qlen 1000 link/ether 00:26:55:7b:6e:b1 brd ff:ff:ff:ff:ff:ff inet 192.168.16.58/24 brd 192.168.16.255 scope global eth1 inet6 fe80::226:55ff:fe7b:6eb1/64 scope link valid_lft forever preferred_lft forever ** PCI devices: 05:00.1 Ethernet controller [0200]: Intel Corporation Device [8086:10c9] (rev 01) Subsystem: Hewlett-Packard Company Device [103c:323f] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx+ Latency: 0, Cache Line Size: 64 bytes Interrupt: pin B routed to IRQ 42 Region 0: Memory at fbee (32-bit, non-prefetchable) [size=128K] Region 1: Memory at fbec (32-bit, non-prefetchable) [size=128K] Region 2: I/O ports at ec00 [size=32] Region 3: Memory at fbebc000 (32-bit, non-prefetchable) [size=16K] Expansion ROM at fbe8 [disabled] [size=128K] Capabilities: access denied Kernel driver in use: igb Kernel modules: igb -- System Information: Debian Release: 5.0.3 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-2-amd64 (SMP w/16 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- Artur Kaszuba, System Administrator Poznan Supercomputing Networking Center Supercomputing Department -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#539399: cifs crash with 2.6.30
On Wed, Nov 18, 2009 at 04:39:00PM +0300, Vladimir Stavrinov wrote: On Wed, Nov 18, 2009 at 02:47:27AM +, Ben Hutchings wrote: Please report this upstream http://bugzilla.kernel.org and let us know the bug number. I have no account there. What You prevent from doing so Yourself? Upstream developers will probably need to ask you questions, so you need to be the reporter or a subscriber to the bug. It is not possible for us to subscribe you to a bug in Bugzilla unless you have an account there. Similarly we cannot reasonably create an account for each Debian bug in order to subscribe it. I know this sucks, but we cannot fix it as long as upstream uses Bugzilla. When we have an upstream bug number we can mark the Debian bug report as forwarded and the bts-link program will notify us of upstream status changes. Ben. -- Ben Hutchings Never attribute to conspiracy what can adequately be explained by stupidity. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#556967: marked as done (IPv6 is not compiled as module)
Your message dated Wed, 18 Nov 2009 20:26:34 + with message-id 20091118202634.gf8...@decadent.org.uk and subject line Re: Bug#556967: IPv6 is not compiled as module has caused the Debian Bug report #556967, regarding IPv6 is not compiled as module 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.) -- 556967: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=556967 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Package: linux-2.6 Version: 2.6.31-2 Severity: important Maybe the Severity is to low rated as that is a security bug! The IPv6 support is not compiled as module than fix in the kernel. So there is no way to switch IPv6 off. That might leeds in security violation as it might be overlooked so there might be no security setting on IPv6 at all and the machine open for all. So please drow away that protocol (put it as module as it was before) and let the admin decide to use it or not! - -- Package-specific info: ** Version: Linux version 2.6.31-1-686 (Debian 2.6.31-2) (b...@decadent.org.uk) (gcc version 4.3.4 (Debian 4.3.4-6) ) #1 SMP Sun Nov 15 20:39:33 UTC 2009 ** Command line: root=LABEL=root ro vga=0x318 ** Not tainted ** Kernel log: [5.978943] input: PC Speaker as /devices/platform/pcspkr/input/input4 [5.994955] ACPI: CPU1 (power states: C1[C1] C2[C2] C3[C3]) [6.006490] processor LNXCPU:01: registered as cooling_device1 [6.018120] ACPI: Processor [CPU1] (supports 8 throttling states) [6.104231] ACPI: Battery Slot [BAT0] (battery present) [6.122269] thinkpad_acpi: ThinkPad ACPI Extras v0.23 [6.133779] thinkpad_acpi: http://ibm-acpi.sf.net/ [6.144855] thinkpad_acpi: ThinkPad BIOS 7NETB3WW (2.13 ), EC 7MHT25WW-1.03 [6.155749] thinkpad_acpi: Lenovo ThinkPad X61s, model 7669A26 [6.181010] thinkpad_acpi: radio switch found; radios are disabled [6.183203] yenta_cardbus :05:00.0: CardBus bridge found [17aa:20c6] [6.203029] thinkpad_acpi: This ThinkPad has standard ACPI backlight brightness control, supported by the ACPI video driver [6.213862] thinkpad_acpi: Disabling thinkpad-acpi brightness events by default... [6.249016] Registered led device: tpacpi::thinklight [6.274330] Registered led device: tpacpi::power [6.286531] i801_smbus :00:1f.3: PCI INT A - GSI 23 (level, low) - IRQ 23 [6.297745] Registered led device: tpacpi::standby [6.308843] Registered led device: tpacpi::thinkvantage [6.309726] yenta_cardbus :05:00.0: ISA IRQ mask 0x0890, PCI irq 16 [6.309733] yenta_cardbus :05:00.0: Socket status: 3006 [6.309739] yenta_cardbus :05:00.0: pcmcia: parent PCI bridge I/O window: 0x4000 - 0x7fff [6.309744] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x4000-0x7fff: clean. [6.310940] yenta_cardbus :05:00.0: pcmcia: parent PCI bridge Memory window: 0xd400 - 0xd7ef [6.310944] yenta_cardbus :05:00.0: pcmcia: parent PCI bridge Memory window: 0xd800 - 0xdbff [6.387943] thinkpad_acpi: Standard ACPI backlight interface available, not loading native one. [6.392210] ath9k :03:00.0: PCI INT A - GSI 17 (level, low) - IRQ 17 [6.392227] ath9k :03:00.0: setting latency timer to 64 [6.411295] input: ThinkPad Extra Buttons as /devices/virtual/input/input5 [6.424846] Error: Driver 'pcspkr' is already registered, aborting... [6.522672] ath: EEPROM regdomain: 0x62 [6.522676] ath: EEPROM indicates we should expect a direct regpair map [6.522680] ath: Country alpha2 being used: 00 [6.522682] ath: Regpair used: 0x62 [6.582369] HDA Intel :00:1b.0: PCI INT B - GSI 17 (level, low) - IRQ 17 [6.593422] hda_intel: probe_mask set to 0x1 for device 17aa:20ac [6.604747] HDA Intel :00:1b.0: setting latency timer to 64 [6.606854] phy0: Selected rate control algorithm 'ath9k_rate_control' [6.607593] Registered led device: ath9k-phy0::radio [6.618999] Registered led device: ath9k-phy0::assoc [6.630471] Registered led device: ath9k-phy0::tx [6.641410] Registered led device: ath9k-phy0::rx [6.656823] phy0: Atheros AR5418 MAC/BB Rev:2 AR5133 RF Rev:81: mem=0xf8e2, irq=17 [6.794689] IBM TrackPoint firmware: 0x0e, buttons: 3/3 [6.833625] input: TPPS/2 IBM TrackPoint as /devices/platform/i8042/serio1/input/input6 [7.001058] Clocksource tsc unstable (delta = -258205080 ns) [7.087271] input: HDA Digital PCBeep as /devices/pci:00/:00:1b.0/input/input7 [7.725690] ohci_hcd: USB 1.1 'Open' Host Controller
Processed: tagging 544905
Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35lenny7 tags 544905 + pending Bug #544905 [linux-2.6] libsigsegv: FTBFS on amd64: Test failure Added tag(s) pending. End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#555835: linux-image-2.6.30-2-686: Unusual usb storage Samsung YP-CP3 not working
[CCing upstream for review/merge of the patch proposed by Vitaly.] This was reported to Debian as http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=555835 Vitaly, please add a Signed-off-by: header as described in Documentation/SubmittingPatches Cheers, Moritz On Thu, Nov 12, 2009 at 02:17:09AM +0300, Vitaly Kuznetsov wrote: Package: linux-image-2.6.30-2-686 Version: 2.6.30-8 Severity: normal Tags: patch Unusual usb storage Samsung YP-CP3 (mp4 player) not working (disconnects immediately after connection), dmesg: [ 1457.432058] usb 2-6: new high speed USB device using ehci_hcd and address 2 [ 1457.564921] usb 2-6: New USB device found, idVendor=04e8, idProduct=5122 [ 1457.564925] usb 2-6: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 1457.564928] usb 2-6: Product: YP-CP3 [ 1457.564931] usb 2-6: Manufacturer: SAMSUNG [ 1457.564933] usb 2-6: SerialNumber: USBV1.00 [ 1457.565058] usb 2-6: configuration #1 chosen from 1 choice [ 1457.648326] Initializing USB Mass Storage driver... [ 1457.648725] scsi3 : SCSI emulation for USB Mass Storage devices [ 1457.648857] usb-storage: device found at 2 [ 1457.648859] usb-storage: waiting for device to settle before scanning [ 1457.648866] usbcore: registered new interface driver usb-storage [ 1457.648870] USB Mass Storage support registered. [ 1462.644223] usb-storage: device scan complete [ 1462.644699] scsi 3:0:0:0: Direct-Access SAMSUNG YP-CP3 1.00 PQ: 0 ANSI: 0 [ 1462.645313] scsi 3:0:0:1: Direct-Access SAMSUNG microSD Card 1.00 PQ: 0 ANSI: 0 CCS [ 1462.649922] sd 3:0:0:0: [sdb] 7649280 512-byte hardware sectors: (3.91 GB/3.64 GiB) [ 1462.761061] usb 2-6: reset high speed USB device using ehci_hcd and address 2 [ 1463.009063] usb 2-6: reset high speed USB device using ehci_hcd and address 2 [ 1463.256053] usb 2-6: reset high speed USB device using ehci_hcd and address 2 [ 1463.505060] usb 2-6: reset high speed USB device using ehci_hcd and address 2 [ 1463.756066] usb 2-6: reset high speed USB device using ehci_hcd and address 2 [ 1464.008104] usb 2-6: reset high speed USB device using ehci_hcd and address 2 [ 1464.140585] sd 3:0:0:0: [sdb] Write Protect is off [ 1464.140590] sd 3:0:0:0: [sdb] Mode Sense: 00 00 00 00 [ 1464.140592] sd 3:0:0:0: [sdb] Assuming drive cache: write through [ 1464.141322] sd 3:0:0:1: [sdc] Attached SCSI removable disk [ 1464.257057] usb 2-6: reset high speed USB device using ehci_hcd and address 2 [ 1464.512064] usb 2-6: reset high speed USB device using ehci_hcd and address 2 [ 1464.760074] usb 2-6: reset high speed USB device using ehci_hcd and address 2 [ 1464.816364] usb 2-6: USB disconnect, address 2 [ 1464.817340] sd 3:0:0:0: [sdb] Assuming drive cache: write through [ 1464.817352] sdb:2ldm_validate_partition_table(): Disk read failed. [ 1464.818575] Dev sdb: unable to read RDB block 0 [ 1464.818618] unable to read partition table I wrote a small patch to fix this problem: --- drivers/usb/storage/unusual_devs.h.old 2009-09-26 01:58:45.0 +0400 +++ drivers/usb/storage/unusual_devs.h 2009-11-12 02:01:20.0 +0300 @@ -495,6 +495,13 @@ US_SC_DEVICE, US_PR_DEVICE, NULL, US_FL_MAX_SECTORS_64), +/* Reported by Vitaly Kuznetsov vi...@altlinux.ru */ +UNUSUAL_DEV( 0x04e8, 0x5122, 0x, 0x, + Samsung, + YP-CP3, + US_SC_DEVICE, US_PR_DEVICE, NULL, + US_FL_MAX_SECTORS_64 | US_FL_FIX_INQUIRY | US_FL_FIX_CAPACITY | US_FL_BULK_IGNORE_TAG), + /* Entry and supporting patch by Theodore Kilgore kilg...@auburn.edu. * Device uses standards-violating 32-byte Bulk Command Block Wrappers and * reports itself as Proprietary SCSI Bulk. Cf. device entry 0x084d:0x0011. Now this device works perfect, dmesg: [ 6126.086942] usb-storage: device found at 19 [ 6126.086947] usb-storage: waiting for device to settle before scanning [ 6131.084350] usb-storage: device scan complete [ 6131.084553] scsi 20:0:0:0: Direct-Access Samsung YP-CP3 PQ: 0 ANSI: 2 [ 6131.084680] scsi 20:0:0:1: Direct-Access Samsung YP-CP3 PQ: 0 ANSI: 2 [ 6131.088943] sd 20:0:0:1: [sdc] Attached SCSI removable disk [ 6131.097925] sd 20:0:0:0: [sdb] Adjusting the sector count from its reported value: 7649280 [ 6131.097940] sd 20:0:0:0: [sdb] 7649279 512-byte hardware sectors: (3.91 GB/3.64 GiB) [ 6131.099241] sd 20:0:0:0: [sdb] Write Protect is off [ 6131.099250] sd 20:0:0:0: [sdb] Mode Sense: 03 00 00 00 [ 6131.099256] sd 20:0:0:0: [sdb] Assuming drive cache: write through [ 6131.100855] sd 20:0:0:0: [sdb] Adjusting the sector count from its reported value: 7649280 [ 6131.101355] sd 20:0:0:0: [sdb] Assuming drive cache: write through [ 6131.101367] sdb: [ 6131.102452] sd 20:0:0:0: [sdb] Attached SCSI removable disk -- To UNSUBSCRIBE, email to
Bug#547902: dash only reads the first character from pipe (bash reads whole line)
On Tue, Oct 13, 2009 at 11:13:01AM +, Gerrit Pape wrote:
tags 547902 + patch
quit
[ Adding Christian to CC: ]
Christian, did you submit your patch upstream?
Cheers,
Moritz
Hi, please see http://bugs.debian.org/547902
Here's a patch from Christian Hohnstaedt chohnsta...@innominate.com
Thanks, Gerrit.
---
Testparameter:
for i in 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19; do dd
if=/proc/sys/net/ipv4/tcp_wmem bs=$i 2/dev/null; done
for i in 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19; do dd
if=/proc/sys/net/ipv4/tcp_wmem skip=$i bs=1 2/dev/null |wc -c ; done
diff --git a/kernel/sysctl.c b/kernel/sysctl.c
index 9270125..038df14 100644
--- a/kernel/sysctl.c
+++ b/kernel/sysctl.c
@@ -2117,17 +2117,16 @@ static int __do_proc_dointvec(void *tbl_data, struct
ctl_table *table,
#define TMPBUFLEN 21
int *i, vleft, first=1, neg, val;
unsigned long lval;
- size_t left, len;
+ size_t left, len, off;
char buf[TMPBUFLEN], *p;
char __user *s = buffer;
- if (!tbl_data || !table-maxlen || !*lenp ||
- (*ppos !write)) {
+ if (!tbl_data || !table-maxlen || !*lenp) {
*lenp = 0;
return 0;
}
-
+ off = 0;
i = (int *) tbl_data;
vleft = table-maxlen / sizeof(*i);
left = *lenp;
@@ -2176,25 +2175,31 @@ static int __do_proc_dointvec(void *tbl_data, struct
ctl_table *table,
if (conv(neg, lval, i, 1, data))
break;
} else {
+ loff_t diff;
p = buf;
- if (!first)
- *p++ = '\t';
-
if (conv(neg, lval, i, 0, data))
break;
- sprintf(p, %s%lu, neg ? - : , lval);
- len = strlen(buf);
- if (len left)
- len = left;
- if(copy_to_user(s, buf, len))
- return -EFAULT;
- left -= len;
- s += len;
+ len = sprintf(p, %s%s%lu, first ? : \t,
+ neg ? - : , lval);
+ diff = *ppos - off;
+ off += len;
+ if (diff 0 diff len) {
+ p += diff;
+ len -= diff;
+ }
+ if (off *ppos) {
+ if (len left)
+ len = left;
+ if(copy_to_user(s, p, len))
+ return -EFAULT;
+ left -= len;
+ s += len;
+ }
}
}
- if (!write !first left) {
+ if (!write !first left off = *ppos) {
if(put_user('\n', s))
return -EFAULT;
left--, s++;
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Success with linux-image-2.6.31-1-xen-amd64_2.6.31-2_amd64.deb
Hello! I finally got back to spending a few hours on working on xenifying this pre-hardware-virtualization AMD64 machine. I re-installed the system. Basing it on stable (Lenny) this time. The ol' combo of xen-hypervisor-3.2-1-amd64 / linux-image-2.6.26-2-xen-amd64 boots fine. Likewise when switching to xen-hypervisor-3.4-amd64. And then the goal, http://hermes.jura.uni-tuebingen.de/~blank/debian/xen-test/linux-image-2.6.31-1-xen-amd64_2.6.31-2_amd64.deb -- which finally, after rising dom0_mem=15 (was 10 before) the system actually boots instead of crashing / rebooting during the handover from initial Xen to Linux (I suppose). Please tell if you're interested in any logs etc. What I didn't try yet is creating domUs. But I'm now confident that this will work as well. :-) The plan is then to gradually update the system to Debian testing and see whether the booting / lvm / initramfs problems come back. Regards, Thomas signature.asc Description: Digital signature
Bug#557033: linux-image-2.6.31-1-amd64: Kernel logs WARNING at hpet.c:390.
Subject: linux-image-2.6.31-1-amd64: Kernel logs WARNING at hpet.c:390. Package: linux-2.6 Version: 2.6.31-1 Severity: normal *** Please type your report below this line *** syslog reports WARNING at hpet.c:390. The system appears to run normally, except for a single message from GNOME: Your system had a kernel failure. However, hpet.c:390 is an invocation of macro WARN_ON_ONCE, so I wonder if the system might be taking a performance hit if the fault is actually occurring many times (see below for more information on this). The computer is a new Intel core i7-860, Chipset P55, Gigabyte P55UD3p, nVidia Geforce 9600GT. Two Seagate 1TB disks in mirrored RAID configuration. The fault initially occurred in the stable lenny distribution with kernel 2.6.26. I installed linux-image-2.6.31-1-amd64 from sid to see if it would go away. It didn't. A similar fault in linux-image-2.6.26-1-686 was reported in bug report 512617 in January 2009, and closed in July 2009. History of my installation: Initially I installed the 32-bit version of lenny: debian-502-i386-DVD-n.iso. When I booted the system, it wrote WARNING messages from hpet.c at the rate of megabytes per minute. I then installed the 64-bit version of lenny: debian-503-amd64-DVD-n.iso. hpet.c:390 from linux-image-2.6.31-1-amd64 invokes WARN_ON_ONCE, but my previous experience with the 32-bit distribution makes me believe that the fault is in fact occurring many times per second, and hence I wonder if there might be a performance hit. -- Package-specific info: ** Version: Linux version 2.6.31-1-amd64 (Debian 2.6.31-1) (wa...@debian.org) (gcc version 4.3.4 (Debian 4.3.4-5) ) #1 SMP Sat Oct 24 17:50:31 UTC 2009 ** Command line: root=/dev/mapper/isw_ifdfaidbh_Volume05 ro quiet ** Tainted: W (512) * Taint on warning. ** Kernel log: [5.049081] sdb14 sdb15 [5.072861] sd 5:0:0:0: [sdb] Attached SCSI disk [5.081135] sd 4:0:0:0: Attached scsi generic sg0 type 0 [5.081153] sd 5:0:0:0: Attached scsi generic sg1 type 0 [5.081172] sr 7:0:0:0: Attached scsi generic sg2 type 5 [5.236070] device-mapper: uevent: version 1.0.3 [5.236630] device-mapper: ioctl: 4.15.0-ioctl (2009-04-01) initialised: dm-de...@redhat.com [5.926876] PM: Starting manual resume from disk [5.950589] kjournald starting. Commit interval 5 seconds [5.950594] EXT3-fs: mounted filesystem with ordered data mode. [6.702415] udevd version 125 started [6.978535] Monitor-Mwait will be used to enter C-1 state [6.978593] Monitor-Mwait will be used to enter C-2 state [6.998699] Monitor-Mwait will be used to enter C-3 state [6.998762] ACPI: CPU0 (power states: C1[C1] C2[C2] C3[C3]) [6.998794] processor LNXCPU:00: registered as cooling_device0 [6.998799] ACPI: Processor [CPU0] (supports 8 throttling states) [6.998857] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input3 [6.998863] ACPI: Power Button [PWRF] [6.999463] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input4 [6.999468] ACPI: Power Button [PWRB] [7.002603] ACPI: CPU1 (power states: C1[C1] C2[C2] C3[C3]) [7.002624] processor LNXCPU:01: registered as cooling_device1 [7.002629] ACPI: Processor [CPU1] (supports 8 throttling states) [7.027097] ACPI: CPU2 (power states: C1[C1] C2[C2] C3[C3]) [7.027123] processor LNXCPU:02: registered as cooling_device2 [7.027128] ACPI: Processor [CPU2] (supports 8 throttling states) [7.035724] ACPI: CPU3 (power states: C1[C1] C2[C2] C3[C3]) [7.035742] processor LNXCPU:03: registered as cooling_device3 [7.035744] ACPI: Processor [CPU3] (supports 8 throttling states) [7.036353] ACPI: CPU4 (power states: C1[C1] C2[C2] C3[C3]) [7.036375] processor LNXCPU:04: registered as cooling_device4 [7.036380] ACPI: Processor [CPU4] (supports 8 throttling states) [7.037120] ACPI: CPU5 (power states: C1[C1] C2[C2] C3[C3]) [7.037141] processor LNXCPU:05: registered as cooling_device5 [7.037145] ACPI: Processor [CPU5] (supports 8 throttling states) [7.037775] [ cut here ] [7.037782] WARNING: at /home/blank/debian/kernel/release/linux-2.6/linux-2.6-2.6.31/debian/build/source_amd64_none/arch/x86/kernel/hpet.c:390 hpet_next_event+0x52/0x77() [7.037785] Modules linked in: button processor(+) ext3 jbd mbcache dm_mirror dm_region_hash dm_log dm_mod sg sd_mod crc_t10dif sr_mod cdrom ide_pci_generic ide_core ata_generic usbhid hid ahci pata_jmicron 8139too r8169 mii libata ehci_hcd scsi_mod uhci_hcd thermal fan thermal_sys [last unloaded: scsi_wait_scan] [7.037807] Pid: 0, comm: swapper Not tainted 2.6.31-1-amd64 #1 [7.037809] Call Trace: [7.037814] [81032983] ? hpet_next_event+0x52/0x77 [7.037818] [8105b3d8] ? warn_slowpath_common+0x85/0xc8 [7.037822] [81032983] ? hpet_next_event+0x52/0x77 [7.037826] [8108441a] ? tick_dev_program_event+0x41/0xc2 [
Re: Custom Kernel Building in Debian
Stephen Powell zlinux...@wowway.com writes: I would like to suggest addressing the building of out-of-tree modules as well. This is kind of a moving target, as Debian does not currently offer a way to build deb packages from out-of-tree modules which have been (prematurely, IMO) converted to DKMS. I'm afraid that's beyond my area of recent experience. The last time I built an out-of-tree module was back in the days when the ALSA drivers were not part of the kernel source tree, and I was using Woody, I think, with a 2.4 kernel. But make-pkpg could do that back then, and I would hope that it still can. I have no experience at all with DKMS. I do mention building out-of-tree modules in passing in my document, but I give no examples because I have none to offer in my recent experience. FYI it can't. The DKMS using modules (vmware specifically) don't build with make-kpkg or module-assistant. That is actualy the reason for the mail. MfG Goswin -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
