search for: 00101000

...journal.c line 410: "bh->b_jlist == 0 || bh->b_jlist == BJ_LogCtl || bh->b_jlist == BJ_IO || bh->b_jlist == BJ_Data" Jan 17 23:09:55 planck kernel: Unable to handle kernel NULL pointer dereference at virtual address 00000000 Jan 17 23:09:55 planck kernel: current->tss.cr3 = 00101000, %cr3 = 00101000 Jan 17 23:09:55 planck kernel: *pde = 00000000 Jan 17 23:09:55 planck kernel: Oops: 0002 Jan 17 23:09:55 planck kernel: CPU: 0 After this a couple of files I had open in vi as well as my /var/log/messages got corrupted with bunch of null bytes inserted into them. The actual co...

...a2.9.5/ (default) -m /boot/System.map-2.2.18pre11-va2.9.5 (specified) Warning (compare_maps): ksyms_base symbol module_list_R__ver_module_list not found in System.map. Ignoring ksyms_base entry Unable to handle kernel NULL pointer dereference at virtual address 00000000 current->tss.cr3 = 00101000, %cr3 = 00101000 *pde = 00000000 Oops: 0002 CPU: 0 EIP: 0010:[<8015b722>] Using defaults from ksymoops -t elf32-i386 -a i386 EFLAGS: 00013282 eax: 0000006d ebx: 86e6ce40 ecx: 00000012 edx: 00000029 esi: 874d70e0 edi: 86e6ce40 ebp: 823ce880 esp: 827cdc58 ds: 0018 es: 0018...

...ution. If the current kernel and/or modules do not match the log, you can get more accurate output by telling me the kernel version and where to find map, modules, ksyms etc. ksymoops -h explains the options. Unable to handle kernel paging request at virtual address 4ed90398 current->tss.cr3 = 00101000, %cr3 = 00101000 *pde = 00000000 Oops: 0000 CPU: 0 EIP: 0010:[<c0133ca7>] Using defaults from ksymoops -t elf32-i386 -a i386 EFLAGS: 00010246 eax: 4ed90330 ebx: 00000000 ecx: 00000000 edx: c01eef0c esi: 4ed90330 edi: ce27ed00 ebp: 00000002 esp: cf04ddac ds: 0018 es: 0018...

...(device sd(8,49)): ext3_free_blocks: bit already cleared for block 2213 Assertion failure in journal_forget() at transaction.c line 860: "!test_and_set_bit(BH_Freed, &bh->b_state)" Unable to handle kernel NULL pointer dereference at virtual address 00000000 current->tss.cr3 = 00101000, %cr3 = 00101000 *pde = 00000000 Oops: 0002 CPU: 0EXT3-fs warning (device sd(8,49)): ext3_free_blocks: bit already cleared for block 56037886 EXT3-fs error (device sd(8,49)): ext3_readdir: bad entry in directory #2933557: directory entry across blocks - offset=0, inode=1986311577, rec_len=302...

Red Hat 2.2.19-6.2.12 + 0.0.7a + https://listman.redhat.com/pipermail/ext3-users/2001-November/002258.html (not tuned in /proc yet) + journal 4MB on each fs + 6 ext3 fs on raid1 (hda+hdc) + 1 ext3 fs on another disk not on raid1 (hdd) While untarring (tar zxf) a file that was on a ext3/raid1 onto hdd I got: ksymoops 2.3.4 on i686 2.2.19-6.2.12.g1. Options used -V (default) -k

...00000}' voltage calculation coefficients: '{0.828570,0.000000}' data receiving error (-1 instead of 16 bytes) data receiving error (-1 instead of 16 bytes) Signal 2: exiting While UPSMON plus is up, doing cat on /dev/ttyS0 gives the following data: (199.0 199.0 235.0 019 50.0 27.8 37.8 00101000^M Any thoughts? Thank you, Dror _________________________________________________________________ Don't just search. Find. Check out the new MSN Search! http://search.msn.com/

