[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1041143: marked as done (Module for accelerometer lis3lv02d isn't loaded at start for Dell Mobile Precision M6700; is this right?)

Your message dated Tue, 01 Aug 2023 01:09:37 +0200
with message-id <6531216.tM3a2QDmDi@bagend>
and subject line Re: Debian's BTS is not for regular user questions
has caused the Debian Bug report #1041143,
regarding Module for accelerometer lis3lv02d isn't loaded at start for Dell Mobile Precision M6700; is this right?
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1041143: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041143
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-image-6.1.0-10-amd64
Version: 6.1.37-1
Severity: wishlist
In the journal we find the following warning concerning an accelerometer (the last line is orange): 

…
Jul 15 03:35:14 AnonymizedMachneName kernel: i801_smbus 0000:00:1f.3: SMBus using PCI interrupt 
Jul 15 03:35:14 AnonymizedMachneName kernel: ACPI: bus type USB registered
Jul 15 03:35:14 AnonymizedMachneName kernel: ACPI: video: Video Device [VID] (multi-head: yes rom: no post: no) Jul 15 03:35:14 AnonymizedMachneName kernel: i801_smbus 0000:00:1f.3: Accelerometer lis3lv02d is present on SMBus but its address is unknown, skipping registration 
…
The machine is a Dell Mobile Precision M6700. BIOS is at its latest available version A20. As the machine experiences high-level issues later at boot (e.g., some services can't start), we wish to be sure about the contribution of the issues warned about here. How much do we have to worry? During boot, /sys/devices/platform does NOT have files referring to lis3lv02d. 

Trying to `modprobe -v lis3lv02d` succeeds and yields new

/sys/kernel/btf/lis3lv02d
/sys/module/lis3lv02d

Trying to `modprobe -v lis3lv02d_i2c` generates even more contents in /sys:

/sys/kernel/btf/lis3lv02d_i2c
/sys/bus/i2c/drivers/lis3lv02d_i2c
/sys/module/lis3lv02d_i2c
/sys/module/lis3lv02d_i2c/drivers/i2c:lis3lv02d_i2c
/sys/module/lis3lv02d/holders/lis3lv02d_i2c
So the kernel might be unaware of the accelerometer by default (which is probably not ideal because, e.g., the we might wish to cut/reduce power to, say, fans, when the laptop starts falling/vibrating (and therefore also reduce the power consumption by various chips, e.g., reducing the CPU frequency) and restore the settings after fall).
Moreover, the documentation on lis3lv02d present in /usr/share/doc/linux-doc-6.1 talks about HP laptops with this accelerometer. Here, we have a Dell laptop. So IF the driver is correct for our accelerometer (how do we find this out with certainty?), the documentation has to be adapted. 

Gratefully,
AlMa

--- End Message ---
--- Begin Message --- 
On Sat, 15 Jul 2023 03:13:51 +0200 AlMa <AlMa0@ro.ru> wrote:
> In the journal I see two yellow lines (which, probably, constitute 
> warnings) directly following one another:
> … 
> Later in the journal we see a white line
> … 
> 
> As the machine (Dell Mobile Precision M6700) experiences various 
> high-level issues later in the boot process, I'm unsure about the 
> contribution of the two issues in the log.  Which software or hardware 
> problems do these warnings inform us about?  Any fix or remedy?

You filed various bugs talking about yellow and white lines of which you 
suspect that yellow may be a warning (which you should be able to find out by 
yourself if that's the case).

The Debian BTS is not meant to ask questions like "what could this message 
tell us?". Put it in a search engine or use one of the MANY user support 
options for that. Computers/Linux put various debug/informational/warning msgs 
in various logs, which _could_ be helpful in case there's an actual ERROR.

But the only *potential* error I see here is "various high-level issues", 
which is so vague so that's completely useless and inactionable.

So I'm going to close this and similar vague bug reports, which aren't 
actually bug reports, but just questions.
And all those ACPI errors? Contact the machine vendor as they're the only ones 
who could resolve such issue. Linux is only reporting that there are issues.

"If we believe Jean Delvare" ... and Jean Delvare response in that bug report:
"This is not a support forum, sorry. If you need help, use support forums and 
mailing lists." ...

From 'bug' #1041191: "Will the fingerprint sensor not work?"
I _assume_ you have the device/machine, so why don't you try it out?
*IF* it turns out it doesn't work then you first use a search engine to see if 
you can make it work yourself by trying out various hints you'll undoubtedly 
find and if that doesn't make it work, *THEN* you have something to file a bug 
about.

You filed *8* different 'bugs' which (almost?) all are about a Dell Mobile 
Precision M6700 ... and not once did you say what actual problem you 
experienced?!?

If you file a bug, you're (basically) asking (several) people to read about a 
problem you're having and then subsequently (potentially) spend time to fix 
that/those problem(s).
Please be more considerate with other people's time and only file bugs for 
*actual* problems and then provide enough information/context so that they
can actually (potentially) act upon it and help you fix that problem.

I initially intended to respond to some actual problems you (also) reported, 
but I've already spend way too much time on these non-issues, so I'm done.

Attachment: signature.asc
Description: This is a digitally signed message part.


--- End Message ---
Reply to: