linux-kernel - Re: 2.6.21-rc3: /proc broken

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 9 Mar 2007 20:59:54 +1100
From:	Con Kolivas <kernel@...ivas.org>
To:	Russell King <rmk+lkml@....linux.org.uk>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org
Subject: Re: 2.6.21-rc3: /proc broken

On Friday 09 March 2007 19:53, Russell King wrote:
> On Fri, Mar 09, 2007 at 08:56:44AM +1100, Con Kolivas wrote:
> > I did make oldconfig from http://userweb.kernel.org/~akpm/ck/config.txt
> > and chose all the defaults. Then building your fat config with -rc3, 'ps'
> > hangs on qemu for almost 30 seconds and then at last produces a broken
> > output
>
> Let me guess - you have either a serial console or something like that
> and you're running these commands over said serial console?
>
> Or you have console directed to both a serial port and the VT and you're
> capturing this off the VT using gpm.
>
> Either way, "serial8250: too much work for irq4" is a printk which will
> be displayed by the kernel when it's unable to clear down work for the
> serial port within 256 loops or so of the interrupt handler; it's a
> protection against the box locking up.
>
> It not actually contained in any of the files.

Thank you very much for taking the time to explain it to me and I apologise 
for the false positive. It's very much due to running qemu directing 
everything to the serial console which is just as you say. Allowing qemu to 
output to graphic fixes the error. Unfortunately that also makes akpm's oops 
go away so I can't really reproduce it now. Perhaps the bug occurs due to 
interrupts being disabled for an extended time; it gives me something to look 
at now.

Thanks!

-- 
-ck
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/