>> i have an old pci analog video capture card that uses bttv
>> it fills the log with timeout errors, 1 or 2 per minute
>> bttv: 2: timeout: drop=725178 irq=4905870/4927747, risc=2014e424, bits: HSYNC
>> each night i run a backup with rsync
>> during that backup
> i have an old pci analog video capture card that uses bttv
> it fills the log with timeout errors, 1 or 2 per minute
> bttv: 2: timeout: drop=725178 irq=4905870/4927747, risc=2014e424, bits: HSYNC
> each night i run a backup with rsync
> during that backup time there are no bt
i have an old pci analog video capture card that uses bttv
it fills the log with timeout errors, 1 or 2 per minute
bttv: 2: timeout: drop=725178 irq=4905870/4927747, risc=2014e424, bits: HSYNC
each night i run a backup with rsync
during that backup time there are no bttv errors
the cameras
On 09/10/24 at 21:10, Jochen Spieker wrote:
Andy Smith:
Hi,
On Wed, Oct 09, 2024 at 08:41:38PM +0200, Franco Martelli wrote:
Do you know whether MD is clever enough to send an email to root when it
fails the device? Or have I to keep an eye on /proc/mdstat?
For more than a decade mdadm has s
Andy Smith:
> Hi,
>
> On Wed, Oct 09, 2024 at 08:41:38PM +0200, Franco Martelli wrote:
>> Do you know whether MD is clever enough to send an email to root when it
>> fails the device? Or have I to keep an eye on /proc/mdstat?
>
> For more than a decade mdadm has shipped with a service that runs i
Hi,
On Wed, Oct 09, 2024 at 08:41:38PM +0200, Franco Martelli wrote:
> Do you know whether MD is clever enough to send an email to root when it
> fails the device? Or have I to keep an eye on /proc/mdstat?
For more than a decade mdadm has shipped with a service that runs in
monitor mode to do thi
On 08/10/24 at 20:40, Andy Smith wrote:
Hi,
On Tue, Oct 08, 2024 at 04:58:46PM +0200, Jochen Spieker wrote:
Why is the RAID still considered healthy? At some point I
would expect the disk to be kicked from the RAID.
This will happen when/if MD can't compensate by reading data from other
m
yours does, but I would definitely question a value of 0 for failed
> (current pending and offline uncorrectable) _and_ reallocated sectors
> for a disk that's reporting I/O errors, for example. _At least_ one of
> those should be >0 for a truthful storage device in that situation.
0 prio class 3
>>| Oct 06 14:28:09 jigsaw kernel: I/O error, dev sdb, sector 9361284864 op etc.
>
> Those aren't sequential, or even exhibiting the same interval from one to
> the next. Am I misinterpreting the data?
No, but the numbers are close to each other and the errors
a
storage. Yes, servo tracks and such things are supposed to catch and
compensate for that; but it might not be quite that bad yet.
Sometimes HDDs fail with a bang, and sometimes they fail with a
whimper.
Also note that some disks actually lie in SMART data. I don't know if
yours does, but I
9361284864 op etc.
Those aren't sequential, or even exhibiting the same interval from one to
the next. Am I misinterpreting the data? Ten of the errors are 1280
sectors after the previous error and five more pairs are 1536 sectors apart;
maybe that's significant?
--
I was 21 years when I
Andy Smith:
> On Tue, Oct 08, 2024 at 04:58:46PM +0200, Jochen Spieker wrote:
>> The way I understand these messages is that some sectors cannot be read
>> from sdb at all and the disk is unable to reallocate the data somewhere
>> else (probably because it doesn't know what the data should be in th
Dan Ritter:
> Jochen Spieker wrote:
>
>> The sector number mentioned at the bottom is increasing during the
>> check.
>
> So it repeats, and it's contiguous. That suggests a flaw in the
> drive itself.
It definitely looks like that:
| Oct 06 14:27:11 jigsaw kernel: I/O error, dev sdb, sector 9
Hi,
On Tue, Oct 08, 2024 at 04:58:46PM +0200, Jochen Spieker wrote:
> The way I understand these messages is that some sectors cannot be read
> from sdb at all and the disk is unable to reallocate the data somewhere
> else (probably because it doesn't know what the data should be in the
> first pl
d
> any of the above kernel messages. But another RAID check triggers these
> messages again, just with different sector numbers. The RAID is still
> healthy, though.
I don't think it is.
> Should this tell me that it is new sectors are dying all the time, or
> should this lea
lt? I don't even see any errors with smartctl:
| # smartctl -a /dev/sdb
| smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.1.0-25-amd64] (local build)
| Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org
|
| === START OF INFORMATION SECTION ===
| Model Family: Wes
On 26/09/24 at 14:53, Jörg-Volker Peetz wrote:
A new microcode for your CPU should be inside of
/usr/lib/firmware/amd-ucode/microcode_amd_fam15h.bin
since it says 'family: 0x15' in your output.
There is a little program on https://github.com/AMDESE/amd_ucode_info to
look into the microcode fil
Hi George,
It would be useful if you paste here full smart attribute stats, command:
sudo smartctl /dev/sda --all
replace sda with correct name as needed
Do "long" SMART test on this drive. It should be able to map out bad
sectors so Linux doesn't see the errors any more. Unless
On 10 Aug 2024 18:20 +1000, from c...@goproject.info (George at Clug):
> I have changed the port it is connected to, and the SATA cable, but
> still the errors follow the disk drive.
So that potentially leaves things like the SATA controller (unlikely),
the power supply (possible) and the
On Sat, 10 Aug 2024 18:20:36 +1000
George at Clug wrote:
> I case there might be a known, fixable, fault that could cause this,
> anyone know what the following errors indicate?
I suspect you have a drive getting ready to die on you, which it may do
at any time.
> Sadly "Unrecove
Hi,
I case there might be a known, fixable, fault that could cause this,
anyone know what the following errors indicate?
Aug 10 17:30:51 srv01 kernel: ata6: EH complete
Aug 10 17:30:54 srv01 kernel: ata6.00: exception Emask 0x0 SAct 0x4000
SErr 0xc action 0x0
Aug 10 17:30:54 srv01 kernel
Hi,
Max Nikulin wrote:
> > > A bit off-topic question. In what wiki page you would expect to find
> > > suggestions to inspect ~/.xsession-errors file and journalctl output?
I wrote:
> > I pasted ".xsession-errors" into the "Search:" field at the up
On 23/07/2024 19:20, Thomas Schmitt wrote:
A bit off-topic question. In what wiki page you would expect to find
suggestions to inspect ~/.xsession-errors file and journalctl output?
I pasted ".xsession-errors" into the "Search:" field at the upper right
corner of any
On Tue, Jul 23, 2024 at 14:20:43 +0200, Thomas Schmitt wrote:
> The only helpful match is
>
>
> https://wiki.debian.org/JigdoOnLive?action=fullsearch&context=180&value=.xsession-errors&fullsearch=Text
>
> "What Does The Log Say?
>...
>I
Hi,
Max Nikulin wrote:
> A bit off-topic question. In what wiki page you would expect to find
> suggestions to inspect ~/.xsession-errors file and journalctl output?
I pasted ".xsession-errors" into the "Search:" field at the upper right
corner of any Debian wiki
On Tue 16 Jul 2024 at 21:35:39 (+0100), mick.crane wrote:
> I installed on a fresh disk the nightly build of Trixie and it works a
> treat and it configured the monitor to it's highest resolution using
> the nouveau module thing.
> Unfortunately I broke my previous Trixie installation trying to get
I installed on a fresh disk the nightly build of Trixie and it works a
treat and it configured the monitor to it's highest resolution using the
nouveau module thing.
Unfortunately I broke my previous Trixie installation trying to get rid
of the nvidia module.
It still works with "startx" but th
en I set the monitors up this way. They were
arranged correctly once I logged in. It's just in lightdm that they were
wrong. They are correct now (I actually don't know why, unless it's
ignoring the hash mark for that line), but I get those errors, which might
be related to it not goi
ly once I logged in. It's just in lightdm that
> they were wrong. They are correct now (I actually don't know why,
> unless it's ignoring the hash mark for that line), but I get those
> errors, which might be related to it not going into suspend overnight.
>
> I m
On Tue, 4 Jun 2024 09:55:51 -0400
Eben King wrote:
> Jun 04 01:57:07 cerberus lightdm[1547009]: xrandr: cannot find mode
> 1920x1200
>
> and so on.
>
> I have three monitors on the onboard connectors. The left
> (1920x1080) is tall, the other two (1920x1200) are wide. The default
> situation
If this is off topic, let me know a better forum please.
Overnight, I'm getting errors every 2s from lightdm.
Jun 04 01:57:01 cerberus lightdm[1546921]: xrandr: cannot find mode 1920x1200
Jun 04 01:57:03 cerberus lightdm[1546948]: xrandr: cannot find mode 1920x1200
Jun 04 01:57:05 cer
I discovred on some BIOSes undocumented features:
Some options can be enabled when set UEFI active, or also when setting a boot
password and a
BIOS password.
Sometimes even new settings appear, when passwords are set. I know, this sounds
weired, but
as I said: this ware undocumented.
Also t
On Tue, Jan 09, 2024 at 04:50:28AM +, Albretch Mueller wrote:
> On 1/6/24, Albretch Mueller wrote:
> > I may not even have an NVMe card in my computer as the manufacturer
> > claims.
>
> My DELL Inspiron 5593 actually does have a M.2 512GB KIOXIA NVMe SSD,
> which I need to use! The problem
On 1/6/24, Albretch Mueller wrote:
> I may not even have an NVMe card in my computer as the manufacturer
> claims.
My DELL Inspiron 5593 actually does have a M.2 512GB KIOXIA NVMe SSD,
which I need to use! The problem, as I described here without getting
a solution for it:
// __ I cannot chang
Sorry, but I don't think I am making much sense out those reported errors.
I may not even have an NVMe card in my computer as the manufacturer claims.
lbrtchx
-physical-layer-id-0010-receiver-id/251840/19>.
>You might find something of interest in it.
Thank you I spent some time going over their discussions which in two
cases were pretty similar to my problem and I decided to post my
problem:
https://forums.developer.nvidia.com/t/dmesg-
On Fri, Jan 5, 2024 at 9:18 AM Albretch Mueller wrote:
>
> I decided to upgrade to Bookworm because I needed to use some NVRAM
> memory supposedly available in my computer, but then my wireless
> Ethernet started to "complain". I initially thought those errors might
> b
I started my computer with the Bullseye Debian live DVD and the dmesg
log is not flooded with such error messages (as it does with
Bookworm):
[ 8095.737532] pcieport :00:1d.0: AER: Multiple Corrected error
received: :01:00.0
[ 8095.737572] r8169 :01:00.0: PCIe Bus Error: severity=Corr
I decided to upgrade to Bookworm because I needed to use some NVRAM
memory supposedly available in my computer, but then my wireless
Ethernet started to "complain". I initially thought those errors might
be related to the lazy use of the Ethernet drivers from Bullseye but
when I star
Hello
On 15.6.2023 7.03, Kushal Kumaran wrote:
On Wed, Jun 14 2023 at 03:55:44 PM, Nicholas Papadonis
wrote:
Hi,
I just cleanly installed Debian 11 and am trying to create a virtual
environment for Python.
I get the following error, does anyone know how to resolve this? Am I
missing some p
Mario Marietto (12023-06-21):
> A rude behavior like yours
The rude person here is you and only you.
--
Nicolas George
@Nicolas George : what about if I don't understand what ? I presume that
between us before all there are some relevant cultural differences. A rude
behavior like yours is not tolerable,since I haven't offended you
personally. I have only expressed opinions based on the cultural view of
the place wh
Mario Marietto (12023-06-20):
> Or am I missing something ?
Yes, a lot.
--
Nicolas George
@nicolas george : you consider yourself a democratic person ? Do you fight
every day for the freedom of speech of other people ? I don't see any
insult from myself. The fact that you see it does not make it is. And what
about your invitation to the other people to ignore me ? I consider this
behavi
Mario Marietto (12023-06-21):
> Probably you call troll what you find difficult to understand ? I'm a
> psychologist,not a troll.
Troll is a behavior, like entitled brat or asshole.
Psychologist is a profession.
They are not incompatible.
I thought a psychologist would know the difference betwe
Mario Marietto (12023-06-20):
> ---> Second, you are asking for help: that means your time is less valuable
> than the time of people who might help you, and the most effort comes from
> you.
>
> it's not a matter of effort : not everything is under our control : If I
> don't know something,I COUL
Probably you call troll what you find difficult to understand ? I'm a
psychologist,not a troll. Try to read and understand. This is the right
method to understand more than what you understand now. If you talk about
troll,you close the door to a lot of interesting topics. Ok,they probably
aren't in
Mario Marietto wrote:
> ---> Second, you are asking for help: that means your time is less
> valuable than the time of people who might help you, and the most
> effort comes from you.
>
> it's not a matter of effort : not everything is under our control :
> If I don't know something,I COULD learn
---> Second, you are asking for help: that means your time is less valuable
than the time of people who might help you, and the most effort comes from
you.
it's not a matter of effort : not everything is under our control : If I
don't know something,I COULD learn MORE,but if I don't know that thin
Mario Marietto (12023-06-20):
> What about if I don't know which kind of information you need ? I'm the
> hobbyist,you are the developer. It's better that you ask what you want to
> know and I try to reply with my limited knowledge.
You are doubly mistaken here.
First, this is a users mailing lis
What about if I don't know which kind of information you need ? I'm the
hobbyist,you are the developer. It's better that you ask what you want to
know and I try to reply with my limited knowledge.
On Tue, Jun 20, 2023 at 4:48 PM Stefan Monnier
wrote:
> > ok,do you have some workaround to propose
> ok,do you have some workaround to propose to me,boys ?
Not before you give more info, no.
Stefan
ok,do you have some workaround to propose to me,boys ? Thank you.
On Tue, Jun 20, 2023 at 3:18 AM Jeffrey Walton wrote:
> On Mon, Jun 19, 2023 at 8:48 PM Stefan Monnier
> wrote:
> >
> > [...]
> > > of=/dev/mmcblk1 status=progress bs=2M but very rarely it wants to
> boot. I
> > > don't understan
On Mon, Jun 19, 2023 at 8:48 PM Stefan Monnier wrote:
>
> [...]
> > of=/dev/mmcblk1 status=progress bs=2M but very rarely it wants to boot. I
> > don't understand where the error is. When I insert the sd card into the
> > slot it beeps and it prepares itself to boot chrome OS from the internal
> >
[...]
> of=/dev/mmcblk1 status=progress bs=2M but very rarely it wants to boot. I
> don't understand where the error is. When I insert the sd card into the
> slot it beeps and it prepares itself to boot chrome OS from the internal
> memory,not Linux from the sd card.
>
> The problem could be system
es itself to boot chrome OS from the internal
memory,not Linux from the sd card.
The problem could be systemd or whatever does that,to check and fix disk
errors because it does not support natively chrome os disk partitions
flags. So it may break those flags after the first boot. So,I want to ask
if the
On Wed, Jun 14 2023 at 03:55:44 PM, Nicholas Papadonis
wrote:
> Hi,
>
> I just cleanly installed Debian 11 and am trying to create a virtual
> environment for Python.
>
> I get the following error, does anyone know how to resolve this? Am I
> missing some packages that need to be installed?
>
>
Am Wed, Jun 14, 2023 at 03:55:44PM -0400 schrieb Nicholas Papadonis:
> File "/home/vboxuser/threading.py", line 3, in
I'm surprised about this file. It should not appear by creating a python
venv.
Best regards
Ulf
ing care of that, I was able to run your
command without any errors on my clean Debian 12 system.
Traceback (most recent call last):
> File "", line 189, in _run_module_as_main
> File "", line 148, in _get_module_details
> File "", line 112, in _get_
Hi,
I just cleanly installed Debian 11 and am trying to create a virtual
environment for Python.
I get the following error, does anyone know how to resolve this? Am I
missing some packages that need to be installed?
1843 [deb12:~]$ python3 -m venv pt
Traceback (most recent call last):
File ""
t; ID=debian
> HOME_URL="https://www.debian.org/";
> SUPPORT_URL="https://www.debian.org/support";
> BUG_REPORT_URL="https://bugs.debian.org/";
>
> Linux me 6.1.0-9-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.27-1 (2023-05-08)
> x86_64 GNU/Linux
&
n.org/support";
BUG_REPORT_URL="https://bugs.debian.org/";
Linux me 6.1.0-9-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.27-1 (2023-05-08)
x86_64 GNU/Linux
I am getting these libqt5 errors.
/../libs/libQt5Core.so.5(_ZN7QObject5eventEP6QEvent+0x82) [0x7f4829cbf6c2]
/../libs/libQt5Wid
__
From: Michael Lee
Sent: Thursday, March 2, 2023 4:30:47 PM
To: debian-user@lists.debian.org
Subject: Boot Errors
While running the stable branch of 64-bit Debian, rebooted into an
alternative OS, but forgot to unmount a USB device beforhand. Shutdown
was taking too long, so forced it anyway. Now
While running the stable branch of 64-bit Debian, rebooted into an
alternative OS, but forgot to unmount a USB device beforhand. Shutdown
was taking too long, so forced it anyway. Now when I try to start
Linux, I get these error messages:
[1.922640] platform gpio_ich.2.auto: failed to claim resou
Roberto C. Sánchez writes:
> On Thu, Feb 16, 2023 at 10:37:00AM +0100, Andreas Leha wrote:
>>
>> Dear Tomas,
>>
>> Thanks for the swift reply!
>>
>> OK, then I should do `quilt pop -a` before the second compilation,
>> right?
>>
>> But that leads to another error message:
>>
>
> This can be
On Thu, Feb 16, 2023 at 10:37:00AM +0100, Andreas Leha wrote:
>
> Dear Tomas,
>
> Thanks for the swift reply!
>
> OK, then I should do `quilt pop -a` before the second compilation,
> right?
>
> But that leads to another error message:
>
This can be considered a bug in the package. The idea i
> LANG=C debuild -us -uc
>>
>>
>> Re-compiling a second time errors out, though:
>>
>> > LANG=C debuild -us -uc
>> (skipped lines)
>> dpkg-source: info: using source format '3.0 (quilt)'
>> dpkg-source: info: bui
On Thu, Feb 16, 2023 at 10:05:54AM +0100, Andreas Leha wrote:
> Dear all,
>
> I am re-compiling xscreensaver.
>
> Re-compiling once works fine:
>
> apt-get source xscreensaver
> cd xscreensaver-6.0.6+dfsg1
> LANG=C debuild -us -uc
>
>
> R
Dear all,
I am re-compiling xscreensaver.
Re-compiling once works fine:
apt-get source xscreensaver
cd xscreensaver-6.0.6+dfsg1
LANG=C debuild -us -uc
Re-compiling a second time errors out, though:
> LANG=C debuild -us -uc
(skipped lines)
dpkg-source: info: us
On 06/02/2023 00:11, Richmond wrote:
Max Nikulin writes:
On 05/02/2023 03:12, Richmond wrote:
The errors about sr0 come before the stuff about resume.
Does the following command generate similar errors (taken from initrd
scripts, UUID is intentionally not from the set of existing
partitions
Max Nikulin writes:
> On 05/02/2023 03:12, Richmond wrote:
>> The errors about sr0 come before the stuff about resume.
>
> Does the following command generate similar errors (taken from initrd
> scripts, UUID is intentionally not from the set of existing
> partitions)?
On 05/02/2023 03:12, Richmond wrote:
The errors about sr0 come before the stuff about resume.
Does the following command generate similar errors (taken from initrd
scripts, UUID is intentionally not from the set of existing partitions)?
blkid -l -t UUID=----
/02/2023 01:47, Richmond wrote:
>>>>>>> It might be a good way for someone to reproduce the error on some
>>>>>>> other
>>>>>>> machine. I have no problems with the CD/DVD writer and have used it a
>>>>>>> few time
t;> >> It might be a good way for someone to reproduce the error on some
>> >> >> other
>> >> >> machine. I have no problems with the CD/DVD writer and have used it a
>> >> >> few times recently.
>> >> >
>> >> >
to reproduce the error on some
> >> >> other
> >> >> machine. I have no problems with the CD/DVD writer and have used it a
> >> >> few times recently.
> >> >
> >> > Do you see the same errors if kernel command line is edited from
ne. I have no problems with the CD/DVD writer and have used it a
>> >> few times recently.
>> >
>> > Do you see the same errors if kernel command line is edited from grub
>> > to pass non-existing UUID specified in the resume=UUID=... argument?
>> &g
the swap space, having commented-it-out
> of fstab. So I imagin that the scripts are the same.
I rather meant the run which you meantioned in your mail of Thu,
02 Feb 2023 14:05:37 +:
> > > sudo update-initramfs -u
> > > After I did this, the errors went away.
It is poss
er and have used it a
> >> few times recently.
> >
> > Do you see the same errors if kernel command line is edited from grub
> > to pass non-existing UUID specified in the resume=UUID=... argument?
> > It might be a quick way to reproduce the issue.
>
> I looked i
Max Nikulin writes:
> On 03/02/2023 01:47, Richmond wrote:
>> It might be a good way for someone to reproduce the error on some
>> other
>> machine. I have no problems with the CD/DVD writer and have used it a
>> few times recently.
>
> Do you see the same errors
"Thomas Schmitt" writes:
> Hi,
>
> Richmond wrote:
>> /tmp/initrd21/scripts/local:[ "${quiet?}" != "y" ] && log_begin_msg
>> "Running /scripts/local-block"
>> [...]
>> local_block()
>> {
>>[ "${quiet?}" != "y" ] && log_begin_msg "Running /scripts/local-block"
>>run_scripts /s
Hi,
Richmond wrote:
> /tmp/initrd21/scripts/local:[ "${quiet?}" != "y" ] && log_begin_msg
> "Running /scripts/local-block"
> [...]
> local_block()
> {
>[ "${quiet?}" != "y" ] && log_begin_msg "Running /scripts/local-block"
>run_scripts /scripts/local-block "$@"
> [...]
> Then
On 03/02/2023 01:47, Richmond wrote:
It might be a good way for someone to reproduce the error on some other
machine. I have no problems with the CD/DVD writer and have used it a
few times recently.
Do you see the same errors if kernel command line is edited from grub to
pass non-existing
sorry, replied to wrong list.
On Fri, 03 Feb 2023 16:55:18 -0500,
John Covici wrote:
>
> For instance I just got a post from Freedom Scientific which had the
> announcement in the Email and also link to the post.
> On Fri, 03 Feb 2023 15:28:55 -0500,
> David Wright wrote:
> >
> > On Fri 03 Feb 2
For instance I just got a post from Freedom Scientific which had the
announcement in the Email and also link to the post.
On Fri, 03 Feb 2023 15:28:55 -0500,
David Wright wrote:
>
> On Fri 03 Feb 2023 at 13:12:05 (+), Richmond wrote:
> > David Wright writes:
> > > On Thu 02 Feb 2023 at 21:58:
On Fri 03 Feb 2023 at 13:12:05 (+), Richmond wrote:
> David Wright writes:
> > On Thu 02 Feb 2023 at 21:58:54 (+), Richmond wrote:
> >> "Thomas Schmitt" writes:
> >> >
> >> > (If not there, then in the /scripts/local-block directory of the initrd
> >> > ?)
> >>
> >> I don't know how I w
"Thomas Schmitt" writes:
> Hi,
>
> Richmond wrote:
>> No local block. :-?
>
> Maybe you can find our from where the message comes:
>
> grep -r 'Running.*scripts.*local-block' /tmp/initrd21
>
>
grep -r 'Running.*scripts.*local-block' /tmp/initrd21
/tmp/initrd21/scripts/local:[ "${quiet?}"
Hi,
Richmond wrote:
> No local block. :-?
Maybe you can find our from where the message comes:
grep -r 'Running.*scripts.*local-block' /tmp/initrd21
Have a nice day :)
Thomas
David Wright writes:
> On Thu 02 Feb 2023 at 21:58:54 (+), Richmond wrote:
>> "Thomas Schmitt" writes:
>> >
>> > (If not there, then in the /scripts/local-block directory of the initrd ?)
>>
>> I don't know how I would look in that. Is it in RAM at boot time?
>
>Choose your kernel ↓
Michel Verdier writes:
> Le 2 février 2023 Richmond a écrit :
>
>> There is no such file. Earlier I ran this:
>>
>> find / -print|grep "scripts/local-block"
>>
>> and it found nothing, which led me to believe it is some temporary file...
>>>
>>> (If not there, then in the /scripts/local-block dir
On Thu 02 Feb 2023 at 21:58:54 (+), Richmond wrote:
> "Thomas Schmitt" writes:
> >
> > (If not there, then in the /scripts/local-block directory of the initrd ?)
>
> I don't know how I would look in that. Is it in RAM at boot time?
Choose your kernel ↓↓Pick any name ↓↓
Le 2 février 2023 Richmond a écrit :
> There is no such file. Earlier I ran this:
>
> find / -print|grep "scripts/local-block"
>
> and it found nothing, which led me to believe it is some temporary file...
>>
>> (If not there, then in the /scripts/local-block directory of the initrd ?)
its part o
"Thomas Schmitt" writes:
> Indeed. But why should only the kernel be brain damaged ?
>
> (I expect some generic UUID searcher for block devices. Probably the sr
> devices are near the end of its iteration. So one would not see any
> protest in the log if the UUID is found on the device which is t
near the end of its iteration. So one would not see any
protest in the log if the UUID is found on the device which is tried
earlier.)
> But also it is quite a coincidence if the errors
> occur when the resume space is messed up, and they go away when it is
> fixed. That has happene
piorunz writes:
> On 02/02/2023 14:05, Richmond wrote:
>> After I did this, the errors went away.
>> I don't know why the errors reference sr0, it's a mystery.
>
> They will most likely come back, this error is related to optical
> drive, nothing to do with s
On 02/02/2023 14:05, Richmond wrote:
After I did this, the errors went away.
I don't know why the errors reference sr0, it's a mystery.
They will most likely come back, this error is related to optical drive,
nothing to do with swap space.
--
With kindest rega
Richmond writes:
> It may be a coincidence but yesterday I installed some
> libguestfs-tools. Now I see errors when booting, which also appear in
> /var/log/messages:
>
> kernel: [9.506798] sr 3:0:0:0: [sr0] tag#12 FAILED Result:
> hostbyte=DID_OK driverbyte=DRIVER_SENSE c
Hi,
Thomas Amm wrote:
> First you might remove the pktcdvd module:
> Not sure if it causes this specific problem but it is for pre-
> growisofs CD-RW writing.
The packet writing device bundles smaller write requests in larger chunks
and ensures to write only at addresses and with sizes which are
On Mon, 2023-01-23 at 17:34 +, Richmond wrote:
> Sven Joachim writes:
>
> > On 2023-01-23 16:13 +, Richmond wrote:
> >
> > > I put a dvd in and mounted it. Then rebooted. I saw these
> > > messages:
> > >
> > > [ 756.539018] pktcdvd: pktcdvd0: writer mapped to sr0
> > > [ 3.744658
Hi,
piorunz wrote:
> read attempts continue,
Obviously your drive groper is different from Richmond's. Both get lured
into their activities by the kernel bugs.
> Inserting blank disc on every reboot is not a solution in my opinion. And I
> didn't verified it myself,
It would be interesting to
- read attempts continue, please see my
earlier messages in this thread, including original bug report 2 years
ago. dmesg is infested with these errors in red, periodically there is
another one, triggered by something, it goes on forever.
Inserting blank disc on every reboot is not a solution in my
1 - 100 of 1716 matches
Mail list logo
