linux-kbuild-3.15 but it is not installable
Hi there, this is the first time since years that you do not provide linux-kbuild packages along with trunk header packages. Is this wanted? I would appreciate if matching linux-kbuild-3.15 package would be added to resources soon. Thanks in advance. Kindest regards, Norbert -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/53b6505a.40...@oracle.com
Re: Bug#753656: linux-image-3.14-1-rt-amd64: Kernel panic caused by ohci_hcd
Control: reassign -1 src:linux On Jo, 03 iul 14, 18:35:01, The GZeus wrote: > Source: linux-image-3.14-1-rt-amd64 > Severity: important > > Dear Maintainer, > > > Twice I have had a kernel panic with nearly identical messages while playing > a game (Dust: An Elysian Tail, obtained via native Linux Steam, which I > installed from non-free) with an official MS XBox 360 wired controller with > the standard xpad driver. > > I took a photo of the most recent one, and I'm willing to type out whatever > lines contain the necessary information. > Would you like the output of lspci/lsusb? > > Odd that I've never had this happen in any other situation, but that's what > happened. > > My system uses an AMD A10 APU. > > *** Reporter, please consider answering these questions, where appropriate *** > >* What led up to the situation? >* What exactly did you do (or not do) that was effective (or > ineffective)? >* What was the outcome of this action? >* What outcome did you expect instead? > > *** End of the template - remove these template lines *** > > > -- System Information: > Debian Release: jessie/sid > APT prefers testing > APT policy: (900, 'testing') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores) > Locale: LANG=en_GB.UTF-8, LC_CTYPE=ja_JP.utf8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash -- http://wiki.debian.org/FAQsFromDebianUser Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic http://nuvreauspam.ro/gpg-transition.txt signature.asc Description: Digital signature
Processed: Re: Bug#753656: linux-image-3.14-1-rt-amd64: Kernel panic caused by ohci_hcd
Processing control commands: > reassign -1 src:linux Bug #753656 [src:linux-image-3.14-1-rt-amd64] linux-image-3.14-1-rt-amd64: Kernel panic caused by ohci_hcd Warning: Unknown package 'src:linux-image-3.14-1-rt-amd64' Bug reassigned from package 'src:linux-image-3.14-1-rt-amd64' to 'src:linux'. Ignoring request to alter found versions of bug #753656 to the same values previously set Ignoring request to alter fixed versions of bug #753656 to the same values previously set -- 753656: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753656 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: https://lists.debian.org/handler.s.b753656.140446191531114.transcr...@bugs.debian.org
Re: linux-kbuild-3.15 but it is not installable
Hello, On Fri, Jul 04, 2014 at 08:57:30AM +0200, norbert.br...@oracle.com wrote: > > > this is the first time since years that you do not provide linux-kbuild > packages along with trunk header packages. In experimental it isn't, just browse old bug reports. > Is this wanted? Yes, we don't care about OOT modules like yours, just use 3.14 if you need such. > I would appreciate if matching linux-kbuild-3.15 package would be > added to resources soon. We will switch to 3.16-rcX in experimental very soon. Best, -- maks -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140704081858.GA23707@gluino
Bug#743267: Experimental kernel 3.15-trunk seems to fix the issue
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I just tried booting the notebook twice with the experimental build 3.15-trunk-686-pae and it seems to work now, but I had this impression already earlier, so I am not closing this at once, just in case problems reappear. -BEGIN PGP SIGNATURE- Version: GnuPG v2 iEYEARECAAYFAlO2pOEACgkQ5+rBHyUt5wtIJwCfXtZbfqa0zKuTZcptfyHdWB3b 3RkAnjFcIMWsB8unxZDdPJ1dTrdzCv/u =nssd -END PGP SIGNATURE-
Bug#690009: "Invalid iomem size. You may experience problems." I do, experience problems.
I also see this message on a Dell Precision M 6700. The message is: sdhci-pci :0c:00.1: Invalid iomem size. You may experience problems. uname -a says: Linux 3.2.0-4-amd64 #1 SMP Debian 3.2.57-3+deb7u2 x86_64 GNU/Linux I don't know if this is related, but I had problems plugging an USB2 Wifi dongle into an USB3 port of the above laptop. Didn't work, output was: xhci_hcd 000:00:14.0: ERROR no room on ep ring (multiple times repeated) The dongle works fine in an USB2 port (no error messages). regards -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/81bf81bf-eb7f-4192-85b8-2bcc573ad...@mailbox.org
Bug#753732: NFS sec=krb5 does not work with cross-realm
Package: nfs-common Version: 1.2.6-4 NFS with sec=krb5i or sec=krb5p using MIT Kerberos does not work when cross-realm authentication is used -- only when clients have an Kerberos ticket for the same realm. This happens consistently and in cases when cross-realm authentication does work with other services on the same machine, such as SSH. To illustrate, I've included two sets of NFS debug output from both a client (daboia.dapadam.nl) and a server (cerastes.dapadam.nl): one set with a successful authentication and the other with a failure. The first set involves a user, jwinius, with an MIT Kerberos ticket from the same realm, DAPADAM.NL, that results in a successful authentication: === Begin === Success, client log output = Jul 1 16:08:37 daboia rpc.gssd[1422]: handling gssd upcall (/var/lib/nfs/rpc_pipefs/nfs/clnt0) Jul 1 16:08:37 daboia rpc.gssd[1422]: handle_gssd_upcall: 'mech=krb5 uid=1 enctypes=18,17,16,23,3,1,2 ' Jul 1 16:08:37 daboia rpc.gssd[1422]: handling krb5 upcall (/var/lib/nfs/rpc_pipefs/nfs/clnt0) Jul 1 16:08:37 daboia rpc.gssd[1422]: process_krb5_upcall: service is '' Jul 1 16:08:37 daboia rpc.gssd[1422]: getting credentials for client with uid 1 for server cerastes.dapadam.nl Jul 1 16:08:37 daboia rpc.gssd[1422]: CC file '/tmp/krb5cc_0_8TcUINGCct' being considered, with preferred realm 'DAPADAM.NL' Jul 1 16:08:37 daboia rpc.gssd[1422]: CC file '/tmp/krb5cc_0_8TcUINGCct' owned by 0, not 1 Jul 1 16:08:37 daboia rpc.gssd[1422]: CC file '/tmp/krb5cc_machine_DAPADAM.NL' being considered, with preferred realm 'DAPADAM.NL' Jul 1 16:08:37 daboia rpc.gssd[1422]: CC file '/tmp/krb5cc_machine_DAPADAM.NL' owned by 0, not 1 Jul 1 16:08:37 daboia rpc.gssd[1422]: CC file '/tmp/krb5cc_1_HFd9c1oOJy' being considered, with preferred realm 'DAPADAM.NL' Jul 1 16:08:37 daboia rpc.gssd[1422]: CC file '/tmp/krb5cc_1_HFd9c1oOJy'(jwin...@dapadam.nl) passed all checks and has mtime of 1404223701 Jul 1 16:08:37 daboia rpc.gssd[1422]: CC file '/tmp/krb5cc_0' being considered, with preferred realm 'DAPADAM.NL' Jul 1 16:08:37 daboia rpc.gssd[1422]: CC file '/tmp/krb5cc_0' owned by 0, not 1 Jul 1 16:08:37 daboia rpc.gssd[1422]: using FILE:/tmp/krb5cc_1_HFd9c1oOJy as credentials cache for client with uid 1 for server cerastes.dapadam.nl Jul 1 16:08:37 daboia rpc.gssd[1422]: using environment variable to select krb5 ccache FILE:/tmp/krb5cc_1_HFd9c1oOJy Jul 1 16:08:37 daboia rpc.gssd[1422]: creating context using fsuid 1 (save_uid 0) Jul 1 16:08:37 daboia rpc.gssd[1422]: creating tcp client for server cerastes.dapadam.nl Jul 1 16:08:37 daboia rpc.gssd[1422]: DEBUG: port already set to 2049 Jul 1 16:08:37 daboia rpc.gssd[1422]: creating context with server n...@cerastes.dapadam.nl Jul 1 16:08:37 daboia rpc.gssd[1422]: DEBUG: serialize_krb5_ctx: lucid version! Jul 1 16:08:37 daboia rpc.gssd[1422]: prepare_krb5_rfc4121_buffer: protocol 1 Jul 1 16:08:37 daboia rpc.gssd[1422]: prepare_krb5_rfc4121_buffer: serializing key with enctype 18 and size 32 Jul 1 16:08:37 daboia rpc.gssd[1422]: doing downcall Jul 1 16:08:37 daboia rpc.idmapd[1417]: nfs4_name_to_uid: calling nsswitch->name_to_uid Jul 1 16:08:37 daboia rpc.idmapd[1417]: nss_getpwnam: name 'jwin...@dapadam.nl' domain 'dapadam.nl': resulting localname 'jwinius' Jul 1 16:08:37 daboia rpc.idmapd[1417]: nfs4_name_to_uid: nsswitch->name_to_uid returned 0 Jul 1 16:08:37 daboia rpc.idmapd[1417]: nfs4_name_to_uid: final return value is 0 Jul 1 16:08:37 daboia rpc.idmapd[1417]: Client 0: (user) name "jwin...@dapadam.nl" -> id "1" Jul 1 16:08:37 daboia rpc.idmapd[1417]: nfs4_name_to_gid: calling nsswitch->name_to_gid Jul 1 16:08:37 daboia rpc.idmapd[1417]: nfs4_name_to_gid: nsswitch->name_to_gid returned 0 Jul 1 16:08:37 daboia rpc.idmapd[1417]: nfs4_name_to_gid: final return value is 0 Jul 1 16:08:37 daboia rpc.idmapd[1417]: Client 0: (group) name "jwin...@dapadam.nl" -> id "1" Jul 1 16:08:37 daboia rpc.gssd[1422]: dir_notify_handler: sig 37 si 0x7fff3cdee670 data 0x7fff3cdee540 Jul 1 16:08:37 daboia rpc.idmapd[1417]: New client: 2 Jul 1 16:17:01 daboia /USR/SBIN/CRON[2399]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) === End = Success, client log output = === Begin === Success, server log output = Jul 1 16:08:37 cerastes rpc.svcgssd[3295]: leaving poll Jul 1 16:08:37 cerastes rpc.svcgssd[3295]: handling null request Jul 1 16:08:37 cerastes rpc.svcgssd[3295]: svcgssd_limit_krb5_enctypes: Calling gss_set_allowable_enctypes with 7 enctypes from the kernel Jul 1 16:08:37 cerastes rpc.svcgssd[3295]: sname = jwin...@dapadam.nl Jul 1 16:08:37 cerastes rpc.svcgssd[3295]: DEBUG: serialize_krb5_ctx: lucid version! Jul 1 16:08:37 cerastes rpc.svcgssd[3295]: prepare_krb5_rfc4121_buffer: protocol 1 Jul 1 16:08:37 cerastes rpc.
Bug#753656: linux-image-3.14-1-rt-amd64: Kernel panic caused by ohci_hcd
UPSTREAM BUG. Been in the kernel for quite some time, too. -_- Used this info to find that out. BUG: unable to handle kernel NULL pointer dereference at 0008 (I could have the number of 0s wrong. Reading this from a photo on my phone) IP:[] finish_urb+0xb2/0x150 [ohci_hcd] I hope that's enough. I'm willing to type the rest out if need be, but there are already bug reports regarding this floating around out there, it's been reported to the kernel ml, and yikes, that's alot of hex! Hope this helps, A. Winkler -- TheGZeus: Proof of Ferocious Will -- On 3 July 2014 19:19, Z Winkler wrote: > CORRECTION. > Thought I was running the rt image, but that's another machine > (obviously). All else is correct. > > -- TheGZeus: Proof of Ferocious Will -- > > > On 3 July 2014 18:35, The GZeus wrote: > >> Source: linux-image-3.14-1-rt-amd64 >> Severity: important >> >> Dear Maintainer, >> >> >> Twice I have had a kernel panic with nearly identical messages while >> playing a game (Dust: An Elysian Tail, obtained via native Linux Steam, >> which I installed from non-free) with an official MS XBox 360 wired >> controller with the standard xpad driver. >> >> I took a photo of the most recent one, and I'm willing to type out >> whatever lines contain the necessary information. >> Would you like the output of lspci/lsusb? >> >> Odd that I've never had this happen in any other situation, but that's >> what happened. >> >> My system uses an AMD A10 APU. >> >> *** Reporter, please consider answering these questions, where >> appropriate *** >> >>* What led up to the situation? >>* What exactly did you do (or not do) that was effective (or >> ineffective)? >>* What was the outcome of this action? >>* What outcome did you expect instead? >> >> *** End of the template - remove these template lines *** >> >> >> -- System Information: >> Debian Release: jessie/sid >> APT prefers testing >> APT policy: (900, 'testing') >> Architecture: amd64 (x86_64) >> Foreign Architectures: i386 >> >> Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores) >> Locale: LANG=en_GB.UTF-8, LC_CTYPE=ja_JP.utf8 (charmap=UTF-8) >> Shell: /bin/sh linked to /bin/dash >> > >
Bug#748615: the system reboot after mounting the partitions
Hi, The module that crashes the linux kernel 3.13 and later on my system is radeon. I says that because blacklisted radeon works fine but, sure, then video has poor quality. The mothercard is MSI A78M-E35 with AMD A4-5300 (CPU+GPU). lspci 00:00.0 Host bridge: Advanced Micro Devices [AMD] Family 15h (Models 10h-1fh) Processor Root Complex 00:00.2 IOMMU: Advanced Micro Devices [AMD] Family 15h (Models 10h-1fh) I/O Memory Management Unit 00:01.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI Device 9993 00:01.1 Audio device: Advanced Micro Devices [AMD] nee ATI Trinity HDMI Audio Controller 00:04.0 PCI bridge: Advanced Micro Devices [AMD] Family 15h (Models 10h-1fh) Processor Root Port 00:05.0 PCI bridge: Advanced Micro Devices [AMD] Family 15h (Models 10h-1fh) Processor Root Port 00:10.0 USB controller: Advanced Micro Devices [AMD] FCH USB XHCI Controller (rev 09) 00:10.1 USB controller: Advanced Micro Devices [AMD] FCH USB XHCI Controller (rev 09) 00:11.0 SATA controller: Advanced Micro Devices [AMD] FCH SATA Controller [AHCI mode] (rev 40) 00:12.0 USB controller: Advanced Micro Devices [AMD] FCH USB OHCI Controller (rev 11) 00:12.2 USB controller: Advanced Micro Devices [AMD] FCH USB EHCI Controller (rev 11) 00:13.0 USB controller: Advanced Micro Devices [AMD] FCH USB OHCI Controller (rev 11) 00:13.2 USB controller: Advanced Micro Devices [AMD] FCH USB EHCI Controller (rev 11) 00:14.0 SMBus: Advanced Micro Devices [AMD] FCH SMBus Controller (rev 16) 00:14.2 Audio device: Advanced Micro Devices [AMD] FCH Azalia Controller (rev 01) 00:14.3 ISA bridge: Advanced Micro Devices [AMD] FCH LPC Bridge (rev 11) 00:14.4 PCI bridge: Advanced Micro Devices [AMD] FCH PCI Bridge (rev 40) 00:14.5 USB controller: Advanced Micro Devices [AMD] FCH USB OHCI Controller (rev 11) 00:18.0 Host bridge: Advanced Micro Devices [AMD] Family 15h (Models 10h-1fh) Processor Function 0 00:18.1 Host bridge: Advanced Micro Devices [AMD] Family 15h (Models 10h-1fh) Processor Function 1 00:18.2 Host bridge: Advanced Micro Devices [AMD] Family 15h (Models 10h-1fh) Processor Function 2 00:18.3 Host bridge: Advanced Micro Devices [AMD] Family 15h (Models 10h-1fh) Processor Function 3 00:18.4 Host bridge: Advanced Micro Devices [AMD] Family 15h (Models 10h-1fh) Processor Function 4 00:18.5 Host bridge: Advanced Micro Devices [AMD] Family 15h (Models 10h-1fh) Processor Function 5 01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 0c) 02:00.0 IDE interface: JMicron Technology Corp. JMB368 IDE controller 03:05.0 Multimedia controller: Philips Semiconductors SAA7134/SAA7135HL Video Broadcast Decoder (rev 01) Regards. -- Alain Rpnpif -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140704175927.501555a2...@chro.home
Bug#748615: the system reboot after mounting the partitions
Here is a workaround : add the parameter on the command line of the kernel : radeon.dpm=0 Please patch these kernels (3.13 and later). See here : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748615 Regards -- Alain Rpnpif -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140704181800.0c0785a2...@chro.home
Bug#753656: linux-image-3.14-1-rt-amd64: Kernel panic caused by ohci_hcd
Control: tag -1 moreinfo On Fri, 2014-07-04 at 11:03 -0500, Z Winkler wrote: > UPSTREAM BUG. > Been in the kernel for quite some time, too. -_- > Used this info to find that out. > > > BUG: unable to handle kernel NULL pointer dereference at > 0008 (I could have the number of 0s wrong. Reading this > from a photo on my phone) > > IP:[] finish_urb+0xb2/0x150 [ohci_hcd] > > > I hope that's enough. I'm willing to type the rest out if need be, but > there are already bug reports regarding this floating around out > there, it's been reported to the kernel ml, and yikes, that's alot of > hex! Please tell us where those bug reports are, then. Ben. -- Ben Hutchings Who are all these weirdos? - David Bowie, reading IRC for the first time signature.asc Description: This is a digitally signed message part
Processed: Re: Bug#753656: linux-image-3.14-1-rt-amd64: Kernel panic caused by ohci_hcd
Processing control commands: > tag -1 moreinfo Bug #753656 [src:linux] linux-image-3.14-1-rt-amd64: Kernel panic caused by ohci_hcd Added tag(s) moreinfo. -- 753656: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753656 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: https://lists.debian.org/handler.s.b753656.140450063026067.transcr...@bugs.debian.org
Bug#748615: the system reboot after mounting the partitions
On Fri, 2014-07-04 at 20:17 +0200, Alain Rpnpif wrote: > Here is a workaround : > add the parameter on the command line of the kernel : radeon.dpm=0 > > Please patch these kernels (3.13 and later). Where's the patch we need to apply? > See here : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748615 That's the bug report you're writing to. Ben. -- Ben Hutchings Who are all these weirdos? - David Bowie, reading IRC for the first time signature.asc Description: This is a digitally signed message part
Bug#690009: "Invalid iomem size. You may experience problems." I do, experience problems.
On Fri, 2014-07-04 at 15:02 +0200, Ulrich Hansen wrote: > I also see this message on a Dell Precision M 6700. > > The message is: > > sdhci-pci :0c:00.1: Invalid iomem size. You may experience problems. > > uname -a says: > > Linux 3.2.0-4-amd64 #1 SMP Debian 3.2.57-3+deb7u2 x86_64 GNU/Linux > > I don't know if this is related, but I had problems plugging an USB2 > Wifi dongle into an USB3 port of the above laptop. [...] I don't think so; sdhci-pci is a driver for the SD card slot. Ben. -- Ben Hutchings Who are all these weirdos? - David Bowie, reading IRC for the first time signature.asc Description: This is a digitally signed message part
Bug#690009: "Invalid iomem size. You may experience problems." I do, experience problems.
>> I don't know if this is related, but I had problems plugging an USB2 >> Wifi dongle into an USB3 port of the above laptop. > [...] > > I don't think so; sdhci-pci is a driver for the SD card slot. > OK, thank you very much for clarifying. I remembered "You may experience problems" and forgot to check it first. Sorry. All in all the Precision M 6700 doesn't seem to be a good choice for Linux anyway. The fan is too noisy and I didn't find a cure for that yet. But I am able to return it and get a thinkpad instead. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1f41461a-a8bb-43b2-a7c8-c4351d128...@mailbox.org
Bug#752578: Bug
I've discovered some more information about this bug. I'll open another bug report - please close this one. Thanks. Chris
Bug#753768: ath9k: Cannot disable 802.11n in the ath9k driver
Package: src:linux
Version: 3.14.7-1
Severity: normal
File: ath9k
Tags: patch
Dear Maintainer,
The ath9k drive does not support an option for disabling 802.11n.
I (as do many other users) suffer from frequent disconnections when connected
to a
a wireless AP using 802.11n. Disconnections are accompanied by a message
indicating that the client has deauthenticated by local choice (reason=3).
Researching the issue seems to point towards a problem with 802.11n roaming
and various open source WiFi drivers *[1]. Some drivers provide an option to
work around this i.e. '11n_disable=1'.
I notice that 'Michel Alexandre Salim' has contributed the following patch
to enable this functionality *[2]:
---
drivers/net/wireless/ath/ath9k/init.c | 10 +-
1 files changed, 9 insertions(+), 1 deletions(-)
diff --git a/drivers/net/wireless/ath/ath9k/init.c
b/drivers/net/wireless/ath/ath9k/init.c
index 616e30b..9521ca3 100644
--- a/drivers/net/wireless/ath/ath9k/init.c
+++ b/drivers/net/wireless/ath/ath9k/init.c
-43,6 +43,10 static int ath9k_btcoex_enable;
module_param_named(btcoex_enable, ath9k_btcoex_enable, int, 0444);
MODULE_PARM_DESC(btcoex_enable, "Enable wifi-BT coexistence");
+int ath9k_modparam_disable_11n;
+module_param_named(11n_disable, ath9k_modparam_disable_11n, int, 0444);
+MODULE_PARM_DESC(11n_disable, "disable 11n functionality");
+
bool is_ath9k_unloaded;
/* We use the hw_value as an index into our private channel structure */
-231,7 +235,11 static void setup_ht_cap(struct
ath_softc *sc,
u8 tx_streams, rx_streams;
Given that the problem is so widespread and significant, would it not be a good
idea to impliment this functionality in the driver to allow debian users to
connect to 802.11n networks which they don't control?
Thanks,
Chris
---
Sources
---
[1]https://bugs.launchpad.net/ubuntu/+source/wpasupplicant/+bug/872578
[2]http://comments.gmane.org/gmane.linux.kernel.wireless.general/72349
-- Package-specific info:
** Version:
Linux version 3.14-1-amd64 (debian-kernel@lists.debian.org) (gcc version 4.8.3
(Debian 4.8.3-3) ) #1 SMP Debian 3.14.7-1 (2014-06-16)
** Command line:
BOOT_IMAGE=/boot/vmlinuz-3.14-1-amd64
root=UUID=4b58066c-f4c5-4fb7-909b-0075b8807a29 ro quiet
** Not tainted
** Kernel log:
[4.710107] ata1: EH complete
[5.231857] Bluetooth: RFCOMM TTY layer initialized
[5.231889] Bluetooth: RFCOMM socket layer initialized
[5.231898] Bluetooth: RFCOMM ver 1.11
[5.237901] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[5.237907] Bluetooth: BNEP filters: protocol multicast
[5.237919] Bluetooth: BNEP socket layer initialized
[5.585019] ata1.00: exception Emask 0x10 SAct 0x8 SErr 0x280100 action
0x6 frozen
[5.585029] ata1.00: irq_stat 0x0800, interface fatal error
[5.585036] ata1: SError: { UnrecovData 10B8B BadCRC }
[5.585043] ata1.00: failed command: READ FPDMA QUEUED
[5.585055] ata1.00: cmd 60/b0:98:00:ac:6b/00:00:00:00:00/40 tag 19 ncq
90112 in
[5.585055] res 50/00:00:00:00:00/00:00:00:00:00/00 Emask 0x10 (ATA
bus error)
[5.585061] ata1.00: status: { DRDY }
[5.585069] ata1: hard resetting link
[5.905089] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[5.905540] ata1.00: configured for UDMA/133
[5.905561] ata1: EH complete
[6.134432] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[6.263383] systemd-logind[2360]: New seat seat0.
[6.264505] systemd-logind[2360]: Watching system buttons on
/dev/input/event4 (Power Button)
[6.264617] systemd-logind[2360]: Watching system buttons on
/dev/input/event5 (Video Bus)
[6.264715] systemd-logind[2360]: Watching system buttons on
/dev/input/event2 (Power Button)
[6.264806] systemd-logind[2360]: Watching system buttons on
/dev/input/event1 (Lid Switch)
[6.264897] systemd-logind[2360]: Watching system buttons on
/dev/input/event3 (Sleep Button)
[6.266079] systemd-logind[2360]: New session c1 of user lightdm.
[6.266221] systemd-logind[2360]: Linked /tmp/.X11-unix/X0 to
/run/user/112/X11-display.
[6.357021] ata1.00: exception Emask 0x10 SAct 0x80 SErr 0x280100 action
0x6 frozen
[6.357032] ata1.00: irq_stat 0x0800, interface fatal error
[6.357039] ata1: SError: { UnrecovData 10B8B BadCRC }
[6.357046] ata1.00: failed command: READ FPDMA QUEUED
[6.357066] ata1.00: cmd 60/00:b8:80:21:39/01:00:00:00:00/40 tag 23 ncq
131072 in
[6.357066] res 50/00:00:00:00:00/00:00:00:00:00/00 Emask 0x10 (ATA
bus error)
[6.357070] ata1.00: status: { DRDY }
[6.357076] ata1: hard resetting link
[6.677111] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[6.677880] ata1.00: configured for UDMA/133
[6.677961] ata1: EH complete
[ 11.039128] tg3 :02:00.0: irq 46 for MSI/MSI-X
[ 11.039145] tg3 :02:00.0: irq 47 for MSI/MSI-X
[ 11.039156] tg3 :02:00.0: irq 48 for MSI/MSI-X
[ 11.598491] IPv6:
Bug#752881: Shorter gitsect list
It appears some where between linux 3.1.0-rc4 and 3.1.0
More detailed git log below:
git bisect view --pretty=oneline --abbrev-commit --graph
* 00411ee watchdog: Convert wm831x driver to watchdog core
* 25dc46e watchdog: s3c2410: convert to use the watchdog framework
* 74cd4c6 Documentation: watchdog: add guide how to convert drivers to
new framework
* deb9197 watchdog: iTCO_wdt.c - problems with newer hardware due to
SMI clearing
* c63b6d0 watchdog: Add WDIOC_GETTIMELEFT ioctl support to w83627
watchdog driver
* 86b5912 watchdog: irq: Remove IRQF_DISABLED
* 47bfd05 watchdog: Octeon: Mark octeon_wdt interrupt as IRQF_NO_THREAD
* cef153a watchdog: sc520_wdt: Remove unnecessary cast.
* dc822e5 ARM: EXYNOS4: Fix the merge conflict
* 5c8a0fb VFS: fix statfs() automounter semantics regression
* fba9569 Merge branch 'next' of git://git.infradead.org/users/vkoul/slave-dma
|\
| * 4598fc2 dmaengine: mid_dma: mask_peripheral_interrupt only when dmac is idle
| * 2389d67 dmaengine/ep93xx_dma: add module.h include
| * 01631243d pch_dma: Reduce wasting memory
| * c43f150 pch_dma: Fix suspend issue
| * f80befe dma/timberdale: free_irq() on an error path
| * 7a1cd9a dma: shdma: transfer based runtime PM
| * b4dae6e dmaengine: shdma: protect against the IRQ handler
| * 0745c9a Merge branch 'samsung_dma' into next
| * f8de8f4 dmaengine i.MX DMA/SDMA: add missing include of linux/module.h
| * 46389470 dmaengine: delete redundant chan_id and chancnt
initialization in dma drivers
| * c120564 dmaengine/amba-pl08x: Check txd->llis_va before freeing dma_pool
| * b7f69d9 dmaengine/amba-pl08x: Add support for sg len greater than
one for slave transfers
| * 937bb6e serial: sh-sci: don't filter on DMA device, use only channel ID
* 3d0a8d1 Merge branch 'for-3.2/drivers' of git://git.kernel.dk/linux-block
* a0eda62 virtio-blk: use ida to allocate disk index
* c4853ef hpsa: add small delay when using PCI Power Management to
reset for kump
* ab5dbeb cciss: add small delay when using PCI Power Management to
reset for kump
* b8d8bdf Merge branch 'stable/for-jens-3.2' of
git://oss.oracle.com/git/kwilk/xen into for-3.2/drivers
|\
| * 6927d92 xen/blkback: Fix two races in the handling of barrier requests.
| * dda1852 xen/blkback: Check for proper operation.
| * 64391b2 xen/blkback: Fix the inhibition to map pages when
discarding sector ranges.
| * 5c62cb4 xen/blkback: Report VBD_WSECT (wr_sect) properly.
| * 29bde09 xen/blkback: Support 'feature-barrier' aka old-style
BARRIER requests.
| * 469738e xen-blkfront: plug device number leak in xlblk_init() error path
| * d11e615 xen-blkfront: If no barrier or flush is supported, use
invalid operation.
| * 8e6dc6f xen-blkback: use kzalloc() in favor of kmalloc()+memset()
| * c555aab xen-blkback: fixed indentation and comments
| * 69ef68c xen-blkfront: fix a deadlock while handling discard response
| * ed30bf3 xen-blkfront: Handle discard requests.
| * b3cb0d6 xen-blkback: Implement discard requests ('feature-discard')
| * 32a8d26 xen-blkfront: add BLKIF_OP_DISCARD and discard request struct
* 4c823cc drivers/block/loop.c: remove unnecessary bdev argument from
loop_clr_fd()
* 8a9c594 drivers/block/loop.c: emit uevent on auto release
* 5a3a76e drivers/block/cpqarray.c: use pci_dev->revision
* e03c8dd loop: always allow userspace partitions and optionally
support automatic scanning
* e8b177c Merge branch 'for-3.2/core' into for-3.2/drivers
|\
| * d27769e block: add GENHD_FL_NO_PART_SCAN
* dfaa2ef loop: add discard support for loop devices
* 548ef6c nbd-replace-some-printk-with-dev_warn-and-dev_info-checkpatch-fixes
* 5eedf54 nbd: replace some printk with dev_warn() and dev_info()
* 7742ce4 nbd: lower the loglevel of an error message
* 7f1b90f nbd: replace printk KERN_ERR with dev_err()
* 1695b87 nbd: replace sysfs_create_file() with device_create_file()
* 25ac0c2 nbd: use task_pid_nr() to get current pid
* f963d27 cciss: add transport mode attribute to sys
* 1304953 cciss: Adds simple mode functionality
git bisect start
# good: [4c37b233616542536c75d20355d38d1065842103] fixes so can build
under wheezy
git bisect good 4c37b233616542536c75d20355d38d1065842103
# bad: [805a6af8dba5dfdd35ec35dc52ec0122400b2610] Linux 3.2
git bisect bad 805a6af8dba5dfdd35ec35dc52ec0122400b2610
# good: [22763c5cf3690a681551162c15d34d935308c8d7] Linux 2.6.32
git bisect good 22763c5cf3690a681551162c15d34d935308c8d7
# good: [8c4877a4128e7931077b024a891a4b284d8756a3] ehea: Use the
standard logging functions
git bisect good 8c4877a4128e7931077b024a891a4b284d8756a3
# good: [1d0738ea48829cb234fcaba830eef3461985ff44] ARM: mach-shmobile:
Use SCIFA and SCIFB port types on sh7377
git bisect good 1d0738ea48829cb234fcaba830eef3461985ff44
# good: [03b7898d300de62078cc130fbc83b84b1d1e0f8d] ARM: perf: move
active_events into struct arm_pmu
git bisect good 03b7898d300de62078cc130fbc83b84b1d1e0f8d
# good: [0e59e7e7feb5a12938fbf9135147eeda3238c6c4] Merge branch
'next-rebase' of
git://git.kernel.org/pub/scm/linux/kernel/git/jbarnes/
Bug#740491: marked as done (nfs-common: fails to upgrade (action "restart" failed))
Your message dated Fri, 04 Jul 2014 21:35:09 + with message-id and subject line Bug#740491: fixed in libtirpc 0.2.3-2 has caused the Debian Bug report #740491, regarding nfs-common: fails to upgrade (action "restart" failed) 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.) -- 740491: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740491 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: nfs-common Version: 1:1.2.8-6 Severity: serious On upgrading today, I got: Setting up nfs-common (1:1.2.8-6) ... Installing new version of config file /etc/init.d/nfs-common ... insserv: warning: current start runlevel(s) (2 3 4 5 S) of script `nfs-common' overrides LSB defaults (S). Job for nfs-common.service failed. See 'systemctl status nfs-common.service' and 'journalctl -xn' for details. invoke-rc.d: initscript nfs-common, action "restart" failed. dpkg: error processing package nfs-common (--configure): subprocess installed post-installation script returned error exit status 1 [...] Errors were encountered while processing: nfs-common E: Sub-process /usr/bin/dpkg returned an error code (1) $ sudo systemctl status nfs-common.service nfs-common.service - LSB: NFS support files common to client and server Loaded: loaded (/etc/init.d/nfs-common) Active: failed (Result: exit-code) since Sun 2014-03-02 12:22:37 CET; 5min ago Process: 14279 ExecStop=/etc/init.d/nfs-common stop (code=exited, status=0/SUCCESS) Process: 14288 ExecStart=/etc/init.d/nfs-common start (code=exited, status=1/FAILURE) Mar 02 12:22:37 betterave systemd[1]: Starting LSB: NFS support files common to client and server... Mar 02 12:22:37 betterave rpc.statd[14293]: Version 1.2.8 starting Mar 02 12:22:37 betterave rpc.statd[14293]: Failed to read /var/lib/nfs/state: Success Mar 02 12:22:37 betterave rpc.statd[14293]: Initializing NSM state Mar 02 12:22:37 betterave nfs-common[14288]: Starting NFS common utilities: statd failed! Mar 02 12:22:37 betterave systemd[1]: nfs-common.service: control process exited, code=exited status=1 Mar 02 12:22:37 betterave systemd[1]: Failed to start LSB: NFS support files common to client and server. Mar 02 12:22:37 betterave systemd[1]: Unit nfs-common.service entered failed state. Cheers, Julien -- Package-specific info: -- rpcinfo -- program vers proto port service 104 tcp111 portmapper 103 tcp111 portmapper 102 tcp111 portmapper 104 udp111 portmapper 103 udp111 portmapper 102 udp111 portmapper 1000241 udp 42073 status 1000241 tcp 42787 status -- /etc/default/nfs-common -- NEED_STATD= STATDOPTS= NEED_IDMAPD= NEED_GSSD= -- /etc/idmapd.conf -- [General] Verbosity = 0 Pipefs-Directory = /run/rpc_pipefs [Mapping] Nobody-User = nobody Nobody-Group = nogroup -- /etc/fstab -- -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (900, 'testing'), (500, 'stable-updates'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.12-1-amd64 (SMP w/4 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 nfs-common depends on: ii adduser 3.113+nmu3 ii initscripts 2.88dsf-51 ii libc6 2.17-97 ii libcap2 1:2.22-1.2 ii libcomerr2 1.42.9-3 ii libdevmapper1.02.1 2:1.02.83-2 ii libevent-2.0-5 2.0.21-stable-1 ii libgssglue1 0.4-2 ii libk5crypto31.12+dfsg-2 ii libkeyutils11.5.6-1 ii libkrb5-3 1.12+dfsg-2 ii libmount1 2.20.1-5.6 ii libnfsidmap20.25-5 ii libtirpc1 0.2.2-5.1 ii libwrap07.6.q-25 ii lsb-base4.1+Debian12 ii rpcbind 0.2.1-3 ii ucf 3.0027+nmu1 Versions of packages nfs-common recommends: ii python 2.7.5-5 Versions of packages nfs-common suggests: pn open-iscsi pn watchdog -- no debconf information signature.asc Description: Digital signature --- End Message --- --- Begin Message --- Source: libtirpc Source-Version: 0.2.3-2 We believe that the bug you reported is fixed in the latest version of libtirpc, which is due to be installed in the Debian FTP archive. 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 740
Bug#752881: Another git bisection
Identified Fault within 7 changes commit b8d8bdfe31a67981bbc398a4886ccc67aff521d5 Merge: 4c823cc 6927d92 Author: Jens Axboe Date: Thu Oct 20 15:10:59 2011 +0200 Merge branch 'stable/for-jens-3.2' of git://oss.oracle.com/git/kwilk/xen into for-3.2/drivers commit 6927d92091df2848fc0e6a693a017d4b2df549c2 Author: Konrad Rzeszutek Wilk Date: Mon Oct 17 14:27:48 2011 -0400 xen/blkback: Fix two races in the handling of barrier requests. There are two windows of opportunity to cause a race when processing a barrier request. This patch fixes this. Signed-off-by: Konrad Rzeszutek Wilk commit dda1852802a6cc6fdecb9021e491b2de680c76b9 Author: Konrad Rzeszutek Wilk Date: Fri Oct 14 12:13:05 2011 -0400 xen/blkback: Check for proper operation. The patch titled: "xen/blkback: Fix the inhibition to map pages when discarding sector ranges." had the right idea except that it used the wrong comparison operator. It had == instead of !=. This fixes the bug where all (except discard) operations would have been ignored. Signed-off-by: Konrad Rzeszutek Wilk commit 64391b2536ca92f9c589b2bfeaca3954896fe057 Author: Konrad Rzeszutek Wilk Date: Mon Oct 10 00:47:49 2011 -0400 xen/blkback: Fix the inhibition to map pages when discarding sector ranges. The 'operation' parameters are the ones provided to the bio layer while the req->operation are the ones passed in between the backend and frontend. We used the wrong 'operation' value to squash the call to map pages when processing the discard operation resulting in an hypercall that did nothing. Lets guard against going in the mapping function by checking for the proper operation type. CC: Li Dongyang Signed-off-by: Konrad Rzeszutek Wilk commit 5c62cb48602dba95159c81ffeca179d3852e25be Author: Konrad Rzeszutek Wilk Date: Mon Oct 10 12:33:21 2011 -0400 xen/blkback: Report VBD_WSECT (wr_sect) properly. We did not increment the amount of sectors written to disk b/c we tested for the == WRITE which is incorrect - as the operations are more of WRITE_FLUSH, WRITE_ODIRECT. This patch fixes it by doing a & WRITE check. CC: sta...@kernel.org Reported-by: Andy Burns Suggested-by: Ian Campbell Signed-off-by: Konrad Rzeszutek Wilk commit 29bde093787f3bdf7b9b4270ada6be7c8076e36b Author: Konrad Rzeszutek Wilk Date: Mon Oct 10 00:42:22 2011 -0400 xen/blkback: Support 'feature-barrier' aka old-style BARRIER requests. We emulate the barrier requests by draining the outstanding bio's and then sending the WRITE_FLUSH command. To drain the I/Os we use the refcnt that is used during disconnect to wait for all the I/Os before disconnecting from the frontend. We latch on its value and if it reaches either the threshold for disconnect or when there are no more outstanding I/Os, then we have drained all I/Os. Suggested-by: Christopher Hellwig Signed-off-by: Konrad Rzeszutek Wilk commit 469738e675524b6aa029ecd46bdda3f878b12eff Author: Laszlo Ersek Date: Fri Oct 7 21:34:38 2011 +0200 xen-blkfront: plug device number leak in xlblk_init() error path ... though after a failed xenbus_register_frontend() all may be lost. Acked-by: Ian Campbell Signed-off-by: Laszlo Ersek Signed-off-by: Konrad Rzeszutek Wilk commit d11e6158307bed3f178399a4e6216eec67d16200 Author: Konrad Rzeszutek Wilk Date: Fri Sep 16 15:15:14 2011 -0400 xen-blkfront: If no barrier or flush is supported, use invalid operation. Guard against issuing BLKIF_OP_WRITE_BARRIER or BLKIF_OP_FLUSH_CACHE by checking whether we successfully negotiated with the backend. The negotiation with the backend also sets the q->flush_flags which fortunately for us is also used when submitting an bio to us. If we don't support barriers or flushes it would be set to zero so we should never end up having to deal with REQ_FLUSH | REQ_FUA. However, other third party implementations of __make_request that might be stacked on top of us might not be so smart, so lets fix this up. Acked-by: Jan Beulich Signed-off-by: Konrad Rzeszutek Wilk commit 8e6dc6fe51957116d363204a725c1262b4b78e19 Author: Jan Beulich Date: Fri Sep 16 08:38:09 2011 +0100 xen-blkback: use kzalloc() in favor of kmalloc()+memset() This fixes the problem of three of those four memset()-s having improper size arguments passed: Sizeof a pointer-typed expression returns the size of the pointer, not that of the pointed to data. It also reverts using kmalloc() instead of kzalloc() for the allocation of the pending grant handles array, as that array gets fully initialized in a subsequent loop. Reported-by: Julia Lawall Signed-off-by: Jan Beulich Signed-off-by: Konrad Rzeszutek Wilk commit c555aab97de139ac8762c922248
