00:00.0 Host bridge: Intel Corp. 82830 830 Chipset Host Bridge (rev 04)
Subsystem: Intel Corp.: Unknown device 1969
Flags: bus master, fast devsel, latency 0
Memory at <unassigned> (32-bit, prefetchable)
Capabilities: [40] #09 [2105]
00:02.0 VGA compatible controller: Intel Corp. 82830 CGC [Chipset Graphics Controller] (rev 04) (prog-if 00 [VGA])
Subsystem: Hewlett-Packard Company: Unknown device 0021
Flags: bus master, fast devsel, latency 0, IRQ 9
Memory at e8000000 (32-bit, prefetchable) [size=128M]
Memory at e0000000 (32-bit, non-prefetchable) [size=512K]
Capabilities: [d0] Power Management version 1
00:02.1 Display controller: Intel Corp. 82830 CGC [Chipset Graphics Controller]
Subsystem: Hewlett-Packard Company: Unknown device 0021
Flags: bus master, fast devsel, latency 0
Memory at f0000000 (32-bit, prefetchable) [size=128M]
Memory at e0080000 (32-bit, non-prefetchable) [size=512K]
Capabilities: [d0] Power Management version 1
00:1d.0 USB Controller: Intel Corp. 82801CA/CAM USB (Hub #1) (rev 02) (prog-if 00 [UHCI])
Subsystem: Hewlett-Packard Company: Unknown device 0021
Flags: bus master, medium devsel, latency 0, IRQ 9
I/O ports at 1800 [size=32]
00:1d.1 USB Controller: Intel Corp. 82801CA/CAM USB (Hub #2) (rev 02) (prog-if 00 [UHCI])
Subsystem: Hewlett-Packard Company: Unknown device 0021
Flags: bus master, medium devsel, latency 0, IRQ 5
I/O ports at 1820 [size=32]
00:1d.2 USB Controller: Intel Corp. 82801CA/CAM USB (Hub #3) (rev 02) (prog-if 00 [UHCI])
Subsystem: Hewlett-Packard Company: Unknown device 0021
Flags: bus master, medium devsel, latency 0, IRQ 5
I/O ports at 1840 [size=32]
00:1e.0 PCI bridge: Intel Corp. 82801BAM/CAM PCI Bridge (rev 42) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=02, subordinate=02, sec-latency=64
I/O behind bridge: 00002000-00002fff
Memory behind bridge: e0200000-e02fffff
00:1f.0 ISA bridge: Intel Corp. 82801CAM ISA Bridge (LPC) (rev 02)
Flags: bus master, medium devsel, latency 0
00:1f.1 IDE interface: Intel Corp. 82801CAM IDE U100 (rev 02) (prog-if 8a [Master SecP PriP])
Subsystem: Hewlett-Packard Company: Unknown device 0021
Flags: bus master, medium devsel, latency 0, IRQ 5
I/O ports at <ignored>
I/O ports at <ignored>
I/O ports at <ignored>
I/O ports at <ignored>
I/O ports at 1860 [size=16]
Memory at e0100000 (32-bit, non-prefetchable) [size=1K]
00:1f.3 SMBus: Intel Corp. 82801CA/CAM SMBus (rev 02)
Subsystem: Hewlett-Packard Company: Unknown device 0021
Flags: medium devsel, IRQ 9
I/O ports at 1880 [size=32]
02:02.0 Communication controller: ESS Technology ES2838/2839 SuperLink Modem (rev 01)
Subsystem: Hewlett-Packard Company: Unknown device 0020
Flags: fast devsel, IRQ 5
I/O ports at 2440 [size=16]
Capabilities: [c0] Power Management version 2
02:03.0 Multimedia audio controller: ESS Technology ES1988 Allegro-1 (rev 12)
Subsystem: Hewlett-Packard Company: Unknown device 0021
Flags: bus master, medium devsel, latency 64, IRQ 5
I/O ports at 2000 [size=256]
Capabilities: [c0] Power Management version 2
02:04.0 CardBus bridge: O2 Micro, Inc. OZ6933 Cardbus Controller (rev 01)
Subsystem: Hewlett-Packard Company: Unknown device 0021
Flags: stepping, slow devsel, IRQ 9
Memory at 10000000 (32-bit, non-prefetchable) [disabled] [size=4K]
Bus: primary=02, secondary=03, subordinate=06, sec-latency=176
I/O window 0: 00000000-00000003
I/O window 1: 00000000-00000003
16-bit legacy interface ports at 0001
02:04.1 CardBus bridge: O2 Micro, Inc. OZ6933 Cardbus Controller (rev 01)
Subsystem: Hewlett-Packard Company: Unknown device 0021
Flags: stepping, slow devsel, IRQ 9
Memory at 10001000 (32-bit, non-prefetchable) [disabled] [size=4K]
Bus: primary=02, secondary=07, subordinate=0a, sec-latency=176
I/O window 0: 00000000-00000003
I/O window 1: 00000000-00000003
16-bit legacy interface ports at 0001
02:08.0 Ethernet controller: Intel Corp. 82801CAM (ICH3) PRO/100 VE (LOM) Ethernet Controller (rev 42)
Subsystem: Hewlett-Packard Company: Unknown device 0021
Flags: bus master, medium devsel, latency 66, IRQ 10
Memory at e0200000 (32-bit, non-prefetchable) [size=4K]
I/O ports at 2400 [size=64]
Capabilities: [dc] Power Management version 2
Stefano Rivoir wrote:
>
> I'm experiencing hard rand lockups using kernel 2.6.0: they are not
[...]
Forgot to say that I use KDE, so it may have something to do with it,
but I use the same KDE in my PC at home, where NO HANG occur...
--
Stefano RIVOIR
GTS Srl
I use GNOME and has hanged once since I have installed 2.6.0t2 a
couple of days ago.
On Wed, 30 Jul 2003, Stefano Rivoir wrote:
> Stefano Rivoir wrote:
>
> >
> > I'm experiencing hard rand lockups using kernel 2.6.0: they are not
> [...]
>
> Forgot to say that I use KDE, so it may have something to do with it,
> but I use the same KDE in my PC at home, where NO HANG occur...
>
>
>
--
Behdad Esfahbod 8 Mordad 1382, 2003 Jul 30
http://behdad.org/ [Finger for Geek Code]
If you do a job too well, you'll get stuck with it.
On Wednesday 30 Jul 2003 09:27, Stefano Rivoir wrote:
> I'm experiencing hard rand lockups using kernel 2.6.0: they are not
> predictable, nor I can find a way to reproduce them. They can occur
> while working with an app, while browsing the fs (I use KDE) or
> while resuming after the screensaver, or anything else. They can
> occur after one hour or 15 minutes, and there's not any strange
> "jerkiness" activity before, nor an intense disk work.
>
> After the hang, the disk starts working for a while, then I have
> to reset w/button, and nothing is left on the various system logs.
What makes you think this is a hang? Does the disc activity stop? If you
press the caps lock or num lock keys does the LED light up? What I'm asking
is could it have been swapping for some reason? I've had the system go
unresponsive on me quite recently, also when running KDE. It easilly took a
two or more minutes to start responding again. The disc light stayed active
all the time it wasn't responding.
--
Ian.
Stefano Rivoir wrote:
>
> I'm experiencing hard rand lockups using kernel 2.6.0: they are not
> predictable, nor I can find a way to reproduce them. They can occur
> while working with an app, while browsing the fs (I use KDE) or
> while resuming after the screensaver, or anything else. They can
> occur after one hour or 15 minutes, and there's not any strange
> "jerkiness" activity before, nor an intense disk work.
>
> After the hang, the disk starts working for a while, then I have
> to reset w/button, and nothing is left on the various system logs.
>
> These hangs did not occur in 2.5 up to .75, but they come also
> with 2.6.0-mm1 (and plain 2.6.0-t1). I had a doubt about the
> soundcard, I've applied latest 0.9.6 alsa patch: the hangs are less
> frequent but still there.
Can you reproduce these hangs without the AGP and DRI modules loaded?
Thanks,
Rahul
--
Rahul Karnik
[email protected]
<quote sender="Rahul Karnik">
> Stefano Rivoir wrote:
> >I'm experiencing hard rand lockups using kernel 2.6.0: they are not
> >predictable, nor I can find a way to reproduce them. They can occur
> >while working with an app, while browsing the fs (I use KDE) or
> >while resuming after the screensaver, or anything else. They can
> >occur after one hour or 15 minutes, and there's not any strange
> >"jerkiness" activity before, nor an intense disk work.
> >
> >After the hang, the disk starts working for a while, then I have
> >to reset w/button, and nothing is left on the various system logs.
> >
> >These hangs did not occur in 2.5 up to .75, but they come also
> >with 2.6.0-mm1 (and plain 2.6.0-t1). I had a doubt about the
> >soundcard, I've applied latest 0.9.6 alsa patch: the hangs are less
> >frequent but still there.
>
> Can you reproduce these hangs without the AGP and DRI modules loaded?
I am encountering the same with 2.6.0-test2 but the
problem is, I patched it with a number of patches that
I am unable to determine which patches/changes causes
the random lockups. Actually I am suspecting it's O11.2int
because I wasn't having any problems with it prior to
this patch. will keep you guys updated.
Eugene
>
> Thanks,
> Rahul
> --
> Rahul Karnik
> [email protected]
>
> -
> 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/
On Thu, 31 Jul 2003 10:13, Eugene Teo wrote:
> <quote sender="Rahul Karnik">
>
> > Stefano Rivoir wrote:
> > >I'm experiencing hard rand lockups using kernel 2.6.0: they are not
> > >predictable, nor I can find a way to reproduce them. They can occur
> > >while working with an app, while browsing the fs (I use KDE) or
> > >while resuming after the screensaver, or anything else. They can
> > >occur after one hour or 15 minutes, and there's not any strange
> > >"jerkiness" activity before, nor an intense disk work.
> > >
> > >After the hang, the disk starts working for a while, then I have
> > >to reset w/button, and nothing is left on the various system logs.
> > >
> > >These hangs did not occur in 2.5 up to .75, but they come also
> > >with 2.6.0-mm1 (and plain 2.6.0-t1). I had a doubt about the
> > >soundcard, I've applied latest 0.9.6 alsa patch: the hangs are less
> > >frequent but still there.
> >
> > Can you reproduce these hangs without the AGP and DRI modules loaded?
>
> I am encountering the same with 2.6.0-test2 but the
> problem is, I patched it with a number of patches that
> I am unable to determine which patches/changes causes
> the random lockups. Actually I am suspecting it's O11.2int
> because I wasn't having any problems with it prior to
> this patch. will keep you guys updated.
O11.2 backs out changes to bring them back to the default, so it can't be that
specific patch. Also the original contributor describes the hangs with plain
2.6.0-t1 which includes none of my patches.
Con
<quote sender="Con Kolivas">
> On Thu, 31 Jul 2003 10:13, Eugene Teo wrote:
> > <quote sender="Rahul Karnik">
> >
> > > Stefano Rivoir wrote:
> > > >I'm experiencing hard rand lockups using kernel 2.6.0: they are not
> > > >predictable, nor I can find a way to reproduce them. They can occur
> > > >while working with an app, while browsing the fs (I use KDE) or
> > > >while resuming after the screensaver, or anything else. They can
> > > >occur after one hour or 15 minutes, and there's not any strange
> > > >"jerkiness" activity before, nor an intense disk work.
> > > >
> > > >After the hang, the disk starts working for a while, then I have
> > > >to reset w/button, and nothing is left on the various system logs.
> > > >
> > > >These hangs did not occur in 2.5 up to .75, but they come also
> > > >with 2.6.0-mm1 (and plain 2.6.0-t1). I had a doubt about the
> > > >soundcard, I've applied latest 0.9.6 alsa patch: the hangs are less
> > > >frequent but still there.
> > >
> > > Can you reproduce these hangs without the AGP and DRI modules loaded?
> >
> > I am encountering the same with 2.6.0-test2 but the
> > problem is, I patched it with a number of patches that
> > I am unable to determine which patches/changes causes
> > the random lockups. Actually I am suspecting it's O11.2int
> > because I wasn't having any problems with it prior to
> > this patch. will keep you guys updated.
>
> O11.2 backs out changes to bring them back to the default, so it can't be that
> specific patch. Also the original contributor describes the hangs with plain
> 2.6.0-t1 which includes none of my patches.
I shall keep you guys updated.
> Con
>
> -
> 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/
Ian Hastie wrote:
> On Wednesday 30 Jul 2003 09:27, Stefano Rivoir wrote:
>
>
> What makes you think this is a hang? Does the disc activity stop? If you
> press the caps lock or num lock keys does the LED light up? What I'm asking
> is could it have been swapping for some reason? I've had the system go
> unresponsive on me quite recently, also when running KDE. It easilly took a
> two or more minutes to start responding again. The disc light stayed active
> all the time it wasn't responding.
No, it hangs. No cursor movement, no keyboard reaction, no ping on eth0,
no disc activity except for 3/4 seconds following. I left it like that
10/15 minutes then I had to power it off...
--
Stefano RIVOIR
GTS Srl
On Thu, 31 Jul 2003 09:11:32 +0200, Stefano Rivoir wrote:
>Ian Hastie wrote:
>> On Wednesday 30 Jul 2003 09:27, Stefano Rivoir wrote:
>>
>
>>
>> What makes you think this is a hang? Does the disc activity stop?
>If you > press the caps lock or num lock keys does the LED light up?
>What I'm asking > is could it have been swapping for some reason? I've
>had the system go > unresponsive on me quite recently, also when
>running KDE. It easilly took a > two or more minutes to start
>responding again. The disc light stayed active > all the time it
>wasn't responding.
>
>No, it hangs. No cursor movement, no keyboard reaction, no ping on
>eth0, no disc activity except for 3/4 seconds following. I left it like
>that 10/15 minutes then I had to power it off...
I have similar symptom when the freeze happen. No disk activity, no
mouse, no keyboard, the open sessions ssh not to respond, no ping, etc.
Until this moment, I happen to me only once, but it takes advantage of
east message to comment to them of the experience.
In any case if experiment these freeze, I return to them to communicate
of the problem, and in any case I test some parameter of starting
or options of compilation that you they recommend to me.
About other beta versions of kernel I cannot comment to them because
not them probe. 2.6.0-test1 probe just a short time.
Lamentably it is not left anything registered in logs, only combinacion
of keys that responds is sysrq-reboot.
sysrq-sync and sysrq-umount not respond (no disk activity).
Running: kernel compilation (over ext3) ,
X 4.3 (DRI no in use), KDE,Mozilla(downloading file over xfs)
,Sylpheed,Xchat, and in the reiser fs partition no activitie.
When reboot fsck deleted orphaned entrys from /tmp (ext3) and no others
problems in others filesystems.
My .config, dmesg and lspci.
http://www.vmlinuz.com.ar/slackware/kernel.config.djgera/config-2.6.0-test2
http://www.vmlinuz.com.ar/slackware/info-hard/dmesg-2.6.0-test2-djgera
http://www.vmlinuz.com.ar/slackware/info-hard/lspci-2.6.0-test2-djgera
(sorry my english)
--
Gerardo Exequiel Pozzi ( djgera )
http://www.vmlinuz.com.ar http://www.djgera.com.ar
KeyID: 0x1B8C330D
Key fingerprint = 0CAA D5D4 CD85 4434 A219 76ED 39AB 221B 1B8C 330D
One thing strange though.
root tty1 Thu Jul 31 07:32 - 07:32 (00:00)
reboot system boot 2.6.0-test2-mm1- Thu Jul 31 07:31 (02:58)
amnesia pts/0 :0.0 Thu Jul 31 01:08 - crash (06:23)
It seems that I can still receive emails when the box freezed.
As we can see, I didn't logoff for 6+ hours... but i can't ping,
can't ssh, can't revive the box.
Eugene
<quote sender="Gerardo Exequiel Pozzi">
> On Thu, 31 Jul 2003 09:11:32 +0200, Stefano Rivoir wrote:
> >Ian Hastie wrote:
> >> On Wednesday 30 Jul 2003 09:27, Stefano Rivoir wrote:
> >>
> >
> >>
> >> What makes you think this is a hang? Does the disc activity stop?
> >If you > press the caps lock or num lock keys does the LED light up?
> >What I'm asking > is could it have been swapping for some reason? I've
> >had the system go > unresponsive on me quite recently, also when
> >running KDE. It easilly took a > two or more minutes to start
> >responding again. The disc light stayed active > all the time it
> >wasn't responding.
> >
> >No, it hangs. No cursor movement, no keyboard reaction, no ping on
> >eth0, no disc activity except for 3/4 seconds following. I left it like
> >that 10/15 minutes then I had to power it off...
>
> I have similar symptom when the freeze happen. No disk activity, no
> mouse, no keyboard, the open sessions ssh not to respond, no ping, etc.
> Until this moment, I happen to me only once, but it takes advantage of
> east message to comment to them of the experience.
> In any case if experiment these freeze, I return to them to communicate
> of the problem, and in any case I test some parameter of starting
> or options of compilation that you they recommend to me.
>
> About other beta versions of kernel I cannot comment to them because
> not them probe. 2.6.0-test1 probe just a short time.
>
> Lamentably it is not left anything registered in logs, only combinacion
> of keys that responds is sysrq-reboot.
> sysrq-sync and sysrq-umount not respond (no disk activity).
>
> Running: kernel compilation (over ext3) ,
> X 4.3 (DRI no in use), KDE,Mozilla(downloading file over xfs)
> ,Sylpheed,Xchat, and in the reiser fs partition no activitie.
>
> When reboot fsck deleted orphaned entrys from /tmp (ext3) and no others
> problems in others filesystems.
>
>
> My .config, dmesg and lspci.
> http://www.vmlinuz.com.ar/slackware/kernel.config.djgera/config-2.6.0-test2
> http://www.vmlinuz.com.ar/slackware/info-hard/dmesg-2.6.0-test2-djgera
> http://www.vmlinuz.com.ar/slackware/info-hard/lspci-2.6.0-test2-djgera
>
>
> (sorry my english)
> --
> Gerardo Exequiel Pozzi ( djgera )
> http://www.vmlinuz.com.ar http://www.djgera.com.ar
> KeyID: 0x1B8C330D
> Key fingerprint = 0CAA D5D4 CD85 4434 A219 76ED 39AB 221B 1B8C 330D
> -
> 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/
>
Eugene Teo wrote:
> One thing strange though.
[...]
Ok, I think I've found. It was very probably an old version of the
synaptics module for X4.3 (it was ...p3). With the new driver,
and with DRI too (along with test2-mm2 patch), it seems to be OK.
At least, I've seen no hangs so far.
Bye
--
Stefano RIVOIR
GTS Srl
<quote sender="Stefano Rivoir">
> Eugene Teo wrote:
>
> >One thing strange though.
>
> [...]
>
> Ok, I think I've found. It was very probably an old version of the
> synaptics module for X4.3 (it was ...p3). With the new driver,
> and with DRI too (along with test2-mm2 patch), it seems to be OK.
> At least, I've seen no hangs so far.
Hmm, can you explain the synaptics module? i experienced a hang again
last night. about 5-6 hours of no activities, and i can't get my box
back up again except with a hard reboot.
Eugene
>
> Bye
>
> --
> Stefano RIVOIR
> GTS Srl
>
>
>
>
Hi everyone,
I think I discovered something interesting that might be some hints
as to why I am getting random hangs. I am using 2.2.20 (default debian
kernel atm), and I have not encounter any random hangs as yet (which
is fortunate... at least i know it is not hardware problem).
Was using 2.6.0-test2-mm2-kj1. I encountered the same hang problem when
I reverted back to 2.6.0-test1-mm2-kj1.
Please comment, and look into it......
======================================================================
This was last night (after I go to bed):
Aug 1 03:20:06 amaryllis kernel: Slab corruption: start=d40055f0, expend=d400566f, problemat=d40055f0
Aug 1 03:20:06 amaryllis kernel: Last user: [reap_timer_fnc+530/1208](reap_timer_fnc+0x212/0x4b8)
Aug 1 03:20:06 amaryllis kernel: Data: 6A 6A *******6A ******6A 2A ******6A 6A ******6A 2A ******6A 2A ******6A 6A ******6A 6A ******6A 2A ******6A *******6A 6A ******6A
********6A *******6A *******6A *******6A *****A5
Aug 1 03:20:06 amaryllis kernel: Next: 61 E0 2C .4B 7B 15 C0 A5 C2 0F 17 08 57 00 D4 50 3A 30 D5 00 00 00 00 00 30 8F CF 01 00 00 00
Aug 1 03:20:06 amaryllis kernel: slab error in check_poison_obj(): cache `size-128': object was modified after freeing
Aug 1 03:20:06 amaryllis kernel: Call Trace:
Aug 1 03:20:06 amaryllis kernel: [check_poison_obj+362/426] check_poison_obj+0x16a/0x1aa
Aug 1 03:20:06 amaryllis kernel: [kmem_cache_alloc+136/425] kmem_cache_alloc+0x88/0x1a9
Aug 1 03:20:06 amaryllis kernel: [cache_grow+1032/1196] cache_grow+0x408/0x4ac
Aug 1 03:20:06 amaryllis kernel: [cache_grow+1032/1196] cache_grow+0x408/0x4ac
Aug 1 03:20:06 amaryllis kernel: [cache_alloc_refill+780/1221] cache_alloc_refill+0x30c/0x4c5
Aug 1 03:20:06 amaryllis kernel: [kmem_cache_alloc+393/425] kmem_cache_alloc+0x189/0x1a9
Aug 1 03:20:06 amaryllis kernel: [pgd_alloc+27/31] pgd_alloc+0x1b/0x1f
Aug 1 03:20:06 amaryllis kernel: [mm_init+467/533] mm_init+0x1d3/0x215
Aug 1 03:20:06 amaryllis kernel: [copy_mm+314/1776] copy_mm+0x13a/0x6f0
Aug 1 03:20:06 amaryllis kernel: [copy_mm+348/1776] copy_mm+0x15c/0x6f0
Aug 1 03:20:06 amaryllis kernel: [check_poison_obj+82/426] check_poison_obj+0x52/0x1aa
Aug 1 03:20:06 amaryllis kernel: [kmem_cache_alloc+156/425] kmem_cache_alloc+0x9c/0x1a9
Aug 1 03:20:06 amaryllis kernel: [copy_process+1372/4275] copy_process+0x55c/0x10b3
Aug 1 03:20:06 amaryllis kernel: [d_alloc+30/898] d_alloc+0x1e/0x382
Aug 1 03:20:06 amaryllis kernel: [do_fork+77/445] do_fork+0x4d/0x1bd
Aug 1 03:20:06 amaryllis kernel: [sys_wait4+423/578] sys_wait4+0x1a7/0x242
Aug 1 03:20:06 amaryllis kernel: [default_wake_function+0/46] default_wake_function+0x0/0x2e
Aug 1 03:20:06 amaryllis kernel: [sys_fork+56/60] sys_fork+0x38/0x3c
Aug 1 03:20:06 amaryllis kernel: [syscall_call+7/11] syscall_call+0x7/0xb
Aug 1 03:20:06 amaryllis kernel:
Aug 1 03:20:06 amaryllis kernel: slab error in cache_alloc_debugcheck_after(): cache `size-128': memory after object was overwritten
Aug 1 03:20:06 amaryllis kernel: Call Trace:
Aug 1 03:20:06 amaryllis kernel: [kmem_cache_alloc+261/425] kmem_cache_alloc+0x105/0x1a9
Aug 1 03:20:06 amaryllis kernel: [cache_grow+1032/1196] cache_grow+0x408/0x4ac
Aug 1 03:20:06 amaryllis kernel: [cache_grow+1032/1196] cache_grow+0x408/0x4ac
Aug 1 03:20:06 amaryllis kernel: [cache_alloc_refill+780/1221] cache_alloc_refill+0x30c/0x4c5
Aug 1 03:20:06 amaryllis kernel: [kmem_cache_alloc+393/425] kmem_cache_alloc+0x189/0x1a9
Aug 1 03:20:06 amaryllis kernel: [pgd_alloc+27/31] pgd_alloc+0x1b/0x1f
Aug 1 03:20:06 amaryllis kernel: [mm_init+467/533] mm_init+0x1d3/0x215
Aug 1 03:20:06 amaryllis kernel: [copy_mm+314/1776] copy_mm+0x13a/0x6f0
Aug 1 03:20:06 amaryllis kernel: [copy_mm+348/1776] copy_mm+0x15c/0x6f0
Aug 1 03:20:06 amaryllis kernel: [check_poison_obj+82/426] check_poison_obj+0x52/0x1aa
Aug 1 03:20:06 amaryllis kernel: [kmem_cache_alloc+156/425] kmem_cache_alloc+0x9c/0x1a9
Aug 1 03:20:06 amaryllis kernel: Slab corruption: start=d4005564, expend=d40055e3, problemat=d4005569
Aug 1 03:20:06 amaryllis kernel: Last user: [do_page_cache_readahead+262/1011](do_page_cache_readahead+0x106/0x3f3)
Aug 1 03:20:06 amaryllis kernel: Data: *****6A ******6A 6A ******6A 6A ******6A 6A ******6A 6A ******6A 6A ******6A 6A ******6A *******2A *******6A 2A *******6A ******2A
6A ******6A 6A ******6A *******6A ********6A *A5
Aug 1 03:20:06 amaryllis kernel: Next: 71 F0 2C .4A 3A 15 C0 A5 C2 0F 17 ....................
Aug 1 03:20:06 amaryllis kernel: slab error in check_poison_obj(): cache `size-128': object was modified after freeing
Aug 1 03:20:06 amaryllis kernel: Call Trace:
Aug 1 03:20:06 amaryllis kernel: [check_poison_obj+362/426] check_poison_obj+0x16a/0x1aa
Aug 1 03:20:06 amaryllis kernel: [kmem_cache_alloc+136/425] kmem_cache_alloc+0x88/0x1a9
Aug 1 03:20:06 amaryllis kernel: [cache_grow+1032/1196] cache_grow+0x408/0x4ac
Aug 1 03:20:06 amaryllis kernel: [cache_grow+1032/1196] cache_grow+0x408/0x4ac
Aug 1 03:20:06 amaryllis kernel: [cache_alloc_refill+780/1221] cache_alloc_refill+0x30c/0x4c5
Aug 1 03:20:06 amaryllis kernel: [kmem_cache_alloc+393/425] kmem_cache_alloc+0x189/0x1a9
Aug 1 03:20:06 amaryllis kernel: [buffered_rmqueue+228/671] buffered_rmqueue+0xe4/0x29f
Aug 1 03:20:06 amaryllis kernel: [radix_tree_node_alloc+32/90] radix_tree_node_alloc+0x20/0x5a
Aug 1 03:20:06 amaryllis kernel: [radix_tree_insert+144/202] radix_tree_insert+0x90/0xca
Aug 1 03:20:06 amaryllis kernel: [__alloc_pages+749/848] __alloc_pages+0x2ed/0x350
Aug 1 03:20:06 amaryllis kernel: [add_to_page_cache+158/507] add_to_page_cache+0x9e/0x1fb
Aug 1 03:20:06 amaryllis kernel: [unlock_page+22/83] unlock_page+0x16/0x53
Aug 1 03:20:06 amaryllis kernel: [generic_file_aio_write_nolock+889/2940] generic_file_aio_write_nolock+0x379/0xb7c
Aug 1 03:20:06 amaryllis kernel: [__kfree_skb+129/246] __kfree_skb+0x81/0xf6
Aug 1 03:20:06 amaryllis kernel: [generic_file_write_nolock+164/189] generic_file_write_nolock+0xa4/0xbd
Aug 1 03:20:06 amaryllis kernel: [buffered_rmqueue+228/671] buffered_rmqueue+0xe4/0x29f
Aug 1 03:20:06 amaryllis kernel: [autoremove_wake_function+0/75] autoremove_wake_function+0x0/0x4b
Aug 1 03:20:06 amaryllis kernel: [sockfd_lookup+26/114] sockfd_lookup+0x1a/0x72
Aug 1 03:20:06 amaryllis kernel: [sys_recvfrom+224/241] sys_recvfrom+0xe0/0xf1
Aug 1 03:20:06 amaryllis kernel: [poll_freewait+58/67] poll_freewait+0x3a/0x43
Aug 1 03:20:06 amaryllis kernel: [generic_file_writev+90/210] generic_file_writev+0x5a/0xd2
Aug 1 03:20:06 amaryllis kernel: [do_readv_writev+512/646] do_readv_writev+0x200/0x286
Aug 1 03:20:06 amaryllis kernel: [do_sync_write+0/244] do_sync_write+0x0/0xf4
Aug 1 03:20:06 amaryllis kernel: [vfs_writev+82/91] vfs_writev+0x52/0x5b
Aug 1 03:20:06 amaryllis kernel: [sys_writev+63/93] sys_writev+0x3f/0x5d
Aug 1 03:20:06 amaryllis kernel: [syscall_call+7/11] syscall_call+0x7/0xb
Aug 1 03:20:06 amaryllis kernel:
Aug 1 03:20:06 amaryllis kernel: slab error in cache_alloc_debugcheck_after(): cache `size-128': memory before object was overwritten
Aug 1 03:20:06 amaryllis kernel: Call Trace:
Aug 1 03:20:06 amaryllis kernel: [kmem_cache_alloc+221/425] kmem_cache_alloc+0xdd/0x1a9
Aug 1 03:20:06 amaryllis kernel: [cache_grow+1032/1196] cache_grow+0x408/0x4ac
Aug 1 03:20:06 amaryllis kernel: [cache_grow+1032/1196] cache_grow+0x408/0x4ac
Aug 1 03:20:06 amaryllis kernel: [cache_alloc_refill+780/1221] cache_alloc_refill+0x30c/0x4c5
Aug 1 03:20:06 amaryllis kernel: [kmem_cache_alloc+393/425] kmem_cache_alloc+0x189/0x1a9
Aug 1 03:20:06 amaryllis kernel: [buffered_rmqueue+228/671] buffered_rmqueue+0xe4/0x29f
Aug 1 03:20:06 amaryllis kernel: [radix_tree_node_alloc+32/90] radix_tree_node_alloc+0x20/0x5a
Aug 1 03:20:06 amaryllis kernel: [radix_tree_insert+144/202] radix_tree_insert+0x90/0xca
Aug 1 03:20:06 amaryllis kernel: [__alloc_pages+749/848] __alloc_pages+0x2ed/0x350
Aug 1 03:20:06 amaryllis kernel: [add_to_page_cache+158/507] add_to_page_cache+0x9e/0x1fb
Aug 1 03:20:06 amaryllis kernel: [unlock_page+22/83] unlock_page+0x16/0x53
Aug 1 03:20:06 amaryllis kernel: [generic_file_aio_write_nolock+889/2940] generic_file_aio_write_nolock+0x379/0xb7c
Aug 1 03:20:06 amaryllis kernel: [__kfree_skb+129/246] __kfree_skb+0x81/0xf6
Aug 1 03:20:06 amaryllis kernel: [generic_file_write_nolock+164/189] generic_file_write_nolock+0xa4/0xbd
Aug 1 03:20:06 amaryllis kernel: [buffered_rmqueue+228/671] buffered_rmqueue+0xe4/0x29f
Aug 1 03:20:06 amaryllis kernel: [autoremove_wake_function+0/75] autoremove_wake_function+0x0/0x4b
Aug 1 03:20:06 amaryllis kernel: [sockfd_lookup+26/114] sockfd_lookup+0x1a/0x72
Aug 1 03:20:06 amaryllis kernel: [sys_recvfrom+224/241] sys_recvfrom+0xe0/0xf1
Aug 1 03:20:06 amaryllis kernel: [poll_freewait+58/67] poll_freewait+0x3a/0x43
Aug 1 03:20:06 amaryllis kernel: [generic_file_writev+90/210] generic_file_writev+0x5a/0xd2
Aug 1 03:20:06 amaryllis kernel: [do_readv_writev+512/646] do_readv_writev+0x200/0x286
Aug 1 03:20:06 amaryllis kernel: [do_sync_write+0/244] do_sync_write+0x0/0xf4
Aug 1 03:20:06 amaryllis kernel: [vfs_writev+82/91] vfs_writev+0x52/0x5b
Aug 1 03:20:06 amaryllis kernel: [sys_writev+63/93] sys_writev+0x3f/0x5d
Aug 1 03:20:06 amaryllis kernel: [syscall_call+7/11] syscall_call+0x7/0xb
Aug 1 03:20:06 amaryllis kernel:
Aug 1 03:20:06 amaryllis kernel: [copy_process+1372/4275] copy_process+0x55c/0x10b3
Aug 1 03:20:06 amaryllis kernel: [d_alloc+30/898] d_alloc+0x1e/0x382
Aug 1 03:20:06 amaryllis kernel: [do_fork+77/445] do_fork+0x4d/0x1bd
Aug 1 03:20:06 amaryllis kernel: [sys_wait4+423/578] sys_wait4+0x1a7/0x242
Aug 1 03:20:06 amaryllis kernel: [default_wake_function+0/46] default_wake_function+0x0/0x2e
Aug 1 03:20:06 amaryllis kernel: [sys_fork+56/60] sys_fork+0x38/0x3c
Aug 1 03:20:06 amaryllis kernel: [syscall_call+7/11] syscall_call+0x7/0xb
Aug 1 03:20:06 amaryllis kernel:
Aug 1 09:40:42 amaryllis kernel: klogd 1.4.1#11, log source = /proc/kmsg started.
9:40 is when I woke up and discovered my laptop is not running (hang,
that is).
--
Another strange message is:
Aug 1 14:35:11 amaryllis kernel: spurious 8259A interrupt: IRQ7.
Any idea what this is?
Eugene
<quote sender="Eugene Teo">
> <quote sender="Stefano Rivoir">
> > Eugene Teo wrote:
> >
> > >One thing strange though.
> >
> > [...]
> >
> > Ok, I think I've found. It was very probably an old version of the
> > synaptics module for X4.3 (it was ...p3). With the new driver,
> > and with DRI too (along with test2-mm2 patch), it seems to be OK.
> > At least, I've seen no hangs so far.
>
> Hmm, can you explain the synaptics module? i experienced a hang again
> last night. about 5-6 hours of no activities, and i can't get my box
> back up again except with a hard reboot.