Strange... I did not yet see any response, comment, note, whatever, in
response to my bug preport. Did I do something wrong?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1328746
Title:
Thanks, Andrew, for testing and for updating the tags. I have just
tested the -proposed kernel and can confirm the fix, too. You beat me by
an hour or so in adding verification-done-trusty.
Mark
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribe
As requested, here is the URL to my e-mail.
http://marc.info/?l=linux-sound&m=140260354628114
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1328746
Title:
Soundblaster Audigy front pan
H. I am running into a serious challenge here. I am OK with the
first step (collecting the information that goes into the e-mail), but
stymied by Step 2. Step 2, section "Reporting non-USB bugs upstream"
states that I need to identify the maintainer in the MAINTAINERS list.
Unfortunately, t
** Attachment removed: "emumpu401.c"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1328746/+attachment/4129882/+files/emumpu401.c
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1
Here is the file. This file replaces /usr/src/linux-
source-3.15.0/sound/pci/emu10k1/emumpu401.c
This is the only file that needs to be modified. Kernel build works
without errors with this file.
** Attachment added: "Attchment contains solution; is replacement file"
https://bugs.launchpad.ne
OK, here are the results:
* Tested with kernel version 3.15.0-031500-lowlatency, specifically the
mainline kernel file linux-
image-3.15.0-031500-lowlatency_3.15.0-031500.201406111300_amd64.deb and
the associated header file.
* Bug persists in the tested kernel version = front panel MIDI uart is
Never mind... I found the kernel source.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1328746
Title:
Soundblaster Audigy front panel MIDI fails to initialize
Status in “linux” package
FIX CONFIRMED. We have been operating with the new NFS server for
several days, and the runaway kworker has not reappeared. Not even once.
The NFS daemon has never "hung" during these days.
I'd say this is it. Thanks, Stefan.
--
You received this bug notification because you are a member of Kern
I am planning to try it with the 3.15 RT kernel -- could you please
point me in the direction of the matching source code, either .deb or
tar? I think the test would be kind of pointless if I tried the upstream
kernel without applying my patch, since I'd be unsurprised if the bug
was still there.
Please note that the entire apport information is irrelevant in this
context.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.ne
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1328746/+attachment/4129350/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1328746/+attachment/4129355/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bug
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1328746/+attachment/4129353/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1328746
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1328746/+attachment/4129349/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "UdevLog.txt"
https://bugs.launchpad.net/bugs/1328746/+attachment/4129354/+files/UdevLog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1328
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1328746/+attachment/4129352/+files/PulseList.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1328746/+attachment/4129351/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1328746/+attachment/4129346/+files/Lspci.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1328746
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1328746/+attachment/4129348/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "BootDmesg.txt"
https://bugs.launchpad.net/bugs/1328746/+attachment/4129344/+files/BootDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/
apport information
** Tags added: apport-collected trusty
** Description changed:
This bug has been around for a while. I have seen it in the forums circa
2007, and I have provided a solution in 2009. Since the modified code
never found its way into the mainstream kernels, I am issuing the
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1328746/+attachment/4129345/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1328746/+attachment/4129347/+files/Lsusb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1328746
** Description changed:
This bug has been around for a while. I have seen it in the forums circa
2007, and I have provided a solution in 2009. Since the modified code
never found its way into the mainstream kernels, I am issuing the fix as
a bug report.
The bug concerns the Soundblast
Public bug reported:
This bug has been around for a while. I have seen it in the forums circa
2007, and I have provided a solution in 2009. Since the modified code
never found its way into the mainstream kernels, I am issuing the fix as
a bug report.
The bug concerns the Soundblaster Audigy cards
Preliminary results: This fixed it.
I say "preliminary", because we tested it only for a short moment. After
some heavy Trados use yesterday, the NFS kernel daemon "hung" again (rpc
timeout, probably choked on its own connect/reconnect state queue), I
installed the kernel packages you prepared. We
Well, I am game.
I'll safely assume that Trados is rather one of the less-frequently used
programs in this community, so it is obviously up to me to run the
actual tests. If you could help me by suggesting debugging functions or
actions, I'll gladly provide more information.
--
You received this
I made one more observation, and it is fully reproducible. Frankly, it
would appear that the bug may not be as impactful as originally though
(if this is a bug, to begin with). Here it is:
On one of the Linux clients, Windows runs in Virtualbox. The NFS share
is mounted within the Linux host, and
I saw the thread with the /etc/exports entry that has fsid=0 (export
filesystem root), and, of course, I tried that. Somehow, I did not get
any valid exports when, for example, using
/home 192.168.1.0/255.255.255.0(rw,fsid=0,root_squash,no_subtree_check)
/home/samba 192.168.1.0/255.255.255.0(r
Strike #11 above. Observation is not correct. The runaway kworker
appears even when all clients use "nfs4".
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1322407
Title:
NFS kernel serv
One more observation that I'll post here as *TENTATIVE*. All clients
are , as I wrote earlier, 12.04 clients. The bug, as described above,
occurs whenever one of the client's fstab entry uses the nfs filesystem:
192.168.1.2:/home /marcato/home nfs
defaults,user,exec,hard,auto,
OK -- bug can be reproduced. Here is an interesting observation: When a
*second* nfs server is connected to the network , the bug seems to be
suppressed, for what it's worth. This one really puzzles me. The runaway
kworker appeared only after I shut down the old server.
As for debugging, the compo
Funny you should mention timing... right now, the server does not show
the runaway kworker. nfds faithfully spits out a few debug messages per
second, but acts normally otherwise. I have put the server back in
production, see if I can catch the runaway kworker when I have more
users -- I'll get so
A few bits for clarification before I get started: (1) Your suggested
value, 524287, clearly is 0x7. This is (RPCDBG_ALL | 0x78000), i.e.,
with four extra bits, correct?
(2) I guess I can harvest the debug messages from /var/log/syslog,
correct? Meaning, once the kworker runs amok, I simply co
Oh, and maybe of less relevance, but to keep it complete, here is the
output of "top":
top - 13:46:47 up 5 days, 56 min, 2 users, load average: 1.00, 0.97, 1.01
Tasks: 172 total, 2 running, 170 sleeping, 0 stopped, 0 zombie
%Cpu(s): 0.0 us, 12.0 sy, 0.0 ni, 83.3 id, 0.0 wa, 4.8 hi, 0.
/etc/exports has one line that is not a comment:
/home 192.168.1.0/255.255.255.0(rw,sync,root_squash,no_subtree_check)
/etc/defaults/nfs-common:
NEED_STATD=no
# Options for rpc.statd.
STATDOPTS=
# Do you want to start the gssd daemon? It is required for Kerberos mounts.
NEED_GSSD=no
/etc/de
*** This bug is a duplicate of bug 1322407 ***
https://bugs.launchpad.net/bugs/1322407
** This bug has been marked a duplicate of bug 1322407
NFS kernel server creates a kworker with 100% CPU usage, then hangs randomly
--
You received this bug notification because you are a member of Kern
Public bug reported:
This concerns the server edition of 14.04. I have set up a NFS server.
Once I attach at least one client, one kworker process starts to use
100% CPU. The runaway kworker returns to idle when I reset the NFS
server daemon with "service nfs-kernel-server stop" followed by "servi
Public bug reported:
This concerns the server edition of 14.04. I have set up a NFS server.
Once I attach at least one client, one kworker process starts to use
100% CPU. The runaway kworker returns to idle when I reset the NFS
server daemon with "service nfs-kernel-server stop" followed by "servi
40 matches
Mail list logo