...been up for 2 weeks before this happened Phil =--= Feb 24 10:25:08 parcelfarce sshd[28545]: Received signal 15; terminating. Feb 24 10:25:09 parcelfarce kernel: Unable to handle kernel NULL pointer derefer ence at virtual address 00000000 Feb 24 10:25:09 parcelfarce kernel: current->tss.cr3 = 00101000, %%cr3 = 0010100 0 Feb 24 10:25:09 parcelfarce kernel: *pde = 00000000 Feb 24 10:25:09 parcelfarce kernel: Oops: 0000 Feb 24 10:25:09 parcelfarce kernel: CPU: 1 Feb 24 10:25:09 parcelfarce kernel: EIP: 0010:[ext3_get_inode_loc+49/340] Feb 24 10:25:09 parcelfarce kernel: EFLAGS: 00010206 Feb 2...

https://bugs.freedesktop.org/show_bug.cgi?id=96411 Bug ID: 96411 Summary: [NVA8] reclocking not working. screen glitches. Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau

...00000}' voltage calculation coefficients: '{0.828570,0.000000}' data receiving error (-1 instead of 16 bytes) data receiving error (-1 instead of 16 bytes) Signal 2: exiting While UPSMON plus is up, doing cat on /dev/ttyS0 gives the following data: (199.0 199.0 235.0 019 50.0 27.8 37.8 00101000^M Any thoughts? Thank you, Dror _________________________________________________________________ Express yourself instantly with MSN Messenger! Download today it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/

https://bugs.freedesktop.org/show_bug.cgi?id=92297 Bug ID: 92297 Summary: dithering detected incorrectly Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: minor Priority: medium Component: Driver/nouveau Assignee: nouveau at

> I finally got a Best Power Patriot Pro II fixed up with a new battery and cable, and tried it with nutdrv_qx (since it uses a variant of the Q1 protocol). It auto-detected the use of Q1. > > It looks like things mostly work: Nice, merging bestups.c into nutdrv_qx has been on my todo list for a while, let's see how far we can get. > 1) The bestups driver uses an "ID"

...utdown_mode does not work on my UPS. (The manual describes fixed timeouts in the pinout section, so that makes sense.) 9.562389 Using protocol: BestUPS 0.01 9.562405 upsdrv_initinfo... 9.562480 send: 'Q1' 9.772351 read: '(119.0 118.1 118.1 020 60.0 13.9 XX.X 00101000' 9.772424 ups_infoval_set: non numerical value [ups.temperature: XX.X] 9.772530 send: 'ID' 9.896340 read: 'PR2,400,120,120,10.8,13.6' 9.896482 send: 'RT' 9.927323 read: '053' 9.927433 send: 'SS?' 10.928470 r...

Hi Daniele, I finally got a Best Power Patriot Pro II fixed up with a new battery and cable, and tried it with nutdrv_qx (since it uses a variant of the Q1 protocol). It auto-detected the use of Q1. It looks like things mostly work: bestups: battery.charge: 100.0 battery.voltage: 13.9 battery.voltage.nominal: 12 device.mfr: Best Power device.model: Patriot Pro II 400 device.type: ups

https://bugs.freedesktop.org/show_bug.cgi?id=98852 Bug ID: 98852 Summary: Nvidia graphics card fan not running or to slow, danger of overheating Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium

https://bugs.freedesktop.org/show_bug.cgi?id=107016 Bug ID: 107016 Summary: Gpio error only from kernel higher as 4.x (k2000m; 0x0e73b0a2; version 80.07.40.00.02) Product: Mesa Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium

https://bugs.freedesktop.org/show_bug.cgi?id=100228 Bug ID: 100228 Summary: [NV137] unknown chipset (137000a1) Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau Assignee: nouveau

...Plugin 00078000 /System/Library/PrivateFrameworks/NetworkConfig.framework/Versions/A/NetworkConfig 000cc000 /System/Library/PrivateFrameworks/ICANotifications.framework/Versions/A/ICANotifications 000f6000 /System/Library/PrivateFrameworks/iPod.framework/Versions/A/iPod 00101000 /System/Library/PrivateFrameworks/BezelServices.framework/Versions/A/BezelServices 0010a000 /System/Library/Frameworks/DiscRecording.framework/Versions/A/DiscRecording 0023e000 /System/Library/PrivateFrameworks/DiskImages.framework/Versions/A/DiskImages 0039d000 /S...