From: Masoud Sharbiani
Two entries for the same system type were added, with two different vendor
names: 'Dell' and 'Dell, Inc.'. Since a prefix match is being used, we can
eliminate the latter.
Signed-off-by: Masoud Sharbiani
---
arch/x86/kernel/reboot.c |8 ---
Hi!
> And what about the code from kernel/sys.c ?
> The version you provided doesn't take care of what's
> the default value of pcspeaker. This would make it
> undefined, which is not really good.
Since the variable is global in kernel/sysctl.c (and not kernel/sys.c),
and globals are set to z
[EMAIL PROTECTED] wrote:
> You see, I can't even begin to write one line of code, because I know
> nothing about what I am supposed to do. Sure, I know the basics, I have
> written toy device drivers for Linux, I know how to implement a driver for
> Minix, understand the main loop, handling messa
Hello,
1) What is your kernel version?
2) It is tainted; Why?
3) Make sure your app/kernel combo works with SIGKILL. If it doesn't,
then you have a serious bug.
cheers,
Masoud
vinay wrote:
Hi.
Why I wanted to force OOM killer to send SIGTERM is that -
When my application receives SIGKILL fr
Hello,
I have a dual P3 machine that crashes when I first (cold) start it with
2.6.13-rc6 and then reboot it to use 2.4.32-pre2.
It boots, and during booting, around the time it is supposed to
initalize serial device and software watchdog, it hangs with a message
like this: (Note: It is garbled
-
Thanks in advance,
Masoud
On Wed, Aug 10, 2005 at 11:15:14AM -0400, Masoud Sharbiani wrote:
> Hello,
> I have a dual P3 machine that crashes when I first (cold) start it with
> 2.6.13-rc6 and then reboot it to use 2.4.32-pre2.
> It boots, and during booting, around the time it is
Hello,
Whenever I reboot my Linux machine it turns itself off in the end,
unless I add the 'acpi=off' to the end of kernel command line on boot.
Apparently, it happens after unmounting filesystems as it doesn't do
fsck after next power-up.
The Kernel is 2.6.13-pre6
The machine itself is a dua
Hello,
Adding reboot=w causes system to reboot properly.
Is this a known issue with 2.6.latest ACPI or is it that my mainboard is
broken?
cheers,
Masoud
Jiri Slaby wrote:
Masoud Sharbiani napsal(a):
Hello,
Whenever I reboot my Linux machine it turns itself off in the end,
unless I add the
Hello,
Jiri Slaby wrote:
Masoud Sharbiani napsal(a):
Is this a known issue with 2.6.latest ACPI or is it that my mainboard
is broken?
No, I don't know about anybody, who has the same problem (it doesn't
mean, that it couldn't be).
Did it work before? Could you accurate ve
Can you turn on UDP checksums and try again? That would isolate the
fault between the network or SATA.
cheers,
Masoud
Grant Coady wrote:
On Fri, 12 Aug 2005 14:43:42 +0400, "Vladimir V. Saveliev" <[EMAIL PROTECTED]>
wrote:
How to test and isolate this error is in NIC driver, SATA driver or
Hello,
I've filed kenrel bug 5099 about this issue.
cheers,
Masoud
Meelis Roos wrote:
I'm currently running 2.6.13-rc6+git as of today and whan I tell my
computer to reboot, it starts a reboot as sual and when it reached
kernel telling "Rebooting" the computer halts instead. I noticed it
just
00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 e6 8c ff 00 00 00 00 2b
00 00 00 00 00 00 00 00 00 00 00 00 00 00
<0>Kernel panic - not syncing: Attempted to kill the idle task!
---
2.6.13-rc6 boots, but has the bug 5099 (at bugzilla.kernel.org).
cheers,
Masoud Sharbiani
-
Sadly, with 2.6.13 (as in with 2.6.13-rc7), it crashes on boot, on a
dual P3 machine
It works just fine when compiled UP.
This bug did NOT exist on 2.6.13-rc6 version.
Through a serial console I captured the following:
---
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing
disabled
Yes. I did also report it (see http://lkml.org/lkml/2005/8/26/252)
cheers,
Masoud Sharbiani
Lee Revell wrote:
On Mon, 2005-08-29 at 14:23 -0400, Masoud Sharbiani wrote:
Sadly, with 2.6.13 (as in with 2.6.13-rc7), it crashes on boot, on a
dual P3 machine
It works just fine when compiled UP
l has been renamed back to the old
> 'exception-trace' to avoid breakage of people's scripts.
>
> cheers,
> Masoud Sharbiani
>
> Signed-off-by: Masoud Sharbiani <[EMAIL PROTECTED]>
> Cc: Andi Kleen <[EMAIL PROTECTED]>
>
> ---
> arch/i386/
On 7/25/07, Andrew Morton <[EMAIL PROTECTED]> wrote:
On Wed, 25 Jul 2007 16:57:43 +0200
Andi Kleen <[EMAIL PROTECTED]> wrote:
> On Wednesday 25 July 2007 16:45, Kirill Korotaev wrote:
> > plz don't enable it by default... :/
> > any user can spam syslog with these messages and if syslog is run a
On 7/25/07, Andrew Morton <[EMAIL PROTECTED]> wrote:
On Wed, 25 Jul 2007 16:40:06 -0700
[EMAIL PROTECTED] (Masoud Asgharifard Sharbiani) wrote:
> > Look: if there's a way in which an unprivileged user can trigger a printk
> > we fix it, end of story. I don't know why this even slightly
> > cont
es can behave more uniformly between
> different kernels. Like x86_64, it can be disabled by setting
> debug.exception-trace sysctl variable to 0 (or by doing
> echo 0 > /proc/sys/debug/exception-trace)
>
> Same behaviour can be extended to other architectures, if needed.
> chee
Hey folks,
I’ve come across an issue that affects most of 4.19, 4.20 and 5.2 linux-stable
kernels that has only been fixed in 5.3-rc1.
It was introduced by
29ef680 memcg, oom: move out_of_memory back to the charge path
The gist of it is that if you have a memory control group for a process that
> On Aug 1, 2019, at 11:19 AM, Greg KH wrote:
>
> On Thu, Aug 01, 2019 at 11:04:14AM -0700, Masoud Sharbiani wrote:
>> Hey folks,
>> I’ve come across an issue that affects most of 4.19, 4.20 and 5.2
>> linux-stable kernels that has only been fixed in 5.3-r
> On Aug 2, 2019, at 12:40 AM, Michal Hocko wrote:
>
> On Thu 01-08-19 11:04:14, Masoud Sharbiani wrote:
>> Hey folks,
>> I’ve come across an issue that affects most of 4.19, 4.20 and 5.2
>> linux-stable kernels that has only been fixed in 5.3-rc1.
>> It
> On Aug 2, 2019, at 7:41 AM, Michal Hocko wrote:
>
> On Fri 02-08-19 07:18:17, Masoud Sharbiani wrote:
>>
>>
>>> On Aug 2, 2019, at 12:40 AM, Michal Hocko wrote:
>>>
>>> On Thu 01-08-19 11:04:14, Masoud Sharbiani wrote:
>>>> He
19.0 and 5.3 that could be necessary…
>
>
> From 2f92c70f390f42185c6e2abb8dda98b1b7d02fa9 Mon Sep 17 00:00:00 2001
> From: Tetsuo Handa
> Date: Sun, 4 Aug 2019 00:41:30 +0900
> Subject: [PATCH] memcg, oom: don't require __GFP_FS when invoking memcg OOM
> killer
>
>
> On Aug 3, 2019, at 10:41 AM, Masoud Sharbiani wrote:
>
>
>
>> On Aug 3, 2019, at 8:51 AM, Tetsuo Handa
>> wrote:
>>
>> Masoud, will you try this patch?
>
> Gladly.
> It looks like it is working (and OOMing properly).
>
>
On 2/24/08, Ady Wicaksono <[EMAIL PROTECTED]> wrote:
> I have 8 Gbytes RAM, but why I can allocate 2.8 Gbytes RAM for a single
> process?
> How to patch kernel so I have more than 2.8 Gbytes limitation?
>
> Kernel:
> ---
> Linux xxx.com 2.6.9-023stab046.2-enterprise #1
On 1/8/08, Tuomo Valkonen <[EMAIL PROTECTED]> wrote:
> On 2008-01-08, Andre Noll <[EMAIL PROTECTED]> wrote:
> > Use tune2fs to deactivate checking.
>
> So, a workaround is the answer to a clear bug. Typical FOSS.
It isn't a bug. It is a feature; Think about silent corruption that
may damage your f
On 12/19/07, Siva Prasad <[EMAIL PROTECTED]> wrote:
>
> Yes!... this is a embedded system, and will not have monitor. So, serial
> is the default console.
>
> I pass cmdline as "root=/dev/ram rw console=ttyS0,115200"
Adding a CONSOLE=/dev/ttyS0 works for me on both Debian and Redhat;
You also want
Commit-ID: b5eafc6f07c95e9f3dd047e72737449cb03c9956
Gitweb: http://git.kernel.org/tip/b5eafc6f07c95e9f3dd047e72737449cb03c9956
Author: Masoud Sharbiani
AuthorDate: Thu, 26 Sep 2013 10:30:43 -0700
Committer: Ingo Molnar
CommitDate: Thu, 26 Sep 2013 20:52:37 +0200
x86/reboot: Remove the
Commit-ID: 4f0acd31c31f03ba42494c8baf6c0465150e2621
Gitweb: http://git.kernel.org/tip/4f0acd31c31f03ba42494c8baf6c0465150e2621
Author: Masoud Sharbiani
AuthorDate: Fri, 20 Sep 2013 15:59:07 -0700
Committer: Ingo Molnar
CommitDate: Mon, 23 Sep 2013 10:26:08 +0200
x86/reboot: Add quirk
29 matches
Mail list logo
