Created attachment 94554 [details] dmesg radeon 6850 I'm running Fedora 20 with the latest distro kernel (3.13.3). I'm running Gnome shell and see very frequent hangs. Its usually observed when the system has been inactive for a while and the monitor goes into powersave mode. When I try to activate the system via keyboard/mouse I get a black screen. I cannot switch to a VT as well. SSH still works and the system is responsive via ssh. DPM is not enabled. However I did switch the card to "low" power profile after boot. echo "low" > /sys/class/drm/card0/device/power_profile cat /sys/kernel/debug/dri/0/radeon_pm_info default engine clock: 775000 kHz current engine clock: 99990 kHz default memory clock: 1000000 kHz current memory clock: 150000 kHz voltage: 950 mV PCIE lanes: 16 dmesg shows the following: [ 8443.493242] radeon 0000:01:00.0: evergreen_surface_check_2d:277 texture pitch 1920 invalid must be aligned with 512 [ 8443.493249] radeon 0000:01:00.0: evergreen_cs_track_validate_texture:826 texture invalid 0x1dfc3bc1 0x40000437 0x060a0000 0x00000000 0x80000000 0x800304da [ 8443.493251] [drm:radeon_cs_ib_chunk] *ERROR* Invalid command stream ! [ 8455.699835] radeon 0000:01:00.0: evergreen_surface_check_2d:277 texture pitch 1920 invalid must be aligned with 512 [ 8455.699841] radeon 0000:01:00.0: evergreen_cs_track_validate_texture:826 texture invalid 0x1dfc3bc1 0x40000437 0x060a0000 0x00000000 0x80000000 0x800304da [ 8455.699844] [drm:radeon_cs_ib_chunk] *ERROR* Invalid command stream ! [ 8456.748217] radeon 0000:01:00.0: evergreen_surface_check_2d:277 texture pitch 1920 invalid must be aligned with 512 [ 8456.748223] radeon 0000:01:00.0: evergreen_cs_track_validate_texture:826 texture invalid 0x1dfc3bc1 0x40000437 0x060a0000 0x00000000 0x80000000 0x800304da [ 8456.748226] [drm:radeon_cs_ib_chunk] *ERROR* Invalid command stream ! [ 8605.668059] radeon 0000:01:00.0: evergreen_surface_check_2d:277 texture pitch 1920 invalid must be aligned with 512 [ 8605.668066] radeon 0000:01:00.0: evergreen_cs_track_validate_texture:826 texture invalid 0x1dfc3bc1 0x40000437 0x060a0000 0x00000000 0x80000000 0x800304da [ 8605.668068] [drm:radeon_cs_ib_chunk] *ERROR* Invalid command stream !
Created attachment 94555 [details] Xorg.0.log
Created attachment 94556 [details] lspci -v output
Created attachment 94557 [details] VBIOS HD6850
rpm -qa | grep mesa mesa-libEGL-9.2.5-1.20131220.fc20.x86_64 mesa-filesystem-9.2.5-1.20131220.fc20.x86_64 mesa-dri-drivers-9.2.5-1.20131220.fc20.x86_64 mesa-libglapi-9.2.5-1.20131220.fc20.x86_64 mesa-libGL-9.2.5-1.20131220.fc20.x86_64 mesa-libwayland-egl-9.2.5-1.20131220.fc20.x86_64 mesa-libgbm-9.2.5-1.20131220.fc20.x86_64 mesa-libxatracker-9.2.5-1.20131220.fc20.x86_64
Does Option "ColorTiling2D" "off" in xorg.conf work around the problem, or at least the error messages in dmesg?
I've disabled ColorTiling2D now. Will report back soon. One observation is that when I disable monitor power saving in Gnome Settings (Power->Blank Screen->Never), I did not hit the issue. Although I tested only for about 12 hours. Without this I usually get the black screen on resuming the monitor from power saving mode in about 1 or 2 hours.
When you try switching VTs after the problem occurs, do lines like (II) AIGLX: Suspending AIGLX clients for VT switch (II) AIGLX: Resuming AIGLX clients after VT switch appear in the Xorg log file? It sounds like maybe there's just a problem lighting up the monitor again after it's turned off...
I can confirm that disabling ColorTiling2D had a positive impact. There were no black screens on resuming the monitor from powersave mode. I ran the system for about 14 hours. Then I turned ColorTiling2D back on, and hit the issue within 5 minutes. The monitor power LED is on when resumed and I can see the backlight. I tried switching to VT and still a black screen. I do see (via ssh) the the lines you mention (in comment 7) in my xorg.0.log when trying to switch VTs. Let me know if you want the full log, following is a snippet from the log: ............... [ 122.925] (II) RADEON(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e) [ 122.925] (II) RADEON(0): Modeline "1920x1080"x60.0 172.80 1920 2040 2248 2576 1080 1081 1084 1118 -hsync +vsync (67.1 kHz e) [ 323.946] (II) AIGLX: Suspending AIGLX clients for VT switch [ 382.915] (II) AIGLX: Resuming AIGLX clients after VT switch [ 382.963] (II) RADEON(0): EDID vendor "DEL", prod id 41055 [ 382.963] (II) RADEON(0): Using hsync ranges from config file [ 382.963] (II) RADEON(0): Using vrefresh ranges from config file [ 382.963] (II) RADEON(0): Printing DDC gathered Modelines: [ 382.963] (II) RADEON(0): Modeline "1920x1080"x0.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz eP) ...................... ...................... And dmesg contains the previously mentioned error: .......... [ 15.485597] IPv6: ADDRCONF(NETDEV_CHANGE): wlp0s26f7u4: link becomes ready [ 95.056067] fuse init (API version 7.22) [ 95.070291] SELinux: initialized (dev fusectl, type fusectl), uses genfs_contexts [ 95.096897] SELinux: initialized (dev fuse, type fuse), uses genfs_contexts [ 382.917539] radeon 0000:01:00.0: evergreen_surface_check_2d:277 texture pitch 1920 invalid must be aligned with 512 [ 382.917545] radeon 0000:01:00.0: evergreen_cs_track_validate_texture:826 texture invalid 0x1dfc3bc1 0x40000437 0x060a0000 0x00000000 0x80000000 0x800304da [ 382.917548] [drm:radeon_cs_ib_chunk] *ERROR* Invalid command stream ! ...........
Does ColorTiling2D work better with a newer version of the mesa-dri-drivers and/or libdrm(-radeon) packages?
FWIW, I have just started seeing behaviour very similar to this, also with an HD6850, though it is probably a distinct bug because all the software versions involved are very different. This happened after closely-adjoined upgrades of the kernel (from 3.19 to 4.0.3), the X server (from 1.15.1, yes, I know, it's because of the security holes I finally upgraded, to 1.17.1), the ATI driver (from 7.3.0-26 to 7.5.0.68, all "git describe" output from the unmodified trunk), Mesa (from 10.2.6 to 10.5.5), and LLVM (from 3.3 to 3.5.2), so the fault could, alas, in theory lie in any or all of these. Mesa is using Gallium in both cases. Glamor is not in use. dpm is, and has been working flawlessly thank you very much, cutting my desktop's power consumption from 130W to 90W :) over the last year that's saved at least the price of the beer I owe you for the dpm work, Michel :) With this setup, with an older Chromium (SVN revision 322707) I see very frequent failures to map the interior of its windows at or shortly after startup, sometimes accompanied by a total loss of the ability to switch focus, whether by keyboard or mouse, whether on a desktop where the Chromium window was mapped or not (X still responded, so I could switch out of X and kill Chromium, whereupon X recovered). Chromium screams on its stderr as this happens: [8893:8893:0523/225116:ERROR:gpu_channel_host.cc(175)] GpuChannelHost::CreateViewCommandBuffer failed. [8893:8893:0523/225116:ERROR:webgraphicscontext3d_command_buffer_impl.cc(226)] Failed to initialize command buffer. [8893:8893:0523/225116:ERROR:gpu_channel_host.cc(175)] GpuChannelHost::CreateViewCommandBuffer failed. [8893:8893:0523/225116:ERROR:webgraphicscontext3d_command_buffer_impl.cc(226)] Failed to initialize command buffer. [8893:8893:0523/225116:ERROR:gpu_process_transport_factory.cc(574)] Lost UI shared context. [9929:9929:0523/225118:ERROR:sandbox_linux.cc(345)] InitializeSandbox() called with multiple threads in process gpu-process [15:41:0523/225118:ERROR:gpu_channel_host.cc(175)] GpuChannelHost::CreateViewCommandBuffer failed. [15:41:0523/225118:ERROR:webgraphicscontext3d_command_buffer_impl.cc(226)] Failed to initialize command buffer. [8893:8916:0523/225118:ERROR:channel.cc(300)] RawChannel read error (connection broken) [8893:8916:0523/225118:ERROR:channel.cc(300)] RawChannel read error (connection broken) [322:337:0523/225119:ERROR:gpu_channel_host.cc(175)] GpuChannelHost::CreateViewCommandBuffer failed. [322:337:0523/225119:ERROR:webgraphicscontext3d_command_buffer_impl.cc(226)] Failed to initialize command buffer. [8893:8916:0523/225119:ERROR:channel.cc(300)] RawChannel read error (connection broken) [9929:9929:0523/225119:ERROR:gles2_cmd_decoder.cc(11630)] [GroupMarkerNotSet(crbug.com/242999)!:D088433BA20D0000]GL ERROR :GL_INVALID_OPERATION : glCreateAndConsumeTextureCHROMIUM: invalid mailbox name [9929:9929:0523/225119:ERROR:gles2_cmd_decoder.cc(4431)] [GroupMarkerNotSet(crbug.com/242999)!:D088433BA20D0000]GL ERROR :GL_INVALID_OPERATION : glBindTexture: id not generated by glGenTextures [9929:9929:0523/225119:ERROR:gles2_cmd_decoder.cc(11630)] [GroupMarkerNotSet(crbug.com/242999)!:D088433BA20D0000]GL ERROR :GL_INVALID_OPERATION : glCreateAndConsumeTextureCHROMIUM: invalid mailbox name [9929:9929:0523/225119:ERROR:gles2_cmd_decoder.cc(4431)] [GroupMarkerNotSet(crbug.com/242999)!:D088433BA20D0000]GL ERROR :GL_INVALID_OPERATION : glBindTexture: id not generated by glGenTextures (There was nothing in dmesg when this happened.) So far, so problematic. But I upgraded Chromium to r331233 today and it got *ever* so much worse. The outward symptoms were the same -- until X crashed with an obvious oops-I-didn't-check-errno error: Fatal server error: [354365.137] (EE) failed to map pixmap -22 In dmesg, we see rather a lot of complaining: May 23 21:59:12 mutilate warning: : [353427.133393] radeon 0000:01:00.0: evergreen_surface_check_2d:278 texture pitch 128 invalid must be aligned with 512 May 23 21:59:12 mutilate warning: : [353427.133402] radeon 0000:01:00.0: evergreen_cs_track_validate_texture:827 texture invalid 0x01ec03c1 0x40000013 0x060a0000 0x00000000 0x80000000 0x800304da May 23 21:59:12 mutilate err: : [353427.133407] [drm:radeon_cs_ioctl] *ERROR* Invalid command stream ! May 23 21:59:13 mutilate err: : [353428.036913] [TTM] Could not find buffer object to map May 23 22:02:03 mutilate err: : [353598.745908] [drm:radeon_cs_parser_relocs] *ERROR* gem object lookup failed 0x421 May 23 22:02:03 mutilate err: : [353598.745917] [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -2! May 23 22:02:03 mutilate err: : [353598.838717] [drm:radeon_cs_parser_relocs] *ERROR* gem object lookup failed 0x421 May 23 22:02:03 mutilate err: : [353598.838727] [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -2! May 23 22:02:03 mutilate err: : [353598.876327] [drm:radeon_cs_parser_relocs] *ERROR* gem object lookup failed 0x421 May 23 22:02:03 mutilate err: : [353598.876336] [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -2! May 23 22:02:11 mutilate err: : [353606.091591] [drm:radeon_cs_parser_relocs] *ERROR* gem object lookup failed 0x5f May 23 22:02:11 mutilate err: : [353606.091600] [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -2! May 23 22:02:11 mutilate err: : [353606.106477] [drm:radeon_cs_parser_relocs] *ERROR* gem object lookup failed 0x5f May 23 22:02:11 mutilate err: : [353606.106491] [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -2! May 23 22:02:11 mutilate err: : [353606.255578] [drm:radeon_cs_parser_relocs] *ERROR* gem object lookup failed 0x5f May 23 22:02:11 mutilate err: : [353606.255586] [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -2! May 23 22:02:15 mutilate err: : [353610.061328] [drm:radeon_cs_parser_relocs] *ERROR* gem object lookup failed 0x5f May 23 22:02:15 mutilate err: : [353610.061341] [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -2! May 23 22:02:15 mutilate warning: : [353610.346573] radeon 0000:01:00.0: evergreen_cs_track_validate_cb:477 cb[0] bo too small (layer size 1148928, offset 0, max layer 1, bo size 8192, slice 4487) May 23 22:02:15 mutilate warning: : [353610.346581] radeon 0000:01:00.0: evergreen_cs_track_validate_cb:481 problematic surf: (704 408) (0 4 1 0 0 4 3) May 23 22:02:15 mutilate warning: : [353610.346584] radeon 0000:01:00.0: evergreen_packet3_check:1970 invalid cmd stream 454 May 23 22:02:15 mutilate err: : [353610.346589] [drm:radeon_cs_ioctl] *ERROR* Invalid command stream ! May 23 22:02:15 mutilate err: : [353610.667843] [drm:radeon_cs_parser_relocs] *ERROR* gem object lookup failed 0x62 May 23 22:02:15 mutilate err: : [353610.667856] [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -2! May 23 22:02:15 mutilate err: : [353610.846176] [drm:radeon_cs_parser_relocs] *ERROR* gem object lookup failed 0x5f May 23 22:02:15 mutilate err: : [353610.846189] [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -2! May 23 22:02:15 mutilate err: : [353610.847112] [drm:radeon_cs_parser_relocs] *ERROR* gem object lookup failed 0x5f May 23 22:02:15 mutilate err: : [353610.847118] [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -2! May 23 22:02:15 mutilate err: : [353610.863055] [drm:radeon_cs_parser_relocs] *ERROR* gem object lookup failed 0x5f May 23 22:02:15 mutilate err: : [353610.863064] [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -2! May 23 22:02:15 mutilate err: : [353610.865096] [drm:radeon_cs_parser_relocs] *ERROR* gem object lookup failed 0x5f May 23 22:02:15 mutilate err: : [353610.865103] [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -2! May 23 22:02:15 mutilate err: : [353610.879232] [drm:radeon_cs_parser_relocs] *ERROR* gem object lookup failed 0x5f May 23 22:02:15 mutilate err: : [353610.879240] [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -2! May 23 22:02:15 mutilate err: : [353610.879883] [drm:radeon_cs_parser_relocs] *ERROR* gem object lookup failed 0x5f May 23 22:02:15 mutilate err: : [353610.879888] [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -2! May 23 22:02:16 mutilate err: : [353610.895706] [drm:radeon_cs_parser_relocs] *ERROR* gem object lookup failed 0x5f May 23 22:02:16 mutilate err: : [353610.895714] [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -2! May 23 22:02:16 mutilate err: : [353610.896413] [drm:radeon_cs_parser_relocs] *ERROR* gem object lookup failed 0x5f May 23 22:02:16 mutilate err: : [353610.896418] [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -2! May 23 22:04:50 mutilate err: : [353765.784060] [drm:radeon_cs_parser_relocs] *ERROR* gem object lookup failed 0x185 May 23 22:04:50 mutilate err: : [353765.784067] [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -2! May 23 22:04:55 mutilate err: : [353770.520155] [drm:radeon_cs_parser_relocs] *ERROR* gem object lookup failed 0x185 May 23 22:04:55 mutilate err: : [353770.520218] [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -2! May 23 22:04:57 mutilate err: : [353772.122908] [drm:radeon_cs_parser_relocs] *ERROR* gem object lookup failed 0x50c May 23 22:04:57 mutilate err: : [353772.122916] [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -2! May 23 22:04:57 mutilate warning: : [353772.132150] radeon 0000:01:00.0: evergreen_cs_track_validate_cb:477 cb[0] bo too small (layer size 1148928, offset 0, max layer 1, bo size 8192, slice 4487) May 23 22:04:57 mutilate warning: : [353772.132159] radeon 0000:01:00.0: evergreen_cs_track_validate_cb:481 problematic surf: (704 408) (0 4 1 0 0 4 3) May 23 22:04:57 mutilate warning: : [353772.132230] radeon 0000:01:00.0: evergreen_packet3_check:1970 invalid cmd stream 454 May 23 22:04:57 mutilate err: : [353772.132239] [drm:radeon_cs_ioctl] *ERROR* Invalid command stream ! May 23 22:05:07 mutilate warning: : [353782.686843] radeon 0000:01:00.0: evergreen_cs_track_validate_cb:477 cb[0] bo too small (layer size 1148928, offset 0, max layer 1, bo size 8192, slice 4487) May 23 22:05:07 mutilate warning: : [353782.686851] radeon 0000:01:00.0: evergreen_cs_track_validate_cb:481 problematic surf: (704 408) (0 4 1 0 0 4 3) May 23 22:05:07 mutilate warning: : [353782.686854] radeon 0000:01:00.0: evergreen_packet3_check:1970 invalid cmd stream 454 May 23 22:05:07 mutilate err: : [353782.686859] [drm:radeon_cs_ioctl] *ERROR* Invalid command stream ! May 23 22:05:10 mutilate err: : [353784.942883] [drm:radeon_cs_parser_relocs] *ERROR* gem object lookup failed 0x185 May 23 22:05:10 mutilate err: : [353784.942893] [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -2! [... lots more of this ...] May 23 22:10:39 mutilate warning: : [354113.922155] radeon 0000:01:00.0: vbo resource seems too big for the bo May 23 22:10:39 mutilate warning: : [354113.922166] radeon 0000:01:00.0: vbo resource seems too big for the bo May 23 22:10:39 mutilate warning: : [354113.922170] radeon 0000:01:00.0: vbo resource seems too big for the bo May 23 22:10:39 mutilate warning: : [354113.922173] radeon 0000:01:00.0: vbo resource seems too big for the bo May 23 22:10:39 mutilate warning: : [354113.922176] radeon 0000:01:00.0: vbo resource seems too big for the bo May 23 22:10:39 mutilate warning: : [354113.922179] radeon 0000:01:00.0: vbo resource seems too big for the bo May 23 22:10:39 mutilate warning: : [354113.922182] radeon 0000:01:00.0: vbo resource seems too big for the bo May 23 22:10:39 mutilate warning: : [354113.922185] radeon 0000:01:00.0: vbo resource seems too big for the bo May 23 22:10:39 mutilate warning: : [354113.922188] radeon 0000:01:00.0: vbo resource seems too big for the bo May 23 22:10:39 mutilate warning: : [354113.922191] radeon 0000:01:00.0: vbo resource seems too big for the bo May 23 22:10:39 mutilate warning: : [354113.922194] radeon 0000:01:00.0: vbo resource seems too big for the bo May 23 22:10:39 mutilate warning: : [354113.922196] radeon 0000:01:00.0: vbo resource seems too big for the bo May 23 22:10:39 mutilate warning: : [354113.922199] radeon 0000:01:00.0: vbo resource seems too big for the bo May 23 22:10:39 mutilate warning: : [354113.922202] radeon 0000:01:00.0: vbo resource seems too big for the bo [... more, followed finally by ...] May 23 21:59:12 mutilate warning: : [353427.133393] radeon 0000:01:00.0: evergreen_surface_check_2d:278 texture pitch 128 invalid must be aligned with 512 May 23 21:59:12 mutilate warning: : [353427.133402] radeon 0000:01:00.0: evergreen_cs_track_validate_texture:827 texture invalid 0x01ec03c1 0x40000013 0x060a0000 0x00000000 0x80000000 0x800304da May 23 21:59:12 mutilate err: : [353427.133407] [drm:radeon_cs_ioctl] *ERROR* Invalid command stream ! May 23 21:59:13 mutilate err: : [353428.036913] [TTM] Could not find buffer object to map Following which the X server crashed, as above. If I start Chromium with --disable-gpu, the problem goes away in both cases, so the fault is likely either in Mesa or in the kernel or in the interaction between the two. (I had the Chromium software rendering blacklist overridden years earlier because it was trying to avoid problems that had been long fixed. I've now reversed that decision, obviously!)
(In reply to Nix from comment #10) > FWIW, I have just started seeing behaviour very similar to this, also with an > HD6850, though it is probably a distinct bug because all the software > versions involved are very different. So it would probably be better to file your own report. > This happened after closely-adjoined upgrades of the kernel (from 3.19 to > 4.0.3), the X server (from 1.15.1, yes, I know, it's because of the security > holes I finally upgraded, to 1.17.1), the ATI driver (from 7.3.0-26 to > 7.5.0.68, all "git describe" output from the unmodified trunk), Mesa (from > 10.2.6 to 10.5.5), and LLVM (from 3.3 to 3.5.2), so the fault could, alas, in > theory lie in any or all of these. It would be great if you could narrow that down a bit. The r600g driver doesn't use LLVM, so that's probably not it. I agree it's most likely between Mesa or the kernel, or maybe xf86-video-ati. > Glamor is not in use. Have you tried glamor to see if it happens with that as well? Does Option "ColorTiling2D" "off" in /etc/X11/xorg.conf or the environment variable R600_DEBUG=no2d (or even R600_DEBUG=notiling) for chromium work around the problem? > dpm is, and has been working flawlessly thank you very much, cutting my > desktop's power consumption from 130W to 90W :) over the last year that's > saved at least the price of the beer I owe you for the dpm work, Michel :) Sounds great, but I haven't done any DPM work, I think that beer would have to go to Alex. :)
That's what I was afraid you'd say :) I'll do some judicious downgrades (at least of the easy and most-likely-relevant bit, the kernel) and file a better report. The other bits are mostly coupled, so a kernel downgrade seems like a good place to start.
Found this Mir bug report - https://bugs.launchpad.net/mir/+bug/1144467 The fix is supposedly http://bazaar.launchpad.net/~mir-team/mir/xf86-video-ati-vladmir/revision/2538 I dont know if this has been upstreamed. Posting it here to see if Michel gets any clues seeing this. I don't see the original problem anymore, but I do get the same issue reported here - https://bugs.freedesktop.org/show_bug.cgi?id=90406 with the latest Arch linux build.
(In reply to oogway.droid from comment #13) > Found this Mir bug report - https://bugs.launchpad.net/mir/+bug/1144467 > > The fix is supposedly > http://bazaar.launchpad.net/~mir-team/mir/xf86-video-ati-vladmir/revision/ > 2538 > > I dont know if this has been upstreamed. Posting it here to see if Michel > gets any clues seeing this. AFAICT we mostly have equivalent changes already. The only thing that might be missing is setting the pixmap pitch to what radeon_bo_get_tiling() returns. > I don't see the original problem anymore, but I do get the same issue reported > here - https://bugs.freedesktop.org/show_bug.cgi?id=90406 with the latest Arch > linux build. That's a different issue I think. Resolving this report as fixed, thanks for the followup.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.