Ubuntu
linux package

kernel BUG at /build/buildd/linux-2.6.35/fs/buffer.c:3346!; RIP: 0010:[<ffffffff8117bb8d>] [<ffffffff8117bb8d>] free_buffer_head+0x3d/0x50

Bug #658584 reported by Charlie
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

WORKAROUND: After removing fglrx the system appears to be stable, I can no longer reproduce the freeze.

here is the /var/syslog that appears right before the freeze

Oct 10 22:19:55 Helios kernel: [ 9052.438463] lo: Disabled Privacy Extensions
Oct 10 22:20:06 Helios kernel: [ 9063.416618] ------------[ cut here ]------------
Oct 10 22:20:06 Helios kernel: [ 9063.416623] kernel BUG at /build/buildd/linux-2.6.35/fs/buffer.c:3346!
Oct 10 22:20:06 Helios kernel: [ 9063.416626] invalid opcode: 0000 [#1] SMP
Oct 10 22:20:06 Helios kernel: [ 9063.416629] last sysfs file: /sys/devices/pci0000:00/0000:00:1c.2/0000:06:00.0/net/eth0/statistics/collisions
Oct 10 22:20:06 Helios kernel: [ 9063.416632] CPU 4
Oct 10 22:20:06 Helios kernel: [ 9063.416633] Modules linked in: nls_utf8 udf rfcomm binfmt_misc sco bnep l2cap parport_pc ppdev nfsd exportfs nfs lockd fscache nfs_acl auth_rpcgss snd_usb_audio snd_usbmidi_lib quickcam_messenger usbvideo snd_hda_codec_atihdmi snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep snd_pcm sunrpc snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq joydev btusb bluetooth usblp snd_timer snd_seq_device fglrx(P) psmouse asus_atk0110 snd gspca_stv06xx gspca_main serio_raw videodev v4l1_compat v4l2_compat_ioctl32 i7core_edac edac_core soundcore snd_page_alloc lp parport firewire_ohci usb_storage usbhid hid ahci r8169 libahci firewire_core pata_jmicron mii crc_itu_t
Oct 10 22:20:06 Helios kernel: [ 9063.416679]
Oct 10 22:20:06 Helios kernel: [ 9063.416683] Pid: 75, comm: kswapd0 Tainted: P 2.6.35-22-generic #33-Ubuntu P6T SE/System Product Name
Oct 10 22:20:06 Helios kernel: [ 9063.416685] RIP: 0010:[<ffffffff8117bb8d>] [<ffffffff8117bb8d>] free_buffer_head+0x3d/0x50
Oct 10 22:20:06 Helios kernel: [ 9063.416693] RSP: 0018:ffff880233879900 EFLAGS: 00010206
Oct 10 22:20:06 Helios kernel: [ 9063.416695] RAX: ffff8800886c7320 RBX: 0000000000000001 RCX: 0000000000000000
Oct 10 22:20:06 Helios kernel: [ 9063.416698] RDX: 0000000000000000 RSI: 0000000000001000 RDI: ffff8800886c72d8
Oct 10 22:20:06 Helios kernel: [ 9063.416700] RBP: ffff880233879900 R08: dead000000200200 R09: dead000000100100
Oct 10 22:20:06 Helios kernel: [ 9063.416702] R10: ffff880100000cd0 R11: 0000000000000000 R12: ffff8800886c72d8
Oct 10 22:20:06 Helios kernel: [ 9063.416705] R13: ffffea00019c9b28 R14: ffffea00019c9b28 R15: ffff8801d6dc739c
Oct 10 22:20:06 Helios kernel: [ 9063.416707] FS: 0000000000000000(0000) GS:ffff880001e80000(0000) knlGS:0000000000000000
Oct 10 22:20:06 Helios kernel: [ 9063.416710] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
Oct 10 22:20:06 Helios kernel: [ 9063.416712] CR2: 00007f0ff3b3c000 CR3: 00000000064b2000 CR4: 00000000000006e0
Oct 10 22:20:06 Helios kernel: [ 9063.416715] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Oct 10 22:20:06 Helios kernel: [ 9063.416717] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Oct 10 22:20:06 Helios kernel: [ 9063.416720] Process kswapd0 (pid: 75, threadinfo ffff880233878000, task ffff8802350944a0)
Oct 10 22:20:06 Helios kernel: [ 9063.416722] Stack:
Oct 10 22:20:06 Helios kernel: [ 9063.416723] ffff880233879940 ffffffff8117bfd9 ffffea0007963fe8 ffff8800886c72d8
Oct 10 22:20:06 Helios kernel: [ 9063.416727] <0> 0200000000000008 ffff8800886c72d8 0000000000000000 ffff8800886c72d8
Oct 10 22:20:06 Helios kernel: [ 9063.416731] <0> ffff8802338799a0 ffffffff81227ce7 ffff8802338799a0 ffffffff8114db26
Oct 10 22:20:06 Helios kernel: [ 9063.416735] Call Trace:
Oct 10 22:20:06 Helios kernel: [ 9063.416740] [<ffffffff8117bfd9>] try_to_free_buffers+0x79/0xc0
Oct 10 22:20:06 Helios kernel: [ 9063.416746] [<ffffffff81227ce7>] jbd2_journal_try_to_free_buffers+0xa7/0x150
Oct 10 22:20:06 Helios kernel: [ 9063.416751] [<ffffffff8114db26>] ? __mem_cgroup_uncharge_common+0x196/0x280
Oct 10 22:20:06 Helios kernel: [ 9063.416756] [<ffffffff811eb375>] ext4_releasepage+0x55/0x90
Oct 10 22:20:06 Helios kernel: [ 9063.416762] [<ffffffff81100872>] try_to_release_page+0x32/0x50
Oct 10 22:20:06 Helios kernel: [ 9063.416767] [<ffffffff8110fa15>] shrink_page_list+0x485/0x580
Oct 10 22:20:06 Helios kernel: [ 9063.416770] [<ffffffff81149799>] ? mem_cgroup_del_lru+0x39/0x40
Oct 10 22:20:06 Helios kernel: [ 9063.416774] [<ffffffff8110e2ab>] ? isolate_lru_pages+0xdb/0x260
Oct 10 22:20:06 Helios kernel: [ 9063.416778] [<ffffffff8110fddd>] shrink_inactive_list+0x2cd/0x7f0
Oct 10 22:20:06 Helios kernel: [ 9063.416783] [<ffffffff8116a13f>] ? destroy_inode+0x4f/0x60
Oct 10 22:20:06 Helios kernel: [ 9063.416787] [<ffffffff81165dbc>] ? prune_one_dentry+0x5c/0x110
Oct 10 22:20:06 Helios kernel: [ 9063.416790] [<ffffffff8110a12a>] ? determine_dirtyable_memory+0x1a/0x30
Oct 10 22:20:06 Helios kernel: [ 9063.416794] [<ffffffff8110a1d7>] ? get_dirty_limits+0x27/0x2f0
Oct 10 22:20:06 Helios kernel: [ 9063.416797] [<ffffffff8110e092>] ? get_scan_count+0x172/0x2b0
Oct 10 22:20:06 Helios kernel: [ 9063.416801] [<ffffffff811104ab>] shrink_zone+0x1ab/0x230
Oct 10 22:20:06 Helios kernel: [ 9063.416804] [<ffffffff81111619>] balance_pgdat+0x679/0x740
Oct 10 22:20:06 Helios kernel: [ 9063.416808] [<ffffffff811117f5>] kswapd+0x115/0x300
Oct 10 22:20:06 Helios kernel: [ 9063.416812] [<ffffffff8107f610>] ? autoremove_wake_function+0x0/0x40
Oct 10 22:20:06 Helios kernel: [ 9063.416815] [<ffffffff811116e0>] ? kswapd+0x0/0x300
Oct 10 22:20:06 Helios kernel: [ 9063.416818] [<ffffffff8107f0b6>] kthread+0x96/0xa0
Oct 10 22:20:06 Helios kernel: [ 9063.416823] [<ffffffff8100aee4>] kernel_thread_helper+0x4/0x10
Oct 10 22:20:06 Helios kernel: [ 9063.416826] [<ffffffff8107f020>] ? kthread+0x0/0xa0
Oct 10 22:20:06 Helios kernel: [ 9063.416829] [<ffffffff8100aee0>] ? kernel_thread_helper+0x0/0x10
Oct 10 22:20:06 Helios kernel: [ 9063.416830] Code: 2a 48 89 fe 48 8b 3d 73 b3 b6 00 e8 8e 64 fc ff 65 48 8b 14 25 58 eb 00 00 48 c7 c0 c0 2b 01 00 83 2c 02 01 e8 15 ff ff ff c9 c3 <0f> 0b eb fe eb 0d 90 90 90 90 90 90 90 90 90 90 90 90 90 55 48
Oct 10 22:20:06 Helios kernel: [ 9063.416861] RIP [<ffffffff8117bb8d>] free_buffer_head+0x3d/0x50
Oct 10 22:20:06 Helios kernel: [ 9063.416865] RSP <ffff880233879900>
Oct 10 22:20:06 Helios kernel: [ 9063.416868] ---[ end trace d4dcbdd5f7a63c06 ]---

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: linux-image-2.6.35-22-generic 2.6.35-22.33
Regression: Yes
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic x86_64
NonfreeKernelModules: fglrx
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC2: charlie 2453 F.... pulseaudio
 /dev/snd/controlC0: charlie 2453 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xfbaf8000 irq 73'
   Mixer name : 'Realtek ALC1200'
   Components : 'HDA:10ec0888,104383c0,00100101'
   Controls : 35
   Simple ctrls : 20
Card1.Amixer.info:
 Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfbbfc000 irq 74'
   Mixer name : 'ATI R6xx HDMI'
   Components : 'HDA:1002aa01,00aa0100,00100100'
   Controls : 4
   Simple ctrls : 1
Card1.Amixer.values:
 Simple mixer control 'IEC958',0
   Capabilities: pswitch pswitch-joined penum
   Playback channels: Mono
   Mono: Playback [on]
Card2.Amixer.info:
 Card hw:2 'Camera'/'Camera at usb-0000:00:1d.0-1, full speed'
   Mixer name : 'USB Mixer'
   Components : 'USB046d:08f0'
   Controls : 3
   Simple ctrls : 2
Date: Mon Oct 11 11:04:47 2010
HibernationDevice: RESUME=UUID=c1ec74b0-f304-48dc-9c18-18aa301590d3
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
MachineType: System manufacturer System Product Name
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-generic root=UUID=b5c06126-8e03-4828-ad28-8ea9919377c1 ro quiet splash
ProcEnviron:
 PATH=(custom, user)
 LANG=en_CA.utf8
 SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.38
RfKill:
 0: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
dmi.bios.date: 03/08/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0808
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P6T SE
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0808:bd03/08/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6TSE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

See original description
Revision history for this message
Charlie (cmsteven) wrote :
Revision history for this message
Charlie (cmsteven) wrote :

Basically what happens is that after approx. 30 mins (sometimes more sometimes less) the whole system locks up.
after searching the forums for an answer I checked the log files and found what was posted above

Thanks in advance

Revision history for this message
Charlie (cmsteven) wrote :

one more note:

After removing fglrx the system appears to be stable, I can no longer reproduce the freeze

description: updated
Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Eliah Kagan (degeneracypressure) wrote :

@Brad Figg
Do you also run the fglrx driver?

Revision history for this message
hallenrm (hallenrm-yahoo) wrote :

I am also suffering the same problem, but the time period is not always 30 mins or so. How does one remove fglrx ? Please guide!!!

Revision history for this message
Poldi (poldi) wrote :

Similar problem here

output from uname -a is

2.6.35-29-generic #51-Ubuntu SMP Fri Apr 15 17:12:35 UTC 2011 x86_64 GNU/Linux

I'm using nvidia drivers

Revision history for this message
Eliah Kagan (degeneracypressure) wrote :

@hallenrm
Vlad has this problem and he is not running fglrx (since fglrx is for ATi cards and he has an Nvidia card), so that won't necessarily help. But you can remove fglrx by opening a Terminal window (Ctrl+Alt+T) and running "sudo apt-get remove fglrx". If you're not sure if you're running fglrx, you can check using the instructions in post #3 at https://answers.launchpad.net/ubuntu/+source/linux/+question/157314 (and please let us know). Please also post the output of "uname -a".

Revision history for this message
Poldi (poldi) wrote :
Download full text (3.9 KiB)

I've had this happen again overnight. This time there is no BUG reported in syslog; the system just 'hangs'.

I cannot login via screen saver, connecting via ssh gives a 'No route to host' error. There is nothing in any of the logs that indicates any problem

---------------- syslog --------------------------
May 19 01:04:38 LeosLinux stunnel: LOG5[2589:140114948318976]: Connection closed: 5250 bytes sent to SSL, 27294994 bytes sent to socket
May 19 01:04:38 LeosLinux stunnel: LOG5[2589:140114948388608]: Connection closed: 5120 bytes sent to SSL, 27982780 bytes sent to socket
May 19 01:09:01 LeosLinux CRON[10962]: (root) CMD ( [ -x /usr/lib/php5/maxlifetime ] && [ -d /var/lib/php5 ] && find /var/lib/php5/ -depth -mindepth 1 -maxdepth 1 -type f -cmin +$(/usr/lib/php5/maxlifetime) -delete)
May 19 01:17:01 LeosLinux CRON[11019]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
May 19 01:39:01 LeosLinux CRON[11074]: (root) CMD ( [ -x /usr/lib/php5/maxlifetime ] && [ -d /var/lib/php5 ] && find /var/lib/php5/ -depth -mindepth 1 -maxdepth 1 -type f -cmin +$(/usr/lib/php5/maxlifetime) -delete)
May 19 02:09:01 LeosLinux CRON[11148]: (root) CMD ( [ -x /usr/lib/php5/maxlifetime ] && [ -d /var/lib/php5 ] && find /var/lib/php5/ -depth -mindepth 1 -maxdepth 1 -type f -cmin +$(/usr/lib/php5/maxlifetime) -delete)
May 19 02:17:01 LeosLinux CRON[11172]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
May 19 02:39:01 LeosLinux CRON[11227]: (root) CMD ( [ -x /usr/lib/php5/maxlifetime ] && [ -d /var/lib/php5 ] && find /var/lib/php5/ -depth -mindepth 1 -maxdepth 1 -type f -cmin +$(/usr/lib/php5/maxlifetime) -delete)
May 19 03:00:01 LeosLinux CRON[11281]: (amandabackup) CMD (/usr/sbin//amdump MyConfig)
May 19 03:09:02 LeosLinux CRON[11367]: (root) CMD ( [ -x /usr/lib/php5/maxlifetime ] && [ -d /var/lib/php5 ] && find /var/lib/php5/ -depth -mindepth 1 -maxdepth 1 -type f -cmin +$(/usr/lib/php5/maxlifetime) -delete)
May 19 03:17:01 LeosLinux CRON[11476]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
May 19 03:39:02 LeosLinux CRON[11537]: (root) CMD ( [ -x /usr/lib/php5/maxlifetime ] && [ -d /var/lib/php5 ] && find /var/lib/php5/ -depth -mindepth 1 -maxdepth 1 -type f -cmin +$(/usr/lib/php5/maxlifetime) -delete)
May 19 04:09:02 LeosLinux CRON[11606]: (root) CMD ( [ -x /usr/lib/php5/maxlifetime ] && [ -d /var/lib/php5 ] && find /var/lib/php5/ -depth -mindepth 1 -maxdepth 1 -type f -cmin +$(/usr/lib/php5/maxlifetime) -delete)
May 19 04:17:02 LeosLinux CRON[11632]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
May 19 06:43:38 LeosLinux kernel: imklog 4.2.0, log source = /proc/kmsg started.
--------------------------------------------------------
I was still using the system at 1:05

A cron job (amanda backup) was started at 03:00, but failed saying that /home/llist (my home) was not found

------------------- email from amanda ---------------------
DUMP SUMMARY:
                                       DUMPER STATS TAPER STATS
HOSTNAME DISK L ORIG-GB OUT-GB COMP% MMM:SS KB/s MMM:SS KB/s
-------------------------- ------------------------------------- ----------------
LeosLinux.zu...

Read more...

Revision history for this message
Poldi (poldi) wrote :

It's just happened again. I've now upgraded to 11.04, so whatever causes this has not been fixed in the new release.

There is absolutely nothing in any of the logs indicating as to why this happens, but I was running a backup (amanda) at the time, and the process was killed at 03:05.
------------------------
$ amstatus MyConfig
Using /mnt/OurBackups/amanda/state/log/amdump
From Wed Jul 6 01:00:02 EST 2011

LeosLinux.zudiewiener.com:/bin 2 0m finished (1:08:44)
LeosLinux.zudiewiener.com:/boot 2 26m finished (1:09:12)
LeosLinux.zudiewiener.com:/etc 2 0m finished (1:09:05)
LeosLinux.zudiewiener.com:/home/llist 0 355586m failed: killed while writing to tape (3:03:41)
LeosLinux.zudiewiener.com:/usr 2 79m finished (1:11:22)
LeosLinux.zudiewiener.com:/var 2 182m finished (1:11:53)
---------------------------
The last entry in the syslog is also around that time
--------------------------
Jul 6 01:39:03 LeosLinux CRON[29242]: (root) CMD ( [ -x /usr/lib/php5/maxlifetime ] && [ -d /var/lib/php5 ] && find /var/lib/php5/ -depth -mindepth 1 -maxdepth 1 -type f -cmin +$(/usr/lib/php5/maxlifetime) -delete)
Jul 6 01:59:57 LeosLinux smartd[2641]: Device: /dev/sda [SAT], Temperature changed +4 Celsius to 37 Celsius (Min/Max 30/37)
Jul 6 02:09:03 LeosLinux CRON[29412]: (root) CMD ( [ -x /usr/lib/php5/maxlifetime ] && [ -d /var/lib/php5 ] && find /var/lib/php5/ -depth -mindepth 1 -maxdepth 1 -type f -cmin +$(/usr/lib/php5/maxlifetime) -delete)
Jul 6 02:17:02 LeosLinux CRON[29467]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Jul 6 02:39:03 LeosLinux CRON[29578]: (root) CMD ( [ -x /usr/lib/php5/maxlifetime ] && [ -d /var/lib/php5 ] && find /var/lib/php5/ -depth -mindepth 1 -maxdepth 1 -type f -cmin +$(/usr/lib/php5/maxlifetime) -delete)
Jul 6 03:09:03 LeosLinux CRON[29742]: (root) CMD ( [ -x /usr/lib/php5/maxlifetime ] && [ -d /var/lib/php5 ] && find /var/lib/php5/ -depth -mindepth 1 -maxdepth 1 -type f -cmin +$(/usr/lib/php5/maxlifetime) -delete)
Jul 6 08:55:36 LeosLinux kernel: imklog 4.6.4, log source = /proc/kmsg started.
-----------------------------------------------------------------------------------------------------------

So I guess my first question is to any theories as to what could be the cause of this. The time seems to be between 03:00 and 04:00. I'm not sure if the backup ran last time when the system hung, but have run full backups before without any probs, so don't think it's the backup.

Thanks

Revision history for this message
Poldi (poldi) wrote :

It just happened again (system was up for at least 24 hours).

One thing I noticed was that the backup just completed before the system froze. I also ran a web crawler and indexer, so my question is,

"Could the problem be I/O related"?

Again there is nothing in any of the logs; the system just stops responding.

I appreciate any suggestions on how to figure out what's going wrong.

Revision history for this message
Poldi (poldi) wrote :

Just had another freeze.

The amanda backup was running again; this is now the third time that the backup was running while the system 'froze'; too much of a coincidence I think, but not sure what to do next. I will post to the amanda mailing list too.

Revision history for this message
Poldi (poldi) wrote :

After posting the problem on the amanda mailing list, I got one response that indicated the network driver as a possible culprit.

I followed instructions in this link https://bbs.archlinux.org/viewtopic.php?id=101836

Will let you know what happens

Revision history for this message
Poldi (poldi) wrote :

I don't think it's related to #12.

As I had some corrupted files on an encrypted file system, I moved the encrypted files to an unencrypted folder (to figure out which files were corrupted). I had moved about 360GB (of 380GB) media files when it hung.

So I think my problem is in some way related to accessing files (not sure if the encryption has any relevance).

Revision history for this message
Poldi (poldi) wrote :

This time the system shut down completely when it did a check on the software raid

------------------------------------------ kernel.log-------------------------
Aug 7 00:30:52 LeosLinux rsyslogd: -- MARK --
Aug 7 00:50:52 LeosLinux rsyslogd: -- MARK --
Aug 7 00:57:01 LeosLinux kernel: [380814.759230] md: data-check of RAID array md0
Aug 7 00:57:01 LeosLinux kernel: [380814.759239] md: minimum _guaranteed_ speed: 1000 KB/sec/disk.
Aug 7 00:57:01 LeosLinux kernel: [380814.759245] md: using maximum available idle IO bandwidth (but not more than 200000 KB/sec) for data-check.
Aug 7 00:57:01 LeosLinux kernel: [380814.759255] md: using 128k window, over a total of 1953511936 blocks.
Aug 7 01:10:52 LeosLinux rsyslogd: -- MARK --
Aug 7 01:30:52 LeosLinux rsyslogd: -- MARK --
Aug 7 01:50:52 LeosLinux rsyslogd: -- MARK --
Aug 7 02:10:52 LeosLinux rsyslogd: -- MARK --
Aug 7 02:30:53 LeosLinux rsyslogd: -- MARK --
Aug 7 02:50:53 LeosLinux rsyslogd: -- MARK --
Aug 7 03:10:53 LeosLinux rsyslogd: -- MARK --
Aug 7 03:30:53 LeosLinux rsyslogd: -- MARK --
Aug 7 03:50:53 LeosLinux rsyslogd: -- MARK --
Aug 7 04:10:53 LeosLinux rsyslogd: -- MARK --
Aug 7 04:30:53 LeosLinux rsyslogd: -- MARK --
Aug 7 04:50:53 LeosLinux rsyslogd: -- MARK --
Aug 7 07:47:01 LeosLinux kernel: imklog 4.6.4, log source = /proc/kmsg started.
--------------------------------------------------------------------------------------------------------------------------------

Is there any additional logging I can turn on?

Could it be my RAID controller?

Revision history for this message
Poldi (poldi) wrote :

I've logged this problem in the Ubuntu forums and somebody suggeested to provide additional cooling to the Southbridge, As I have a separate SATA controller I added a small fan, and have not had the problem since.

See http://ubuntuforums.org/showthread.php?t=1821845

Revision history for this message
penalvch (penalvch) wrote :

charlie, thank you for reporting this bug and helping make Ubuntu better. This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux <replace-with-bug-number>

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

summary: - system freezes after 30min of uptime
+ kernel BUG at /build/buildd/linux-2.6.35/fs/buffer.c:3346!; RIP:
+ 0010:[<ffffffff8117bb8d>] [<ffffffff8117bb8d>]
+ free_buffer_head+0x3d/0x50
description: updated
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Related questions

Remote bug watches

Bug watches keep track of this bug in other bug trackers.