Your message dated Mon, 04 Jun 2012 07:16:30 +0100
with message-id <1338790590.3979.189.camel@deadeye>
and subject line Re: Xen system can't boot with a damaged audio card
has caused the Debian Bug report #630671,
regarding Xen system can't boot with a damaged audio card
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
630671: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=630671
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: xen-linux-system-2.6.32-5-xen-686
Distribution : Debian GNU/Linux 6.0 Squeeze
Hardware: Dell Optiplex 360
CPU: Pentium(R) Dual-Core CPU E5300 @ 2.60GHz
Configured Xen according official wiki http://wiki.debian.org/Xen
aptitude -P install xen-linux-system
mv -i /etc/grub.d/10_linux /etc/grub.d/21_linuxupdate-grub
chmod +x /etc/xen/scripts/*
When I reboot I got error output like this:
udevd[297]: worker[332] unexpectedly returned with status 0x000b
udevd[297]: worker[333] unexpectedly returned with status 0x000b
Boot process hangs and I can't enter system.
My audio card has problem. There is no sound after installation. So I guess
it maybe related to this issue.
audio card information
00:1b.0 Audio device: Intel Corporation N10/ICH 7 Family High Definition
Audio Controller (rev 01)
Subsystem: Dell Device 0294
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 16
Region 0: Memory at dfdfc000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [50] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=55mA
PME(D0+,D1-,D2-,D3hot+,D3cold+
)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [60] MSI: Enable- Count=1/1 Maskable- 64bit+
Address: 0000000000000000 Data: 0000
Capabilities: [70] Express (v1) Root Complex Integrated Endpoint,
MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s
<64ns, L1 <1us
ExtTag- RBE- FLReset-
DevCtl: Report errors: Correctable- Non-Fatal- Fatal-
Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop+
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+
TransPend-
LnkCap: Port #0, Speed unknown, Width x0, ASPM unknown,
Latency L0 <64ns, L1 <1us
ClockPM- Surprise- LLActRep- BwNot-
LnkCtl: ASPM Disabled; Disabled- Retrain- CommClk-
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed unknown, Width x0, TrErr- Train- SlotClk-
DLActive- BWMgmt- ABWMgmt-
Capabilities: [100 v1] Virtual Channel
Caps: LPEVC=0 RefClk=100ns PATEntryBits=1
Arb: Fixed- WRR32- WRR64- WRR128-
Ctrl: ArbSelect=Fixed
Status: InProgress-
VC0: Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
Arb: Fixed- WRR32- WRR64- WRR128- TWRR128-
WRR256-
Ctrl: Enable+ ID=0 ArbSelect=Fixed TC/VC=01
Status: NegoPending- InProgress-
VC1: Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
Arb: Fixed- WRR32- WRR64- WRR128- TWRR128-
WRR256-
Ctrl: Enable+ ID=1 ArbSelect=Fixed TC/VC=80
Status: NegoPending- InProgress-
Capabilities: [130 v1] Root Complex Link
Desc: PortNumber=0f ComponentID=02 EltType=Config
Link0: Desc: TargetPort=00 TargetComponent=02 AssocRCRB-
LinkType=MemMapped LinkValid+
Addr: 00000000feda8000
Kernel driver in use: HDA Intel
So anyone has a solution?
--
Best Regards.
Leftuesc
--- End Message ---
--- Begin Message ---
Closing due to lack of response.
Ben.
--
Ben Hutchings
It is impossible to make anything foolproof because fools are so ingenious.
signature.asc
Description: This is a digitally signed message part
--- End Message ---
