Re: Maybe a bug in kernel/irq/chip.c unmask_irq(), device IRQ masked unexpectedly. (re-formated the mail body, sorry)

Hi, Thomas I canceled that patch. In my testing, that will not fix the problem. Why the IRQ is unexpectedly masked, that is not an easy bug for me. More time need to hacking the driver/kernel code. Thanks for your reply. Thomas Gleixner 于2019年10月14日周一 下午8:34写道： > > On Tue, 8 Oct 2019, Yi Zheng

Re: Maybe a bug in kernel/irq/chip.c unmask_irq(), device IRQ masked unexpectedly. (re-formated the mail body, sorry)

On Tue, 8 Oct 2019, Yi Zheng wrote: > There is some defects on IRQ processing: > > (1) At the beginning of handle_level_irq(), the IRQ-28 is masked, and ACK > action is executed: On my machine, it runs the 'else' branch: > > static inline void mask_ack_irq(struct ir

Re: Maybe a bug in kernel/irq/chip.c unmask_irq(), device IRQ masked unexpectedly. (re-formated the mail body, sorry)

* Yi Zheng [191010 06:22]: > Hi > >My patch is canceled. I have tested that simple adjustment, the > device IRQ masked unexpectedly. It seems that it is more easily to > occur with that patch. > > So, the root cause is not found yet. OK. Based on your description, it could be a missing flus

Re: Maybe a bug in kernel/irq/chip.c unmask_irq(), device IRQ masked unexpectedly. (re-formated the mail body, sorry)

Hi My patch is canceled. I have tested that simple adjustment, the device IRQ masked unexpectedly. It seems that it is more easily to occur with that patch. So, the root cause is not found yet.

Re: Maybe a bug in kernel/irq/chip.c unmask_irq(), device IRQ masked unexpectedly. (re-formated the mail body, sorry)

Hi, * Yi Zheng [191008 13:06]: > NOTE: (1) My SoC is a single core ARM chip: TI-AM3352, so the raw > spin-lock irq_desc->lock will be optimized to > nothing. handle_level_irq() has no spin-lock protection, right? Well not always, With CONFIG_SMP we modify only some of the

Re: maybe a bug in SELinux: security_context_to_sid_core

Hi, Bill For below SELinux behavior, do you know why. BR. Ning. 在 2018-02-28三的 14:47 +0800，Zhang Ning写道： > Hi, > > Before SELinux is initialized, get scontext by secid by using: > > security_secctx_to_secid() may return wrong numbe > > eg: > security_secctx_to_secid("devnull", strlen("devnul

Re: Maybe a bug

Maciej W. Rozycki wrote: > Hmm, you state the watchdog works from time to time and the log you > provided confirms the statement -- it reports: > > ..TIMER: vector=49 pin1=2 pin2=0 > > activating NMI Watchdog ... done. Yes, but I reach this message only once of 10 trials to boot. The other nin

Re: Maybe a bug

On Mon, 19 Feb 2001, Matthias Kleine wrote: > The problem appears on a machine using the pretty new ASUS CUVX-D Dual Socket > 370 Motherboard, so there may be a chance for an unknown bug ;-). With NMI > watchdog activated, a 2.4.x Kernel is not willing to boot on this machine, it > just stops

Re: Maybe a bug (unexpected IO-APIC)

> > Feb 19 19:37:17 delphin kernel: testing the IO APIC... > Feb 19 19:37:17 delphin kernel: > Feb 19 19:37:17 delphin kernel: WARNING: unexpected IO-APIC, please mail > Feb 19 19:37:17 delphin kernel: to [EMAIL PROTECTED] > Feb 19 19:37:17 delphin kernel: ..