On Tue, Jun 21, 2005 at 10:34:24AM +0200, Pavel Machek wrote:
> Hi!
>
> I got
>
> Jun 21 10:30:20 amd kernel: ------------[ cut here ]------------
> Jun 21 10:30:20 amd kernel: kernel BUG at fs/open.c:935!
> Jun 21 10:30:20 amd kernel: invalid operand: 0000 [#1]
> Jun 21 10:30:20 amd kernel: Modules linked in: ipw2100
> Jun 21 10:30:20 amd kernel: CPU: 0
> Jun 21 10:30:20 amd kernel: EIP: 0060:[page_referenced+39/160] Not tainted VLI
> Jun 21 10:30:20 amd kernel: EFLAGS: 00010286 (2.6.12-mm1)
> Jun 21 10:30:20 amd kernel: EIP is at fd_install+0x27/0x40
> Jun 21 10:30:20 amd kernel: eax: f7268e00 ebx: 00000080 ecx: f61a9800 edx: f6106400
This has been reported by several other people.
I am looking at it except that I can't reproduce it with the config
files in one of those bug reports. Probably whatever userland triggers
this bug isn't in my lab machine. Besides I am running really old
userland anyway. I am going to find a box with newer userland
and try.
Some things are common - always with fcntl() or fcntl64() and with
a daemon. Does your box come up at all ? If so, can you get me an
strace on the process that triggers this ? If I can narrow it
down to a small testcase, it would be a lot easier. Also, does
switching off CONFIG_PREEMPT fix this problem ?
Thanks
Dipankar
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
