Bug#1033937: system does a poweroff instead of reboot
Source: linux-signed-amd64
Version: 6.1.12+1~bpo11+1
Severity: normal
Hi!
While running linux-image-6.1.0-0.deb11.5-amd64 on bullseye (with stable
systemd or with backports systemd), when I type reboot, the system goes
down for reboot but then powers off.
This issue is not present in the stable kernel, but I have also observed
it in linux-image-6.0.0-0.deb11.6-amd64.
The system is a ProLiant DL360 Gen10 Plus (P28948-B21).
| Starting virtual serial port.
| Press 'ESC (' to return to the CLI Session.
|
| [1203707.236892] watchdog: watchdog0: watchdog did not stop!
| [1203707.766484] systemd-shutdown[1]: Failed to finalize DM devices, ignoring.
| [1203708.709332] reboot: Restarting system
[several seconds later]
| The server is not powered on. The Virtual Serial Port is not available.
and:
| hpiLO-> power
|
| status=0
| status_tag=COMMAND COMPLETED
| Tue Apr 4 10:45:22 2023
|
|
|
| power: server power is currently: Off
It'd be nice if the system actually rebooted on a reboot :)
Cheers,
weasel
--
| .''`. ** Debian **
Peter Palfrader | : :' : The universal
https://www.palfrader.org/ | `. `' Operating System
| `-https://www.debian.org/
Bug#939873: qla2xxx .. Async-gnlist failed
Package: src:linux Version: 4.19.67-2 Severity: important The buster kernel, as well as the backports kernel (linux-image-5.2.0-0.bpo.2-amd64 5.2.9-2~bpo10+1) fail to boot sibelius.debian.org, which has some storage attached to it via, presumably, FC. The kernel keeps printing | qla2xxx [...]-...: Async-gpdb failed - hdl=.. ... and systemd keeps waiting for the devices to appear. Screenshot of remote console attached. -- | .''`. ** Debian ** Peter Palfrader | : :' : The universal https://www.palfrader.org/ | `. `' Operating System | `-https://www.debian.org/
Bug#906769: arm kernels fail to boot
Package: linux-image-4.9.0-8-arm64 Version: 4.9.110-3+deb9u3 Severity: critical X-Debbugs-Cc: d...@debian.org The latest kernel fails to boot on our arm64 hosts at conova (Gigabyte X-Gene MP30-AR0) and the VMs on those hosts. Booting the old -7 kernel works one those. After grub, the last thing I see is | OSBootEvent = Success | L3c Cache: 8MB Furthermore, arm-arm-0[134] are down. According to our documentation those are AMD Seattle rev B0, APM X-Gene, and AMD Seattle rev B1 systems. Also, some 32 bit hosts appear to be affected, though I have not yet looked into them in detail. However, abel and arnold, hartmann, hoiby (Armada XP GP), and henze (probably also the same hw) are all down. harris (imx53 QSB) booted just fine. It's -- from a quick glance -- the only arm* host of us that survived this kernel update. Cheers, -- | .''`. ** Debian ** Peter Palfrader | : :' : The universal https://www.palfrader.org/ | `. `' Operating System | `-https://www.debian.org/
Bug#856111: closed by Ben Hutchings <b...@decadent.org.uk> (Bug#856111: fixed in linux 4.9.13-1)
s=14 max_order=18 bucket_order=4
} [1.368692] zbud: loaded
} [1.731182] Key type asymmetric registered
} [1.731208] Asymmetric key parser 'x509' registered
} [1.731317] bounce: pool size: 64 pages
} [1.731473] Block layer SCSI generic (bsg) driver version 0.4 loaded
(major 248)
} [1.731689] io scheduler noop registered
} [1.731704] io scheduler deadline registered
} [1.731804] io scheduler cfq registered (default)
} [1.738475] sun7i-a20-pinctrl 1c20800.pinctrl: initialized sunXi PIO driver
} [1.755477] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
} [1.758333] console [ttyS0] disabled
} [1.778602] 1c28000.serial: ttyS0 at MMIO 0x1c28000 (irq = 45, base_baud =
150) is a U6_16550A
} [2.489692] console [ttyS0] enabled
} [2.516892] 1c28c00.serial: ttyS1 at MMIO 0x1c28c00 (irq = 46, base_baud =
150) is a U6_16550A
} [2.549618] 1c29c00.serial: ttyS2 at MMIO 0x1c29c00 (irq = 47, base_baud =
150) is a U6_16550A
} [2.559643] Serial: AMBA driver
} [2.566456] libphy: Fixed MDIO Bus: probed
} [2.571695] mousedev: PS/2 mouse device common for all mice
} [2.579851] sunxi-rtc 1c20d00.rtc: rtc core: registered rtc-sunxi as rtc0
} [2.586691] sunxi-rtc 1c20d00.rtc: RTC enabled
} [2.594002] ledtrig-cpu: registered to indicate activity on CPUs
} [2.601202] NET: Registered protocol family 10
} [2.607013] mip6: Mobile IPv6
} [2.610062] NET: Registered protocol family 17
} [2.614562] mpls_gso: MPLS GSO support
} [2.618410] ThumbEE CPU extension supported.
} [2.622719] Registering SWP/SWPB emulation handler
} [2.628680] registered taskstats version 1
} [2.632852] Loading compiled-in X.509 certificates
} [2.650659] alg: No test for pkcs1pad(rsa,sha256)
(pkcs1pad(rsa-generic,sha256))
} [2.660319] Loaded X.509 cert 'Debian Project: Ben Hutchings:
008a018dca80932630'
} [2.668063] zswap: loaded using pool lzo/zbud
} [2.684003] sunxi-rtc 1c20d00.rtc: setting system clock to 1970-01-01
00:05:47 UTC (347)
} [2.692172] sr_init: No PMIC hook to init smartreflex
} [2.697458] sr_init: platform driver register failed for SR
} [2.703522] vcc3v0: disabling
} [2.706497] vcc3v3: disabling
} [2.709577] vcc5v0: disabling
} [2.712573] usb0-vbus: disabling
} [2.715800] usb1-vbus: disabling
} [2.719051] usb2-vbus: disabling
} [2.722292] gmac-3v3: disabling
} [2.727277] Freeing unused kernel memory: 1024K (c0b0 - c0c0)
} [2.799383] random: systemd-udevd: uninitialized urandom read (16 bytes
read)
} [2.807738] random: udevadm: uninitialized urandom read (16 bytes read)
} [2.807786] random: systemd-udevd: uninitialized urandom read (16 bytes
read)
} [2.807901] random: systemd-udevd: uninitialized urandom read (16 bytes
read)
} [2.830916] random: udevadm: uninitialized urandom read (16 bytes read)
} [2.838291] random: udevadm: uninitialized urandom read (16 bytes read)
} [2.845707] random: udevadm: uninitialized urandom read (16 bytes read)
} [2.852986] random: udevadm: uninitialized urandom read (16 bytes read)
} [2.860170] random: udevadm: uninitialized urandom read (16 bytes read)
} [2.867554] random: udevadm: uninitialized urandom read (16 bytes read)
} [3.181352] usbcore: registered new interface driver usbfs
} [3.187132] usbcore: registered new interface driver hub
} [3.192994] usbcore: registered new device driver usb
} [3.24] sunxi-mmc 1c0f000.mmc: Got CD GPIO
} [3.291794] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
} [3.297416] sunxi-mmc 1c0f000.mmc: base:0xf08fd000 irq:28
} [3.354854] mmc0: host does not support reading read-only switch, assuming
write-enable
} [3.366826] ehci-platform: EHCI generic platform driver
} [3.383189] mmc0: new high speed SDHC card at address b368
} [3.385990] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
} [3.391851] ohci-platform: OHCI generic platform driver
} [3.400238] SCSI subsystem initialized
} [3.496324] mmcblk0: mmc0:b368 SDC 30.2 GiB
} [3.507383] mmcblk0: p1
} [3.542290] ahci-sunxi 1c18000.sata: controller can't do PMP, turning off
CAP_PMP
} [3.549870] ahci-sunxi 1c18000.sata: forcing PORTS_IMPL to 0x1
} [3.555964] ahci-sunxi 1c18000.sata: AHCI 0001.0100 32 slots 1 ports 3
Gbps 0x1 impl platform mode
} [3.565033] ahci-sunxi 1c18000.sata: flags: ncq sntf pm led clo only pio
slum part ccc
} [3.575075] scsi host0: ahci-sunxi
} [3.579183] ata1: SATA max UDMA/133 mmio [mem 0x01c18000-0x01c18fff] port
0x100 irq 33
} [3.908699] ata1: SATA link down (SStatus 0 SControl 300)
} Starting system log daemon: syslogd, klogd.
[curses stuff starts up]
--
| .''`. ** Debian **
Peter Palfrader | : :' : The universal
https://www.palfrader.org/ | `. `' Operating System
| `-https://www.debian.org/
Bug#856111: closed by Ben Hutchings <b...@decadent.org.uk> (Bug#856111: fixed in linux 4.9.13-1)
On Wed, 01 Mar 2017, Ben Hutchings wrote:
> > I retried with the images from March 1st, which should include
> > 4.9.13-1 according to
> > https://d-i.debian.org/daily-images/armhf/20170301-00:17/build_hd-media.log
> >
> > I still have no keyboard in d-i.
>
> The installer now seems to include all the USB drivers for this
> platform, and all the HID drivers we build. So I'm puzzled as to what
> might be missing.
>
> Do you have a serial console that could be used to debug this further?
No, I don't currently have the right connectors needed to get that
going. Hm.
--
| .''`. ** Debian **
Peter Palfrader | : :' : The universal
https://www.palfrader.org/ | `. `' Operating System
| `-https://www.debian.org/
Bug#856111: closed by Ben Hutchings <b...@decadent.org.uk> (Bug#856111: fixed in linux 4.9.13-1)
control: reopen -1 >* udeb: Add more USB host and dual-role drivers to usb-modules > (Closes: #856111) I wrote previously: > After copying the firmware and installer to the SDcard, I set the > environment and booted the installer in uboot using: > | setenv console tty1 > | setenv bootargs console=tty1 fb=false > | boot > > The kernel boots, the syslogger starts, I get prompted with the > 'Select a language' dialog, but my USB keyboard does not work in d-i (it > did in uboot). I retried with the images from March 1st, which should include 4.9.13-1 according to https://d-i.debian.org/daily-images/armhf/20170301-00:17/build_hd-media.log I still have no keyboard in d-i. Cheers, weasel -- | .''`. ** Debian ** Peter Palfrader | : :' : The universal https://www.palfrader.org/ | `. `' Operating System | `-https://www.debian.org/
Bug#853170: fails to boot on debian's MP30-AR1 systems [regression]
.. ] Starting LSB: Start or stop stunnel 4.x (SSL tunnel ...ork daemons)... ] Starting LSB: Start NTP daemon... ] Starting (null)... ] Starting LSB: Start Bacula File Daemon at boot time... ] Starting LSB: Entropy Key Manager, EGD->Linux pool stirrer... ] Starting LSB: Initialize EDAC... ] Starting (null)... ] Starting (null)... ] Starting D-Bus System Message Bus... ] [7.118611] random: crng init done ] [ OK ] Started D-Bus System Message Bus. ] Starting Virtualization daemon... ] Starting Permit User Sessions... ] [ OK ] Started LLDP daemon. ] [ OK ] Started Munin Node. ] [ OK ] Started Netfilter Userspace Logging Daemon. ] [7.211591] xgene-enet 1f21.ethernet eth0: Link is Down ] [ OK ] Started /etc/rc.local Compatibility. ] [ OK ] Started LSB: Start or stop stunnel 4.x (SSL tunnel f...twork daemons). ] [7.243581] xgene-enet 1f210030.ethernet eth1: Link is Down ] [ OK ] Started LSB: Start NTP daemon. ] [ OK ] Started (null). ] [ OK ] Started LSB: Start Bacula File Daemon at boot time. ] [ OK ] Started LSB: Entropy Key Manager, EGD->Linux pool stirrer. ] [ OK ] Started LSB: Initialize EDAC. ] [ OK ] Started (null). ] [ OK ] Started Permit User Sessions. ] [ OK ] Started Virtualization daemon. ] [ OK ] Started Login Service. ] Starting Suspend/Resume Running libvirt Guests... ] Starting System Logger Daemon... ] [ OK ] Reached target Host and Network Name Lookups. ] Starting LSB: exim Mail Transport Agent... ] Starting LSB: Open vSwitch switch... ] Starting LSB: Start/Stop the Nagios remote plugin execution daemon... ] Starting Getty on tty1... ] [ OK ] Started Getty on tty1. ] Starting Serial Getty on ttyS0... ] [ OK ] Started Serial Getty on ttyS0. ] [ OK ] Reached target Login Prompts. ] Starting Munin Node - asynchronous proxy... ] [ OK ] Started Munin Node - asynchronous proxy. ] [ OK ] Started Suspend/Resume Running libvirt Guests. ] [FAILED] Failed to start System Logger Daemon. ] See 'systemctl status syslog-ng.service' for details. ] [ OK ] Started LSB: exim Mail Transport Agent. ] [ OK ] Started LSB: Start/Stop the Nagios remote plugin execution daemon. ] [7.724317] openvswitch: Open vSwitch switching datapath ] [7.755506] scsi 4:0:0:0: CD-ROMMP EMS Virtual Media0326 PQ: 0 ANSI: 0 ] [7.766445] scsi 4:0:0:1: Direct-Access MP EMS Virtual Media0326 PQ: 0 ANSI: 0 CCS ] [7.775499] scsi 4:0:0:2: Direct-Access MP EMS Virtual Media0326 PQ: 0 ANSI: 0 CCS ] [7.784696] scsi 4:0:0:0: Attached scsi generic sg2 type 5 ] [7.790719] sd 4:0:0:1: Attached scsi generic sg3 type 0 ] [7.796602] sd 4:0:0:2: Attached scsi generic sg4 type 0 ] [7.912420] sr 4:0:0:0: [sr0] scsi3-mmc drive: 0x/0x cd/rw caddy ] [7.918430] cdrom: Uniform CD-ROM driver Revision: 3.20 ] [7.920581] sd 4:0:0:2: [sdd] Attached SCSI removable disk ] [7.920918] sd 4:0:0:1: [sdc] Attached SCSI removable disk ] [8.065309] d950] openvswitch: netlink: Key type 62 is out of range max 26 ] [8.103092] device eth0 entered promiscuous mode ] [8.112958] device br-inet entered promiscuous mode ] [ OK ] Created slice system-ifup.slice. ] Starting ifup for br-inet... ] [ OK ] Started ifup for br-inet. ] [ OK ] Started LSB: Open vSwitch switch. ] [8.298807] xgene-enet 1f61.ethernet eth2: Link is Up - 10Gbps ] [8.304993] IPv6: ADDRCONF(NETDEV_CHANGE): eth2: link becomes ready ] [ OK ] Started (null). ] [ OK ] Reached target Multi-User System. ] [ OK ] Reached target Graphical Interface. ] Starting Update UTMP about System Runlevel Changes... ] [ OK ] Started Update UTMP about System Runlevel Changes. ] [9.260153] xgene-enet 1f21.ethernet eth0: Link is Up - 1Gbps/Full - flow control off ] [9.295203] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready ] [9.301572] xgene-enet 1f210030.ethernet eth1: Link is Up - 1Gbps/Full - flow control off ] ] Debian GNU/Linux 8 aagaard ttyS0 ] ] aagaard login: [ 10.191904] efi_call_virt_check_flags: 75 callbacks suppressed ] [ 10.197723] efi: [Firmware Bug]: IRQ flags corrupted (0x0140=>0x0100) by EFI set_time ] [ 10.206306] efi: [Firmware Bug]: IRQ flags corrupted (0x0140=>0x0100) by EFI get_time ] [ 12.143611] 8021q: 802.1Q VLAN Support v1.8 -- | .''`. ** Debian ** Peter Palfrader | : :' : The universal https://www.palfrader.org/ | `. `' Operating System | `-https://www.debian.org/
Bug#853170: fails to boot on debian's MP30-AR1 systems [regression]
] V28 0xC000C2D4C018 00028A005180 V29 0x104022036000 54204050082D0C08 ] V30 0x84300804 0040801080004048 V31 0x424202010206 0504421020242840 ] ] SP 0x000FFFE36410 ELR 0x00807954A740 SPSR 0x0309 FPSR 0x288A ] ESR 0x9621 FAR 0x008079BC369D ] ] ESR : EC 0x25 IL 0x1 ISS 0x0021 ] ] Data abort: Alignment fault [..] -- | .''`. ** Debian ** Peter Palfrader | : :' : The universal https://www.palfrader.org/ | `. `' Operating System | `-https://www.debian.org/
Bug#851695: replacing base package with -unsigned removes module files
-4.9.0-1-amd64 } (Reading database ... 26396 files and directories currently installed.) } Purging configuration files for linux-image-4.9.0-1-amd64 (4.9.2-2) ... } I: /vmlinuz is now a symlink to boot/vmlinuz-4.8.0-2-amd64 } I: /initrd.img is now a symlink to boot/initrd.img-4.8.0-2-amd64 } rmdir: failed to remove '/lib/modules/4.9.0-1-amd64': Directory not empty } root@sid:~# ls -l /lib/modules/4.9.0-1-amd64/ } total 136 } drwxr-xr-x 12 root root 4096 Jan 17 19:39 kernel } -rw-r--r-- 1 root root 4027 Jan 12 16:52 modules.builtin } -rw-r--r-- 1 root root 130336 Jan 12 16:52 modules.order } root@sid:~# Same in the other direction: ] root@sid:~# ls -l /lib/modules/4.9.0-1-amd64/ ] total 4048 ] drwxr-xr-x 12 root root4096 Jan 17 19:44 kernel ] -rw-r--r-- 1 root root 1004588 Jan 17 19:44 modules.alias ] -rw-r--r-- 1 root root 963236 Jan 17 19:44 modules.alias.bin ] -rw-r--r-- 1 root root4027 Jan 12 16:52 modules.builtin ] -rw-r--r-- 1 root root5485 Jan 17 19:44 modules.builtin.bin ] -rw-r--r-- 1 root root 386694 Jan 17 19:44 modules.dep ] -rw-r--r-- 1 root root 535244 Jan 17 19:44 modules.dep.bin ] -rw-r--r-- 1 root root 402 Jan 17 19:44 modules.devname ] -rw-r--r-- 1 root root 130336 Jan 12 16:52 modules.order ] -rw-r--r-- 1 root root 523 Jan 17 19:44 modules.softdep ] -rw-r--r-- 1 root root 483974 Jan 17 19:44 modules.symbols ] -rw-r--r-- 1 root root 598780 Jan 17 19:44 modules.symbols.bin ] root@sid:~# dpkg -l | grep linux-ima ] ii linux-image-4.8.0-2-amd64 4.8.15-2amd64 Linux 4.8 for 64-bit PCs (signed) ] ii linux-image-4.9.0-1-amd64 4.9.2-2 amd64 Linux 4.9 for 64-bit PCs (signed) ] rc linux-image-4.9.0-1-amd64-unsigned 4.9.2-2 amd64 Linux 4.9 for 64-bit PCs ] ii linux-image-amd64 4.9+78 amd64 Linux for 64-bit PCs (meta-package) ] root@sid:~# dpkg --purge linux-image-4.9.0-1-amd64-unsigned ] (Reading database ... 26398 files and directories currently installed.) ] Purging configuration files for linux-image-4.9.0-1-amd64-unsigned (4.9.2-2) ... ] I: /vmlinuz is now a symlink to boot/vmlinuz-4.8.0-2-amd64 ] I: /initrd.img is now a symlink to boot/initrd.img-4.8.0-2-amd64 ] rmdir: failed to remove '/lib/modules/4.9.0-1-amd64': Directory not empty ] root@sid:~# dpkg -l | grep linux-ima ] ii linux-image-4.8.0-2-amd64 4.8.15-2amd64 Linux 4.8 for 64-bit PCs (signed) ] ii linux-image-4.9.0-1-amd64 4.9.2-2 amd64 Linux 4.9 for 64-bit PCs (signed) ] ii linux-image-amd64 4.9+78 amd64 Linux for 64-bit PCs (meta-package) ] root@sid:~# ls -l /lib/modules/4.9.0-1-amd64/ ] total 136 ] drwxr-xr-x 12 root root 4096 Jan 17 19:44 kernel ] -rw-r--r-- 1 root root 4027 Jan 12 16:52 modules.builtin ] -rw-r--r-- 1 root root 130336 Jan 12 16:52 modules.order ] root@sid:~# -- | .''`. ** Debian ** Peter Palfrader | : :' : The universal https://www.palfrader.org/ | `. `' Operating System | `-https://www.debian.org/
Bug#819881: radeon_fence_ref BUG: unable to handle kernel NULL pointer dereference
Ben Hutchings schrieb am Sonntag, dem 03. April 2016:
> > with the latest jessie kernel, my system freezes when I visit certain
> > webpages in iceweasel (such as the system upgrade page from my
> > mikrotik
> > router).
> All three call traces are very similar and, based on the functions
> listed, I believe the attached patch (taken from the next 3.16.7-ckt
> stable update) should fix the bug. Please test that, following the
> instructions at
That seems to do it. Thanks for the quick turnaround.
> <https://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-official>
(nice documentation too!)
Cheers,
weasel
--
| .''`. ** Debian **
Peter Palfrader | : :' : The universal
https://www.palfrader.org/ | `. `' Operating System
| `-https://www.debian.org/
Re: broken mount behaviour on jessie
On Mon, 01 Feb 2016, Brian May wrote:
> Michael Biebl <bi...@debian.org> writes:
>
> > Have you tried the patch in
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786566
>
> I see two patches here - one patch applies easy enough to schroot -
> 1.6-schroot-mount-make-bind-mounts-private.patch
>
> I am not sure what the
> master-libexec-mount-make-bind-mounts-private.patch is for, it seems to
> patch files not in schroot but has references to schroot files.
>
> Do I need the 2nd patch or is the 1st one sufficient?
The first seems to have helped significantly for schroot.
It doesn't, of course, fix the inherent brokeness that can be observed
by the sysadmin doing other mount things.
Also, it is still racy, as it first mounts the target and afterwards
modifies flags.
Cheers,
--
| .''`. ** Debian **
Peter Palfrader | : :' : The universal
https://www.palfrader.org/ | `. `' Operating System
| `-https://www.debian.org/
broken mount behaviour on jessie
Trying to figure out why my schroot builds keep failing after upgrading to jessie, I finally narrowed it down to broken behaviour with mount on jessie: } root@valiant:/mnt# find } . } ./tmp1 } ./tmp1/dev } ./tmp0 } ./tmp0/dev Two trees, with a dev directory each. Let's mount /dev and /dev/pts there: } root@valiant:/mnt# /bin/mount -v -t none -o rw,bind /dev tmp0/dev } mount: /dev bound on /mnt/tmp0/dev. } root@valiant:/mnt# /bin/mount -v -t none -o rw,bind /dev/pts tmp0/dev/pts } mount: /dev/pts bound on /mnt/tmp0/dev/pts. } root@valiant:/mnt# grep /mnt /proc/mounts } udev /mnt/tmp0/dev devtmpfs rw,relatime,size=10240k,nr_inodes=3087992,mode=755 0 0 } devpts /mnt/tmp0/dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0 Seems to have worked. Yay. Now the second tree: } root@valiant:/mnt# /bin/mount -v -t none -o rw,bind /dev tmp1/dev } mount: /dev bound on /mnt/tmp1/dev. } root@valiant:/mnt# grep /mnt /proc/mounts } udev /mnt/tmp0/dev devtmpfs rw,relatime,size=10240k,nr_inodes=3087992,mode=755 0 0 } devpts /mnt/tmp0/dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0 } udev /mnt/tmp1/dev devtmpfs rw,relatime,size=10240k,nr_inodes=3087992,mode=755 0 0 So far, so good. Now for /dev/pts: } root@valiant:/mnt# /bin/mount -v -t none -o rw,bind /dev/pts tmp1/dev/pts } mount: /dev/pts bound on /mnt/tmp1/dev/pts. } root@valiant:/mnt# grep /mnt /proc/mounts } udev /mnt/tmp0/dev devtmpfs rw,relatime,size=10240k,nr_inodes=3087992,mode=755 0 0 } devpts /mnt/tmp0/dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0 } udev /mnt/tmp1/dev devtmpfs rw,relatime,size=10240k,nr_inodes=3087992,mode=755 0 0 } devpts /mnt/tmp1/dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0 } devpts /mnt/tmp0/dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0 Something's fishy here. Note how there is now a second mount on tmp0/dev/pts. This is a real problem as exhibited in these two use-cases: o) you cannot unmount the tmp0 tree while the tmp1 tree is busy: } root@valiant:/mnt# (cd tmp1/dev/pts ; sleep 10 &) } root@valiant:/mnt# umount /mnt/tmp0/dev/pts } umount: /mnt/tmp0/dev/pts: target is busy } (In some cases useful info about processes that } use the device is found by lsof(8) or fuser(1).) o) if it's not busy, and you try to umount the tmp0 tree, you mess with the tmp1 tree instead: } root@valiant:/mnt# ls /mnt/tmp0/dev/pts } 0 1 10 11 13 14 15 16 17 18 19 2 20 21 22 23 24 25 26 3 4 5 6 7 8 ptmx } root@valiant:/mnt# ls /mnt/tmp1/dev/pts } 0 1 10 11 13 14 15 16 17 18 19 2 20 21 22 23 24 25 26 3 4 5 6 7 8 ptmx } root@valiant:/mnt# umount /mnt/tmp0/dev/pts } root@valiant:/mnt# ls /mnt/tmp0/dev/pts } 0 1 10 11 13 14 15 16 17 18 19 2 20 21 22 23 24 25 26 3 4 5 6 7 8 ptmx } root@valiant:/mnt# ls /mnt/tmp1/dev/pts } root@valiant:/mnt# It has been suggested on IRC that this is due to systemd mounting filesystems with O_SHARE. Regardless of why, these two things at the bottom are horribly broken. We need to fix this somehow. Cheers, -- | .''`. ** Debian ** Peter Palfrader | : :' : The universal https://www.palfrader.org/ | `. `' Operating System | `-https://www.debian.org/
Bug#711135: caballero.debian.org does not boot on wheezy kernels
} SFW 0 1 0x20A400E0 MEM_CONFIG } SFW 0 0 0x00B100E0 MEM_DISCOVERY } SFW 0 0 0x00DF00E0 MEM_RESET } SFW 0 0 0x00C600E0 MEM_INIT_SCR_TABLES } SFW 0 1 0x20FE00E0 MEM_WARN_REG_TEST_BYPASS } SFW 0 0 0x00EC00E0 MEM_SPD_START } SFW 0 0 0x00A600E0 MEM_CONFIG_FROM_NVM } SFW 0 0 0x04E300E0 000AFF74 MEM_SPD_1G_DIMM_FOUND } SFW 0 0 0x04E300E0 000BFF74 MEM_SPD_1G_DIMM_FOUND } SFW 0 0 0x04E300E0 001AFF74 MEM_SPD_1G_DIMM_FOUND } SFW 0 0 0x04E300E0 001BFF74 MEM_SPD_1G_DIMM_FOUND } SFW 0 0 0x020500E0 MEM_LOADING_ORDER } SFW 0 0 0x00B200E0 MEM_DISCOVERY_EXIT } SFW 0 0 0x00C900E0 MEM_MAIN_MEM } SFW 0 0 0x00C200E0 MEM_GENERATE_INTERLEAVING } SFW 0 0 0x00A800E0 MEM_DEST_TEST } SFW 0 0 0x00CE00E0 MEM_MEM_TEST } SFW 0 0 0x00B800E0 MEM_ECC_TEST } SFW 0 0 0x00F600E0 MEM_TEST_WRITE } SFW 0 0 0x16F700E0 0032 MEM_TEST_WRITE_BARGRAPH } SFW 0 0 0x16F700E0 0064 MEM_TEST_WRITE_BARGRAPH } SFW 0 0 0x00F100E0 MEM_TEST_READ_WRITE } SFW 0 0 0x16F200E0 0032 MEM_TEST_READ_WRITE_BARGRAPH } SFW 0 0 0x16F200E0 0064 MEM_TEST_READ_WRITE_BARGRAPH } SFW 0 0 0x00EF00E0 MEM_TEST_READ } SFW 0 0 0x16F000E0 0032 MEM_TEST_READ_BARGRAPH } SFW 0 0 0x16F000E0 0064 MEM_TEST_READ_BARGRAPH } SFW 0 0 0x00A500E0 MEM_CONFIG_EXIT } SFW 0 0 0x002600E0 BOOT_CPU_LATE_TEST_START } SFW 1 0 0x165E01E0 0903 BOOT_SLAVE_RENDEZ_INT_RECEIVED } SFW 1 0 0x002601E0 BOOT_CPU_LATE_TEST_START } SFW 1 0 0x166001E0 0001 BOOT_SLAVE_RENDEZ_STAGE_2 } SFW 1 0 0x165E01E0 0257 BOOT_SLAVE_RENDEZ_INT_RECEIVED } SFW 1 0 0x166101E0 0001 BOOT_SLAVE_RENDEZ_STAGE_3 } SFW 0 0 0x024E00E0 BOOT_FINAL_PLATFORM_CHECK } SFW 0 1 0x361400E0 BOOT_CELL_RELOCATION_START } SFW 0 0 0x001200E0 BOOT_CELL_RELOCATE_PAL } SFW 0 0 0x001300E0 BOOT_CELL_RELOCATE_SAL } SFW 0 0 0x000F00E0 BOOT_CELL_RELOCATE_ACPI } SFW 0 0 0x000700E0 BOOT_CELL_BUILD_SYS_TABLES } SFW 0 0 0x001000E0 BOOT_CELL_RELOCATE_EFI } SFW 0 0 0x001100E0 BOOT_CELL_RELOCATE_IVT } SFW 0 1 0x200900E0 BOOT_CELL_LAUNCH_EFI } } * } } EARLY BOOT VFP * } End of early boot detected } * [system reboots] -- | .''`. ** Debian ** Peter Palfrader | : :' : The universal http://www.palfrader.org/ | `. `' Operating System | `-http://www.debian.org/ -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20131130233715.gb28...@anguilla.noreply.org
Bug#711294: random lockups
Package: linux-image-3.2.0-4-sparc64-smp Version: 3.2.41-2+deb7u2 Severity: important Hi, smetana.debian.org, running our wheezy 3.2 kernel, locks up regularly. It runs quite reliably using the squeeze kernel. When it locks up it still responds to pings but one cannot login. I saw this on the console last time it had this problem: [443310.647567] BUG: NMI Watchdog detected LOCKUP on CPU0, ip 00438e00, registers: [443310.743716] TSTATE: 11e01605 TPC: 00438e00 TNPC: 00438e04 Y: Not tainted [443310.874123] TPC: cheetah_xcall_deliver+0x1a8/0x240 [443310.940537] g0: 6e6e656c3a20 g1: 0004 g2: 0002 g3: [443311.056064] g4: f8103f1c32e0 g5: f8acc000 g6: f834 g7: 0001869f [443311.171583] o0: 0001 o1: o2: o3: [443311.287104] o4: o5: sp: f8342e81 ret_pc: 000c [443311.407232] RPC: 0xc [443311.439320] l0: 0001 l1: l2: 000186a0 l3: f8003f818040 [443311.554847] l4: 0050 l5: 0040 l6: 008f4a48 l7: [443311.670365] i0: f8003f818000 i1: 0001 i2: 0008 i3: 0016 [443311.785886] i4: f8003f818040 i5: i6: f8342f31 i7: 00438b04 [443311.901408] I7: xcall_deliver+0xdc/0x104 [443311.956296] Call Trace: [443311.989469] [00438b04] xcall_deliver+0xdc/0x104 [443312.060384] [00439634] flush_dcache_page_all+0x90/0xf4 [443312.139310] [004fa740] move_page_tables+0x2e4/0x400 [443312.214794] [0051bb0c] shift_arg_pages+0x80/0x120 [443312.287990] [0051bcb4] setup_arg_pages+0x108/0x1a8 [443312.362343] [0055ba00] load_elf_binary+0x418/0x1194 [443312.437824] [0051b538] search_binary_handler+0x12c/0x3a0 [443312.519031] [0051cd88] do_execve_common.isra.17+0x198/0x294 [443312.603676] [004406a0] sparc32_execve+0x64/0xa8 [443312.674588] [00406134] linux_sparc_syscall32+0x34/0x40 [443312.753497] Call Trace: [443312.786670] [004209f4] tl0_irq15+0x14/0x20 [443312.851863] [00438e00] cheetah_xcall_deliver+0x1a8/0x240 [443312.933070] [00438b04] xcall_deliver+0xdc/0x104 [443313.003984] [00439634] flush_dcache_page_all+0x90/0xf4 [443313.082902] [004fa740] move_page_tables+0x2e4/0x400 [443313.158390] [0051bb0c] shift_arg_pages+0x80/0x120 [443313.231589] [0051bcb4] setup_arg_pages+0x108/0x1a8 [443313.305935] [0055ba00] load_elf_binary+0x418/0x1194 [443313.381424] [0051b538] search_binary_handler+0x12c/0x3a0 [443313.462630] [0051cd88] do_execve_common.isra.17+0x198/0x294 [443313.547270] [004406a0] sparc32_execve+0x64/0xa8 [443313.618182] [00406134] linux_sparc_syscall32+0x34/0x40 That message never made it to /var/log on the host itself or to the loghosts. This bug might be the same as #648766. If so, please merge. Cheers, weasel -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130606065823.ga8...@valiant.palfrader.org
Re: Donation of a Calxeda Highbank node
On Fri, 26 Apr 2013, Steve Langasek wrote: On Fri, Apr 26, 2013 at 02:49:05PM +0200, Hector Oron wrote: Thanks, that is a very kind offer and with ARM hat on, we cannot reject the offer, it makes it very interesting as a playground machine. However, let me make some points here: * ARM porters hat: It is very interesting machine, and very useful to start experimenting with it as Debian is seeking for a full Calxeda chassis. * DSA hat: The machine shall not be a debian.org machine, so DSA could export accounts if requested. Why in the world not? I'm sure there's no requirement for debian.org machines to be hardware owned by Debian. The s390 porter machines/buildds certainly aren't; I don't see why this machine would necessarily *not* be a d.o machine managed by DSA. Of course if it's going to be DSA-administered, I'm sure DSA would want exclusive admin rights on the machine; but that's just common sense, and AIUI not excluded by the offer. The impression I got during the brief from the arm porters is that it is so far unclear how well Debian will run on this nice shiney thing. So for now it's just a test box/early porting box, and the policies and procedures that come with DSAing a machine would be more a hindrance than an asset during that stage. Also, if it were a d.o system, it would be /either/ a porterbox /or/ a buildd, not both. Whereas, as long as it's a test/play system run by the porters presumably, they can stress test is at needed, maybe run a (non-official?) buildd, while also providing porter chroots. Once we have Debian running properly on this kind of HW, I wouldn't mind taking over the machine. Though, to be really useful, we probably will try to get more than one instance, one for a porterbox, and two - ideally in different locations - for autobuilding packages. Cheers, weasel -- | .''`. ** Debian ** Peter Palfrader | : :' : The universal http://www.palfrader.org/ | `. `' Operating System | `-http://www.debian.org/ -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130427073259.gx23...@anguilla.noreply.org
Re: Donation of a Calxeda Highbank node
On Fri, 26 Apr 2013, Raphael Hertzog wrote: To be a useful porter machine, it would be nice if all DD can have access to it. But if it's not administrated by DSA, I don't know if the newly announced self-served chroot service can be setup on this machine. Neither of these require the machine to be DSA administered. We can help in setting these up initially, and I assume Hector would be happy to take a more hands-on approach there. Cheers -- | .''`. ** Debian ** Peter Palfrader | : :' : The universal http://www.palfrader.org/ | `. `' Operating System | `-http://www.debian.org/ -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130427073625.gy23...@anguilla.noreply.org
Bug#697357: bridging broken over bond interfaces
Package: linux-image-3.2.0-4-amd64 Version: 3.2.35-2 Severity: important Hi, I tried to set up a new KVM host in the usual way: - have a bond0 interface over all physcial eth* interfaces - create a br0 over that bond0 and any vnet* interfaces for the guests. on wheezy's 3.2.0-4-amd64 this setup results in network breaking in the following way: - host can talk to guest and vice versa, - host can talk to other hosts on the network, and vice versa, - other hosts on the network can get arp replies from guests, but cannot talk IP to them. tcpdumping on the host suggests the br0 never even sees the packets intended for the guest. * Manually switching the eth* to promiscious mode makes stuff work. Cheers, weasel -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130104111712.25539.62770.report...@valiant.palfrader.org
Bug#697357: bridging broken over bond interfaces
On Fri, 04 Jan 2013, Bastian Blank wrote: On Fri, Jan 04, 2013 at 12:17:12PM +0100, Peter Palfrader wrote: I tried to set up a new KVM host in the usual way: - have a bond0 interface over all physcial eth* interfaces - create a br0 over that bond0 and any vnet* interfaces for the guests. Also, arp works through the bridge, forgot to mention that. * Manually switching the eth* to promiscious mode makes stuff work. Okay, so a workaround is available. When did it last work? Does it work with the kernel from experimental? It works nicely on stable, e.g. pasquini.debian.org: | weasel@pasquini:~$ sudo brctl show | bridge name bridge id STP enabled interfaces | br0 8000.e83935a9ec10 no bond0 | tap0 | tap1 | tap2 | br1 8000.e83935a9ec10 no bond0.221 | br2 8000.da1343affe92 no bond0.3301 | tap3 And there the bond interface is promisc automatically: weasel@pasquini:~$ ip a | grep -i bond | 2: eth0: BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP mtu 1500 qdisc pfifo_fast master bond0 state UP qlen 1000 | 3: eth1: BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP mtu 1500 qdisc pfifo_fast master bond0 state UP qlen 1000 | 4: bond0: BROADCAST,MULTICAST,PROMISC,MASTER,UP,LOWER_UP mtu 1500 qdisc noqueue state UP | 7: bond0.221@bond0: BROADCAST,MULTICAST,MASTER,UP,LOWER_UP mtu 1500 qdisc noqueue state UP | 9: bond0.3301@bond0: BROADCAST,MULTICAST,MASTER,UP,LOWER_UP mtu 1500 qdisc noqueue state UP Likewise it works as expected when one does br directly on eth0, without any bonding. It's also broken with linux-image-3.7-trunk-amd64_3.7.1-1~experimental.1_amd64.deb. Cheers, -- | .''`. ** Debian ** Peter Palfrader | : :' : The universal http://www.palfrader.org/ | `. `' Operating System | `-http://www.debian.org/ -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130104124012.gh14...@anguilla.noreply.org
Bug#585770: a collection of NULL pointer dereference [ipv6 and vlans?]
On Mon, 14 Jun 2010, Ben Hutchings wrote: On Sun, 2010-06-13 at 20:45 +0200, Peter Palfrader wrote: cimarosa.d.o runs linux-image-2.6.32-bpo.3-amd64 (from 2.6.32-9) just fine. However, it does not boot with linux-image-2.6.32-bpo.5-amd64 (2.6.32-15): During boot up, when init brings up the network we get various different kernel NULL pointer dereferences. Cimarosa has a lo, an eth0 and an eth0.221 vlan device. If the eth0.221 is not configured to be brought up on boot then the system boots correctly, and bringing up the interface later also appears to work without any ill effects. So there might be some racy thing going on. It'd be pretty sweet if cimarosa could be made to work with a recent debian kernel. [...] Could you try reverting the patch bugfix/all/vlan-macvlan-propagate-transmission-state-to-upper-layer.patch ? That appears to have helped. | * Rebuild without | bugfix/all/vlan-macvlan-propagate-transmission-state-to-upper-layer.patch. | - change macvlan-allow-multiple-driver-backends.patch to apply cleanly. wea...@cimarosa:~$ uname -a Linux cimarosa 2.6.32-5-amd64 #1 SMP Mon Jun 14 11:14:51 CEST 2010 x86_64 GNU/Linux wea...@cimarosa:~$ cat /proc/version Linux version 2.6.32-5-amd64 (Debian 2.6.32-15) (wea...@came.sbg.ac.at) (gcc version 4.3.2 (Debian 4.3.2-1.1) ) #1 SMP Mon Jun 14 11:14:51 CEST 2010 Cheers, weasel -- | .''`. ** Debian GNU/Linux ** Peter Palfrader | : :' : The universal http://www.palfrader.org/ | `. `' Operating System | `-http://www.debian.org/ -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100614111424.gn14...@anguilla.noreply.org
Bug#493863: closed by maximilian attems m...@stro.at (Re: firmware-bnx2: doesn't rebuild all initrds)
reopen 493863 thanks On Sun, 29 Mar 2009, Debian Bug Tracking System wrote: Maybe the firmware-bnx2 package should do update-initramfs -u -k all instead of just update-initramfs -u. no. it was explicitly asked that packages in postinst only update the newest initramfs (which can be the one which has the symlink). yes conservative people want to have least possible damage policy, but it is easily overridable. It didn't update the newest initramfs - for 2.6.24. It updated the one it was running at the time - 2.6.18. -- | .''`. ** Debian GNU/Linux ** Peter Palfrader | : :' : The universal http://www.palfrader.org/ | `. `' Operating System | `-http://www.debian.org/ -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#493863: closed by maximilian attems m...@stro.at (Re: firmware-bnx2: doesn't rebuild all initrds)
maximilian attems schrieb am Sonntag, dem 29. März 2009: On Sun, Mar 29, 2009 at 08:25:46PM +0200, Peter Palfrader wrote: maximilian attems schrieb am Sonntag, dem 29. März 2009: It didn't update the newest initramfs - for 2.6.24. It updated the one it was running at the time - 2.6.18. sure you had the initrd symlink pointing to that one. so it got attributed as the newest. I don't have symlinks. please post on that box output of sh -x update-initramfs -u Ah. there were symlinks in / - tho they were never ever used on this system. Seems pretty broken to rely on symlinks that might (and are) years out of date. -- | .''`. ** Debian GNU/Linux ** Peter Palfrader | : :' : The universal http://www.palfrader.org/ | `. `' Operating System | `-http://www.debian.org/ -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#514149: 2.6.26-1-openvz ooopses and dies
On Thu, 05 Feb 2009, Konstantin Khlebnikov wrote: try to boot with maxcpus=4 as kernel argument, That does make it boot up properly and not ooops immediately. -- | .''`. ** Debian GNU/Linux ** Peter Palfrader | : :' : The universal http://www.palfrader.org/ | `. `' Operating System | `-http://www.debian.org/ -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#514149: 2.6.26-1-openvz ooopses and dies
On Thu, 05 Feb 2009, Konstantin Khlebnikov wrote: try to boot with maxcpus=4 as kernel argument, and check 2.6.26-chekhov release rpm package from http://openvz.org (simple extract it via rpm2cpio .rpm | cpio -id and run mkinitramfs) And the checkov kernel appears to work also, with all 8 cores running. I think bug already fixed upstream, but still not merged into debian kernel. commit: http://git.openvz.org/?p=linux-2.6.26-openvz;a=commit;h=777e8164ebf8a03e43511983cdec472f8691a8af Can we expect that to be included for lenny r1? Cheers, Peter -- | .''`. ** Debian GNU/Linux ** Peter Palfrader | : :' : The universal http://www.palfrader.org/ | `. `' Operating System | `-http://www.debian.org/ -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#514149: 2.6.26-1-openvz ooopses and dies
Package: linux-image-2.6.26-1-openvz-amd64 Version: 2.6.26-13 Severity: grave Hi, I tried to boot linux-image-2.6.26-1-openvz-amd64 on a Sun Fire X4140. This is just booting the kernel, there aren't any containers or anything in the game yet. The first time it panicked and I had to reset the machine, the second time it booted through but started Oooopsing left and right as soon as I sshed in. Every command I typed in was killed immidiately. This i what the kernel log has to say after booting into a working kernel again: | Feb 4 19:24:04 ziva kernel: [ 23.415008] warning: `ntpd' uses 32-bit capabilities (legacy support in use) | Feb 4 19:24:21 ziva kernel: [ 44.248929] PGD 203067 PUD 207063 PMD 0 | Feb 4 19:24:21 ziva kernel: [ 44.248929] CPU: 6 | Feb 4 19:24:21 ziva kernel: [ 44.248929] Modules linked in: vzethdev vznetdev simfs vzrst vzcpt tun vzdquota vzmon vzdev xt_tcpudp xt_length ipt_ttl xt_tcpmss xt_TCPMSS iptable_mangle iptable_filter xt_multiport xt_limit xt_dscp ipt_REJECT ip_tables x_tables ipv6 cpufreq_userspace cpufreq_conservative cpufreq_powersave cpufreq_stats sg sr_mod cdrom powernow_k8 cpufreq_ondemand freq_table bonding snd_pcm snd_timer snd soundcore snd_page_alloc pcspkr button i2c_nforce2 i2c_core joydev evdev ext3 jbd mbcache ide_pci_generic ide_core ata_generic ses enclosure sd_mod usbhid hid ff_memless usb_storage sata_nv aacraid libata scsi_mod forcedeth ohci_hcd ehci_hcd dock thermal processor fan thermal_sys | Feb 4 19:24:21 ziva kernel: [ 44.248929] Pid: 3811, comm: bash Not tainted 2.6.26-1-openvz-amd64 #1 036test001 | Feb 4 19:24:21 ziva kernel: [ 44.248929] RIP: 0010:[8030161f] [8030161f] submit_bio+0xa9/0x134 | Feb 4 19:24:21 ziva kernel: [ 44.248929] RSP: 0018:81022484fae8 EFLAGS: 00010246 | Feb 4 19:24:21 ziva kernel: [ 44.248929] RAX: 8083c350 RBX: 810424898e40 RCX: 3000 | Feb 4 19:24:21 ziva kernel: [ 44.248929] RDX: 0018 RSI: 0018 RDI: | Feb 4 19:24:21 ziva kernel: [ 44.248929] RBP: R08: R09: 0200 | Feb 4 19:24:21 ziva kernel: [ 44.248929] R10: 810424898e40 R11: 0002 R12: 81022484fc18 | Feb 4 19:24:21 ziva kernel: [ 44.248929] R13: 810424898e40 R14: a0144a32 R15: 810226d0bea0 | Feb 4 19:24:21 ziva kernel: [ 44.248929] FS: 7fea32cb06e0() GS:81042662d340() knlGS: | Feb 4 19:24:21 ziva kernel: [ 44.248929] CS: 0010 DS: ES: CR0: 8005003b | Feb 4 19:24:21 ziva kernel: [ 44.248929] CR2: 8083c368 CR3: 0002245af000 CR4: 06e0 | Feb 4 19:24:21 ziva kernel: [ 44.248929] DR0: DR1: DR2: | Feb 4 19:24:21 ziva kernel: [ 44.248929] DR3: DR6: 0ff0 DR7: 0400 | Feb 4 19:24:21 ziva kernel: [ 44.248929] Process bash (pid: 3811, veid=0, threadinfo 81022484e000, task 810224406050) | Feb 4 19:24:21 ziva kernel: [ 44.248929] Stack: 2440c900 e2001096c4c0 e2001096c4c0 e2001096c4c0 | Feb 4 19:24:21 ziva kernel: [ 44.248929] 0001 e2001096c4c0 802c7b12 | Feb 4 19:24:21 ziva kernel: [ 44.248929] 81022484fc18 802c8745 a0144a32 810228000e00 | Feb 4 19:24:21 ziva kernel: [ 44.248929] Call Trace: | Feb 4 19:24:21 ziva kernel: [ 44.248929] [802c7b12] mpage_bio_submit+0x22/0x26 | Feb 4 19:24:21 ziva kernel: [ 44.248929] [802c8745] mpage_readpages+0xd1/0xe8 | Feb 4 19:24:21 ziva kernel: [ 44.248929] [a0144a32] :ext3:ext3_get_block+0x0/0xf9 | Feb 4 19:24:21 ziva kernel: [ 44.248929] [8027b3a1] __alloc_pages_internal+0x3f6/0x41a | Feb 4 19:24:21 ziva kernel: [ 44.248929] [80251f57] ub_kmemsize_charge+0x4e/0x86 | Feb 4 19:24:21 ziva kernel: [ 44.248929] [8027d0c6] __do_page_cache_readahead+0xf1/0x183 | Feb 4 19:24:21 ziva kernel: [ 44.248929] [8027d43f] ondemand_readahead+0x156/0x165 | Feb 4 19:24:21 ziva kernel: [ 44.248929] [802771a0] generic_file_aio_read+0x1d7/0x4a9 | Feb 4 19:24:21 ziva kernel: [ 44.248929] [802a0b63] do_sync_read+0xc9/0x10c | Feb 4 19:24:21 ziva kernel: [ 44.248929] [80247be5] autoremove_wake_function+0x0/0x2e | Feb 4 19:24:21 ziva kernel: [ 44.248929] [80288e6b] __vma_link+0x42/0x4b | Feb 4 19:24:21 ziva kernel: [ 44.248929] [802a1333] vfs_read+0xaa/0x152 | Feb 4 19:24:21 ziva kernel: [ 44.248929] [802a491d] kernel_read+0x38/0x4d | Feb 4 19:24:21 ziva kernel: [ 44.248929] [802a5af2] do_execve+0xf7/0x20f | Feb 4 19:24:21 ziva kernel: [ 44.248929] [8020a467] sys_execve+0x35/0x4c | Feb 4 19:24:21 ziva kernel: [ 44.248929] [8020c43a] stub_execve+0x6a/0xc0 | Feb
Bug#495919: kswapd0: page allocation failure. order:0, mode:0x20
Package: linux-2.6 Version: 2.6.26-3snapshot.12100 linux-image-2.6.26-1-vserver-686-bigmem 2.6.26-3snapshot.12100 appears to have page allocation failures: [186553.927388] kswapd0: page allocation failure. order:0, mode:0x20 [186553.927388] Pid: 193, comm: kswapd0 Not tainted 2.6.26-1-vserver-686-bigmem #1 [186553.927388] [c016a3a4] __alloc_pages_internal+0x344/0x358 [186553.927388] [c029ffad] tcp_rcv_established+0x3b3/0x636 [186553.927388] [c016a3c4] __alloc_pages+0x7/0x9 [186553.927388] [c01843b8] cache_alloc_refill+0x26f/0x48c [186553.931389] [c018464a] __kmalloc+0x75/0xb5 [186553.931389] [c0270a59] __alloc_skb+0x49/0xf7 [186553.931389] [c02717a5] __netdev_alloc_skb+0x14/0x2d [186553.931389] [f88846fe] tg3_alloc_rx_skb+0xb0/0x13b [tg3] [186553.931389] [c02747c9] netif_receive_skb+0x2d6/0x343 [186553.931389] [f4b4] tg3_poll+0x379/0x8b9 [tg3] [186553.931389] [c02764e6] net_rx_action+0x9c/0x177 [186553.931389] [c012d529] __do_softirq+0x66/0xd3 [186553.931389] [c012d5db] do_softirq+0x45/0x53 [186553.931389] [c012d892] irq_exit+0x35/0x67 [186553.931389] [c01152a1] smp_apic_timer_interrupt+0x6b/0x76 [186553.931389] [c0109364] apic_timer_interrupt+0x28/0x30 [186553.931389] [c019860f] dispose_list+0x8c/0xc2 [186553.931389] [c01987d4] shrink_icache_memory+0x18f/0x1b7 [186553.931389] [c016e1aa] shrink_slab+0xd3/0x132 [186553.931389] [c016e82b] kswapd+0x29b/0x3ed [186553.931389] [c016d230] isolate_pages_global+0x0/0x42 [186553.931389] [c01392e0] autoremove_wake_function+0x0/0x2d [186553.931389] [c016e590] kswapd+0x0/0x3ed [186553.931389] [c013921d] kthread+0x38/0x5f [186553.931389] [c01391e5] kthread+0x0/0x5f [186553.931389] [c01094f3] kernel_thread_helper+0x7/0x10 [186553.931389] === [186553.931389] Mem-info: [186553.931389] DMA per-cpu: [186553.931389] CPU0: hi:0, btch: 1 usd: 0 [186553.931389] CPU1: hi:0, btch: 1 usd: 0 [186553.931389] CPU2: hi:0, btch: 1 usd: 0 [186553.931389] CPU3: hi:0, btch: 1 usd: 0 [186553.931389] Normal per-cpu: [186553.931389] CPU0: hi: 186, btch: 31 usd: 64 [186553.931389] CPU1: hi: 186, btch: 31 usd: 179 [186553.931389] CPU2: hi: 186, btch: 31 usd: 58 [186553.931389] CPU3: hi: 186, btch: 31 usd: 160 [186553.931389] HighMem per-cpu: [186553.931389] CPU0: hi: 186, btch: 31 usd: 3 [186553.931389] CPU1: hi: 186, btch: 31 usd: 28 [186553.931389] CPU2: hi: 186, btch: 31 usd: 40 [186553.931389] CPU3: hi: 186, btch: 31 usd: 181 [186553.931389] Active:183441 inactive:988359 dirty:120 writeback:0 unstable:0 [186553.931389] free:789746 slab:92793 mapped:10406 pagetables:696 bounce:0 [186553.931389] DMA free:3504kB min:68kB low:84kB high:100kB active:716kB inactive:272kB present:16256kB pages_scanned:0 all_unreclaimable? no [186553.931389] lowmem_reserve[]: 0 873 8556 8556 [186553.931389] Normal free:1540kB min:3744kB low:4680kB high:5616kB active:207836kB inactive:235076kB present:894080kB pages_scanned:0 all_unreclaimable? no [186553.931389] lowmem_reserve[]: 0 0 61467 61467 [186553.931389] HighMem free:3153940kB min:512kB low:8756kB high:17000kB active:525212kB inactive:3718088kB present:7867900kB pages_scanned:0 all_unreclaimable? no [186553.931389] lowmem_reserve[]: 0 0 0 0 [186553.931389] DMA: 364*4kB 0*8kB 0*16kB 0*32kB 0*64kB 0*128kB 0*256kB 0*512kB 0*1024kB 1*2048kB 0*4096kB = 3504kB [186553.931389] Normal: 63*4kB 0*8kB 1*16kB 1*32kB 0*64kB 0*128kB 1*256kB 0*512kB 1*1024kB 0*2048kB 0*4096kB = 1580kB [186553.931389] HighMem: 130*4kB 52*8kB 107*16kB 90*32kB 46*64kB 25*128kB 10*256kB 2*512kB 3*1024kB 169*2048kB 681*4096kB = 3153816kB [186553.931389] 1150784 total pagecache pages [186553.931389] Swap cache: add 13, delete 0, find 0/0 [186553.931389] Free swap = 7813140kB [186553.931389] Total swap = 7813192kB [186553.931389] 2211839 pages of RAM [186553.931389] 1982463 pages of HIGHMEM [186553.931389] 149619 reserved pages [186553.931389] 226218 pages shared [186553.931389] 13 pages swap cached [186553.931389] 120 pages dirty [186553.931389] 0 pages writeback [186553.931389] 10406 pages mapped [186553.931389] 92793 pages slab [186553.931389] 696 pages pagetables -- | .''`. ** Debian GNU/Linux ** Peter Palfrader | : :' : The universal http://www.palfrader.org/ | `. `' Operating System | `-http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#494365: 2.6.26 hangs on opteron CPUs
On Fri, Aug 08, 2008 at 08:51:33PM +0200, Peter Palfrader wrote: it seems that 2.6.26 (whether the debian package or the kernel.org kernel) locks up after a while on Debian's DL385G1 systems. On Mon, Aug 11, 2008 at 11:17:34PM -0600, dann frazier wrote: hey Peter, This is readily reproducible - a simple kernel compile was all it took. git bisecting suggests that this issue was introduced by [1] and unmasked by [2] during 2.6.26 devlopment. It was later fixed during 2.6.27 development by [3]. Can you confirm that the attached backport of [3] fixes the problem for you? [3] 8004dd965b13b01a96def054d420f6df7ff22d53 I upgraded several of Debian's machines to 2.6.26.2 plus the patch you provided. So far they are still running - and I put them under load that would reliably kill them before. Thanks, weasel -- | .''`. ** Debian GNU/Linux ** Peter Palfrader | : :' : The universal http://www.palfrader.org/ | `. `' Operating System | `-http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#494365: 2.6.26 hangs on opteron CPUs
Package: linux-image-2.6.26-1-amd64 Version: 2.6.26-1 Severity: important Hi, it seems that 2.6.26 (whether the debian package or the kernel.org kernel) locks up after a while on Debian's DL385G1 systems. After a while, sooner with more disk IO/filesystem load, the system hangs: it continues to do stuff but everything involving disk hangs forever. The systems work just fine on a 2.6.25.10 kernel. The servers have Opterons like this: cpu family : 15 model : 33 so http://www.uwsg.iu.edu/hypermail/linux/kernel/0808.0/0882.html might explain it. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#493863: firmware-bnx2: doesn't rebuild all initrds
Package: firmware-bnx2 Version: 0.4+etchnhalf.1 Severity: important I installed the etchnhalf kernel, rebooted only to find out that I had not network, booted the old kernel again and installed firmware-bnx2: | thelma:~# apt-get install firmware-bnx2 | Reading package lists... Done | Building dependency tree... Done | The following NEW packages will be installed: | firmware-bnx2 | 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. | Need to get 104kB of archives. | After unpacking 279kB of additional disk space will be used. | Get:1 http://mirror.came.sbg.ac.at etch/non-free firmware-bnx2 0.4+etchnhalf.1 [104kB] | Fetched 104kB in 0s (1818kB/s) | Selecting previously deselected package firmware-bnx2. | (Reading database ... 62627 files and directories currently installed.) | Unpacking firmware-bnx2 (from .../firmware-bnx2_0.4+etchnhalf.1_all.deb) ... | Setting up firmware-bnx2 (0.4+etchnhalf.1) ... | update-initramfs: Generating /boot/initrd.img-2.6.18-5-amd64 Note how it doesn't rebuild the 2.6.24 etchnhalf initrd. Needless to say the system still didn't properly boot, only purging and reinstalling the linux-image-2.6.24-etchnhalf.1-amd64 did the trick. Maybe the firmware-bnx2 package should do update-initramfs -u -k all instead of just update-initramfs -u. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#409313: linux-image-2.6.18-4-sparc64: Netra X1 - Kernel unaligned access in rp_rcv and ip_fast_csum
On Thu, 01 Mar 2007, Emanuele Rocca wrote:
Hello Peter,
* Peter Palfrader [EMAIL PROTECTED], [2007-03-01 0:53 +0100]:
On Tue, 27 Feb 2007, Emanuele Rocca wrote:
http://article.gmane.org/gmane.linux.ports.sparc/7178
I'll also test the patch tomorrow and let you know how it works out.
I guess it should work but yeah, please try it out.
I can confirm that the patch at the location above fixes the unaligned
access problems I have been reporting. Network access is now fast and
lag free and no silly warnings filling up the logs.
for reference again, this is the patch:
--- a/drivers/net/tulip/tulip_core.c
+++ b/drivers/net/tulip/tulip_core.c
@@ -67,7 +67,7 @@ const char * const medianame[32] = {
/* Set the copy breakpoint for the copy-only-tiny-buffer Rx structure. */
#if defined(__alpha__) || defined(__arm__) || defined(__hppa__) \
- || defined(__sparc_) || defined(__ia64__) \
+ || defined(__sparc__) || defined(__ia64__) \
|| defined(__sh__) || defined(__mips__)
static int rx_copybreak = 1518;
#else
--
| .''`. ** Debian GNU/Linux **
Peter Palfrader | : :' : The universal
http://www.palfrader.org/ | `. `' Operating System
| `-http://www.debian.org/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#409313: linux-image-2.6.18-4-sparc64: Netra X1 - Kernel unaligned access in rp_rcv and ip_fast_csum
On Tue, 27 Feb 2007, Emanuele Rocca wrote: Hello, * Peter Palfrader [EMAIL PROTECTED], [2007-02-20 18:18 +0100]: On Thu, 01 Feb 2007, Richard Mortimer wrote: Kernel unaligned access at TPC[5e4420] ip_rcv+0xd0/0x58c Kernel unaligned access at TPC[517f84] ip_fast_csum+0xc/0x80 Kernel unaligned access at TPC[517f88] ip_fast_csum+0x10/0x80 Kernel unaligned access at TPC[517f8c] ip_fast_csum+0x14/0x80 Kernel unaligned access at TPC[517f94] ip_fast_csum+0x1c/0x80 Same on a v100, both on 2.6.18-4, and a self compiled 2.6.20.1. Could you guys apply the following patch and see if it solves the ip_rcv issue? I wrote it a bit blindly as I cannot reproduce the problem on my system (a Blade). +#include asm/unaligned.h - len = ntohs(iph-tot_len); + len = ntohs(get_unaligned(iph-tot_len)); I'm afraid that didn't fix it. My sparc doesn't do much or anything yet, would access to it be helpful? Peter -- | .''`. ** Debian GNU/Linux ** Peter Palfrader | : :' : The universal http://www.palfrader.org/ | `. `' Operating System | `-http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#409313: linux-image-2.6.18-4-sparc64: Netra X1 - Kernel unaligned access in rp_rcv and ip_fast_csum
On Thu, 01 Feb 2007, Richard Mortimer wrote: Kernel unaligned access at TPC[5e4420] ip_rcv+0xd0/0x58c Kernel unaligned access at TPC[517f84] ip_fast_csum+0xc/0x80 Kernel unaligned access at TPC[517f88] ip_fast_csum+0x10/0x80 Kernel unaligned access at TPC[517f8c] ip_fast_csum+0x14/0x80 Kernel unaligned access at TPC[517f94] ip_fast_csum+0x1c/0x80 Same on a v100, both on 2.6.18-4, and a self compiled 2.6.20.1. Peter -- | .''`. ** Debian GNU/Linux ** Peter Palfrader | : :' : The universal http://www.palfrader.org/ | `. `' Operating System | `-http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#399691: same here, no net with b44
reassign 399691 linux-image-2.6.18-3-xen-k7 thanks This bug is also present in the now current -3 version of the kernel. I have the same problem here: | Jan 23 12:10:44 uschi kernel: b44.c:v1.01 (Jun 16, 2006) | Jan 23 12:10:44 uschi kernel: ACPI: PCI Interrupt :00:0b.0[A] - GSI 18 (level, low) - IRQ 16 | Jan 23 12:10:44 uschi kernel: ACPI: PCI interrupt for device :00:0b.0 disabled | Jan 23 12:10:44 uschi kernel: b44: probe of :00:0b.0 failed with error -5 and no interface then. Apparently fedora fixed this about two months ago, see https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=208242 Cheers, Peter -- | .''`. ** Debian GNU/Linux ** Peter Palfrader | : :' : The universal http://www.palfrader.org/ | `. `' Operating System | `-http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
