[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#435308: marked as done (linux-image-2.6-amd64: kernel BUG at mm/rmap.c:522)

Your message dated Sun, 23 Nov 2008 21:56:51 +0100
with message-id <20081123205651.GD14306@galadriel.inutil.org>
and subject line Re: linux-image-2.6.18-5-686: kernel BUG at mm/rmap.c:522
has caused the Debian Bug report #427658,
regarding linux-image-2.6-amd64: kernel BUG at mm/rmap.c:522
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
427658: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=427658
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-image-2.6-amd64
Version: 2.6.18+6
Severity: normal


Jul 26 09:21:45 localhost kernel: Kernel BUG at mm/rmap.c:522
Jul 26 09:21:45 localhost kernel: invalid opcode: 0000 [1] SMP
Jul 26 09:21:45 localhost kernel: CPU 1
Jul 26 09:21:45 localhost kernel: Modules linked in: nls_iso8859_1 isofs udf ppdev lp button ac 
battery ip6table_filter ip6_tables iptable_raw xt_policy xt_multiport ipt_ULOG ipt_TTL ipt_ttl 
ipt_TOS ipt_tos ipt_TCPMSS ipt_SAME ipt_REJECT ipt_REDIRECT ipt_recent ipt_owner ipt_NETMAP 
ipt_MASQUERADE ipt_LOG ipt_iprange ipt_hashlimit ipt_ECN ipt_ecn ipt_DSCP ipt_dscp 
ipt_CLUSTERIP ipt_ah ipt_addrtype ip_nat_tftp ip_nat_snmp_basic ip_nat_pptp ip_nat_irc 
ip_nat_ftp ip_nat_amanda ip_conntrack_tftp ip_conntrack_pptp ip_conntrack_netbios_ns 
ip_conntrack_irc ip_conntrack_ftp ts_kmp ip_conntrack_amanda xt_tcpmss xt_pkttype xt_physdev 
bridge xt_NFQUEUE xt_MARK xt_mark xt_mac xt_limit xt_length xt_helper xt_dccp xt_conntrack 
xt_CONNMARK xt_connmark xt_CLASSIFY xt_tcpudp xt_state iptable_nat ip_nat ip_conntrack 
iptable_mangle nfnetlink iptable_filter ip_tables x_tables ipv6 dm_snapshot dm_mirror dm_mod 
it87 hwmon_vid i2c_isa eeprom sbp2 loop snd_hda_intel snd_hda_codec snd_pcm_oss snd_mixer_oss 
snd_pcm parport_pc snd_timer parp
Jul 26 09:21:45 localhost kernel: rt snd soundcore snd_page_alloc psmouse serio_raw pcspkr 
i2c_nforce2 i2c_core joydev tsdev evdev eth1394 ext3 jbd mbcache ide_cd cdrom usbhid sd_mod 
amd74xx generic ide_core 8139cp ohci1394 8139too ieee1394 mii forcedeth ohci_hcd ehci_hcd 
sata_nv libata scsi_mod thermal processor fan
Jul 26 09:21:45 localhost kernel: Pid: 24449, comm: floaters Not tainted 2.6.18-4-amd64 #1
Jul 26 09:21:45 localhost kernel: RIP: 0010:[<ffffffff8020aa18>]  [<ffffffff8020aa18>] 
page_remove_rmap+0x13/0x2c
Jul 26 09:21:45 localhost kernel: RSP: 0018:ffff810071d0fc30  EFLAGS: 00010286
Jul 26 09:21:45 localhost kernel: RAX: 00000000ffffffff RBX: ffff81007fbe1c40 RCX: 
000000000000003f
Jul 26 09:21:45 localhost kernel: RDX: 0000000000000001 RSI: 8000000072438067 RDI: 
ffff81007fbe1c40
Jul 26 09:21:45 localhost kernel: RBP: 0000000072438020 R08: 0000000077ef8020 R09: 
ffff81000000c400
Jul 26 09:21:45 localhost kernel: R10: 0000000000000000 R11: 0000000000000246 R12: 
0000000000807000
Jul 26 09:21:45 localhost kernel: R13: ffff81002d05d038 R14: ffff8100010182a0 R15: 
0000000000a00000
Jul 26 09:21:45 localhost kernel: FS:  00002afebec84aa0(0000) GS:ffff81007e2aaac0(0000) 
knlGS:0000000000000000
Jul 26 09:21:45 localhost kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
Jul 26 09:21:45 localhost kernel: CR2: 000000000051f960 CR3: 0000000000201000 CR4: 
00000000000006e0
Jul 26 09:21:45 localhost kernel: Process floaters (pid: 24449, threadinfo ffff810071d0e000, 
task ffff8100158b1080)
Jul 26 09:21:45 localhost kernel: Stack:  ffffffff80207a3f 0000000000000000 ffff810071d0fd08 
ffffffffffffffff
Jul 26 09:21:45 localhost kernel:  0000000000000000 ffff810076994a28 ffff810071d0fd10 
0000000000000000
Jul 26 09:21:45 localhost kernel:  000000018024206a 0000000000cc6000 ffff810070bcb000 
ffff810029fc0000
Jul 26 09:21:45 localhost kernel: Call Trace:
Jul 26 09:21:45 localhost kernel:  [<ffffffff80207a3f>] unmap_vmas+0x3f4/0x713
Jul 26 09:21:45 localhost kernel:  [<ffffffff80237c76>] exit_mmap+0x76/0xf1
Jul 26 09:21:45 localhost kernel:  [<ffffffff80239d2d>] mmput+0x28/0x98
Jul 26 09:21:45 localhost kernel:  [<ffffffff8021353d>] do_exit+0x220/0x8ae
Jul 26 09:21:45 localhost kernel:  [<ffffffff8024534d>] cpuset_exit+0x0/0x6c
Jul 26 09:21:45 localhost kernel:  [<ffffffff8022956f>] get_signal_to_deliver+0x46e/0x49d
Jul 26 09:21:45 localhost kernel:  [<ffffffff80227fd6>] do_signal+0x55/0x751
Jul 26 09:21:45 localhost kernel:  [<ffffffff802b9e4d>] do_readv_writev+0x271/0x294
Jul 26 09:21:45 localhost kernel:  [<ffffffff8025cc4e>] thread_return+0x0/0xe7
Jul 26 09:21:45 localhost kernel:  [<ffffffff80258a98>] retint_signal+0x3d/0x79
Jul 26 09:21:45 localhost kernel:
Jul 26 09:21:45 localhost kernel:
Jul 26 09:21:45 localhost kernel: Code: 0f 0b 68 3a a2 40 80 c2 0a 02 8b 77 18 83 f6 01 83 e6 
01 e9
Jul 26 09:21:45 localhost kernel: RIP  [<ffffffff8020aa18>] page_remove_rmap+0x13/0x2c
Jul 26 09:21:45 localhost kernel:  RSP <ffff810071d0fc30>
Jul 26 09:21:45 localhost kernel:  <1>Fixing recursive fault but reboot is needed!
Jul 26 09:23:17 localhost kernel: Bad page state in process 'Xvnc4'
Jul 26 09:23:17 localhost kernel: page:ffff81007fbe1c40 flags:0x0100000000000014 
mapping:0000000000000000 mapcount:-1 count:0
Jul 26 09:23:17 localhost kernel: Trying to fix it up, but a reboot is needed
Jul 26 09:23:17 localhost kernel: Backtrace:
Jul 26 09:23:17 localhost kernel:
Jul 26 09:23:17 localhost kernel: Call Trace:
Jul 26 09:23:17 localhost kernel:  [<ffffffff802a7b0c>] bad_page+0x4e/0x78
Jul 26 09:23:17 localhost kernel:  [<ffffffff80209f65>] get_page_from_freelist+0x26d/0x3a6
Jul 26 09:23:17 localhost kernel:  [<ffffffff8020de4a>] __alloc_pages+0x5c/0x2a9
Jul 26 09:23:17 localhost kernel:  [<ffffffff8020f3f9>] do_wp_page+0x1df/0x3ec
Jul 26 09:23:17 localhost kernel:  [<ffffffff80208c54>] __handle_mm_fault+0x8b1/0x91a
Jul 26 09:23:17 localhost kernel:  [<ffffffff8020a69c>] do_page_fault+0x39d/0x706
Jul 26 09:23:17 localhost kernel:  [<ffffffff8020d422>] do_mmap_pgoff+0x5da/0x72e
Jul 26 09:23:17 localhost kernel:  [<ffffffff8020b009>] vfs_read+0x13c/0x171
Jul 26 09:23:17 localhost kernel:  [<ffffffff802591a5>] error_exit+0x0/0x84
Jul 26 09:23:17 localhost kernel:


-- System Information:
Debian Release: 4.0
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'testing')
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-4-amd64
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

