From rk111810 at gmail.com  Sun Feb  5 09:17:46 2012
From: rk111810 at gmail.com (R KANNAN)
Date: Sun, 5 Feb 2012 09:17:46 -0500
Subject: [mdlug] [OT] Yahoo web server detects my java bot HTTP request
Message-ID: <CABX2cSHCcUYPCtAzjW_VfvWk2_G3=owJy5cLV4uE7=sYz82qyA@mail.gmail.com>

Hello,

I have a java code that makes HTTP requests to finance.yahoo.com and parses
the returned page for net asset value and write to a text file in a format
that can be read into Quicken. So basically it is a crude way of getting
stock prices.

It has been working fine since 2004 with a few tweaks for search strings
whenever yahoo makes a change in their web pages.

It stopped working on Wed (2/1) and I thought it is a matter changing
search string to fix it.  But on debugging the code, I found that the web
server was not returning most of the page when requested from the Java
code. It was returning HTTP comments like

<!--> robot0 <-->

in web page segments where the price was supposed to be, whereas the page
source from the browser looks fine.

I switched to money.cnn.com which doesn't detect my bot and it seems to
work for now.

I am just curious how the webserver detected that the request (perhaps it
was looking for browser properties: Firefox/IE/Opera , version etc.) and
how it can be included in my HTTP requests.

Thanks

From awilliam at whitemice.org  Sun Feb  5 09:22:31 2012
From: awilliam at whitemice.org (Adam Tauno Williams)
Date: Sun, 05 Feb 2012 09:22:31 -0500
Subject: [mdlug] [OT] Yahoo web server detects my java bot HTTP request
In-Reply-To: <CABX2cSHCcUYPCtAzjW_VfvWk2_G3=owJy5cLV4uE7=sYz82qyA@mail.gmail.com>
References: <CABX2cSHCcUYPCtAzjW_VfvWk2_G3=owJy5cLV4uE7=sYz82qyA@mail.gmail.com>
Message-ID: <1328451751.3386.5.camel@linux-dauq.site>

On Sun, 2012-02-05 at 09:17 -0500, R KANNAN wrote:
> I am just curious how the webserver detected that the request (perhaps it
> was looking for browser properties: Firefox/IE/Opera , version etc.) and
> how it can be included in my HTTP requests.

Probably;  I always set my User-Agent header on requests to be Internet
Explorer.  Commerce sites rarely screw with IE.

"Mozilla/4.0 (Windows; MSIE 7.0; Windows NT 5.1; SV1; .NET CLR
2.0.50727)"

<http://www.useragentstring.com/pages/Internet%20Explorer/> is a handy
page.

-- 
System & Network Administrator [ LPI & NCLA ]
<http://www.whitemiceconsulting.com>
OpenGroupware Developer <http://www.opengroupware.us>
Adam Tauno Williams


From rk111810 at gmail.com  Sun Feb  5 10:41:44 2012
From: rk111810 at gmail.com (R KANNAN)
Date: Sun, 5 Feb 2012 10:41:44 -0500
Subject: [mdlug] [OT] Yahoo web server detects my java bot HTTP request
In-Reply-To: <1328451751.3386.5.camel@linux-dauq.site>
References: <CABX2cSHCcUYPCtAzjW_VfvWk2_G3=owJy5cLV4uE7=sYz82qyA@mail.gmail.com>
	<1328451751.3386.5.camel@linux-dauq.site>
Message-ID: <CABX2cSGFaKkYLYTMc3XvYbV+YnKo+ccduLDaoNrh5ib1nKFcXg@mail.gmail.com>

That worked perfectly. Thanks.

On Sun, Feb 5, 2012 at 9:22 AM, Adam Tauno Williams
<awilliam at whitemice.org>wrote:

> On Sun, 2012-02-05 at 09:17 -0500, R KANNAN wrote:
> > I am just curious how the webserver detected that the request (perhaps it
> > was looking for browser properties: Firefox/IE/Opera , version etc.) and
> > how it can be included in my HTTP requests.
>
> Probably;  I always set my User-Agent header on requests to be Internet
> Explorer.  Commerce sites rarely screw with IE.
>
> "Mozilla/4.0 (Windows; MSIE 7.0; Windows NT 5.1; SV1; .NET CLR
> 2.0.50727)"
>
> <http://www.useragentstring.com/pages/Internet%20Explorer/> is a handy
> page.
>
> --
> System & Network Administrator [ LPI & NCLA ]
> <http://www.whitemiceconsulting.com>
> OpenGroupware Developer <http://www.opengroupware.us>
> Adam Tauno Williams
>
> _______________________________________________
> mdlug mailing list
> mdlug at mdlug.org
> http://mdlug.org/mailman/listinfo/mdlug
>

From jjn at nuge.com  Tue Feb  7 14:45:00 2012
From: jjn at nuge.com (Jay Nugent)
Date: Tue, 7 Feb 2012 14:45:00 -0500 (EST)
Subject: [mdlug] Mark Bobak
Message-ID: <alpine.LRH.2.02.1202071443460.3643@server1.nuge.com>

Greetings,
    Mark, can you hear me now?  (heh heh)   I need a good email address for 
you.  The only one I have on file is bouncing.

       --- Jay Nugent

         () ascii ribbon campaign in
         /\ support of plain text e-mail
+------------------------------------------------------------------------+
| Jay Nugent   jjn at nuge.com    (734)484-5105    (734)649-0850/Cell       |
|   Nugent Telecommunications  [www.nuge.com]                            |
|   Internet Consulting/Linux SysAdmin/Engineering & Design/ISP Reseller |
| ISP Monitoring [www.ispmonitor.org] ISP & Modem Performance Monitoring |
| Web-Pegasus    [www.webpegasus.com] Web Hosting/DNS Hosting/Shell Accts|
+------------------------------------------------------------------------+
  14:01:02 up 155 days, 20:39,  3 users,  load average: 0.09, 0.05, 0.02

From mikemol at gmail.com  Fri Feb 10 10:05:59 2012
From: mikemol at gmail.com (Michael Mol)
Date: Fri, 10 Feb 2012 10:05:59 -0500
Subject: [mdlug] Regarding NAT and IPv6
Message-ID: <CA+czFiAG6CxW2QEqywg761kKiR_Sh5RK6ztLyR9WjkSFYyC7ew@mail.gmail.com>

A recurring question I get about IPv6 is NAT.

Here's a good thread to dive into, if that's something that'd be on
your mind: http://www.reddit.com/r/ipv6/comments/pj4ij/why_the_hate_for_nat66/

-- 
:wq

From otakurider at gmail.com  Fri Feb 10 10:47:05 2012
From: otakurider at gmail.com (Gmail-otakurider)
Date: Fri, 10 Feb 2012 10:47:05 -0500
Subject: [mdlug] hanging machine kernel panic
In-Reply-To: <4F168A40.7050905@gmail.com>
References: <20120116.092215.5262.1@webmail08.vgs.untd.com>
	<4F14545E.3090402@wowway.com>
	<50F4BFBDC6001340B94E13C70E39F9B00149C887@nasa-dtw-ex004.nasa.cpwr.corp>
	<1326827757.4660.5.camel@linux-dauq.site>
	<4F168A40.7050905@gmail.com>
Message-ID: <4F353BF9.5090804@gmail.com>

Ok gurus here is one for you, Does this look to you as a memory chip
issue? I am thinking yes.

yes its its is true fedora 5  2.6.20 - why, because it is - anyway here
is the dmesg list with error


Linux version 2.6.20-1.2320.fc5
(brewbuilder at hs20-bc2-2.build.redhat.com) (gcc version 4.1.1 20070105
(Red Hat 4.1.1-51)) #1 Tue Jun 12 18:50:38 EDT 2007
BIOS-provided physical RAM map:
sanitize start
sanitize end
copy_e820_map() start: 0000000000000000 size: 000000000009fc00 end:
000000000009fc00 type: 1
copy_e820_map() type is E820_RAM
copy_e820_map() start: 000000000009fc00 size: 0000000000000400 end:
00000000000a0000 type: 2
copy_e820_map() start: 00000000000f0000 size: 0000000000010000 end:
0000000000100000 type: 2
copy_e820_map() start: 0000000000100000 size: 000000000feec000 end:
000000000ffec000 type: 1
copy_e820_map() type is E820_RAM
copy_e820_map() start: 000000000ffec000 size: 0000000000003000 end:
000000000ffef000 type: 3
copy_e820_map() start: 000000000ffef000 size: 0000000000010000 end:
000000000ffff000 type: 2
copy_e820_map() start: 000000000ffff000 size: 0000000000001000 end:
0000000010000000 type: 4
copy_e820_map() start: 00000000ffff0000 size: 0000000000010000 end:
0000000100000000 type: 2
 BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
 BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
 BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
 BIOS-e820: 0000000000100000 - 000000000ffec000 (usable)
 BIOS-e820: 000000000ffec000 - 000000000ffef000 (ACPI data)
 BIOS-e820: 000000000ffef000 - 000000000ffff000 (reserved)
 BIOS-e820: 000000000ffff000 - 0000000010000000 (ACPI NVS)
 BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
BUG: unable to handle kernel paging request at virtual address b7c00010
 printing eip:
c044e088
*pde = 02f0c067
Oops: 0002 [#1]
last sysfs file: /block/hda/hda1/size
Modules linked in: nfsd exportfs lockd nfs_acl autofs4 hidp l2cap
bluetooth sunrpc dm_mirror dm_mod video sbs i2c_ec dock container button
battery asus_acpi backlight ac ipv6 lp parport_pc parport floppy
ohci_hcd serio_raw ide_cd i2c_ali15x3 cdrom i2c_ali1535 i2c_core 8139too
mii pcspkr ext3 jbd
CPU:    0
EIP:    0060:[<c044e088>]    Not tainted VLI
EFLAGS: 00010212   (2.6.20-1.2320.fc5 #1)
EIP is at free_pgd_range+0x5b/0x16e
eax: b7beffff   ebx: c5bf17c0   ecx: b7bf0000   edx: b7bfffff
esi: b8000000   edi: 00000000   ebp: b7c00000   esp: c3c5ef0c
ds: 007b   es: 007b   ss: 0068
Process munin-graph (pid: 6667, ti=c3c5e000 task=c6fbf3d0 task.ti=c3c5e000)
Stack: b7bf0000 c3c5ef68 ccefa380 cc9ac518 c0451532 c5bf17c0 00000000
00000000
       b7fe3000 c045056e b7fde000 b7ff0000 b7fde000 c3c5ef68 c5bf17c0
cd26fca4
       c7d510d4 cc9ac518 c0451225 b7ff0000 c3c5ef64 00000000 00000000
c072e31c
Call Trace:
 [<c0451532>] unlink_file_vma+0x28/0x38
 [<c045056e>] free_pgtables+0x90/0xa0
 [<c0451225>] unmap_region+0xa7/0xd7
 [<c0451bca>] do_munmap+0x15a/0x1af
 [<c0451c4f>] sys_munmap+0x30/0x3e
 [<c0403dc8>] syscall_call+0x7/0xb
 =======================
Code: 81 e5 00 00 c0 ff 0f 84 2a 01 00 00 8b 04 24 8d 55 ff 8b 0c 24 48
81 e9 00 00 40 00 39 d0 0f 46 0c 24 89 0c 24 8b 04 24 48 39 c6 <89> 44
24 10 0f 87 01 01 00 00 8b 54 24 04 8b 02 8b 10 89 f0 c1
EIP: [<c044e088>] free_pgd_range+0x5b/0x16e SS:ESP 0068:c3c5ef0c
 <0>general protection fault: 0000 [#2]
last sysfs file: /block/hda/hda1/size
Modules linked in: nfsd exportfs lockd nfs_acl autofs4 hidp l2cap
bluetooth sunrpc dm_mirror dm_mod video sbs i2c_ec dock container button
battery asus_acpi backlight ac ipv6 lp parport_pc parport floppy
ohci_hcd serio_raw ide_cd i2c_ali15x3 cdrom i2c_ali1535 i2c_core 8139too
mii pcspkr ext3 jbd
CPU:    0
EIP:    0060:[<c0467ad2>]    Not tainted VLI
EFLAGS: 00010286   (2.6.20-1.2320.fc5 #1)
EIP is at link_path_walk+0x26/0xaf
eax: cef1edac   ebx: cff97320   ecx: cffdfca0   edx: fffffffe
esi: cef1ee38   edi: ffffffff   ebp: cffdfca0   esp: cef1eda8
ds: 007b   es: 007b   ss: 0068
Process df (pid: 13138, ti=cef1e000 task=c5ddae90 task.ti=cef1e000)
Stack: cef1eede ffffffff cffdfca0 00000246 00000246 c0600289 00000001
00000001
       00000000 000000d0 00000246 cfdb7478 00000080 cff96520 c05a6c66
00000000
       cffe1860 c3edcd60 00000001 c3edcd60 0000006e cff97320 cff97324
cef1ee38
Call Trace:
 [<c0600289>] unix_sock_destructor+0x11/0xd3
 [<c05a6c66>] __alloc_skb+0x49/0xf7
 [<c0467df2>] do_path_lookup+0x173/0x1c3
 [<c04687fc>] path_lookup+0x14/0x16
 [<c05ff287>] unix_find_other+0x2a/0x17b
 [<c0600289>] unix_sock_destructor+0x11/0xd3
 [<c05a6c66>] __alloc_skb+0x49/0xf7
 [<c0600de7>] unix_stream_connect+0xe2/0x3aa
 [<c05a22af>] sys_connect+0x82/0xad
 [<c05a17c1>] sock_map_fd+0x41/0x4a
 [<c05a2afb>] sys_socketcall+0xac/0x261
 [<c046975e>] sys_fcntl64+0x7d/0x85
 [<c0403dc8>] syscall_call+0x7/0xb
 =======================
Code: 5b 5e 5f 5d c3 55 b9 50 00 00 00 57 56 89 d6 53 83 ec 54 89 04 24
8d 44 24 04 e8 a2 05 07 00 8b 7c 24 04 8b 6c 24 08 85 ff 74 0b <83> 3f
00 75 04 0f 0b eb fe ff 07 85 ed 74 03 ff 45 28 8b 04 24
EIP: [<c0467ad2>] link_path_walk+0x26/0xaf SS:ESP 0068:cef1eda8
 <1>BUG: unable to handle kernel paging request at virtual address fffecc69
 printing eip:
c0480c1c
*pde = 00002067
Oops: 0002 [#3]
last sysfs file: /block/hda/hda1/size
Modules linked in: nfsd exportfs lockd nfs_acl autofs4 hidp l2cap
bluetooth sunrpc dm_mirror dm_mod video sbs i2c_ec dock container button
battery asus_acpi backlight ac ipv6 lp parport_pc parport floppy
ohci_hcd serio_raw ide_cd i2c_ali15x3 cdrom i2c_ali1535 i2c_core 8139too
mii pcspkr ext3 jbd
CPU:    0
EIP:    0060:[<c0480c1c>]    Not tainted VLI
EFLAGS: 00010246   (2.6.20-1.2320.fc5 #1)
EIP is at do_mpage_readpage+0x21b/0x58f
eax: fffecc69   ebx: 00000000   ecx: 00000000   edx: 00001b97
esi: 00001b97   edi: 00000000   ebp: ca893d00   esp: ca893be9
ds: 007b   es: 007b   ss: 0068
Process rpmq (pid: 29469, ti=ca893000 task=c5ddae90 task.ti=ca893000)
Stack: 48000000 00000c60 00000000 e4000001 08cfcc6b 98000000 0000001b
34000000
       40d08896 38ca893d 01ca893d 00000000 00c112b6 90000000 b4c5ddae
0cc08eab
       01000000 98000000 0000001b 00000000 01000000 00000000 01000000
00000000
Call Trace:
 =======================
Code: 00 00 00 00 00 c7 45 14 00 00 00 00 3b 7c 24 40 77 44 72 06 3b 74
24 3c 73 3c 8b 44 24 3c 89 f2 8a 4c 24 34 29 f0 31 db d3 e0 f6 <c1> 20
0f 45 c3 89 f9 89 45 14 8b 44 24 30 c7 44 24 04 00 00 00
EIP: [<c0480c1c>] do_mpage_readpage+0x21b/0x58f SS:ESP 0068:ca893be9
 <3>BUG: sleeping function called from invalid context at kernel/rwsem.c:20
in_atomic():0, irqs_disabled():1
 [<c042f150>] down_read+0x12/0x26
 [<c043a8b3>] acct_collect+0x38/0x141
 [<c041ef63>] do_exit+0x1af/0x70d
 [<c041d212>] printk+0x1f/0x95
 [<c0405285>] die+0x1f1/0x216
 [<c0609829>] do_page_fault+0x3fe/0x4d1
 [<c060942b>] do_page_fault+0x0/0x4d1
 [<c0608214>] error_code+0x74/0x7c
 [<c0480c1c>] do_mpage_readpage+0x21b/0x58f
 =======================


Thanks

Pat

From mat.enders at gmail.com  Fri Feb 10 10:59:42 2012
From: mat.enders at gmail.com (Mat Enders)
Date: Fri, 10 Feb 2012 15:59:42 +0000
Subject: [mdlug] hanging machine kernel panic
In-Reply-To: <4F353BF9.5090804@gmail.com>
References: <20120116.092215.5262.1@webmail08.vgs.untd.com>
	<4F14545E.3090402@wowway.com>
	<50F4BFBDC6001340B94E13C70E39F9B00149C887@nasa-dtw-ex004.nasa.cpwr.corp>
	<1326827757.4660.5.camel@linux-dauq.site>
	<4F168A40.7050905@gmail.com> <4F353BF9.5090804@gmail.com>
Message-ID: <392094381-1328889582-cardhu_decombobulator_blackberry.rim.net-263310594-@b12.c27.bise6.blackberry>

It looks ram related what does memtest86 say when you run it. 
Mat Enders from my BlackBerry?

-----Original Message-----
From: Gmail-otakurider <otakurider at gmail.com>
Sender: mdlug-bounces at mdlug.org
Date: Fri, 10 Feb 2012 10:47:05 
To: MDLUG's Main discussion list<mdlug at mdlug.org>
Reply-To: MDLUG's Main discussion list <mdlug at mdlug.org>
Subject: [mdlug] hanging machine kernel panic

Ok gurus here is one for you, Does this look to you as a memory chip
issue? I am thinking yes.

yes its its is true fedora 5  2.6.20 - why, because it is - anyway here
is the dmesg list with error


Linux version 2.6.20-1.2320.fc5
(brewbuilder at hs20-bc2-2.build.redhat.com) (gcc version 4.1.1 20070105
(Red Hat 4.1.1-51)) #1 Tue Jun 12 18:50:38 EDT 2007
BIOS-provided physical RAM map:
sanitize start
sanitize end
copy_e820_map() start: 0000000000000000 size: 000000000009fc00 end:
000000000009fc00 type: 1
copy_e820_map() type is E820_RAM
copy_e820_map() start: 000000000009fc00 size: 0000000000000400 end:
00000000000a0000 type: 2
copy_e820_map() start: 00000000000f0000 size: 0000000000010000 end:
0000000000100000 type: 2
copy_e820_map() start: 0000000000100000 size: 000000000feec000 end:
000000000ffec000 type: 1
copy_e820_map() type is E820_RAM
copy_e820_map() start: 000000000ffec000 size: 0000000000003000 end:
000000000ffef000 type: 3
copy_e820_map() start: 000000000ffef000 size: 0000000000010000 end:
000000000ffff000 type: 2
copy_e820_map() start: 000000000ffff000 size: 0000000000001000 end:
0000000010000000 type: 4
copy_e820_map() start: 00000000ffff0000 size: 0000000000010000 end:
0000000100000000 type: 2
 BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
 BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
 BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
 BIOS-e820: 0000000000100000 - 000000000ffec000 (usable)
 BIOS-e820: 000000000ffec000 - 000000000ffef000 (ACPI data)
 BIOS-e820: 000000000ffef000 - 000000000ffff000 (reserved)
 BIOS-e820: 000000000ffff000 - 0000000010000000 (ACPI NVS)
 BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
BUG: unable to handle kernel paging request at virtual address b7c00010
 printing eip:
c044e088
*pde = 02f0c067
Oops: 0002 [#1]
last sysfs file: /block/hda/hda1/size
Modules linked in: nfsd exportfs lockd nfs_acl autofs4 hidp l2cap
bluetooth sunrpc dm_mirror dm_mod video sbs i2c_ec dock container button
battery asus_acpi backlight ac ipv6 lp parport_pc parport floppy
ohci_hcd serio_raw ide_cd i2c_ali15x3 cdrom i2c_ali1535 i2c_core 8139too
mii pcspkr ext3 jbd
CPU:    0
EIP:    0060:[<c044e088>]    Not tainted VLI
EFLAGS: 00010212   (2.6.20-1.2320.fc5 #1)
EIP is at free_pgd_range+0x5b/0x16e
eax: b7beffff   ebx: c5bf17c0   ecx: b7bf0000   edx: b7bfffff
esi: b8000000   edi: 00000000   ebp: b7c00000   esp: c3c5ef0c
ds: 007b   es: 007b   ss: 0068
Process munin-graph (pid: 6667, ti=c3c5e000 task=c6fbf3d0 task.ti=c3c5e000)
Stack: b7bf0000 c3c5ef68 ccefa380 cc9ac518 c0451532 c5bf17c0 00000000
00000000
       b7fe3000 c045056e b7fde000 b7ff0000 b7fde000 c3c5ef68 c5bf17c0
cd26fca4
       c7d510d4 cc9ac518 c0451225 b7ff0000 c3c5ef64 00000000 00000000
c072e31c
Call Trace:
 [<c0451532>] unlink_file_vma+0x28/0x38
 [<c045056e>] free_pgtables+0x90/0xa0
 [<c0451225>] unmap_region+0xa7/0xd7
 [<c0451bca>] do_munmap+0x15a/0x1af
 [<c0451c4f>] sys_munmap+0x30/0x3e
 [<c0403dc8>] syscall_call+0x7/0xb
 =======================
Code: 81 e5 00 00 c0 ff 0f 84 2a 01 00 00 8b 04 24 8d 55 ff 8b 0c 24 48
81 e9 00 00 40 00 39 d0 0f 46 0c 24 89 0c 24 8b 04 24 48 39 c6 <89> 44
24 10 0f 87 01 01 00 00 8b 54 24 04 8b 02 8b 10 89 f0 c1
EIP: [<c044e088>] free_pgd_range+0x5b/0x16e SS:ESP 0068:c3c5ef0c
 <0>general protection fault: 0000 [#2]
last sysfs file: /block/hda/hda1/size
Modules linked in: nfsd exportfs lockd nfs_acl autofs4 hidp l2cap
bluetooth sunrpc dm_mirror dm_mod video sbs i2c_ec dock container button
battery asus_acpi backlight ac ipv6 lp parport_pc parport floppy
ohci_hcd serio_raw ide_cd i2c_ali15x3 cdrom i2c_ali1535 i2c_core 8139too
mii pcspkr ext3 jbd
CPU:    0
EIP:    0060:[<c0467ad2>]    Not tainted VLI
EFLAGS: 00010286   (2.6.20-1.2320.fc5 #1)
EIP is at link_path_walk+0x26/0xaf
eax: cef1edac   ebx: cff97320   ecx: cffdfca0   edx: fffffffe
esi: cef1ee38   edi: ffffffff   ebp: cffdfca0   esp: cef1eda8
ds: 007b   es: 007b   ss: 0068
Process df (pid: 13138, ti=cef1e000 task=c5ddae90 task.ti=cef1e000)
Stack: cef1eede ffffffff cffdfca0 00000246 00000246 c0600289 00000001
00000001
       00000000 000000d0 00000246 cfdb7478 00000080 cff96520 c05a6c66
00000000
       cffe1860 c3edcd60 00000001 c3edcd60 0000006e cff97320 cff97324
cef1ee38
Call Trace:
 [<c0600289>] unix_sock_destructor+0x11/0xd3
 [<c05a6c66>] __alloc_skb+0x49/0xf7
 [<c0467df2>] do_path_lookup+0x173/0x1c3
 [<c04687fc>] path_lookup+0x14/0x16
 [<c05ff287>] unix_find_other+0x2a/0x17b
 [<c0600289>] unix_sock_destructor+0x11/0xd3
 [<c05a6c66>] __alloc_skb+0x49/0xf7
 [<c0600de7>] unix_stream_connect+0xe2/0x3aa
 [<c05a22af>] sys_connect+0x82/0xad
 [<c05a17c1>] sock_map_fd+0x41/0x4a
 [<c05a2afb>] sys_socketcall+0xac/0x261
 [<c046975e>] sys_fcntl64+0x7d/0x85
 [<c0403dc8>] syscall_call+0x7/0xb
 =======================
Code: 5b 5e 5f 5d c3 55 b9 50 00 00 00 57 56 89 d6 53 83 ec 54 89 04 24
8d 44 24 04 e8 a2 05 07 00 8b 7c 24 04 8b 6c 24 08 85 ff 74 0b <83> 3f
00 75 04 0f 0b eb fe ff 07 85 ed 74 03 ff 45 28 8b 04 24
EIP: [<c0467ad2>] link_path_walk+0x26/0xaf SS:ESP 0068:cef1eda8
 <1>BUG: unable to handle kernel paging request at virtual address fffecc69
 printing eip:
c0480c1c
*pde = 00002067
Oops: 0002 [#3]
last sysfs file: /block/hda/hda1/size
Modules linked in: nfsd exportfs lockd nfs_acl autofs4 hidp l2cap
bluetooth sunrpc dm_mirror dm_mod video sbs i2c_ec dock container button
battery asus_acpi backlight ac ipv6 lp parport_pc parport floppy
ohci_hcd serio_raw ide_cd i2c_ali15x3 cdrom i2c_ali1535 i2c_core 8139too
mii pcspkr ext3 jbd
CPU:    0
EIP:    0060:[<c0480c1c>]    Not tainted VLI
EFLAGS: 00010246   (2.6.20-1.2320.fc5 #1)
EIP is at do_mpage_readpage+0x21b/0x58f
eax: fffecc69   ebx: 00000000   ecx: 00000000   edx: 00001b97
esi: 00001b97   edi: 00000000   ebp: ca893d00   esp: ca893be9
ds: 007b   es: 007b   ss: 0068
Process rpmq (pid: 29469, ti=ca893000 task=c5ddae90 task.ti=ca893000)
Stack: 48000000 00000c60 00000000 e4000001 08cfcc6b 98000000 0000001b
34000000
       40d08896 38ca893d 01ca893d 00000000 00c112b6 90000000 b4c5ddae
0cc08eab
       01000000 98000000 0000001b 00000000 01000000 00000000 01000000
00000000
Call Trace:
 =======================
Code: 00 00 00 00 00 c7 45 14 00 00 00 00 3b 7c 24 40 77 44 72 06 3b 74
24 3c 73 3c 8b 44 24 3c 89 f2 8a 4c 24 34 29 f0 31 db d3 e0 f6 <c1> 20
0f 45 c3 89 f9 89 45 14 8b 44 24 30 c7 44 24 04 00 00 00
EIP: [<c0480c1c>] do_mpage_readpage+0x21b/0x58f SS:ESP 0068:ca893be9
 <3>BUG: sleeping function called from invalid context at kernel/rwsem.c:20
in_atomic():0, irqs_disabled():1
 [<c042f150>] down_read+0x12/0x26
 [<c043a8b3>] acct_collect+0x38/0x141
 [<c041ef63>] do_exit+0x1af/0x70d
 [<c041d212>] printk+0x1f/0x95
 [<c0405285>] die+0x1f1/0x216
 [<c0609829>] do_page_fault+0x3fe/0x4d1
 [<c060942b>] do_page_fault+0x0/0x4d1
 [<c0608214>] error_code+0x74/0x7c
 [<c0480c1c>] do_mpage_readpage+0x21b/0x58f
 =======================


Thanks

Pat
_______________________________________________
mdlug mailing list
mdlug at mdlug.org
http://mdlug.org/mailman/listinfo/mdlug

From Raymond.Ingles at compuware.com  Fri Feb 10 12:12:29 2012
From: Raymond.Ingles at compuware.com (Ingles, Raymond)
Date: Fri, 10 Feb 2012 12:12:29 -0500
Subject: [mdlug] hanging machine kernel panic
In-Reply-To: <392094381-1328889582-cardhu_decombobulator_blackberry.rim.net-263310594-@b12.c27.bise6.blackberry>
References: <20120116.092215.5262.1@webmail08.vgs.untd.com><4F14545E.3090402@wowway.com><50F4BFBDC6001340B94E13C70E39F9B00149C887@nasa-dtw-ex004.nasa.cpwr.corp><1326827757.4660.5.camel@linux-dauq.site><4F168A40.7050905@gmail.com>
	<4F353BF9.5090804@gmail.com>
	<392094381-1328889582-cardhu_decombobulator_blackberry.rim.net-263310594-@b12.c27.bise6.blackberry>
Message-ID: <50F4BFBDC6001340B94E13C70E39F9B001630A7E@nasa-dtw-ex004.nasa.cpwr.corp>

I've run into bad RAM a couple times. Definitely memtest86 it.

 Sincerely,

 Ray Ingles                                            (313) 227-2317

  "Technically, Windows is an operating system, which means that it
 supplies your computer with the basic commands it needs to suddenly,
      with no warning whatsoever, stop operating." - Dave Barry

> 
http://www.compuware.com/
The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.

> From: mdlug-bounces at mdlug.org [mailto:mdlug-bounces at mdlug.org] On
Behalf Of
> Mat Enders
> Sent: Friday, February 10, 2012 11:00 AM
> To: MDLUG's Main discussion list
> Subject: Re: [mdlug] hanging machine kernel panic
> 
> It looks ram related what does memtest86 say when you run it.
> Mat Enders from my BlackBerry(r)
> 
> -----Original Message-----
> From: Gmail-otakurider <otakurider at gmail.com>
> Sender: mdlug-bounces at mdlug.org
> Date: Fri, 10 Feb 2012 10:47:05
> To: MDLUG's Main discussion list<mdlug at mdlug.org>
> Reply-To: MDLUG's Main discussion list <mdlug at mdlug.org>
> Subject: [mdlug] hanging machine kernel panic
> 
> Ok gurus here is one for you, Does this look to you as a memory chip
> issue? I am thinking yes.
> 
> yes its its is true fedora 5  2.6.20 - why, because it is - anyway
here
> is the dmesg list with error
> 
> 
> Linux version 2.6.20-1.2320.fc5
> (brewbuilder at hs20-bc2-2.build.redhat.com) (gcc version 4.1.1 20070105
> (Red Hat 4.1.1-51)) #1 Tue Jun 12 18:50:38 EDT 2007
> BIOS-provided physical RAM map:
> sanitize start
> sanitize end
> copy_e820_map() start: 0000000000000000 size: 000000000009fc00 end:
> 000000000009fc00 type: 1
> copy_e820_map() type is E820_RAM
> copy_e820_map() start: 000000000009fc00 size: 0000000000000400 end:
> 00000000000a0000 type: 2
> copy_e820_map() start: 00000000000f0000 size: 0000000000010000 end:
> 0000000000100000 type: 2
> copy_e820_map() start: 0000000000100000 size: 000000000feec000 end:
> 000000000ffec000 type: 1
> copy_e820_map() type is E820_RAM
> copy_e820_map() start: 000000000ffec000 size: 0000000000003000 end:
> 000000000ffef000 type: 3
> copy_e820_map() start: 000000000ffef000 size: 0000000000010000 end:
> 000000000ffff000 type: 2
> copy_e820_map() start: 000000000ffff000 size: 0000000000001000 end:
> 0000000010000000 type: 4
> copy_e820_map() start: 00000000ffff0000 size: 0000000000010000 end:
> 0000000100000000 type: 2
>  BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
>  BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
>  BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
>  BIOS-e820: 0000000000100000 - 000000000ffec000 (usable)
>  BIOS-e820: 000000000ffec000 - 000000000ffef000 (ACPI data)
>  BIOS-e820: 000000000ffef000 - 000000000ffff000 (reserved)
>  BIOS-e820: 000000000ffff000 - 0000000010000000 (ACPI NVS)
>  BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
> BUG: unable to handle kernel paging request at virtual address
b7c00010
>  printing eip:
> c044e088
> *pde = 02f0c067
> Oops: 0002 [#1]
> last sysfs file: /block/hda/hda1/size
> Modules linked in: nfsd exportfs lockd nfs_acl autofs4 hidp l2cap
> bluetooth sunrpc dm_mirror dm_mod video sbs i2c_ec dock container
button
> battery asus_acpi backlight ac ipv6 lp parport_pc parport floppy
> ohci_hcd serio_raw ide_cd i2c_ali15x3 cdrom i2c_ali1535 i2c_core
8139too
> mii pcspkr ext3 jbd
> CPU:    0
> EIP:    0060:[<c044e088>]    Not tainted VLI
> EFLAGS: 00010212   (2.6.20-1.2320.fc5 #1)
> EIP is at free_pgd_range+0x5b/0x16e
> eax: b7beffff   ebx: c5bf17c0   ecx: b7bf0000   edx: b7bfffff
> esi: b8000000   edi: 00000000   ebp: b7c00000   esp: c3c5ef0c
> ds: 007b   es: 007b   ss: 0068
> Process munin-graph (pid: 6667, ti=c3c5e000 task=c6fbf3d0
task.ti=c3c5e000)
> Stack: b7bf0000 c3c5ef68 ccefa380 cc9ac518 c0451532 c5bf17c0 00000000
> 00000000
>        b7fe3000 c045056e b7fde000 b7ff0000 b7fde000 c3c5ef68 c5bf17c0
> cd26fca4
>        c7d510d4 cc9ac518 c0451225 b7ff0000 c3c5ef64 00000000 00000000
> c072e31c
> Call Trace:
>  [<c0451532>] unlink_file_vma+0x28/0x38
>  [<c045056e>] free_pgtables+0x90/0xa0
>  [<c0451225>] unmap_region+0xa7/0xd7
>  [<c0451bca>] do_munmap+0x15a/0x1af
>  [<c0451c4f>] sys_munmap+0x30/0x3e
>  [<c0403dc8>] syscall_call+0x7/0xb
>  =======================
> Code: 81 e5 00 00 c0 ff 0f 84 2a 01 00 00 8b 04 24 8d 55 ff 8b 0c 24
48
> 81 e9 00 00 40 00 39 d0 0f 46 0c 24 89 0c 24 8b 04 24 48 39 c6 <89> 44
> 24 10 0f 87 01 01 00 00 8b 54 24 04 8b 02 8b 10 89 f0 c1
> EIP: [<c044e088>] free_pgd_range+0x5b/0x16e SS:ESP 0068:c3c5ef0c
>  <0>general protection fault: 0000 [#2]
> last sysfs file: /block/hda/hda1/size
> Modules linked in: nfsd exportfs lockd nfs_acl autofs4 hidp l2cap
> bluetooth sunrpc dm_mirror dm_mod video sbs i2c_ec dock container
button
> battery asus_acpi backlight ac ipv6 lp parport_pc parport floppy
> ohci_hcd serio_raw ide_cd i2c_ali15x3 cdrom i2c_ali1535 i2c_core
8139too
> mii pcspkr ext3 jbd
> CPU:    0
> EIP:    0060:[<c0467ad2>]    Not tainted VLI
> EFLAGS: 00010286   (2.6.20-1.2320.fc5 #1)
> EIP is at link_path_walk+0x26/0xaf
> eax: cef1edac   ebx: cff97320   ecx: cffdfca0   edx: fffffffe
> esi: cef1ee38   edi: ffffffff   ebp: cffdfca0   esp: cef1eda8
> ds: 007b   es: 007b   ss: 0068
> Process df (pid: 13138, ti=cef1e000 task=c5ddae90 task.ti=cef1e000)
> Stack: cef1eede ffffffff cffdfca0 00000246 00000246 c0600289 00000001
> 00000001
>        00000000 000000d0 00000246 cfdb7478 00000080 cff96520 c05a6c66
> 00000000
>        cffe1860 c3edcd60 00000001 c3edcd60 0000006e cff97320 cff97324
> cef1ee38
> Call Trace:
>  [<c0600289>] unix_sock_destructor+0x11/0xd3
>  [<c05a6c66>] __alloc_skb+0x49/0xf7
>  [<c0467df2>] do_path_lookup+0x173/0x1c3
>  [<c04687fc>] path_lookup+0x14/0x16
>  [<c05ff287>] unix_find_other+0x2a/0x17b
>  [<c0600289>] unix_sock_destructor+0x11/0xd3
>  [<c05a6c66>] __alloc_skb+0x49/0xf7
>  [<c0600de7>] unix_stream_connect+0xe2/0x3aa
>  [<c05a22af>] sys_connect+0x82/0xad
>  [<c05a17c1>] sock_map_fd+0x41/0x4a
>  [<c05a2afb>] sys_socketcall+0xac/0x261
>  [<c046975e>] sys_fcntl64+0x7d/0x85
>  [<c0403dc8>] syscall_call+0x7/0xb
>  =======================
> Code: 5b 5e 5f 5d c3 55 b9 50 00 00 00 57 56 89 d6 53 83 ec 54 89 04
24
> 8d 44 24 04 e8 a2 05 07 00 8b 7c 24 04 8b 6c 24 08 85 ff 74 0b <83> 3f
> 00 75 04 0f 0b eb fe ff 07 85 ed 74 03 ff 45 28 8b 04 24
> EIP: [<c0467ad2>] link_path_walk+0x26/0xaf SS:ESP 0068:cef1eda8
>  <1>BUG: unable to handle kernel paging request at virtual address
fffecc69
>  printing eip:
> c0480c1c
> *pde = 00002067
> Oops: 0002 [#3]
> last sysfs file: /block/hda/hda1/size
> Modules linked in: nfsd exportfs lockd nfs_acl autofs4 hidp l2cap
> bluetooth sunrpc dm_mirror dm_mod video sbs i2c_ec dock container
button
> battery asus_acpi backlight ac ipv6 lp parport_pc parport floppy
> ohci_hcd serio_raw ide_cd i2c_ali15x3 cdrom i2c_ali1535 i2c_core
8139too
> mii pcspkr ext3 jbd
> CPU:    0
> EIP:    0060:[<c0480c1c>]    Not tainted VLI
> EFLAGS: 00010246   (2.6.20-1.2320.fc5 #1)
> EIP is at do_mpage_readpage+0x21b/0x58f
> eax: fffecc69   ebx: 00000000   ecx: 00000000   edx: 00001b97
> esi: 00001b97   edi: 00000000   ebp: ca893d00   esp: ca893be9
> ds: 007b   es: 007b   ss: 0068
> Process rpmq (pid: 29469, ti=ca893000 task=c5ddae90 task.ti=ca893000)
> Stack: 48000000 00000c60 00000000 e4000001 08cfcc6b 98000000 0000001b
> 34000000
>        40d08896 38ca893d 01ca893d 00000000 00c112b6 90000000 b4c5ddae
> 0cc08eab
>        01000000 98000000 0000001b 00000000 01000000 00000000 01000000
> 00000000
> Call Trace:
>  =======================
> Code: 00 00 00 00 00 c7 45 14 00 00 00 00 3b 7c 24 40 77 44 72 06 3b
74
> 24 3c 73 3c 8b 44 24 3c 89 f2 8a 4c 24 34 29 f0 31 db d3 e0 f6 <c1> 20
> 0f 45 c3 89 f9 89 45 14 8b 44 24 30 c7 44 24 04 00 00 00
> EIP: [<c0480c1c>] do_mpage_readpage+0x21b/0x58f SS:ESP 0068:ca893be9
>  <3>BUG: sleeping function called from invalid context at
kernel/rwsem.c:20
> in_atomic():0, irqs_disabled():1
>  [<c042f150>] down_read+0x12/0x26
>  [<c043a8b3>] acct_collect+0x38/0x141
>  [<c041ef63>] do_exit+0x1af/0x70d
>  [<c041d212>] printk+0x1f/0x95
>  [<c0405285>] die+0x1f1/0x216
>  [<c0609829>] do_page_fault+0x3fe/0x4d1
>  [<c060942b>] do_page_fault+0x0/0x4d1
>  [<c0608214>] error_code+0x74/0x7c
>  [<c0480c1c>] do_mpage_readpage+0x21b/0x58f
>  =======================
> 
> 
> Thanks
> 
> Pat
> _______________________________________________
> mdlug mailing list
> mdlug at mdlug.org
> http://mdlug.org/mailman/listinfo/mdlug
> _______________________________________________
> mdlug mailing list
> mdlug at mdlug.org
> http://mdlug.org/mailman/listinfo/mdlug


From jhansonxi at gmail.com  Fri Feb 10 14:33:42 2012
From: jhansonxi at gmail.com (Jeff Hanson)
Date: Fri, 10 Feb 2012 14:33:42 -0500
Subject: [mdlug] hanging machine kernel panic
In-Reply-To: <50F4BFBDC6001340B94E13C70E39F9B001630A7E@nasa-dtw-ex004.nasa.cpwr.corp>
References: <20120116.092215.5262.1@webmail08.vgs.untd.com>
	<4F14545E.3090402@wowway.com>
	<50F4BFBDC6001340B94E13C70E39F9B00149C887@nasa-dtw-ex004.nasa.cpwr.corp>
	<1326827757.4660.5.camel@linux-dauq.site>
	<4F168A40.7050905@gmail.com> <4F353BF9.5090804@gmail.com>
	<392094381-1328889582-cardhu_decombobulator_blackberry.rim.net-263310594-@b12.c27.bise6.blackberry>
	<50F4BFBDC6001340B94E13C70E39F9B001630A7E@nasa-dtw-ex004.nasa.cpwr.corp>
Message-ID: <CAD39dTa7dh0F-bTqKV6ffO4d8vC15R5UwVx9uNag0kswbkrcTw@mail.gmail.com>

If it is a recent development on a previously functional system then
probably RAM.  Could also be loose memory module, daughtercards,
SATA/IDE port or cable, or overheating CPU.

On 2/10/12, Ingles, Raymond <Raymond.Ingles at compuware.com> wrote:
> I've run into bad RAM a couple times. Definitely memtest86 it.
>
>  Sincerely,
>
>  Ray Ingles                                            (313) 227-2317
>
>   "Technically, Windows is an operating system, which means that it
>  supplies your computer with the basic commands it needs to suddenly,
>       with no warning whatsoever, stop operating." - Dave Barry
>
>>
> http://www.compuware.com/
> The contents of this e-mail are intended for the named addressee only. It
> contains information that may be confidential. Unless you are the named
> addressee or an authorized designee, you may not copy or use it, or disclose
> it to anyone else. If you received it in error please notify us immediately
> and then destroy it.
>
>> From: mdlug-bounces at mdlug.org [mailto:mdlug-bounces at mdlug.org] On
> Behalf Of
>> Mat Enders
>> Sent: Friday, February 10, 2012 11:00 AM
>> To: MDLUG's Main discussion list
>> Subject: Re: [mdlug] hanging machine kernel panic
>>
>> It looks ram related what does memtest86 say when you run it.
>> Mat Enders from my BlackBerry(r)
>>
>> -----Original Message-----
>> From: Gmail-otakurider <otakurider at gmail.com>
>> Sender: mdlug-bounces at mdlug.org
>> Date: Fri, 10 Feb 2012 10:47:05
>> To: MDLUG's Main discussion list<mdlug at mdlug.org>
>> Reply-To: MDLUG's Main discussion list <mdlug at mdlug.org>
>> Subject: [mdlug] hanging machine kernel panic
>>
>> Ok gurus here is one for you, Does this look to you as a memory chip
>> issue? I am thinking yes.
>>
>> yes its its is true fedora 5  2.6.20 - why, because it is - anyway
> here
>> is the dmesg list with error
>>
>>
>> Linux version 2.6.20-1.2320.fc5
>> (brewbuilder at hs20-bc2-2.build.redhat.com) (gcc version 4.1.1 20070105
>> (Red Hat 4.1.1-51)) #1 Tue Jun 12 18:50:38 EDT 2007
>> BIOS-provided physical RAM map:
>> sanitize start
>> sanitize end
>> copy_e820_map() start: 0000000000000000 size: 000000000009fc00 end:
>> 000000000009fc00 type: 1
>> copy_e820_map() type is E820_RAM
>> copy_e820_map() start: 000000000009fc00 size: 0000000000000400 end:
>> 00000000000a0000 type: 2
>> copy_e820_map() start: 00000000000f0000 size: 0000000000010000 end:
>> 0000000000100000 type: 2
>> copy_e820_map() start: 0000000000100000 size: 000000000feec000 end:
>> 000000000ffec000 type: 1
>> copy_e820_map() type is E820_RAM
>> copy_e820_map() start: 000000000ffec000 size: 0000000000003000 end:
>> 000000000ffef000 type: 3
>> copy_e820_map() start: 000000000ffef000 size: 0000000000010000 end:
>> 000000000ffff000 type: 2
>> copy_e820_map() start: 000000000ffff000 size: 0000000000001000 end:
>> 0000000010000000 type: 4
>> copy_e820_map() start: 00000000ffff0000 size: 0000000000010000 end:
>> 0000000100000000 type: 2
>>  BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
>>  BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
>>  BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
>>  BIOS-e820: 0000000000100000 - 000000000ffec000 (usable)
>>  BIOS-e820: 000000000ffec000 - 000000000ffef000 (ACPI data)
>>  BIOS-e820: 000000000ffef000 - 000000000ffff000 (reserved)
>>  BIOS-e820: 000000000ffff000 - 0000000010000000 (ACPI NVS)
>>  BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
>> BUG: unable to handle kernel paging request at virtual address
> b7c00010
>>  printing eip:
>> c044e088
>> *pde = 02f0c067
>> Oops: 0002 [#1]
>> last sysfs file: /block/hda/hda1/size
>> Modules linked in: nfsd exportfs lockd nfs_acl autofs4 hidp l2cap
>> bluetooth sunrpc dm_mirror dm_mod video sbs i2c_ec dock container
> button
>> battery asus_acpi backlight ac ipv6 lp parport_pc parport floppy
>> ohci_hcd serio_raw ide_cd i2c_ali15x3 cdrom i2c_ali1535 i2c_core
> 8139too
>> mii pcspkr ext3 jbd
>> CPU:    0
>> EIP:    0060:[<c044e088>]    Not tainted VLI
>> EFLAGS: 00010212   (2.6.20-1.2320.fc5 #1)
>> EIP is at free_pgd_range+0x5b/0x16e
>> eax: b7beffff   ebx: c5bf17c0   ecx: b7bf0000   edx: b7bfffff
>> esi: b8000000   edi: 00000000   ebp: b7c00000   esp: c3c5ef0c
>> ds: 007b   es: 007b   ss: 0068
>> Process munin-graph (pid: 6667, ti=c3c5e000 task=c6fbf3d0
> task.ti=c3c5e000)
>> Stack: b7bf0000 c3c5ef68 ccefa380 cc9ac518 c0451532 c5bf17c0 00000000
>> 00000000
>>        b7fe3000 c045056e b7fde000 b7ff0000 b7fde000 c3c5ef68 c5bf17c0
>> cd26fca4
>>        c7d510d4 cc9ac518 c0451225 b7ff0000 c3c5ef64 00000000 00000000
>> c072e31c
>> Call Trace:
>>  [<c0451532>] unlink_file_vma+0x28/0x38
>>  [<c045056e>] free_pgtables+0x90/0xa0
>>  [<c0451225>] unmap_region+0xa7/0xd7
>>  [<c0451bca>] do_munmap+0x15a/0x1af
>>  [<c0451c4f>] sys_munmap+0x30/0x3e
>>  [<c0403dc8>] syscall_call+0x7/0xb
>>  =======================
>> Code: 81 e5 00 00 c0 ff 0f 84 2a 01 00 00 8b 04 24 8d 55 ff 8b 0c 24
> 48
>> 81 e9 00 00 40 00 39 d0 0f 46 0c 24 89 0c 24 8b 04 24 48 39 c6 <89> 44
>> 24 10 0f 87 01 01 00 00 8b 54 24 04 8b 02 8b 10 89 f0 c1
>> EIP: [<c044e088>] free_pgd_range+0x5b/0x16e SS:ESP 0068:c3c5ef0c
>>  <0>general protection fault: 0000 [#2]
>> last sysfs file: /block/hda/hda1/size
>> Modules linked in: nfsd exportfs lockd nfs_acl autofs4 hidp l2cap
>> bluetooth sunrpc dm_mirror dm_mod video sbs i2c_ec dock container
> button
>> battery asus_acpi backlight ac ipv6 lp parport_pc parport floppy
>> ohci_hcd serio_raw ide_cd i2c_ali15x3 cdrom i2c_ali1535 i2c_core
> 8139too
>> mii pcspkr ext3 jbd
>> CPU:    0
>> EIP:    0060:[<c0467ad2>]    Not tainted VLI
>> EFLAGS: 00010286   (2.6.20-1.2320.fc5 #1)
>> EIP is at link_path_walk+0x26/0xaf
>> eax: cef1edac   ebx: cff97320   ecx: cffdfca0   edx: fffffffe
>> esi: cef1ee38   edi: ffffffff   ebp: cffdfca0   esp: cef1eda8
>> ds: 007b   es: 007b   ss: 0068
>> Process df (pid: 13138, ti=cef1e000 task=c5ddae90 task.ti=cef1e000)
>> Stack: cef1eede ffffffff cffdfca0 00000246 00000246 c0600289 00000001
>> 00000001
>>        00000000 000000d0 00000246 cfdb7478 00000080 cff96520 c05a6c66
>> 00000000
>>        cffe1860 c3edcd60 00000001 c3edcd60 0000006e cff97320 cff97324
>> cef1ee38
>> Call Trace:
>>  [<c0600289>] unix_sock_destructor+0x11/0xd3
>>  [<c05a6c66>] __alloc_skb+0x49/0xf7
>>  [<c0467df2>] do_path_lookup+0x173/0x1c3
>>  [<c04687fc>] path_lookup+0x14/0x16
>>  [<c05ff287>] unix_find_other+0x2a/0x17b
>>  [<c0600289>] unix_sock_destructor+0x11/0xd3
>>  [<c05a6c66>] __alloc_skb+0x49/0xf7
>>  [<c0600de7>] unix_stream_connect+0xe2/0x3aa
>>  [<c05a22af>] sys_connect+0x82/0xad
>>  [<c05a17c1>] sock_map_fd+0x41/0x4a
>>  [<c05a2afb>] sys_socketcall+0xac/0x261
>>  [<c046975e>] sys_fcntl64+0x7d/0x85
>>  [<c0403dc8>] syscall_call+0x7/0xb
>>  =======================
>> Code: 5b 5e 5f 5d c3 55 b9 50 00 00 00 57 56 89 d6 53 83 ec 54 89 04
> 24
>> 8d 44 24 04 e8 a2 05 07 00 8b 7c 24 04 8b 6c 24 08 85 ff 74 0b <83> 3f
>> 00 75 04 0f 0b eb fe ff 07 85 ed 74 03 ff 45 28 8b 04 24
>> EIP: [<c0467ad2>] link_path_walk+0x26/0xaf SS:ESP 0068:cef1eda8
>>  <1>BUG: unable to handle kernel paging request at virtual address
> fffecc69
>>  printing eip:
>> c0480c1c
>> *pde = 00002067
>> Oops: 0002 [#3]
>> last sysfs file: /block/hda/hda1/size
>> Modules linked in: nfsd exportfs lockd nfs_acl autofs4 hidp l2cap
>> bluetooth sunrpc dm_mirror dm_mod video sbs i2c_ec dock container
> button
>> battery asus_acpi backlight ac ipv6 lp parport_pc parport floppy
>> ohci_hcd serio_raw ide_cd i2c_ali15x3 cdrom i2c_ali1535 i2c_core
> 8139too
>> mii pcspkr ext3 jbd
>> CPU:    0
>> EIP:    0060:[<c0480c1c>]    Not tainted VLI
>> EFLAGS: 00010246   (2.6.20-1.2320.fc5 #1)
>> EIP is at do_mpage_readpage+0x21b/0x58f
>> eax: fffecc69   ebx: 00000000   ecx: 00000000   edx: 00001b97
>> esi: 00001b97   edi: 00000000   ebp: ca893d00   esp: ca893be9
>> ds: 007b   es: 007b   ss: 0068
>> Process rpmq (pid: 29469, ti=ca893000 task=c5ddae90 task.ti=ca893000)
>> Stack: 48000000 00000c60 00000000 e4000001 08cfcc6b 98000000 0000001b
>> 34000000
>>        40d08896 38ca893d 01ca893d 00000000 00c112b6 90000000 b4c5ddae
>> 0cc08eab
>>        01000000 98000000 0000001b 00000000 01000000 00000000 01000000
>> 00000000
>> Call Trace:
>>  =======================
>> Code: 00 00 00 00 00 c7 45 14 00 00 00 00 3b 7c 24 40 77 44 72 06 3b
> 74
>> 24 3c 73 3c 8b 44 24 3c 89 f2 8a 4c 24 34 29 f0 31 db d3 e0 f6 <c1> 20
>> 0f 45 c3 89 f9 89 45 14 8b 44 24 30 c7 44 24 04 00 00 00
>> EIP: [<c0480c1c>] do_mpage_readpage+0x21b/0x58f SS:ESP 0068:ca893be9
>>  <3>BUG: sleeping function called from invalid context at
> kernel/rwsem.c:20
>> in_atomic():0, irqs_disabled():1
>>  [<c042f150>] down_read+0x12/0x26
>>  [<c043a8b3>] acct_collect+0x38/0x141
>>  [<c041ef63>] do_exit+0x1af/0x70d
>>  [<c041d212>] printk+0x1f/0x95
>>  [<c0405285>] die+0x1f1/0x216
>>  [<c0609829>] do_page_fault+0x3fe/0x4d1
>>  [<c060942b>] do_page_fault+0x0/0x4d1
>>  [<c0608214>] error_code+0x74/0x7c
>>  [<c0480c1c>] do_mpage_readpage+0x21b/0x58f
>>  =======================
>>
>>
>> Thanks
>>
>> Pat
>> _______________________________________________
>> mdlug mailing list
>> mdlug at mdlug.org
>> http://mdlug.org/mailman/listinfo/mdlug
>> _______________________________________________
>> mdlug mailing list
>> mdlug at mdlug.org
>> http://mdlug.org/mailman/listinfo/mdlug
>
> _______________________________________________
> mdlug mailing list
> mdlug at mdlug.org
> http://mdlug.org/mailman/listinfo/mdlug
>

From lugnuts at doehler.us  Fri Feb 10 15:20:34 2012
From: lugnuts at doehler.us (Joe Doehler)
Date: Fri, 10 Feb 2012 15:20:34 -0500
Subject: [mdlug] IPv6 anyone?
In-Reply-To: <CAD39dTa7dh0F-bTqKV6ffO4d8vC15R5UwVx9uNag0kswbkrcTw@mail.gmail.com>
References: <20120116.092215.5262.1@webmail08.vgs.untd.com>
	<4F14545E.3090402@wowway.com>
	<50F4BFBDC6001340B94E13C70E39F9B00149C887@nasa-dtw-ex004.nasa.cpwr.corp>
	<1326827757.4660.5.camel@linux-dauq.site>
	<4F168A40.7050905@gmail.com> <4F353BF9.5090804@gmail.com>
	<392094381-1328889582-cardhu_decombobulator_blackberry.rim.net-263310594-@b12.c27.bise6.blackberry>
	<50F4BFBDC6001340B94E13C70E39F9B001630A7E@nasa-dtw-ex004.nasa.cpwr.corp>
	<CAD39dTa7dh0F-bTqKV6ffO4d8vC15R5UwVx9uNag0kswbkrcTw@mail.gmail.com>
Message-ID: <4F357C12.2010102@doehler.us>

Has anyone's ISP here implemented IPv6? If not, has anyone contemplated
free IPv6 services like:
http://www.he.net/
http://gogonet.gogo6.com/page/freenet6-ipv6-services

Joe.

From mikemol at gmail.com  Fri Feb 10 15:46:52 2012
From: mikemol at gmail.com (Michael Mol)
Date: Fri, 10 Feb 2012 15:46:52 -0500
Subject: [mdlug] IPv6 anyone?
In-Reply-To: <4F357C12.2010102@doehler.us>
References: <20120116.092215.5262.1@webmail08.vgs.untd.com>
	<4F14545E.3090402@wowway.com>
	<50F4BFBDC6001340B94E13C70E39F9B00149C887@nasa-dtw-ex004.nasa.cpwr.corp>
	<1326827757.4660.5.camel@linux-dauq.site>
	<4F168A40.7050905@gmail.com> <4F353BF9.5090804@gmail.com>
	<392094381-1328889582-cardhu_decombobulator_blackberry.rim.net-263310594-@b12.c27.bise6.blackberry>
	<50F4BFBDC6001340B94E13C70E39F9B001630A7E@nasa-dtw-ex004.nasa.cpwr.corp>
	<CAD39dTa7dh0F-bTqKV6ffO4d8vC15R5UwVx9uNag0kswbkrcTw@mail.gmail.com>
	<4F357C12.2010102@doehler.us>
Message-ID: <CA+czFiCx1qgrRP7Y3Cwt7U_x8nKZbpfEbohuMCzON+GRQiL3Pg@mail.gmail.com>

On Fri, Feb 10, 2012 at 3:20 PM, Joe Doehler <lugnuts at doehler.us> wrote:
> Has anyone's ISP here implemented IPv6? If not, has anyone contemplated
> free IPv6 services like:
> http://www.he.net/
> http://gogonet.gogo6.com/page/freenet6-ipv6-services

I use both. tunnelbroker.net (he.net) on my home LAN, and freenet6 on my laptop.

Charter has apparently deployed 6rd. My employer is moving to Charter
territory shortly, so I might get a chance to poke at it. I'm not the
network admin here, though.

-- 
:wq

From awilliam at whitemice.org  Fri Feb 10 16:41:01 2012
From: awilliam at whitemice.org (Adam Tauno Williams)
Date: Fri, 10 Feb 2012 16:41:01 -0500
Subject: [mdlug] IPv6 anyone?
In-Reply-To: <4F357C12.2010102@doehler.us>
References: <20120116.092215.5262.1@webmail08.vgs.untd.com>
	<4F14545E.3090402@wowway.com>
	<50F4BFBDC6001340B94E13C70E39F9B00149C887@nasa-dtw-ex004.nasa.cpwr.corp>
	<1326827757.4660.5.camel@linux-dauq.site> <4F168A40.7050905@gmail.com>
	<4F353BF9.5090804@gmail.com>
	<392094381-1328889582-cardhu_decombobulator_blackberry.rim.net-263310594-@b12.c27.bise6.blackberry>
	<50F4BFBDC6001340B94E13C70E39F9B001630A7E@nasa-dtw-ex004.nasa.cpwr.corp>
	<CAD39dTa7dh0F-bTqKV6ffO4d8vC15R5UwVx9uNag0kswbkrcTw@mail.gmail.com>
	<4F357C12.2010102@doehler.us>
Message-ID: <1328910061.3474.15.camel@linux-dauq.site>

On Fri, 2012-02-10 at 15:20 -0500, Joe Doehler wrote:
> Has anyone's ISP here implemented IPv6? If not, has anyone contemplated
> free IPv6 services like:
> http://www.he.net/

+1 Hurricane Electric

-- 
System & Network Administrator [ LPI & NCLA ]
<http://www.whitemiceconsulting.com>
OpenGroupware Developer <http://www.opengroupware.us>
Adam Tauno Williams


From carl at carltm.com  Fri Feb 10 17:48:15 2012
From: carl at carltm.com (Carl T. Miller)
Date: Fri, 10 Feb 2012 17:48:15 -0500
Subject: [mdlug] IPv6 anyone?
In-Reply-To: <4F357C12.2010102@doehler.us>
References: <20120116.092215.5262.1@webmail08.vgs.untd.com>
	<4F14545E.3090402@wowway.com>
	<50F4BFBDC6001340B94E13C70E39F9B00149C887@nasa-dtw-ex004.nasa.cpwr.corp>
	<1326827757.4660.5.camel@linux-dauq.site> <4F168A40.7050905@gmail.com>
	<4F353BF9.5090804@gmail.com>
	<392094381-1328889582-cardhu_decombobulator_blackberry.rim.net-263310594-@b12.c27.bise6.blackberry>
	<50F4BFBDC6001340B94E13C70E39F9B001630A7E@nasa-dtw-ex004.nasa.cpwr.corp>
	<CAD39dTa7dh0F-bTqKV6ffO4d8vC15R5UwVx9uNag0kswbkrcTw@mail.gmail.com>
	<4F357C12.2010102@doehler.us>
Message-ID: <2ca8b7684c3c096eddfca05bee0a3a83.squirrel@mail.carltm.com>

Joe Doehler wrote:
> Has anyone's ISP here implemented IPv6? If not, has anyone contemplated
> free IPv6 services like:
> http://www.he.net/

Contemplated.  Tested.  Used.  Put into production.  Twice.

I'm currently using he.net for a VPS, a server at home and
several workstations.  It was rather easy to set up and has
worked flawlessly for several weeks.

c



From mat.enders at gmail.com  Fri Feb 10 18:28:52 2012
From: mat.enders at gmail.com (Mat Enders)
Date: Fri, 10 Feb 2012 23:28:52 +0000
Subject: [mdlug] Fw: MDLUG and job opportunities
Message-ID: <917947886-1328916532-cardhu_decombobulator_blackberry.rim.net-575245744-@b12.c27.bise6.blackberry>

No endorsement just passing it along. 
Mat Enders from my BlackBerry?

-----Original Message-----
From: Joseph Fleming <joseph.fleming at autodesk.com>
Date: Fri, 10 Feb 2012 18:06:15 
To: president at mdlug.org<president at mdlug.org>
Subject: MDLUG and job opportunities

Hi,

I run the Southeast Michigan chapter of PASS (Professional Association for SQL Server) and one of my members pointed me in your direction last night when I mentioned that my company was looking for Java and Linux people.  We're getting a new product off the ground and need some really seasoned folks to help us out with it.  I'm the DBA, we've got a growing team of Java guys, and one Linux admin based in Toronto.  We're looking to add one in Novi and I was wondering if your group was open to discussing job opportunities and if so, what the best way to approach them would be.

I'm not a recruiter, and I don't want to spam your members with crap, as I hate it when people try to do that to my UG members.  I do have an opportunity with an awesome company with great pay and benefits, though :)

Let me know the way you'd prefer to approach this, or if you'd prefer I jump in a lake.

Thanks,
Joe Fleming


From rjclay at gmail.com  Fri Feb 10 18:24:11 2012
From: rjclay at gmail.com (Robert J. Clay)
Date: Fri, 10 Feb 2012 18:24:11 -0500
Subject: [mdlug] IPv6 anyone?
In-Reply-To: <4F357C12.2010102@doehler.us>
References: <20120116.092215.5262.1@webmail08.vgs.untd.com>
	<4F14545E.3090402@wowway.com>
	<50F4BFBDC6001340B94E13C70E39F9B00149C887@nasa-dtw-ex004.nasa.cpwr.corp>
	<1326827757.4660.5.camel@linux-dauq.site>
	<4F168A40.7050905@gmail.com> <4F353BF9.5090804@gmail.com>
	<392094381-1328889582-cardhu_decombobulator_blackberry.rim.net-263310594-@b12.c27.bise6.blackberry>
	<50F4BFBDC6001340B94E13C70E39F9B001630A7E@nasa-dtw-ex004.nasa.cpwr.corp>
	<CAD39dTa7dh0F-bTqKV6ffO4d8vC15R5UwVx9uNag0kswbkrcTw@mail.gmail.com>
	<4F357C12.2010102@doehler.us>
Message-ID: <CAL4BjXk0OgqAaeDFKAhxziEyW38cGvtwLpBEc-Rs7xiF4vjs+w@mail.gmail.com>

Joe,

On Fri, Feb 10, 2012 at 3:20 PM, Joe Doehler <lugnuts at doehler.us> wrote:
> Has anyone's ISP here implemented IPv6? If not, has anyone contemplated
> free IPv6 services like:
> http://www.he.net/

      That's what I use on my home network.   Recently changed the
install on my netbook to Debian Testing;  have toredo enabled on it,
don't know what else I might set up.



-- 
Robert J. Clay
rjclay at gmail.com

From otakurider at gmail.com  Sat Feb 11 10:24:16 2012
From: otakurider at gmail.com (Gmail-otakurider)
Date: Sat, 11 Feb 2012 10:24:16 -0500
Subject: [mdlug] My cloud presentation -canceled
In-Reply-To: <4F357C12.2010102@doehler.us>
References: <20120116.092215.5262.1@webmail08.vgs.untd.com>
	<4F14545E.3090402@wowway.com>
	<50F4BFBDC6001340B94E13C70E39F9B00149C887@nasa-dtw-ex004.nasa.cpwr.corp>
	<1326827757.4660.5.camel@linux-dauq.site>
	<4F168A40.7050905@gmail.com> <4F353BF9.5090804@gmail.com>
	<392094381-1328889582-cardhu_decombobulator_blackberry.rim.net-263310594-@b12.c27.bise6.blackberry>
	<50F4BFBDC6001340B94E13C70E39F9B001630A7E@nasa-dtw-ex004.nasa.cpwr.corp>
	<CAD39dTa7dh0F-bTqKV6ffO4d8vC15R5UwVx9uNag0kswbkrcTw@mail.gmail.com>
	<4F357C12.2010102@doehler.us>
Message-ID: <4F368820.5040005@gmail.com>


Sorry all
 
 Have to cancel the cloud presentation for today  - put me down for next
month.

Pat.

From lugnuts at doehler.us  Sat Feb 11 10:46:57 2012
From: lugnuts at doehler.us (Joe Doehler)
Date: Sat, 11 Feb 2012 10:46:57 -0500
Subject: [mdlug] IPv6 anyone?
In-Reply-To: <2ca8b7684c3c096eddfca05bee0a3a83.squirrel@mail.carltm.com>
References: <20120116.092215.5262.1@webmail08.vgs.untd.com>
	<4F14545E.3090402@wowway.com>
	<50F4BFBDC6001340B94E13C70E39F9B00149C887@nasa-dtw-ex004.nasa.cpwr.corp>
	<1326827757.4660.5.camel@linux-dauq.site>
	<4F168A40.7050905@gmail.com> <4F353BF9.5090804@gmail.com>
	<392094381-1328889582-cardhu_decombobulator_blackberry.rim.net-263310594-@b12.c27.bise6.blackberry>
	<50F4BFBDC6001340B94E13C70E39F9B001630A7E@nasa-dtw-ex004.nasa.cpwr.corp>
	<CAD39dTa7dh0F-bTqKV6ffO4d8vC15R5UwVx9uNag0kswbkrcTw@mail.gmail.com>
	<4F357C12.2010102@doehler.us>
	<2ca8b7684c3c096eddfca05bee0a3a83.squirrel@mail.carltm.com>
Message-ID: <4F368D71.2090808@doehler.us>

On 2/10/2012 5:48 PM, Carl T. Miller wrote:
> Joe Doehler wrote:
>> Has anyone's ISP here implemented IPv6? If not, has anyone
>> contemplated free IPv6 services like: http://www.he.net/
>
> Contemplated.  Tested.  Used.  Put into production.  Twice.
>
> I'm currently using he.net for a VPS, a server at home and several
> workstations.  It was rather easy to set up and has worked flawlessly
> for several weeks.

Thanks to all who answered. Looks like "he.net" is a good way to go. I
have older devices on my home network that speak only IPv4, so I'll
leave that subnet alone. But my e-mail/web server (Ubuntu 10.10) is on a
different, dedicated IP, and I'll play with that.

Joe.

From mikemol at gmail.com  Sat Feb 11 11:29:55 2012
From: mikemol at gmail.com (Michael Mol)
Date: Sat, 11 Feb 2012 11:29:55 -0500
Subject: [mdlug] IPv6 anyone?
In-Reply-To: <4F368D71.2090808@doehler.us>
References: <20120116.092215.5262.1@webmail08.vgs.untd.com>
	<4F14545E.3090402@wowway.com>
	<50F4BFBDC6001340B94E13C70E39F9B00149C887@nasa-dtw-ex004.nasa.cpwr.corp>
	<1326827757.4660.5.camel@linux-dauq.site>
	<4F168A40.7050905@gmail.com> <4F353BF9.5090804@gmail.com>
	<392094381-1328889582-cardhu_decombobulator_blackberry.rim.net-263310594-@b12.c27.bise6.blackberry>
	<50F4BFBDC6001340B94E13C70E39F9B001630A7E@nasa-dtw-ex004.nasa.cpwr.corp>
	<CAD39dTa7dh0F-bTqKV6ffO4d8vC15R5UwVx9uNag0kswbkrcTw@mail.gmail.com>
	<4F357C12.2010102@doehler.us>
	<2ca8b7684c3c096eddfca05bee0a3a83.squirrel@mail.carltm.com>
	<4F368D71.2090808@doehler.us>
Message-ID: <CA+czFiD6OYwsW04hyxRQwa6tcvbysmhf5FKLfM6ZaAJfJmJH5A@mail.gmail.com>

On Sat, Feb 11, 2012 at 10:46 AM, Joe Doehler <lugnuts at doehler.us> wrote:
> On 2/10/2012 5:48 PM, Carl T. Miller wrote:
>> Joe Doehler wrote:
>>> Has anyone's ISP here implemented IPv6? If not, has anyone
>>> contemplated free IPv6 services like: http://www.he.net/
>>
>> Contemplated. ?Tested. ?Used. ?Put into production. ?Twice.
>>
>> I'm currently using he.net for a VPS, a server at home and several
>> workstations. ?It was rather easy to set up and has worked flawlessly
>> for several weeks.
>
> Thanks to all who answered. Looks like "he.net" is a good way to go. I
> have older devices on my home network that speak only IPv4, so I'll
> leave that subnet alone. But my e-mail/web server (Ubuntu 10.10) is on a
> different, dedicated IP, and I'll play with that.

The recommended approach is to have both IPv6 and IPv4 on the same
network. This is called dual-stack. Devices on the network which
support IPv4 will tie into that, devices which support IPv6 will tie
into that, devices which support both will tie into both.

My entire network at home is dual-stacked. The devices which are
IPv4-only (a wireless AP's management interface, and the PS3) interact
fine with devices which support both (everything else).

It's not an either/or thing; you can (and should) have both IPv6 and IPv4.

-- 
:wq

From artdries at yahoo.com  Sun Feb 12 07:51:14 2012
From: artdries at yahoo.com (Art Dries)
Date: Sun, 12 Feb 2012 04:51:14 -0800 (PST)
Subject: [mdlug] hanging machine kernel panic
Message-ID: <1329051074.36045.yint-ygo-j2me@web110616.mail.gq1.yahoo.com>


Almost all kernel panics under Linux are hardware related

I suggest a cleaning/reseating of all your memory modules.

I had a problem with a new system where a module wasn't entirely seated into the slot.

A dusting inside the case wouldn't hurt either.

From tesral at wowway.com  Sun Feb 12 08:34:54 2012
From: tesral at wowway.com (Garry Stahl)
Date: Sun, 12 Feb 2012 08:34:54 -0500
Subject: [mdlug] hanging machine kernel panic
In-Reply-To: <1329051074.36045.yint-ygo-j2me@web110616.mail.gq1.yahoo.com>
References: <1329051074.36045.yint-ygo-j2me@web110616.mail.gq1.yahoo.com>
Message-ID: <4F37BFFE.4080500@wowway.com>

On 02/12/2012 07:51 AM, Art Dries wrote:
> Almost all kernel panics under Linux are hardware related
>
I had that one Thinkpad 600X that would kernel panic booting Ubuntu in a 
predicable 15 seconds, but would run anything else.  We never did sort 
that out.  Version didn't matter either.


-- 
Garry  AKA  --Phoenix--  Rising above the Flames.

Politically I have given up on being an anything-arian. I am for accountability and nothing else. Hold the government, in specific the office holders, elected or appointed, accountable for all actions taken in office. Authority must be granted grudgingly and reluctantly. When it is abused it must be snatched away at once. Be it a minimum wage screener at the TSA or the President of the United States.
Star Trek mort. Viva la Star Trek admiraetur
The Olde Phoenix Inn http://phoenixinn.iwarp.com
Metro Detroit Linux Users Group http://www.mdlug.org


From mikemol at gmail.com  Sun Feb 12 10:41:57 2012
From: mikemol at gmail.com (Michael Mol)
Date: Sun, 12 Feb 2012 10:41:57 -0500
Subject: [mdlug] hanging machine kernel panic
In-Reply-To: <4F37BFFE.4080500@wowway.com>
References: <1329051074.36045.yint-ygo-j2me@web110616.mail.gq1.yahoo.com>
	<4F37BFFE.4080500@wowway.com>
Message-ID: <CA+czFiD9=Ccp=+202FJMr+ugDxXFo84GLrxjXvrCdQoOHZG=xA@mail.gmail.com>

On Sun, Feb 12, 2012 at 8:34 AM, Garry Stahl <tesral at wowway.com> wrote:
> On 02/12/2012 07:51 AM, Art Dries wrote:
>> Almost all kernel panics under Linux are hardware related
>>
> I had that one Thinkpad 600X that would kernel panic booting Ubuntu in a
> predicable 15 seconds, but would run anything else. ?We never did sort
> that out. ?Version didn't matter either.

Laptops have notoriously buggy BIOS. Walk through the kernel
configuration process end to end some time and note all the
workarounds. You can bet those systems were only tested against
Windows when they were designed, so it's likely anything that would
have tripped Windows was fixed. Not a Linux-hating thing, just bad Q/A
at the design stage.

-- 
:wq

From awilliam at whitemice.org  Sun Feb 12 10:48:06 2012
From: awilliam at whitemice.org (Adam Tauno Williams)
Date: Sun, 12 Feb 2012 10:48:06 -0500
Subject: [mdlug] hanging machine kernel panic
In-Reply-To: <CA+czFiD9=Ccp=+202FJMr+ugDxXFo84GLrxjXvrCdQoOHZG=xA@mail.gmail.com>
References: <1329051074.36045.yint-ygo-j2me@web110616.mail.gq1.yahoo.com>
	<4F37BFFE.4080500@wowway.com>
	<CA+czFiD9=Ccp=+202FJMr+ugDxXFo84GLrxjXvrCdQoOHZG=xA@mail.gmail.com>
Message-ID: <1329061686.3307.5.camel@linux-dauq.site>

On Sun, 2012-02-12 at 10:41 -0500, Michael Mol wrote:
> On Sun, Feb 12, 2012 at 8:34 AM, Garry Stahl <tesral at wowway.com> wrote:
> > On 02/12/2012 07:51 AM, Art Dries wrote:
> >> Almost all kernel panics under Linux are hardware related
> > I had that one Thinkpad 600X that would kernel panic booting Ubuntu in a
> > predicable 15 seconds, but would run anything else.  We never did sort
> > that out.  Version didn't matter either.
> Laptops have notoriously buggy BIOS. Walk through the kernel
> configuration process end to end some time and note all the
> workarounds. You can bet those systems were only tested against
> Windows when they were designed, so it's likely anything that would
> have tripped Windows was fixed. Not a Linux-hating thing, just bad Q/A
> at the design stage.

Try booting with acpi=off, noapic, etc... to see if that makes to
lock-up not happen.  Also try booting into run level 3 [no X] and see if
the machine is stable that way.

Since you have ~15 seconds you might be able to login and disable DMA on
the SATA channels.

Possibly Ubuntu offer's multiple kernels [openSUSE does, no clue about
Ubuntu].  You can switch around the kernels to see if one of them is
more/less stable.

-- 
System & Network Administrator [ LPI & NCLA ]
<http://www.whitemiceconsulting.com>
OpenGroupware Developer <http://www.opengroupware.us>
Adam Tauno Williams


From tesral at wowway.com  Sun Feb 12 11:58:10 2012
From: tesral at wowway.com (Garry Stahl)
Date: Sun, 12 Feb 2012 11:58:10 -0500
Subject: [mdlug] hanging machine kernel panic
In-Reply-To: <1329061686.3307.5.camel@linux-dauq.site>
References: <1329051074.36045.yint-ygo-j2me@web110616.mail.gq1.yahoo.com>	<4F37BFFE.4080500@wowway.com>	<CA+czFiD9=Ccp=+202FJMr+ugDxXFo84GLrxjXvrCdQoOHZG=xA@mail.gmail.com>
	<1329061686.3307.5.camel@linux-dauq.site>
Message-ID: <4F37EFA2.6070906@wowway.com>

On 02/12/2012 10:48 AM, Adam Tauno Williams wrote:
> Try booting with acpi=off, noapic, etc... to see if that makes to
> lock-up not happen.  Also try booting into run level 3 [no X] and see if
> the machine is stable that way.

Academic.  I gave that laptop away some time ago.

-- 
Garry  AKA  --Phoenix--  Rising above the Flames.

Politically I have given up on being an anything-arian. I am for accountability and nothing else. Hold the government, in specific the office holders, elected or appointed, accountable for all actions taken in office. Authority must be granted grudgingly and reluctantly. When it is abused it must be snatched away at once. Be it a minimum wage screener at the TSA or the President of the United States.
Star Trek mort. Viva la Star Trek admiraetur
The Olde Phoenix Inn http://phoenixinn.iwarp.com
Metro Detroit Linux Users Group http://www.mdlug.org


From skyefire at skyefire.org  Sun Feb 12 13:58:56 2012
From: skyefire at skyefire.org (David McMillan)
Date: Sun, 12 Feb 2012 13:58:56 -0500
Subject: [mdlug] Fixing a Dell Precision server
Message-ID: <4F380BF0.3030600@skyefire.org>


	Running Windows, alas.  But it's for a local nonprofit that can't 
easily afford a shop repair or to replace the machine.

	It was running fine until recently, when the BIOS began giving warnings 
that the BIOS battery needed replacing.  Well, someone went ahead and 
replaced the battery... with the machine off, which obviously wiped any 
non-factory BIOS settings.  Now the BIOS won't recognize the hard drive.
	The kicker is, the main hard drive is SCSI (which I have zero 
experience with), plugs directly into the motherboard, and is (as far as 
I have been able to determine) the original factory configuration.

	So, since everything else was operating fine, my best guess is that the 
BIOS needs adjusting to use the SCSI drive as a boot device.  Although 
*why* this would be, when the SCSI drive was factory-original, confuses 
me.  The problem is, when the nonprofit's in-house "computer guy" 
contacted Dell with the service tag#, Dell told him that BIOS upgrades 
for this computer are no longer available.

	So, now the thing's landed in my lap.  I'm guessing it should be *that* 
hard -- the BIOS firmware shouldn't have been changed by the battery 
change, just the settings, correct?  It should just be a matter of 
figuring out what the right BIOS settings are.  But since I've *never* 
used SCSI in my life, well... any guidance from more knowledgeable 
people would be appreciated.

	Now I'm going to go boot it with a Linux CD and see what a hardware 
scan says....



From mat.enders at gmail.com  Sun Feb 12 14:25:38 2012
From: mat.enders at gmail.com (Mat Enders)
Date: Sun, 12 Feb 2012 19:25:38 +0000
Subject: [mdlug] Fixing a Dell Precision server
In-Reply-To: <4F380BF0.3030600@skyefire.org>
References: <4F380BF0.3030600@skyefire.org>
Message-ID: <521978980-1329074739-cardhu_decombobulator_blackberry.rim.net-526806484-@b12.c27.bise6.blackberry>

Replacing the cmos battery may have been coincidental. What was the up time before that?  When running the live cd does it see the SCSI bus?  If it sees the bus does it see the drive?  
Mat Enders from my BlackBerry?

-----Original Message-----
From: David McMillan <skyefire at skyefire.org>
Sender: mdlug-bounces at mdlug.org
Date: Sun, 12 Feb 2012 13:58:56 
To: <mdlug at mdlug.org>
Reply-To: MDLUG's Main discussion list <mdlug at mdlug.org>
Subject: [mdlug] Fixing a Dell Precision server


	Running Windows, alas.  But it's for a local nonprofit that can't 
easily afford a shop repair or to replace the machine.

	It was running fine until recently, when the BIOS began giving warnings 
that the BIOS battery needed replacing.  Well, someone went ahead and 
replaced the battery... with the machine off, which obviously wiped any 
non-factory BIOS settings.  Now the BIOS won't recognize the hard drive.
	The kicker is, the main hard drive is SCSI (which I have zero 
experience with), plugs directly into the motherboard, and is (as far as 
I have been able to determine) the original factory configuration.

	So, since everything else was operating fine, my best guess is that the 
BIOS needs adjusting to use the SCSI drive as a boot device.  Although 
*why* this would be, when the SCSI drive was factory-original, confuses 
me.  The problem is, when the nonprofit's in-house "computer guy" 
contacted Dell with the service tag#, Dell told him that BIOS upgrades 
for this computer are no longer available.

	So, now the thing's landed in my lap.  I'm guessing it should be *that* 
hard -- the BIOS firmware shouldn't have been changed by the battery 
change, just the settings, correct?  It should just be a matter of 
figuring out what the right BIOS settings are.  But since I've *never* 
used SCSI in my life, well... any guidance from more knowledgeable 
people would be appreciated.

	Now I'm going to go boot it with a Linux CD and see what a hardware 
scan says....


_______________________________________________
mdlug mailing list
mdlug at mdlug.org
http://mdlug.org/mailman/listinfo/mdlug

From carl at carltm.com  Sun Feb 12 16:48:14 2012
From: carl at carltm.com (Carl T. Miller)
Date: Sun, 12 Feb 2012 16:48:14 -0500
Subject: [mdlug] Fixing a Dell Precision server
In-Reply-To: <521978980-1329074739-cardhu_decombobulator_blackberry.rim.net-526806484-@b12.c27.bise6.blackberry>
References: <4F380BF0.3030600@skyefire.org>
	<521978980-1329074739-cardhu_decombobulator_blackberry.rim.net-526806484-@b12.c27.bise6.blackberry>
Message-ID: <27861f8f8490683362124330622c1ce6.squirrel@mail.carltm.com>

It's also possible that the person who changed the
battery did some other tinkering.  When you boot the
computer, do you see something about a SCSI controller,
a RAID controller or a PERC device?  There is probably
a message to press a key combination within 5 seconds
to configure it.

c


Mat Enders wrote:
> Replacing the cmos battery may have been coincidental. What was the up
> time before that?  When running the live cd does it see the SCSI bus?  If
> it sees the bus does it see the drive?
> Mat Enders from my BlackBerry?
>
> -----Original Message-----
> From: David McMillan <skyefire at skyefire.org>
> Sender: mdlug-bounces at mdlug.org
> Date: Sun, 12 Feb 2012 13:58:56
> To: <mdlug at mdlug.org>
> Reply-To: MDLUG's Main discussion list <mdlug at mdlug.org>
> Subject: [mdlug] Fixing a Dell Precision server
>
>
> 	Running Windows, alas.  But it's for a local nonprofit that can't
> easily afford a shop repair or to replace the machine.
>
> 	It was running fine until recently, when the BIOS began giving warnings
> that the BIOS battery needed replacing.  Well, someone went ahead and
> replaced the battery... with the machine off, which obviously wiped any
> non-factory BIOS settings.  Now the BIOS won't recognize the hard drive.
> 	The kicker is, the main hard drive is SCSI (which I have zero
> experience with), plugs directly into the motherboard, and is (as far as
> I have been able to determine) the original factory configuration.
>
> 	So, since everything else was operating fine, my best guess is that the
> BIOS needs adjusting to use the SCSI drive as a boot device.  Although
> *why* this would be, when the SCSI drive was factory-original, confuses
> me.  The problem is, when the nonprofit's in-house "computer guy"
> contacted Dell with the service tag#, Dell told him that BIOS upgrades
> for this computer are no longer available.
>
> 	So, now the thing's landed in my lap.  I'm guessing it should be *that*
> hard -- the BIOS firmware shouldn't have been changed by the battery
> change, just the settings, correct?  It should just be a matter of
> figuring out what the right BIOS settings are.  But since I've *never*
> used SCSI in my life, well... any guidance from more knowledgeable
> people would be appreciated.
>
> 	Now I'm going to go boot it with a Linux CD and see what a hardware
> scan says....
>
>
> _______________________________________________
> mdlug mailing list
> mdlug at mdlug.org
> http://mdlug.org/mailman/listinfo/mdlug
> _______________________________________________
> mdlug mailing list
> mdlug at mdlug.org
> http://mdlug.org/mailman/listinfo/mdlug
>



From skyefire at skyefire.org  Sun Feb 12 19:39:03 2012
From: skyefire at skyefire.org (David McMillan)
Date: Sun, 12 Feb 2012 19:39:03 -0500
Subject: [mdlug] Fixing a Dell Precision server
In-Reply-To: <521978980-1329074739-cardhu_decombobulator_blackberry.rim.net-526806484-@b12.c27.bise6.blackberry>
References: <4F380BF0.3030600@skyefire.org>
	<521978980-1329074739-cardhu_decombobulator_blackberry.rim.net-526806484-@b12.c27.bise6.blackberry>
Message-ID: <4F385BA7.3030400@skyefire.org>

On 2/12/2012 2:25 PM, Mat Enders wrote:

> Replacing the cmos battery may have been coincidental. What was the up time before that?  When running the live cd does it see the SCSI bus?  If it sees the bus does it see the drive?

	Well that was a molehill rather than a mountain.  On first boot, I went 
into the BIOS setting in order to set the (IDE) CD-ROM as a boot device. 
  And while cruising through the settings, under "Integrated 
Peripherals", guess what?  There was an entry for the mobo SCSI 
controller, and it was set to "Off."  Switched in "On," rebooted, and 
the whole shebang worked -- XP booted perfectly.  So it looks like, for 
whatever reason, a BIOS reset shuts off the SCSI controller on this 
model of workstation.
	I do appreciate all the responses, though.  I honestly thought this was 
going to be a bigger deal.


From carl at carltm.com  Sun Feb 12 20:31:38 2012
From: carl at carltm.com (Carl T. Miller)
Date: Sun, 12 Feb 2012 20:31:38 -0500
Subject: [mdlug] Fixing a Dell Precision server
In-Reply-To: <4F385BA7.3030400@skyefire.org>
References: <4F380BF0.3030600@skyefire.org>
	<521978980-1329074739-cardhu_decombobulator_blackberry.rim.net-526806484-@b12.c27.bise6.blackberry>
	<4F385BA7.3030400@skyefire.org>
Message-ID: <9fbe756f61af64525607ab0bfee39148.squirrel@mail.carltm.com>

David McMillan wrote:
> 	Well that was a molehill rather than a mountain.  On first boot, I went
> into the BIOS setting in order to set the (IDE) CD-ROM as a boot device.
>   And while cruising through the settings, under "Integrated
> Peripherals", guess what?  There was an entry for the mobo SCSI
> controller, and it was set to "Off."  Switched in "On," rebooted, and
> the whole shebang worked -- XP booted perfectly.  So it looks like, for
> whatever reason, a BIOS reset shuts off the SCSI controller on this
> model of workstation.
> 	I do appreciate all the responses, though.  I honestly thought this was
> going to be a bigger deal.

Very cool.  I'm glad to hear that it was something easy.

c



From gib at juno.com  Fri Feb 17 19:06:51 2012
From: gib at juno.com (gib@juno.com)
Date: Sat, 18 Feb 2012 00:06:51 GMT
Subject: [mdlug] Video - Wireless YPSI: free WIFI should be provided
	whereever people g	ather
Message-ID: <20120217.190651.26993.0@webmail02.vgs.untd.com>

http://www.youtube.com/watch?v=eTRRzpRIyeM

This is a video recorded during the Michigan User Group (mug.org) meeting 2/14/2012. It is a presentation by Steve Pierce President of HDL (hdl.com).  He presents the positive open position that free WIFI should be provided whereever people gather. He describes a $200 (US) device that can be used to provide the free connection to people nearby when the device can find a connection to the internet. The device can be used to extend that range of existing WIFI too. Examples of community projects include free WIFI (Wireless YPSI) in YPSI and "Open Dearborn". 2.1 Gig, 1:40  Note poor quality video is due to a cheap camera.


Related Links:
Wireless YPSI: 
http://www.metromodemedia.com/devnews/wirelessypsi0051.aspx

Open Dearborn:
http://www.metromodemedia.com/devnews/opendearborn0076.aspx


____________________________________________________________
Groupon&#8482 Official Site
1 ridiculously huge coupon a day. Get 50-90% off your city&#39;s best!
http://thirdpartyoffers.juno.com/TGL3131/4f3eebdf7a4d110a85fcst03vuc

From carl at carltm.com  Sun Feb 19 18:16:53 2012
From: carl at carltm.com (Carl T. Miller)
Date: Sun, 19 Feb 2012 18:16:53 -0500
Subject: [mdlug] [Fwd: Join us for virtual "Build a Cloud" day(s) featuring
 top open source cloud experts and strategists!]
Message-ID: <def5d4b7e9a7183782502b682f165ee1.squirrel@mail.carltm.com>

A few people have talked about clouds, and here is some
info about a free two day session about building a cloud.

<http://cloudstack.org/blog/114-virtual-build-a-cloud-day-2-28-2-29.html>

c



From nk.oorda at gmail.com  Sun Feb 26 00:13:54 2012
From: nk.oorda at gmail.com (nk oorda)
Date: Sun, 26 Feb 2012 10:43:54 +0530
Subject: [mdlug] CentOS for Production (CentOS 6.0 Vs 6.1 Vs 6.2)
Message-ID: <CAJmxLYi0FeN8iU8RAQ6fWXLxct4J4ytUZBvJC7YXn0Xt56ziWw@mail.gmail.com>

Hi

We are currently using CentOS 5.3 for production systems.

The application/software/package we are using mainly:
- Apache
- Tomcat
- SOLR
- Mysql

We are in process to upgrade the CentOS.

What would be the best CentOS candidate for upgrade (CentOS 6.0 Vs 6.1 Vs
6.2)

We are using both physical and virtual system.

Best Regards
NK

From carl at carltm.com  Sun Feb 26 04:30:11 2012
From: carl at carltm.com (Carl T. Miller)
Date: Sun, 26 Feb 2012 04:30:11 -0500
Subject: [mdlug] CentOS for Production (CentOS 6.0 Vs 6.1 Vs 6.2)
In-Reply-To: <CAJmxLYi0FeN8iU8RAQ6fWXLxct4J4ytUZBvJC7YXn0Xt56ziWw@mail.gmail.com>
References: <CAJmxLYi0FeN8iU8RAQ6fWXLxct4J4ytUZBvJC7YXn0Xt56ziWw@mail.gmail.com>
Message-ID: <6076f31e13a4b367fcd2ed7dadec36ed.squirrel@mail.carltm.com>

nk oorda wrote:
> What would be the best CentOS candidate for upgrade (CentOS 6.0 Vs 6.1 Vs
> 6.2)
>
> We are using both physical and virtual system.

Unless you have a very good reason, it's best to go with
the most recent version.  Also it's important to apply
the updates that become available, which will keep you
on the most recent version.  This is true for both
physical and virtual machines.

A couple of thoughts.  You shouldn't try to upgrade
from 5.3 to 6.2.  It would be better to back up the
entire system then do a fresh install of 6.2.  Also
I'd recommend that you find another system to test
your applications on 6.2 just to make sure there
aren't any surprises.

c



From billings at negate.org  Sun Feb 26 09:32:21 2012
From: billings at negate.org (Jonathan Billings)
Date: Sun, 26 Feb 2012 09:32:21 -0500
Subject: [mdlug] CentOS for Production (CentOS 6.0 Vs 6.1 Vs 6.2)
In-Reply-To: <CAJmxLYi0FeN8iU8RAQ6fWXLxct4J4ytUZBvJC7YXn0Xt56ziWw@mail.gmail.com>
References: <CAJmxLYi0FeN8iU8RAQ6fWXLxct4J4ytUZBvJC7YXn0Xt56ziWw@mail.gmail.com>
Message-ID: <20120226143221.GA1635@proton.local>

On Boomtime, the 57th of Chaos, 3178 , nk oorda said:
> What would be the best CentOS candidate for upgrade (CentOS 6.0 Vs 6.1 Vs
> 6.2)

Any CentOS 6 release earlier than CentOS 6.2 has a trivially
exploitable kernel.  (see
http://rhn.redhat.com/errata/RHSA-2012-0052.html)  Of course, the same
could be said of CentOS 5.3 kernels, which have had many updates since
it was released.  I'm going to assume you've kept it up to date and
just installed it as 5.3.

Basically, you don't choose the point release (unless you pay for an
extended support contract for RHEL), and you update to the latest
point release release when it comes out.  You can download the
installation media for CentOS 6.0, 6.1 or 6.2, but as soon as you run
'yum update', you'll be updated to the latest 6.2 updates.


-- 
Jonathan Billings <billings at negate.org>

From awilliam at whitemice.org  Sun Feb 26 10:00:03 2012
From: awilliam at whitemice.org (Adam Tauno Williams)
Date: Sun, 26 Feb 2012 10:00:03 -0500
Subject: [mdlug] CentOS for Production (CentOS 6.0 Vs 6.1 Vs 6.2)
In-Reply-To: <CAJmxLYi0FeN8iU8RAQ6fWXLxct4J4ytUZBvJC7YXn0Xt56ziWw@mail.gmail.com>
References: <CAJmxLYi0FeN8iU8RAQ6fWXLxct4J4ytUZBvJC7YXn0Xt56ziWw@mail.gmail.com>
Message-ID: <1330268403.3990.0.camel@linux-dauq.site>

On Sun, 2012-02-26 at 10:43 +0530, nk oorda wrote:
> We are currently using CentOS 5.3 for production systems.
> The application/software/package we are using mainly:
> - Apache
> - Tomcat
> - SOLR
> - Mysql
> We are in process to upgrade the CentOS.
> What would be the best CentOS candidate for upgrade (CentOS 6.0 Vs 6.1 Vs
> 6.2)
> We are using both physical and virtual system.

I'd use 6.2;  I cannot really think of a reason to hold back to older
versions.

-- 
System & Network Administrator [ LPI & NCLA ]
<http://www.whitemiceconsulting.com>
OpenGroupware Developer <http://www.opengroupware.us>
Adam Tauno Williams


From awilliam at whitemice.org  Sun Feb 26 10:01:05 2012
From: awilliam at whitemice.org (Adam Tauno Williams)
Date: Sun, 26 Feb 2012 10:01:05 -0500
Subject: [mdlug] CentOS for Production (CentOS 6.0 Vs 6.1 Vs 6.2)
In-Reply-To: <6076f31e13a4b367fcd2ed7dadec36ed.squirrel@mail.carltm.com>
References: <CAJmxLYi0FeN8iU8RAQ6fWXLxct4J4ytUZBvJC7YXn0Xt56ziWw@mail.gmail.com>
	<6076f31e13a4b367fcd2ed7dadec36ed.squirrel@mail.carltm.com>
Message-ID: <1330268465.3990.1.camel@linux-dauq.site>

On Sun, 2012-02-26 at 04:30 -0500, Carl T. Miller wrote:
> A couple of thoughts.  You shouldn't try to upgrade
> from 5.3 to 6.2.  It would be better to back up the
> entire system then do a fresh install of 6.2.  Also
> I'd recommend that you find another system to test
> your applications on 6.2 just to make sure there
> aren't any surprises.

+1  This is especially true if you compile any code yourself.  The
versions of gcc and it's attendants have changed significantly.

-- 
System & Network Administrator [ LPI & NCLA ]
<http://www.whitemiceconsulting.com>
OpenGroupware Developer <http://www.opengroupware.us>
Adam Tauno Williams


From nk.oorda at gmail.com  Sun Feb 26 11:57:07 2012
From: nk.oorda at gmail.com (nk oorda)
Date: Sun, 26 Feb 2012 22:27:07 +0530
Subject: [mdlug] CentOS for Production (CentOS 6.0 Vs 6.1 Vs 6.2)
In-Reply-To: <1330268465.3990.1.camel@linux-dauq.site>
References: <CAJmxLYi0FeN8iU8RAQ6fWXLxct4J4ytUZBvJC7YXn0Xt56ziWw@mail.gmail.com>
	<6076f31e13a4b367fcd2ed7dadec36ed.squirrel@mail.carltm.com>
	<1330268465.3990.1.camel@linux-dauq.site>
Message-ID: <CAJmxLYjww3VEFCWxGh3nXjmvMYV5HUV_Z3M1x2Qo0jwJZFnB6g@mail.gmail.com>

Hi

Thank you all for the suggestions.

will go by CentOS 6.2 and patch it as and when required.


--NK

On Sun, Feb 26, 2012 at 8:31 PM, Adam Tauno Williams <awilliam at whitemice.org
> wrote:

> On Sun, 2012-02-26 at 04:30 -0500, Carl T. Miller wrote:
> > A couple of thoughts.  You shouldn't try to upgrade
> > from 5.3 to 6.2.  It would be better to back up the
> > entire system then do a fresh install of 6.2.  Also
> > I'd recommend that you find another system to test
> > your applications on 6.2 just to make sure there
> > aren't any surprises.
>
> +1  This is especially true if you compile any code yourself.  The
> versions of gcc and it's attendants have changed significantly.
>
> --
> System & Network Administrator [ LPI & NCLA ]
> <http://www.whitemiceconsulting.com>
> OpenGroupware Developer <http://www.opengroupware.us>
> Adam Tauno Williams
>
> _______________________________________________
> mdlug mailing list
> mdlug at mdlug.org
> http://mdlug.org/mailman/listinfo/mdlug
>

From akulkis00 at gmail.com  Sun Feb 26 23:10:49 2012
From: akulkis00 at gmail.com (Aaron Kulkis)
Date: Sun, 26 Feb 2012 23:10:49 -0500
Subject: [mdlug] CentOS for Production (CentOS 6.0 Vs 6.1 Vs 6.2)
In-Reply-To: <CAJmxLYi0FeN8iU8RAQ6fWXLxct4J4ytUZBvJC7YXn0Xt56ziWw@mail.gmail.com>
References: <CAJmxLYi0FeN8iU8RAQ6fWXLxct4J4ytUZBvJC7YXn0Xt56ziWw@mail.gmail.com>
Message-ID: <4F4B0249.5080201@gmail.com>

nk oorda wrote:
> Hi
>
> We are currently using CentOS 5.3 for production systems.
>
> The application/software/package we are using mainly:
> - Apache
> - Tomcat
> - SOLR
> - Mysql
>
> We are in process to upgrade the CentOS.
>
> What would be the best CentOS candidate for upgrade (CentOS 6.0 Vs 6.1 Vs
> 6.2)
>
> We are using both physical and virtual system.

Rule number one, ALWAYS use a test system before upgrading your production systems,
otherwise, you really have no idea what will happen.

From nk.oorda at gmail.com  Mon Feb 27 00:51:41 2012
From: nk.oorda at gmail.com (nk oorda)
Date: Mon, 27 Feb 2012 11:21:41 +0530
Subject: [mdlug] CentOS for Production (CentOS 6.0 Vs 6.1 Vs 6.2)
In-Reply-To: <4F4B0249.5080201@gmail.com>
References: <CAJmxLYi0FeN8iU8RAQ6fWXLxct4J4ytUZBvJC7YXn0Xt56ziWw@mail.gmail.com>
	<4F4B0249.5080201@gmail.com>
Message-ID: <CAJmxLYge5XYisX0cZFh95pBoVOyEovCMc_QG1a_KTtKvt8jULg@mail.gmail.com>

On Mon, Feb 27, 2012 at 9:40 AM, Aaron Kulkis <akulkis00 at gmail.com> wrote:

> nk oorda wrote:
> > Hi
> >
> > We are currently using CentOS 5.3 for production systems.
> >
> > The application/software/package we are using mainly:
> > - Apache
> > - Tomcat
> > - SOLR
> > - Mysql
> >
> > We are in process to upgrade the CentOS.
> >
> > What would be the best CentOS candidate for upgrade (CentOS 6.0 Vs 6.1 Vs
> > 6.2)
> >
> > We are using both physical and virtual system.
>
> Rule number one, ALWAYS use a test system before upgrading your production
> systems,
> otherwise, you really have no idea what will happen.
>


Thanks for the suggestion Aaron,

Yes, we have QA and staging environment in place. So we are going to update
the QA first then Staging and then Production.

Thanks again for the suggestion  :)



--NK

_______________________________________________
> mdlug mailing list
> mdlug at mdlug.org
> http://mdlug.org/mailman/listinfo/mdlug
>

From awilliam at whitemice.org  Mon Feb 27 07:08:34 2012
From: awilliam at whitemice.org (Adam Tauno Williams)
Date: Mon, 27 Feb 2012 07:08:34 -0500
Subject: [mdlug] CentOS for Production (CentOS 6.0 Vs 6.1 Vs 6.2) [TIP]
In-Reply-To: <CAJmxLYge5XYisX0cZFh95pBoVOyEovCMc_QG1a_KTtKvt8jULg@mail.gmail.com>
References: <CAJmxLYi0FeN8iU8RAQ6fWXLxct4J4ytUZBvJC7YXn0Xt56ziWw@mail.gmail.com>
	<4F4B0249.5080201@gmail.com>
	<CAJmxLYge5XYisX0cZFh95pBoVOyEovCMc_QG1a_KTtKvt8jULg@mail.gmail.com>
Message-ID: <1330344514.9055.12.camel@workstation.wmmi.net>

On Mon, 2012-02-27 at 11:21 +0530, nk oorda wrote:
> On Mon, Feb 27, 2012 at 9:40 AM, Aaron Kulkis <akulkis00 at gmail.com> wrote:
> > > We are currently using CentOS 5.3 for production systems.
> > > The application/software/package we are using mainly:
> > > - Apache
> > > - Tomcat
> > > - SOLR
> > > - Mysq
> > > We are in process to upgrade the CentOS.
> > > What would be the best CentOS candidate for upgrade (CentOS 6.0 Vs 6.1 Vs
> > > 6.2)
> > > We are using both physical and virtual system.
> > Rule number one, ALWAYS use a test system before upgrading your production
> > systems,
> > otherwise, you really have no idea what will happen.
> Yes, we have QA and staging environment in place. So we are going to update
> the QA first then Staging and then Production.

One gotcha I've noticed specifically with CentOS6 is that with new
installs / instances that ONBOOT=yes does not get added to the network
interface profile.  So you reboot.... to no network connectivity till
you "ifup eth?" at the console - then everything works.  Looking
in /etc/sysconfig/networ.../ifcfg-eth0 you see "ONBOOT=no".

Hasn't happened everytime, but fairly frequently.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part
Url : http://mdlug.org/pipermail/mdlug/attachments/20120227/fffc008e/attachment.pgp

From otakurider at gmail.com  Mon Feb 27 20:57:41 2012
From: otakurider at gmail.com (Gmail-otakurider)
Date: Mon, 27 Feb 2012 20:57:41 -0500
Subject: [mdlug] hanging machine kernel panic - on going
In-Reply-To: <4F37EFA2.6070906@wowway.com>
References: <1329051074.36045.yint-ygo-j2me@web110616.mail.gq1.yahoo.com>	<4F37BFFE.4080500@wowway.com>	<CA+czFiD9=Ccp=+202FJMr+ugDxXFo84GLrxjXvrCdQoOHZG=xA@mail.gmail.com>
	<1329061686.3307.5.camel@linux-dauq.site>
	<4F37EFA2.6070906@wowway.com>
Message-ID: <4F4C3495.3060809@gmail.com>

Here is the messages dump - check around 16:53 anyone have any ideas?
checked memory tested ok - checked HDD tested ok

Yes I know its long but wanted to give all info

 thinking of setting panic=  setting to have it just reboot

Thank in advance



Feb 27 10:37:30 kuza avahi-daemon[2006]: Network interface enumeration
completed.
Feb 27 10:37:30 kuza avahi-daemon[2006]: Registering new address record
for fe80::250:baff:fe5f:e4c3 on eth0.
Feb 27 10:37:30 kuza avahi-daemon[2006]: Registering new address record
for 192.168.1.3 on eth0.
Feb 27 10:37:30 kuza avahi-daemon[2006]: Registering HINFO record with
values 'I686'/'LINUX'.
Feb 27 10:37:31 kuza avahi-daemon[2006]: Server startup complete. Host
name is kuza.local. Local service cookie is 1101511634.
Feb 27 10:43:10 kuza nmbd[1926]: [2012/02/27 10:43:10, 0]
nmbd/nmbd_become_lmb.c:become_local_master_stage2(396)
Feb 27 10:43:10 kuza nmbd[1926]:   *****
Feb 27 10:43:10 kuza nmbd[1926]:   
Feb 27 10:43:10 kuza nmbd[1926]:   Samba name server KUZA is now a local
master browser for workgroup WORKGROUP on subnet 192.168.1.3
Feb 27 10:43:10 kuza nmbd[1926]:   
Feb 27 10:43:10 kuza nmbd[1926]:   *****
Feb 27 11:18:52 kuza avahi-daemon[2006]: Invalid query packet.
Feb 27 11:19:32 kuza last message repeated 26 times
Feb 27 11:19:32 kuza avahi-daemon[2006]: Invalid query packet.
Feb 27 16:53:41 kuza kernel: BUG: unable to handle kernel NULL pointer
dereference at virtual address 00000000
Feb 27 16:53:41 kuza kernel:  printing eip:
Feb 27 16:53:41 kuza kernel: cab88e5c
Feb 27 16:53:41 kuza kernel: *pde = 09606067
Feb 27 16:53:41 kuza kernel: Oops: 0002 [#1]
Feb 27 16:53:41 kuza kernel: last sysfs file: /block/hda/hda1/size
Feb 27 16:53:41 kuza kernel: Modules linked in: nfsd exportfs lockd
nfs_acl autofs4 hidp l2cap bluetooth sunrpc dm_mirror dm_mod video sbs
i2c_ec dock container button battery asus_acpi backlight ac ipv6 lp
parport_pc parport floppy ohci_hcd 8139too i2c_ali15x3 serio_raw mii
i2c_ali1535 i2c_core pcspkr ide_cd cdrom ext3 jbd
Feb 27 16:53:41 kuza kernel: CPU:    0
Feb 27 16:53:41 kuza kernel: EIP:    0060:[<cab88e5c>]    Not tainted VLI
Feb 27 16:53:41 kuza kernel: EFLAGS: 00210206   (2.6.20-1.2320.fc5 #1)
Feb 27 16:53:41 kuza kernel: EIP is at 0xcab88e5c
Feb 27 16:53:41 kuza kernel: eax: 00000000   ebx: cab88f9c   ecx:
ca3c3610   edx: c137c980
Feb 27 16:53:41 kuza kernel: esi: cab88f48   edi: 00000006   ebp:
cab88e58   esp: cab88ba4
Feb 27 16:53:41 kuza kernel: ds: 007b   es: 007b   ss: 0068
Feb 27 16:53:41 kuza kernel: Process python (pid: 1745, ti=cab88000
task=cfec30d0 task.ti=cab88000)
Feb 27 16:53:41 kuza kernel: Stack: cab88e60 cab88e4c cab88e50 cab88e54
00000030 00000000 00000000 00000030
Feb 27 16:53:41 kuza kernel:        00000000 00000000 00000000 00000000
00000000 00000000 c046ad08 00000000
Feb 27 16:53:41 kuza kernel:        00000000 00000002 ccd0f320 00000000
cfec30d0 c0419bdc 00100100 00200200
Feb 27 16:53:41 kuza kernel: Call Trace:
Feb 27 16:53:41 kuza kernel:  [<c046ad08>] __pollwait+0x0/0xab
Feb 27 16:53:41 kuza kernel:  [<c0419bdc>] default_wake_function+0x0/0xc
Feb 27 16:53:41 kuza kernel:  [<c0419bdc>] default_wake_function+0x0/0xc
Feb 27 16:53:41 kuza kernel:  [<d082fb73>]
do_get_write_access+0x48b/0x4b8 [jbd]
Feb 27 16:53:41 kuza kernel:  [<d08885f8>]
__ext3_get_inode_loc+0x10a/0x2fd [ext3]
Feb 27 16:53:41 kuza kernel:  [<c0608164>] _read_unlock_irq+0x5/0x7
Feb 27 16:53:41 kuza kernel:  [<d0893712>]
__ext3_journal_dirty_metadata+0x16/0x3a [ext3]
Feb 27 16:53:41 kuza kernel:  [<d082fbc1>]
journal_get_write_access+0x21/0x26 [jbd]
Feb 27 16:53:41 kuza kernel:  [<d0888489>]
ext3_mark_iloc_dirty+0x275/0x2da [ext3]
Feb 27 16:53:41 kuza kernel:  [<c0418de8>] __wake_up+0x32/0x43
Feb 27 16:53:41 kuza kernel:  [<d082f6dc>] journal_stop+0x1cb/0x1d7 [jbd]
Feb 27 16:53:41 kuza kernel:  [<d088f703>] __ext3_journal_stop+0x19/0x34
[ext3]
Feb 27 16:53:41 kuza kernel:  [<d088a6b2>]
ext3_ordered_commit_write+0xba/0xd8 [ext3]
Feb 27 16:53:41 kuza kernel:  [<c044aaa7>] __pagevec_lru_add+0x7a/0x85
Feb 27 16:53:41 kuza kernel:  [<c0446328>]
generic_file_buffered_write+0x579/0x5e8
Feb 27 16:53:41 kuza kernel:  [<c047aa2a>] __getblk+0x3b/0x287
Feb 27 16:53:41 kuza kernel:  [<c0420638>] current_fs_time+0x45/0x51
Feb 27 16:53:41 kuza kernel:  [<c0405e65>] do_IRQ+0xbf/0xd6
Feb 27 16:53:41 kuza kernel:  [<c0404763>] common_interrupt+0x23/0x28
Feb 27 16:53:41 kuza kernel:  [<c046aa67>] core_sys_select+0x2d2/0x2f3
Feb 27 16:53:41 kuza kernel:  [<c0448dff>] __alloc_pages+0x68/0x29c
Feb 27 16:53:41 kuza kernel:  [<c0608164>] _read_unlock_irq+0x5/0x7
Feb 27 16:53:41 kuza kernel:  [<c0444c30>] find_get_page+0x35/0x3a
Feb 27 16:53:41 kuza kernel:  [<c044710b>] filemap_nopage+0x159/0x2d4
Feb 27 16:53:41 kuza kernel:  [<c044f9c9>] __handle_mm_fault+0x858/0x87a
Feb 27 16:53:41 kuza kernel:  [<c0452bf4>] do_mmap_pgoff+0x587/0x6e8
Feb 27 16:53:41 kuza kernel:  [<c046b04e>] sys_select+0xa0/0x186
Feb 27 16:53:41 kuza kernel:  [<c0403dc8>] syscall_call+0x7/0xb
Feb 27 16:53:41 kuza kernel:  =======================
Feb 27 16:53:41 kuza kernel: Code: aa 46 c0 48 4b c3 bf ea ff ff ff 00
e0 9a 08 00 e0 9a 08 06 00 00 00 30 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 <00> 00 00 00 44 00 00 00 46 02 20 00 01 00 00 00
00 00 00 00 d2
Feb 27 16:53:41 kuza kernel: EIP: [<cab88e5c>] 0xcab88e5c SS:ESP
0068:cab88ba4
Feb 27 20:04:54 kuza avahi-daemon[2006]: Invalid query packet.
Feb 27 20:05:38 kuza last message repeated 30 times
Feb 27 20:49:41 kuza syslogd 1.4.1: restart.
Feb 27 20:49:41 kuza kernel: klogd 1.4.1, log source = /proc/kmsg started.
Feb 27 20:49:41 kuza kernel: Linux version 2.6.20-1.2320.fc5
(brewbuilder at hs20-bc2-2.build.redhat.com) (gcc version 4.1.1 20070105
(Red Hat 4.1.1-51)) #1 Tue Jun 12 18:50:38 EDT 2007
Feb 27 20:49:41 kuza kernel: BIOS-provided physical RAM map:
Feb 27 20:49:41 kuza kernel: sanitize start
Feb 27 20:49:41 kuza kernel: sanitize end
Feb 27 20:49:41 kuza kernel: copy_e820_map() start: 0000000000000000
size: 000000000009fc00 end: 000000000009fc00 type: 1
Feb 27 20:49:41 kuza kernel: copy_e820_map() type is E820_RAM
Feb 27 20:49:41 kuza kernel: copy_e820_map() start: 000000000009fc00
size: 0000000000000400 end: 00000000000a0000 type: 2
Feb 27 20:49:41 kuza kernel: copy_e820_map() start: 00000000000f0000
size: 0000000000010000 end: 0000000000100000 type: 2
Feb 27 20:49:41 kuza kernel: copy_e820_map() start: 0000000000100000
size: 000000000feec000 end: 000000000ffec000 type: 1
Feb 27 20:49:41 kuza kernel: copy_e820_map() type is E820_RAM
Feb 27 20:49:41 kuza kernel: copy_e820_map() start: 000000000ffec000
size: 0000000000003000 end: 000000000ffef000 type: 3
Feb 27 20:49:41 kuza kernel: copy_e820_map() start: 000000000ffef000
size: 0000000000010000 end: 000000000ffff000 type: 2
Feb 27 20:49:41 kuza kernel: copy_e820_map() start: 000000000ffff000
size: 0000000000001000 end: 0000000010000000 type: 4
Feb 27 20:49:41 kuza kernel: copy_e820_map() start: 00000000ffff0000
size: 0000000000010000 end: 0000000100000000 type: 2
Feb 27 20:49:41 kuza kernel:  BIOS-e820: 0000000000000000 -
000000000009fc00 (usable)
Feb 27 20:49:41 kuza kernel:  BIOS-e820: 000000000009fc00 -
00000000000a0000 (reserved)
Feb 27 20:49:41 kuza kernel:  BIOS-e820: 00000000000f0000 -
0000000000100000 (reserved)
Feb 27 20:49:41 kuza kernel:  BIOS-e820: 0000000000100000 -
000000000ffec000 (usable)
Feb 27 20:49:41 kuza kernel:  BIOS-e820: 000000000ffec000 -
000000000ffef000 (ACPI data)
Feb 27 20:49:41 kuza kernel:  BIOS-e820: 000000000ffef000 -
000000000ffff000 (reserved)
Feb 27 20:49:41 kuza kernel:  BIOS-e820: 000000000ffff000 -
0000000010000000 (ACPI NVS)
Feb 27 20:49:41 kuza kernel:  BIOS-e820: 00000000ffff0000 -
0000000100000000 (reserved)
Feb 27 20:49:41 kuza kernel: 0MB HIGHMEM available.
Feb 27 20:49:41 kuza kernel: 255MB LOWMEM available.
Feb 27 20:49:41 kuza kernel: Using x86 segment limits to approximate NX
protection
Feb 27 20:49:41 kuza kernel: Zone PFN ranges:
Feb 27 20:49:41 kuza kernel:   DMA             0 ->     4096
Feb 27 20:49:43 kuza kernel:   Normal       4096 ->    65516
Feb 27 20:49:43 kuza kernel:   HighMem     65516 ->    65516
Feb 27 20:49:43 kuza kernel: early_node_map[1] active PFN ranges
Feb 27 20:49:43 kuza kernel:     0:        0 ->    65516
Feb 27 20:49:43 kuza kernel: DMI 2.3 present.
Feb 27 20:49:43 kuza kernel: Using APIC driver default
Feb 27 20:49:43 kuza kernel: ACPI: PM-Timer IO Port: 0xe408
Feb 27 20:49:43 kuza kernel: Allocating PCI resources starting at
20000000 (gap: 10000000:efff0000)
Feb 27 20:49:43 kuza kernel: Detected 807.940 MHz processor.
Feb 27 20:49:43 kuza kernel: Built 1 zonelists.  Total pages: 65005
Feb 27 20:49:43 kuza kernel: Kernel command line: ro root=LABEL=/ rhgb quiet
Feb 27 20:49:43 kuza kernel: Local APIC disabled by BIOS -- you can
enable it with "lapic"
Feb 27 20:49:43 kuza kernel: Enabling fast FPU save and restore... done.
Feb 27 20:49:43 kuza kernel: Initializing CPU#0
Feb 27 20:49:43 kuza kernel: CPU 0 irqstacks, hard=c0720000 soft=c071f000
Feb 27 20:49:43 kuza kernel: PID hash table entries: 1024 (order: 10,
4096 bytes)
Feb 27 20:49:43 kuza kernel: Console: colour VGA+ 80x25
Feb 27 20:49:43 kuza kernel: Dentry cache hash table entries: 32768
(order: 5, 131072 bytes)
Feb 27 20:49:43 kuza kernel: Inode-cache hash table entries: 16384
(order: 4, 65536 bytes)
Feb 27 20:49:43 kuza kernel: Memory: 254596k/262064k available (2091k
kernel code, 6828k reserved, 845k data, 232k init, 0k highmem)
Feb 27 20:49:43 kuza kernel: virtual kernel memory layout:
Feb 27 20:49:43 kuza kernel:     fixmap  : 0xfff9b000 - 0xfffff000   (
400 kB)
Feb 27 20:49:43 kuza kernel:     pkmap   : 0xff800000 - 0xffc00000  
(4096 kB)
Feb 27 20:49:43 kuza kernel:     vmalloc : 0xd0800000 - 0xff7fe000   (
751 MB)
Feb 27 20:49:43 kuza kernel:     lowmem  : 0xc0000000 - 0xcffec000   (
255 MB)
Feb 27 20:49:43 kuza kernel:       .init : 0xc06e0000 - 0xc071a000   (
232 kB)
Feb 27 20:49:43 kuza kernel:       .data : 0xc060aefd - 0xc06de614   (
845 kB)
Feb 27 20:49:43 kuza kernel:       .text : 0xc0400000 - 0xc060aefd  
(2091 kB)
Feb 27 20:49:43 kuza kernel: Checking if this processor honours the WP
bit even in supervisor mode... Ok.
Feb 27 20:49:43 kuza kernel: Calibrating delay using timer specific
routine.. 1616.55 BogoMIPS (lpj=808275)
Feb 27 20:49:43 kuza kernel: Security Framework v1.0.0 initialized
Feb 27 20:49:43 kuza kernel: SELinux:  Initializing.
Feb 27 20:49:43 kuza kernel: SELinux:  Starting in permissive mode
Feb 27 20:49:43 kuza kernel: selinux_register_security:  Registering
secondary module capability
Feb 27 20:49:43 kuza kernel: Capability LSM initialized as secondary
Feb 27 20:49:43 kuza kernel: Mount-cache hash table entries: 512
Feb 27 20:49:43 kuza kernel: CPU: L1 I Cache: 64K (64 bytes/line), D
cache 64K (64 bytes/line)
Feb 27 20:49:43 kuza kernel: CPU: L2 Cache: 64K (64 bytes/line)
Feb 27 20:49:43 kuza kernel: Intel machine check architecture supported.
Feb 27 20:49:43 kuza kernel: Intel machine check reporting enabled on CPU#0.
Feb 27 20:49:43 kuza kernel: CPU: AMD Duron(tm) Processor stepping 01
Feb 27 20:49:43 kuza kernel: Checking 'hlt' instruction... OK.
Feb 27 20:49:43 kuza kernel: ACPI: Core revision 20060707
Feb 27 20:49:43 kuza kernel: ACPI: setting ELCR to 0200 (from 0e20)
Feb 27 20:49:43 kuza kernel: NET: Registered protocol family 16
Feb 27 20:49:43 kuza kernel: ACPI: bus type pci registered
Feb 27 20:49:43 kuza kernel: PCI: PCI BIOS revision 2.10 entry at
0xf1170, last bus=1
Feb 27 20:49:43 kuza kernel: PCI: Using configuration type 1
Feb 27 20:49:43 kuza kernel: Setting up standard PCI resources
Feb 27 20:49:43 kuza kernel: ACPI: Interpreter enabled
Feb 27 20:49:43 kuza kernel: ACPI: Using PIC for interrupt routing
Feb 27 20:49:43 kuza kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5
6 7 9 10 *11 12 14 15)
Feb 27 20:49:43 kuza kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5
6 7 9 10 11 12 14 15) *0, disabled.
Feb 27 20:49:43 kuza kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5
6 7 9 *10 11 12 14 15)
Feb 27 20:49:43 kuza kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5
6 7 9 10 11 12 14 15) *0, disabled.
Feb 27 20:49:43 kuza kernel: ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4
*5 6 7 9 10 11 12 14 15)
Feb 27 20:49:43 kuza kernel: ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5
6 7 9 10 11 12 14 15) *0, disabled.
Feb 27 20:49:43 kuza kernel: ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5
6 7 9 10 11 12 14 15) *0, disabled.
Feb 27 20:49:43 kuza kernel: ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5
6 7 9 10 11 12 14 15) *0, disabled.
Feb 27 20:49:43 kuza kernel: ACPI: PCI Interrupt Link [LNKI] (IRQs 3 4 5
6 7 *9 10 11 12 14 15)
Feb 27 20:49:43 kuza kernel: ACPI: PCI Root Bridge [PCI0] (0000:00)
Feb 27 20:49:43 kuza kernel: ACPI: Assume root bridge [\_SB_.PCI0] bus is 0
Feb 27 20:49:43 kuza kernel: PCI quirk: region e400-e43f claimed by
ali7101 ACPI
Feb 27 20:49:43 kuza kernel: PCI quirk: region e800-e81f claimed by
ali7101 SMB
Feb 27 20:49:43 kuza kernel: Linux Plug and Play Support v0.97 (c) Adam
Belay
Feb 27 20:49:43 kuza kernel: pnp: PnP ACPI init
Feb 27 20:49:43 kuza kernel: pnp: PnP ACPI: found 15 devices
Feb 27 20:49:43 kuza kernel: usbcore: registered new interface driver usbfs
Feb 27 20:49:43 kuza kernel: usbcore: registered new interface driver hub
Feb 27 20:49:43 kuza kernel: usbcore: registered new device driver usb
Feb 27 20:49:43 kuza kernel: PCI: Using ACPI for IRQ routing
Feb 27 20:49:43 kuza kernel: PCI: If a device doesn't work, try
"pci=routeirq".  If it helps, post a report
Feb 27 20:49:43 kuza kernel: NetLabel: Initializing
Feb 27 20:49:43 kuza kernel: NetLabel:  domain hash size = 128
Feb 27 20:49:43 kuza kernel: NetLabel:  protocols = UNLABELED CIPSOv4
Feb 27 20:49:43 kuza kernel: NetLabel:  unlabeled traffic allowed by default
Feb 27 20:49:43 kuza kernel: pnp: 00:02: ioport range 0xe400-0xe47f
could not be reserved
Feb 27 20:49:43 kuza kernel: pnp: 00:02: ioport range 0xe800-0xe81f has
been reserved
Feb 27 20:49:43 kuza kernel: pnp: 00:02: ioport range 0x40b-0x40b has
been reserved
Feb 27 20:49:43 kuza kernel: pnp: 00:02: ioport range 0x480-0x48f has
been reserved
Feb 27 20:49:43 kuza kernel: pnp: 00:02: ioport range 0x4d6-0x4d6 has
been reserved
Feb 27 20:49:43 kuza kernel: PCI: Bridge: 0000:00:01.0
Feb 27 20:49:43 kuza kernel:   IO window: disabled.
Feb 27 20:49:43 kuza kernel:   MEM window: ec000000-edefffff
Feb 27 20:49:43 kuza kernel:   PREFETCH window: edf00000-efffffff
Feb 27 20:49:43 kuza kernel: NET: Registered protocol family 2
Feb 27 20:49:43 kuza kernel: IP route cache hash table entries: 2048
(order: 1, 8192 bytes)
Feb 27 20:49:43 kuza kernel: TCP established hash table entries: 8192
(order: 5, 131072 bytes)
Feb 27 20:49:43 kuza kernel: TCP bind hash table entries: 4096 (order:
4, 81920 bytes)
Feb 27 20:49:43 kuza kernel: TCP: Hash tables configured (established
8192 bind 4096)
Feb 27 20:49:43 kuza kernel: TCP reno registered
Feb 27 20:49:43 kuza kernel: checking if image is initramfs... it is
Feb 27 20:49:43 kuza kernel: Freeing initrd memory: 913k freed
Feb 27 20:49:43 kuza kernel: Simple Boot Flag at 0x3a set to 0x1
Feb 27 20:49:43 kuza kernel: apm: BIOS version 1.2 Flags 0x0b (Driver
version 1.16ac)
Feb 27 20:49:43 kuza kernel: apm: overridden by ACPI.
Feb 27 20:49:43 kuza kernel: audit: initializing netlink socket (disabled)
Feb 27 20:49:43 kuza kernel: audit(1330375714.653:1): initialized
Feb 27 20:49:43 kuza kernel: Total HugeTLB memory allocated, 0
Feb 27 20:49:43 kuza kernel: VFS: Disk quotas dquot_6.5.1
Feb 27 20:49:43 kuza kernel: Dquot-cache hash table entries: 1024 (order
0, 4096 bytes)
Feb 27 20:49:43 kuza kernel: SELinux:  Registering netfilter hooks
Feb 27 20:49:43 kuza kernel: ksign: Installing public key data
Feb 27 20:49:43 kuza kernel: Loading keyring
Feb 27 20:49:43 kuza kernel: - Added public key FA1AD44A9013A628
Feb 27 20:49:43 kuza kernel: - User ID: Red Hat, Inc. (Kernel Module GPG
key)
Feb 27 20:49:43 kuza kernel: io scheduler noop registered
Feb 27 20:49:43 kuza kernel: io scheduler anticipatory registered
Feb 27 20:49:43 kuza kernel: io scheduler deadline registered
Feb 27 20:49:43 kuza kernel: io scheduler cfq registered (default)
Feb 27 20:49:43 kuza kernel: Limiting direct PCI/PCI transfers.
Feb 27 20:49:43 kuza kernel: Activating ISA DMA hang workarounds.
Feb 27 20:49:43 kuza kernel: pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Feb 27 20:49:43 kuza kernel: ACPI: Invalid PBLK length [5]
Feb 27 20:49:43 kuza kernel: isapnp: Scanning for PnP cards...
Feb 27 20:49:43 kuza kernel: isapnp: No Plug & Play device found
Feb 27 20:49:43 kuza kernel: Real Time Clock Driver v1.12ac
Feb 27 20:49:43 kuza kernel: Non-volatile memory driver v1.2
Feb 27 20:49:43 kuza kernel: Linux agpgart interface v0.101 (c) Dave Jones
Feb 27 20:49:43 kuza kernel: agpgart: Detected ALi M1647 chipset
Feb 27 20:49:43 kuza kernel: agpgart: AGP aperture is 128M @ 0xf0000000
Feb 27 20:49:43 kuza kernel: Serial: 8250/16550 driver $Revision: 1.90 $
4 ports, IRQ sharing enabled
Feb 27 20:49:43 kuza kernel: serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is
a 16550A
Feb 27 20:49:43 kuza kernel: serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is
a 16550A
Feb 27 20:49:43 kuza kernel: 00:0b: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
Feb 27 20:49:43 kuza kernel: 00:0c: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
Feb 27 20:49:43 kuza kernel: RAMDISK driver initialized: 16 RAM disks of
16384K size 4096 blocksize
Feb 27 20:49:43 kuza kernel: input: Macintosh mouse button emulation as
/class/input/input0
Feb 27 20:49:43 kuza kernel: Uniform Multi-Platform E-IDE driver
Revision: 7.00alpha2
Feb 27 20:49:43 kuza kernel: ide: Assuming 33MHz system bus speed for
PIO modes; override with idebus=xx
Feb 27 20:49:43 kuza kernel: ALI15X3: IDE controller at PCI slot
0000:00:04.0
Feb 27 20:49:43 kuza kernel: ACPI: Unable to derive IRQ for device
0000:00:04.0
Feb 27 20:49:43 kuza kernel: ACPI: PCI Interrupt 0000:00:04.0[A]: no GSI
Feb 27 20:49:43 kuza kernel: ALI15X3: chipset revision 196
Feb 27 20:49:43 kuza kernel: ALI15X3: not 100% native mode: will probe
irqs later
Feb 27 20:49:43 kuza kernel:     ide0: BM-DMA at 0xd400-0xd407, BIOS
settings: hda:DMA, hdb:DMA
Feb 27 20:49:43 kuza kernel:     ide1: BM-DMA at 0xd408-0xd40f, BIOS
settings: hdc:DMA, hdd:pio
Feb 27 20:49:43 kuza kernel: hda: Maxtor 4D040H2, ATA DISK drive
Feb 27 20:49:43 kuza kernel: hdb: ST3120814A, ATA DISK drive
Feb 27 20:49:43 kuza kernel: hda: hw_config=603b
Feb 27 20:49:43 kuza kernel: hda: hw_config=603b
Feb 27 20:49:43 kuza kernel: hdb: hw_config=6d00
Feb 27 20:49:43 kuza kernel: hdb: hw_config=6d00
Feb 27 20:49:43 kuza kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Feb 27 20:49:49 kuza kernel: hdc: MATSHITA CR-583, ATAPI CD/DVD-ROM drive
Feb 27 20:49:49 kuza rpc.statd[1535]: Version 1.0.8 Starting
Feb 27 20:49:49 kuza kernel: hdd: no response (status = 0xa1), resetting
drive
Feb 27 20:49:49 kuza kernel: hdd: no response (status = 0xa1)
Feb 27 20:49:49 kuza kernel: ide1 at 0x170-0x177,0x376 on irq 15
Feb 27 20:49:49 kuza kernel: hda: max request size: 128KiB
Feb 27 20:49:49 kuza kernel: hda: 80043264 sectors (40982 MB) w/2048KiB
Cache, CHS=65535/16/63<6>hda: hw_config=603b
Feb 27 20:49:49 kuza kernel: , UDMA(100)
Feb 27 20:49:49 kuza kernel: hda: cache flushes not supported
Feb 27 20:49:49 kuza kernel:  hda: hda1 hda2 hda3 hda4 < hda5 >
Feb 27 20:49:49 kuza kernel: hdb: max request size: 128KiB
Feb 27 20:49:49 kuza kernel: hdb: 234441648 sectors (120034 MB)
w/8192KiB Cache, CHS=16383/255/63<6>hdb: hw_config=6d00
Feb 27 20:49:49 kuza kernel: , UDMA(100)
Feb 27 20:49:49 kuza kernel: hdb: cache flushes supported
Feb 27 20:49:49 kuza kernel:  hdb: hdb1
Feb 27 20:49:49 kuza kernel: ide-floppy driver 0.99.newide
Feb 27 20:49:49 kuza kernel: usbcore: registered new interface driver
libusual
Feb 27 20:49:49 kuza kernel: usbcore: registered new interface driver hiddev
Feb 27 20:49:49 kuza kernel: usbcore: registered new interface driver usbhid
Feb 27 20:49:49 kuza kernel: drivers/usb/input/hid-core.c: v2.6:USB HID
core driver
Feb 27 20:49:49 kuza kernel: PNP: PS/2 Controller
[PNP0303:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,12
Feb 27 20:49:49 kuza kernel: serio: i8042 KBD port at 0x60,0x64 irq 1
Feb 27 20:49:49 kuza kernel: serio: i8042 AUX port at 0x60,0x64 irq 12
Feb 27 20:49:49 kuza kernel: mice: PS/2 mouse device common for all mice
Feb 27 20:49:49 kuza kernel: input: AT Translated Set 2 keyboard as
/class/input/input1
Feb 27 20:49:49 kuza kernel: TCP bic registered
Feb 27 20:49:49 kuza kernel: Initializing XFRM netlink socket
Feb 27 20:49:49 kuza kernel: NET: Registered protocol family 1
Feb 27 20:49:49 kuza kernel: NET: Registered protocol family 17
Feb 27 20:49:49 kuza kernel: powernow-k8: Processor cpuid 631 not supported
Feb 27 20:49:49 kuza kernel: Using IPI Shortcut mode
Feb 27 20:49:49 kuza kernel: Time: tsc clocksource has been installed.
Feb 27 20:49:49 kuza kernel: ACPI: (supports S0 S1 S4 S5)
Feb 27 20:49:49 kuza kernel: Freeing unused kernel memory: 232k freed
Feb 27 20:49:49 kuza kernel: Write protecting the kernel read-only data:
585k
Feb 27 20:49:49 kuza kernel: input: ImPS/2 Generic Wheel Mouse as
/class/input/input2
Feb 27 20:49:49 kuza kernel: EXT3-fs: INFO: recovery required on
readonly filesystem.
Feb 27 20:49:49 kuza kernel: EXT3-fs: write access will be enabled
during recovery.
Feb 27 20:49:49 kuza kernel: kjournald starting.  Commit interval 5 seconds
Feb 27 20:49:49 kuza kernel: EXT3-fs: recovery complete.
Feb 27 20:49:49 kuza kernel: EXT3-fs: mounted filesystem with ordered
data mode.
Feb 27 20:49:49 kuza kernel: SELinux:  Disabled at runtime.
Feb 27 20:49:49 kuza kernel: SELinux:  Unregistering netfilter hooks
Feb 27 20:49:49 kuza kernel: audit(1330375739.875:2): selinux=0
auid=4294967295
Feb 27 20:49:49 kuza kernel: alim7101_wdt: Steve Hill <steve at navaho.co.uk>.
Feb 27 20:49:49 kuza kernel: alim7101_wdt: Detected old alim7101
revision 'a1d'.  If this is a cobalt board, set the 'use_gpio' module
parameter.
Feb 27 20:49:49 kuza kernel: input: PC Speaker as /class/input/input3
Feb 27 20:49:49 kuza kernel: hdc: ATAPI 8X CD-ROM drive, 128kB Cache, DMA
Feb 27 20:49:49 kuza kernel: Uniform CD-ROM driver Revision: 3.20
Feb 27 20:49:49 kuza kernel: 8139too Fast Ethernet driver 0.9.28
Feb 27 20:49:49 kuza kernel: ACPI: PCI Interrupt Link [LNKC] enabled at
IRQ 10
Feb 27 20:49:49 kuza kernel: ACPI: PCI Interrupt 0000:00:0a.0[A] -> Link
[LNKC] -> GSI 10 (level, low) -> IRQ 10
Feb 27 20:49:49 kuza kernel: eth0: RealTek RTL8139 at 0xd081e000,
00:50:ba:5f:e4:c3, IRQ 10
Feb 27 20:49:49 kuza kernel: Floppy drive(s): fd0 is 1.44M
Feb 27 20:49:49 kuza kernel: FDC 0 is a post-1991 82077
Feb 27 20:49:49 kuza kernel: ACPI: PCI Interrupt Link [LNKI] enabled at
IRQ 9
Feb 27 20:49:49 kuza kernel: ACPI: PCI Interrupt 0000:00:02.0[A] -> Link
[LNKI] -> GSI 9 (level, low) -> IRQ 9
Feb 27 20:49:49 kuza kernel: ohci_hcd 0000:00:02.0: OHCI Host Controller
Feb 27 20:49:49 kuza kernel: ohci_hcd 0000:00:02.0: new USB bus
registered, assigned bus number 1
Feb 27 20:49:49 kuza kernel: ohci_hcd 0000:00:02.0: irq 9, io mem 0xeb800000
Feb 27 20:49:49 kuza kernel: usb usb1: configuration #1 chosen from 1 choice
Feb 27 20:49:49 kuza kernel: hub 1-0:1.0: USB hub found
Feb 27 20:49:49 kuza kernel: hub 1-0:1.0: 4 ports detected
Feb 27 20:49:49 kuza kernel: ACPI: PCI Interrupt Link [LNKE] enabled at
IRQ 5
Feb 27 20:49:49 kuza kernel: ACPI: PCI Interrupt 0000:00:06.0[A] -> Link
[LNKE] -> GSI 5 (level, low) -> IRQ 5
Feb 27 20:49:49 kuza kernel: ohci_hcd 0000:00:06.0: OHCI Host Controller
Feb 27 20:49:49 kuza kernel: ohci_hcd 0000:00:06.0: new USB bus
registered, assigned bus number 2
Feb 27 20:49:49 kuza kernel: ohci_hcd 0000:00:06.0: irq 5, io mem 0xea800000
Feb 27 20:49:49 kuza kernel: usb usb2: configuration #1 chosen from 1 choice
Feb 27 20:49:49 kuza kernel: hub 2-0:1.0: USB hub found
Feb 27 20:49:49 kuza kernel: hub 2-0:1.0: 2 ports detected
Feb 27 20:49:49 kuza kernel: usb 1-1: new low speed USB device using
ohci_hcd and address 2
Feb 27 20:49:49 kuza kernel: usb 1-1: configuration #1 chosen from 1 choice
Feb 27 20:49:49 kuza kernel: parport: PnPBIOS parport detected.
Feb 27 20:49:49 kuza kernel: parport0: PC-style at 0x378 (0x778), irq 7
[PCSPP,TRISTATE]
Feb 27 20:49:49 kuza kernel: lp0: using parport0 (interrupt-driven).
Feb 27 20:49:49 kuza kernel: lp0: console ready
Feb 27 20:49:49 kuza kernel: hiddev96: USB HID v1.10 Device [American
Power Conversion Back-UPS XS 1300 LCD FW:836.H5 .D USB FW:H5 ] on
usb-0000:00:02.0-1
Feb 27 20:49:49 kuza kernel: NET: Registered protocol family 10
Feb 27 20:49:49 kuza kernel: lo: Disabled Privacy Extensions
Feb 27 20:49:49 kuza kernel: Mobile IPv6
Feb 27 20:49:49 kuza kernel: input: Power Button (FF) as /class/input/input4
Feb 27 20:49:49 kuza kernel: ACPI: Power Button (FF) [PWRF]
Feb 27 20:49:49 kuza kernel: input: Power Button (CM) as /class/input/input5
Feb 27 20:49:49 kuza kernel: ACPI: Power Button (CM) [PWRB]
Feb 27 20:49:49 kuza kernel: No dock devices found.
Feb 27 20:49:49 kuza kernel: ibm_acpi: ec object not found
Feb 27 20:49:49 kuza kernel: md: Autodetecting RAID arrays.
Feb 27 20:49:49 kuza kernel: md: autorun ...
Feb 27 20:49:49 kuza kernel: md: ... autorun DONE.
Feb 27 20:49:49 kuza kernel: device-mapper: ioctl: 4.11.0-ioctl
(2006-10-12) initialised: dm-devel at redhat.com
Feb 27 20:49:49 kuza kernel: EXT3 FS on hda5, internal journal
Feb 27 20:49:49 kuza kernel: kjournald starting.  Commit interval 5 seconds
Feb 27 20:49:49 kuza kernel: EXT3 FS on hda1, internal journal
Feb 27 20:49:49 kuza kernel: EXT3-fs: mounted filesystem with ordered
data mode.
Feb 27 20:49:49 kuza kernel: kjournald starting.  Commit interval 5 seconds
Feb 27 20:49:49 kuza kernel: EXT3 FS on hdb1, internal journal
Feb 27 20:49:50 kuza kernel: EXT3-fs: mounted filesystem with ordered
data mode.
Feb 27 20:49:50 kuza kernel: kjournald starting.  Commit interval 5 seconds
Feb 27 20:49:50 kuza kernel: EXT3 FS on hda2, internal journal
Feb 27 20:49:50 kuza kernel: EXT3-fs: mounted filesystem with ordered
data mode.
Feb 27 20:49:50 kuza kernel: Adding 514072k swap on /dev/hda3. 
Priority:-1 extents:1 across:514072k
Feb 27 20:49:50 kuza kernel: eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
Feb 27 20:49:53 kuza kernel: Bluetooth: Core ver 2.11
Feb 27 20:49:53 kuza kernel: NET: Registered protocol family 31
Feb 27 20:49:53 kuza kernel: Bluetooth: HCI device and connection
manager initialized
Feb 27 20:49:53 kuza kernel: Bluetooth: HCI socket layer initialized
Feb 27 20:49:53 kuza kernel: Bluetooth: L2CAP ver 2.8
Feb 27 20:49:53 kuza kernel: Bluetooth: L2CAP socket layer initialized
Feb 27 20:49:53 kuza kernel: Bluetooth: HIDP (Human Interface Emulation)
ver 1.1
Feb 27 20:49:53 kuza hidd[1621]: Bluetooth HID daemon
Feb 27 20:49:56 kuza smartd[1719]: smartd version 5.36
[i686-redhat-linux-gnu] Copyright (C) 2002-6 Bruce Allen
Feb 27 20:49:56 kuza smartd[1719]: Home page is
http://smartmontools.sourceforge.net/ 
Feb 27 20:49:56 kuza smartd[1719]: Opened configuration file
/etc/smartd.conf
Feb 27 20:49:56 kuza smartd[1719]: Configuration file /etc/smartd.conf
parsed.
Feb 27 20:49:56 kuza smartd[1719]: Device: /dev/hda, opened
Feb 27 20:49:56 kuza smartd[1719]: Device: /dev/hda, found in smartd
database.
Feb 27 20:49:57 kuza smartd[1719]: Device: /dev/hda, is SMART capable.
Adding to "monitor" list.
Feb 27 20:49:57 kuza smartd[1719]: Device: /dev/hdb, opened
Feb 27 20:49:57 kuza smartd[1719]: Device: /dev/hdb, not found in smartd
database.
Feb 27 20:49:58 kuza smartd[1719]: Device: /dev/hdb, is SMART capable.
Adding to "monitor" list.
Feb 27 20:49:58 kuza smartd[1719]: Monitoring 2 ATA and 0 SCSI devices
Feb 27 20:49:59 kuza smartd[1724]: smartd has fork()ed into background
mode. New PID=1724.
Feb 27 20:49:59 kuza hpiod: 1.6.6a accepting connections at 50000...
Feb 27 20:50:06 kuza xinetd[1770]: xinetd Version 2.3.13 started with
libwrap loadavg options compiled in.
Feb 27 20:50:06 kuza xinetd[1770]: Started working: 1 available service
Feb 27 20:50:06 kuza exportfs[1803]: No host name given with /data
(sync,rw), suggest *(sync,rw) to avoid warning
Feb 27 20:50:06 kuza apcupsd[1789]: apcupsd 3.12.4 (19 August 2006)
redhat startup succeeded
Feb 27 20:50:06 kuza apcupsd[1789]: NIS server startup succeeded
Feb 27 20:50:07 kuza kernel: Installing knfsd (copyright (C) 1996
okir at monad.swb.de).
Feb 27 20:50:07 kuza kernel: NFSD: Using /var/lib/nfs/v4recovery as the
NFSv4 state recovery directory
Feb 27 20:50:07 kuza kernel: NFSD: starting 90-second grace period
Feb 27 20:50:08 kuza gpm[1855]: *** info [startup.c(95)]:
Feb 27 20:50:08 kuza gpm[1855]: Started gpm successfully. Entered daemon
mode.
Feb 27 20:50:20 kuza avahi-daemon[2009]: Found user 'avahi' (UID 70) and
group 'avahi' (GID 70).
Feb 27 20:50:20 kuza avahi-daemon[2009]: Successfully dropped root
privileges.
Feb 27 20:50:20 kuza avahi-daemon[2009]: avahi-daemon 0.6.11 starting up.
Feb 27 20:50:20 kuza avahi-daemon[2009]: WARNING: No NSS support for
mDNS detected, consider installing nss-mdns!
Feb 27 20:50:21 kuza avahi-daemon[2009]: Successfully called chroot().
Feb 27 20:50:21 kuza avahi-daemon[2009]: Successfully dropped remaining
capabilities.
Feb 27 20:50:21 kuza avahi-daemon[2009]: No service found in
/etc/avahi/services.
Feb 27 20:50:21 kuza avahi-daemon[2009]: New relevant interface
eth0.IPv6 for mDNS.
Feb 27 20:50:21 kuza avahi-daemon[2009]: Joining mDNS multicast group on
interface eth0.IPv6 with address fe80::250:baff:fe5f:e4c3.
Feb 27 20:50:21 kuza avahi-daemon[2009]: New relevant interface
eth0.IPv4 for mDNS.
Feb 27 20:50:21 kuza avahi-daemon[2009]: Joining mDNS multicast group on
interface eth0.IPv4 with address 192.168.1.3.
Feb 27 20:50:21 kuza avahi-daemon[2009]: Network interface enumeration
completed.
Feb 27 20:50:21 kuza avahi-daemon[2009]: Registering new address record
for fe80::250:baff:fe5f:e4c3 on eth0.
Feb 27 20:50:21 kuza avahi-daemon[2009]: Registering new address record
for 192.168.1.3 on eth0.
Feb 27 20:50:21 kuza avahi-daemon[2009]: Registering HINFO record with
values 'I686'/'LINUX'.
Feb 27 20:50:21 kuza avahi-daemon[2009]: Server startup complete. Host
name is kuza.local. Local service cookie is 2874978490.
Feb 27 20:56:06 kuza nmbd[1930]: [2012/02/27 20:56:06, 0]
nmbd/nmbd_become_lmb.c:become_local_master_stage2(396)
Feb 27 20:56:06 kuza nmbd[1930]:   *****
Feb 27 20:56:06 kuza nmbd[1930]:   
Feb 27 20:56:06 kuza nmbd[1930]:   Samba name server KUZA is now a local
master browser for workgroup WORKGROUP on subnet 192.168.1.3
Feb 27 20:56:06 kuza nmbd[1930]:   
Feb 27 20:56:06 kuza nmbd[1930]:   *****

From jhansonxi at gmail.com  Mon Feb 27 21:13:58 2012
From: jhansonxi at gmail.com (Jeff Hanson)
Date: Mon, 27 Feb 2012 21:13:58 -0500
Subject: [mdlug] hanging machine kernel panic - on going
In-Reply-To: <4F4C3495.3060809@gmail.com>
References: <1329051074.36045.yint-ygo-j2me@web110616.mail.gq1.yahoo.com>
	<4F37BFFE.4080500@wowway.com>
	<CA+czFiD9=Ccp=+202FJMr+ugDxXFo84GLrxjXvrCdQoOHZG=xA@mail.gmail.com>
	<1329061686.3307.5.camel@linux-dauq.site>
	<4F37EFA2.6070906@wowway.com> <4F4C3495.3060809@gmail.com>
Message-ID: <CAD39dTaGTFWqGZ9gtbt22fH=Aq5wQKDZhjmL6P9qD-mM7GcQJw@mail.gmail.com>

I can't tell from the messages.  Possibly a network device problem.

Video and BIOS bugs can cause intermittent panics.

I had many intermittent problems with hard drives on one system that
turned out to be a failing southbridge (overheated).  Heavy drive I/O
would cause it to start failing.

On 2/27/12, Gmail-otakurider <otakurider at gmail.com> wrote:
> Here is the messages dump - check around 16:53 anyone have any ideas?
> checked memory tested ok - checked HDD tested ok
>
> Yes I know its long but wanted to give all info
>
>  thinking of setting panic=  setting to have it just reboot
>
> Thank in advance
>
>
>
> Feb 27 10:37:30 kuza avahi-daemon[2006]: Network interface enumeration
> completed.
> Feb 27 10:37:30 kuza avahi-daemon[2006]: Registering new address record
> for fe80::250:baff:fe5f:e4c3 on eth0.
> Feb 27 10:37:30 kuza avahi-daemon[2006]: Registering new address record
> for 192.168.1.3 on eth0.
> Feb 27 10:37:30 kuza avahi-daemon[2006]: Registering HINFO record with
> values 'I686'/'LINUX'.
> Feb 27 10:37:31 kuza avahi-daemon[2006]: Server startup complete. Host
> name is kuza.local. Local service cookie is 1101511634.
> Feb 27 10:43:10 kuza nmbd[1926]: [2012/02/27 10:43:10, 0]
> nmbd/nmbd_become_lmb.c:become_local_master_stage2(396)
> Feb 27 10:43:10 kuza nmbd[1926]:   *****
> Feb 27 10:43:10 kuza nmbd[1926]:
> Feb 27 10:43:10 kuza nmbd[1926]:   Samba name server KUZA is now a local
> master browser for workgroup WORKGROUP on subnet 192.168.1.3
> Feb 27 10:43:10 kuza nmbd[1926]:
> Feb 27 10:43:10 kuza nmbd[1926]:   *****
> Feb 27 11:18:52 kuza avahi-daemon[2006]: Invalid query packet.
> Feb 27 11:19:32 kuza last message repeated 26 times
> Feb 27 11:19:32 kuza avahi-daemon[2006]: Invalid query packet.
> Feb 27 16:53:41 kuza kernel: BUG: unable to handle kernel NULL pointer
> dereference at virtual address 00000000
> Feb 27 16:53:41 kuza kernel:  printing eip:
> Feb 27 16:53:41 kuza kernel: cab88e5c
> Feb 27 16:53:41 kuza kernel: *pde = 09606067
> Feb 27 16:53:41 kuza kernel: Oops: 0002 [#1]
> Feb 27 16:53:41 kuza kernel: last sysfs file: /block/hda/hda1/size
> Feb 27 16:53:41 kuza kernel: Modules linked in: nfsd exportfs lockd
> nfs_acl autofs4 hidp l2cap bluetooth sunrpc dm_mirror dm_mod video sbs
> i2c_ec dock container button battery asus_acpi backlight ac ipv6 lp
> parport_pc parport floppy ohci_hcd 8139too i2c_ali15x3 serio_raw mii
> i2c_ali1535 i2c_core pcspkr ide_cd cdrom ext3 jbd
> Feb 27 16:53:41 kuza kernel: CPU:    0
> Feb 27 16:53:41 kuza kernel: EIP:    0060:[<cab88e5c>]    Not tainted VLI
> Feb 27 16:53:41 kuza kernel: EFLAGS: 00210206   (2.6.20-1.2320.fc5 #1)
> Feb 27 16:53:41 kuza kernel: EIP is at 0xcab88e5c
> Feb 27 16:53:41 kuza kernel: eax: 00000000   ebx: cab88f9c   ecx:
> ca3c3610   edx: c137c980
> Feb 27 16:53:41 kuza kernel: esi: cab88f48   edi: 00000006   ebp:
> cab88e58   esp: cab88ba4
> Feb 27 16:53:41 kuza kernel: ds: 007b   es: 007b   ss: 0068
> Feb 27 16:53:41 kuza kernel: Process python (pid: 1745, ti=cab88000
> task=cfec30d0 task.ti=cab88000)
> Feb 27 16:53:41 kuza kernel: Stack: cab88e60 cab88e4c cab88e50 cab88e54
> 00000030 00000000 00000000 00000030
> Feb 27 16:53:41 kuza kernel:        00000000 00000000 00000000 00000000
> 00000000 00000000 c046ad08 00000000
> Feb 27 16:53:41 kuza kernel:        00000000 00000002 ccd0f320 00000000
> cfec30d0 c0419bdc 00100100 00200200
> Feb 27 16:53:41 kuza kernel: Call Trace:
> Feb 27 16:53:41 kuza kernel:  [<c046ad08>] __pollwait+0x0/0xab
> Feb 27 16:53:41 kuza kernel:  [<c0419bdc>] default_wake_function+0x0/0xc
> Feb 27 16:53:41 kuza kernel:  [<c0419bdc>] default_wake_function+0x0/0xc
> Feb 27 16:53:41 kuza kernel:  [<d082fb73>]
> do_get_write_access+0x48b/0x4b8 [jbd]
> Feb 27 16:53:41 kuza kernel:  [<d08885f8>]
> __ext3_get_inode_loc+0x10a/0x2fd [ext3]
> Feb 27 16:53:41 kuza kernel:  [<c0608164>] _read_unlock_irq+0x5/0x7
> Feb 27 16:53:41 kuza kernel:  [<d0893712>]
> __ext3_journal_dirty_metadata+0x16/0x3a [ext3]
> Feb 27 16:53:41 kuza kernel:  [<d082fbc1>]
> journal_get_write_access+0x21/0x26 [jbd]
> Feb 27 16:53:41 kuza kernel:  [<d0888489>]
> ext3_mark_iloc_dirty+0x275/0x2da [ext3]
> Feb 27 16:53:41 kuza kernel:  [<c0418de8>] __wake_up+0x32/0x43
> Feb 27 16:53:41 kuza kernel:  [<d082f6dc>] journal_stop+0x1cb/0x1d7 [jbd]
> Feb 27 16:53:41 kuza kernel:  [<d088f703>] __ext3_journal_stop+0x19/0x34
> [ext3]
> Feb 27 16:53:41 kuza kernel:  [<d088a6b2>]
> ext3_ordered_commit_write+0xba/0xd8 [ext3]
> Feb 27 16:53:41 kuza kernel:  [<c044aaa7>] __pagevec_lru_add+0x7a/0x85
> Feb 27 16:53:41 kuza kernel:  [<c0446328>]
> generic_file_buffered_write+0x579/0x5e8
> Feb 27 16:53:41 kuza kernel:  [<c047aa2a>] __getblk+0x3b/0x287
> Feb 27 16:53:41 kuza kernel:  [<c0420638>] current_fs_time+0x45/0x51
> Feb 27 16:53:41 kuza kernel:  [<c0405e65>] do_IRQ+0xbf/0xd6
> Feb 27 16:53:41 kuza kernel:  [<c0404763>] common_interrupt+0x23/0x28
> Feb 27 16:53:41 kuza kernel:  [<c046aa67>] core_sys_select+0x2d2/0x2f3
> Feb 27 16:53:41 kuza kernel:  [<c0448dff>] __alloc_pages+0x68/0x29c
> Feb 27 16:53:41 kuza kernel:  [<c0608164>] _read_unlock_irq+0x5/0x7
> Feb 27 16:53:41 kuza kernel:  [<c0444c30>] find_get_page+0x35/0x3a
> Feb 27 16:53:41 kuza kernel:  [<c044710b>] filemap_nopage+0x159/0x2d4
> Feb 27 16:53:41 kuza kernel:  [<c044f9c9>] __handle_mm_fault+0x858/0x87a
> Feb 27 16:53:41 kuza kernel:  [<c0452bf4>] do_mmap_pgoff+0x587/0x6e8
> Feb 27 16:53:41 kuza kernel:  [<c046b04e>] sys_select+0xa0/0x186
> Feb 27 16:53:41 kuza kernel:  [<c0403dc8>] syscall_call+0x7/0xb
> Feb 27 16:53:41 kuza kernel:  =======================
> Feb 27 16:53:41 kuza kernel: Code: aa 46 c0 48 4b c3 bf ea ff ff ff 00
> e0 9a 08 00 e0 9a 08 06 00 00 00 30 00 00 00 00 00 00 00 00 00 00 00 00
> 00 00 00 00 00 00 00 <00> 00 00 00 44 00 00 00 46 02 20 00 01 00 00 00
> 00 00 00 00 d2
> Feb 27 16:53:41 kuza kernel: EIP: [<cab88e5c>] 0xcab88e5c SS:ESP
> 0068:cab88ba4
> Feb 27 20:04:54 kuza avahi-daemon[2006]: Invalid query packet.
> Feb 27 20:05:38 kuza last message repeated 30 times
> Feb 27 20:49:41 kuza syslogd 1.4.1: restart.
> Feb 27 20:49:41 kuza kernel: klogd 1.4.1, log source = /proc/kmsg started.
> Feb 27 20:49:41 kuza kernel: Linux version 2.6.20-1.2320.fc5
> (brewbuilder at hs20-bc2-2.build.redhat.com) (gcc version 4.1.1 20070105
> (Red Hat 4.1.1-51)) #1 Tue Jun 12 18:50:38 EDT 2007
> Feb 27 20:49:41 kuza kernel: BIOS-provided physical RAM map:
> Feb 27 20:49:41 kuza kernel: sanitize start
> Feb 27 20:49:41 kuza kernel: sanitize end
> Feb 27 20:49:41 kuza kernel: copy_e820_map() start: 0000000000000000
> size: 000000000009fc00 end: 000000000009fc00 type: 1
> Feb 27 20:49:41 kuza kernel: copy_e820_map() type is E820_RAM
> Feb 27 20:49:41 kuza kernel: copy_e820_map() start: 000000000009fc00
> size: 0000000000000400 end: 00000000000a0000 type: 2
> Feb 27 20:49:41 kuza kernel: copy_e820_map() start: 00000000000f0000
> size: 0000000000010000 end: 0000000000100000 type: 2
> Feb 27 20:49:41 kuza kernel: copy_e820_map() start: 0000000000100000
> size: 000000000feec000 end: 000000000ffec000 type: 1
> Feb 27 20:49:41 kuza kernel: copy_e820_map() type is E820_RAM
> Feb 27 20:49:41 kuza kernel: copy_e820_map() start: 000000000ffec000
> size: 0000000000003000 end: 000000000ffef000 type: 3
> Feb 27 20:49:41 kuza kernel: copy_e820_map() start: 000000000ffef000
> size: 0000000000010000 end: 000000000ffff000 type: 2
> Feb 27 20:49:41 kuza kernel: copy_e820_map() start: 000000000ffff000
> size: 0000000000001000 end: 0000000010000000 type: 4
> Feb 27 20:49:41 kuza kernel: copy_e820_map() start: 00000000ffff0000
> size: 0000000000010000 end: 0000000100000000 type: 2
> Feb 27 20:49:41 kuza kernel:  BIOS-e820: 0000000000000000 -
> 000000000009fc00 (usable)
> Feb 27 20:49:41 kuza kernel:  BIOS-e820: 000000000009fc00 -
> 00000000000a0000 (reserved)
> Feb 27 20:49:41 kuza kernel:  BIOS-e820: 00000000000f0000 -
> 0000000000100000 (reserved)
> Feb 27 20:49:41 kuza kernel:  BIOS-e820: 0000000000100000 -
> 000000000ffec000 (usable)
> Feb 27 20:49:41 kuza kernel:  BIOS-e820: 000000000ffec000 -
> 000000000ffef000 (ACPI data)
> Feb 27 20:49:41 kuza kernel:  BIOS-e820: 000000000ffef000 -
> 000000000ffff000 (reserved)
> Feb 27 20:49:41 kuza kernel:  BIOS-e820: 000000000ffff000 -
> 0000000010000000 (ACPI NVS)
> Feb 27 20:49:41 kuza kernel:  BIOS-e820: 00000000ffff0000 -
> 0000000100000000 (reserved)
> Feb 27 20:49:41 kuza kernel: 0MB HIGHMEM available.
> Feb 27 20:49:41 kuza kernel: 255MB LOWMEM available.
> Feb 27 20:49:41 kuza kernel: Using x86 segment limits to approximate NX
> protection
> Feb 27 20:49:41 kuza kernel: Zone PFN ranges:
> Feb 27 20:49:41 kuza kernel:   DMA             0 ->     4096
> Feb 27 20:49:43 kuza kernel:   Normal       4096 ->    65516
> Feb 27 20:49:43 kuza kernel:   HighMem     65516 ->    65516
> Feb 27 20:49:43 kuza kernel: early_node_map[1] active PFN ranges
> Feb 27 20:49:43 kuza kernel:     0:        0 ->    65516
> Feb 27 20:49:43 kuza kernel: DMI 2.3 present.
> Feb 27 20:49:43 kuza kernel: Using APIC driver default
> Feb 27 20:49:43 kuza kernel: ACPI: PM-Timer IO Port: 0xe408
> Feb 27 20:49:43 kuza kernel: Allocating PCI resources starting at
> 20000000 (gap: 10000000:efff0000)
> Feb 27 20:49:43 kuza kernel: Detected 807.940 MHz processor.
> Feb 27 20:49:43 kuza kernel: Built 1 zonelists.  Total pages: 65005
> Feb 27 20:49:43 kuza kernel: Kernel command line: ro root=LABEL=/ rhgb quiet
> Feb 27 20:49:43 kuza kernel: Local APIC disabled by BIOS -- you can
> enable it with "lapic"
> Feb 27 20:49:43 kuza kernel: Enabling fast FPU save and restore... done.
> Feb 27 20:49:43 kuza kernel: Initializing CPU#0
> Feb 27 20:49:43 kuza kernel: CPU 0 irqstacks, hard=c0720000 soft=c071f000
> Feb 27 20:49:43 kuza kernel: PID hash table entries: 1024 (order: 10,
> 4096 bytes)
> Feb 27 20:49:43 kuza kernel: Console: colour VGA+ 80x25
> Feb 27 20:49:43 kuza kernel: Dentry cache hash table entries: 32768
> (order: 5, 131072 bytes)
> Feb 27 20:49:43 kuza kernel: Inode-cache hash table entries: 16384
> (order: 4, 65536 bytes)
> Feb 27 20:49:43 kuza kernel: Memory: 254596k/262064k available (2091k
> kernel code, 6828k reserved, 845k data, 232k init, 0k highmem)
> Feb 27 20:49:43 kuza kernel: virtual kernel memory layout:
> Feb 27 20:49:43 kuza kernel:     fixmap  : 0xfff9b000 - 0xfffff000   (
> 400 kB)
> Feb 27 20:49:43 kuza kernel:     pkmap   : 0xff800000 - 0xffc00000
> (4096 kB)
> Feb 27 20:49:43 kuza kernel:     vmalloc : 0xd0800000 - 0xff7fe000   (
> 751 MB)
> Feb 27 20:49:43 kuza kernel:     lowmem  : 0xc0000000 - 0xcffec000   (
> 255 MB)
> Feb 27 20:49:43 kuza kernel:       .init : 0xc06e0000 - 0xc071a000   (
> 232 kB)
> Feb 27 20:49:43 kuza kernel:       .data : 0xc060aefd - 0xc06de614   (
> 845 kB)
> Feb 27 20:49:43 kuza kernel:       .text : 0xc0400000 - 0xc060aefd
> (2091 kB)
> Feb 27 20:49:43 kuza kernel: Checking if this processor honours the WP
> bit even in supervisor mode... Ok.
> Feb 27 20:49:43 kuza kernel: Calibrating delay using timer specific
> routine.. 1616.55 BogoMIPS (lpj=808275)
> Feb 27 20:49:43 kuza kernel: Security Framework v1.0.0 initialized
> Feb 27 20:49:43 kuza kernel: SELinux:  Initializing.
> Feb 27 20:49:43 kuza kernel: SELinux:  Starting in permissive mode
> Feb 27 20:49:43 kuza kernel: selinux_register_security:  Registering
> secondary module capability
> Feb 27 20:49:43 kuza kernel: Capability LSM initialized as secondary
> Feb 27 20:49:43 kuza kernel: Mount-cache hash table entries: 512
> Feb 27 20:49:43 kuza kernel: CPU: L1 I Cache: 64K (64 bytes/line), D
> cache 64K (64 bytes/line)
> Feb 27 20:49:43 kuza kernel: CPU: L2 Cache: 64K (64 bytes/line)
> Feb 27 20:49:43 kuza kernel: Intel machine check architecture supported.
> Feb 27 20:49:43 kuza kernel: Intel machine check reporting enabled on CPU#0.
> Feb 27 20:49:43 kuza kernel: CPU: AMD Duron(tm) Processor stepping 01
> Feb 27 20:49:43 kuza kernel: Checking 'hlt' instruction... OK.
> Feb 27 20:49:43 kuza kernel: ACPI: Core revision 20060707
> Feb 27 20:49:43 kuza kernel: ACPI: setting ELCR to 0200 (from 0e20)
> Feb 27 20:49:43 kuza kernel: NET: Registered protocol family 16
> Feb 27 20:49:43 kuza kernel: ACPI: bus type pci registered
> Feb 27 20:49:43 kuza kernel: PCI: PCI BIOS revision 2.10 entry at
> 0xf1170, last bus=1
> Feb 27 20:49:43 kuza kernel: PCI: Using configuration type 1
> Feb 27 20:49:43 kuza kernel: Setting up standard PCI resources
> Feb 27 20:49:43 kuza kernel: ACPI: Interpreter enabled
> Feb 27 20:49:43 kuza kernel: ACPI: Using PIC for interrupt routing
> Feb 27 20:49:43 kuza kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5
> 6 7 9 10 *11 12 14 15)
> Feb 27 20:49:43 kuza kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5
> 6 7 9 10 11 12 14 15) *0, disabled.
> Feb 27 20:49:43 kuza kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5
> 6 7 9 *10 11 12 14 15)
> Feb 27 20:49:43 kuza kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5
> 6 7 9 10 11 12 14 15) *0, disabled.
> Feb 27 20:49:43 kuza kernel: ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4
> *5 6 7 9 10 11 12 14 15)
> Feb 27 20:49:43 kuza kernel: ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5
> 6 7 9 10 11 12 14 15) *0, disabled.
> Feb 27 20:49:43 kuza kernel: ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5
> 6 7 9 10 11 12 14 15) *0, disabled.
> Feb 27 20:49:43 kuza kernel: ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5
> 6 7 9 10 11 12 14 15) *0, disabled.
> Feb 27 20:49:43 kuza kernel: ACPI: PCI Interrupt Link [LNKI] (IRQs 3 4 5
> 6 7 *9 10 11 12 14 15)
> Feb 27 20:49:43 kuza kernel: ACPI: PCI Root Bridge [PCI0] (0000:00)
> Feb 27 20:49:43 kuza kernel: ACPI: Assume root bridge [\_SB_.PCI0] bus is 0
> Feb 27 20:49:43 kuza kernel: PCI quirk: region e400-e43f claimed by
> ali7101 ACPI
> Feb 27 20:49:43 kuza kernel: PCI quirk: region e800-e81f claimed by
> ali7101 SMB
> Feb 27 20:49:43 kuza kernel: Linux Plug and Play Support v0.97 (c) Adam
> Belay
> Feb 27 20:49:43 kuza kernel: pnp: PnP ACPI init
> Feb 27 20:49:43 kuza kernel: pnp: PnP ACPI: found 15 devices
> Feb 27 20:49:43 kuza kernel: usbcore: registered new interface driver usbfs
> Feb 27 20:49:43 kuza kernel: usbcore: registered new interface driver hub
> Feb 27 20:49:43 kuza kernel: usbcore: registered new device driver usb
> Feb 27 20:49:43 kuza kernel: PCI: Using ACPI for IRQ routing
> Feb 27 20:49:43 kuza kernel: PCI: If a device doesn't work, try
> "pci=routeirq".  If it helps, post a report
> Feb 27 20:49:43 kuza kernel: NetLabel: Initializing
> Feb 27 20:49:43 kuza kernel: NetLabel:  domain hash size = 128
> Feb 27 20:49:43 kuza kernel: NetLabel:  protocols = UNLABELED CIPSOv4
> Feb 27 20:49:43 kuza kernel: NetLabel:  unlabeled traffic allowed by default
> Feb 27 20:49:43 kuza kernel: pnp: 00:02: ioport range 0xe400-0xe47f
> could not be reserved
> Feb 27 20:49:43 kuza kernel: pnp: 00:02: ioport range 0xe800-0xe81f has
> been reserved
> Feb 27 20:49:43 kuza kernel: pnp: 00:02: ioport range 0x40b-0x40b has
> been reserved
> Feb 27 20:49:43 kuza kernel: pnp: 00:02: ioport range 0x480-0x48f has
> been reserved
> Feb 27 20:49:43 kuza kernel: pnp: 00:02: ioport range 0x4d6-0x4d6 has
> been reserved
> Feb 27 20:49:43 kuza kernel: PCI: Bridge: 0000:00:01.0
> Feb 27 20:49:43 kuza kernel:   IO window: disabled.
> Feb 27 20:49:43 kuza kernel:   MEM window: ec000000-edefffff
> Feb 27 20:49:43 kuza kernel:   PREFETCH window: edf00000-efffffff
> Feb 27 20:49:43 kuza kernel: NET: Registered protocol family 2
> Feb 27 20:49:43 kuza kernel: IP route cache hash table entries: 2048
> (order: 1, 8192 bytes)
> Feb 27 20:49:43 kuza kernel: TCP established hash table entries: 8192
> (order: 5, 131072 bytes)
> Feb 27 20:49:43 kuza kernel: TCP bind hash table entries: 4096 (order:
> 4, 81920 bytes)
> Feb 27 20:49:43 kuza kernel: TCP: Hash tables configured (established
> 8192 bind 4096)
> Feb 27 20:49:43 kuza kernel: TCP reno registered
> Feb 27 20:49:43 kuza kernel: checking if image is initramfs... it is
> Feb 27 20:49:43 kuza kernel: Freeing initrd memory: 913k freed
> Feb 27 20:49:43 kuza kernel: Simple Boot Flag at 0x3a set to 0x1
> Feb 27 20:49:43 kuza kernel: apm: BIOS version 1.2 Flags 0x0b (Driver
> version 1.16ac)
> Feb 27 20:49:43 kuza kernel: apm: overridden by ACPI.
> Feb 27 20:49:43 kuza kernel: audit: initializing netlink socket (disabled)
> Feb 27 20:49:43 kuza kernel: audit(1330375714.653:1): initialized
> Feb 27 20:49:43 kuza kernel: Total HugeTLB memory allocated, 0
> Feb 27 20:49:43 kuza kernel: VFS: Disk quotas dquot_6.5.1
> Feb 27 20:49:43 kuza kernel: Dquot-cache hash table entries: 1024 (order
> 0, 4096 bytes)
> Feb 27 20:49:43 kuza kernel: SELinux:  Registering netfilter hooks
> Feb 27 20:49:43 kuza kernel: ksign: Installing public key data
> Feb 27 20:49:43 kuza kernel: Loading keyring
> Feb 27 20:49:43 kuza kernel: - Added public key FA1AD44A9013A628
> Feb 27 20:49:43 kuza kernel: - User ID: Red Hat, Inc. (Kernel Module GPG
> key)
> Feb 27 20:49:43 kuza kernel: io scheduler noop registered
> Feb 27 20:49:43 kuza kernel: io scheduler anticipatory registered
> Feb 27 20:49:43 kuza kernel: io scheduler deadline registered
> Feb 27 20:49:43 kuza kernel: io scheduler cfq registered (default)
> Feb 27 20:49:43 kuza kernel: Limiting direct PCI/PCI transfers.
> Feb 27 20:49:43 kuza kernel: Activating ISA DMA hang workarounds.
> Feb 27 20:49:43 kuza kernel: pci_hotplug: PCI Hot Plug PCI Core version: 0.5
> Feb 27 20:49:43 kuza kernel: ACPI: Invalid PBLK length [5]
> Feb 27 20:49:43 kuza kernel: isapnp: Scanning for PnP cards...
> Feb 27 20:49:43 kuza kernel: isapnp: No Plug & Play device found
> Feb 27 20:49:43 kuza kernel: Real Time Clock Driver v1.12ac
> Feb 27 20:49:43 kuza kernel: Non-volatile memory driver v1.2
> Feb 27 20:49:43 kuza kernel: Linux agpgart interface v0.101 (c) Dave Jones
> Feb 27 20:49:43 kuza kernel: agpgart: Detected ALi M1647 chipset
> Feb 27 20:49:43 kuza kernel: agpgart: AGP aperture is 128M @ 0xf0000000
> Feb 27 20:49:43 kuza kernel: Serial: 8250/16550 driver $Revision: 1.90 $
> 4 ports, IRQ sharing enabled
> Feb 27 20:49:43 kuza kernel: serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is
> a 16550A
> Feb 27 20:49:43 kuza kernel: serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is
> a 16550A
> Feb 27 20:49:43 kuza kernel: 00:0b: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
> Feb 27 20:49:43 kuza kernel: 00:0c: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
> Feb 27 20:49:43 kuza kernel: RAMDISK driver initialized: 16 RAM disks of
> 16384K size 4096 blocksize
> Feb 27 20:49:43 kuza kernel: input: Macintosh mouse button emulation as
> /class/input/input0
> Feb 27 20:49:43 kuza kernel: Uniform Multi-Platform E-IDE driver
> Revision: 7.00alpha2
> Feb 27 20:49:43 kuza kernel: ide: Assuming 33MHz system bus speed for
> PIO modes; override with idebus=xx
> Feb 27 20:49:43 kuza kernel: ALI15X3: IDE controller at PCI slot
> 0000:00:04.0
> Feb 27 20:49:43 kuza kernel: ACPI: Unable to derive IRQ for device
> 0000:00:04.0
> Feb 27 20:49:43 kuza kernel: ACPI: PCI Interrupt 0000:00:04.0[A]: no GSI
> Feb 27 20:49:43 kuza kernel: ALI15X3: chipset revision 196
> Feb 27 20:49:43 kuza kernel: ALI15X3: not 100% native mode: will probe
> irqs later
> Feb 27 20:49:43 kuza kernel:     ide0: BM-DMA at 0xd400-0xd407, BIOS
> settings: hda:DMA, hdb:DMA
> Feb 27 20:49:43 kuza kernel:     ide1: BM-DMA at 0xd408-0xd40f, BIOS
> settings: hdc:DMA, hdd:pio
> Feb 27 20:49:43 kuza kernel: hda: Maxtor 4D040H2, ATA DISK drive
> Feb 27 20:49:43 kuza kernel: hdb: ST3120814A, ATA DISK drive
> Feb 27 20:49:43 kuza kernel: hda: hw_config=603b
> Feb 27 20:49:43 kuza kernel: hda: hw_config=603b
> Feb 27 20:49:43 kuza kernel: hdb: hw_config=6d00
> Feb 27 20:49:43 kuza kernel: hdb: hw_config=6d00
> Feb 27 20:49:43 kuza kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
> Feb 27 20:49:49 kuza kernel: hdc: MATSHITA CR-583, ATAPI CD/DVD-ROM drive
> Feb 27 20:49:49 kuza rpc.statd[1535]: Version 1.0.8 Starting
> Feb 27 20:49:49 kuza kernel: hdd: no response (status = 0xa1), resetting
> drive
> Feb 27 20:49:49 kuza kernel: hdd: no response (status = 0xa1)
> Feb 27 20:49:49 kuza kernel: ide1 at 0x170-0x177,0x376 on irq 15
> Feb 27 20:49:49 kuza kernel: hda: max request size: 128KiB
> Feb 27 20:49:49 kuza kernel: hda: 80043264 sectors (40982 MB) w/2048KiB
> Cache, CHS=65535/16/63<6>hda: hw_config=603b
> Feb 27 20:49:49 kuza kernel: , UDMA(100)
> Feb 27 20:49:49 kuza kernel: hda: cache flushes not supported
> Feb 27 20:49:49 kuza kernel:  hda: hda1 hda2 hda3 hda4 < hda5 >
> Feb 27 20:49:49 kuza kernel: hdb: max request size: 128KiB
> Feb 27 20:49:49 kuza kernel: hdb: 234441648 sectors (120034 MB)
> w/8192KiB Cache, CHS=16383/255/63<6>hdb: hw_config=6d00
> Feb 27 20:49:49 kuza kernel: , UDMA(100)
> Feb 27 20:49:49 kuza kernel: hdb: cache flushes supported
> Feb 27 20:49:49 kuza kernel:  hdb: hdb1
> Feb 27 20:49:49 kuza kernel: ide-floppy driver 0.99.newide
> Feb 27 20:49:49 kuza kernel: usbcore: registered new interface driver
> libusual
> Feb 27 20:49:49 kuza kernel: usbcore: registered new interface driver hiddev
> Feb 27 20:49:49 kuza kernel: usbcore: registered new interface driver usbhid
> Feb 27 20:49:49 kuza kernel: drivers/usb/input/hid-core.c: v2.6:USB HID
> core driver
> Feb 27 20:49:49 kuza kernel: PNP: PS/2 Controller
> [PNP0303:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,12
> Feb 27 20:49:49 kuza kernel: serio: i8042 KBD port at 0x60,0x64 irq 1
> Feb 27 20:49:49 kuza kernel: serio: i8042 AUX port at 0x60,0x64 irq 12
> Feb 27 20:49:49 kuza kernel: mice: PS/2 mouse device common for all mice
> Feb 27 20:49:49 kuza kernel: input: AT Translated Set 2 keyboard as
> /class/input/input1
> Feb 27 20:49:49 kuza kernel: TCP bic registered
> Feb 27 20:49:49 kuza kernel: Initializing XFRM netlink socket
> Feb 27 20:49:49 kuza kernel: NET: Registered protocol family 1
> Feb 27 20:49:49 kuza kernel: NET: Registered protocol family 17
> Feb 27 20:49:49 kuza kernel: powernow-k8: Processor cpuid 631 not supported
> Feb 27 20:49:49 kuza kernel: Using IPI Shortcut mode
> Feb 27 20:49:49 kuza kernel: Time: tsc clocksource has been installed.
> Feb 27 20:49:49 kuza kernel: ACPI: (supports S0 S1 S4 S5)
> Feb 27 20:49:49 kuza kernel: Freeing unused kernel memory: 232k freed
> Feb 27 20:49:49 kuza kernel: Write protecting the kernel read-only data:
> 585k
> Feb 27 20:49:49 kuza kernel: input: ImPS/2 Generic Wheel Mouse as
> /class/input/input2
> Feb 27 20:49:49 kuza kernel: EXT3-fs: INFO: recovery required on
> readonly filesystem.
> Feb 27 20:49:49 kuza kernel: EXT3-fs: write access will be enabled
> during recovery.
> Feb 27 20:49:49 kuza kernel: kjournald starting.  Commit interval 5 seconds
> Feb 27 20:49:49 kuza kernel: EXT3-fs: recovery complete.
> Feb 27 20:49:49 kuza kernel: EXT3-fs: mounted filesystem with ordered
> data mode.
> Feb 27 20:49:49 kuza kernel: SELinux:  Disabled at runtime.
> Feb 27 20:49:49 kuza kernel: SELinux:  Unregistering netfilter hooks
> Feb 27 20:49:49 kuza kernel: audit(1330375739.875:2): selinux=0
> auid=4294967295
> Feb 27 20:49:49 kuza kernel: alim7101_wdt: Steve Hill <steve at navaho.co.uk>.
> Feb 27 20:49:49 kuza kernel: alim7101_wdt: Detected old alim7101
> revision 'a1d'.  If this is a cobalt board, set the 'use_gpio' module
> parameter.
> Feb 27 20:49:49 kuza kernel: input: PC Speaker as /class/input/input3
> Feb 27 20:49:49 kuza kernel: hdc: ATAPI 8X CD-ROM drive, 128kB Cache, DMA
> Feb 27 20:49:49 kuza kernel: Uniform CD-ROM driver Revision: 3.20
> Feb 27 20:49:49 kuza kernel: 8139too Fast Ethernet driver 0.9.28
> Feb 27 20:49:49 kuza kernel: ACPI: PCI Interrupt Link [LNKC] enabled at
> IRQ 10
> Feb 27 20:49:49 kuza kernel: ACPI: PCI Interrupt 0000:00:0a.0[A] -> Link
> [LNKC] -> GSI 10 (level, low) -> IRQ 10
> Feb 27 20:49:49 kuza kernel: eth0: RealTek RTL8139 at 0xd081e000,
> 00:50:ba:5f:e4:c3, IRQ 10
> Feb 27 20:49:49 kuza kernel: Floppy drive(s): fd0 is 1.44M
> Feb 27 20:49:49 kuza kernel: FDC 0 is a post-1991 82077
> Feb 27 20:49:49 kuza kernel: ACPI: PCI Interrupt Link [LNKI] enabled at
> IRQ 9
> Feb 27 20:49:49 kuza kernel: ACPI: PCI Interrupt 0000:00:02.0[A] -> Link
> [LNKI] -> GSI 9 (level, low) -> IRQ 9
> Feb 27 20:49:49 kuza kernel: ohci_hcd 0000:00:02.0: OHCI Host Controller
> Feb 27 20:49:49 kuza kernel: ohci_hcd 0000:00:02.0: new USB bus
> registered, assigned bus number 1
> Feb 27 20:49:49 kuza kernel: ohci_hcd 0000:00:02.0: irq 9, io mem 0xeb800000
> Feb 27 20:49:49 kuza kernel: usb usb1: configuration #1 chosen from 1 choice
> Feb 27 20:49:49 kuza kernel: hub 1-0:1.0: USB hub found
> Feb 27 20:49:49 kuza kernel: hub 1-0:1.0: 4 ports detected
> Feb 27 20:49:49 kuza kernel: ACPI: PCI Interrupt Link [LNKE] enabled at
> IRQ 5
> Feb 27 20:49:49 kuza kernel: ACPI: PCI Interrupt 0000:00:06.0[A] -> Link
> [LNKE] -> GSI 5 (level, low) -> IRQ 5
> Feb 27 20:49:49 kuza kernel: ohci_hcd 0000:00:06.0: OHCI Host Controller
> Feb 27 20:49:49 kuza kernel: ohci_hcd 0000:00:06.0: new USB bus
> registered, assigned bus number 2
> Feb 27 20:49:49 kuza kernel: ohci_hcd 0000:00:06.0: irq 5, io mem 0xea800000
> Feb 27 20:49:49 kuza kernel: usb usb2: configuration #1 chosen from 1 choice
> Feb 27 20:49:49 kuza kernel: hub 2-0:1.0: USB hub found
> Feb 27 20:49:49 kuza kernel: hub 2-0:1.0: 2 ports detected
> Feb 27 20:49:49 kuza kernel: usb 1-1: new low speed USB device using
> ohci_hcd and address 2
> Feb 27 20:49:49 kuza kernel: usb 1-1: configuration #1 chosen from 1 choice
> Feb 27 20:49:49 kuza kernel: parport: PnPBIOS parport detected.
> Feb 27 20:49:49 kuza kernel: parport0: PC-style at 0x378 (0x778), irq 7
> [PCSPP,TRISTATE]
> Feb 27 20:49:49 kuza kernel: lp0: using parport0 (interrupt-driven).
> Feb 27 20:49:49 kuza kernel: lp0: console ready
> Feb 27 20:49:49 kuza kernel: hiddev96: USB HID v1.10 Device [American
> Power Conversion Back-UPS XS 1300 LCD FW:836.H5 .D USB FW:H5 ] on
> usb-0000:00:02.0-1
> Feb 27 20:49:49 kuza kernel: NET: Registered protocol family 10
> Feb 27 20:49:49 kuza kernel: lo: Disabled Privacy Extensions
> Feb 27 20:49:49 kuza kernel: Mobile IPv6
> Feb 27 20:49:49 kuza kernel: input: Power Button (FF) as /class/input/input4
> Feb 27 20:49:49 kuza kernel: ACPI: Power Button (FF) [PWRF]
> Feb 27 20:49:49 kuza kernel: input: Power Button (CM) as /class/input/input5
> Feb 27 20:49:49 kuza kernel: ACPI: Power Button (CM) [PWRB]
> Feb 27 20:49:49 kuza kernel: No dock devices found.
> Feb 27 20:49:49 kuza kernel: ibm_acpi: ec object not found
> Feb 27 20:49:49 kuza kernel: md: Autodetecting RAID arrays.
> Feb 27 20:49:49 kuza kernel: md: autorun ...
> Feb 27 20:49:49 kuza kernel: md: ... autorun DONE.
> Feb 27 20:49:49 kuza kernel: device-mapper: ioctl: 4.11.0-ioctl
> (2006-10-12) initialised: dm-devel at redhat.com
> Feb 27 20:49:49 kuza kernel: EXT3 FS on hda5, internal journal
> Feb 27 20:49:49 kuza kernel: kjournald starting.  Commit interval 5 seconds
> Feb 27 20:49:49 kuza kernel: EXT3 FS on hda1, internal journal
> Feb 27 20:49:49 kuza kernel: EXT3-fs: mounted filesystem with ordered
> data mode.
> Feb 27 20:49:49 kuza kernel: kjournald starting.  Commit interval 5 seconds
> Feb 27 20:49:49 kuza kernel: EXT3 FS on hdb1, internal journal
> Feb 27 20:49:50 kuza kernel: EXT3-fs: mounted filesystem with ordered
> data mode.
> Feb 27 20:49:50 kuza kernel: kjournald starting.  Commit interval 5 seconds
> Feb 27 20:49:50 kuza kernel: EXT3 FS on hda2, internal journal
> Feb 27 20:49:50 kuza kernel: EXT3-fs: mounted filesystem with ordered
> data mode.
> Feb 27 20:49:50 kuza kernel: Adding 514072k swap on /dev/hda3.
> Priority:-1 extents:1 across:514072k
> Feb 27 20:49:50 kuza kernel: eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
> Feb 27 20:49:53 kuza kernel: Bluetooth: Core ver 2.11
> Feb 27 20:49:53 kuza kernel: NET: Registered protocol family 31
> Feb 27 20:49:53 kuza kernel: Bluetooth: HCI device and connection
> manager initialized
> Feb 27 20:49:53 kuza kernel: Bluetooth: HCI socket layer initialized
> Feb 27 20:49:53 kuza kernel: Bluetooth: L2CAP ver 2.8
> Feb 27 20:49:53 kuza kernel: Bluetooth: L2CAP socket layer initialized
> Feb 27 20:49:53 kuza kernel: Bluetooth: HIDP (Human Interface Emulation)
> ver 1.1
> Feb 27 20:49:53 kuza hidd[1621]: Bluetooth HID daemon
> Feb 27 20:49:56 kuza smartd[1719]: smartd version 5.36
> [i686-redhat-linux-gnu] Copyright (C) 2002-6 Bruce Allen
> Feb 27 20:49:56 kuza smartd[1719]: Home page is
> http://smartmontools.sourceforge.net/
> Feb 27 20:49:56 kuza smartd[1719]: Opened configuration file
> /etc/smartd.conf
> Feb 27 20:49:56 kuza smartd[1719]: Configuration file /etc/smartd.conf
> parsed.
> Feb 27 20:49:56 kuza smartd[1719]: Device: /dev/hda, opened
> Feb 27 20:49:56 kuza smartd[1719]: Device: /dev/hda, found in smartd
> database.
> Feb 27 20:49:57 kuza smartd[1719]: Device: /dev/hda, is SMART capable.
> Adding to "monitor" list.
> Feb 27 20:49:57 kuza smartd[1719]: Device: /dev/hdb, opened
> Feb 27 20:49:57 kuza smartd[1719]: Device: /dev/hdb, not found in smartd
> database.
> Feb 27 20:49:58 kuza smartd[1719]: Device: /dev/hdb, is SMART capable.
> Adding to "monitor" list.
> Feb 27 20:49:58 kuza smartd[1719]: Monitoring 2 ATA and 0 SCSI devices
> Feb 27 20:49:59 kuza smartd[1724]: smartd has fork()ed into background
> mode. New PID=1724.
> Feb 27 20:49:59 kuza hpiod: 1.6.6a accepting connections at 50000...
> Feb 27 20:50:06 kuza xinetd[1770]: xinetd Version 2.3.13 started with
> libwrap loadavg options compiled in.
> Feb 27 20:50:06 kuza xinetd[1770]: Started working: 1 available service
> Feb 27 20:50:06 kuza exportfs[1803]: No host name given with /data
> (sync,rw), suggest *(sync,rw) to avoid warning
> Feb 27 20:50:06 kuza apcupsd[1789]: apcupsd 3.12.4 (19 August 2006)
> redhat startup succeeded
> Feb 27 20:50:06 kuza apcupsd[1789]: NIS server startup succeeded
> Feb 27 20:50:07 kuza kernel: Installing knfsd (copyright (C) 1996
> okir at monad.swb.de).
> Feb 27 20:50:07 kuza kernel: NFSD: Using /var/lib/nfs/v4recovery as the
> NFSv4 state recovery directory
> Feb 27 20:50:07 kuza kernel: NFSD: starting 90-second grace period
> Feb 27 20:50:08 kuza gpm[1855]: *** info [startup.c(95)]:
> Feb 27 20:50:08 kuza gpm[1855]: Started gpm successfully. Entered daemon
> mode.
> Feb 27 20:50:20 kuza avahi-daemon[2009]: Found user 'avahi' (UID 70) and
> group 'avahi' (GID 70).
> Feb 27 20:50:20 kuza avahi-daemon[2009]: Successfully dropped root
> privileges.
> Feb 27 20:50:20 kuza avahi-daemon[2009]: avahi-daemon 0.6.11 starting up.
> Feb 27 20:50:20 kuza avahi-daemon[2009]: WARNING: No NSS support for
> mDNS detected, consider installing nss-mdns!
> Feb 27 20:50:21 kuza avahi-daemon[2009]: Successfully called chroot().
> Feb 27 20:50:21 kuza avahi-daemon[2009]: Successfully dropped remaining
> capabilities.
> Feb 27 20:50:21 kuza avahi-daemon[2009]: No service found in
> /etc/avahi/services.
> Feb 27 20:50:21 kuza avahi-daemon[2009]: New relevant interface
> eth0.IPv6 for mDNS.
> Feb 27 20:50:21 kuza avahi-daemon[2009]: Joining mDNS multicast group on
> interface eth0.IPv6 with address fe80::250:baff:fe5f:e4c3.
> Feb 27 20:50:21 kuza avahi-daemon[2009]: New relevant interface
> eth0.IPv4 for mDNS.
> Feb 27 20:50:21 kuza avahi-daemon[2009]: Joining mDNS multicast group on
> interface eth0.IPv4 with address 192.168.1.3.
> Feb 27 20:50:21 kuza avahi-daemon[2009]: Network interface enumeration
> completed.
> Feb 27 20:50:21 kuza avahi-daemon[2009]: Registering new address record
> for fe80::250:baff:fe5f:e4c3 on eth0.
> Feb 27 20:50:21 kuza avahi-daemon[2009]: Registering new address record
> for 192.168.1.3 on eth0.
> Feb 27 20:50:21 kuza avahi-daemon[2009]: Registering HINFO record with
> values 'I686'/'LINUX'.
> Feb 27 20:50:21 kuza avahi-daemon[2009]: Server startup complete. Host
> name is kuza.local. Local service cookie is 2874978490.
> Feb 27 20:56:06 kuza nmbd[1930]: [2012/02/27 20:56:06, 0]
> nmbd/nmbd_become_lmb.c:become_local_master_stage2(396)
> Feb 27 20:56:06 kuza nmbd[1930]:   *****
> Feb 27 20:56:06 kuza nmbd[1930]:
> Feb 27 20:56:06 kuza nmbd[1930]:   Samba name server KUZA is now a local
> master browser for workgroup WORKGROUP on subnet 192.168.1.3
> Feb 27 20:56:06 kuza nmbd[1930]:
> Feb 27 20:56:06 kuza nmbd[1930]:   *****
> _______________________________________________
> mdlug mailing list
> mdlug at mdlug.org
> http://mdlug.org/mailman/listinfo/mdlug
>

From billings at negate.org  Mon Feb 27 21:33:03 2012
From: billings at negate.org (Jonathan Billings)
Date: Mon, 27 Feb 2012 21:33:03 -0500
Subject: [mdlug] hanging machine kernel panic - on going
In-Reply-To: <4F4C3495.3060809@gmail.com>
References: <1329051074.36045.yint-ygo-j2me@web110616.mail.gq1.yahoo.com>	<4F37BFFE.4080500@wowway.com>	<CA+czFiD9=Ccp=+202FJMr+ugDxXFo84GLrxjXvrCdQoOHZG=xA@mail.gmail.com>
	<1329061686.3307.5.camel@linux-dauq.site>
	<4F37EFA2.6070906@wowway.com> <4F4C3495.3060809@gmail.com>
Message-ID: <C55F83EF-C36E-4E68-9A97-9881FDC92BEA@negate.org>


On Feb 27, 2012, at 8:57 PM, Gmail-otakurider wrote:

> Feb 27 16:53:41 kuza kernel: BUG: unable to handle kernel NULL pointer
> dereference at virtual address 00000000
> Feb 27 16:53:41 kuza kernel:  printing eip:
> Feb 27 16:53:41 kuza kernel: cab88e5c
> Feb 27 16:53:41 kuza kernel: *pde = 09606067
> Feb 27 16:53:41 kuza kernel: Oops: 0002 [#1]
> Feb 27 16:53:41 kuza kernel: last sysfs file: /block/hda/hda1/size
> Feb 27 16:53:41 kuza kernel: Modules linked in: nfsd exportfs lockd
> nfs_acl autofs4 hidp l2cap bluetooth sunrpc dm_mirror dm_mod video sbs
> i2c_ec dock container button battery asus_acpi backlight ac ipv6 lp
> parport_pc parport floppy ohci_hcd 8139too i2c_ali15x3 serio_raw mii
> i2c_ali1535 i2c_core pcspkr ide_cd cdrom ext3 jbd
> Feb 27 16:53:41 kuza kernel: CPU:    0
> Feb 27 16:53:41 kuza kernel: EIP:    0060:[<cab88e5c>]    Not tainted VLI
> Feb 27 16:53:41 kuza kernel: EFLAGS: 00210206   (2.6.20-1.2320.fc5 #1)
> Feb 27 16:53:41 kuza kernel: EIP is at 0xcab88e5c
> Feb 27 16:53:41 kuza kernel: eax: 00000000   ebx: cab88f9c   ecx:
> ca3c3610   edx: c137c980
> Feb 27 16:53:41 kuza kernel: esi: cab88f48   edi: 00000006   ebp:
> cab88e58   esp: cab88ba4
> Feb 27 16:53:41 kuza kernel: ds: 007b   es: 007b   ss: 0068
> Feb 27 16:53:41 kuza kernel: Process python (pid: 1745, ti=cab88000
> task=cfec30d0 task.ti=cab88000)

Ok, so python was the current task when it panicked.  This is most likely not the cause, just what happened to be currently operating.

> Feb 27 16:53:41 kuza kernel: Stack: cab88e60 cab88e4c cab88e50 cab88e54
> 00000030 00000000 00000000 00000030
> Feb 27 16:53:41 kuza kernel:        00000000 00000000 00000000 00000000
> 00000000 00000000 c046ad08 00000000
> Feb 27 16:53:41 kuza kernel:        00000000 00000002 ccd0f320 00000000
> cfec30d0 c0419bdc 00100100 00200200
> Feb 27 16:53:41 kuza kernel: Call Trace:
> Feb 27 16:53:41 kuza kernel:  [<c046ad08>] __pollwait+0x0/0xab
> Feb 27 16:53:41 kuza kernel:  [<c0419bdc>] default_wake_function+0x0/0xc
> Feb 27 16:53:41 kuza kernel:  [<c0419bdc>] default_wake_function+0x0/0xc
> Feb 27 16:53:41 kuza kernel:  [<d082fb73>]
> do_get_write_access+0x48b/0x4b8 [jbd]
> Feb 27 16:53:41 kuza kernel:  [<d08885f8>]
> __ext3_get_inode_loc+0x10a/0x2fd [ext3]
> Feb 27 16:53:41 kuza kernel:  [<c0608164>] _read_unlock_irq+0x5/0x7
> Feb 27 16:53:41 kuza kernel:  [<d0893712>]
> __ext3_journal_dirty_metadata+0x16/0x3a [ext3]
> Feb 27 16:53:41 kuza kernel:  [<d082fbc1>]
> journal_get_write_access+0x21/0x26 [jbd]
> Feb 27 16:53:41 kuza kernel:  [<d0888489>]
> ext3_mark_iloc_dirty+0x275/0x2da [ext3]
> Feb 27 16:53:41 kuza kernel:  [<c0418de8>] __wake_up+0x32/0x43
> Feb 27 16:53:41 kuza kernel:  [<d082f6dc>] journal_stop+0x1cb/0x1d7 [jbd]
> Feb 27 16:53:41 kuza kernel:  [<d088f703>] __ext3_journal_stop+0x19/0x34
> [ext3]
> Feb 27 16:53:41 kuza kernel:  [<d088a6b2>]
> ext3_ordered_commit_write+0xba/0xd8 [ext3]
> Feb 27 16:53:41 kuza kernel:  [<c044aaa7>] __pagevec_lru_add+0x7a/0x85
> Feb 27 16:53:41 kuza kernel:  [<c0446328>]
> generic_file_buffered_write+0x579/0x5e8
> Feb 27 16:53:41 kuza kernel:  [<c047aa2a>] __getblk+0x3b/0x287
> Feb 27 16:53:41 kuza kernel:  [<c0420638>] current_fs_time+0x45/0x51
> Feb 27 16:53:41 kuza kernel:  [<c0405e65>] do_IRQ+0xbf/0xd6
> Feb 27 16:53:41 kuza kernel:  [<c0404763>] common_interrupt+0x23/0x28
> Feb 27 16:53:41 kuza kernel:  [<c046aa67>] core_sys_select+0x2d2/0x2f3
> Feb 27 16:53:41 kuza kernel:  [<c0448dff>] __alloc_pages+0x68/0x29c
> Feb 27 16:53:41 kuza kernel:  [<c0608164>] _read_unlock_irq+0x5/0x7
> Feb 27 16:53:41 kuza kernel:  [<c0444c30>] find_get_page+0x35/0x3a
> Feb 27 16:53:41 kuza kernel:  [<c044710b>] filemap_nopage+0x159/0x2d4
> Feb 27 16:53:41 kuza kernel:  [<c044f9c9>] __handle_mm_fault+0x858/0x87a
> Feb 27 16:53:41 kuza kernel:  [<c0452bf4>] do_mmap_pgoff+0x587/0x6e8
> Feb 27 16:53:41 kuza kernel:  [<c046b04e>] sys_select+0xa0/0x186
> Feb 27 16:53:41 kuza kernel:  [<c0403dc8>] syscall_call+0x7/0xb
> Feb 27 16:53:41 kuza kernel:  =======================

The above call stack seems to indicate it was in the middle of a kernel operation with opearting on the ext3 journal.  If I recall how this works, it looks like a case of running out of memory during a kernel system call?

> Feb 27 16:53:41 kuza kernel: Code: aa 46 c0 48 4b c3 bf ea ff ff ff 00
> e0 9a 08 00 e0 9a 08 06 00 00 00 30 00 00 00 00 00 00 00 00 00 00 00 00
> 00 00 00 00 00 00 00 <00> 00 00 00 44 00 00 00 46 02 20 00 01 00 00 00
> 00 00 00 00 d2
> Feb 27 16:53:41 kuza kernel: EIP: [<cab88e5c>] 0xcab88e5c SS:ESP
> 0068:cab88ba4
> Feb 27 20:04:54 kuza avahi-daemon[2006]: Invalid query packet.
> Feb 27 20:05:38 kuza last message repeated 30 times
> Feb 27 20:49:41 kuza syslogd 1.4.1: restart.
> Feb 27 20:49:41 kuza kernel: klogd 1.4.1, log source = /proc/kmsg started.

I see a couple avahi-daemon entries before the machine was reset, making me think that some part of the system was still responding, enough to write log entries, unless you grabbed this off a remote syslog.

--
Jonathan Billings <billings at negate.org>



From lugnuts at doehler.us  Mon Feb 27 23:37:15 2012
From: lugnuts at doehler.us (Joe Doehler)
Date: Mon, 27 Feb 2012 23:37:15 -0500
Subject: [mdlug] hanging machine kernel panic - on going
In-Reply-To: <4F4C3495.3060809@gmail.com>
References: <1329051074.36045.yint-ygo-j2me@web110616.mail.gq1.yahoo.com>	<4F37BFFE.4080500@wowway.com>	<CA+czFiD9=Ccp=+202FJMr+ugDxXFo84GLrxjXvrCdQoOHZG=xA@mail.gmail.com>
	<1329061686.3307.5.camel@linux-dauq.site>
	<4F37EFA2.6070906@wowway.com> <4F4C3495.3060809@gmail.com>
Message-ID: <4F4C59FB.6080606@doehler.us>

On 2/27/2012 8:57 PM, Gmail-otakurider wrote:
> Here is the messages dump - check around 16:53 anyone have any
> ideas? checked memory tested ok - checked HDD tested ok
>
> Yes I know its long but wanted to give all info

You have evidently already checked the most obvious possibilities, so
here are some more uncommon ones. In your shoes, I would check/do a few
other things.

1-
> Feb 27 11:18:52 kuza avahi-daemon[2006]: Invalid query packet.
 > Feb 27 11:19:32 kuza last message repeated 26 times
 > Feb 27 11:19:32 kuza avahi-daemon[2006]: Invalid query packet.

I would disable "avahi". If a network is configured properly, it should
not be needed. It can cause problems if you have both Microsoft and
Apple devices on your network; they have incompatible responses to a
network that they think is ill.

2-
> Feb 27 20:49:43 kuza kernel: ACPI: Unable to derive IRQ for device
> 0000:00:04.0

I would try disabling any power management. I would try to see what that
device (0000:00:04.0) is; do "lspci" and see if what is returned matches
what is actually plugged in. Take out that device if possible to check
if stability returns; could be a bad device or a bad driver.

3-
Memory problems are often misdiagnosed when a machine operates in
Protected Mode. Because of its complicated logic, the MMU onboard the
CPU chip is frequently the first thing to misfire when the CPU gets too
hot, making it look like memory problems. To what extent the MMU was
stressed during your "memory" check depends on the software doing the
checking. So, check the chip temperature. Can you do that while the
machine is busy?

4-
Disconnect USB devices. If more than one USB device is connected with a
hub w/o its own power, more current may be drawn than any one USB plug
is capable of delivering, causing severe crashes. This can happen even
w/o a hub.

I don't claim to have the answers, but I hope this helps.

Joe.

From akulkis00 at gmail.com  Tue Feb 28 10:47:07 2012
From: akulkis00 at gmail.com (Aaron Kulkis)
Date: Tue, 28 Feb 2012 10:47:07 -0500
Subject: [mdlug] hanging machine kernel panic - on going
In-Reply-To: <4F4C3495.3060809@gmail.com>
References: <1329051074.36045.yint-ygo-j2me@web110616.mail.gq1.yahoo.com>	<4F37BFFE.4080500@wowway.com>	<CA+czFiD9=Ccp=+202FJMr+ugDxXFo84GLrxjXvrCdQoOHZG=xA@mail.gmail.com>
	<1329061686.3307.5.camel@linux-dauq.site>
	<4F37EFA2.6070906@wowway.com> <4F4C3495.3060809@gmail.com>
Message-ID: <4F4CF6FB.4070607@gmail.com>

Gmail-otakurider wrote:
> Here is the messages dump - check around 16:53 anyone have any ideas?
> checked memory tested ok - checked HDD tested ok
>


I've been getting some panics lately, too.  My suspicion
is that a kernel bug was recently introduced.  I also trust
that with time, it will be found and go away.

Fortunately, I still have some habits from my college days
when Purdue's Electrical Engineering department was the
primary test site for Gould Electronics' high performance
Unix division, and endured periods in which typical
uptime was <90 minutes, until the problems were found
and resolved.

> Yes I know its long but wanted to give all info
>
>   thinking of setting panic=  setting to have it just reboot
>
> Thank in advance
>
>
>
> Feb 27 10:37:30 kuza avahi-daemon[2006]: Network interface enumeration
> completed.
> Feb 27 10:37:30 kuza avahi-daemon[2006]: Registering new address record
> for fe80::250:baff:fe5f:e4c3 on eth0.
> Feb 27 10:37:30 kuza avahi-daemon[2006]: Registering new address record
> for 192.168.1.3 on eth0.
> Feb 27 10:37:30 kuza avahi-daemon[2006]: Registering HINFO record with
> values 'I686'/'LINUX'.
> Feb 27 10:37:31 kuza avahi-daemon[2006]: Server startup complete. Host
> name is kuza.local. Local service cookie is 1101511634.
> Feb 27 10:43:10 kuza nmbd[1926]: [2012/02/27 10:43:10, 0]
> nmbd/nmbd_become_lmb.c:become_local_master_stage2(396)
> Feb 27 10:43:10 kuza nmbd[1926]:   *****
> Feb 27 10:43:10 kuza nmbd[1926]:
> Feb 27 10:43:10 kuza nmbd[1926]:   Samba name server KUZA is now a local
> master browser for workgroup WORKGROUP on subnet 192.168.1.3
> Feb 27 10:43:10 kuza nmbd[1926]:
> Feb 27 10:43:10 kuza nmbd[1926]:   *****
> Feb 27 11:18:52 kuza avahi-daemon[2006]: Invalid query packet.
> Feb 27 11:19:32 kuza last message repeated 26 times
> Feb 27 11:19:32 kuza avahi-daemon[2006]: Invalid query packet.
> Feb 27 16:53:41 kuza kernel: BUG: unable to handle kernel NULL pointer
> dereference at virtual address 00000000
> Feb 27 16:53:41 kuza kernel:  printing eip:
> Feb 27 16:53:41 kuza kernel: cab88e5c
> Feb 27 16:53:41 kuza kernel: *pde = 09606067
> Feb 27 16:53:41 kuza kernel: Oops: 0002 [#1]
> Feb 27 16:53:41 kuza kernel: last sysfs file: /block/hda/hda1/size
> Feb 27 16:53:41 kuza kernel: Modules linked in: nfsd exportfs lockd
> nfs_acl autofs4 hidp l2cap bluetooth sunrpc dm_mirror dm_mod video sbs
> i2c_ec dock container button battery asus_acpi backlight ac ipv6 lp
> parport_pc parport floppy ohci_hcd 8139too i2c_ali15x3 serio_raw mii
> i2c_ali1535 i2c_core pcspkr ide_cd cdrom ext3 jbd
> Feb 27 16:53:41 kuza kernel: CPU:    0
> Feb 27 16:53:41 kuza kernel: EIP:    0060:[<cab88e5c>]    Not tainted VLI
> Feb 27 16:53:41 kuza kernel: EFLAGS: 00210206   (2.6.20-1.2320.fc5 #1)
> Feb 27 16:53:41 kuza kernel: EIP is at 0xcab88e5c
> Feb 27 16:53:41 kuza kernel: eax: 00000000   ebx: cab88f9c   ecx:
> ca3c3610   edx: c137c980
> Feb 27 16:53:41 kuza kernel: esi: cab88f48   edi: 00000006   ebp:
> cab88e58   esp: cab88ba4
> Feb 27 16:53:41 kuza kernel: ds: 007b   es: 007b   ss: 0068
> Feb 27 16:53:41 kuza kernel: Process python (pid: 1745, ti=cab88000
> task=cfec30d0 task.ti=cab88000)
> Feb 27 16:53:41 kuza kernel: Stack: cab88e60 cab88e4c cab88e50 cab88e54
> 00000030 00000000 00000000 00000030
> Feb 27 16:53:41 kuza kernel:        00000000 00000000 00000000 00000000
> 00000000 00000000 c046ad08 00000000
> Feb 27 16:53:41 kuza kernel:        00000000 00000002 ccd0f320 00000000
> cfec30d0 c0419bdc 00100100 00200200
> Feb 27 16:53:41 kuza kernel: Call Trace:
> Feb 27 16:53:41 kuza kernel:  [<c046ad08>] __pollwait+0x0/0xab
> Feb 27 16:53:41 kuza kernel:  [<c0419bdc>] default_wake_function+0x0/0xc
> Feb 27 16:53:41 kuza kernel:  [<c0419bdc>] default_wake_function+0x0/0xc
> Feb 27 16:53:41 kuza kernel:  [<d082fb73>]
> do_get_write_access+0x48b/0x4b8 [jbd]
> Feb 27 16:53:41 kuza kernel:  [<d08885f8>]
> __ext3_get_inode_loc+0x10a/0x2fd [ext3]
> Feb 27 16:53:41 kuza kernel:  [<c0608164>] _read_unlock_irq+0x5/0x7
> Feb 27 16:53:41 kuza kernel:  [<d0893712>]
> __ext3_journal_dirty_metadata+0x16/0x3a [ext3]
> Feb 27 16:53:41 kuza kernel:  [<d082fbc1>]
> journal_get_write_access+0x21/0x26 [jbd]
> Feb 27 16:53:41 kuza kernel:  [<d0888489>]
> ext3_mark_iloc_dirty+0x275/0x2da [ext3]
> Feb 27 16:53:41 kuza kernel:  [<c0418de8>] __wake_up+0x32/0x43
> Feb 27 16:53:41 kuza kernel:  [<d082f6dc>] journal_stop+0x1cb/0x1d7 [jbd]
> Feb 27 16:53:41 kuza kernel:  [<d088f703>] __ext3_journal_stop+0x19/0x34
> [ext3]
> Feb 27 16:53:41 kuza kernel:  [<d088a6b2>]
> ext3_ordered_commit_write+0xba/0xd8 [ext3]
> Feb 27 16:53:41 kuza kernel:  [<c044aaa7>] __pagevec_lru_add+0x7a/0x85
> Feb 27 16:53:41 kuza kernel:  [<c0446328>]
> generic_file_buffered_write+0x579/0x5e8
> Feb 27 16:53:41 kuza kernel:  [<c047aa2a>] __getblk+0x3b/0x287
> Feb 27 16:53:41 kuza kernel:  [<c0420638>] current_fs_time+0x45/0x51
> Feb 27 16:53:41 kuza kernel:  [<c0405e65>] do_IRQ+0xbf/0xd6
> Feb 27 16:53:41 kuza kernel:  [<c0404763>] common_interrupt+0x23/0x28
> Feb 27 16:53:41 kuza kernel:  [<c046aa67>] core_sys_select+0x2d2/0x2f3
> Feb 27 16:53:41 kuza kernel:  [<c0448dff>] __alloc_pages+0x68/0x29c
> Feb 27 16:53:41 kuza kernel:  [<c0608164>] _read_unlock_irq+0x5/0x7
> Feb 27 16:53:41 kuza kernel:  [<c0444c30>] find_get_page+0x35/0x3a
> Feb 27 16:53:41 kuza kernel:  [<c044710b>] filemap_nopage+0x159/0x2d4
> Feb 27 16:53:41 kuza kernel:  [<c044f9c9>] __handle_mm_fault+0x858/0x87a
> Feb 27 16:53:41 kuza kernel:  [<c0452bf4>] do_mmap_pgoff+0x587/0x6e8
> Feb 27 16:53:41 kuza kernel:  [<c046b04e>] sys_select+0xa0/0x186
> Feb 27 16:53:41 kuza kernel:  [<c0403dc8>] syscall_call+0x7/0xb
> Feb 27 16:53:41 kuza kernel:  =======================
> Feb 27 16:53:41 kuza kernel: Code: aa 46 c0 48 4b c3 bf ea ff ff ff 00
> e0 9a 08 00 e0 9a 08 06 00 00 00 30 00 00 00 00 00 00 00 00 00 00 00 00
> 00 00 00 00 00 00 00<00>  00 00 00 44 00 00 00 46 02 20 00 01 00 00 00
> 00 00 00 00 d2
> Feb 27 16:53:41 kuza kernel: EIP: [<cab88e5c>] 0xcab88e5c SS:ESP
> 0068:cab88ba4
> Feb 27 20:04:54 kuza avahi-daemon[2006]: Invalid query packet.
> Feb 27 20:05:38 kuza last message repeated 30 times
> Feb 27 20:49:41 kuza syslogd 1.4.1: restart.
> Feb 27 20:49:41 kuza kernel: klogd 1.4.1, log source = /proc/kmsg started.
> Feb 27 20:49:41 kuza kernel: Linux version 2.6.20-1.2320.fc5
> (brewbuilder at hs20-bc2-2.build.redhat.com) (gcc version 4.1.1 20070105
> (Red Hat 4.1.1-51)) #1 Tue Jun 12 18:50:38 EDT 2007
> Feb 27 20:49:41 kuza kernel: BIOS-provided physical RAM map:
> Feb 27 20:49:41 kuza kernel: sanitize start
> Feb 27 20:49:41 kuza kernel: sanitize end
> Feb 27 20:49:41 kuza kernel: copy_e820_map() start: 0000000000000000
> size: 000000000009fc00 end: 000000000009fc00 type: 1
> Feb 27 20:49:41 kuza kernel: copy_e820_map() type is E820_RAM
> Feb 27 20:49:41 kuza kernel: copy_e820_map() start: 000000000009fc00
> size: 0000000000000400 end: 00000000000a0000 type: 2
> Feb 27 20:49:41 kuza kernel: copy_e820_map() start: 00000000000f0000
> size: 0000000000010000 end: 0000000000100000 type: 2
> Feb 27 20:49:41 kuza kernel: copy_e820_map() start: 0000000000100000
> size: 000000000feec000 end: 000000000ffec000 type: 1
> Feb 27 20:49:41 kuza kernel: copy_e820_map() type is E820_RAM
> Feb 27 20:49:41 kuza kernel: copy_e820_map() start: 000000000ffec000
> size: 0000000000003000 end: 000000000ffef000 type: 3
> Feb 27 20:49:41 kuza kernel: copy_e820_map() start: 000000000ffef000
> size: 0000000000010000 end: 000000000ffff000 type: 2
> Feb 27 20:49:41 kuza kernel: copy_e820_map() start: 000000000ffff000
> size: 0000000000001000 end: 0000000010000000 type: 4
> Feb 27 20:49:41 kuza kernel: copy_e820_map() start: 00000000ffff0000
> size: 0000000000010000 end: 0000000100000000 type: 2
> Feb 27 20:49:41 kuza kernel:  BIOS-e820: 0000000000000000 -
> 000000000009fc00 (usable)
> Feb 27 20:49:41 kuza kernel:  BIOS-e820: 000000000009fc00 -
> 00000000000a0000 (reserved)
> Feb 27 20:49:41 kuza kernel:  BIOS-e820: 00000000000f0000 -
> 0000000000100000 (reserved)
> Feb 27 20:49:41 kuza kernel:  BIOS-e820: 0000000000100000 -
> 000000000ffec000 (usable)
> Feb 27 20:49:41 kuza kernel:  BIOS-e820: 000000000ffec000 -
> 000000000ffef000 (ACPI data)
> Feb 27 20:49:41 kuza kernel:  BIOS-e820: 000000000ffef000 -
> 000000000ffff000 (reserved)
> Feb 27 20:49:41 kuza kernel:  BIOS-e820: 000000000ffff000 -
> 0000000010000000 (ACPI NVS)
> Feb 27 20:49:41 kuza kernel:  BIOS-e820: 00000000ffff0000 -
> 0000000100000000 (reserved)
> Feb 27 20:49:41 kuza kernel: 0MB HIGHMEM available.
> Feb 27 20:49:41 kuza kernel: 255MB LOWMEM available.
> Feb 27 20:49:41 kuza kernel: Using x86 segment limits to approximate NX
> protection
> Feb 27 20:49:41 kuza kernel: Zone PFN ranges:
> Feb 27 20:49:41 kuza kernel:   DMA             0 ->      4096
> Feb 27 20:49:43 kuza kernel:   Normal       4096 ->     65516
> Feb 27 20:49:43 kuza kernel:   HighMem     65516 ->     65516
> Feb 27 20:49:43 kuza kernel: early_node_map[1] active PFN ranges
> Feb 27 20:49:43 kuza kernel:     0:        0 ->     65516
> Feb 27 20:49:43 kuza kernel: DMI 2.3 present.
> Feb 27 20:49:43 kuza kernel: Using APIC driver default
> Feb 27 20:49:43 kuza kernel: ACPI: PM-Timer IO Port: 0xe408
> Feb 27 20:49:43 kuza kernel: Allocating PCI resources starting at
> 20000000 (gap: 10000000:efff0000)
> Feb 27 20:49:43 kuza kernel: Detected 807.940 MHz processor.
> Feb 27 20:49:43 kuza kernel: Built 1 zonelists.  Total pages: 65005
> Feb 27 20:49:43 kuza kernel: Kernel command line: ro root=LABEL=/ rhgb quiet
> Feb 27 20:49:43 kuza kernel: Local APIC disabled by BIOS -- you can
> enable it with "lapic"
> Feb 27 20:49:43 kuza kernel: Enabling fast FPU save and restore... done.
> Feb 27 20:49:43 kuza kernel: Initializing CPU#0
> Feb 27 20:49:43 kuza kernel: CPU 0 irqstacks, hard=c0720000 soft=c071f000
> Feb 27 20:49:43 kuza kernel: PID hash table entries: 1024 (order: 10,
> 4096 bytes)
> Feb 27 20:49:43 kuza kernel: Console: colour VGA+ 80x25
> Feb 27 20:49:43 kuza kernel: Dentry cache hash table entries: 32768
> (order: 5, 131072 bytes)
> Feb 27 20:49:43 kuza kernel: Inode-cache hash table entries: 16384
> (order: 4, 65536 bytes)
> Feb 27 20:49:43 kuza kernel: Memory: 254596k/262064k available (2091k
> kernel code, 6828k reserved, 845k data, 232k init, 0k highmem)
> Feb 27 20:49:43 kuza kernel: virtual kernel memory layout:
> Feb 27 20:49:43 kuza kernel:     fixmap  : 0xfff9b000 - 0xfffff000   (
> 400 kB)
> Feb 27 20:49:43 kuza kernel:     pkmap   : 0xff800000 - 0xffc00000
> (4096 kB)
> Feb 27 20:49:43 kuza kernel:     vmalloc : 0xd0800000 - 0xff7fe000   (
> 751 MB)
> Feb 27 20:49:43 kuza kernel:     lowmem  : 0xc0000000 - 0xcffec000   (
> 255 MB)
> Feb 27 20:49:43 kuza kernel:       .init : 0xc06e0000 - 0xc071a000   (
> 232 kB)
> Feb 27 20:49:43 kuza kernel:       .data : 0xc060aefd - 0xc06de614   (
> 845 kB)
> Feb 27 20:49:43 kuza kernel:       .text : 0xc0400000 - 0xc060aefd
> (2091 kB)
> Feb 27 20:49:43 kuza kernel: Checking if this processor honours the WP
> bit even in supervisor mode... Ok.
> Feb 27 20:49:43 kuza kernel: Calibrating delay using timer specific
> routine.. 1616.55 BogoMIPS (lpj=808275)
> Feb 27 20:49:43 kuza kernel: Security Framework v1.0.0 initialized
> Feb 27 20:49:43 kuza kernel: SELinux:  Initializing.
> Feb 27 20:49:43 kuza kernel: SELinux:  Starting in permissive mode
> Feb 27 20:49:43 kuza kernel: selinux_register_security:  Registering
> secondary module capability
> Feb 27 20:49:43 kuza kernel: Capability LSM initialized as secondary
> Feb 27 20:49:43 kuza kernel: Mount-cache hash table entries: 512
> Feb 27 20:49:43 kuza kernel: CPU: L1 I Cache: 64K (64 bytes/line), D
> cache 64K (64 bytes/line)
> Feb 27 20:49:43 kuza kernel: CPU: L2 Cache: 64K (64 bytes/line)
> Feb 27 20:49:43 kuza kernel: Intel machine check architecture supported.
> Feb 27 20:49:43 kuza kernel: Intel machine check reporting enabled on CPU#0.
> Feb 27 20:49:43 kuza kernel: CPU: AMD Duron(tm) Processor stepping 01
> Feb 27 20:49:43 kuza kernel: Checking 'hlt' instruction... OK.
> Feb 27 20:49:43 kuza kernel: ACPI: Core revision 20060707
> Feb 27 20:49:43 kuza kernel: ACPI: setting ELCR to 0200 (from 0e20)
> Feb 27 20:49:43 kuza kernel: NET: Registered protocol family 16
> Feb 27 20:49:43 kuza kernel: ACPI: bus type pci registered
> Feb 27 20:49:43 kuza kernel: PCI: PCI BIOS revision 2.10 entry at
> 0xf1170, last bus=1
> Feb 27 20:49:43 kuza kernel: PCI: Using configuration type 1
> Feb 27 20:49:43 kuza kernel: Setting up standard PCI resources
> Feb 27 20:49:43 kuza kernel: ACPI: Interpreter enabled
> Feb 27 20:49:43 kuza kernel: ACPI: Using PIC for interrupt routing
> Feb 27 20:49:43 kuza kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5
> 6 7 9 10 *11 12 14 15)
> Feb 27 20:49:43 kuza kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5
> 6 7 9 10 11 12 14 15) *0, disabled.
> Feb 27 20:49:43 kuza kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5
> 6 7 9 *10 11 12 14 15)
> Feb 27 20:49:43 kuza kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5
> 6 7 9 10 11 12 14 15) *0, disabled.
> Feb 27 20:49:43 kuza kernel: ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4
> *5 6 7 9 10 11 12 14 15)
> Feb 27 20:49:43 kuza kernel: ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5
> 6 7 9 10 11 12 14 15) *0, disabled.
> Feb 27 20:49:43 kuza kernel: ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5
> 6 7 9 10 11 12 14 15) *0, disabled.
> Feb 27 20:49:43 kuza kernel: ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5
> 6 7 9 10 11 12 14 15) *0, disabled.
> Feb 27 20:49:43 kuza kernel: ACPI: PCI Interrupt Link [LNKI] (IRQs 3 4 5
> 6 7 *9 10 11 12 14 15)
> Feb 27 20:49:43 kuza kernel: ACPI: PCI Root Bridge [PCI0] (0000:00)
> Feb 27 20:49:43 kuza kernel: ACPI: Assume root bridge [\_SB_.PCI0] bus is 0
> Feb 27 20:49:43 kuza kernel: PCI quirk: region e400-e43f claimed by
> ali7101 ACPI
> Feb 27 20:49:43 kuza kernel: PCI quirk: region e800-e81f claimed by
> ali7101 SMB
> Feb 27 20:49:43 kuza kernel: Linux Plug and Play Support v0.97 (c) Adam
> Belay
> Feb 27 20:49:43 kuza kernel: pnp: PnP ACPI init
> Feb 27 20:49:43 kuza kernel: pnp: PnP ACPI: found 15 devices
> Feb 27 20:49:43 kuza kernel: usbcore: registered new interface driver usbfs
> Feb 27 20:49:43 kuza kernel: usbcore: registered new interface driver hub
> Feb 27 20:49:43 kuza kernel: usbcore: registered new device driver usb
> Feb 27 20:49:43 kuza kernel: PCI: Using ACPI for IRQ routing
> Feb 27 20:49:43 kuza kernel: PCI: If a device doesn't work, try
> "pci=routeirq".  If it helps, post a report
> Feb 27 20:49:43 kuza kernel: NetLabel: Initializing
> Feb 27 20:49:43 kuza kernel: NetLabel:  domain hash size = 128
> Feb 27 20:49:43 kuza kernel: NetLabel:  protocols = UNLABELED CIPSOv4
> Feb 27 20:49:43 kuza kernel: NetLabel:  unlabeled traffic allowed by default
> Feb 27 20:49:43 kuza kernel: pnp: 00:02: ioport range 0xe400-0xe47f
> could not be reserved
> Feb 27 20:49:43 kuza kernel: pnp: 00:02: ioport range 0xe800-0xe81f has
> been reserved
> Feb 27 20:49:43 kuza kernel: pnp: 00:02: ioport range 0x40b-0x40b has
> been reserved
> Feb 27 20:49:43 kuza kernel: pnp: 00:02: ioport range 0x480-0x48f has
> been reserved
> Feb 27 20:49:43 kuza kernel: pnp: 00:02: ioport range 0x4d6-0x4d6 has
> been reserved
> Feb 27 20:49:43 kuza kernel: PCI: Bridge: 0000:00:01.0
> Feb 27 20:49:43 kuza kernel:   IO window: disabled.
> Feb 27 20:49:43 kuza kernel:   MEM window: ec000000-edefffff
> Feb 27 20:49:43 kuza kernel:   PREFETCH window: edf00000-efffffff
> Feb 27 20:49:43 kuza kernel: NET: Registered protocol family 2
> Feb 27 20:49:43 kuza kernel: IP route cache hash table entries: 2048
> (order: 1, 8192 bytes)
> Feb 27 20:49:43 kuza kernel: TCP established hash table entries: 8192
> (order: 5, 131072 bytes)
> Feb 27 20:49:43 kuza kernel: TCP bind hash table entries: 4096 (order:
> 4, 81920 bytes)
> Feb 27 20:49:43 kuza kernel: TCP: Hash tables configured (established
> 8192 bind 4096)
> Feb 27 20:49:43 kuza kernel: TCP reno registered
> Feb 27 20:49:43 kuza kernel: checking if image is initramfs... it is
> Feb 27 20:49:43 kuza kernel: Freeing initrd memory: 913k freed
> Feb 27 20:49:43 kuza kernel: Simple Boot Flag at 0x3a set to 0x1
> Feb 27 20:49:43 kuza kernel: apm: BIOS version 1.2 Flags 0x0b (Driver
> version 1.16ac)
> Feb 27 20:49:43 kuza kernel: apm: overridden by ACPI.
> Feb 27 20:49:43 kuza kernel: audit: initializing netlink socket (disabled)
> Feb 27 20:49:43 kuza kernel: audit(1330375714.653:1): initialized
> Feb 27 20:49:43 kuza kernel: Total HugeTLB memory allocated, 0
> Feb 27 20:49:43 kuza kernel: VFS: Disk quotas dquot_6.5.1
> Feb 27 20:49:43 kuza kernel: Dquot-cache hash table entries: 1024 (order
> 0, 4096 bytes)
> Feb 27 20:49:43 kuza kernel: SELinux:  Registering netfilter hooks
> Feb 27 20:49:43 kuza kernel: ksign: Installing public key data
> Feb 27 20:49:43 kuza kernel: Loading keyring
> Feb 27 20:49:43 kuza kernel: - Added public key FA1AD44A9013A628
> Feb 27 20:49:43 kuza kernel: - User ID: Red Hat, Inc. (Kernel Module GPG
> key)
> Feb 27 20:49:43 kuza kernel: io scheduler noop registered
> Feb 27 20:49:43 kuza kernel: io scheduler anticipatory registered
> Feb 27 20:49:43 kuza kernel: io scheduler deadline registered
> Feb 27 20:49:43 kuza kernel: io scheduler cfq registered (default)
> Feb 27 20:49:43 kuza kernel: Limiting direct PCI/PCI transfers.
> Feb 27 20:49:43 kuza kernel: Activating ISA DMA hang workarounds.
> Feb 27 20:49:43 kuza kernel: pci_hotplug: PCI Hot Plug PCI Core version: 0.5
> Feb 27 20:49:43 kuza kernel: ACPI: Invalid PBLK length [5]
> Feb 27 20:49:43 kuza kernel: isapnp: Scanning for PnP cards...
> Feb 27 20:49:43 kuza kernel: isapnp: No Plug&  Play device found
> Feb 27 20:49:43 kuza kernel: Real Time Clock Driver v1.12ac
> Feb 27 20:49:43 kuza kernel: Non-volatile memory driver v1.2
> Feb 27 20:49:43 kuza kernel: Linux agpgart interface v0.101 (c) Dave Jones
> Feb 27 20:49:43 kuza kernel: agpgart: Detected ALi M1647 chipset
> Feb 27 20:49:43 kuza kernel: agpgart: AGP aperture is 128M @ 0xf0000000
> Feb 27 20:49:43 kuza kernel: Serial: 8250/16550 driver $Revision: 1.90 $
> 4 ports, IRQ sharing enabled
> Feb 27 20:49:43 kuza kernel: serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is
> a 16550A
> Feb 27 20:49:43 kuza kernel: serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is
> a 16550A
> Feb 27 20:49:43 kuza kernel: 00:0b: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
> Feb 27 20:49:43 kuza kernel: 00:0c: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
> Feb 27 20:49:43 kuza kernel: RAMDISK driver initialized: 16 RAM disks of
> 16384K size 4096 blocksize
> Feb 27 20:49:43 kuza kernel: input: Macintosh mouse button emulation as
> /class/input/input0
> Feb 27 20:49:43 kuza kernel: Uniform Multi-Platform E-IDE driver
> Revision: 7.00alpha2
> Feb 27 20:49:43 kuza kernel: ide: Assuming 33MHz system bus speed for
> PIO modes; override with idebus=xx
> Feb 27 20:49:43 kuza kernel: ALI15X3: IDE controller at PCI slot
> 0000:00:04.0
> Feb 27 20:49:43 kuza kernel: ACPI: Unable to derive IRQ for device
> 0000:00:04.0
> Feb 27 20:49:43 kuza kernel: ACPI: PCI Interrupt 0000:00:04.0[A]: no GSI
> Feb 27 20:49:43 kuza kernel: ALI15X3: chipset revision 196
> Feb 27 20:49:43 kuza kernel: ALI15X3: not 100% native mode: will probe
> irqs later
> Feb 27 20:49:43 kuza kernel:     ide0: BM-DMA at 0xd400-0xd407, BIOS
> settings: hda:DMA, hdb:DMA
> Feb 27 20:49:43 kuza kernel:     ide1: BM-DMA at 0xd408-0xd40f, BIOS
> settings: hdc:DMA, hdd:pio
> Feb 27 20:49:43 kuza kernel: hda: Maxtor 4D040H2, ATA DISK drive
> Feb 27 20:49:43 kuza kernel: hdb: ST3120814A, ATA DISK drive
> Feb 27 20:49:43 kuza kernel: hda: hw_config=603b
> Feb 27 20:49:43 kuza kernel: hda: hw_config=603b
> Feb 27 20:49:43 kuza kernel: hdb: hw_config=6d00
> Feb 27 20:49:43 kuza kernel: hdb: hw_config=6d00
> Feb 27 20:49:43 kuza kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
> Feb 27 20:49:49 kuza kernel: hdc: MATSHITA CR-583, ATAPI CD/DVD-ROM drive
> Feb 27 20:49:49 kuza rpc.statd[1535]: Version 1.0.8 Starting
> Feb 27 20:49:49 kuza kernel: hdd: no response (status = 0xa1), resetting
> drive
> Feb 27 20:49:49 kuza kernel: hdd: no response (status = 0xa1)
> Feb 27 20:49:49 kuza kernel: ide1 at 0x170-0x177,0x376 on irq 15
> Feb 27 20:49:49 kuza kernel: hda: max request size: 128KiB
> Feb 27 20:49:49 kuza kernel: hda: 80043264 sectors (40982 MB) w/2048KiB
> Cache, CHS=65535/16/63<6>hda: hw_config=603b
> Feb 27 20:49:49 kuza kernel: , UDMA(100)
> Feb 27 20:49:49 kuza kernel: hda: cache flushes not supported
> Feb 27 20:49:49 kuza kernel:  hda: hda1 hda2 hda3 hda4<  hda5>
> Feb 27 20:49:49 kuza kernel: hdb: max request size: 128KiB
> Feb 27 20:49:49 kuza kernel: hdb: 234441648 sectors (120034 MB)
> w/8192KiB Cache, CHS=16383/255/63<6>hdb: hw_config=6d00
> Feb 27 20:49:49 kuza kernel: , UDMA(100)
> Feb 27 20:49:49 kuza kernel: hdb: cache flushes supported
> Feb 27 20:49:49 kuza kernel:  hdb: hdb1
> Feb 27 20:49:49 kuza kernel: ide-floppy driver 0.99.newide
> Feb 27 20:49:49 kuza kernel: usbcore: registered new interface driver
> libusual
> Feb 27 20:49:49 kuza kernel: usbcore: registered new interface driver hiddev
> Feb 27 20:49:49 kuza kernel: usbcore: registered new interface driver usbhid
> Feb 27 20:49:49 kuza kernel: drivers/usb/input/hid-core.c: v2.6:USB HID
> core driver
> Feb 27 20:49:49 kuza kernel: PNP: PS/2 Controller
> [PNP0303:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,12
> Feb 27 20:49:49 kuza kernel: serio: i8042 KBD port at 0x60,0x64 irq 1
> Feb 27 20:49:49 kuza kernel: serio: i8042 AUX port at 0x60,0x64 irq 12
> Feb 27 20:49:49 kuza kernel: mice: PS/2 mouse device common for all mice
> Feb 27 20:49:49 kuza kernel: input: AT Translated Set 2 keyboard as
> /class/input/input1
> Feb 27 20:49:49 kuza kernel: TCP bic registered
> Feb 27 20:49:49 kuza kernel: Initializing XFRM netlink socket
> Feb 27 20:49:49 kuza kernel: NET: Registered protocol family 1
> Feb 27 20:49:49 kuza kernel: NET: Registered protocol family 17
> Feb 27 20:49:49 kuza kernel: powernow-k8: Processor cpuid 631 not supported
> Feb 27 20:49:49 kuza kernel: Using IPI Shortcut mode
> Feb 27 20:49:49 kuza kernel: Time: tsc clocksource has been installed.
> Feb 27 20:49:49 kuza kernel: ACPI: (supports S0 S1 S4 S5)
> Feb 27 20:49:49 kuza kernel: Freeing unused kernel memory: 232k freed
> Feb 27 20:49:49 kuza kernel: Write protecting the kernel read-only data:
> 585k
> Feb 27 20:49:49 kuza kernel: input: ImPS/2 Generic Wheel Mouse as
> /class/input/input2
> Feb 27 20:49:49 kuza kernel: EXT3-fs: INFO: recovery required on
> readonly filesystem.
> Feb 27 20:49:49 kuza kernel: EXT3-fs: write access will be enabled
> during recovery.
> Feb 27 20:49:49 kuza kernel: kjournald starting.  Commit interval 5 seconds
> Feb 27 20:49:49 kuza kernel: EXT3-fs: recovery complete.
> Feb 27 20:49:49 kuza kernel: EXT3-fs: mounted filesystem with ordered
> data mode.
> Feb 27 20:49:49 kuza kernel: SELinux:  Disabled at runtime.
> Feb 27 20:49:49 kuza kernel: SELinux:  Unregistering netfilter hooks
> Feb 27 20:49:49 kuza kernel: audit(1330375739.875:2): selinux=0
> auid=4294967295
> Feb 27 20:49:49 kuza kernel: alim7101_wdt: Steve Hill<steve at navaho.co.uk>.
> Feb 27 20:49:49 kuza kernel: alim7101_wdt: Detected old alim7101
> revision 'a1d'.  If this is a cobalt board, set the 'use_gpio' module
> parameter.
> Feb 27 20:49:49 kuza kernel: input: PC Speaker as /class/input/input3
> Feb 27 20:49:49 kuza kernel: hdc: ATAPI 8X CD-ROM drive, 128kB Cache, DMA
> Feb 27 20:49:49 kuza kernel: Uniform CD-ROM driver Revision: 3.20
> Feb 27 20:49:49 kuza kernel: 8139too Fast Ethernet driver 0.9.28
> Feb 27 20:49:49 kuza kernel: ACPI: PCI Interrupt Link [LNKC] enabled at
> IRQ 10
> Feb 27 20:49:49 kuza kernel: ACPI: PCI Interrupt 0000:00:0a.0[A] ->  Link
> [LNKC] ->  GSI 10 (level, low) ->  IRQ 10
> Feb 27 20:49:49 kuza kernel: eth0: RealTek RTL8139 at 0xd081e000,
> 00:50:ba:5f:e4:c3, IRQ 10
> Feb 27 20:49:49 kuza kernel: Floppy drive(s): fd0 is 1.44M
> Feb 27 20:49:49 kuza kernel: FDC 0 is a post-1991 82077
> Feb 27 20:49:49 kuza kernel: ACPI: PCI Interrupt Link [LNKI] enabled at
> IRQ 9
> Feb 27 20:49:49 kuza kernel: ACPI: PCI Interrupt 0000:00:02.0[A] ->  Link
> [LNKI] ->  GSI 9 (level, low) ->  IRQ 9
> Feb 27 20:49:49 kuza kernel: ohci_hcd 0000:00:02.0: OHCI Host Controller
> Feb 27 20:49:49 kuza kernel: ohci_hcd 0000:00:02.0: new USB bus
> registered, assigned bus number 1
> Feb 27 20:49:49 kuza kernel: ohci_hcd 0000:00:02.0: irq 9, io mem 0xeb800000
> Feb 27 20:49:49 kuza kernel: usb usb1: configuration #1 chosen from 1 choice
> Feb 27 20:49:49 kuza kernel: hub 1-0:1.0: USB hub found
> Feb 27 20:49:49 kuza kernel: hub 1-0:1.0: 4 ports detected
> Feb 27 20:49:49 kuza kernel: ACPI: PCI Interrupt Link [LNKE] enabled at
> IRQ 5
> Feb 27 20:49:49 kuza kernel: ACPI: PCI Interrupt 0000:00:06.0[A] ->  Link
> [LNKE] ->  GSI 5 (level, low) ->  IRQ 5
> Feb 27 20:49:49 kuza kernel: ohci_hcd 0000:00:06.0: OHCI Host Controller
> Feb 27 20:49:49 kuza kernel: ohci_hcd 0000:00:06.0: new USB bus
> registered, assigned bus number 2
> Feb 27 20:49:49 kuza kernel: ohci_hcd 0000:00:06.0: irq 5, io mem 0xea800000
> Feb 27 20:49:49 kuza kernel: usb usb2: configuration #1 chosen from 1 choice
> Feb 27 20:49:49 kuza kernel: hub 2-0:1.0: USB hub found
> Feb 27 20:49:49 kuza kernel: hub 2-0:1.0: 2 ports detected
> Feb 27 20:49:49 kuza kernel: usb 1-1: new low speed USB device using
> ohci_hcd and address 2
> Feb 27 20:49:49 kuza kernel: usb 1-1: configuration #1 chosen from 1 choice
> Feb 27 20:49:49 kuza kernel: parport: PnPBIOS parport detected.
> Feb 27 20:49:49 kuza kernel: parport0: PC-style at 0x378 (0x778), irq 7
> [PCSPP,TRISTATE]
> Feb 27 20:49:49 kuza kernel: lp0: using parport0 (interrupt-driven).
> Feb 27 20:49:49 kuza kernel: lp0: console ready
> Feb 27 20:49:49 kuza kernel: hiddev96: USB HID v1.10 Device [American
> Power Conversion Back-UPS XS 1300 LCD FW:836.H5 .D USB FW:H5 ] on
> usb-0000:00:02.0-1
> Feb 27 20:49:49 kuza kernel: NET: Registered protocol family 10
> Feb 27 20:49:49 kuza kernel: lo: Disabled Privacy Extensions
> Feb 27 20:49:49 kuza kernel: Mobile IPv6
> Feb 27 20:49:49 kuza kernel: input: Power Button (FF) as /class/input/input4
> Feb 27 20:49:49 kuza kernel: ACPI: Power Button (FF) [PWRF]
> Feb 27 20:49:49 kuza kernel: input: Power Button (CM) as /class/input/input5
> Feb 27 20:49:49 kuza kernel: ACPI: Power Button (CM) [PWRB]
> Feb 27 20:49:49 kuza kernel: No dock devices found.
> Feb 27 20:49:49 kuza kernel: ibm_acpi: ec object not found
> Feb 27 20:49:49 kuza kernel: md: Autodetecting RAID arrays.
> Feb 27 20:49:49 kuza kernel: md: autorun ...
> Feb 27 20:49:49 kuza kernel: md: ... autorun DONE.
> Feb 27 20:49:49 kuza kernel: device-mapper: ioctl: 4.11.0-ioctl
> (2006-10-12) initialised: dm-devel at redhat.com
> Feb 27 20:49:49 kuza kernel: EXT3 FS on hda5, internal journal
> Feb 27 20:49:49 kuza kernel: kjournald starting.  Commit interval 5 seconds
> Feb 27 20:49:49 kuza kernel: EXT3 FS on hda1, internal journal
> Feb 27 20:49:49 kuza kernel: EXT3-fs: mounted filesystem with ordered
> data mode.
> Feb 27 20:49:49 kuza kernel: kjournald starting.  Commit interval 5 seconds
> Feb 27 20:49:49 kuza kernel: EXT3 FS on hdb1, internal journal
> Feb 27 20:49:50 kuza kernel: EXT3-fs: mounted filesystem with ordered
> data mode.
> Feb 27 20:49:50 kuza kernel: kjournald starting.  Commit interval 5 seconds
> Feb 27 20:49:50 kuza kernel: EXT3 FS on hda2, internal journal
> Feb 27 20:49:50 kuza kernel: EXT3-fs: mounted filesystem with ordered
> data mode.
> Feb 27 20:49:50 kuza kernel: Adding 514072k swap on /dev/hda3.
> Priority:-1 extents:1 across:514072k
> Feb 27 20:49:50 kuza kernel: eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
> Feb 27 20:49:53 kuza kernel: Bluetooth: Core ver 2.11
> Feb 27 20:49:53 kuza kernel: NET: Registered protocol family 31
> Feb 27 20:49:53 kuza kernel: Bluetooth: HCI device and connection
> manager initialized
> Feb 27 20:49:53 kuza kernel: Bluetooth: HCI socket layer initialized
> Feb 27 20:49:53 kuza kernel: Bluetooth: L2CAP ver 2.8
> Feb 27 20:49:53 kuza kernel: Bluetooth: L2CAP socket layer initialized
> Feb 27 20:49:53 kuza kernel: Bluetooth: HIDP (Human Interface Emulation)
> ver 1.1
> Feb 27 20:49:53 kuza hidd[1621]: Bluetooth HID daemon
> Feb 27 20:49:56 kuza smartd[1719]: smartd version 5.36
> [i686-redhat-linux-gnu] Copyright (C) 2002-6 Bruce Allen
> Feb 27 20:49:56 kuza smartd[1719]: Home page is
> http://smartmontools.sourceforge.net/
> Feb 27 20:49:56 kuza smartd[1719]: Opened configuration file
> /etc/smartd.conf
> Feb 27 20:49:56 kuza smartd[1719]: Configuration file /etc/smartd.conf
> parsed.
> Feb 27 20:49:56 kuza smartd[1719]: Device: /dev/hda, opened
> Feb 27 20:49:56 kuza smartd[1719]: Device: /dev/hda, found in smartd
> database.
> Feb 27 20:49:57 kuza smartd[1719]: Device: /dev/hda, is SMART capable.
> Adding to "monitor" list.
> Feb 27 20:49:57 kuza smartd[1719]: Device: /dev/hdb, opened
> Feb 27 20:49:57 kuza smartd[1719]: Device: /dev/hdb, not found in smartd
> database.
> Feb 27 20:49:58 kuza smartd[1719]: Device: /dev/hdb, is SMART capable.
> Adding to "monitor" list.
> Feb 27 20:49:58 kuza smartd[1719]: Monitoring 2 ATA and 0 SCSI devices
> Feb 27 20:49:59 kuza smartd[1724]: smartd has fork()ed into background
> mode. New PID=1724.
> Feb 27 20:49:59 kuza hpiod: 1.6.6a accepting connections at 50000...
> Feb 27 20:50:06 kuza xinetd[1770]: xinetd Version 2.3.13 started with
> libwrap loadavg options compiled in.
> Feb 27 20:50:06 kuza xinetd[1770]: Started working: 1 available service
> Feb 27 20:50:06 kuza exportfs[1803]: No host name given with /data
> (sync,rw), suggest *(sync,rw) to avoid warning
> Feb 27 20:50:06 kuza apcupsd[1789]: apcupsd 3.12.4 (19 August 2006)
> redhat startup succeeded
> Feb 27 20:50:06 kuza apcupsd[1789]: NIS server startup succeeded
> Feb 27 20:50:07 kuza kernel: Installing knfsd (copyright (C) 1996
> okir at monad.swb.de).
> Feb 27 20:50:07 kuza kernel: NFSD: Using /var/lib/nfs/v4recovery as the
> NFSv4 state recovery directory
> Feb 27 20:50:07 kuza kernel: NFSD: starting 90-second grace period
> Feb 27 20:50:08 kuza gpm[1855]: *** info [startup.c(95)]:
> Feb 27 20:50:08 kuza gpm[1855]: Started gpm successfully. Entered daemon
> mode.
> Feb 27 20:50:20 kuza avahi-daemon[2009]: Found user 'avahi' (UID 70) and
> group 'avahi' (GID 70).
> Feb 27 20:50:20 kuza avahi-daemon[2009]: Successfully dropped root
> privileges.
> Feb 27 20:50:20 kuza avahi-daemon[2009]: avahi-daemon 0.6.11 starting up.
> Feb 27 20:50:20 kuza avahi-daemon[2009]: WARNING: No NSS support for
> mDNS detected, consider installing nss-mdns!
> Feb 27 20:50:21 kuza avahi-daemon[2009]: Successfully called chroot().
> Feb 27 20:50:21 kuza avahi-daemon[2009]: Successfully dropped remaining
> capabilities.
> Feb 27 20:50:21 kuza avahi-daemon[2009]: No service found in
> /etc/avahi/services.
> Feb 27 20:50:21 kuza avahi-daemon[2009]: New relevant interface
> eth0.IPv6 for mDNS.
> Feb 27 20:50:21 kuza avahi-daemon[2009]: Joining mDNS multicast group on
> interface eth0.IPv6 with address fe80::250:baff:fe5f:e4c3.
> Feb 27 20:50:21 kuza avahi-daemon[2009]: New relevant interface
> eth0.IPv4 for mDNS.
> Feb 27 20:50:21 kuza avahi-daemon[2009]: Joining mDNS multicast group on
> interface eth0.IPv4 with address 192.168.1.3.
> Feb 27 20:50:21 kuza avahi-daemon[2009]: Network interface enumeration
> completed.
> Feb 27 20:50:21 kuza avahi-daemon[2009]: Registering new address record
> for fe80::250:baff:fe5f:e4c3 on eth0.
> Feb 27 20:50:21 kuza avahi-daemon[2009]: Registering new address record
> for 192.168.1.3 on eth0.
> Feb 27 20:50:21 kuza avahi-daemon[2009]: Registering HINFO record with
> values 'I686'/'LINUX'.
> Feb 27 20:50:21 kuza avahi-daemon[2009]: Server startup complete. Host
> name is kuza.local. Local service cookie is 2874978490.
> Feb 27 20:56:06 kuza nmbd[1930]: [2012/02/27 20:56:06, 0]
> nmbd/nmbd_become_lmb.c:become_local_master_stage2(396)
> Feb 27 20:56:06 kuza nmbd[1930]:   *****
> Feb 27 20:56:06 kuza nmbd[1930]:
> Feb 27 20:56:06 kuza nmbd[1930]:   Samba name server KUZA is now a local
> master browser for workgroup WORKGROUP on subnet 192.168.1.3
> Feb 27 20:56:06 kuza nmbd[1930]:
> Feb 27 20:56:06 kuza nmbd[1930]:   *****
> _______________________________________________
> mdlug mailing list
> mdlug at mdlug.org
> http://mdlug.org/mailman/listinfo/mdlug


From GregWojtak at quickenloans.com  Tue Feb 28 16:08:20 2012
From: GregWojtak at quickenloans.com (Wojtak, Greg (Superfly))
Date: Tue, 28 Feb 2012 21:08:20 +0000
Subject: [mdlug] hanging machine kernel panic - on going
In-Reply-To: <4F4CF6FB.4070607@gmail.com>
Message-ID: <CB72AC79.1F1D0%gregwojtak@quickenloans.com>

If you're feeling really ambitious you could make sure that the kdump
system is configured, grab the kernel dump, and run gdb on it...

On 2012-02-28 10:47 AM, "Aaron Kulkis" <akulkis00 at gmail.com> wrote:

>Gmail-otakurider wrote:
>> Here is the messages dump - check around 16:53 anyone have any ideas?
>> checked memory tested ok - checked HDD tested ok
>>
>
>
>I've been getting some panics lately, too.  My suspicion
>is that a kernel bug was recently introduced.  I also trust
>that with time, it will be found and go away.
>
>Fortunately, I still have some habits from my college days
>when Purdue's Electrical Engineering department was the
>primary test site for Gould Electronics' high performance
>Unix division, and endured periods in which typical
>uptime was <90 minutes, until the problems were found
>and resolved.
>
>> Yes I know its long but wanted to give all info
>>
>>   thinking of setting panic=  setting to have it just reboot
>>
>> Thank in advance
>>
>>
>>
>> Feb 27 10:37:30 kuza avahi-daemon[2006]: Network interface enumeration
>> completed.
>> Feb 27 10:37:30 kuza avahi-daemon[2006]: Registering new address record
>> for fe80::250:baff:fe5f:e4c3 on eth0.
>> Feb 27 10:37:30 kuza avahi-daemon[2006]: Registering new address record
>> for 192.168.1.3 on eth0.
>> Feb 27 10:37:30 kuza avahi-daemon[2006]: Registering HINFO record with
>> values 'I686'/'LINUX'.
>> Feb 27 10:37:31 kuza avahi-daemon[2006]: Server startup complete. Host
>> name is kuza.local. Local service cookie is 1101511634.
>> Feb 27 10:43:10 kuza nmbd[1926]: [2012/02/27 10:43:10, 0]
>> nmbd/nmbd_become_lmb.c:become_local_master_stage2(396)
>> Feb 27 10:43:10 kuza nmbd[1926]:   *****
>> Feb 27 10:43:10 kuza nmbd[1926]:
>> Feb 27 10:43:10 kuza nmbd[1926]:   Samba name server KUZA is now a local
>> master browser for workgroup WORKGROUP on subnet 192.168.1.3
>> Feb 27 10:43:10 kuza nmbd[1926]:
>> Feb 27 10:43:10 kuza nmbd[1926]:   *****
>> Feb 27 11:18:52 kuza avahi-daemon[2006]: Invalid query packet.
>> Feb 27 11:19:32 kuza last message repeated 26 times
>> Feb 27 11:19:32 kuza avahi-daemon[2006]: Invalid query packet.
>> Feb 27 16:53:41 kuza kernel: BUG: unable to handle kernel NULL pointer
>> dereference at virtual address 00000000
>> Feb 27 16:53:41 kuza kernel:  printing eip:
>> Feb 27 16:53:41 kuza kernel: cab88e5c
>> Feb 27 16:53:41 kuza kernel: *pde = 09606067
>> Feb 27 16:53:41 kuza kernel: Oops: 0002 [#1]
>> Feb 27 16:53:41 kuza kernel: last sysfs file: /block/hda/hda1/size
>> Feb 27 16:53:41 kuza kernel: Modules linked in: nfsd exportfs lockd
>> nfs_acl autofs4 hidp l2cap bluetooth sunrpc dm_mirror dm_mod video sbs
>> i2c_ec dock container button battery asus_acpi backlight ac ipv6 lp
>> parport_pc parport floppy ohci_hcd 8139too i2c_ali15x3 serio_raw mii
>> i2c_ali1535 i2c_core pcspkr ide_cd cdrom ext3 jbd
>> Feb 27 16:53:41 kuza kernel: CPU:    0
>> Feb 27 16:53:41 kuza kernel: EIP:    0060:[<cab88e5c>]    Not tainted
>>VLI
>> Feb 27 16:53:41 kuza kernel: EFLAGS: 00210206   (2.6.20-1.2320.fc5 #1)
>> Feb 27 16:53:41 kuza kernel: EIP is at 0xcab88e5c
>> Feb 27 16:53:41 kuza kernel: eax: 00000000   ebx: cab88f9c   ecx:
>> ca3c3610   edx: c137c980
>> Feb 27 16:53:41 kuza kernel: esi: cab88f48   edi: 00000006   ebp:
>> cab88e58   esp: cab88ba4
>> Feb 27 16:53:41 kuza kernel: ds: 007b   es: 007b   ss: 0068
>> Feb 27 16:53:41 kuza kernel: Process python (pid: 1745, ti=cab88000
>> task=cfec30d0 task.ti=cab88000)
>> Feb 27 16:53:41 kuza kernel: Stack: cab88e60 cab88e4c cab88e50 cab88e54
>> 00000030 00000000 00000000 00000030
>> Feb 27 16:53:41 kuza kernel:        00000000 00000000 00000000 00000000
>> 00000000 00000000 c046ad08 00000000
>> Feb 27 16:53:41 kuza kernel:        00000000 00000002 ccd0f320 00000000
>> cfec30d0 c0419bdc 00100100 00200200
>> Feb 27 16:53:41 kuza kernel: Call Trace:
>> Feb 27 16:53:41 kuza kernel:  [<c046ad08>] __pollwait+0x0/0xab
>> Feb 27 16:53:41 kuza kernel:  [<c0419bdc>] default_wake_function+0x0/0xc
>> Feb 27 16:53:41 kuza kernel:  [<c0419bdc>] default_wake_function+0x0/0xc
>> Feb 27 16:53:41 kuza kernel:  [<d082fb73>]
>> do_get_write_access+0x48b/0x4b8 [jbd]
>> Feb 27 16:53:41 kuza kernel:  [<d08885f8>]
>> __ext3_get_inode_loc+0x10a/0x2fd [ext3]
>> Feb 27 16:53:41 kuza kernel:  [<c0608164>] _read_unlock_irq+0x5/0x7
>> Feb 27 16:53:41 kuza kernel:  [<d0893712>]
>> __ext3_journal_dirty_metadata+0x16/0x3a [ext3]
>> Feb 27 16:53:41 kuza kernel:  [<d082fbc1>]
>> journal_get_write_access+0x21/0x26 [jbd]
>> Feb 27 16:53:41 kuza kernel:  [<d0888489>]
>> ext3_mark_iloc_dirty+0x275/0x2da [ext3]
>> Feb 27 16:53:41 kuza kernel:  [<c0418de8>] __wake_up+0x32/0x43
>> Feb 27 16:53:41 kuza kernel:  [<d082f6dc>] journal_stop+0x1cb/0x1d7
>>[jbd]
>> Feb 27 16:53:41 kuza kernel:  [<d088f703>] __ext3_journal_stop+0x19/0x34
>> [ext3]
>> Feb 27 16:53:41 kuza kernel:  [<d088a6b2>]
>> ext3_ordered_commit_write+0xba/0xd8 [ext3]
>> Feb 27 16:53:41 kuza kernel:  [<c044aaa7>] __pagevec_lru_add+0x7a/0x85
>> Feb 27 16:53:41 kuza kernel:  [<c0446328>]
>> generic_file_buffered_write+0x579/0x5e8
>> Feb 27 16:53:41 kuza kernel:  [<c047aa2a>] __getblk+0x3b/0x287
>> Feb 27 16:53:41 kuza kernel:  [<c0420638>] current_fs_time+0x45/0x51
>> Feb 27 16:53:41 kuza kernel:  [<c0405e65>] do_IRQ+0xbf/0xd6
>> Feb 27 16:53:41 kuza kernel:  [<c0404763>] common_interrupt+0x23/0x28
>> Feb 27 16:53:41 kuza kernel:  [<c046aa67>] core_sys_select+0x2d2/0x2f3
>> Feb 27 16:53:41 kuza kernel:  [<c0448dff>] __alloc_pages+0x68/0x29c
>> Feb 27 16:53:41 kuza kernel:  [<c0608164>] _read_unlock_irq+0x5/0x7
>> Feb 27 16:53:41 kuza kernel:  [<c0444c30>] find_get_page+0x35/0x3a
>> Feb 27 16:53:41 kuza kernel:  [<c044710b>] filemap_nopage+0x159/0x2d4
>> Feb 27 16:53:41 kuza kernel:  [<c044f9c9>] __handle_mm_fault+0x858/0x87a
>> Feb 27 16:53:41 kuza kernel:  [<c0452bf4>] do_mmap_pgoff+0x587/0x6e8
>> Feb 27 16:53:41 kuza kernel:  [<c046b04e>] sys_select+0xa0/0x186
>> Feb 27 16:53:41 kuza kernel:  [<c0403dc8>] syscall_call+0x7/0xb
>> Feb 27 16:53:41 kuza kernel:  =======================
>> Feb 27 16:53:41 kuza kernel: Code: aa 46 c0 48 4b c3 bf ea ff ff ff 00
>> e0 9a 08 00 e0 9a 08 06 00 00 00 30 00 00 00 00 00 00 00 00 00 00 00 00
>> 00 00 00 00 00 00 00<00>  00 00 00 44 00 00 00 46 02 20 00 01 00 00 00
>> 00 00 00 00 d2
>> Feb 27 16:53:41 kuza kernel: EIP: [<cab88e5c>] 0xcab88e5c SS:ESP
>> 0068:cab88ba4
>> Feb 27 20:04:54 kuza avahi-daemon[2006]: Invalid query packet.
>> Feb 27 20:05:38 kuza last message repeated 30 times
>> Feb 27 20:49:41 kuza syslogd 1.4.1: restart.
>> Feb 27 20:49:41 kuza kernel: klogd 1.4.1, log source = /proc/kmsg
>>started.
>> Feb 27 20:49:41 kuza kernel: Linux version 2.6.20-1.2320.fc5
>> (brewbuilder at hs20-bc2-2.build.redhat.com) (gcc version 4.1.1 20070105
>> (Red Hat 4.1.1-51)) #1 Tue Jun 12 18:50:38 EDT 2007
>> Feb 27 20:49:41 kuza kernel: BIOS-provided physical RAM map:
>> Feb 27 20:49:41 kuza kernel: sanitize start
>> Feb 27 20:49:41 kuza kernel: sanitize end
>> Feb 27 20:49:41 kuza kernel: copy_e820_map() start: 0000000000000000
>> size: 000000000009fc00 end: 000000000009fc00 type: 1
>> Feb 27 20:49:41 kuza kernel: copy_e820_map() type is E820_RAM
>> Feb 27 20:49:41 kuza kernel: copy_e820_map() start: 000000000009fc00
>> size: 0000000000000400 end: 00000000000a0000 type: 2
>> Feb 27 20:49:41 kuza kernel: copy_e820_map() start: 00000000000f0000
>> size: 0000000000010000 end: 0000000000100000 type: 2
>> Feb 27 20:49:41 kuza kernel: copy_e820_map() start: 0000000000100000
>> size: 000000000feec000 end: 000000000ffec000 type: 1
>> Feb 27 20:49:41 kuza kernel: copy_e820_map() type is E820_RAM
>> Feb 27 20:49:41 kuza kernel: copy_e820_map() start: 000000000ffec000
>> size: 0000000000003000 end: 000000000ffef000 type: 3
>> Feb 27 20:49:41 kuza kernel: copy_e820_map() start: 000000000ffef000
>> size: 0000000000010000 end: 000000000ffff000 type: 2
>> Feb 27 20:49:41 kuza kernel: copy_e820_map() start: 000000000ffff000
>> size: 0000000000001000 end: 0000000010000000 type: 4
>> Feb 27 20:49:41 kuza kernel: copy_e820_map() start: 00000000ffff0000
>> size: 0000000000010000 end: 0000000100000000 type: 2
>> Feb 27 20:49:41 kuza kernel:  BIOS-e820: 0000000000000000 -
>> 000000000009fc00 (usable)
>> Feb 27 20:49:41 kuza kernel:  BIOS-e820: 000000000009fc00 -
>> 00000000000a0000 (reserved)
>> Feb 27 20:49:41 kuza kernel:  BIOS-e820: 00000000000f0000 -
>> 0000000000100000 (reserved)
>> Feb 27 20:49:41 kuza kernel:  BIOS-e820: 0000000000100000 -
>> 000000000ffec000 (usable)
>> Feb 27 20:49:41 kuza kernel:  BIOS-e820: 000000000ffec000 -
>> 000000000ffef000 (ACPI data)
>> Feb 27 20:49:41 kuza kernel:  BIOS-e820: 000000000ffef000 -
>> 000000000ffff000 (reserved)
>> Feb 27 20:49:41 kuza kernel:  BIOS-e820: 000000000ffff000 -
>> 0000000010000000 (ACPI NVS)
>> Feb 27 20:49:41 kuza kernel:  BIOS-e820: 00000000ffff0000 -
>> 0000000100000000 (reserved)
>> Feb 27 20:49:41 kuza kernel: 0MB HIGHMEM available.
>> Feb 27 20:49:41 kuza kernel: 255MB LOWMEM available.
>> Feb 27 20:49:41 kuza kernel: Using x86 segment limits to approximate NX
>> protection
>> Feb 27 20:49:41 kuza kernel: Zone PFN ranges:
>> Feb 27 20:49:41 kuza kernel:   DMA             0 ->      4096
>> Feb 27 20:49:43 kuza kernel:   Normal       4096 ->     65516
>> Feb 27 20:49:43 kuza kernel:   HighMem     65516 ->     65516
>> Feb 27 20:49:43 kuza kernel: early_node_map[1] active PFN ranges
>> Feb 27 20:49:43 kuza kernel:     0:        0 ->     65516
>> Feb 27 20:49:43 kuza kernel: DMI 2.3 present.
>> Feb 27 20:49:43 kuza kernel: Using APIC driver default
>> Feb 27 20:49:43 kuza kernel: ACPI: PM-Timer IO Port: 0xe408
>> Feb 27 20:49:43 kuza kernel: Allocating PCI resources starting at
>> 20000000 (gap: 10000000:efff0000)
>> Feb 27 20:49:43 kuza kernel: Detected 807.940 MHz processor.
>> Feb 27 20:49:43 kuza kernel: Built 1 zonelists.  Total pages: 65005
>> Feb 27 20:49:43 kuza kernel: Kernel command line: ro root=LABEL=/ rhgb
>>quiet
>> Feb 27 20:49:43 kuza kernel: Local APIC disabled by BIOS -- you can
>> enable it with "lapic"
>> Feb 27 20:49:43 kuza kernel: Enabling fast FPU save and restore... done.
>> Feb 27 20:49:43 kuza kernel: Initializing CPU#0
>> Feb 27 20:49:43 kuza kernel: CPU 0 irqstacks, hard=c0720000
>>soft=c071f000
>> Feb 27 20:49:43 kuza kernel: PID hash table entries: 1024 (order: 10,
>> 4096 bytes)
>> Feb 27 20:49:43 kuza kernel: Console: colour VGA+ 80x25
>> Feb 27 20:49:43 kuza kernel: Dentry cache hash table entries: 32768
>> (order: 5, 131072 bytes)
>> Feb 27 20:49:43 kuza kernel: Inode-cache hash table entries: 16384
>> (order: 4, 65536 bytes)
>> Feb 27 20:49:43 kuza kernel: Memory: 254596k/262064k available (2091k
>> kernel code, 6828k reserved, 845k data, 232k init, 0k highmem)
>> Feb 27 20:49:43 kuza kernel: virtual kernel memory layout:
>> Feb 27 20:49:43 kuza kernel:     fixmap  : 0xfff9b000 - 0xfffff000   (
>> 400 kB)
>> Feb 27 20:49:43 kuza kernel:     pkmap   : 0xff800000 - 0xffc00000
>> (4096 kB)
>> Feb 27 20:49:43 kuza kernel:     vmalloc : 0xd0800000 - 0xff7fe000   (
>> 751 MB)
>> Feb 27 20:49:43 kuza kernel:     lowmem  : 0xc0000000 - 0xcffec000   (
>> 255 MB)
>> Feb 27 20:49:43 kuza kernel:       .init : 0xc06e0000 - 0xc071a000   (
>> 232 kB)
>> Feb 27 20:49:43 kuza kernel:       .data : 0xc060aefd - 0xc06de614   (
>> 845 kB)
>> Feb 27 20:49:43 kuza kernel:       .text : 0xc0400000 - 0xc060aefd
>> (2091 kB)
>> Feb 27 20:49:43 kuza kernel: Checking if this processor honours the WP
>> bit even in supervisor mode... Ok.
>> Feb 27 20:49:43 kuza kernel: Calibrating delay using timer specific
>> routine.. 1616.55 BogoMIPS (lpj=808275)
>> Feb 27 20:49:43 kuza kernel: Security Framework v1.0.0 initialized
>> Feb 27 20:49:43 kuza kernel: SELinux:  Initializing.
>> Feb 27 20:49:43 kuza kernel: SELinux:  Starting in permissive mode
>> Feb 27 20:49:43 kuza kernel: selinux_register_security:  Registering
>> secondary module capability
>> Feb 27 20:49:43 kuza kernel: Capability LSM initialized as secondary
>> Feb 27 20:49:43 kuza kernel: Mount-cache hash table entries: 512
>> Feb 27 20:49:43 kuza kernel: CPU: L1 I Cache: 64K (64 bytes/line), D
>> cache 64K (64 bytes/line)
>> Feb 27 20:49:43 kuza kernel: CPU: L2 Cache: 64K (64 bytes/line)
>> Feb 27 20:49:43 kuza kernel: Intel machine check architecture supported.
>> Feb 27 20:49:43 kuza kernel: Intel machine check reporting enabled on
>>CPU#0.
>> Feb 27 20:49:43 kuza kernel: CPU: AMD Duron(tm) Processor stepping 01
>> Feb 27 20:49:43 kuza kernel: Checking 'hlt' instruction... OK.
>> Feb 27 20:49:43 kuza kernel: ACPI: Core revision 20060707
>> Feb 27 20:49:43 kuza kernel: ACPI: setting ELCR to 0200 (from 0e20)
>> Feb 27 20:49:43 kuza kernel: NET: Registered protocol family 16
>> Feb 27 20:49:43 kuza kernel: ACPI: bus type pci registered
>> Feb 27 20:49:43 kuza kernel: PCI: PCI BIOS revision 2.10 entry at
>> 0xf1170, last bus=1
>> Feb 27 20:49:43 kuza kernel: PCI: Using configuration type 1
>> Feb 27 20:49:43 kuza kernel: Setting up standard PCI resources
>> Feb 27 20:49:43 kuza kernel: ACPI: Interpreter enabled
>> Feb 27 20:49:43 kuza kernel: ACPI: Using PIC for interrupt routing
>> Feb 27 20:49:43 kuza kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5
>> 6 7 9 10 *11 12 14 15)
>> Feb 27 20:49:43 kuza kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5
>> 6 7 9 10 11 12 14 15) *0, disabled.
>> Feb 27 20:49:43 kuza kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5
>> 6 7 9 *10 11 12 14 15)
>> Feb 27 20:49:43 kuza kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5
>> 6 7 9 10 11 12 14 15) *0, disabled.
>> Feb 27 20:49:43 kuza kernel: ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4
>> *5 6 7 9 10 11 12 14 15)
>> Feb 27 20:49:43 kuza kernel: ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5
>> 6 7 9 10 11 12 14 15) *0, disabled.
>> Feb 27 20:49:43 kuza kernel: ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5
>> 6 7 9 10 11 12 14 15) *0, disabled.
>> Feb 27 20:49:43 kuza kernel: ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5
>> 6 7 9 10 11 12 14 15) *0, disabled.
>> Feb 27 20:49:43 kuza kernel: ACPI: PCI Interrupt Link [LNKI] (IRQs 3 4 5
>> 6 7 *9 10 11 12 14 15)
>> Feb 27 20:49:43 kuza kernel: ACPI: PCI Root Bridge [PCI0] (0000:00)
>> Feb 27 20:49:43 kuza kernel: ACPI: Assume root bridge [\_SB_.PCI0] bus
>>is 0
>> Feb 27 20:49:43 kuza kernel: PCI quirk: region e400-e43f claimed by
>> ali7101 ACPI
>> Feb 27 20:49:43 kuza kernel: PCI quirk: region e800-e81f claimed by
>> ali7101 SMB
>> Feb 27 20:49:43 kuza kernel: Linux Plug and Play Support v0.97 (c) Adam
>> Belay
>> Feb 27 20:49:43 kuza kernel: pnp: PnP ACPI init
>> Feb 27 20:49:43 kuza kernel: pnp: PnP ACPI: found 15 devices
>> Feb 27 20:49:43 kuza kernel: usbcore: registered new interface driver
>>usbfs
>> Feb 27 20:49:43 kuza kernel: usbcore: registered new interface driver
>>hub
>> Feb 27 20:49:43 kuza kernel: usbcore: registered new device driver usb
>> Feb 27 20:49:43 kuza kernel: PCI: Using ACPI for IRQ routing
>> Feb 27 20:49:43 kuza kernel: PCI: If a device doesn't work, try
>> "pci=routeirq".  If it helps, post a report
>> Feb 27 20:49:43 kuza kernel: NetLabel: Initializing
>> Feb 27 20:49:43 kuza kernel: NetLabel:  domain hash size = 128
>> Feb 27 20:49:43 kuza kernel: NetLabel:  protocols = UNLABELED CIPSOv4
>> Feb 27 20:49:43 kuza kernel: NetLabel:  unlabeled traffic allowed by
>>default
>> Feb 27 20:49:43 kuza kernel: pnp: 00:02: ioport range 0xe400-0xe47f
>> could not be reserved
>> Feb 27 20:49:43 kuza kernel: pnp: 00:02: ioport range 0xe800-0xe81f has
>> been reserved
>> Feb 27 20:49:43 kuza kernel: pnp: 00:02: ioport range 0x40b-0x40b has
>> been reserved
>> Feb 27 20:49:43 kuza kernel: pnp: 00:02: ioport range 0x480-0x48f has
>> been reserved
>> Feb 27 20:49:43 kuza kernel: pnp: 00:02: ioport range 0x4d6-0x4d6 has
>> been reserved
>> Feb 27 20:49:43 kuza kernel: PCI: Bridge: 0000:00:01.0
>> Feb 27 20:49:43 kuza kernel:   IO window: disabled.
>> Feb 27 20:49:43 kuza kernel:   MEM window: ec000000-edefffff
>> Feb 27 20:49:43 kuza kernel:   PREFETCH window: edf00000-efffffff
>> Feb 27 20:49:43 kuza kernel: NET: Registered protocol family 2
>> Feb 27 20:49:43 kuza kernel: IP route cache hash table entries: 2048
>> (order: 1, 8192 bytes)
>> Feb 27 20:49:43 kuza kernel: TCP established hash table entries: 8192
>> (order: 5, 131072 bytes)
>> Feb 27 20:49:43 kuza kernel: TCP bind hash table entries: 4096 (order:
>> 4, 81920 bytes)
>> Feb 27 20:49:43 kuza kernel: TCP: Hash tables configured (established
>> 8192 bind 4096)
>> Feb 27 20:49:43 kuza kernel: TCP reno registered
>> Feb 27 20:49:43 kuza kernel: checking if image is initramfs... it is
>> Feb 27 20:49:43 kuza kernel: Freeing initrd memory: 913k freed
>> Feb 27 20:49:43 kuza kernel: Simple Boot Flag at 0x3a set to 0x1
>> Feb 27 20:49:43 kuza kernel: apm: BIOS version 1.2 Flags 0x0b (Driver
>> version 1.16ac)
>> Feb 27 20:49:43 kuza kernel: apm: overridden by ACPI.
>> Feb 27 20:49:43 kuza kernel: audit: initializing netlink socket
>>(disabled)
>> Feb 27 20:49:43 kuza kernel: audit(1330375714.653:1): initialized
>> Feb 27 20:49:43 kuza kernel: Total HugeTLB memory allocated, 0
>> Feb 27 20:49:43 kuza kernel: VFS: Disk quotas dquot_6.5.1
>> Feb 27 20:49:43 kuza kernel: Dquot-cache hash table entries: 1024 (order
>> 0, 4096 bytes)
>> Feb 27 20:49:43 kuza kernel: SELinux:  Registering netfilter hooks
>> Feb 27 20:49:43 kuza kernel: ksign: Installing public key data
>> Feb 27 20:49:43 kuza kernel: Loading keyring
>> Feb 27 20:49:43 kuza kernel: - Added public key FA1AD44A9013A628
>> Feb 27 20:49:43 kuza kernel: - User ID: Red Hat, Inc. (Kernel Module GPG
>> key)
>> Feb 27 20:49:43 kuza kernel: io scheduler noop registered
>> Feb 27 20:49:43 kuza kernel: io scheduler anticipatory registered
>> Feb 27 20:49:43 kuza kernel: io scheduler deadline registered
>> Feb 27 20:49:43 kuza kernel: io scheduler cfq registered (default)
>> Feb 27 20:49:43 kuza kernel: Limiting direct PCI/PCI transfers.
>> Feb 27 20:49:43 kuza kernel: Activating ISA DMA hang workarounds.
>> Feb 27 20:49:43 kuza kernel: pci_hotplug: PCI Hot Plug PCI Core
>>version: 0.5
>> Feb 27 20:49:43 kuza kernel: ACPI: Invalid PBLK length [5]
>> Feb 27 20:49:43 kuza kernel: isapnp: Scanning for PnP cards...
>> Feb 27 20:49:43 kuza kernel: isapnp: No Plug&  Play device found
>> Feb 27 20:49:43 kuza kernel: Real Time Clock Driver v1.12ac
>> Feb 27 20:49:43 kuza kernel: Non-volatile memory driver v1.2
>> Feb 27 20:49:43 kuza kernel: Linux agpgart interface v0.101 (c) Dave
>>Jones
>> Feb 27 20:49:43 kuza kernel: agpgart: Detected ALi M1647 chipset
>> Feb 27 20:49:43 kuza kernel: agpgart: AGP aperture is 128M @ 0xf0000000
>> Feb 27 20:49:43 kuza kernel: Serial: 8250/16550 driver $Revision: 1.90 $
>> 4 ports, IRQ sharing enabled
>> Feb 27 20:49:43 kuza kernel: serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is
>> a 16550A
>> Feb 27 20:49:43 kuza kernel: serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is
>> a 16550A
>> Feb 27 20:49:43 kuza kernel: 00:0b: ttyS0 at I/O 0x3f8 (irq = 4) is a
>>16550A
>> Feb 27 20:49:43 kuza kernel: 00:0c: ttyS1 at I/O 0x2f8 (irq = 3) is a
>>16550A
>> Feb 27 20:49:43 kuza kernel: RAMDISK driver initialized: 16 RAM disks of
>> 16384K size 4096 blocksize
>> Feb 27 20:49:43 kuza kernel: input: Macintosh mouse button emulation as
>> /class/input/input0
>> Feb 27 20:49:43 kuza kernel: Uniform Multi-Platform E-IDE driver
>> Revision: 7.00alpha2
>> Feb 27 20:49:43 kuza kernel: ide: Assuming 33MHz system bus speed for
>> PIO modes; override with idebus=xx
>> Feb 27 20:49:43 kuza kernel: ALI15X3: IDE controller at PCI slot
>> 0000:00:04.0
>> Feb 27 20:49:43 kuza kernel: ACPI: Unable to derive IRQ for device
>> 0000:00:04.0
>> Feb 27 20:49:43 kuza kernel: ACPI: PCI Interrupt 0000:00:04.0[A]: no GSI
>> Feb 27 20:49:43 kuza kernel: ALI15X3: chipset revision 196
>> Feb 27 20:49:43 kuza kernel: ALI15X3: not 100% native mode: will probe
>> irqs later
>> Feb 27 20:49:43 kuza kernel:     ide0: BM-DMA at 0xd400-0xd407, BIOS
>> settings: hda:DMA, hdb:DMA
>> Feb 27 20:49:43 kuza kernel:     ide1: BM-DMA at 0xd408-0xd40f, BIOS
>> settings: hdc:DMA, hdd:pio
>> Feb 27 20:49:43 kuza kernel: hda: Maxtor 4D040H2, ATA DISK drive
>> Feb 27 20:49:43 kuza kernel: hdb: ST3120814A, ATA DISK drive
>> Feb 27 20:49:43 kuza kernel: hda: hw_config=603b
>> Feb 27 20:49:43 kuza kernel: hda: hw_config=603b
>> Feb 27 20:49:43 kuza kernel: hdb: hw_config=6d00
>> Feb 27 20:49:43 kuza kernel: hdb: hw_config=6d00
>> Feb 27 20:49:43 kuza kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
>> Feb 27 20:49:49 kuza kernel: hdc: MATSHITA CR-583, ATAPI CD/DVD-ROM
>>drive
>> Feb 27 20:49:49 kuza rpc.statd[1535]: Version 1.0.8 Starting
>> Feb 27 20:49:49 kuza kernel: hdd: no response (status = 0xa1), resetting
>> drive
>> Feb 27 20:49:49 kuza kernel: hdd: no response (status = 0xa1)
>> Feb 27 20:49:49 kuza kernel: ide1 at 0x170-0x177,0x376 on irq 15
>> Feb 27 20:49:49 kuza kernel: hda: max request size: 128KiB
>> Feb 27 20:49:49 kuza kernel: hda: 80043264 sectors (40982 MB) w/2048KiB
>> Cache, CHS=65535/16/63<6>hda: hw_config=603b
>> Feb 27 20:49:49 kuza kernel: , UDMA(100)
>> Feb 27 20:49:49 kuza kernel: hda: cache flushes not supported
>> Feb 27 20:49:49 kuza kernel:  hda: hda1 hda2 hda3 hda4<  hda5>
>> Feb 27 20:49:49 kuza kernel: hdb: max request size: 128KiB
>> Feb 27 20:49:49 kuza kernel: hdb: 234441648 sectors (120034 MB)
>> w/8192KiB Cache, CHS=16383/255/63<6>hdb: hw_config=6d00
>> Feb 27 20:49:49 kuza kernel: , UDMA(100)
>> Feb 27 20:49:49 kuza kernel: hdb: cache flushes supported
>> Feb 27 20:49:49 kuza kernel:  hdb: hdb1
>> Feb 27 20:49:49 kuza kernel: ide-floppy driver 0.99.newide
>> Feb 27 20:49:49 kuza kernel: usbcore: registered new interface driver
>> libusual
>> Feb 27 20:49:49 kuza kernel: usbcore: registered new interface driver
>>hiddev
>> Feb 27 20:49:49 kuza kernel: usbcore: registered new interface driver
>>usbhid
>> Feb 27 20:49:49 kuza kernel: drivers/usb/input/hid-core.c: v2.6:USB HID
>> core driver
>> Feb 27 20:49:49 kuza kernel: PNP: PS/2 Controller
>> [PNP0303:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,12
>> Feb 27 20:49:49 kuza kernel: serio: i8042 KBD port at 0x60,0x64 irq 1
>> Feb 27 20:49:49 kuza kernel: serio: i8042 AUX port at 0x60,0x64 irq 12
>> Feb 27 20:49:49 kuza kernel: mice: PS/2 mouse device common for all mice
>> Feb 27 20:49:49 kuza kernel: input: AT Translated Set 2 keyboard as
>> /class/input/input1
>> Feb 27 20:49:49 kuza kernel: TCP bic registered
>> Feb 27 20:49:49 kuza kernel: Initializing XFRM netlink socket
>> Feb 27 20:49:49 kuza kernel: NET: Registered protocol family 1
>> Feb 27 20:49:49 kuza kernel: NET: Registered protocol family 17
>> Feb 27 20:49:49 kuza kernel: powernow-k8: Processor cpuid 631 not
>>supported
>> Feb 27 20:49:49 kuza kernel: Using IPI Shortcut mode
>> Feb 27 20:49:49 kuza kernel: Time: tsc clocksource has been installed.
>> Feb 27 20:49:49 kuza kernel: ACPI: (supports S0 S1 S4 S5)
>> Feb 27 20:49:49 kuza kernel: Freeing unused kernel memory: 232k freed
>> Feb 27 20:49:49 kuza kernel: Write protecting the kernel read-only data:
>> 585k
>> Feb 27 20:49:49 kuza kernel: input: ImPS/2 Generic Wheel Mouse as
>> /class/input/input2
>> Feb 27 20:49:49 kuza kernel: EXT3-fs: INFO: recovery required on
>> readonly filesystem.
>> Feb 27 20:49:49 kuza kernel: EXT3-fs: write access will be enabled
>> during recovery.
>> Feb 27 20:49:49 kuza kernel: kjournald starting.  Commit interval 5
>>seconds
>> Feb 27 20:49:49 kuza kernel: EXT3-fs: recovery complete.
>> Feb 27 20:49:49 kuza kernel: EXT3-fs: mounted filesystem with ordered
>> data mode.
>> Feb 27 20:49:49 kuza kernel: SELinux:  Disabled at runtime.
>> Feb 27 20:49:49 kuza kernel: SELinux:  Unregistering netfilter hooks
>> Feb 27 20:49:49 kuza kernel: audit(1330375739.875:2): selinux=0
>> auid=4294967295
>> Feb 27 20:49:49 kuza kernel: alim7101_wdt: Steve
>>Hill<steve at navaho.co.uk>.
>> Feb 27 20:49:49 kuza kernel: alim7101_wdt: Detected old alim7101
>> revision 'a1d'.  If this is a cobalt board, set the 'use_gpio' module
>> parameter.
>> Feb 27 20:49:49 kuza kernel: input: PC Speaker as /class/input/input3
>> Feb 27 20:49:49 kuza kernel: hdc: ATAPI 8X CD-ROM drive, 128kB Cache,
>>DMA
>> Feb 27 20:49:49 kuza kernel: Uniform CD-ROM driver Revision: 3.20
>> Feb 27 20:49:49 kuza kernel: 8139too Fast Ethernet driver 0.9.28
>> Feb 27 20:49:49 kuza kernel: ACPI: PCI Interrupt Link [LNKC] enabled at
>> IRQ 10
>> Feb 27 20:49:49 kuza kernel: ACPI: PCI Interrupt 0000:00:0a.0[A] ->
>>Link
>> [LNKC] ->  GSI 10 (level, low) ->  IRQ 10
>> Feb 27 20:49:49 kuza kernel: eth0: RealTek RTL8139 at 0xd081e000,
>> 00:50:ba:5f:e4:c3, IRQ 10
>> Feb 27 20:49:49 kuza kernel: Floppy drive(s): fd0 is 1.44M
>> Feb 27 20:49:49 kuza kernel: FDC 0 is a post-1991 82077
>> Feb 27 20:49:49 kuza kernel: ACPI: PCI Interrupt Link [LNKI] enabled at
>> IRQ 9
>> Feb 27 20:49:49 kuza kernel: ACPI: PCI Interrupt 0000:00:02.0[A] ->
>>Link
>> [LNKI] ->  GSI 9 (level, low) ->  IRQ 9
>> Feb 27 20:49:49 kuza kernel: ohci_hcd 0000:00:02.0: OHCI Host Controller
>> Feb 27 20:49:49 kuza kernel: ohci_hcd 0000:00:02.0: new USB bus
>> registered, assigned bus number 1
>> Feb 27 20:49:49 kuza kernel: ohci_hcd 0000:00:02.0: irq 9, io mem
>>0xeb800000
>> Feb 27 20:49:49 kuza kernel: usb usb1: configuration #1 chosen from 1
>>choice
>> Feb 27 20:49:49 kuza kernel: hub 1-0:1.0: USB hub found
>> Feb 27 20:49:49 kuza kernel: hub 1-0:1.0: 4 ports detected
>> Feb 27 20:49:49 kuza kernel: ACPI: PCI Interrupt Link [LNKE] enabled at
>> IRQ 5
>> Feb 27 20:49:49 kuza kernel: ACPI: PCI Interrupt 0000:00:06.0[A] ->
>>Link
>> [LNKE] ->  GSI 5 (level, low) ->  IRQ 5
>> Feb 27 20:49:49 kuza kernel: ohci_hcd 0000:00:06.0: OHCI Host Controller
>> Feb 27 20:49:49 kuza kernel: ohci_hcd 0000:00:06.0: new USB bus
>> registered, assigned bus number 2
>> Feb 27 20:49:49 kuza kernel: ohci_hcd 0000:00:06.0: irq 5, io mem
>>0xea800000
>> Feb 27 20:49:49 kuza kernel: usb usb2: configuration #1 chosen from 1
>>choice
>> Feb 27 20:49:49 kuza kernel: hub 2-0:1.0: USB hub found
>> Feb 27 20:49:49 kuza kernel: hub 2-0:1.0: 2 ports detected
>> Feb 27 20:49:49 kuza kernel: usb 1-1: new low speed USB device using
>> ohci_hcd and address 2
>> Feb 27 20:49:49 kuza kernel: usb 1-1: configuration #1 chosen from 1
>>choice
>> Feb 27 20:49:49 kuza kernel: parport: PnPBIOS parport detected.
>> Feb 27 20:49:49 kuza kernel: parport0: PC-style at 0x378 (0x778), irq 7
>> [PCSPP,TRISTATE]
>> Feb 27 20:49:49 kuza kernel: lp0: using parport0 (interrupt-driven).
>> Feb 27 20:49:49 kuza kernel: lp0: console ready
>> Feb 27 20:49:49 kuza kernel: hiddev96: USB HID v1.10 Device [American
>> Power Conversion Back-UPS XS 1300 LCD FW:836.H5 .D USB FW:H5 ] on
>> usb-0000:00:02.0-1
>> Feb 27 20:49:49 kuza kernel: NET: Registered protocol family 10
>> Feb 27 20:49:49 kuza kernel: lo: Disabled Privacy Extensions
>> Feb 27 20:49:49 kuza kernel: Mobile IPv6
>> Feb 27 20:49:49 kuza kernel: input: Power Button (FF) as
>>/class/input/input4
>> Feb 27 20:49:49 kuza kernel: ACPI: Power Button (FF) [PWRF]
>> Feb 27 20:49:49 kuza kernel: input: Power Button (CM) as
>>/class/input/input5
>> Feb 27 20:49:49 kuza kernel: ACPI: Power Button (CM) [PWRB]
>> Feb 27 20:49:49 kuza kernel: No dock devices found.
>> Feb 27 20:49:49 kuza kernel: ibm_acpi: ec object not found
>> Feb 27 20:49:49 kuza kernel: md: Autodetecting RAID arrays.
>> Feb 27 20:49:49 kuza kernel: md: autorun ...
>> Feb 27 20:49:49 kuza kernel: md: ... autorun DONE.
>> Feb 27 20:49:49 kuza kernel: device-mapper: ioctl: 4.11.0-ioctl
>> (2006-10-12) initialised: dm-devel at redhat.com
>> Feb 27 20:49:49 kuza kernel: EXT3 FS on hda5, internal journal
>> Feb 27 20:49:49 kuza kernel: kjournald starting.  Commit interval 5
>>seconds
>> Feb 27 20:49:49 kuza kernel: EXT3 FS on hda1, internal journal
>> Feb 27 20:49:49 kuza kernel: EXT3-fs: mounted filesystem with ordered
>> data mode.
>> Feb 27 20:49:49 kuza kernel: kjournald starting.  Commit interval 5
>>seconds
>> Feb 27 20:49:49 kuza kernel: EXT3 FS on hdb1, internal journal
>> Feb 27 20:49:50 kuza kernel: EXT3-fs: mounted filesystem with ordered
>> data mode.
>> Feb 27 20:49:50 kuza kernel: kjournald starting.  Commit interval 5
>>seconds
>> Feb 27 20:49:50 kuza kernel: EXT3 FS on hda2, internal journal
>> Feb 27 20:49:50 kuza kernel: EXT3-fs: mounted filesystem with ordered
>> data mode.
>> Feb 27 20:49:50 kuza kernel: Adding 514072k swap on /dev/hda3.
>> Priority:-1 extents:1 across:514072k
>> Feb 27 20:49:50 kuza kernel: eth0: link up, 100Mbps, full-duplex, lpa
>>0x45E1
>> Feb 27 20:49:53 kuza kernel: Bluetooth: Core ver 2.11
>> Feb 27 20:49:53 kuza kernel: NET: Registered protocol family 31
>> Feb 27 20:49:53 kuza kernel: Bluetooth: HCI device and connection
>> manager initialized
>> Feb 27 20:49:53 kuza kernel: Bluetooth: HCI socket layer initialized
>> Feb 27 20:49:53 kuza kernel: Bluetooth: L2CAP ver 2.8
>> Feb 27 20:49:53 kuza kernel: Bluetooth: L2CAP socket layer initialized
>> Feb 27 20:49:53 kuza kernel: Bluetooth: HIDP (Human Interface Emulation)
>> ver 1.1
>> Feb 27 20:49:53 kuza hidd[1621]: Bluetooth HID daemon
>> Feb 27 20:49:56 kuza smartd[1719]: smartd version 5.36
>> [i686-redhat-linux-gnu] Copyright (C) 2002-6 Bruce Allen
>> Feb 27 20:49:56 kuza smartd[1719]: Home page is
>> http://smartmontools.sourceforge.net/
>> Feb 27 20:49:56 kuza smartd[1719]: Opened configuration file
>> /etc/smartd.conf
>> Feb 27 20:49:56 kuza smartd[1719]: Configuration file /etc/smartd.conf
>> parsed.
>> Feb 27 20:49:56 kuza smartd[1719]: Device: /dev/hda, opened
>> Feb 27 20:49:56 kuza smartd[1719]: Device: /dev/hda, found in smartd
>> database.
>> Feb 27 20:49:57 kuza smartd[1719]: Device: /dev/hda, is SMART capable.
>> Adding to "monitor" list.
>> Feb 27 20:49:57 kuza smartd[1719]: Device: /dev/hdb, opened
>> Feb 27 20:49:57 kuza smartd[1719]: Device: /dev/hdb, not found in smartd
>> database.
>> Feb 27 20:49:58 kuza smartd[1719]: Device: /dev/hdb, is SMART capable.
>> Adding to "monitor" list.
>> Feb 27 20:49:58 kuza smartd[1719]: Monitoring 2 ATA and 0 SCSI devices
>> Feb 27 20:49:59 kuza smartd[1724]: smartd has fork()ed into background
>> mode. New PID=1724.
>> Feb 27 20:49:59 kuza hpiod: 1.6.6a accepting connections at 50000...
>> Feb 27 20:50:06 kuza xinetd[1770]: xinetd Version 2.3.13 started with
>> libwrap loadavg options compiled in.
>> Feb 27 20:50:06 kuza xinetd[1770]: Started working: 1 available service
>> Feb 27 20:50:06 kuza exportfs[1803]: No host name given with /data
>> (sync,rw), suggest *(sync,rw) to avoid warning
>> Feb 27 20:50:06 kuza apcupsd[1789]: apcupsd 3.12.4 (19 August 2006)
>> redhat startup succeeded
>> Feb 27 20:50:06 kuza apcupsd[1789]: NIS server startup succeeded
>> Feb 27 20:50:07 kuza kernel: Installing knfsd (copyright (C) 1996
>> okir at monad.swb.de).
>> Feb 27 20:50:07 kuza kernel: NFSD: Using /var/lib/nfs/v4recovery as the
>> NFSv4 state recovery directory
>> Feb 27 20:50:07 kuza kernel: NFSD: starting 90-second grace period
>> Feb 27 20:50:08 kuza gpm[1855]: *** info [startup.c(95)]:
>> Feb 27 20:50:08 kuza gpm[1855]: Started gpm successfully. Entered daemon
>> mode.
>> Feb 27 20:50:20 kuza avahi-daemon[2009]: Found user 'avahi' (UID 70) and
>> group 'avahi' (GID 70).
>> Feb 27 20:50:20 kuza avahi-daemon[2009]: Successfully dropped root
>> privileges.
>> Feb 27 20:50:20 kuza avahi-daemon[2009]: avahi-daemon 0.6.11 starting
>>up.
>> Feb 27 20:50:20 kuza avahi-daemon[2009]: WARNING: No NSS support for
>> mDNS detected, consider installing nss-mdns!
>> Feb 27 20:50:21 kuza avahi-daemon[2009]: Successfully called chroot().
>> Feb 27 20:50:21 kuza avahi-daemon[2009]: Successfully dropped remaining
>> capabilities.
>> Feb 27 20:50:21 kuza avahi-daemon[2009]: No service found in
>> /etc/avahi/services.
>> Feb 27 20:50:21 kuza avahi-daemon[2009]: New relevant interface
>> eth0.IPv6 for mDNS.
>> Feb 27 20:50:21 kuza avahi-daemon[2009]: Joining mDNS multicast group on
>> interface eth0.IPv6 with address fe80::250:baff:fe5f:e4c3.
>> Feb 27 20:50:21 kuza avahi-daemon[2009]: New relevant interface
>> eth0.IPv4 for mDNS.
>> Feb 27 20:50:21 kuza avahi-daemon[2009]: Joining mDNS multicast group on
>> interface eth0.IPv4 with address 192.168.1.3.
>> Feb 27 20:50:21 kuza avahi-daemon[2009]: Network interface enumeration
>> completed.
>> Feb 27 20:50:21 kuza avahi-daemon[2009]: Registering new address record
>> for fe80::250:baff:fe5f:e4c3 on eth0.
>> Feb 27 20:50:21 kuza avahi-daemon[2009]: Registering new address record
>> for 192.168.1.3 on eth0.
>> Feb 27 20:50:21 kuza avahi-daemon[2009]: Registering HINFO record with
>> values 'I686'/'LINUX'.
>> Feb 27 20:50:21 kuza avahi-daemon[2009]: Server startup complete. Host
>> name is kuza.local. Local service cookie is 2874978490.
>> Feb 27 20:56:06 kuza nmbd[1930]: [2012/02/27 20:56:06, 0]
>> nmbd/nmbd_become_lmb.c:become_local_master_stage2(396)
>> Feb 27 20:56:06 kuza nmbd[1930]:   *****
>> Feb 27 20:56:06 kuza nmbd[1930]:
>> Feb 27 20:56:06 kuza nmbd[1930]:   Samba name server KUZA is now a local
>> master browser for workgroup WORKGROUP on subnet 192.168.1.3
>> Feb 27 20:56:06 kuza nmbd[1930]:
>> Feb 27 20:56:06 kuza nmbd[1930]:   *****
>> _______________________________________________
>> mdlug mailing list
>> mdlug at mdlug.org
>> http://mdlug.org/mailman/listinfo/mdlug
>
>_______________________________________________
>mdlug mailing list
>mdlug at mdlug.org
>http://mdlug.org/mailman/listinfo/mdlug


From rk111810 at gmail.com  Tue Feb 28 18:06:41 2012
From: rk111810 at gmail.com (R KANNAN)
Date: Tue, 28 Feb 2012 18:06:41 -0500
Subject: [mdlug] Lenovo laptop lost sound in Ubuntu 11.11
Message-ID: <CABX2cSFtxX48P+H+sr16aVuo37xvkmshUAWAfDEVeRnTz3mu9Q@mail.gmail.com>

Hello,

My Lenovo laptop suddenly lost sound in Ubuntu 11.11. relevant 'lspci'
entry shows:

00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio
Controller (rev 03)
    Subsystem: Lenovo ThinkPad T61
    Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR+ FastB2B- D
isINTx+
    Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort-
<MAbort- >SERR- <PERR-
 INTx-
......
            Addr:    00000000fed1c000
    Kernel driver in use: HDA Intel
    Kernel modules: snd-hda-intel

'lsmod' shows:

snd_hda_intel          24262  0
snd_hda_codec          91859  2 snd_hda_codec_analog,snd_hda_intel
snd_hwdep              13276  1 snd_hda_codec
snd_pcm                80435  2 snd_hda_intel,snd_hda_codec
snd_seq_midi           13132  0
snd_rawmidi            25241  1 snd_seq_midi
snd_seq_midi_event     14475  1 snd_seq_midi
snd_seq                51567  2 snd_seq_midi,snd_seq_midi_event
snd_timer              28932  2 snd_pcm,snd_seq
snd_seq_device         14172  3 snd_seq_midi,snd_rawmidi,snd_seq

My feeling is that there is a hardware failure. Anything I can check for?

Thanks

From rk111810 at gmail.com  Tue Feb 28 18:16:01 2012
From: rk111810 at gmail.com (R KANNAN)
Date: Tue, 28 Feb 2012 18:16:01 -0500
Subject: [mdlug] Lenovo laptop lost sound in Ubuntu 11.11
In-Reply-To: <CABX2cSFtxX48P+H+sr16aVuo37xvkmshUAWAfDEVeRnTz3mu9Q@mail.gmail.com>
References: <CABX2cSFtxX48P+H+sr16aVuo37xvkmshUAWAfDEVeRnTz3mu9Q@mail.gmail.com>
Message-ID: <CABX2cSEBXjt3vtscRc8sFdgT_bioPJshuUe-yk-nibGd3Yg0Rw@mail.gmail.com>

Never mind. A reboot seems to have fixed the issue.

On Tue, Feb 28, 2012 at 6:06 PM, R KANNAN <rk111810 at gmail.com> wrote:

> Hello,
>
> My Lenovo laptop suddenly lost sound in Ubuntu 11.11. relevant 'lspci'
> entry shows:
>
> 00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio
> Controller (rev 03)
>     Subsystem: Lenovo ThinkPad T61
>     Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
> Stepping- SERR+ FastB2B- D
> isINTx+
>     Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
> <TAbort- <MAbort- >SERR- <PERR-
>  INTx-
> ......
>             Addr:    00000000fed1c000
>     Kernel driver in use: HDA Intel
>     Kernel modules: snd-hda-intel
>
> 'lsmod' shows:
>
> snd_hda_intel          24262  0
> snd_hda_codec          91859  2 snd_hda_codec_analog,snd_hda_intel
> snd_hwdep              13276  1 snd_hda_codec
> snd_pcm                80435  2 snd_hda_intel,snd_hda_codec
> snd_seq_midi           13132  0
> snd_rawmidi            25241  1 snd_seq_midi
> snd_seq_midi_event     14475  1 snd_seq_midi
> snd_seq                51567  2 snd_seq_midi,snd_seq_midi_event
> snd_timer              28932  2 snd_pcm,snd_seq
> snd_seq_device         14172  3 snd_seq_midi,snd_rawmidi,snd_seq
>
> My feeling is that there is a hardware failure. Anything I can check for?
>
> Thanks
>
>
>

From akulkis00 at gmail.com  Wed Feb 29 04:04:44 2012
From: akulkis00 at gmail.com (Aaron Kulkis)
Date: Wed, 29 Feb 2012 04:04:44 -0500
Subject: [mdlug] hanging machine kernel panic - on going
In-Reply-To: <CB72AC79.1F1D0%gregwojtak@quickenloans.com>
References: <CB72AC79.1F1D0%gregwojtak@quickenloans.com>
Message-ID: <4F4DEA2C.8050202@gmail.com>

Wojtak, Greg (Superfly) wrote:
> If you're feeling really ambitious you could make sure that the kdump
> system is configured, grab the kernel dump, and run gdb on it...
>

I haven't fired up a debugger in over a decade.  Even though I
have debugged a kernel (we had to write a multi-user, pre-emptive
multi-tasking kernel with interprocess communication in 4 weeks for
one of my senior-level labs), that was on code I was familiar with,
on a processor which I thoroughly understood.

Unfortunately, neither of those applies here.

I would be lost both in the Linux kernel code and also on
a modern Intel or AMD processor. :-(.

Recently, I've been slowly working my way through an x86 assembly
language book -- and it's odd.  The assembly language seems to be
simultaneously much simpler (fewer operation types, and far fewer
addressing modes) than other assembly languages that I learned
(6502, 8080, PDP-11, IBM 370, and VAX-11), but for some reason,
paradoxically, more complex.  I won't bore you with the details,
other than to say that there are 8, 16, 32 (and now 64)-bit
versions of four registers A, B, C, and D (which Intel intended
to stand for Accumulator, Base, Code, and Data), but which,
other than the A registers, seem to be used rather inconsistently.

To make things more confusing, gcc and g++ don't produce
standard Intel format assembly code (ASM / NASM compatible),
instead producing something called AT&T format assembly code,
which has operands in the reverse order of Intel format
(not to mention distinctly different assembler directives
for things such as labels, reserving memory blocks, pre-positioned
constants, etc.)

SoI'm just going to wait for the kernel team to
figure it all out.

> On 2012-02-28 10:47 AM, "Aaron Kulkis"<akulkis00 at gmail.com>  wrote:
>
>> Gmail-otakurider wrote:
>>> Here is the messages dump - check around 16:53 anyone have any ideas?
>>> checked memory tested ok - checked HDD tested ok
>>>
>>
>>
>> I've been getting some panics lately, too.  My suspicion
>> is that a kernel bug was recently introduced.  I also trust
>> that with time, it will be found and go away.
>>
>> Fortunately, I still have some habits from my college days
>> when Purdue's Electrical Engineering department was the
>> primary test site for Gould Electronics' high performance
>> Unix division, and endured periods in which typical
>> uptime was<90 minutes, until the problems were found
>> and resolved.
>>
>>> Yes I know its long but wanted to give all info
>>>
>>>    thinking of setting panic=  setting to have it just reboot
>>>
>>> Thank in advance
>>>
>>>
>>>
>>> Feb 27 10:37:30 kuza avahi-daemon[2006]: Network interface enumeration
>>> completed.
>>> Feb 27 10:37:30 kuza avahi-daemon[2006]: Registering new address record
>>> for fe80::250:baff:fe5f:e4c3 on eth0.
>>> Feb 27 10:37:30 kuza avahi-daemon[2006]: Registering new address record
>>> for 192.168.1.3 on eth0.
>>> Feb 27 10:37:30 kuza avahi-daemon[2006]: Registering HINFO record with
>>> values 'I686'/'LINUX'.
>>> Feb 27 10:37:31 kuza avahi-daemon[2006]: Server startup complete. Host
>>> name is kuza.local. Local service cookie is 1101511634.
>>> Feb 27 10:43:10 kuza nmbd[1926]: [2012/02/27 10:43:10, 0]
>>> nmbd/nmbd_become_lmb.c:become_local_master_stage2(396)
>>> Feb 27 10:43:10 kuza nmbd[1926]:   *****
>>> Feb 27 10:43:10 kuza nmbd[1926]:
>>> Feb 27 10:43:10 kuza nmbd[1926]:   Samba name server KUZA is now a local
>>> master browser for workgroup WORKGROUP on subnet 192.168.1.3
>>> Feb 27 10:43:10 kuza nmbd[1926]:
>>> Feb 27 10:43:10 kuza nmbd[1926]:   *****
>>> Feb 27 11:18:52 kuza avahi-daemon[2006]: Invalid query packet.
>>> Feb 27 11:19:32 kuza last message repeated 26 times
>>> Feb 27 11:19:32 kuza avahi-daemon[2006]: Invalid query packet.
>>> Feb 27 16:53:41 kuza kernel: BUG: unable to handle kernel NULL pointer
>>> dereference at virtual address 00000000
>>> Feb 27 16:53:41 kuza kernel:  printing eip:
>>> Feb 27 16:53:41 kuza kernel: cab88e5c
>>> Feb 27 16:53:41 kuza kernel: *pde = 09606067
>>> Feb 27 16:53:41 kuza kernel: Oops: 0002 [#1]
>>> Feb 27 16:53:41 kuza kernel: last sysfs file: /block/hda/hda1/size
>>> Feb 27 16:53:41 kuza kernel: Modules linked in: nfsd exportfs lockd
>>> nfs_acl autofs4 hidp l2cap bluetooth sunrpc dm_mirror dm_mod video sbs
>>> i2c_ec dock container button battery asus_acpi backlight ac ipv6 lp
>>> parport_pc parport floppy ohci_hcd 8139too i2c_ali15x3 serio_raw mii
>>> i2c_ali1535 i2c_core pcspkr ide_cd cdrom ext3 jbd
>>> Feb 27 16:53:41 kuza kernel: CPU:    0
>>> Feb 27 16:53:41 kuza kernel: EIP:    0060:[<cab88e5c>]    Not tainted
>>> VLI
>>> Feb 27 16:53:41 kuza kernel: EFLAGS: 00210206   (2.6.20-1.2320.fc5 #1)
>>> Feb 27 16:53:41 kuza kernel: EIP is at 0xcab88e5c
>>> Feb 27 16:53:41 kuza kernel: eax: 00000000   ebx: cab88f9c   ecx:
>>> ca3c3610   edx: c137c980
>>> Feb 27 16:53:41 kuza kernel: esi: cab88f48   edi: 00000006   ebp:
>>> cab88e58   esp: cab88ba4
>>> Feb 27 16:53:41 kuza kernel: ds: 007b   es: 007b   ss: 0068
>>> Feb 27 16:53:41 kuza kernel: Process python (pid: 1745, ti=cab88000
>>> task=cfec30d0 task.ti=cab88000)
>>> Feb 27 16:53:41 kuza kernel: Stack: cab88e60 cab88e4c cab88e50 cab88e54
>>> 00000030 00000000 00000000 00000030
>>> Feb 27 16:53:41 kuza kernel:        00000000 00000000 00000000 00000000
>>> 00000000 00000000 c046ad08 00000000
>>> Feb 27 16:53:41 kuza kernel:        00000000 00000002 ccd0f320 00000000
>>> cfec30d0 c0419bdc 00100100 00200200
>>> Feb 27 16:53:41 kuza kernel: Call Trace:
>>> Feb 27 16:53:41 kuza kernel:  [<c046ad08>] __pollwait+0x0/0xab
>>> Feb 27 16:53:41 kuza kernel:  [<c0419bdc>] default_wake_function+0x0/0xc
>>> Feb 27 16:53:41 kuza kernel:  [<c0419bdc>] default_wake_function+0x0/0xc
>>> Feb 27 16:53:41 kuza kernel:  [<d082fb73>]
>>> do_get_write_access+0x48b/0x4b8 [jbd]
>>> Feb 27 16:53:41 kuza kernel:  [<d08885f8>]
>>> __ext3_get_inode_loc+0x10a/0x2fd [ext3]
>>> Feb 27 16:53:41 kuza kernel:  [<c0608164>] _read_unlock_irq+0x5/0x7
>>> Feb 27 16:53:41 kuza kernel:  [<d0893712>]
>>> __ext3_journal_dirty_metadata+0x16/0x3a [ext3]
>>> Feb 27 16:53:41 kuza kernel:  [<d082fbc1>]
>>> journal_get_write_access+0x21/0x26 [jbd]
>>> Feb 27 16:53:41 kuza kernel:  [<d0888489>]
>>> ext3_mark_iloc_dirty+0x275/0x2da [ext3]
>>> Feb 27 16:53:41 kuza kernel:  [<c0418de8>] __wake_up+0x32/0x43
>>> Feb 27 16:53:41 kuza kernel:  [<d082f6dc>] journal_stop+0x1cb/0x1d7
>>> [jbd]
>>> Feb 27 16:53:41 kuza kernel:  [<d088f703>] __ext3_journal_stop+0x19/0x34
>>> [ext3]
>>> Feb 27 16:53:41 kuza kernel:  [<d088a6b2>]
>>> ext3_ordered_commit_write+0xba/0xd8 [ext3]
>>> Feb 27 16:53:41 kuza kernel:  [<c044aaa7>] __pagevec_lru_add+0x7a/0x85
>>> Feb 27 16:53:41 kuza kernel:  [<c0446328>]
>>> generic_file_buffered_write+0x579/0x5e8
>>> Feb 27 16:53:41 kuza kernel:  [<c047aa2a>] __getblk+0x3b/0x287
>>> Feb 27 16:53:41 kuza kernel:  [<c0420638>] current_fs_time+0x45/0x51
>>> Feb 27 16:53:41 kuza kernel:  [<c0405e65>] do_IRQ+0xbf/0xd6
>>> Feb 27 16:53:41 kuza kernel:  [<c0404763>] common_interrupt+0x23/0x28
>>> Feb 27 16:53:41 kuza kernel:  [<c046aa67>] core_sys_select+0x2d2/0x2f3
>>> Feb 27 16:53:41 kuza kernel:  [<c0448dff>] __alloc_pages+0x68/0x29c
>>> Feb 27 16:53:41 kuza kernel:  [<c0608164>] _read_unlock_irq+0x5/0x7
>>> Feb 27 16:53:41 kuza kernel:  [<c0444c30>] find_get_page+0x35/0x3a
>>> Feb 27 16:53:41 kuza kernel:  [<c044710b>] filemap_nopage+0x159/0x2d4
>>> Feb 27 16:53:41 kuza kernel:  [<c044f9c9>] __handle_mm_fault+0x858/0x87a
>>> Feb 27 16:53:41 kuza kernel:  [<c0452bf4>] do_mmap_pgoff+0x587/0x6e8
>>> Feb 27 16:53:41 kuza kernel:  [<c046b04e>] sys_select+0xa0/0x186
>>> Feb 27 16:53:41 kuza kernel:  [<c0403dc8>] syscall_call+0x7/0xb
>>> Feb 27 16:53:41 kuza kernel:  =======================
>>> Feb 27 16:53:41 kuza kernel: Code: aa 46 c0 48 4b c3 bf ea ff ff ff 00
>>> e0 9a 08 00 e0 9a 08 06 00 00 00 30 00 00 00 00 00 00 00 00 00 00 00 00
>>> 00 00 00 00 00 00 00<00>   00 00 00 44 00 00 00 46 02 20 00 01 00 00 00
>>> 00 00 00 00 d2
>>> Feb 27 16:53:41 kuza kernel: EIP: [<cab88e5c>] 0xcab88e5c SS:ESP
>>> 0068:cab88ba4
>>> Feb 27 20:04:54 kuza avahi-daemon[2006]: Invalid query packet.
>>> Feb 27 20:05:38 kuza last message repeated 30 times
>>> Feb 27 20:49:41 kuza syslogd 1.4.1: restart.
>>> Feb 27 20:49:41 kuza kernel: klogd 1.4.1, log source = /proc/kmsg
>>> started.
>>> Feb 27 20:49:41 kuza kernel: Linux version 2.6.20-1.2320.fc5
>>> (brewbuilder at hs20-bc2-2.build.redhat.com) (gcc version 4.1.1 20070105
>>> (Red Hat 4.1.1-51)) #1 Tue Jun 12 18:50:38 EDT 2007
>>> Feb 27 20:49:41 kuza kernel: BIOS-provided physical RAM map:
>>> Feb 27 20:49:41 kuza kernel: sanitize start
>>> Feb 27 20:49:41 kuza kernel: sanitize end
>>> Feb 27 20:49:41 kuza kernel: copy_e820_map() start: 0000000000000000
>>> size: 000000000009fc00 end: 000000000009fc00 type: 1
>>> Feb 27 20:49:41 kuza kernel: copy_e820_map() type is E820_RAM
>>> Feb 27 20:49:41 kuza kernel: copy_e820_map() start: 000000000009fc00
>>> size: 0000000000000400 end: 00000000000a0000 type: 2
>>> Feb 27 20:49:41 kuza kernel: copy_e820_map() start: 00000000000f0000
>>> size: 0000000000010000 end: 0000000000100000 type: 2
>>> Feb 27 20:49:41 kuza kernel: copy_e820_map() start: 0000000000100000
>>> size: 000000000feec000 end: 000000000ffec000 type: 1
>>> Feb 27 20:49:41 kuza kernel: copy_e820_map() type is E820_RAM
>>> Feb 27 20:49:41 kuza kernel: copy_e820_map() start: 000000000ffec000
>>> size: 0000000000003000 end: 000000000ffef000 type: 3
>>> Feb 27 20:49:41 kuza kernel: copy_e820_map() start: 000000000ffef000
>>> size: 0000000000010000 end: 000000000ffff000 type: 2
>>> Feb 27 20:49:41 kuza kernel: copy_e820_map() start: 000000000ffff000
>>> size: 0000000000001000 end: 0000000010000000 type: 4
>>> Feb 27 20:49:41 kuza kernel: copy_e820_map() start: 00000000ffff0000
>>> size: 0000000000010000 end: 0000000100000000 type: 2
>>> Feb 27 20:49:41 kuza kernel:  BIOS-e820: 0000000000000000 -
>>> 000000000009fc00 (usable)
>>> Feb 27 20:49:41 kuza kernel:  BIOS-e820: 000000000009fc00 -
>>> 00000000000a0000 (reserved)
>>> Feb 27 20:49:41 kuza kernel:  BIOS-e820: 00000000000f0000 -
>>> 0000000000100000 (reserved)
>>> Feb 27 20:49:41 kuza kernel:  BIOS-e820: 0000000000100000 -
>>> 000000000ffec000 (usable)
>>> Feb 27 20:49:41 kuza kernel:  BIOS-e820: 000000000ffec000 -
>>> 000000000ffef000 (ACPI data)
>>> Feb 27 20:49:41 kuza kernel:  BIOS-e820: 000000000ffef000 -
>>> 000000000ffff000 (reserved)
>>> Feb 27 20:49:41 kuza kernel:  BIOS-e820: 000000000ffff000 -
>>> 0000000010000000 (ACPI NVS)
>>> Feb 27 20:49:41 kuza kernel:  BIOS-e820: 00000000ffff0000 -
>>> 0000000100000000 (reserved)
>>> Feb 27 20:49:41 kuza kernel: 0MB HIGHMEM available.
>>> Feb 27 20:49:41 kuza kernel: 255MB LOWMEM available.
>>> Feb 27 20:49:41 kuza kernel: Using x86 segment limits to approximate NX
>>> protection
>>> Feb 27 20:49:41 kuza kernel: Zone PFN ranges:
>>> Feb 27 20:49:41 kuza kernel:   DMA             0 ->       4096
>>> Feb 27 20:49:43 kuza kernel:   Normal       4096 ->      65516
>>> Feb 27 20:49:43 kuza kernel:   HighMem     65516 ->      65516
>>> Feb 27 20:49:43 kuza kernel: early_node_map[1] active PFN ranges
>>> Feb 27 20:49:43 kuza kernel:     0:        0 ->      65516
>>> Feb 27 20:49:43 kuza kernel: DMI 2.3 present.
>>> Feb 27 20:49:43 kuza kernel: Using APIC driver default
>>> Feb 27 20:49:43 kuza kernel: ACPI: PM-Timer IO Port: 0xe408
>>> Feb 27 20:49:43 kuza kernel: Allocating PCI resources starting at
>>> 20000000 (gap: 10000000:efff0000)
>>> Feb 27 20:49:43 kuza kernel: Detected 807.940 MHz processor.
>>> Feb 27 20:49:43 kuza kernel: Built 1 zonelists.  Total pages: 65005
>>> Feb 27 20:49:43 kuza kernel: Kernel command line: ro root=LABEL=/ rhgb
>>> quiet
>>> Feb 27 20:49:43 kuza kernel: Local APIC disabled by BIOS -- you can
>>> enable it with "lapic"
>>> Feb 27 20:49:43 kuza kernel: Enabling fast FPU save and restore... done.
>>> Feb 27 20:49:43 kuza kernel: Initializing CPU#0
>>> Feb 27 20:49:43 kuza kernel: CPU 0 irqstacks, hard=c0720000
>>> soft=c071f000
>>> Feb 27 20:49:43 kuza kernel: PID hash table entries: 1024 (order: 10,
>>> 4096 bytes)
>>> Feb 27 20:49:43 kuza kernel: Console: colour VGA+ 80x25
>>> Feb 27 20:49:43 kuza kernel: Dentry cache hash table entries: 32768
>>> (order: 5, 131072 bytes)
>>> Feb 27 20:49:43 kuza kernel: Inode-cache hash table entries: 16384
>>> (order: 4, 65536 bytes)
>>> Feb 27 20:49:43 kuza kernel: Memory: 254596k/262064k available (2091k
>>> kernel code, 6828k reserved, 845k data, 232k init, 0k highmem)
>>> Feb 27 20:49:43 kuza kernel: virtual kernel memory layout:
>>> Feb 27 20:49:43 kuza kernel:     fixmap  : 0xfff9b000 - 0xfffff000   (
>>> 400 kB)
>>> Feb 27 20:49:43 kuza kernel:     pkmap   : 0xff800000 - 0xffc00000
>>> (4096 kB)
>>> Feb 27 20:49:43 kuza kernel:     vmalloc : 0xd0800000 - 0xff7fe000   (
>>> 751 MB)
>>> Feb 27 20:49:43 kuza kernel:     lowmem  : 0xc0000000 - 0xcffec000   (
>>> 255 MB)
>>> Feb 27 20:49:43 kuza kernel:       .init : 0xc06e0000 - 0xc071a000   (
>>> 232 kB)
>>> Feb 27 20:49:43 kuza kernel:       .data : 0xc060aefd - 0xc06de614   (
>>> 845 kB)
>>> Feb 27 20:49:43 kuza kernel:       .text : 0xc0400000 - 0xc060aefd
>>> (2091 kB)
>>> Feb 27 20:49:43 kuza kernel: Checking if this processor honours the WP
>>> bit even in supervisor mode... Ok.
>>> Feb 27 20:49:43 kuza kernel: Calibrating delay using timer specific
>>> routine.. 1616.55 BogoMIPS (lpj=808275)
>>> Feb 27 20:49:43 kuza kernel: Security Framework v1.0.0 initialized
>>> Feb 27 20:49:43 kuza kernel: SELinux:  Initializing.
>>> Feb 27 20:49:43 kuza kernel: SELinux:  Starting in permissive mode
>>> Feb 27 20:49:43 kuza kernel: selinux_register_security:  Registering
>>> secondary module capability
>>> Feb 27 20:49:43 kuza kernel: Capability LSM initialized as secondary
>>> Feb 27 20:49:43 kuza kernel: Mount-cache hash table entries: 512
>>> Feb 27 20:49:43 kuza kernel: CPU: L1 I Cache: 64K (64 bytes/line), D
>>> cache 64K (64 bytes/line)
>>> Feb 27 20:49:43 kuza kernel: CPU: L2 Cache: 64K (64 bytes/line)
>>> Feb 27 20:49:43 kuza kernel: Intel machine check architecture supported.
>>> Feb 27 20:49:43 kuza kernel: Intel machine check reporting enabled on
>>> CPU#0.
>>> Feb 27 20:49:43 kuza kernel: CPU: AMD Duron(tm) Processor stepping 01
>>> Feb 27 20:49:43 kuza kernel: Checking 'hlt' instruction... OK.
>>> Feb 27 20:49:43 kuza kernel: ACPI: Core revision 20060707
>>> Feb 27 20:49:43 kuza kernel: ACPI: setting ELCR to 0200 (from 0e20)
>>> Feb 27 20:49:43 kuza kernel: NET: Registered protocol family 16
>>> Feb 27 20:49:43 kuza kernel: ACPI: bus type pci registered
>>> Feb 27 20:49:43 kuza kernel: PCI: PCI BIOS revision 2.10 entry at
>>> 0xf1170, last bus=1
>>> Feb 27 20:49:43 kuza kernel: PCI: Using configuration type 1
>>> Feb 27 20:49:43 kuza kernel: Setting up standard PCI resources
>>> Feb 27 20:49:43 kuza kernel: ACPI: Interpreter enabled
>>> Feb 27 20:49:43 kuza kernel: ACPI: Using PIC for interrupt routing
>>> Feb 27 20:49:43 kuza kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5
>>> 6 7 9 10 *11 12 14 15)
>>> Feb 27 20:49:43 kuza kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5
>>> 6 7 9 10 11 12 14 15) *0, disabled.
>>> Feb 27 20:49:43 kuza kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5
>>> 6 7 9 *10 11 12 14 15)
>>> Feb 27 20:49:43 kuza kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5
>>> 6 7 9 10 11 12 14 15) *0, disabled.
>>> Feb 27 20:49:43 kuza kernel: ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4
>>> *5 6 7 9 10 11 12 14 15)
>>> Feb 27 20:49:43 kuza kernel: ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5
>>> 6 7 9 10 11 12 14 15) *0, disabled.
>>> Feb 27 20:49:43 kuza kernel: ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5
>>> 6 7 9 10 11 12 14 15) *0, disabled.
>>> Feb 27 20:49:43 kuza kernel: ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5
>>> 6 7 9 10 11 12 14 15) *0, disabled.
>>> Feb 27 20:49:43 kuza kernel: ACPI: PCI Interrupt Link [LNKI] (IRQs 3 4 5
>>> 6 7 *9 10 11 12 14 15)
>>> Feb 27 20:49:43 kuza kernel: ACPI: PCI Root Bridge [PCI0] (0000:00)
>>> Feb 27 20:49:43 kuza kernel: ACPI: Assume root bridge [\_SB_.PCI0] bus
>>> is 0
>>> Feb 27 20:49:43 kuza kernel: PCI quirk: region e400-e43f claimed by
>>> ali7101 ACPI
>>> Feb 27 20:49:43 kuza kernel: PCI quirk: region e800-e81f claimed by
>>> ali7101 SMB
>>> Feb 27 20:49:43 kuza kernel: Linux Plug and Play Support v0.97 (c) Adam
>>> Belay
>>> Feb 27 20:49:43 kuza kernel: pnp: PnP ACPI init
>>> Feb 27 20:49:43 kuza kernel: pnp: PnP ACPI: found 15 devices
>>> Feb 27 20:49:43 kuza kernel: usbcore: registered new interface driver
>>> usbfs
>>> Feb 27 20:49:43 kuza kernel: usbcore: registered new interface driver
>>> hub
>>> Feb 27 20:49:43 kuza kernel: usbcore: registered new device driver usb
>>> Feb 27 20:49:43 kuza kernel: PCI: Using ACPI for IRQ routing
>>> Feb 27 20:49:43 kuza kernel: PCI: If a device doesn't work, try
>>> "pci=routeirq".  If it helps, post a report
>>> Feb 27 20:49:43 kuza kernel: NetLabel: Initializing
>>> Feb 27 20:49:43 kuza kernel: NetLabel:  domain hash size = 128
>>> Feb 27 20:49:43 kuza kernel: NetLabel:  protocols = UNLABELED CIPSOv4
>>> Feb 27 20:49:43 kuza kernel: NetLabel:  unlabeled traffic allowed by
>>> default
>>> Feb 27 20:49:43 kuza kernel: pnp: 00:02: ioport range 0xe400-0xe47f
>>> could not be reserved
>>> Feb 27 20:49:43 kuza kernel: pnp: 00:02: ioport range 0xe800-0xe81f has
>>> been reserved
>>> Feb 27 20:49:43 kuza kernel: pnp: 00:02: ioport range 0x40b-0x40b has
>>> been reserved
>>> Feb 27 20:49:43 kuza kernel: pnp: 00:02: ioport range 0x480-0x48f has
>>> been reserved
>>> Feb 27 20:49:43 kuza kernel: pnp: 00:02: ioport range 0x4d6-0x4d6 has
>>> been reserved
>>> Feb 27 20:49:43 kuza kernel: PCI: Bridge: 0000:00:01.0
>>> Feb 27 20:49:43 kuza kernel:   IO window: disabled.
>>> Feb 27 20:49:43 kuza kernel:   MEM window: ec000000-edefffff
>>> Feb 27 20:49:43 kuza kernel:   PREFETCH window: edf00000-efffffff
>>> Feb 27 20:49:43 kuza kernel: NET: Registered protocol family 2
>>> Feb 27 20:49:43 kuza kernel: IP route cache hash table entries: 2048
>>> (order: 1, 8192 bytes)
>>> Feb 27 20:49:43 kuza kernel: TCP established hash table entries: 8192
>>> (order: 5, 131072 bytes)
>>> Feb 27 20:49:43 kuza kernel: TCP bind hash table entries: 4096 (order:
>>> 4, 81920 bytes)
>>> Feb 27 20:49:43 kuza kernel: TCP: Hash tables configured (established
>>> 8192 bind 4096)
>>> Feb 27 20:49:43 kuza kernel: TCP reno registered
>>> Feb 27 20:49:43 kuza kernel: checking if image is initramfs... it is
>>> Feb 27 20:49:43 kuza kernel: Freeing initrd memory: 913k freed
>>> Feb 27 20:49:43 kuza kernel: Simple Boot Flag at 0x3a set to 0x1
>>> Feb 27 20:49:43 kuza kernel: apm: BIOS version 1.2 Flags 0x0b (Driver
>>> version 1.16ac)
>>> Feb 27 20:49:43 kuza kernel: apm: overridden by ACPI.
>>> Feb 27 20:49:43 kuza kernel: audit: initializing netlink socket
>>> (disabled)
>>> Feb 27 20:49:43 kuza kernel: audit(1330375714.653:1): initialized
>>> Feb 27 20:49:43 kuza kernel: Total HugeTLB memory allocated, 0
>>> Feb 27 20:49:43 kuza kernel: VFS: Disk quotas dquot_6.5.1
>>> Feb 27 20:49:43 kuza kernel: Dquot-cache hash table entries: 1024 (order
>>> 0, 4096 bytes)
>>> Feb 27 20:49:43 kuza kernel: SELinux:  Registering netfilter hooks
>>> Feb 27 20:49:43 kuza kernel: ksign: Installing public key data
>>> Feb 27 20:49:43 kuza kernel: Loading keyring
>>> Feb 27 20:49:43 kuza kernel: - Added public key FA1AD44A9013A628
>>> Feb 27 20:49:43 kuza kernel: - User ID: Red Hat, Inc. (Kernel Module GPG
>>> key)
>>> Feb 27 20:49:43 kuza kernel: io scheduler noop registered
>>> Feb 27 20:49:43 kuza kernel: io scheduler anticipatory registered
>>> Feb 27 20:49:43 kuza kernel: io scheduler deadline registered
>>> Feb 27 20:49:43 kuza kernel: io scheduler cfq registered (default)
>>> Feb 27 20:49:43 kuza kernel: Limiting direct PCI/PCI transfers.
>>> Feb 27 20:49:43 kuza kernel: Activating ISA DMA hang workarounds.
>>> Feb 27 20:49:43 kuza kernel: pci_hotplug: PCI Hot Plug PCI Core
>>> version: 0.5
>>> Feb 27 20:49:43 kuza kernel: ACPI: Invalid PBLK length [5]
>>> Feb 27 20:49:43 kuza kernel: isapnp: Scanning for PnP cards...
>>> Feb 27 20:49:43 kuza kernel: isapnp: No Plug&   Play device found
>>> Feb 27 20:49:43 kuza kernel: Real Time Clock Driver v1.12ac
>>> Feb 27 20:49:43 kuza kernel: Non-volatile memory driver v1.2
>>> Feb 27 20:49:43 kuza kernel: Linux agpgart interface v0.101 (c) Dave
>>> Jones
>>> Feb 27 20:49:43 kuza kernel: agpgart: Detected ALi M1647 chipset
>>> Feb 27 20:49:43 kuza kernel: agpgart: AGP aperture is 128M @ 0xf0000000
>>> Feb 27 20:49:43 kuza kernel: Serial: 8250/16550 driver $Revision: 1.90 $
>>> 4 ports, IRQ sharing enabled
>>> Feb 27 20:49:43 kuza kernel: serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is
>>> a 16550A
>>> Feb 27 20:49:43 kuza kernel: serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is
>>> a 16550A
>>> Feb 27 20:49:43 kuza kernel: 00:0b: ttyS0 at I/O 0x3f8 (irq = 4) is a
>>> 16550A
>>> Feb 27 20:49:43 kuza kernel: 00:0c: ttyS1 at I/O 0x2f8 (irq = 3) is a
>>> 16550A
>>> Feb 27 20:49:43 kuza kernel: RAMDISK driver initialized: 16 RAM disks of
>>> 16384K size 4096 blocksize
>>> Feb 27 20:49:43 kuza kernel: input: Macintosh mouse button emulation as
>>> /class/input/input0
>>> Feb 27 20:49:43 kuza kernel: Uniform Multi-Platform E-IDE driver
>>> Revision: 7.00alpha2
>>> Feb 27 20:49:43 kuza kernel: ide: Assuming 33MHz system bus speed for
>>> PIO modes; override with idebus=xx
>>> Feb 27 20:49:43 kuza kernel: ALI15X3: IDE controller at PCI slot
>>> 0000:00:04.0
>>> Feb 27 20:49:43 kuza kernel: ACPI: Unable to derive IRQ for device
>>> 0000:00:04.0
>>> Feb 27 20:49:43 kuza kernel: ACPI: PCI Interrupt 0000:00:04.0[A]: no GSI
>>> Feb 27 20:49:43 kuza kernel: ALI15X3: chipset revision 196
>>> Feb 27 20:49:43 kuza kernel: ALI15X3: not 100% native mode: will probe
>>> irqs later
>>> Feb 27 20:49:43 kuza kernel:     ide0: BM-DMA at 0xd400-0xd407, BIOS
>>> settings: hda:DMA, hdb:DMA
>>> Feb 27 20:49:43 kuza kernel:     ide1: BM-DMA at 0xd408-0xd40f, BIOS
>>> settings: hdc:DMA, hdd:pio
>>> Feb 27 20:49:43 kuza kernel: hda: Maxtor 4D040H2, ATA DISK drive
>>> Feb 27 20:49:43 kuza kernel: hdb: ST3120814A, ATA DISK drive
>>> Feb 27 20:49:43 kuza kernel: hda: hw_config=603b
>>> Feb 27 20:49:43 kuza kernel: hda: hw_config=603b
>>> Feb 27 20:49:43 kuza kernel: hdb: hw_config=6d00
>>> Feb 27 20:49:43 kuza kernel: hdb: hw_config=6d00
>>> Feb 27 20:49:43 kuza kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
>>> Feb 27 20:49:49 kuza kernel: hdc: MATSHITA CR-583, ATAPI CD/DVD-ROM
>>> drive
>>> Feb 27 20:49:49 kuza rpc.statd[1535]: Version 1.0.8 Starting
>>> Feb 27 20:49:49 kuza kernel: hdd: no response (status = 0xa1), resetting
>>> drive
>>> Feb 27 20:49:49 kuza kernel: hdd: no response (status = 0xa1)
>>> Feb 27 20:49:49 kuza kernel: ide1 at 0x170-0x177,0x376 on irq 15
>>> Feb 27 20:49:49 kuza kernel: hda: max request size: 128KiB
>>> Feb 27 20:49:49 kuza kernel: hda: 80043264 sectors (40982 MB) w/2048KiB
>>> Cache, CHS=65535/16/63<6>hda: hw_config=603b
>>> Feb 27 20:49:49 kuza kernel: , UDMA(100)
>>> Feb 27 20:49:49 kuza kernel: hda: cache flushes not supported
>>> Feb 27 20:49:49 kuza kernel:  hda: hda1 hda2 hda3 hda4<   hda5>
>>> Feb 27 20:49:49 kuza kernel: hdb: max request size: 128KiB
>>> Feb 27 20:49:49 kuza kernel: hdb: 234441648 sectors (120034 MB)
>>> w/8192KiB Cache, CHS=16383/255/63<6>hdb: hw_config=6d00
>>> Feb 27 20:49:49 kuza kernel: , UDMA(100)
>>> Feb 27 20:49:49 kuza kernel: hdb: cache flushes supported
>>> Feb 27 20:49:49 kuza kernel:  hdb: hdb1
>>> Feb 27 20:49:49 kuza kernel: ide-floppy driver 0.99.newide
>>> Feb 27 20:49:49 kuza kernel: usbcore: registered new interface driver
>>> libusual
>>> Feb 27 20:49:49 kuza kernel: usbcore: registered new interface driver
>>> hiddev
>>> Feb 27 20:49:49 kuza kernel: usbcore: registered new interface driver
>>> usbhid
>>> Feb 27 20:49:49 kuza kernel: drivers/usb/input/hid-core.c: v2.6:USB HID
>>> core driver
>>> Feb 27 20:49:49 kuza kernel: PNP: PS/2 Controller
>>> [PNP0303:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,12
>>> Feb 27 20:49:49 kuza kernel: serio: i8042 KBD port at 0x60,0x64 irq 1
>>> Feb 27 20:49:49 kuza kernel: serio: i8042 AUX port at 0x60,0x64 irq 12
>>> Feb 27 20:49:49 kuza kernel: mice: PS/2 mouse device common for all mice
>>> Feb 27 20:49:49 kuza kernel: input: AT Translated Set 2 keyboard as
>>> /class/input/input1
>>> Feb 27 20:49:49 kuza kernel: TCP bic registered
>>> Feb 27 20:49:49 kuza kernel: Initializing XFRM netlink socket
>>> Feb 27 20:49:49 kuza kernel: NET: Registered protocol family 1
>>> Feb 27 20:49:49 kuza kernel: NET: Registered protocol family 17
>>> Feb 27 20:49:49 kuza kernel: powernow-k8: Processor cpuid 631 not
>>> supported
>>> Feb 27 20:49:49 kuza kernel: Using IPI Shortcut mode
>>> Feb 27 20:49:49 kuza kernel: Time: tsc clocksource has been installed.
>>> Feb 27 20:49:49 kuza kernel: ACPI: (supports S0 S1 S4 S5)
>>> Feb 27 20:49:49 kuza kernel: Freeing unused kernel memory: 232k freed
>>> Feb 27 20:49:49 kuza kernel: Write protecting the kernel read-only data:
>>> 585k
>>> Feb 27 20:49:49 kuza kernel: input: ImPS/2 Generic Wheel Mouse as
>>> /class/input/input2
>>> Feb 27 20:49:49 kuza kernel: EXT3-fs: INFO: recovery required on
>>> readonly filesystem.
>>> Feb 27 20:49:49 kuza kernel: EXT3-fs: write access will be enabled
>>> during recovery.
>>> Feb 27 20:49:49 kuza kernel: kjournald starting.  Commit interval 5
>>> seconds
>>> Feb 27 20:49:49 kuza kernel: EXT3-fs: recovery complete.
>>> Feb 27 20:49:49 kuza kernel: EXT3-fs: mounted filesystem with ordered
>>> data mode.
>>> Feb 27 20:49:49 kuza kernel: SELinux:  Disabled at runtime.
>>> Feb 27 20:49:49 kuza kernel: SELinux:  Unregistering netfilter hooks
>>> Feb 27 20:49:49 kuza kernel: audit(1330375739.875:2): selinux=0
>>> auid=4294967295
>>> Feb 27 20:49:49 kuza kernel: alim7101_wdt: Steve
>>> Hill<steve at navaho.co.uk>.
>>> Feb 27 20:49:49 kuza kernel: alim7101_wdt: Detected old alim7101
>>> revision 'a1d'.  If this is a cobalt board, set the 'use_gpio' module
>>> parameter.
>>> Feb 27 20:49:49 kuza kernel: input: PC Speaker as /class/input/input3
>>> Feb 27 20:49:49 kuza kernel: hdc: ATAPI 8X CD-ROM drive, 128kB Cache,
>>> DMA
>>> Feb 27 20:49:49 kuza kernel: Uniform CD-ROM driver Revision: 3.20
>>> Feb 27 20:49:49 kuza kernel: 8139too Fast Ethernet driver 0.9.28
>>> Feb 27 20:49:49 kuza kernel: ACPI: PCI Interrupt Link [LNKC] enabled at
>>> IRQ 10
>>> Feb 27 20:49:49 kuza kernel: ACPI: PCI Interrupt 0000:00:0a.0[A] ->
>>> Link
>>> [LNKC] ->   GSI 10 (level, low) ->   IRQ 10
>>> Feb 27 20:49:49 kuza kernel: eth0: RealTek RTL8139 at 0xd081e000,
>>> 00:50:ba:5f:e4:c3, IRQ 10
>>> Feb 27 20:49:49 kuza kernel: Floppy drive(s): fd0 is 1.44M
>>> Feb 27 20:49:49 kuza kernel: FDC 0 is a post-1991 82077
>>> Feb 27 20:49:49 kuza kernel: ACPI: PCI Interrupt Link [LNKI] enabled at
>>> IRQ 9
>>> Feb 27 20:49:49 kuza kernel: ACPI: PCI Interrupt 0000:00:02.0[A] ->
>>> Link
>>> [LNKI] ->   GSI 9 (level, low) ->   IRQ 9
>>> Feb 27 20:49:49 kuza kernel: ohci_hcd 0000:00:02.0: OHCI Host Controller
>>> Feb 27 20:49:49 kuza kernel: ohci_hcd 0000:00:02.0: new USB bus
>>> registered, assigned bus number 1
>>> Feb 27 20:49:49 kuza kernel: ohci_hcd 0000:00:02.0: irq 9, io mem
>>> 0xeb800000
>>> Feb 27 20:49:49 kuza kernel: usb usb1: configuration #1 chosen from 1
>>> choice
>>> Feb 27 20:49:49 kuza kernel: hub 1-0:1.0: USB hub found
>>> Feb 27 20:49:49 kuza kernel: hub 1-0:1.0: 4 ports detected
>>> Feb 27 20:49:49 kuza kernel: ACPI: PCI Interrupt Link [LNKE] enabled at
>>> IRQ 5
>>> Feb 27 20:49:49 kuza kernel: ACPI: PCI Interrupt 0000:00:06.0[A] ->
>>> Link
>>> [LNKE] ->   GSI 5 (level, low) ->   IRQ 5
>>> Feb 27 20:49:49 kuza kernel: ohci_hcd 0000:00:06.0: OHCI Host Controller
>>> Feb 27 20:49:49 kuza kernel: ohci_hcd 0000:00:06.0: new USB bus
>>> registered, assigned bus number 2
>>> Feb 27 20:49:49 kuza kernel: ohci_hcd 0000:00:06.0: irq 5, io mem
>>> 0xea800000
>>> Feb 27 20:49:49 kuza kernel: usb usb2: configuration #1 chosen from 1
>>> choice
>>> Feb 27 20:49:49 kuza kernel: hub 2-0:1.0: USB hub found
>>> Feb 27 20:49:49 kuza kernel: hub 2-0:1.0: 2 ports detected
>>> Feb 27 20:49:49 kuza kernel: usb 1-1: new low speed USB device using
>>> ohci_hcd and address 2
>>> Feb 27 20:49:49 kuza kernel: usb 1-1: configuration #1 chosen from 1
>>> choice
>>> Feb 27 20:49:49 kuza kernel: parport: PnPBIOS parport detected.
>>> Feb 27 20:49:49 kuza kernel: parport0: PC-style at 0x378 (0x778), irq 7
>>> [PCSPP,TRISTATE]
>>> Feb 27 20:49:49 kuza kernel: lp0: using parport0 (interrupt-driven).
>>> Feb 27 20:49:49 kuza kernel: lp0: console ready
>>> Feb 27 20:49:49 kuza kernel: hiddev96: USB HID v1.10 Device [American
>>> Power Conversion Back-UPS XS 1300 LCD FW:836.H5 .D USB FW:H5 ] on
>>> usb-0000:00:02.0-1
>>> Feb 27 20:49:49 kuza kernel: NET: Registered protocol family 10
>>> Feb 27 20:49:49 kuza kernel: lo: Disabled Privacy Extensions
>>> Feb 27 20:49:49 kuza kernel: Mobile IPv6
>>> Feb 27 20:49:49 kuza kernel: input: Power Button (FF) as
>>> /class/input/input4
>>> Feb 27 20:49:49 kuza kernel: ACPI: Power Button (FF) [PWRF]
>>> Feb 27 20:49:49 kuza kernel: input: Power Button (CM) as
>>> /class/input/input5
>>> Feb 27 20:49:49 kuza kernel: ACPI: Power Button (CM) [PWRB]
>>> Feb 27 20:49:49 kuza kernel: No dock devices found.
>>> Feb 27 20:49:49 kuza kernel: ibm_acpi: ec object not found
>>> Feb 27 20:49:49 kuza kernel: md: Autodetecting RAID arrays.
>>> Feb 27 20:49:49 kuza kernel: md: autorun ...
>>> Feb 27 20:49:49 kuza kernel: md: ... autorun DONE.
>>> Feb 27 20:49:49 kuza kernel: device-mapper: ioctl: 4.11.0-ioctl
>>> (2006-10-12) initialised: dm-devel at redhat.com
>>> Feb 27 20:49:49 kuza kernel: EXT3 FS on hda5, internal journal
>>> Feb 27 20:49:49 kuza kernel: kjournald starting.  Commit interval 5
>>> seconds
>>> Feb 27 20:49:49 kuza kernel: EXT3 FS on hda1, internal journal
>>> Feb 27 20:49:49 kuza kernel: EXT3-fs: mounted filesystem with ordered
>>> data mode.
>>> Feb 27 20:49:49 kuza kernel: kjournald starting.  Commit interval 5
>>> seconds
>>> Feb 27 20:49:49 kuza kernel: EXT3 FS on hdb1, internal journal
>>> Feb 27 20:49:50 kuza kernel: EXT3-fs: mounted filesystem with ordered
>>> data mode.
>>> Feb 27 20:49:50 kuza kernel: kjournald starting.  Commit interval 5
>>> seconds
>>> Feb 27 20:49:50 kuza kernel: EXT3 FS on hda2, internal journal
>>> Feb 27 20:49:50 kuza kernel: EXT3-fs: mounted filesystem with ordered
>>> data mode.
>>> Feb 27 20:49:50 kuza kernel: Adding 514072k swap on /dev/hda3.
>>> Priority:-1 extents:1 across:514072k
>>> Feb 27 20:49:50 kuza kernel: eth0: link up, 100Mbps, full-duplex, lpa
>>> 0x45E1
>>> Feb 27 20:49:53 kuza kernel: Bluetooth: Core ver 2.11
>>> Feb 27 20:49:53 kuza kernel: NET: Registered protocol family 31
>>> Feb 27 20:49:53 kuza kernel: Bluetooth: HCI device and connection
>>> manager initialized
>>> Feb 27 20:49:53 kuza kernel: Bluetooth: HCI socket layer initialized
>>> Feb 27 20:49:53 kuza kernel: Bluetooth: L2CAP ver 2.8
>>> Feb 27 20:49:53 kuza kernel: Bluetooth: L2CAP socket layer initialized
>>> Feb 27 20:49:53 kuza kernel: Bluetooth: HIDP (Human Interface Emulation)
>>> ver 1.1
>>> Feb 27 20:49:53 kuza hidd[1621]: Bluetooth HID daemon
>>> Feb 27 20:49:56 kuza smartd[1719]: smartd version 5.36
>>> [i686-redhat-linux-gnu] Copyright (C) 2002-6 Bruce Allen
>>> Feb 27 20:49:56 kuza smartd[1719]: Home page is
>>> http://smartmontools.sourceforge.net/
>>> Feb 27 20:49:56 kuza smartd[1719]: Opened configuration file
>>> /etc/smartd.conf
>>> Feb 27 20:49:56 kuza smartd[1719]: Configuration file /etc/smartd.conf
>>> parsed.
>>> Feb 27 20:49:56 kuza smartd[1719]: Device: /dev/hda, opened
>>> Feb 27 20:49:56 kuza smartd[1719]: Device: /dev/hda, found in smartd
>>> database.
>>> Feb 27 20:49:57 kuza smartd[1719]: Device: /dev/hda, is SMART capable.
>>> Adding to "monitor" list.
>>> Feb 27 20:49:57 kuza smartd[1719]: Device: /dev/hdb, opened
>>> Feb 27 20:49:57 kuza smartd[1719]: Device: /dev/hdb, not found in smartd
>>> database.
>>> Feb 27 20:49:58 kuza smartd[1719]: Device: /dev/hdb, is SMART capable.
>>> Adding to "monitor" list.
>>> Feb 27 20:49:58 kuza smartd[1719]: Monitoring 2 ATA and 0 SCSI devices
>>> Feb 27 20:49:59 kuza smartd[1724]: smartd has fork()ed into background
>>> mode. New PID=1724.
>>> Feb 27 20:49:59 kuza hpiod: 1.6.6a accepting connections at 50000...
>>> Feb 27 20:50:06 kuza xinetd[1770]: xinetd Version 2.3.13 started with
>>> libwrap loadavg options compiled in.
>>> Feb 27 20:50:06 kuza xinetd[1770]: Started working: 1 available service
>>> Feb 27 20:50:06 kuza exportfs[1803]: No host name given with /data
>>> (sync,rw), suggest *(sync,rw) to avoid warning
>>> Feb 27 20:50:06 kuza apcupsd[1789]: apcupsd 3.12.4 (19 August 2006)
>>> redhat startup succeeded
>>> Feb 27 20:50:06 kuza apcupsd[1789]: NIS server startup succeeded
>>> Feb 27 20:50:07 kuza kernel: Installing knfsd (copyright (C) 1996
>>> okir at monad.swb.de).
>>> Feb 27 20:50:07 kuza kernel: NFSD: Using /var/lib/nfs/v4recovery as the
>>> NFSv4 state recovery directory
>>> Feb 27 20:50:07 kuza kernel: NFSD: starting 90-second grace period
>>> Feb 27 20:50:08 kuza gpm[1855]: *** info [startup.c(95)]:
>>> Feb 27 20:50:08 kuza gpm[1855]: Started gpm successfully. Entered daemon
>>> mode.
>>> Feb 27 20:50:20 kuza avahi-daemon[2009]: Found user 'avahi' (UID 70) and
>>> group 'avahi' (GID 70).
>>> Feb 27 20:50:20 kuza avahi-daemon[2009]: Successfully dropped root
>>> privileges.
>>> Feb 27 20:50:20 kuza avahi-daemon[2009]: avahi-daemon 0.6.11 starting
>>> up.
>>> Feb 27 20:50:20 kuza avahi-daemon[2009]: WARNING: No NSS support for
>>> mDNS detected, consider installing nss-mdns!
>>> Feb 27 20:50:21 kuza avahi-daemon[2009]: Successfully called chroot().
>>> Feb 27 20:50:21 kuza avahi-daemon[2009]: Successfully dropped remaining
>>> capabilities.
>>> Feb 27 20:50:21 kuza avahi-daemon[2009]: No service found in
>>> /etc/avahi/services.
>>> Feb 27 20:50:21 kuza avahi-daemon[2009]: New relevant interface
>>> eth0.IPv6 for mDNS.
>>> Feb 27 20:50:21 kuza avahi-daemon[2009]: Joining mDNS multicast group on
>>> interface eth0.IPv6 with address fe80::250:baff:fe5f:e4c3.
>>> Feb 27 20:50:21 kuza avahi-daemon[2009]: New relevant interface
>>> eth0.IPv4 for mDNS.
>>> Feb 27 20:50:21 kuza avahi-daemon[2009]: Joining mDNS multicast group on
>>> interface eth0.IPv4 with address 192.168.1.3.
>>> Feb 27 20:50:21 kuza avahi-daemon[2009]: Network interface enumeration
>>> completed.
>>> Feb 27 20:50:21 kuza avahi-daemon[2009]: Registering new address record
>>> for fe80::250:baff:fe5f:e4c3 on eth0.
>>> Feb 27 20:50:21 kuza avahi-daemon[2009]: Registering new address record
>>> for 192.168.1.3 on eth0.
>>> Feb 27 20:50:21 kuza avahi-daemon[2009]: Registering HINFO record with
>>> values 'I686'/'LINUX'.
>>> Feb 27 20:50:21 kuza avahi-daemon[2009]: Server startup complete. Host
>>> name is kuza.local. Local service cookie is 2874978490.
>>> Feb 27 20:56:06 kuza nmbd[1930]: [2012/02/27 20:56:06, 0]
>>> nmbd/nmbd_become_lmb.c:become_local_master_stage2(396)
>>> Feb 27 20:56:06 kuza nmbd[1930]:   *****
>>> Feb 27 20:56:06 kuza nmbd[1930]:
>>> Feb 27 20:56:06 kuza nmbd[1930]:   Samba name server KUZA is now a local
>>> master browser for workgroup WORKGROUP on subnet 192.168.1.3
>>> Feb 27 20:56:06 kuza nmbd[1930]:
>>> Feb 27 20:56:06 kuza nmbd[1930]:   *****
>>> _______________________________________________
>>> mdlug mailing list
>>> mdlug at mdlug.org
>>> http://mdlug.org/mailman/listinfo/mdlug
>>
>> _______________________________________________
>> mdlug mailing list
>> mdlug at mdlug.org
>> http://mdlug.org/mailman/listinfo/mdlug
>
> _______________________________________________
> mdlug mailing list
> mdlug at mdlug.org
> http://mdlug.org/mailman/listinfo/mdlug


From billings at negate.org  Wed Feb 29 09:53:05 2012
From: billings at negate.org (Jonathan Billings)
Date: Wed, 29 Feb 2012 09:53:05 -0500
Subject: [mdlug] hanging machine kernel panic - on going
In-Reply-To: <CB72AC79.1F1D0%gregwojtak@quickenloans.com>
References: <4F4CF6FB.4070607@gmail.com>
	<CB72AC79.1F1D0%gregwojtak@quickenloans.com>
Message-ID: <20120229145305.GA3109@caen-gx755.engin.umich.edu>

On Tue, Feb 28, 2012 at 09:08:20PM +0000, Wojtak, Greg (Superfly) wrote:
>
> If you're feeling really ambitious you could make sure that the kdump
> system is configured, grab the kernel dump, and run gdb on it...

The 'crash' utility (http://people.redhat.com/anderson/) actually
makes analyzing kernel kdumps a bit easier, and it uses gdb for parts
of it, but you can also get a lot of kernel-specific information as
well.  I know I've used it to find out what users were logged on to a
multi-user system that kept crashing, for example.

-- 
Jonathan Billings <billings at negate.org>

From Raymond.Ingles at compuware.com  Wed Feb 29 09:58:13 2012
From: Raymond.Ingles at compuware.com (Ingles, Raymond)
Date: Wed, 29 Feb 2012 09:58:13 -0500
Subject: [mdlug] hanging machine kernel panic - on going
In-Reply-To: <4F4DEA2C.8050202@gmail.com>
References: <CB72AC79.1F1D0%gregwojtak@quickenloans.com>
	<4F4DEA2C.8050202@gmail.com>
Message-ID: <50F4BFBDC6001340B94E13C70E39F9B0017DC016@nasa-dtw-ex004.nasa.cpwr.corp>

> From: Aaron Kulkis
> I won't bore you with the details,
> other than to say that there are 8, 16, 32 (and now 64)-bit
> versions of four registers A, B, C, and D (which Intel intended
> to stand for Accumulator, Base, Code, and Data), but which,
> other than the A registers, seem to be used rather inconsistently.

Yeah, the x86 instruction set is famously non-orthogonal. Instructions
can and do affect each other in awkward ways.

Even more silly, 'under the hood' it's all translated into a
more-or-less RISC format for actual execution. In a sense, *everything*
on an x86 runs as a 'virtual machine'. :-/

 Sincerely,

 Ray Ingles                                    (313) 227-2317

 "Any technology distinguishable from magic is insufficiently
         advanced." - Anonymous' restatement of Clarke

http://www.compuware.com/
The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.


From akulkis00 at gmail.com  Wed Feb 29 14:41:08 2012
From: akulkis00 at gmail.com (Aaron Kulkis)
Date: Wed, 29 Feb 2012 14:41:08 -0500
Subject: [mdlug] hanging machine kernel panic - on going
In-Reply-To: <50F4BFBDC6001340B94E13C70E39F9B0017DC016@nasa-dtw-ex004.nasa.cpwr.corp>
References: <CB72AC79.1F1D0%gregwojtak@quickenloans.com>
	<4F4DEA2C.8050202@gmail.com>
	<50F4BFBDC6001340B94E13C70E39F9B0017DC016@nasa-dtw-ex004.nasa.cpwr.corp>
Message-ID: <4F4E7F54.8060007@gmail.com>

Ingles, Raymond wrote:
>> From: Aaron Kulkis
>> I won't bore you with the details,
>> other than to say that there are 8, 16, 32 (and now 64)-bit
>> versions of four registers A, B, C, and D (which Intel intended
>> to stand for Accumulator, Base, Code, and Data), but which,
>> other than the A registers, seem to be used rather inconsistently.
>
> Yeah, the x86 instruction set is famously non-orthogonal. Instructions
> can and do affect each other in awkward ways.

ah yes, the non-orthgonality, forgot about that one.


If you has ever programmed in VAX-11 assembly, you would probably
agree that the VAX-11 instruction set is

* Beautiful

* Elegant

* Masterful

* Sublime

* Wonderful to program in

* And totally WRONG :-(

[Primarily because it was possible for a single instruction
to produce as many as 13 page-faults, each time requiring that
the all register and memory changes be rolled back to the
contents before the instruction started executing]. A heavily
loaded VAX thrashes alot (swapping virtual memory pages in
and out) to the point where ~90% of CPU cycles are spent on
page-swapping activity and only ~10% running user code.
I cannot begin to express how painful it was to try to
do anything on a heavily loaded VAX.


It was the complete failure of the VAX to hold up well
in multi-user multi-tasking environments which led to the
development of Reduced Instruction Set Computer (RISC).

>
> Even more silly, 'under the hood' it's all translated into a
> more-or-less RISC format for actual execution. In a sense, *everything*
> on an x86 runs as a 'virtual machine'. :-/


It's such a shame that this pathetic architecture has
taken over the world :-(.  I'd rather that the dominant
architecture were something more like the 680x0 or
IBM 370 lines of CPUs (although I'm not familiar with
the Power CPU (IBM-designed microprocessor) line.

It was the complete failure of the VAX to hold up well
in multi-user multi-tasking environments which led to the
development of RISC.


>
>   Sincerely,
>
>   Ray Ingles                                    (313) 227-2317
>
>   "Any technology distinguishable from magic is insufficiently
>           advanced." - Anonymous' restatement of Clarke
>
> http://www.compuware.com/
> The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.
>