home bbs files messages ]

Forums before death by AOL, social media and spammers... "We can't have nice things"

   linux.debian.kernel      Debian kernel discussions      3,019 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 2,756 of 3,019   
   Salvatore Bonaccorso to All   
   Bug#1126671: more info about it (1/18)   
   17 Feb 26 10:30:01   
   
   XPost: linux.debian.bugs.dist   
   From: carnil@debian.org   
      
   Control: tags -1 - moreinfo   
      
   Hi David,   
      
   Thanks for providning the information, I'm forwarding it to the Debian   
   bug, and exceptionally top-posting here. We will have a look.   
      
   Regards   
   Salvatore   
      
   p.s.: please have a look at https://people.kernel.org/tglx/notes   
   about-netiquette   
      
   On Fri, Feb 13, 2026 at 10:09:36PM +0100, Z80user wrote:   
   > Finally I was getting the errors with netconsole, it took me some time to   
   > make it happen and the computer where I receive the messages got flooded   
   > with over 512 lines and it wasn't in front of the computer when the   
   > computer crashed most of the time.   
   > This is on the computer I have at home:   
   >   
   > The dmesg.txt file is the output of dmesg at boot time on the computer   
   > The errors.txt is the messages on the other computer where I receive the   
   > netconsole messages   
   >   
   > and this is what I use to enable the netconsole messages until I see "test"   
   > on the other computer where I execute "netcat -u -l -p 6666"   
   >   
   > sudo modprobe netconsole netconsole=@/enp4s0,6666@10.0.0.221   
   > mkdir /sys/kernel/config/netconsole/target1   
   > echo enp4s0 > /sys/kernel/config/netconsole/target1/dev_name   
   > echo 10.0.0.221 > /sys/kernel/config/netconsole/target1/remote_ip   
   > echo 1 > /sys/kernel/config/netconsole/target1/enabled   
   > echo "test" > /dev/kmsg   
   >   
   > El mar, 10 feb 2026 a las 21:22, Salvatore Bonaccorso ()   
   > escribió:   
   >   
   > > Control: tags -1 + moreinfo   
   > >   
   > > Hi David,   
   > >   
   > > On Mon, Feb 02, 2026 at 03:59:38PM +0100, Z80user wrote:   
   > > > ============================================   
   > > > NOTES to understand the rest of the message:   
   > > > ============================================   
   > > > English isn't my natural language   
   > > > Dates are as YYYY-MM-DD   
   > > >   
   > > > all of the partitions I talking are NTFS partitions, is just because if   
   > > the   
   > > > partition is corrupted I know how to rescue it more easy   
   > > >   
   > > > Type of data corruptions   
   > > > Type 1. the partition can NOT be mount with gnome-disk-utility but it can   
   > > > be mount with the mount command or if it is added to the /mnt/   
   > > > Type 2. the partition can NOT be mount with gnome-disk-utility either   
   > > with   
   > > > mount on /mnt/ but if the partition is copy into a file with "dd" or   
   > > > "ddrescue" and you mount it in a loop device you can read the data from   
   > > it   
   > > > Type 3. the partition can NOT be mount with gnome-disk-utility, mount or   
   > > > the loop device trick and the data is lost unless you used a data rescue   
   > > > software   
   > > >   
   > > > only Type 1 and 2 are present on this problems, so is possible to read it   
   > > > back and isn't data corruption but as normal people can not access it's   
   > > > almost like a data corruption, is needed to use some trick to can read it   
   > > > I didn't have any Type 3 data corruption yet   
   > > >   
   > > > at the end of the first report I wrote a lot of extra info too but as is   
   > > > the first time I made a report I didn't know where to place that info   
   > > > ============================================   
   > > > The video show the problem, sometimes on the top left corner appear a box   
   > > > where I enter the root password to allow changes   
   > > > 0:40 the Operating system didn't leave me to unmount the partition   
   > > because   
   > > > ffmpeg was creating a miniature because "caja" was open.   
   > > >   
   > > > it happen the same on two of my physical computers   
   > > > On the computer on the shop I have (the one that create the report,   
   > > install   
   > > > on 2025-01-09):   
   > > > 6.12.48+deb13-amd64 *1   
   > > > 6.12.57+deb13-amd64 *2   
   > > > 6.12.63+deb13-amd64 *3   
   > > > 6.17.13+deb13-amd64 *4  in use   
   > > >   
   > > > On the computer I have at home: (I install it 2026-11-21)   
   > > > 6.12.41+deb13-amd64 *5   
   > > > 6.12.57+deb13-amd64   
   > > > 6.12.63+deb13-amd64 in use   
   > > >   
   > > > I have a VM on proxmox that don't show that problem with Debian 12 (I   
   > > > create it 2026-01-09)   
   > > > 6.1.0-22-amd64   
   > > > 6.1.0-42-amd64 in use   
   > > >   
   > > >   
   > > > *1 I didn't test it yet   
   > > > *2 it have the problem   
   > > > *3 it have the problem   
   > > > *4 it have the problem, I manually install and this days is the one is   
   > > use   
   > > >   
   > > >   
   > > > -. It's not too easy to replicate it, only if I move a lot of data   
   > > between   
   > > > one disk and another, usually if the NvME drivers are used   
   > > > -. mount and unmount any partition does not create this problems and you   
   > > > can see on the video   
   > > > -. if I reboot or power off the computer and a external HDD is mount, the   
   > > > partition get "corrupted" with the Type 2 of corruption (see the start of   
   > > > the post)   
   > > > -. data lost when the computer is turn off by software   
   > > > -. sometimes data lost when the computer crash is Type 1 on internal   
   > > > devices (I don't know on external devices)   
      
   [continued in next message]   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca