Just FYI, this solves the orig issue for me as well. ;)
Thanks for all the work in tracking it down...
Tested-by: Kevin Fenzi
kevin
signature.asc
Description: PGP signature
On Mon, 20 Oct 2014 14:53:59 -0600
Kevin Fenzi wrote:
> On Mon, 20 Oct 2014 16:43:26 -0400
> Dave Jones wrote:
>
> > I've seen similar soft lockup traces from the sys_unshare path when
> > running my fuzz tester. It seems that if you create enough network
> >
On Mon, 20 Oct 2014 16:43:26 -0400
Dave Jones wrote:
> I've seen similar soft lockup traces from the sys_unshare path when
> running my fuzz tester. It seems that if you create enough network
> namespaces, it can take a huge amount of time for them to be iterated.
> (Running trinity with '-c uns
Greetings.
I'm seeing suspend/resume failures with recent 3.18 git kernels.
Full dmesg at: http://paste.fedoraproject.org/143615/83287914/
The possibly interesting parts:
[ 78.373144] PM: Syncing filesystems ... done.
[ 78.411180] PM: Preparing system for mem sleep
[ 78.411995] Freezin
Well, that was fun. ;)
git bisect start
# bad: [69c88dc7d9f1a6c3eceb7058111677c640811c94] vfs: fix new kernel-doc
warnings
git bisect bad 69c88dc7d9f1a6c3eceb7058111677c640811c94
# good: [31d141e3a666269a3b6fcccddb0351caf7454240] Linux 3.12-rc6
git bisect good 31d141e3a666269a3b6fcccddb0351caf74
On Thu, 7 Nov 2013 16:10:07 +0800
AceLan Kao wrote:
> Hi Kevin,
>
> http://people.canonical.com/~acelan/elan_touchscreen/
> Here are the kernels, please test them one by one and tell me which
> one works. As your description, the first one should work, and the
> second one doesn't, I just want t
On Wed, 6 Nov 2013 09:44:11 +0800
AceLan Kao wrote:
> Hi,
>
> Sorry, no thoughts about this.
> If Kevin would like to try, I can bisect the kernel and build the
> Ubuntu .deb package for him.
> But like I say above, those 4 commits doesn't look like to lead to the
> problem, so I'll try to bisec
On Wed, 30 Oct 2013 09:41:06 +0800
AceLan Kao wrote:
> Hi,
>
> It's hard to believe that those quirks will lead to the problem.
> And actually, there are 4 new commits introduced to -rc7, and 3 of
> them are quirks.
>
> % git log --pretty=oneline v3.12-rc6..v3.12-rc7 drivers/hid
> 86b84167d4e67
Greetings.
I have a lenovo yoga 2 pro.. it has a ELAN Touchscreen.
In 3.12rc5 it was detected and works.
in 3.12rc6 it was detected and works.
Sometime after the rc6 timeframe it stopped working. It doesn't work with
rc7.
In dmesg I get:
[ 159.519663] usb 2-7: New USB device found, idVe
On Sun, 13 Jan 2013 10:06:41 +0100
Takashi Iwai wrote:
> At Sat, 12 Jan 2013 11:40:24 -0700,
> Kevin Fenzi wrote:
> >
> > On Tue, 08 Jan 2013 16:26:38 +0100
> > Takashi Iwai wrote:
> >
> > > At Sat, 22 Dec 2012 14:23:24 -0700,
> > &g
On Tue, 08 Jan 2013 16:26:38 +0100
Takashi Iwai wrote:
> At Sat, 22 Dec 2012 14:23:24 -0700,
> Kevin Fenzi wrote:
> >
> > Greetings.
> >
> > I've got an issue with sound on my t510. It started in the late
> > 3.4.x kernels. Sound works on boot and for
On Tue, 08 Jan 2013 16:26:38 +0100
Takashi Iwai wrote:
> It's a known problem that some people have already reported, but
> currently no clue who actually turns down the pin to D3.
> Conexant guys wrote me that the codec doesn't do it by itself, and the
> driver neither, AFAIK. A possible answer
Greetings.
I've got an issue with sound on my t510. It started in the late 3.4.x
kernels. Sound works on boot and for 5-10min after, then the speakers
stop working at all.
I posted a while back on the alsa-users list, and someone else had the
same issue:
http://www.mail-archive.com/alsa-user@
On Sat, 3 Mar 2007 07:45:19 +0100
[EMAIL PROTECTED] (Oliver Neukum) wrote:
> Am Samstag, 3. März 2007 03:37 schrieb Kevin Fenzi:
> > I'm seeing some oddity with the latest fedora development kernel
> > and a usbserial device.
>
> Very interesting. Is this repeatable?
I'm seeing some oddity with the latest fedora development kernel and a
usbserial device.
2.6.20-1.2949.fc7 #1 SMP Mon Feb 26 18:33:03 EST 2007 x86_64 x86_64
x86_64 GNU/Linux
Its a evdo device.
Doing:
modprobe usbserial vendor=0x413c product=0x8128 debug=1
gets:
drivers/usb/serial/usb-seri
Duh.
I figured out the problem. In 2.4.0-test13-pre3 is the introduction of
the shmall sysctl. I had installed a package called powertweak a while
back. It looks like powertweak sets any sysctl it doesn't know to 0.
So, the problem was that there was no shared memory for X. ;(
I set that up
> "Alan" == Alan Cox <[EMAIL PROTECTED]> writes:
>> (II) Loading /usr/X11R6/lib/modules/linux/libint10.a (II) Module
>> int10: vendor="The XFree86 Project" compiled for 4.0.1a, module
>> version = 1.0.0 ABI class: XFree86 Video Driver, version 0.2 (EE)
>> ATI(0): Unable to initialise int10 in
> "Alan" == Alan Cox <[EMAIL PROTECTED]> writes:
>> (II) Loading /usr/X11R6/lib/modules/linux/libint10.a (II) Module
>> int10: vendor="The XFree86 Project" compiled for 4.0.1a, module
>> version = 1.0.0 ABI class: XFree86 Video Driver, version 0.2 (EE)
>> ATI(0): Unable to initialise int10 in
Hi there. Having been running the 2.4.0-test kernels on my laptop, I
quickly upgraded to 2.4.0 when it came out. A problem quickly arose:
X won't start.
Under 2.4.0-test12 it works fine.
Under 2.4.0 it exits after trying to load the int10 module...
from 2.4.0-test12 (and all others):
(II)
19 matches
Mail list logo
