| Summary: | [ILK]I-G-T/gem_cs_prefetch warning with "<6>[ 503.521104] VFS: file-max limit 376470 reached ” | ||||||
|---|---|---|---|---|---|---|---|
| Product: | DRI | Reporter: | Guang Yang <guang.a.yang> | ||||
| Component: | DRM/Intel | Assignee: | Daniel Vetter <daniel> | ||||
| Status: | CLOSED NOTABUG | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||
| Severity: | normal | ||||||
| Priority: | medium | ||||||
| Version: | unspecified | ||||||
| Hardware: | Other | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| i915 platform: | i915 features: | ||||||
| Attachments: |
|
||||||
An intentional side-effect of the test as it creates obscene numbers of buffers to fill all memory. As it runs as root, it is unaffected by those limits, but any other program try to run in parallel is. Is it possible to disappear such info since it's not a actual issue, or change its level to 7 in dmesg? As we understood, anything in the dmesg which is high than level 6 can seem as a issue. It's a core vfs warning, so we can't touch it. The test could in theory be refactored, but it is a working test so I'd rather not... The warning will only occur if something else executes on the box, which is a bad sign for a test machine. We should just grep "drm:.*" in the dmesg. Closing old verified. |
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.
Created attachment 70402 [details] dmesg info with gem_cs_prefetch System Environment: -------------------------- Platform: IronLake Kernel: (drm-intel-next-queued)2d60696d645809c6a1a737c31898b3e630d7d495 Bug detailed description: ------------------------- On IronLake platform, after running gem_cs_prefetch dmesg -r shows: <6>[ 503.521104] VFS: file-max limit 376470 reached I attach the dmesg.