search for: 0x128

Hi, Since update to 2.6.37 I can''t build openwrt on my btrfs buildroot anymore. I''m not sure if this is related to the other flush-btrfs-1 thread. plenty of diskspace is free: /dev/mapper/cruor-build 97G 68G 27G 73% /opt/build It always hangs when openwrt builds the ext4 image and runs tune2fs on it.

...c:smb_panic2(1398) Apr 20 15:21:02 gandalf2 smbd[6891]: PANIC: internal error Apr 20 15:21:02 gandalf2 smbd[6891]: [2004/04/20 15:21:02, 0] lib/util.c:smb_panic2(1406) Apr 20 15:21:02 gandalf2 smbd[6891]: BACKTRACE: 27 stack frames: Apr 20 15:21:02 gandalf2 smbd[6891]: #0 smbd(smb_panic2+0x128) [0x81cb288] Apr 20 15:21:02 gandalf2 smbd[6891]: #1 smbd(smb_panic+0x19) [0x81cb159] Apr 20 15:21:02 gandalf2 smbd[6891]: #2 smbd [0x81b96f2] Apr 20 15:21:02 gandalf2 smbd[6891]: #3 /lib/tls/libc.so.6 [0x420275c8] Apr 20 15:21:02 gandalf2 smbd[6891]: #4 /lib/tls/libc.so.6(malloc+0x...