Versions of packages linux-image-2.6-amd64 depends on:
ii  linux-image-2.6.18 2.6.18.dfsg.1-12etch2 Linux 2.6.18 image on AMD64

linux-image-2.6-amd64 recommends no packages.

-- no debconf information

--- End Message ---
--- Begin Message --- 
On Sat, Nov 22, 2008 at 01:45:35PM -0200, Rodrigo Campos wrote:
> On Sat, Nov 22, 2008 at 11:21 AM, Moritz Muehlenhoff <jmm@inutil.org> wrote:
> > On Tue, Jun 05, 2007 at 11:12:58AM -0300, Rodrigo Campos wrote:
> >> Package: linux-image-2.6.18-5-686
> >> Version: 2.6.18.dfsg.1-13
> >> Severity: grave
> >> Justification: renders package unusable
> >>
> >> Hi, the other day i upgrade from  lastest linux-image-2.6.18-4-686 to
> >> linux-image-2.6.18-5-686 from proposed-updates and all seems to be ok.
> >> But yesterday after i power it on, i hit this kernel bug. I dot know
> >> how to reproduce it, but the trace might be useful.
> >>
> >> Let me know if you need any other extra information or tests, and feel
> >> free to downgrade the severity :)
> >
> > Does this error still occur with more recent kernel versions?
> 
> 
> No, it never happen again. I tried to reproduce before reporting the
> bug, but I couldn't.
> 
> It happen just that time and never again. And since then I've tried
> .18, .21, .22, .23, .24, .25, .26 debian kernels.

Thanks, I'll close that bug, then.

Cheers,
        Moritz

--- End Message ---
Reply to: