Ubuntu
linux package

  1. Bug #286285
  2. Comment #94

Comment 94 for bug 286285

Revision history for this message
Jakub Nowacki (j-s-nowacki) wrote : Re: [Bug 286285] Re: kernel 2.6.27-7-generic bug BUG: scheduling while atomic: swapper/0/0x00000100

The time of the lock up was on 16:06. As I said here is nothing in the
logs. Every aforementioned log have message:

Nov 10 16:06:31 newdumolap kernel: [ 1416.138732] Inbound IN=wlan0 OUT=
MAC= SRC=192.168.1.3 DST=239.192.152.143 LEN=147 TOS=0x00 PREC=0x00
TTL=1 ID=0 DF PROTO=UDP SPT=44287 DPT=6771 LEN=127
Nov 10 16:06:32 newdumolap kernel: [ 1417.146590] Inbound IN=wlan0 OUT=
MAC= SRC=192.168.1.3 DST=239.192.152.143 LEN=147 TOS=0x00 PREC=0x00
TTL=1 ID=0 DF PROTO=UDP SPT=44287 DPT=6771 LEN=127
Nov 10 16:06:36 newdumolap kernel: [ 1420.934073] Inbound IN=wlan0 OUT=
MAC=00:16:ea:d1:ba:c6:00:1e:2a:61:af:e8:08:00 SRC=79.173.31.87
DST=192.168.1.3 LEN=58 TOS=0x00 PREC=0x00 TTL=112 ID=18080 DF PROTO=TCP
SPT=33372 DPT=50557 WINDOW=16098 RES=0x00 ACK PSH URGP=0
Nov 10 16:06:44 newdumolap kernel: [ 1428.840973] Inbound IN=wlan0 OUT=
MAC=00:16:ea:d1:ba:c6:00:1e:2a:61:af:e8:08:00 SRC=79.173.31.87
DST=192.168.1.3 LEN=58 TOS=0x00 PREC=0x00 TTL=112 ID=18783 DF PROTO=TCP
SPT=33372 DPT=50557 WINDOW=16098 RES=0x00 ACK PSH URGP=0
Nov 10 16:06:54 newdumolap kernel: [ 1438.914986] Inbound IN=wlan0 OUT=
MAC=00:16:ea:d1:ba:c6:00:1e:2a:61:af:e8:08:00 SRC=75.157.153.91
DST=192.168.1.3 LEN=75 TOS=0x00 PREC=0x00 TTL=106 ID=12920 PROTO=UDP
SPT=7403 DPT=55575 LEN=55
Nov 10 16:06:54 newdumolap kernel: [ 1439.424686] Inbound IN=wlan0 OUT=
MAC=00:16:ea:d1:ba:c6:00:1e:2a:61:af:e8:08:00 SRC=85.217.178.210
DST=192.168.1.3 LEN=75 TOS=0x00 PREC=0x00 TTL=110 ID=57128 PROTO=UDP
SPT=17953 DPT=55575 LEN=55
Nov 10 16:08:01 newdumolap syslogd 1.5.0#2ubuntu6: restart.
Nov 10 16:08:01 newdumolap kernel: Inspecting
/boot/System.map-2.6.27-7-server
Nov 10 16:08:01 newdumolap kernel: Cannot find map file.
Nov 10 16:08:01 newdumolap kernel: Loaded 70900 symbols from 97 modules.
Nov 10 16:08:01 newdumolap kernel: [ 0.000000] Initializing cgroup
subsys cpuset
Nov 10 16:08:01 newdumolap kernel: [ 0.000000] Initializing cgroup
subsys cpu
Nov 10 16:08:01 newdumolap kernel: [ 0.000000] Linux version
2.6.27-7-server (buildd@palmer) (gcc version 4.3.2 (Ubuntu
4.3.2-1ubuntu11) ) #1 SMP Tue Nov 4 20:18:35 UTC 2008 (Ubuntu
2.6.27-7.16-server)
Nov 10 16:08:01 newdumolap kernel: [ 0.000000] BIOS-provided physical
RAM map:

So it just acts like normal reboot... Actually there were two lock ups
first was 15 min before and it looked exactly the same (in logs as
well). Both occured during high network activity.

Robb Topolski wrote:
> Jakub,
>
> What was the date/time when the system locked up? You'll want to check
> your logs matching up those times to help figure out why the kernel
> panicked.
>
> As to the printout you provided, those look like routine firewall logs.
> To get help with turning that off, see
> http://www.ubuntu.com/support/communitysupport for different ways to get
> help. If I had that logging problem and couldn't find the answer by
> searching, I might go to http://ubuntuforums.org/forumdisplay.php?f=336
> and ask.
>