Hi folks, I''m trying to shape two clients in my LAN when accessing the internet. Actual situation is that EVERY traffic goes into 1:40, so the client which should fall into 1:30 does not get the lower uplink it should have, but the uplink defined for the client defined as 1:30 When I disable the definition of 1:40, every traffic falls into 1:30 (except for the traffic defined to be in

..._kms_helper drm i2c_algo_bit i2c_core video output dm_mirror dm_region_hash dm_log dm_mod [last unloaded: scsi_wait_scan] [<ffffffffa03a7c8c>] ? iwl_grab_nic_access+0x5c/0x70 [iwlwifi] [<ffffffffa03a7ed1>] ? iwl_write_prph+0x41/0xa0 [iwlwifi] [<ffffffffa03b5088>] ? iwl_apm_init+0x128/0x1c0 [iwlwifi] [<ffffffffa03b5248>] ? iwl_trans_pcie_start_hw+0x128/0x1a0 [iwlwifi] [<ffffffffa039a579>] ? iwl_op_mode_dvm_start+0x179/0x500 [iwlwifi] [<ffffffffa03b3c96>] ? iwl_ucode_callback+0xb86/0xd80 [iwlwifi] iwlwifi 0000:02:00.0: Unknown hardware type iwlwifi 0000:02:00...

Hi, I just want to know if somebody use 2.6.31.4 xenified kernel (aka OpenSUSE) in production? We have been testing it on new Nehalem Xeon server for few weeks w/o any problem. But as soon we tried it on production machine - after several production domUs started - hard OS failure. We had to switch back to 2.6.18.8 - xen stock kernel. Peter _______________________________________________

A new employee started today, when logging into his new mailbox this morning during a walk-through I got a nasty server error response in Thunderbird - something I never see, DC runs smooth as butter for us. Checking the server log I see this: == snip == dovecot: Jul 09 09:38:54 Error: IMAP(xxxxxxx): Maildir /home/x/xxxxxxx/Maildir sync: UIDVALIDITY changed (1183406107 -> 1183999134)

...[schedule+1682/1696] schedule+0x692/0x6a0 [__change_page_attr+203/624] __change_page_attr+0xcb/0x270 [sys_sched_yield+89/112] sys_sched_yield+0x59/0x70 [coredump_wait+63/176] coredump_wait+0x3f/0xb0 [do_coredump+222/471] do_coredump+0xde/0x1d7 [__dequeue_signal+296/432] __dequeue_signal+0x128/0x1b0 [__dequeue_signal+245/432] __dequeue_signal+0xf5/0x1b0 [dequeue_signal+53/160] dequeue_signal+0x35/0xa0 [get_signal_to_deliver+599/848] get_signal_to_deliver+0x257/0x350 [do_signal+103/288] do_signal+0x67/0x120 [dnotify_parent+58/176] dnotify_parent+0x3a/0xb0 [vfs_read+210/304] vf...

...se.dir/lib/BrowserApp.cpp.o:(.rodata._ZTV10BrowserApp[vtable for BrowserApp]+0x120): undefined reference to `wxApp::OnAssertFailure(wchar_t const*, int, wchar_t const*, wchar_t const*, wchar_t const*)' CMakeFiles/llbrowse.dir/lib/BrowserApp.cpp.o:(.rodata._ZTV10BrowserApp[vtable for BrowserApp]+0x128): undefined reference to `wxAppConsole::OnAssert(wchar_t const*, int, wchar_t const*, wchar_t const*)' CMakeFiles/llbrowse.dir/lib/TreeView.cpp.o: In function `wxStringBase::wxStringBase(wxStringBase const&)': TreeView.cpp:(.text._ZN12wxStringBaseC2ERKS_[wxStringBase::wxStringBase(wxStr...

...__driver_attach+0x190/0x210 > > [ 3.717645] bus_for_each_dev+0x14c/0x1f0 > > [ 3.728633] driver_attach+0x48/0x78 > > [ 3.740249] bus_add_driver+0x26c/0x5b8 > > [ 3.752248] driver_register+0x16c/0x398 > > [ 3.757211] __platform_driver_register+0xd8/0x128 > > [ 3.770860] virtio_mmio_init+0x1c/0x24 > > [ 3.782671] do_one_initcall+0xe0/0x398 > > [ 3.791890] kernel_init_freeable+0x594/0x660 > > [ 3.798514] kernel_init+0x18/0x190 > > [ 3.810220] ret_from_fork+0x10/0x18 > > > > To fix this, w...

...__driver_attach+0x190/0x210 > > [ 3.717645] bus_for_each_dev+0x14c/0x1f0 > > [ 3.728633] driver_attach+0x48/0x78 > > [ 3.740249] bus_add_driver+0x26c/0x5b8 > > [ 3.752248] driver_register+0x16c/0x398 > > [ 3.757211] __platform_driver_register+0xd8/0x128 > > [ 3.770860] virtio_mmio_init+0x1c/0x24 > > [ 3.782671] do_one_initcall+0xe0/0x398 > > [ 3.791890] kernel_init_freeable+0x594/0x660 > > [ 3.798514] kernel_init+0x18/0x190 > > [ 3.810220] ret_from_fork+0x10/0x18 > > > > To fix this, w...

...2] driver_probe_device+0x250/0x828 [ 3.706187] __driver_attach+0x190/0x210 [ 3.717645] bus_for_each_dev+0x14c/0x1f0 [ 3.728633] driver_attach+0x48/0x78 [ 3.740249] bus_add_driver+0x26c/0x5b8 [ 3.752248] driver_register+0x16c/0x398 [ 3.757211] __platform_driver_register+0xd8/0x128 [ 3.770860] virtio_mmio_init+0x1c/0x24 [ 3.782671] do_one_initcall+0xe0/0x398 [ 3.791890] kernel_init_freeable+0x594/0x660 [ 3.798514] kernel_init+0x18/0x190 [ 3.810220] ret_from_fork+0x10/0x18 To fix this, we can simply rip out the explicit cleanup that the devm infrastructure...

...2] driver_probe_device+0x250/0x828 [ 3.706187] __driver_attach+0x190/0x210 [ 3.717645] bus_for_each_dev+0x14c/0x1f0 [ 3.728633] driver_attach+0x48/0x78 [ 3.740249] bus_add_driver+0x26c/0x5b8 [ 3.752248] driver_register+0x16c/0x398 [ 3.757211] __platform_driver_register+0xd8/0x128 [ 3.770860] virtio_mmio_init+0x1c/0x24 [ 3.782671] do_one_initcall+0xe0/0x398 [ 3.791890] kernel_init_freeable+0x594/0x660 [ 3.798514] kernel_init+0x18/0x190 [ 3.810220] ret_from_fork+0x10/0x18 To fix this, we can simply rip out the explicit cleanup that the devm infrastructure...

On 2011-02-14 20:39, Talin wrote: > > > On Mon, Feb 14, 2011 at 1:17 AM, Renato Golin <rengolin at systemcall.org > <mailto:rengolin at systemcall.org>> wrote: > > I think this deserves a blog post... > > I'd like to wait until I get some feedback - I don't know yet if anyone > is having trouble building or running the thing... Hi Talin,

...004/09/26 11:22:40, 0] lib/fault.c:fault_report(39) =============================================================== [2004/09/26 11:22:41, 0] lib/util.c:smb_panic2(1385) PANIC: internal error [2004/09/26 11:22:41, 0] lib/util.c:smb_panic2(1393) BACKTRACE: 14 stack frames: #0 nmbd(smb_panic2+0x128) [0x80c5668] #1 nmbd(smb_panic+0x19) [0x80c5539] #2 nmbd [0x80b3622] #3 /lib/libc.so.6 [0x40154c18] #4 nmbd(retransmit_or_expire_response_records+0x11b) [0x806efeb] #5 nmbd(unbecome_local_master_browser+0x150) [0x8061f00] #6 nmbd [0x8062254] #7 nmbd [0x806a5d7] #8 nmbd [0x80...

...b4>] update_atime+0x8c/0x98 [<c0145b74>] link_path_walk+0x698/0x8c0 [<c0169ca7>] ext3_dirty_inode+0xdf/0x14c [<c0147e53>] vfs_follow_link+0x12f/0x1a4 [<c0170df6>] ext3_follow_link+0x16/0x20 [<c0145b81>] link_path_walk+0x6a5/0x8c0 [<c0146074>] path_lookup+0x128/0x134 [<c01461af>] __user_walk+0x2f/0x4c [<c0141d62>] vfs_stat+0x1a/0x44 [<c0142248>] sys_stat64+0x14/0x2c [<c0108b03>] syscall_call+0x7/0xb Code: 0f 0b ea 02 60 16 29 c0 83 c4 14 8b 4d 08 8b 45 0c ff 49 04 <6>note: bash[227] exited with preempt_count 2 Debug: sl...

