On Mon, Jul 30, 2007 at 11:05:09AM -0700, Christoph Lameter wrote:
> Looks like the slab header was corrupted. If this can be reproduced then
> you need to enable slub debugging to find the kernel function that
> corrupts memory.
Yup, I'll try that if it happens again.
> Otherwise it could be
On Mon, 30 Jul 2007, Robert Schwebel wrote:
> On Mon, Jul 30, 2007 at 12:16:04AM -0700, Andrew Morton wrote:
> > > My Dell Latitude D520 just dies with this BUG:
> >
> > Reproducible, I assume.
>
> No, happened only one time.
Looks like the slab header was corrupted. If this can be reproduced
On Mon, Jul 30, 2007 at 12:16:04AM -0700, Andrew Morton wrote:
> > My Dell Latitude D520 just dies with this BUG:
>
> Reproducible, I assume.
No, happened only one time.
> Have you tried testing a kernel which doesn't have those drivers?
>
> (It'd be a clever little driver to cause that BUG
st kernel: [ cut here ]
> Jul 29 09:30:00 localhost kernel: kernel BUG at mm/slab.c:2980!
> Jul 29 09:30:00 localhost kernel: invalid opcode: [#1]
> Jul 29 09:30:00 localhost kernel: PREEMPT SMP
> Jul 29 09:30:00 localhost kernel: Modules linked in: button psmouse hi
:30:00 localhost kernel: kernel BUG at mm/slab.c:2980!
Jul 29 09:30:00 localhost kernel: invalid opcode: [#1]
Jul 29 09:30:00 localhost kernel: PREEMPT SMP
Jul 29 09:30:00 localhost kernel: Modules linked in: button psmouse hidp
rfcomm l2cap hci_vhci dtl1_cs btuart_cs bt3c_cs bluecard_cs bf
On Mon, Jul 30, 2007 at 12:16:04AM -0700, Andrew Morton wrote:
My Dell Latitude D520 just dies with this BUG:
Reproducible, I assume.
No, happened only one time.
Have you tried testing a kernel which doesn't have those drivers?
(It'd be a clever little driver to cause that BUG though)
On Mon, 30 Jul 2007, Robert Schwebel wrote:
On Mon, Jul 30, 2007 at 12:16:04AM -0700, Andrew Morton wrote:
My Dell Latitude D520 just dies with this BUG:
Reproducible, I assume.
No, happened only one time.
Looks like the slab header was corrupted. If this can be reproduced then
you
On Mon, Jul 30, 2007 at 11:05:09AM -0700, Christoph Lameter wrote:
Looks like the slab header was corrupted. If this can be reproduced then
you need to enable slub debugging to find the kernel function that
corrupts memory.
Yup, I'll try that if it happens again.
Otherwise it could be bad
Hi,
My Dell Latitude D520 just dies with this BUG:
--8<--8<--8<--8<--
Jul 29 09:30:00 localhost kernel: [ cut here ]
Jul 29 09:30:00 localhost kernel: kernel BUG at mm/slab.c:2980!
Jul 29 09:30:00 localhost kernel: in
Hi,
My Dell Latitude D520 just dies with this BUG:
--8--8--8--8--
Jul 29 09:30:00 localhost kernel: [ cut here ]
Jul 29 09:30:00 localhost kernel: kernel BUG at mm/slab.c:2980!
Jul 29 09:30:00 localhost kernel: invalid opcode:
Hi !
On Wed, Dec 20, 2006 at 12:21:59PM -0700, Sebastian Kuzminsky wrote:
> Hi folks, I've got an old PC (Pentium 133 MHz, 64 MB RAM, no swap)
> running Linux 2.4.32, and lately I've been getting kernel BUGs like this:
>
> kernel: kernel BUG at slab.c:1582!
> kernel:
Hi !
On Wed, Dec 20, 2006 at 12:21:59PM -0700, Sebastian Kuzminsky wrote:
Hi folks, I've got an old PC (Pentium 133 MHz, 64 MB RAM, no swap)
running Linux 2.4.32, and lately I've been getting kernel BUGs like this:
kernel: kernel BUG at slab.c:1582!
kernel: invalid operand:
Hi folks, I've got an old PC (Pentium 133 MHz, 64 MB RAM, no swap)
running Linux 2.4.32, and lately I've been getting kernel BUGs like this:
kernel: kernel BUG at slab.c:1582!
kernel: invalid operand:
kernel: CPU:0
kernel: EIP:0010:[kmem_cache_free+105/624
Hi folks, I've got an old PC (Pentium 133 MHz, 64 MB RAM, no swap)
running Linux 2.4.32, and lately I've been getting kernel BUGs like this:
kernel: kernel BUG at slab.c:1582!
kernel: invalid operand:
kernel: CPU:0
kernel: EIP:0010:[kmem_cache_free+105/624
Hello,
At Fri, 22 Jun 2001 15:01:43 +,
Gav wrote:
>
> This second one was immediately after rebooting, and hard locked at getty.
>
> kernel BUG at slab.c:1244!
> invalid operand:
> CPU:0
> EIP:0010:[]
> EFLAGS: 00010082
> eax: 001b ebx: c18
Gav wrote:
> The first occurrence of this I didn't even notice until i checked my logs.
I have seen the same here, once with ac13 and twice with ac15 so far.
Completely standard hardware, PIII, 440BX motherboard, esssolo1.
--
LarsG
-
To unsubscribe from this list: send the line
Gav wrote:
The first occurrence of this I didn't even notice until i checked my logs.
I have seen the same here, once with ac13 and twice with ac15 so far.
Completely standard hardware, PIII, 440BX motherboard, esssolo1.
--
LarsG
-
To unsubscribe from this list: send the line unsubscribe
Hello,
At Fri, 22 Jun 2001 15:01:43 +,
Gav wrote:
This second one was immediately after rebooting, and hard locked at getty.
kernel BUG at slab.c:1244!
invalid operand:
CPU:0
EIP:0010:[c0126850]
EFLAGS: 00010082
eax: 001b ebx: c187f788 ecx: 0001 edx
The first occurrence of this I didn't even notice until i checked my logs.
kernel BUG at slab.c:1244!
invalid operand:
CPU:0
EIP:0010:[]
EFLAGS: 00010082
eax: 001b ebx: c187f788 ecx: 0001 edx: 2765
esi: d9a5f000 edi: d9a5f9aa ebp: 00012800 esp: d9fcbda4
ds
The first occurrence of this I didn't even notice until i checked my logs.
kernel BUG at slab.c:1244!
invalid operand:
CPU:0
EIP:0010:[c0126850]
EFLAGS: 00010082
eax: 001b ebx: c187f788 ecx: 0001 edx: 2765
esi: d9a5f000 edi: d9a5f9aa ebp: 00012800 esp
I tend to get these after a few days uptime. This one locked X
hard, ping and ssh over net etc still worked ok.
Pretty standard x86 PC hardware.
kernel BUG at slab.c:1244!
invalid operand:
CPU:0
EIP:0010:[]
EFLAGS: 00213082
eax: 001b ebx: cfffc768 ecx: c0217700 edx
I tend to get these after a few days uptime. This one locked X
hard, ping and ssh over net etc still worked ok.
Pretty standard x86 PC hardware.
kernel BUG at slab.c:1244!
invalid operand:
CPU:0
EIP:0010:[c012842f]
EFLAGS: 00213082
eax: 001b ebx: cfffc768 ecx: c0217700
: No such file or directory
Error (expand_objects): cannot stat(/lib/ide-mod.o) for ide-mod
ksymoops: No such file or directory
kernel BUG at slab.c:1200!
invalid operand:
CPU:0
EIP:0010:[]
EFLAGS: 00210082
eax: 001b ebx: c824e000 ecx: 0001 edx: 6518
esi: edi
: No such file or directory
Error (expand_objects): cannot stat(/lib/ide-mod.o) for ide-mod
ksymoops: No such file or directory
kernel BUG at slab.c:1200!
invalid operand:
CPU:0
EIP:0010:[c01280d9]
EFLAGS: 00210082
eax: 001b ebx: c824e000 ecx: 0001 edx: 6518
esi:
... and yesterday my box completely lockups and magic keys didn't work too
for me ... no messages in logs ...
Best regards,
.R.V.
--
_
|-| __ Robert Vojta -= Oo.oO =-
|=| [Ll] IPEX, s.r.o.
"^" `o
PGP signature
... and yesterday my box completely lockups and magic keys didn't work too
for me ... no messages in logs ...
Best regards,
.R.V.
--
_
|-| __ Robert Vojta vojta-at-ipex.cz -= Oo.oO =-
|=| [Ll] IPEX, s.r.o.
^ `o
PGP signature
> What X server ? and also run the trace through ksymoops
It's fresh installation of RH 7.1 (XFree86-4.0.3-5) ...
>>EIP; c0129884<=
Trace; c01b08db
Trace; c01affd7
Trace; c01e4e79
Trace; c0129ddc
Trace; c01adc1c
Trace; c01b0a9b
Trace; c01adf53
Trace; c01adfeb
Trace; c01321bc
Hi,
I download kernel 2.4.5 and -ac6 patches and I see this ... After that I
have black rxvt window on my desktop and I can't remove it in any way.
kernel BUG at slab.c:1244!
invalid operand:
CPU:0
EIP:0010:[]
EFLAGS: 00010082
eax: 001b ebx: c1103768 ecx: 0001 edx
Hi,
I download kernel 2.4.5 and -ac6 patches and I see this ... After that I
have black rxvt window on my desktop and I can't remove it in any way.
kernel BUG at slab.c:1244!
invalid operand:
CPU:0
EIP:0010:[c0129884]
EFLAGS: 00010082
eax: 001b ebx: c1103768 ecx: 0001
What X server ? and also run the trace through ksymoops
It's fresh installation of RH 7.1 (XFree86-4.0.3-5) ...
EIP; c0129884 try_to_swap_out+174/1d0 =
Trace; c01b08db skb_checksum+3b/220
Trace; c01affd7 pskb_copy+167/170
Trace; c01e4e79 netlink_create+59/d0
Trace; c0129ddc
Keith Owens wrote:
>
> On Wed, 21 Mar 2001 23:15:14 -0800,
> Greg Billock <[EMAIL PROTECTED]> wrote:
> >Summary: Hotplugging a USB device causes an unrecoverable kernel Aiee!
> >
> >Copied from screen after interrupt handler killed, so sorry for
> >incompleteness. This
> >bug is reproducable so
On Wed, 21 Mar 2001 23:15:14 -0800,
Greg Billock <[EMAIL PROTECTED]> wrote:
>Summary: Hotplugging a USB device causes an unrecoverable kernel Aiee!
>
>Copied from screen after interrupt handler killed, so sorry for
>incompleteness. This
>bug is reproducable so if necessary, I can try it
Summary: Hotplugging a USB device causes an unrecoverable kernel Aiee!
Copied from screen after interrupt handler killed, so sorry for
incompleteness. This
bug is reproducable so if necessary, I can try it again
kernel BUG at slab.c:1402!
invalid operand:
CPU: 0
EIP: 0010: []
EFLAGS
Summary: Hotplugging a USB device causes an unrecoverable kernel Aiee!
Copied from screen after interrupt handler killed, so sorry for
incompleteness. This
bug is reproducable so if necessary, I can try it again
kernel BUG at slab.c:1402!
invalid operand:
CPU: 0
EIP: 0010: [c012ddb4
On Wed, 21 Mar 2001 23:15:14 -0800,
Greg Billock [EMAIL PROTECTED] wrote:
Summary: Hotplugging a USB device causes an unrecoverable kernel Aiee!
Copied from screen after interrupt handler killed, so sorry for
incompleteness. This
bug is reproducable so if necessary, I can try it again
The
Keith Owens wrote:
On Wed, 21 Mar 2001 23:15:14 -0800,
Greg Billock [EMAIL PROTECTED] wrote:
Summary: Hotplugging a USB device causes an unrecoverable kernel Aiee!
Copied from screen after interrupt handler killed, so sorry for
incompleteness. This
bug is reproducable so if necessary, I
Tim Fletcher writes:
> What ever a none privilaged user space apps does witness:
>
> root@localhost# dd if=/dev/random of=/dev/mem
If you can do that as a non-priviledged user, then you've got bigger
security problems than that.
/dev/mem should NOT be read/writable by anyone other than root.
Tim Fletcher writes:
What ever a none privilaged user space apps does witness:
root@localhost# dd if=/dev/random of=/dev/mem
If you can do that as a non-priviledged user, then you've got bigger
security problems than that.
/dev/mem should NOT be read/writable by anyone other than root. Its
> I sent the below patch to Linus earlier today. I didn't copy
> any mailing list because it's a bit security-related. Oh well.
Its been in -ac for while but using a define since its a constant
so it not a secret 8)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> > > kernel BUG at slab.c:1542!
>
> The kernel should never oops, no matter what user space does to it.
What ever a none privilaged user space apps does witness:
root@localhost# dd if=/dev/random of=/dev/mem
--
Tim Fletcher - Network manager .~.
> The kernel appears to run fine with this bug() removed.
>
> BTW- gimp and a few other apps also manage to trigger it..
You can add sane with an advansys scsi card and various scsi scanners to
that list
--
Tim Fletcher - Network manager .~.
/V\ L
86 mailing list. There
> > is a fix in the works (depends on the TrueType fonts your using).
>
> A BUG is a BUG:
>
> > > kernel BUG at slab.c:1542!
>
> The kernel should never oops, no matter what user space does to it.
>
> --
> Daniel
-
To unsubscribe f
Daniel Phillips wrote:
>
> I don't know much about the history of this bug but it's quite clear
> it's deliberately inserted:
>
> void * kmalloc (size_t size, int flags)
>
> BUG(); // too big size
> return NULL;
>
I sent the below patch
t; is a fix in the works (depends on the TrueType fonts your using).
> >
> > A BUG is a BUG:
> >
> > > > kernel BUG at slab.c:1542!
> >
> > The kernel should never oops, no matter what user space does to it.
>
> The kernel appears to run fine with this bug
e fonts your using).
>
> A BUG is a BUG:
>
> > > kernel BUG at slab.c:1542!
>
> The kernel should never oops, no matter what user space does to it.
The kernel appears to run fine with this bug() removed.
BTW- gimp and a few other apps also manage to trigger it..
-
To
Shawn Starr wrote:
> This is not a kernel bug, This is a bug in the XFree86 TrueType rendering
> extention. This has been discussed on the Xpert XFree86 mailing list. There
> is a fix in the works (depends on the TrueType fonts your using).
A BUG is a BUG:
> > kernel BUG
Shawn Starr wrote:
This is not a kernel bug, This is a bug in the XFree86 TrueType rendering
extention. This has been discussed on the Xpert XFree86 mailing list. There
is a fix in the works (depends on the TrueType fonts your using).
A BUG is a BUG:
kernel BUG at slab.c:1542!
The kernel
is a BUG:
kernel BUG at slab.c:1542!
The kernel should never oops, no matter what user space does to it.
The kernel appears to run fine with this bug() removed.
BTW- gimp and a few other apps also manage to trigger it..
-
To unsubscribe from this list: send the line "unsubscribe
fonts your using).
A BUG is a BUG:
kernel BUG at slab.c:1542!
The kernel should never oops, no matter what user space does to it.
The kernel appears to run fine with this bug() removed.
I don't know much about the history of this bug but it's quite clear
it's deliberately inserted
Daniel Phillips wrote:
I don't know much about the history of this bug but it's quite clear
it's deliberately inserted:
void * kmalloc (size_t size, int flags)
if allocation succeeds, exit
BUG(); // too big size
return NULL;
I
. There
is a fix in the works (depends on the TrueType fonts your using).
A BUG is a BUG:
kernel BUG at slab.c:1542!
The kernel should never oops, no matter what user space does to it.
--
Daniel
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of
kernel BUG at slab.c:1542!
The kernel should never oops, no matter what user space does to it.
What ever a none privilaged user space apps does witness:
root@localhost# dd if=/dev/random of=/dev/mem
--
Tim Fletcher - Network manager .~.
/V\ L
The kernel appears to run fine with this bug() removed.
BTW- gimp and a few other apps also manage to trigger it..
You can add sane with an advansys scsi card and various scsi scanners to
that list
--
Tim Fletcher - Network manager .~.
/V\ L I
I sent the below patch to Linus earlier today. I didn't copy
any mailing list because it's a bit security-related. Oh well.
Its been in -ac for while but using a define since its a constant
so it not a secret 8)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
If it makes the kernel do Bad Things, the kernel needs to be fixed.
-d
Shawn Starr wrote:
> This is not a kernel bug, This is a bug in the XFree86 TrueType rendering
> extention. This has been discussed on the Xpert XFree86 mailing list. There
> is a fix in the works (depends on the TrueType
gt; Code; c012c063
>d: 5epop%esi
> Code; c012c064
>e: 5f pop%edi
> Code; c012c065
>f: 5dpop%ebp
> Code; c012c066
> 10: 83 c4 0c add$0xc,%esp
&g
ebp
Code; c012c066
10: 83 c4 0c add$0xc,%esp
Code; c012c069
13: c3ret
1 warning issued. Results may not be reliable.
kernel BUG at slab.c:1542!
invalid operand:
CPU:1
EIP:0010:[kmalloc+274/296]
EFLAGS: 00010292
eax: 0
add$0xc,%esp
Code; c012c069 kmalloc+125/128
13: c3ret
1 warning issued. Results may not be reliable.
kernel BUG at slab.c:1542!
invalid operand:
CPU:1
EIP:0010:[kmalloc+274/296]
EFLAGS: 00010292
eax: 001b ebx: c27cc680 ecx: 0008
Code; c012c065 kmalloc+121/128
f: 5dpop%ebp
Code; c012c066 kmalloc+122/128
10: 83 c4 0c add$0xc,%esp
Code; c012c069 kmalloc+125/128
13: c3ret
1 warning issued. Results may not be reliable.
kernel BUG
If it makes the kernel do Bad Things, the kernel needs to be fixed.
-d
Shawn Starr wrote:
This is not a kernel bug, This is a bug in the XFree86 TrueType rendering
extention. This has been discussed on the Xpert XFree86 mailing list. There
is a fix in the works (depends on the TrueType
On Wed, 17 Jan 2001, Rick Richardson wrote:
> Problem: kmalloc() of 4M causes kernel message "kernel BUG at slab.c:1542"
This BUG() has been been removed in the later -ac patches as it was meant
to be a temporary debugging help during the -test3 slab.c changes. This
does not h
** Reply to message from Brian Pomerantz <[EMAIL PROTECTED]> on Wed, 17
Jan 2001 12:17:19 -0800
> The most you can kmalloc() is 128KB unless this has changed in the 2.4
> kernel which I doubt. If you want a region of memory that large, use
> vmalloc(). Of course, this doesn't guarantee a
On Wed, Jan 17, 2001 at 01:54:20PM -0600, Rick Richardson wrote:
>
> [please cc me on any responses]
>
> Environment: 2.4.0 released, Pentium III with 256MB's of RAM.
> Problem: kmalloc() of 4M causes kernel message "kernel BUG at slab.c:1542"
>
The most you c
[please cc me on any responses]
Environment: 2.4.0 released, Pentium III with 256MB's of RAM.
Problem: kmalloc() of 4M causes kernel message "kernel BUG at slab.c:1542"
Here is the dmesg output:
kernel BUG at slab.c:1542!
invalid operand:
CPU:0
EIP:0010
[please cc me on any responses]
Environment: 2.4.0 released, Pentium III with 256MB's of RAM.
Problem: kmalloc() of 4M causes kernel message "kernel BUG at slab.c:1542"
Here is the dmesg output:
kernel BUG at slab.c:1542!
invalid operand:
CPU:0
EIP:0010:[c0129b
On Wed, Jan 17, 2001 at 01:54:20PM -0600, Rick Richardson wrote:
[please cc me on any responses]
Environment: 2.4.0 released, Pentium III with 256MB's of RAM.
Problem: kmalloc() of 4M causes kernel message "kernel BUG at slab.c:1542"
The most you can kmalloc() is 128KB unles
** Reply to message from Brian Pomerantz [EMAIL PROTECTED] on Wed, 17
Jan 2001 12:17:19 -0800
The most you can kmalloc() is 128KB unless this has changed in the 2.4
kernel which I doubt. If you want a region of memory that large, use
vmalloc(). Of course, this doesn't guarantee a
On Wed, 17 Jan 2001, Rick Richardson wrote:
Problem: kmalloc() of 4M causes kernel message "kernel BUG at slab.c:1542"
This BUG() has been been removed in the later -ac patches as it was meant
to be a temporary debugging help during the -test3 slab.c changes. This
does not howe
I'd guess this is because of a bug that crept into test9,
where a TD is now leaked ... you can get rid of the slab
BUG warning by commenting out the line at the top of
drivers/usb/usb-ohci.c that #defines OHCI_MEM_SLAB.
That TD leak prevents the kmem_cache from getting freed,
and hence prevents
I'd guess this is because of a bug that crept into test9,
where a TD is now leaked ... you can get rid of the slab
BUG warning by commenting out the line at the top of
drivers/usb/usb-ohci.c that #defines OHCI_MEM_SLAB.
That TD leak prevents the kmem_cache from getting freed,
and hence prevents
ristian kernel: usb.c: USB bus 2 deregistered
christian> kmem_cache_destroy: Can't free all objects c116a890
christian> : usb-ohci.h: td_cache remained
christian> kernel BUG at slab.c:804!
christian> invalid operand:
christian> CPU:0
christian> EIP:0010:[]
ch
On Thu, 26 Oct 2000 15:39:59 +0200 (CEST),
Christian Reiser <[EMAIL PROTECTED]> wrote:
> kernel BUG at slab.c:804!
>Code: 0f 0b 83 c4 0c 8d b4 26 00 00 00 00 8b 1b 81 fb bc 23 26 c0
>... hope it could help ...
Almost completely useless until you follow the procedures in
linux
:00 christian kernel: usb.c: kusbd: /sbin/hotplug remove 2
Oct 26 15:11:00 christian kernel: usb.c: USB bus 2 deregistered
kmem_cache_destroy: Can't free all objects c116a890
: usb-ohci.h: td_cache remained
kernel BUG at slab.c:804!
invalid operand:
CPU:0
EIP:0010
:00 christian kernel: usb.c: kusbd: /sbin/hotplug remove 2
Oct 26 15:11:00 christian kernel: usb.c: USB bus 2 deregistered
kmem_cache_destroy: Can't free all objects c116a890
: usb-ohci.h: td_cache remained
kernel BUG at slab.c:804!
invalid operand:
CPU:0
EIP:0010
On Thu, 26 Oct 2000 15:39:59 +0200 (CEST),
Christian Reiser [EMAIL PROTECTED] wrote:
kernel BUG at slab.c:804!
Code: 0f 0b 83 c4 0c 8d b4 26 00 00 00 00 8b 1b 81 fb bc 23 26 c0
... hope it could help ...
Almost completely useless until you follow the procedures in
linux/REPORTING-BUGS
roy: Can't free all objects c116a890
christian : usb-ohci.h: td_cache remained
christian kernel BUG at slab.c:804!
christian invalid operand:
christian CPU:0
christian EIP:0010:[c0125974]
christian EFLAGS: 00010282
christian eax: 001a ebx: c116a8ec ecx
76 matches
Mail list logo
