Bug#972678: initramfs-tools: bad error message when zstd requested but not installed

[積丹尼 Dan Jacobson]

update-initramfs: Generating /boot/initrd.img-5.16.0-6-amd64
W: No zstd in /usr/bin:/sbin:/bin, using gzip

Shouldn't it just not remind the user?

Bug#947356: Please have upstream fix this

[積丹尼 Dan Jacobson]

Please have upstream fix this soon. Thanks.

Bug#953522: W: Possible missing firmware /lib/firmware/rtl_nic/rtl8125a-3.fw for module r8169

[積丹尼 Dan Jacobson]

Package: src:linux
Version: 5.4.19-1

No idea where to report this.

# update-initramfs -u
update-initramfs: Generating /boot/initrd.img-5.4.0-4-amd64
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8125a-3.fw for module 
r8169

Bug#948357: thousands of identical lookup_builtin_file warnings

[積丹尼 Dan Jacobson]

Package: initramfs-tools-core
Version: 0.135
Severity: important

$ aptitude full-upgrade gives thousands of identical
depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open 
builtin file '/lib/modules/5.4.0-2-amd64/modules.builtin.bin'
depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open 
builtin file '/lib/modules/5.4.0-2-amd64/modules.builtin.bin'
depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open 
builtin file '/lib/modules/5.4.0-2-amd64/modules.builtin.bin'

so many that it pushed everything else off the screen.

One would be enough. Not thousands.

Bug#947356: Kernel install warnings

[積丹尼 Dan Jacobson]

Kernel install warns
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8125a-3.fw for module 
r8169

Bug#925891: AMD/ATI Carrizo driver incorrectly detected

[積丹尼 Dan Jacobson]

unmerge 925891
retitle 925891 AMD/ATI Carrizo driver incorrectly detected?
thanks

Now making the incorrect driver detection a separate issue.

All I know is with that minimal install, it somehow assumes the correct
driver is present, or it is, but it uses it wrong. See also
https://wiki.debian.org/AtiHowTo . Anyway the result is a successful
install, but a black screen upon boot.

I'm delaying completing my installation so I can help somebody fix this.
I can work around it myself.
Just tell me when you don't need my help anymore for testing the
installer on this, so I can proceed with my installation. Thanks.

Bug#926149: AMD: Add nomodeset kernel parameter to avoid black screen

[積丹尼 Dan Jacobson]

clone 926149 -1
retitle -1 [AMD/ATI] Carrizo driver incorrectly detected
retitle 926149 Add nomodeset kernel parameter for recovery boot grub entry
thanks

> "BH" == Ben Hutchings  writes:

BH> However it might be reasonable to add "nomodeset" to the command line
BH> in GRUB's "recovery" boot menu items.

Bug#926149: AMD: Add nomodeset kernel parameter to avoid black screen

[積丹尼 Dan Jacobson]

> However it might be reasonable to add "nomodeset" to the command line
> in GRUB's "recovery" boot menu items.

OK, great. Now all that is left is for me to help you figure out why
the installer incorrectly detects that the drivers are available, etc.

I am able to workaround all this, I just want to help you finish testing before 
I
finish installing my system and thus will not be able to help anymore.

Bug#926149: AMD: Add nomodeset kernel parameter to avoid black screen

[積丹尼 Dan Jacobson]

And lo and behold, in /etc/grub.d/10_linux :

if [ "$ubuntu_recovery" = 1 ]; then
GRUB_CMDLINE_LINUX_RECOVERY="$GRUB_CMDLINE_LINUX_RECOVERY nomodeset"
fi

Bug#926149: AMD: Add nomodeset kernel parameter to avoid black screen

[積丹尼 Dan Jacobson]

> "BH" == Ben Hutchings  writes:

BH> The installer normally uses a dumb framebuffer driver (probably efifb
BH> on this system) that is built into the kernel.  This is too low-
BH> performance for a proper desktop.

OK, the installer could first double check that the framebuffer driver
it intends to write to the installation really will work, by telling the
user:

"5 seconds please, while we test your framebuffer ability."

During which it could launch its proposed framebuffer,
see if /proc/sys/.../{voltage or number of lit pixels, etc.} has
suddenly dropped to zero, indicating a black screen, and then back out
of that choice. Or simply ask the user "in a moment you will be asked if
you saw a black screen".

Anyway, if the installer thinks a certain video mode is so cool that it
sets it up as what will be used when the new system boots, then why
doesn't the installer try a "taste of its own medicine," and use it
right away when running the graphical and non-graphical interactive
installs. I mean if it is so confident that it will work...

Or the kernel itself certainly should have a way to do "OK, for the next
operation, check if it has made the screen (which was not black) now
become suddenly black? If so, back out."

Anyway certainly
https://lists.opensuse.org/opensuse-factory/2011-09/msg00732.html
has it right at least about the *2nd (recovery mode) grub entries*.
They should certainly have nomodeset added!

Bug#926149: AMD: Add nomodeset kernel parameter to avoid black screen

[積丹尼 Dan Jacobson]

So the question becomes why does that installer ISO know how to properly deal
with the

BH> 00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Carrizo [1002:9874] (rev e6)
BH> Subsystem: ASUSTeK Computer Inc. Device [1043:8719]

giving nice splash screens, a snappy graphical install interface, crisp
non-graphical rescue shells etc. ... but then the system that it
installs oddly cannot deal with that hardware anymore? (Black screen.)

Note the whole experiment was done offline as to reduce outside
interference in isolating the problem.

Bug#926149: AMD: Add nomodeset kernel parameter to avoid black screen

[積丹尼 Dan Jacobson]

BH> Please send the output of "lspci -vnn" for the system that shows this
BH> problem.

Would lspci -knn be good enough for now?:
https://bugs.debian.org/cgi-bin/bugreport.cgi?att=0;bug=925556;filename=logs.gz;msg=50

Bug#766385: Generating /boot/initrd.img-* twice in the same full-upgrade

[積丹尼 Dan Jacobson]

Doesn't happen every time, only sometimes.

# egrep init.*Genera\|Log\ started /var/log/apt/term.log
Log started: 2018-09-23  09:51:40
update-initramfs: Generating /boot/initrd.img-4.18.0-1-686-pae
update-initramfs: Generating /boot/initrd.img-4.18.0-1-686-pae



term.log.gz
Description: application/gzip

Bug#906310: video=SVIDEO-1:d

[積丹尼 Dan Jacobson]

Preliminary results show that the video=SVIDEO-1:d boot line workaround
is working...

Bug#906310: actually vblank wait timed out on crtc 0

[積丹尼 Dan Jacobson]

rename 906310 vblank wait timed out on crtc 0
thanks

It turns out this is just still the
vblank wait timed out on crtc 0
bug seen on kernels later than 4.15



syslog.gz
Description: syslog


Xorg.0.log.gz
Description: Xlog

Bug#906310: notified xrandr source (7.7+8)

[積丹尼 Dan Jacobson]

I created https://gitlab.freedesktop.org/xorg/app/xrandr/issues/40 .

Bug#905607: certain crash about a half an hour browsing Facebook with chromium

[積丹尼 Dan Jacobson]

Package: src:linux
Version: 4.17.8-1