...2] driver_probe_device+0x250/0x828 [ 3.706187] __driver_attach+0x190/0x210 [ 3.717645] bus_for_each_dev+0x14c/0x1f0 [ 3.728633] driver_attach+0x48/0x78 [ 3.740249] bus_add_driver+0x26c/0x5b8 [ 3.752248] driver_register+0x16c/0x398 [ 3.757211] __platform_driver_register+0xd8/0x128 [ 3.770860] virtio_mmio_init+0x1c/0x24 [ 3.782671] do_one_initcall+0xe0/0x398 [ 3.791890] kernel_init_freeable+0x594/0x660 [ 3.798514] kernel_init+0x18/0x190 [ 3.810220] ret_from_fork+0x10/0x18 To fix this, we can simply rip out the explicit cleanup that the devm infrastructure...

...2] driver_probe_device+0x250/0x828 [ 3.706187] __driver_attach+0x190/0x210 [ 3.717645] bus_for_each_dev+0x14c/0x1f0 [ 3.728633] driver_attach+0x48/0x78 [ 3.740249] bus_add_driver+0x26c/0x5b8 [ 3.752248] driver_register+0x16c/0x398 [ 3.757211] __platform_driver_register+0xd8/0x128 [ 3.770860] virtio_mmio_init+0x1c/0x24 [ 3.782671] do_one_initcall+0xe0/0x398 [ 3.791890] kernel_init_freeable+0x594/0x660 [ 3.798514] kernel_init+0x18/0x190 [ 3.810220] ret_from_fork+0x10/0x18 To fix this, we can simply rip out the explicit cleanup that the devm infrastructure...

...8/0xfc [77216.796004] [<ffff0000084c29a8>] __pci_register_driver+0x60/0x6c [77216.802047] [<ffff00000137bcb8>] drm_pci_init+0x108/0x138 [drm] [77216.808146] [<ffff000001530158>] nouveau_drm_init+0x158/0x10000 [nouveau] [77216.814922] [<ffff0000080831a8>] do_one_initcall+0x44/0x128 [77216.820483] [<ffff0000081cad6c>] do_init_module+0x68/0x1e0 [77216.825957] [<ffff000008150d84>] load_module+0xfac/0x12bc [77216.831343] [<ffff00000815132c>] SyS_finit_module+0xe4/0xf0 [77216.836902] [<ffff000008082b70>] el0_svc_naked+0x24/0x28 By default fedora is using a...

On Fri, May 26, 2023 at 5:11?AM Karol Herbst <kherbst at redhat.com> wrote: > > 1ba6113a90a0 removed a lot of the kernel GPU channel, but method 0x128 > was important as otherwise the GPU spams us with `CACHE_ERROR` messages. > > We use the blit subchannel inside our vblank handling, so we should keep > at least this part. > > v2: Only do it for NV11+ GPUs > > Closes: https://gitlab.freedesktop.org/drm/nouveau/-/issues/201...

1ba6113a90a0 removed a lot of the kernel GPU channel, but method 0x128 was important as otherwise the GPU spams us with `CACHE_ERROR` messages. We use the blit subchannel inside our vblank handling, so we should keep at least this part. v2: Only do it for NV11+ GPUs Closes: https://gitlab.freedesktop.org/drm/nouveau/-/issues/201 Fixes: 4a16dd9d18a0 ("drm/nouve...