Hello,
If I remember correctly kernel developers promised not to break user APIs in
the Linux kernel
however in Linux 3.7 a /proc//oom_adj file has been totally removed which
makes KDE 3.5.x
(and I suppose TDE) unusable as they depend on this file and simply refuse to
start in its absence.
Hello,
If I remember correctly kernel developers promised not to break user APIs in
the Linux kernel
however in Linux 3.7 a /proc/PID/oom_adj file has been totally removed which
makes KDE 3.5.x
(and I suppose TDE) unusable as they depend on this file and simply refuse to
start in its absence.
On Nov 8, 2012, Takashi Iwai wrote:
> How about the patch below? (It's for 3.6, and won't be applied cleanly
> to 3.7, but easy to adapt.)
This patch fixes my problem, thank you!
You can add me as "Tested by".
Artem
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel"
On Nov 8, 2012, Takashi Iwai wrote:
How about the patch below? (It's for 3.6, and won't be applied cleanly
to 3.7, but easy to adapt.)
This patch fixes my problem, thank you!
You can add me as Tested by.
Artem
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the
On Oct 22, 2012, Alan Stern wrote:
> A BUG() at these points would crash the machine hard. And where we
> came from doesn't matter; what matters is the values in the pointers.
OK, here's what the kernel prints with your patch:
usb 6.1.4: ep 86 list del corruption prev: e5103b54 e5103a94
On Oct 22, 2012, Alan Stern st...@rowland.harvard.edu wrote:
A BUG() at these points would crash the machine hard. And where we
came from doesn't matter; what matters is the values in the pointers.
OK, here's what the kernel prints with your patch:
usb 6.1.4: ep 86 list del corruption prev:
> Nice. Could you do that again with the patch applied I sent yo some
> hours ago?
That patch was of no help - the system has crashed and I couldn't spot relevant
messages.
I've no idea what it means.
Artem
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body
>
> On Oct 21, 2012, Borislav Petkov wrote:
>
> On Sun, Oct 21, 2012 at 11:59:36AM +0000, Artem S. Tashkinov wrote:
> > http://imageshack.us/a/img685/9452/panicz.jpg
> >
> > list_del corruption. prev->next should be ... but was ...
>
> Btw, this
> On Oct 21, 2012, Daniel Mack wrote:
>
> [Cc: alsa-devel]
>
> On 21.10.2012 14:30, Artem S. Tashkinov wrote:
> > On Oct 21, 2012, Daniel Mack wrote:
> >
> >> A hint at least. How did you enable the audio record exactly? Can you
> >> reprod
On Oct 21, 2012, Daniel Mack wrote:
> A hint at least. How did you enable the audio record exactly? Can you
> reproduce this with arecord?
>
> What chipset are you on? Please provide both "lspci -v" and "lsusb -v"
> dumps. As I said, I fail to reproduce that issue on any of my machines.
All
On Oct 21, 2012, Borislav Petkov wrote:
>
> On Sun, Oct 21, 2012 at 01:57:21AM +, Artem S. Tashkinov wrote:
> > The freeze happens on my *host* Linux PC. For an experiment I decided
> > to check if I could reproduce the freeze under a virtual machine - it
> > turns out
On Oct 21, 2012, Borislav Petkov wrote:
On Sun, Oct 21, 2012 at 01:57:21AM +, Artem S. Tashkinov wrote:
The freeze happens on my *host* Linux PC. For an experiment I decided
to check if I could reproduce the freeze under a virtual machine - it
turns out the Linux kernel running under
On Oct 21, 2012, Daniel Mack wrote:
A hint at least. How did you enable the audio record exactly? Can you
reproduce this with arecord?
What chipset are you on? Please provide both lspci -v and lsusb -v
dumps. As I said, I fail to reproduce that issue on any of my machines.
All other
On Oct 21, 2012, Daniel Mack wrote:
[Cc: alsa-devel]
On 21.10.2012 14:30, Artem S. Tashkinov wrote:
On Oct 21, 2012, Daniel Mack wrote:
A hint at least. How did you enable the audio record exactly? Can you
reproduce this with arecord?
What chipset are you on? Please provide
On Oct 21, 2012, Borislav Petkov b...@alien8.de wrote:
On Sun, Oct 21, 2012 at 11:59:36AM +, Artem S. Tashkinov wrote:
http://imageshack.us/a/img685/9452/panicz.jpg
list_del corruption. prev-next should be ... but was ...
Btw, this is one of the debug options I told you
Nice. Could you do that again with the patch applied I sent yo some
hours ago?
That patch was of no help - the system has crashed and I couldn't spot relevant
messages.
I've no idea what it means.
Artem
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a
> On Oct 21, 2012, Borislav Petkov wrote:
>
> On Sat, Oct 20, 2012 at 11:15:17PM +0000, Artem S. Tashkinov wrote:
> > You don't get me - I have *no* VirtualBox (or any proprietary) modules
> > running
>
> Ok, good. We got that out of the way - I wanted to make sure a
You don't get me - I have *no* VirtualBox (or any proprietary) modules running
- but I can reproduce this problem using *the same system running under*
VirtualBox
in Windows 7 64.
It's almost definitely either a USB driver bug or video4linux driver bug:
I'm CC'ing linux-media and linux-usb
Hi,
I can only reproduce this panic when my USB webcamera is plugged in - when
I click settings in Adobe Flash it sends some commands to my USB webcam using,
presumably, Video4Linux API calls which cause a kernel hard crash.
Your kernel debug features haven't helped at all, even the virtual
On Oct 21, 2012, Borislav Petkov wrote:
> Ok, here's what you can try:
>
> * You say this happens with google chrome. Does it happen if you use
> another browser: firefox, etc?
>
> * Can you build a 64-bit kernel and try the same with it? The 32-bit
> userspace should work in compat mode just
Hello,
I'm running vanilla Linux 3.6.2 x86 on top of CentOS 6.3 userspace.
Every time when I enter the chat roulette website, right click anywhere and
choose "Settings",
my PC crashes (with or without NVIDIA drivers running, it happens even when
I'm running Vesa).
Web browser:
Hello,
I'm running vanilla Linux 3.6.2 x86 on top of CentOS 6.3 userspace.
Every time when I enter the chat roulette website, right click anywhere and
choose Settings,
my PC crashes (with or without NVIDIA drivers running, it happens even when
I'm running Vesa).
Web browser:
On Oct 21, 2012, Borislav Petkov wrote:
Ok, here's what you can try:
* You say this happens with google chrome. Does it happen if you use
another browser: firefox, etc?
* Can you build a 64-bit kernel and try the same with it? The 32-bit
userspace should work in compat mode just fine.
Hi,
I can only reproduce this panic when my USB webcamera is plugged in - when
I click settings in Adobe Flash it sends some commands to my USB webcam using,
presumably, Video4Linux API calls which cause a kernel hard crash.
Your kernel debug features haven't helped at all, even the virtual
You don't get me - I have *no* VirtualBox (or any proprietary) modules running
- but I can reproduce this problem using *the same system running under*
VirtualBox
in Windows 7 64.
It's almost definitely either a USB driver bug or video4linux driver bug:
I'm CC'ing linux-media and linux-usb
On Oct 21, 2012, Borislav Petkov wrote:
On Sat, Oct 20, 2012 at 11:15:17PM +, Artem S. Tashkinov wrote:
You don't get me - I have *no* VirtualBox (or any proprietary) modules
running
Ok, good. We got that out of the way - I wanted to make sure after you
replied with two other
101 - 126 of 126 matches
Mail list logo