Just wanted to let you know that after about a half an hour browsing
Facebook with chromium, (I didn't try other browsers) the kernel always crashes.

There are never any logs to send. The system just freezes for 10 seconds
and reboots. Nothing gets recorded about the crash.

Bug#903679: happens in all of 4.16.

[積丹尼 Dan Jacobson]

Happens in all of 4.16.
4.15 unaffected.

Bug#903679: Bad: 4.16.16-2

[積丹尼 Dan Jacobson]

Problem turns out not to be related to xrandr.
Problem occurs when starting or stopping X windows.
OK:  linux-image-4.16.0-1-amd64:amd64 4.16.5-1
Bad: linux-image-4.16.0-2-amd64:amd64 4.16.16-2

Bug#903679: /build/linux-hny3SU/linux-4.16.5/drivers/gpu/drm/drm_vblank.c:1073 drm_wait_one_vblank+0x16e/0x180 [drm]

[積丹尼 Dan Jacobson]

Package: src:linux
Version: 4.16.16-2
Severity: important

Problem occurs with
vmlinuz-4.16.0-2-amd64
No problem in
vmlinuz-4.15.0-3-amd64

Problem occurs if user puts
xrandr --output LVDS-1 --mode 1024x576
in his ~/.xsession
file.
Problem doesn't occur if user just invokes
xrandr --output LVDS-1 --mode 1024x576
from the command line in an xterm.

Problem is
vblank wait timed out on crtc 0
[drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* 
[CRTC:37:pipe A] flip_done timed out
WARNING: CPU: 0 PID: 671 at 
/build/linux-hny3SU/linux-4.16.5/drivers/gpu/drm/drm_vblank.c:1073 
drm_wait_one_vblank+0x16e/0x180 [drm]

Using video=SVIDEO-1:d doesn't help.

Anyway the computer must be rebooted and the line taken out of .xsession
to be usable.

vblank wait timed out on crtc 0
WARNING: CPU: 1 PID: 671 at 
/build/linux-hny3SU/linux-4.16.5/drivers/gpu/drm/drm_vblank.c:1073 drm_wa

Modules linked in: arc4 brcmsmac intel_rapl cordic brcmutil 
x86_pkg_temp_thermal b43 intel_powerclamp
cm irqbypass btintel bluetooth crct10dif_pclmul crc32_pclmul drbg 
ghash_clmulni_intel cfg80211 ssb pc
tel_cstate iTCO_wdt videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 
ecdh_generic videobuf2_common i
b_ms media memstick intel_rapl_perf snd_hda_codec_hdmi snd_hda_codec_conexant 
snd_hda_codec_generic j
nd_hwdep snd_pcm ideapad_laptop i915 snd_timer pcspkr mei_me mei evdev 
serio_raw snd sg drm_kms_helpe
 lpc_ich video ac drm button battery i2c_algo_bit
 ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 crc32c_generic fscrypto ecb 
crypto_simd cryptd gl
_usb_sdmmc mmc_core rtsx_usb sr_mod cdrom sd_mod uas usb_storage ahci libahci 
crc32c_intel psmouse i2
d xhci_hcd alx mdio usbcore usb_common thermal
CPU: 1 PID: 671 Comm: Xorg Tainted: GW4.16.0-1-amd64 #1 Debian 
4.16.5-1
Hardware name: LENOVO 20150/Product Name, BIOS 5ECN40WW(V3.06) 10/22/2012
RIP: 0010:drm_wait_one_vblank+0x16e/0x180 [drm]
RSP: 0018:a86701313800 EFLAGS: 00010286
RAX:  RBX: 91aa25a5 RCX: 
RDX:  RSI: 0002 RDI: 0202
RBP:  R08:  R09: 001f
R10: a867013136b8 R11:  R12: 
R13: 337f R14: 91aa20b8c808 R15: 91aa25a5
FS:  7fbd8b29da40() GS:91aa2f24() knlGS:
CS:  0010 DS:  ES:  CR0: 80050033
CR2: 55d2787f99cc CR3: 0001a4450001 CR4: 000606e0
Call Trace:
 ? finish_wait+0x80/0x80
 ironlake_crtc_enable+0x4bb/0xcd0 [i915]
 intel_update_crtc+0x39/0x90 [i915]
 intel_update_crtcs+0x47/0x60 [i915]
 intel_atomic_commit_tail+0x1dd/0xd30 [i915]
 intel_atomic_commit+0x21f/0x2d0 [i915]
 restore_fbdev_mode_atomic+0x1ac/0x210 [drm_kms_helper]
 drm_fb_helper_restore_fbdev_mode_unlocked+0x45/0x90 [drm_kms_helper]
 drm_fb_helper_set_par+0x29/0x50 [drm_kms_helper]
 intel_fbdev_set_par+0x16/0x60 [i915]
 ? __update_load_avg_se.isra.35+0x1b6/0x1c0
 fb_set_var+0x179/0x3e0
 ? update_load_avg+0x563/0x6c0
 ? __cgroup_account_cputime+0x24/0x30
 ? account_entity_enqueue+0xc5/0xf0
 ? __update_load_avg_se.isra.35+0x1b6/0x1c0
 ? __update_load_avg_se.isra.35+0x1b6/0x1c0
 fbcon_blank+0x26f/0x320
 do_unblank_screen+0xb3/0x1a0
 complete_change_console+0x54/0xd0
 vt_ioctl+0x695/0x1120
 ? _copy_to_user+0x22/0x30
 ? drm_ioctl+0x2ee/0x380 [drm]
 tty_ioctl+0xef/0x890
 ? __handle_mm_fault+0xa27/0x1220
 do_vfs_ioctl+0xa4/0x630
 ? handle_mm_fault+0xdc/0x210
 SyS_ioctl+0x74/0x80
 do_syscall_64+0x6c/0x130
 entry_SYSCALL_64_after_hwframe+0x3d/0xa2
RIP: 0033:0x7fbd8c79c097
RSP: 002b:7ffce45db298 EFLAGS: 3246 ORIG_RAX: 0010
RAX: ffda RBX: 55ccf3743650 RCX: 7fbd8c79c097
RDX: 0001 RSI: 5605 RDI: 000d
RBP: 55ccf374358c R08:  R09: 0001
R10: 0093 R11: 3246 R12: 0001
R13: 0008 R14: 55ccf3743640 R15: 55ccf3743588
Code: 2d ff ff ff e8 d4 b7 b6 ec 48 89 e6 4c 89 f7 e8 99 f3 ba ec 45 85 e4 0f 
85 0a ff ff ff 89 ee 48 c7 c7 58 aa 52 c0 e8 22 b5 b6 ec <0f> 0b e9 f5 fe ff ff 
90 66 2e 0f 1f 84 00 00 00 00 00 66 66 66

Bug#898814: When I log in, it hangs until crng init done

[積丹尼 Dan Jacobson]

Package: linux-image-4.16.0-1-amd64

I am also experiencing:
https://unix.stackexchange.com/questions/442698/when-i-log-in-it-hangs-until-crng-init-done

Bug#886510: OK now I installed libelf-dev, but...

[積丹尼 Dan Jacobson]

OK now I did,

# aptitude install libelf-dev
The following NEW packages will be installed:
  libelf-dev
The following packages will be REMOVED:
  linux-headers-4.14.0-1-amd64{pu}  linux-headers-4.14.0-1-common{pu} (D: 
linux-headers-4.14.0-1-amd64)

And now the error is gone,

# aptitude reinstall linux-image-4.14.0-3-amd64
The following packages will be REINSTALLED:
  linux-image-4.14.0-3-amd64
Preparing to unpack .../linux-image-4.14.0-3-amd64_4.14.12-2_amd64.deb ...
Unpacking linux-image-4.14.0-3-amd64 (4.14.12-2) over (4.14.12-2) ...
Setting up linux-image-4.14.0-3-amd64 (4.14.12-2) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-4.14.0-3-amd64

But I didn't see and nvidia-legacy-304xx-kernel-dkms related messages...
so maybe I have wiped that component out in the process, ruining the
whole purpose?

Bug#876977: hwdb.bin does not exist, please run systemd-hwdb update

[積丹尼 Dan Jacobson]

Package: initramfs-tools
Version: 0.130
Severity: wishlist

Showing the user warnings like
systemd-udevd[68]: hwdb.bin does not exist, please run systemd-hwdb update
in journalctl is bad, because according to e.g.,
https://bbs.archlinux.org/viewtopic.php?id=189536
there is nothing he can do about it.

I'm sorry I don't know the exact package to assign this bug to.

Bug#876977: Maybe related to 875924

[積丹尼 Dan Jacobson]

Maybe related to https://bugs.debian.org/875924 .

Bug#875924: "Please convert the driver to use hwmon_device_register_with_info()." messages

[積丹尼 Dan Jacobson]

Package: src:linux
Version: 4.12.6-1

There is not enough information in these messages to determine what
package to assign this bug to.

# journalctl | grep -C 1 deprecated
Sep 16 09:10:48 jidanni6 kernel: ACPI: bus type USB registered
Sep 16 09:10:48 jidanni6 kernel: (NULL device *): hwmon_device_register() is 
deprecated. Please convert the driver to use hwmon_device_register_with_info().
Sep 16 09:10:48 jidanni6 kernel: SCSI subsystem initialized
--
Sep 16 09:10:50 jidanni6 kernel: input: PC Speaker as 
/devices/platform/pcspkr/input/input8
Sep 16 09:10:50 jidanni6 kernel: k8temp :00:18.3: hwmon_device_register() 
is deprecated. Please convert the driver to use 
hwmon_device_register_with_info().
Sep 16 09:10:50 jidanni6 kernel: MCE: In-kernel MCE decoding enabled.

One would hope for better messages.

Bug#873767: W: mdadm: failed to auto-generate the mdadm.conf file

[積丹尼 Dan Jacobson]

Package: initramfs-tools
Version: 0.130

Processing triggers for initramfs-tools (0.130) ...
update-initramfs: Generating /boot/initrd.img-4.12.0-1-amd64
W: mkconf: MD subsystem is not loaded, thus I cannot scan for arrays.
W: mdadm: failed to auto-generate the mdadm.conf file.
W: mdadm: please read /usr/share/doc/mdadm/README.upgrading-2.5.3.gz .

Also there is no such file in /usr/share/doc/mdadm/

Hope I can still boot...

Bug#869670: Depends: linux-headers-4.11.0-2-common ... but it is not going to be installed

[積丹尼 Dan Jacobson]

Package: linux-headers-4.11.0-2-amd64
Version: 4.11.11-1

The following packages have unmet dependencies:
 linux-headers-4.11.0-2-amd64 : Depends: linux-headers-4.11.0-2-common (= 
4.11.11-1+b1) but it is not going to be installed

Bug#861057: Today I suddenly see swap warning

[積丹尼 Dan Jacobson]

Today I suddenly see:

Processing triggers for initramfs-tools (0.129) ...
update-initramfs: Generating /boot/initrd.img-4.9.0-2-amd64
W: initramfs-tools configuration sets 
RESUME=UUID=eff505d5-d5bf-4bba-8a07-f3d0d11018b9
W: but no matching swap device is available.
I: The initramfs will attempt to resume from /dev/sda9
I: (UUID=eff505d5-d5bf-4bba-8a07-f3d0d11018b9)
I: Set the RESUME variable to override this.
Processing triggers for libc-bin (2.24-10) ...
Processing triggers for menu (2.1.47+b1) ...

I have never messed with any of this.

Bug#852194: make a /run/initramfs/messages

[積丹尼 Dan Jacobson]

BH> There is no log daemon for logger to talk to.

Err... I mean talk to the same thing that is saving them up to put them
into journalctl.

Bug#852194: make a /run/initramfs/messages

[積丹尼 Dan Jacobson]

BH> initramfs-tools does not use systemd.  If systemd is failing to log its
BH>  output at boot time, that is not a bug in initramfs-tools.

OK I filed #852229 [systemd] failing to log output at boot time

BH> (I recognise that initramfs-tools should log output before it hands
BH> over to systemd (or other init system), so this is a valid bug.
BH> Unfortunately it will not be easy to do this consistently.)

Yes even though the user sees them flying by in the original order on
the screen, alas you will probably have to collect them into separate files
depending on where they came from. It is too bad they can't be put into
the dmesg/syslog... or actually they could. With just a simple logger(1) 
command(?).

Bug#852192: using boot_delay=500 renders system unbootable

[積丹尼 Dan Jacobson]

BH> The delay is applied after every line that is logged, whether or not
BH> it's displayed on the console.

OK maybe they should warn about that in
/usr/share/doc/linux-doc-4.9/Documentation/kernel-parameters.txt.gz

And add a new parameter that only applies to ones that are shown on the
console.

Hmmm, I always thought there were more lines sent to the console then
went in the logs (#852194).

Now I learn that there maybe instead less.

It is just a shame that there is no way to make sure without connecting
an external device.

Anyway I don't want to power cycle each time to test this.

Yup, not much the user can do to try to read them as they fly off the
screen.

No sure fire way to slow them down without also slowing down the many
more invisible ones... (but no way to tell without a high speed camera.)

Bug#852192: using boot_delay=500 renders system unbootable

[積丹尼 Dan Jacobson]

Package: src:linux
Version: 4.8.15-2

$ cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-4.8.0-2-amd64 
root=UUID=50c0e259-55bb-4fc0-867e-63160edef01f ro single 
systemd.log_level=debug systemd.log_target=kmsg log_buf_len=262144 enforcing=0 
panic=33 earlyprintk=vga
worked fine. But if boot_delay=500 is added to it,
all that happens is two lines are printed on the screen, and one has to
power cycle.

Bug#849280: say 'incompatible binary version', not "not found"

[積丹尼 Dan Jacobson]

> "MH" == Marc Haber  writes:

MH> Does /lib/ld-linux.so.2 exist on your system?

No.

MH> If not, the error message is correct. The kernel just knows that the
MH> interpreter given in the executable does not exist, it cannot give a
MH> more meaningful error message because lack of knowledge.

Well I though something might first stat the file that that something
then prints that it can't find. But OK never mind as the bug is closed.

Bug#849280: say 'incompatible binary version', not "not found"

[積丹尼 Dan Jacobson]

Package: src:linux
Version: 4.8.11-1
Severity: wishlist

Please give a more correct message, like 'incompatible binary version'.
Returning a not found error to shells is just plain misleading.

$ set who who2
$ for i in 'ls -l ' 'file ' './'; do $i$1; $i$2; done
-rwxr-xr-x 1 jidanni jidanni 51092 12-09 22:08 who
-rwxr-xr-x 1 jidanni jidanni 52168 12-09 22:08 who2
who: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically 
linked, interpreter /lib/ld-linux.so.2, for GNU/Linux 2.6.32, 
BuildID[sha1]=91f94a82b58bc7a63525c4ff35e43f9dbbe29caa, stripped
who2: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically 
linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.32, 
BuildID[sha1]=2d07a0c30c834741b64bda8289fa557fa1e1a876, stripped
bash: ./who: No such file or directory
jidanni  pts/02016-12-24 18:02 (:0)
$ uname -r
4.8.0-2-amd64
$ ./ #same messages as when something that really isn't there:
bash: ./: No such file or directory
$ ./who
dash: 2: ./who: not found

Bug#849276: cp: cannot stat '/etc/modprobe.d/*': No such file or directory

[積丹尼 Dan Jacobson]

Package: src:linux
Version: 4.8.11-1
Severity: minor

Please check to see if /etc/modprobe.d really exists (it might not!) first.

Log started: 2016-12-23  22:37:09
Selecting previously unselected package linux-image-4.8.0-1-amd64.
(Reading database ... 9940 files and directories currently installed.)
Preparing to unpack .../0-linux-image-4.8.0-1-amd64_4.8.7-1_amd64.deb ...
Unpacking linux-image-4.8.0-1-amd64 (4.8.7-1) ...
Selecting previously unselected package linux-image-amd64.
Preparing to unpack .../1-linux-image-amd64_4.8+76_amd64.deb ...
Unpacking linux-image-amd64 (4.8+76) ...
Setting up linux-image-4.8.0-1-amd64 (4.8.7-1) ...
I: /vmlinuz.old is now a symlink to boot/vmlinuz-4.8.0-1-amd64
I: /initrd.img.old is now a symlink to boot/initrd.img-4.8.0-1-amd64
I: /vmlinuz is now a symlink to boot/vmlinuz-4.8.0-1-amd64
I: /initrd.img is now a symlink to boot/initrd.img-4.8.0-1-amd64
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-4.8.0-1-amd64
cp: cannot stat '/etc/modprobe.d/*': No such file or directory
Setting up linux-image-amd64 (4.8+76) ...
Log ended: 2016-12-23  22:37:25

Bug#848724: now just a directory left behind

[積丹尼 Dan Jacobson]

OK now there is only the directory
/etc/kernel/signed_postinst.d/
left behind.

Bug#848724: unable to delete old directory '/etc/kernel/signed_postinst.d': Directory not empty

[積丹尼 Dan Jacobson]

Package: initramfs-tools
Version: 0.126
Severity: minor

Unpacking initramfs-tools (0.126) over (0.125) ...
dpkg: warning: unable to delete old directory '/etc/kernel/signed_postinst.d': 
Directory not empty

  /etc/kernel/signed_postinst.d:
  drwxr-xr-x 2 root 4096 12-20 04:20 .
  drwxr-xr-x 7 root 4096 09-21 14:41 ..
  -rwxr-xr-x 1 root  577 2016-04-18  initramfs-tools.dpkg-remove

firmware-linux obsolete?

[積丹尼 Dan Jacobson]

Hello, do I just purge these?
# aptitude search ~o~i~nfirm
i   firmware-amd-graphics
i   firmware-linux
i   firmware-linux-nonfree
i   firmware-misc-nonfree
i   firmware-realtek
Won't my computer stop working?

Bug#843485: mention () vs (()) of filename

[積丹尼 Dan Jacobson]

All I know is "one may have noticed () vs. (())". I don't know how they
got there. So I am not the best person to write about it.

Bug#843485: mention () vs (()) of filename

[積丹尼 Dan Jacobson]

BH> The extra parentheses have no special meaning.

Well please document how they got there at least.

BH> What the documentation ought to mention is that a thread's name can
BH> be overridden using prctl(PR_SET_NAME, ...). Care to send a patch?

I have no kernel knowledge.

Bug#843485: mention () vs (()) of filename

[積丹尼 Dan Jacobson]

Package: linux-doc-4.8
Version: 4.8.5-1
Severity: wishlist
File: /usr/share/doc/linux-doc-4.8/Documentation/filesystems/proc.txt.gz

One only sees
  tcomm filename of the executable

But no explanation of () vs (())

$ perl -anwle 'print $F[1]' /proc/[0-9]*/stat|sort -u|head
((sd-pam))
(Xorg)
(acpi_thermal_pm)

Bug#843113: better missing kernel headers message

[積丹尼 Dan Jacobson]

Package: src:linux
Version: 4.8.5-1
Severity: wishlist

Setting up linux-image-4.8.0-1-686-pae (4.8.5-1) ...
I: /vmlinuz.old is now a symlink to boot/vmlinuz-4.7.0-1-686-pae
I: /initrd.img.old is now a symlink to boot/initrd.img-4.7.0-1-686-pae
I: /vmlinuz is now a symlink to boot/vmlinuz-4.8.0-1-686-pae
I: /initrd.img is now a symlink to boot/initrd.img-4.8.0-1-686-pae
/etc/kernel/postinst.d/dkms:
Error! Your kernel headers for kernel 4.8.0-1-686-pae cannot be found.
Please install the linux-headers-4.8.0-1-686-pae package,
or use the --kernelsourcedir option to tell DKMS where it's located

1. That error message is not coming from that file. In fact from no
file with dkms in its name:
$ dlocate --filename-only dkms|xargs grep Error.*You 2>&-|wc -l
0

2. Please also have the message mention if one then needs to reinstall
linux-image-4.8.0-1-686-pae .

(Seen when offine installing from a /var/cache/apt/archives/ that has
some, but not all packages...)

Bug#841690: freezes with blank screen after printing two lines.

[積丹尼 Dan Jacobson]

Sorry, at least Bug #842221,
dpkg-checkbuilddeps: error: Unmet build dependencies: openssl:native, and
# df /var/cache/apt/archives/ -h
Filesystem  Size  Used Avail Use% Mounted on
/dev/sdc2   3.1G  2.0G 1018M  66% /var/cache/apt/archives
mean I give up trying to make a .deb. Please send me a .deb. Thanks.

Bug#841690: freezes with blank screen after printing two lines.

[積丹尼 Dan Jacobson]

I forgot how to save the traceback to disk.

Bug#841690: freezes with blank screen after printing two lines.

[積丹尼 Dan Jacobson]

No... unplugging all USB and rebooting doesn't help.

Bug#841690: freezes with blank screen after printing two lines.

[積丹尼 Dan Jacobson]

Thanks. It's the Bad EIP value problem of
http://www.linuxquestions.org/questions/fedora-35/bad-eip-value-189710/

I will try unplugging all USB...

Bug#841690: freezes with blank screen after printing two lines.

[積丹尼 Dan Jacobson]

In the changelog it seems some detection of
Thinkpad r50e hardware (wifi) perhaps has been added.
causing
Blinking cursor at top-left corner / A plain black screen
as mentioned in
https://community.linuxmint.com/tutorial/view/842
Of course there are no logs available at this point.

Bug#841690: freezes with blank screen after printing two lines.

[積丹尼 Dan Jacobson]

Package: src:linux
Version: 4.7.8-1

Version: 4.7.6-1 works fine.
Version: 4.7.8-1 freezes with blank screen after printing two lines.
Thinkpad r50e.

Bug#818252: swap.target: Job swap.target/start failed with result 'dependency'.

[積丹尼 Dan Jacobson]

Package: src:linux
Version: 4.4.4-2

Today I got a bug very much like
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764539
but without a custom kernel.

 3月 15 10:17:23 jidanni2 swapon[310]: swapon: sys-utils/swapon.c:653: 
parse_options: Assertion `ctl->discard' failed.
 3月 15 10:17:23 jidanni2 systemd[1]: 
dev-disk-by\x2duuid-ce5499e2\x2d019e\x2d44cc\x2d8f95\x2dd027832b3d7d.swap: Swap 
process exited, code=killed status=6
 3月 15 10:17:23 jidanni2 systemd[1]: Failed to activate swap 
/dev/disk/by-uuid/ce5499e2-019e-44cc-8f95-d027832b3d7d.
 3月 15 10:17:23 jidanni2 systemd[1]: Dependency failed for Swap.
 3月 15 10:17:23 jidanni2 systemd[1]: swap.target: Job swap.target/start failed 
with result 'dependency'.
 3月 15 10:17:23 jidanni2 systemd[1]: 
dev-disk-by\x2duuid-ce5499e2\x2d019e\x2d44cc\x2d8f95\x2dd027832b3d7d.swap: Unit 
entered failed state.

So I had to do a manual
# swapon /dev/sda12
which worked fine.

Bug#809206: dpkg: warning: unable to delete old directory '/etc/initramfs-tools/conf.d': Directory not empty

[積丹尼 Dan Jacobson]

> "BH" == Ben Hutchings  writes:

BH> I can't reproduce this, using either APT or direct invocation of dpkg.
BH> Please explain how you attempted to upgrade.

I always use aptitude full-upgrade.

Anyway on my jidanni2 machine I also find:

$ set /etc/initramfs-tools/conf.d /var/lib/initramfs-tools
$ find $@ -type f|xargs ls -og
-rw-r--r-- 1 70 2010-05-06  /etc/initramfs-tools/conf.d/resume
-rw-r--r-- 1 17 2008-02-12  /etc/initramfs-tools/conf.d/resume^old
-rw-r--r-- 1 75 12-08 08:43 /var/lib/initramfs-tools/4.2.0-1-686-pae
-rw-r--r-- 1 75 01-22 10:39 /var/lib/initramfs-tools/4.3.0-1-686-pae
$ find $@ -type f|xargs more|cat
::
/etc/initramfs-tools/conf.d/resume
::
# RESUME=/dev/hda5
RESUME='UUID=89a43990-ecd9-426f-adf2-529902935af4'
::
/etc/initramfs-tools/conf.d/resume^old
::
RESUME=/dev/hda5
::
/var/lib/initramfs-tools/4.3.0-1-686-pae
::
1dba8e95df7fe33aa6c404433e548e93524fb3ae  /boot/initrd.img-4.3.0-1-686-pae
::
/var/lib/initramfs-tools/4.2.0-1-686-pae
::
a9763ca08e6e8cea06bcd66ff03ddeb201bf793b  /boot/initrd.img-4.2.0-1-686-pae

Bug#809206: so can I delete them by hand?

[積丹尼 Dan Jacobson]

So can I delete them anyway?

Bug#809204: busybox is required but not installed

[積丹尼 Dan Jacobson]

> "BH" == Ben Hutchings  writes:
BH> You've convinced me that this isn't a good way to handle the change.

Glad!

BH> What I intend to do is to add a third option, BUSYBOX=auto, with the
BH> old semantics of BUSYBOX=y, and make that the default.  On upgrade you
BH> may be prompted to resolve conflicts in the configuration file, but
BH> otherwise nothing will break.

BH> In the case that there are configuration hooks that set BUSYBOX=y,
BH> mkinitramfs will still refuse to create a broken initramfs.

OK... I don't know about the details. I'm just happy the standards will
stay the same.

Bug#808563: better cover up this version fast

[積丹尼 Dan Jacobson]

You really need to put something else it its place fast.
Else users will end up with scrambled disks, and unable to boot.
Treat it like a virus.
Can't you just copy the previous kernel into a "4.3a" release?
That way the damaging kernel won't be the default anymore.

Bug#809204: busybox is required but not installed

[積丹尼 Dan Jacobson]

> "BH" == Ben Hutchings  writes:

BH> Wrong, initramfs-tools-core does (and initramfs-tools used to do so
BH> directly).

OK, but you are still going to run into problems if the user has set

# apt-config dump|egrep Rec\|Sugg
APT::Install-Recommends "false";
APT::Install-Suggests "0";

Bug#809204: busybox is required but not installed

[積丹尼 Dan Jacobson]

> "BH" == Ben Hutchings  writes:
>> OK, but you are still going to run into problems if the user has set
>> 
>> # apt-config dump|egrep Rec\|Sugg
>> APT::Install-Recommends "false";
>> APT::Install-Suggests "0";

BH> Users that do that need to accept that they will encounter errors like
BH> this.

OK, but I am sure yours is the very first package to "lower the
barrier" of
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-binarydeps
in that way.

In the past an entire working Debian could be completely installed counting on 
only
Depends.

Or maybe
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-binarydeps
needs to have some additional explanation about special cases like this?

Bug#809204: busybox is required but not installed

[積丹尼 Dan Jacobson]

Package: initramfs-tools
Version: 0.121~rc2

Processing triggers for initramfs-tools (0.121~rc2) ...
update-initramfs: Generating /boot/initrd.img-4.3.0-1-686-pae
E: busybox is required but not installed
E: /usr/share/initramfs-tools/hooks/busybox failed with return 1.
update-initramfs: failed for /boot/initrd.img-4.3.0-1-686-pae with 1.
dpkg: error processing package initramfs-tools (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 initramfs-tools
E: Sub-process /usr/bin/dpkg returned an error code (1)

Bug#809206: dpkg: warning: unable to delete old directory '/etc/initramfs-tools/conf.d': Directory not empty

[積丹尼 Dan Jacobson]

Package: initramfs-tools
Version: 0.121~rc2

Unpacking initramfs-tools (0.121~rc2) over (0.120) ...
dpkg: warning: unable to delete old directory '/etc/initramfs-tools/conf.d': 
Directory not empty
dpkg: warning: unable to delete old directory '/var/lib/initramfs-tools': 
Directory not empty

$ ls -lA /etc/initramfs-tools/conf.d /var/lib/initramfs-tools
/etc/initramfs-tools/conf.d:
total 4
-rw-r--r-- 1 root root 49 2014-10-13  resume

/var/lib/initramfs-tools:
total 8
-rw-r--r-- 1 root root 75 10-15 12:36 4.2.0-1-686-pae
-rw-r--r-- 1 root root 75 12-27 07:37 4.3.0-1-686-pae

Bug#809204: closed by Ben Hutchings <b...@decadent.org.uk> (Re: Bug#809204: busybox is required but not installed)

[積丹尼 Dan Jacobson]

B> Read the NEWS.

"You may need
to modify /etc/initramfs-tools/initramfs-tools.conf or install busybox
when upgrading."

$ ls /etc/initramfs-tools/initramfs-tools.conf
ls: cannot access /etc/initramfs-tools/initramfs-tools.conf: No such file or 
directory

Maybe that means the default state will be an installation failure.

Bug#809204: closed by Ben Hutchings <b...@decadent.org.uk> (Re: Bug#809204: busybox is required but not installed)

[積丹尼 Dan Jacobson]

OK I find BUSYBOX=y.
But I don't think I ever tampered with that file.
That means that ... you are going to have a lot of people with problems 
shortly...

Bug#809204: closed by Ben Hutchings <b...@decadent.org.uk> (Re: Bug#809204: busybox is required but not installed)

[積丹尼 Dan Jacobson]

>>>>> "BH" == Ben Hutchings <b...@decadent.org.uk> writes:

BH> On Mon, 2015-12-28 at 21:20 +0800, 積丹尼 Dan Jacobson wrote:
>> OK I find BUSYBOX=y.
>> But I don't think I ever tampered with that file.

BH> That is the default.

>> That means that ... you are going to have a lot of people with
>> problems shortly...

BH> Perhaps, but busybox is also installed by default so you have to remove
BH> it to get into this situation.

So is Windows! They would have to remove Windows and install Linux to
have Linux. All I know is you are breaking all five of my machines...
until I now know I you don't even Suggest or Recommend busybox. You are
setting a dangerous precedence by not putting it in Depends. Can you
find one single package "as broken as this" on Debian? What is the big
harm in putting it in Depends (: busybox|something_else) then? The user
won't be offended as he is already choosing a different configuration so
can do something different in two places instead of one. I don't know
what you mean by default (maybe "automatic installation of Debian via
CDrom tasksel or what ever that was called but that is a very weak
supposition to gamble with when a correct Depends is the proper way and .

Bug#808563: really should be serious bug: data loss

[積丹尼 Dan Jacobson]

Will try Wednesday.
Actually better to have the raid people test. I only have one disk... too risky.

Bug#808563: really should be serious bug: data loss

[積丹尼 Dan Jacobson]

Rotational.
watch outscrambled data fsck forced can't boot stay away...

Bug#808563: really should be serious bug: data loss

[積丹尼 Dan Jacobson]

ata1.00: exception Emask 0x60 SAct 0x1c SErr 0x800 action 0x6 frozen
ata1.00: irq_stat 0x2000, host bus error
ata1: SError: { HostInt }
ata1.00: failed command: WRITE FPDMA QUEUED
ata1.00: cmd 61/00:10:00:a8:10/08:00:26:00:00/40 tag 2 ncq 1048576 out
 res 40/00:20:00:48:11/00:00:26:00:00/40 Emask 0x60 (host bus error)
ata1.00: status: { DRDY }
ata1.00: failed command: WRITE FPDMA QUEUED
ata1.00: cmd 61/00:18:00:b0:10/08:00:26:00:00/40 tag 3 ncq 1048576 out
 res 40/00:20:00:48:11/00:00:26:00:00/40 Emask 0x60 (host bus error)
ata1.00: status: { DRDY }
ata1.00: failed command: WRITE FPDMA QUEUED
ata1.00: cmd 61/98:20:00:48:11/03:00:26:00:00/40 tag 4 ncq 471040 out
 res 40/00:20:00:48:11/00:00:26:00:00/40 Emask 0x60 (host bus error)
ata1.00: status: { DRDY }
ata1: hard resetting link
ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata1.00: configured for UDMA/133
ata1: EH complete
ata1.00: exception Emask 0x60 SAct 0x1800 SErr 0x800 action 0x6 frozen
ata1.00: irq_stat 0x2000, host bus error
ata1: SError: { HostInt }
ata1.00: failed command: WRITE FPDMA QUEUED
ata1.00: cmd 61/d0:d8:80:9e:10/05:00:26:00:00/40 tag 27 ncq 761856 out
 res 40/00:e0:d0:5f:12/00:00:26:00:00/40 Emask 0x60 (host bus error)
ata1.00: status: { DRDY }
ata1.00: failed command: WRITE FPDMA QUEUED
ata1.00: cmd 61/30:e0:d0:5f:12/00:00:26:00:00/40 tag 28 ncq 24576 out
 res 40/00:e0:d0:5f:12/00:00:26:00:00/40 Emask 0x60 (host bus error)
ata1.00: status: { DRDY }
ata1: hard resetting link
ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata1.00: configured for UDMA/133
ata1: EH complete
ata1.00: exception Emask 0x60 SAct 0x1f8 SErr 0x800 action 0x6 frozen
ata1.00: irq_stat 0x2000, host bus error
ata1: SError: { HostInt }
ata1.00: failed command: WRITE FPDMA QUEUED
ata1.00: cmd 61/00:18:00:08:12/08:00:26:00:00/40 tag 3 ncq 1048576 out
 res 40/00:40:00:88:1a/00:00:26:00:00/40 Emask 0x60 (host bus error)
ata1.00: status: { DRDY }
ata1.00: failed command: WRITE FPDMA QUEUED
ata1.00: cmd 61/00:20:00:10:12/08:00:26:00:00/40 tag 4 ncq 1048576 out
 res 40/00:40:00:88:1a/00:00:26:00:00/40 Emask 0x60 (host bus error)
ata1.00: status: { DRDY }
ata1.00: failed command: WRITE FPDMA QUEUED
ata1.00: cmd 61/00:28:00:18:12/28:00:26:00:00/40 tag 5 ncq 5242880 out
 res 40/00:40:00:88:1a/00:00:26:00:00/40 Emask 0x60 (host bus error)
ata1.00: status: { DRDY }
ata1.00: failed command: WRITE FPDMA QUEUED
ata1.00: cmd 61/00:30:00:40:12/08:00:26:00:00/40 tag 6 ncq 1048576 out
 res 40/00:40:00:88:1a/00:00:26:00:00/40 Emask 0x60 (host bus error)
ata1.00: status: { DRDY }
ata1.00: failed command: WRITE FPDMA QUEUED
ata1.00: cmd 61/00:38:00:48:1a/40:00:26:00:00/40 tag 7 ncq 8388608 out
 res 40/00:40:00:88:1a/00:00:26:00:00/40 Emask 0x60 (host bus error)
ata1.00: status: { DRDY }
ata1.00: failed command: WRITE FPDMA QUEUED
ata1.00: cmd 61/08:40:00:88:1a/44:00:26:00:00/40 tag 8 ncq 8916992 out
 res 40/00:40:00:88:1a/00:00:26:00:00/40 Emask 0x60 (host bus error)
ata1.00: status: { DRDY }
ata1: hard resetting link

Bug#808563: really should be serious bug: data loss

[積丹尼 Dan Jacobson]

Package: src:linux
Version: 4.3.3-2

-- Package-specific info:
** Kernel log: boot messages should be attached

** Model information
not available

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation 2nd Generation Core Processor 
Family DRAM Controller [8086:0104] (rev 09)
Subsystem: Lenovo Device [17aa:3977]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 

00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation Core 
Processor Family Integrated Graphics Controller [8086:0106] (rev 09) (prog-if 
00 [VGA controller])
Subsystem: Lenovo Device [17aa:3977]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR-  [disabled]
Capabilities: 
Kernel driver in use: i915

00:14.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset 
Family USB xHCI Host Controller [8086:1e31] (rev 04) (prog-if 30 [XHCI])
Subsystem: Lenovo Device [17aa:3977]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- 
Kernel driver in use: xhci_hcd

00:16.0 Communication controller [0780]: Intel Corporation 7 Series/C210 Series 
Chipset Family MEI Controller #1 [8086:1e3a] (rev 04)
Subsystem: Lenovo Device [17aa:3977]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: mei_me

00:1a.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset 
Family USB Enhanced Host Controller #2 [8086:1e2d] (rev 04) (prog-if 20 [EHCI])
Subsystem: Lenovo Device [17aa:3977]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- 
Kernel driver in use: ehci-pci

00:1b.0 Audio device [0403]: Intel Corporation 7 Series/C210 Series Chipset 
Family High Definition Audio Controller [8086:1e20] (rev 04)
Subsystem: Lenovo Device [17aa:3977]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: snd_hda_intel

00:1c.0 PCI bridge [0604]: Intel Corporation 7 Series/C210 Series Chipset 
Family PCI Express Root Port 1 [8086:1e10] (rev c4) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:1d.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset 
Family USB Enhanced Host Controller #1 [8086:1e26] (rev 04) (prog-if 20 [EHCI])
Subsystem: Lenovo Device [17aa:3977]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- 
Kernel driver in use: ehci-pci

00:1f.0 ISA bridge [0601]: Intel Corporation HM76 Express Chipset LPC 
Controller [8086:1e59] (rev 04)
Subsystem: Lenovo Device [17aa:3977]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- 
SERR- 
Kernel driver in use: lpc_ich

00:1f.2 SATA controller [0106]: Intel Corporation 7 Series Chipset Family 
6-port SATA Controller [AHCI mode] [8086:1e03] (rev 04) (prog-if 01 [AHCI 1.0])
Subsystem: Lenovo Device [17aa:3977]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- 
Kernel driver in use: ahci

00:1f.3 SMBus [0c05]: Intel Corporation 7 Series/C210 Series Chipset Family 
SMBus Controller [8086:1e22] (rev 04)
Subsystem: Lenovo Device [17aa:3977]
Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- TAbort- SERR- 
Kernel driver in use: alx


** USB devices:
Bus 004 Device 003: ID 04f2:b2e2 Chicony Electronics Co., Ltd 
Bus 004 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 004 

Bug#808563: really should be serious bug: data loss

[積丹尼 Dan Jacobson]

The first time it happened I couldn't boot again without a fsck.ext4 via
a rescue CD!

Bug#808563: Boot with 4.3: SATA errors. Returning to 4.2: no errors

[積丹尼 Dan Jacobson]

Package: src:linux
Version: 4.3.3-2
Severity: important

I am getting these errors (sort -u'd here) with linux-image-4.3.0-1-686-pae

 res 40/00:20:00:48:11/00:00:26:00:00/40 Emask 0x60 (host bus error)
ata1.00: cmd 61/d0:d8:80:9e:10/05:00:26:00:00/40 tag 27 ncq 761856 out
ata1.00: configured for UDMA/133
ata1.00: exception Emask 0x60 SAct 0x1800 SErr 0x800 action 0x6 frozen
ata1.00: exception Emask 0x60 SAct 0x1f8 SErr 0x800 action 0x6 frozen
ata1.00: exception Emask 0x60 SAct 0xfe SErr 0x800 action 0x6 frozen
ata1.00: failed command: READ FPDMA QUEUED
ata1.00: failed command: WRITE FPDMA QUEUED
ata1.00: irq_stat 0x2000, host bus error
ata1.00: status: { DRDY }
ata1: EH complete
ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata1: SError: { HostInt }
ata1: hard resetting link

Switching back to 4.2.6-3 solves it.

Did it twice so far. Consistent results.

Bug#683237: closed by Ben Hutchings <b...@decadent.org.uk> (Re: document how one uses the firmware here)

[積丹尼 Dan Jacobson]

> "B" == Debian Bug Tracking System  writes:

B> This is covered by the Installation Manual:
B> https://www.debian.org/releases/jessie/amd64/ch06s04.html.en

OK but maybe you should mention that somewhere in the package docs.
Also not everybody has an AMD64.

Bug#786385: /init: touch not found

[積丹尼 Dan Jacobson]

Package: initramfs-tools
Version: 0.120
Severity: wishlist

I saw /init: touch not found during the messages flashing by at boot,
but even installing bootlogd offers no way of capturing them because
they are from initrd.img-4.0.0-1-686-pae .


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/87d21uxuex@jidanni.org

Bug#785435: init: touch not found

[積丹尼 Dan Jacobson]

Package: initramfs-tools
Version: 0.120
Severity: wishlist

I swear I saw something about init: touch not found fly past on my
screen, but I have no log file to prove it.

I wish there was a log file.


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/87382wvquo@jidanni.org

Bug#780239: closed by Ben Hutchings b...@decadent.org.uk (Re: Bug#780239: log timestamps could be off by a whole minute)

[積丹尼 Dan Jacobson]

Please reassign.


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/87vbi844w9@jidanni.org

Bug#780239: log timestamps could be off by a whole minute

[積丹尼 Dan Jacobson]

reopen 780239
reassign 780239 rsyslog
found 780239 8.8.0-1
thanks
I'll try the above.

BH On Wed, 2015-03-11 at 10:57 +0800, 積丹尼 Dan Jacobson wrote:
 Please reassign.

BH What's the point?  I could only reassign it to general so that Holger
BH could close it.


--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/87oao042xr.fsf...@jidanni.org

Bug#780239: log timestamps could be off by a whole minute

[積丹尼 Dan Jacobson]

Package: src:linux
Version: 3.16.7-ckt7-1
Severity: wishlist

Here's a risk I sent to
http://catless.ncl.ac.uk/Risks/28.55.html#subj13
which ought to also be reported here.

One day in a court of law, the log files of a computer system will be
used to prove that some incident happened at some certain time.

Let's have a look.

journalctl says
Mar 10 03:14:32 jidanni2 kernel: sd 2:0:0:0: [sdb] Attached SCSI
Mar 10 03:14:32 jidanni2 kernel: EXT4-fs (sda8): mounted filesys

/var/log/kern.log says
Mar 10 03:14:47 jidanni2 kernel: [4.000166] sd 2:0:0:0: [sdb
Mar 10 03:14:47 jidanni2 kernel: [   62.534080] EXT4-fs (sda8):

So did this happen at 03:14:32 or 03:14:47 or is all we in fact really
know was that there was an entire (62 - 4 =) 58 second gap between the
two lines?

The latter: my screen froze for a minute.


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/87y4n44da8@jidanni.org

Bug#766448: why one would want fstype auto for /

[積丹尼 Dan Jacobson]

You might ask why one would want fstype auto for /.
Well sometimes it is a lifesaver.
E.g., when trying to boot with a older kernel that doesn't understand
newer filesystems. I don't recall the exact details... but it gave me
the flexibility to change something...


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/87tx2sytld@jidanni.org

Bug#766448: root fstype auto in /etc/fstab guaranteed unbootable

[積丹尼 Dan Jacobson]

For 0.118 not only did I discover setting the root fstype to auto in
/etc/fstab and then running mkinitramfs -u make the system guaranteed
unbootable, furthermore I found this code in
/usr/share/initramfs-tools/hook-functions

# check that fstype rootfs recognition
if [ ${FSTYPE} = unknown ]; then
FSTYPE=$(blkid -o value -s TYPE ${root})
if [  -z ${FSTYPE} ]; then
echo mkinitramfs: unknown fstype on root ${root} 2
echo mkinitramfs: workaround is MODULES=most 2
echo Error please report bug on initramfs-tools 2
exit 1
fi

But alas it is never reached if the user put type 'auto' for / there in fstab!


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/87tx2tyn9o@jidanni.org

Bug#766448: 0.116 to 0.118 makes systems unbootable with 5 second message

[積丹尼 Dan Jacobson]

Package: initramfs-tools
Version: 0.118
Severity: grave

On all my systems, 0.116 works fine,
0.118 just gives some message about rebooting in 5 seconds that is not
enough time to read.

I.e., the system becomes unbootable.

1. Please tell me what steps you would like me to take.

Thanks.


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/87d29jkzt6@jidanni.org

Bug#766447: add parameter to override the seconds of 'Will restart in 5 seconds.'

[積丹尼 Dan Jacobson]

Package: src:linux
Version: 3.16.5-1
Severity: wishlist


Regarding

'Attempt to start maintenance shell failed. Will restart in 5 seconds.'

5 seconds is not long enough to read all but a few of the words on the screen.

Please add a boot parameter to control this.

Also document it in
Documentation/kernel-parameters.txt.gz
and perhaps say adjust with xyz= right there in the message.

One would think that panic= is the parameter that is used, but it is not.


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/87h9yvl040@jidanni.org

Bug#766446: mention what disk when saying Warning: couldn't identify filesystem type

[積丹尼 Dan Jacobson]

Package: initramfs-tools
Version: 0.118
Severity: wishlist

Please mention what disk you are talking about in messages like
Warning: couldn't identify filesystem type for fsck hook, ignoring.
else the user will get very worried that one of his disks are bad and
need to test them all. Thanks.

Preparing to unpack .../initramfs-tools_0.118_all.deb ...
Unpacking initramfs-tools (0.118) over (0.116) ...
Processing triggers for man-db (2.7.0.2-2) ...
Processing triggers for doc-base (0.10.6) ...
Processing 1 changed doc-base file...
Registering documents with scrollkeeper...
Setting up initramfs-tools (0.118) ...
update-initramfs: deferring update (trigger activated)
Processing triggers for initramfs-tools (0.118) ...
update-initramfs: Generating /boot/initrd.img-3.16-3-686-pae
Warning: couldn't identify filesystem type for fsck hook, ignoring.


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/87vbnbb6zn@jidanni.org

Bug#766448: root fstype auto in /etc/fstab guaranteed unbootable

[積丹尼 Dan Jacobson]

reopen 766448
retitle root fstype auto in /etc/fstab guaranteed unbootable
thanks

Please try these simple steps:
Change /etc/fstab making the type for / be auto, not ext4 etc.
Now with initramfs-tools Ver: 0.118 installed,
run update-initramfs -u
and reboot.
But first see also #766578.


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/87wq7qm3op@jidanni.org

Bug#766385: Generating /boot/initrd... seen twice in a single aptitude full-upgrade

[積丹尼 Dan Jacobson]

Package: initramfs-tools
Version: 0.116
Severity: wishlist
File: /usr/sbin/update-initramfs

Often I see Generating /boot/initrd... twice

# aptitude full-upgrade
...
Setting up linux-image-3.16-3-686-pae (3.16.5-1) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-3.16-3-686-pae
...
Processing triggers for initramfs-tools (0.116) ...
update-initramfs: Generating /boot/initrd.img-3.16-3-686-pae

(I am holding at version 0.116 for other reasons...)


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/87siigc85u@jidanni.org

Bug#686544: upstream response

[積丹尼 Dan Jacobson]

Upstream closed  https://bugzilla.kernel.org/show_bug.cgi?id=85471
Now what should I do? Thanks.


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20141014211043.ga9...@ps11007.dreamhostps.com

Bug#764021: 118 fails to boot to boot

[積丹尼 Dan Jacobson]

Your 118 also fails to boot to boot.
(Your 118 also fails to boot in addition.)

It says rebooting in 5 seconds and indeed reboot in 5 seconds, too
short for me to read what else it said.

Even though I have panic=33 to give it more time.

Maybe it has to do with the
Warning: couldn't identify filesystem type for fsck hook, ignoring.

Why can't you tell? Just use blkid or mount and then grep, when
encountering auto in fstab. Why isn't this working?

 How are we going to boot with an empty etc/fstab?

B We don't; we use the one on the real root partition.  It is only there
B to stop some utilities from warning.

Then perhaps put such a note in a comment inside it. It is the only
empty file in the whole thing!


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/87sij3qayv@jidanni.org

Bug#764019: closed by Ben Hutchings b...@decadent.org.uk (Re: Bug#764019: /etc/initramfs-tools/conf.d/resume out of date)

[積丹尼 Dan Jacobson]

B The latter file is left over from the device ID conversion in a
B lenny-squeeze upgrade, and is not used.

Yes but the former file points to a non-usable partition too!!


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/87oatrq98e@jidanni.org

Bug#764019: closed by Ben Hutchings b...@decadent.org.uk (Re: Bug#764019: /etc/initramfs-tools/conf.d/resume out of date)

[積丹尼 Dan Jacobson]

BH Then you'll need to update it.

BH Are you expecting update-initramfs to warn about this?

All I know is reportbug --template initramfs-tools alerted me to the
existence of /etc/initramfs-tools/conf.d/resume and its outdated
contents.

All I know is initramfs-tools created this file, not me.

Therefore initramfs-tools should keep it current.


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/87egumako4@jidanni.org

Bug#764020: list lsinitramfs on initramfs-tools man page's SEE ALSO

[積丹尼 Dan Jacobson]

Package: initramfs-tools
Version: 0.117
Severity: minor

Please list lsinitramfs on initramfs-tools man page's SEE ALSO.
In fact maybe there are others missing too.

Problem, lsinitramfs is in manual section 8 but in bin, not sbin.
Perhaps make it section 1.

Maybe other pages have this problem too.


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/8738b3sihr@jidanni.org

Bug#764019: /etc/initramfs-tools/conf.d/resume out of date

[積丹尼 Dan Jacobson]

Package: initramfs-tools
Version: 0.117

I discovered these ancient files

$ find /etc/initramfs-tools/conf.d -type f|xargs more|cat
::
/etc/initramfs-tools/conf.d/resume
::
# RESUME=/dev/hda5
RESUME='UUID=89a43990-ecd9-426f-adf2-529902935af4'
::
/etc/initramfs-tools/conf.d/resume^old
::
RESUME=/dev/hda5

That is an ancient swap partition not currently mounted.


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/877g0fsiyb@jidanni.org

Bug#764022: inaccurate DEBUG method on man page

[積丹尼 Dan Jacobson]

Package: initramfs-tools
Version: 0.117
File: /usr/share/man/man8/initramfs-tools.8.gz

We read

DEBUG
   It  is  easy  to check the generated initramfs for its content. One may
   need to double-check if it contains the relevant binaries, libs or mod-
   ules:
  mkdir tmp/initramfs
  cd tmp/initramfs
  gunzip -c /boot/initrd.img-2.6.18-1-686 | \
  cpio -i -d -H newc --no-absolute-filenames

However these days this will merely get the user:

gzip: /boot/initrd.img-3.16-2-686-pae: not in gzip format
cpio: premature end of file

These days

$ file initrd.img-3.16-*
initrd.img-3.16-2-686-pae: ASCII cpio archive (SVR4 with no CRC)
$ cpio -tF initrd.img-3.16-2-686-pae
kernel
kernel/x86
kernel/x86/microcode
kernel/x86/microcode/GenuineIntel.bin
6 blocks

Noting the 6 blocks, I then did

set -uxe
cd /
mkdir -p tmp/initramfs
cd tmp/initramfs
dd if=/boot/initrd.img-3.16-2-686-pae skip=6|zcat|
cpio -vi -d -H newc --no-absolute-filenames

which worked.

So the man page needs to be updated.


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/87wq8fr34g@jidanni.org

Bug#764021: How are we going to boot with an empty etc/fstab?

[積丹尼 Dan Jacobson]

Package: initramfs-tools
Version: 0.117
Severity: critical
File: /usr/share/initramfs-tools/hooks/fsck

How are we going to boot with an empty etc/fstab?

It is the only empty file in the whole initrd.img !

dd if=/boot/initrd.img-3.16-2-686-pae skip=6|zcat|
cpio -vt|perl -anwle 'next if /^d/; print unless $F[4]'
28648+1 records in
28648+1 records out
14667780 bytes (15 MB) copied, 1.00837 s, 14.5 MB/s
71060 blocks
-rw-r--r--   1 root root0 Oct  5 03:38 etc/fstab

Setting up initramfs-tools (0.117) ...
update-initramfs: deferring update (trigger activated)
Processing triggers for initramfs-tools (0.117) ...
update-initramfs: Generating /boot/initrd.img-3.16-2-686-pae
Warning: couldn't identify filesystem type for fsck hook, ignoring.

OK in /etc/fstab I changed root's type from auto to ext4, reinstalled
initramfs-tools, and the warning went away. But still couldn't boot, as
etc/fstab as generated was still 0 bytes.

Maybe one must take all the autos out completely.

Here's my fstab. You can see if maybe that will fix it.

UUID=355d426a-cbfc-4faf-91d6-4f9405199517 /home auto 
defaults,commit=222,noatime 0 2
UUID=34610b6a-70a3-48d9-b135-96907dc2ba16 /var auto defaults,commit=222,noatime 
0 2
UUID=1d11e0e3-26d7-42be-89d2-00fbe939dc1c / ext4 
defaults,commit=222,noatime,errors=remount-ro 0 1
UUID=4ff328e3-a3a7-44f7-a998-6c0404616e15 /music auto 
defaults,commit=222,noatime,user,noauto 0 2
/dev/cdrom5 /cdrom iso9660 defaults,ro,user,noauto 0 0
UUID=ce5499e2-019e-44cc-8f95-d027832b3d7d none swap sw 0 0
/dev/sr0 /mnt/usb/cdrom iso9660 defaults,user,noauto 0 0
tmpfs /tmp tmpfs defaults 0 0
UUID=00b63f91-edff-42db-8b45-81243ac43d44 /mnt/usb/cf auto 
noauto,noatime,errors=remount-ro 0 0
UUID=-006F /mnt/usb/s1mp3 vfat 
iocharset=ascii,shortname=mixed,noauto,noatime,nodiratime,user,fmask=133,uid=jidanni,gid=jidanni
 0 0
UUID=26a1643a-011c-4d6b-8234-c327f9dc2495 /var/lib/apt/lists auto 
noauto,noatime,errors=remount-ro 0 0
UUID=82152152-fd1b-41f5-8860-a65f18de2275 /var/cache/apt/archives auto 
noauto,noatime,errors=remount-ro 0 0

I just don't see why initramfs-tools doesn't detect that it generated a
0 byte fstab and stop and think for a moment before exiting 0.

When we try to boot we get lots of -f: no such file or directory,
fsck: no such file or directory, mount: Usage ... etc. No init
found, etc.

P.S., other programs can deal with auto. Indeed one must be able to
use auto 100% in their fstabs! Does my using auto mean that my disks
will no longer be checked?


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/87ppe7r1gn@jidanni.org

Bug#686544: bug happing again

[積丹尼 Dan Jacobson]

 BH == Ben Hutchings b...@decadent.org.uk writes:

BH Control: close -1 3.5.5-1~experimental.1

BH You don't have the same hardware, so don't hijack this bug.

Should I file a new bug?


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/87eguqv2fe@jidanni.org

Bug#686544: bug happing again

[積丹尼 Dan Jacobson]

OK submitted https://bugzilla.kernel.org/show_bug.cgi?id=85471 . Thanks.


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/87y4sytloi@jidanni.org

Bug#686544: bug happing again

[積丹尼 Dan Jacobson]

# journalctl

10月 02 10:01:12 jidanni5 kernel: ACPI: AC Adapter [ACAD] (on-line)
10月 02 10:01:12 jidanni5 kernel: ACPI Warning: SystemIO range 
0x0428-0x042f conflicts with OpRegion 0x0400-0x047f (\PMIO) 
(20140424/utaddress-258)
10月 02 10:01:12 jidanni5 kernel: ACPI: If an ACPI driver is available for this 
device, you should use it instead of the native driver
10月 02 10:01:12 jidanni5 kernel: ACPI Warning: SystemIO range 
0x0540-0x054f conflicts with OpRegion 0x0500-0x0563 (\GPIO) 
(20140424/utaddress-258)
10月 02 10:01:12 jidanni5 kernel: ACPI: If an ACPI driver is available for this 
device, you should use it instead of the native driver
10月 02 10:01:12 jidanni5 kernel: ACPI Warning: SystemIO range 
0x0530-0x053f conflicts with OpRegion 0x0500-0x0563 (\GPIO) 
(20140424/utaddress-258)
10月 02 10:01:12 jidanni5 kernel: ACPI: If an ACPI driver is available for this 
device, you should use it instead of the native driver
10月 02 10:01:12 jidanni5 kernel: ACPI Warning: SystemIO range 
0x0500-0x052f conflicts with OpRegion 0x0500-0x0563 (\GPIO) 
(20140424/utaddress-258)
10月 02 10:01:12 jidanni5 kernel: ACPI: If an ACPI driver is available for this 
device, you should use it instead of the native driver
10月 02 10:01:12 jidanni5 kernel: lpc_ich: Resource conflict(s) found affecting 
gpio_ich
10月 02 10:01:12 jidanni5 kernel: mei_me :00:16.0: irq 42 for MSI/MSI-X
10月 02 10:01:12 jidanni5 kernel: ACPI Warning: SystemIO range 
0x3040-0x305f conflicts with OpRegion 0x3040-0x304f 
(\_SB_.PCI0.SBUS.SMBI) (20140424/utaddress-258)
10月 02 10:01:12 jidanni5 kernel: ACPI: If an ACPI driver is available for this 
device, you should use it instead of the native driver
10月 02 10:01:12 jidanni5 kernel: [drm] Initialized drm 1.1.0 20060810

# lshw -sanitize|head ...
computer
description: Notebook
product: 20150 (Type1Sku0)
vendor: LENOVO
version: Lenovo G580
serial: [REMOVED]
width: 32 bits
capabilities: smbios-2.7 dmi-2.7 smp-1.4 smp
configuration: boot=normal chassis=notebook cpus=1 family=IDEAPAD 
sku=Type1Sku0 uuid=[REMOVED]
  *-core
   description: Motherboard
   product: Product Name
   vendor: LENOVO
   physical id: 0
   version: Mainboard version
   serial: [REMOVED]
   slot: Type2 - Board Chassis Location
 *-firmware
  description: BIOS
  vendor: LENOVO
  physical id: 0
  version: 5ECN40WW(V3.06)
  date: 10/22/2012
  size: 128KiB
  capacity: 4544KiB
  capabilities: pci upgrade shadowing cdboot bootselect edd 
int13floppynec int13floppytoshiba int13floppy360 int13floppy1200 int13floppy720 
int13floppy2880 int9keyboard int10video acpi usb biosbootspecification uefi


--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/87egurz0cq@jidanni.org

Bug#763123: mention grub can now do badram directly

[積丹尼 Dan Jacobson]

Package: linux-doc-3.16
Version: 3.16.3-2
X-debbugs-Cc: Jan-Simon Moeller dl...@gmx.de
Severity: minor
File: /usr/share/doc/linux-doc-3.16/Documentation/bad_memory.txt.gz

Please mention now grub can do badram directly!

$ info grub commands 'command-line and menu entry commands' badram


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/87tx3s7hsf@jidanni.org

Bug#762870: can't boot!

[積丹尼 Dan Jacobson]

Me too, can't boot.


trace.log
Description: Binary data

Bug#762870: can't boot!

[積丹尼 Dan Jacobson]

All I know is I couldn't boot with that thing at the top of
# ls /boot/ -ltog
-rw-r--r-- 1 2907647 09-26 08:46 initrd.img-3.16-2-686-pae
drwxr-xr-x 54096 09-23 00:39 grub
-rw-r--r-- 1 2726738 09-22 23:00 initrd.img-3.16-1-686-pae
-rw-r--r-- 1 2089608 09-21 01:56 System.map-3.16-2-686-pae
-rw-r--r-- 1  159970 09-21 01:56 config-3.16-2-686-pae
-rw-r--r-- 1 3006608 09-21 01:54 vmlinuz-3.16-2-686-pae
-rw-r--r-- 1 2087689 09-13 14:27 System.map-3.16-1-686-pae
-rw-r--r-- 1  159879 09-13 14:27 config-3.16-1-686-pae
-rw-r--r-- 1 3003440 09-13 14:25 vmlinuz-3.16-1-686-pae
-rw-r--r-- 1 2750492 09-11 10:37 initrd.img-3.14-2-686-pae
-rw-r--r-- 1 1933464 08-09 16:44 System.map-3.14-2-686-pae
-rw-r--r-- 1  157566 08-09 16:44 config-3.14-2-686-pae
-rw-r--r-- 1 2833376 08-09 16:42 vmlinuz-3.14-2-686-pae

so I chose the oldest one from the grub menu and was able to boot.


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/87wq8r81oy@jidanni.org

Bug#757380: adding boot_delay=1000 to the boot command line results in black screens

[積丹尼 Dan Jacobson]

Package: src:linux
Version: 3.14.13-2

Despite https://lkml.org/lkml/2012/11/13/40
adding boot_delay=1000 to the boot command line results in black screens.


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/87egwse4it@jidanni.org

Bug#757380: try boot_delay=1 etc.

[積丹尼 Dan Jacobson]

Please try boot_delay=1 , 10, 100, 1000 .

With 1 one indeed sees messages after a minute . (Tested with no quiet.)

With the others you'll be waiting a long time.

But with 1 messages fly by, so the point is lost.

And with the others who can wait so long?


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/878un0e38h@jidanni.org

Bug#756820: keep hands off intel_backlight/brightness when switching to tty1-6

[積丹尼 Dan Jacobson]

Package: src:linux
Version: 3.14.13-2

On Lenovo (my other non-Lenovo are fine) G580,
switching from X on tty7 to any of tty1...6 gives a very dim screen.
So one must hit Fn Up Arrow (or Fn Down Arrow), after which one can read
the screen again.
Switching back to tty7 and then back again to tty1-6 recreates the
problem.

Running

printf '%3d %3d %3d | %3d %3d %3d\n' $(
cat \
/sys/class/backlight/intel_backlight/*brightness \
/sys/class/backlight/acpi_video0/*brightness
)

before and after hitting a Fn Down Arrow shows

  7   7 976 |  15  15  15
838 838 976 |  14  14  15

Therefore something is messing with
/sys/class/backlight/intel_backlight/brightness ,
knocking it down to 7, when it should keep its hands off!


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/87r40zvb98@jidanni.org

Bug#756820: one tap enough

[積丹尼 Dan Jacobson]

Note that one tap of Fn Up Arrow or Fn Down Arrow is enough to 'wake up
the brightness' from the depths. There are no need for several taps.


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/87mwbnvaut@jidanni.org

Bug#736899: tons of [drm:i915_stolen_to_physical] *ERROR* in syslog every day

[積丹尼 Dan Jacobson]

found 736899 linux/3.13.7-1
thanks

Tons of these everyday
[drm:i915_stolen_to_physical] *ERROR* conflict detected with stolen region: 
[0x3f80 - 0x4000]
[drm:intel_pipe_config_compare] *ERROR* mismatch in 
adjusted_mode.flags(DRM_MODE_FLAG_NHSYNC) (expected 2, found 0)
[drm:intel_pipe_config_compare] *ERROR* mismatch in gmch_pfit.lvds_border_bits 
(expected 32768, found 0)
I said to myself, here on my jidanni3 machine.


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/87fvly99k9@jidanni.org